Bonjour à tous,
 
J'ai acheté il y a 3 mois environ mon PC, que j'ai monté par mes soins.
 
Voici les specs rapidement :
 
Système d'exploitation
   Windows 7 Édition Familiale Premium 64-bit SP1
  Processeur
   Intel Core i5 4670K @ 3.40GHz 28 °C
   Technologie Haswell 22nm
  RAM
   8,00 Go Canal-Double DDR3 @ 799 MHz (11-11-11-28)
  Carte mère
   MSI Z87-G45 GAMING (MS-7821) (SOCKET 0) 31 °C
  Graphiques
   ASUS VN247 (1920x1080@60Hz)
   3071 MoNVIDIA GeForce GTX 780 (ASUStek Computer Inc) 27 °C
  Stockage
   119GB PLEXTOR PX-128M5Pro SCSI Disk Device (SSD)
   1863GB Seagate ST2000DM 001-1CH164 SCSI Disk Device (SATA) 30 °C
  Disques optiques
   Aucun disque optique détecté
  Audio
   NVIDIA High Definition Audio
 
Voilà le problème, depuis quelques semaines je suis sujet à des BS et les informaticiens semblent me dire que c'est du à une alimentation sous dimensionnée  :
 
J'ai une Seasonic G-550, est il utile d'en prendre une plus grosse, comme la 650 ?
 
Merci d'avance pour vos réponses.
 
Pierre

1 - Les températures à coté des composants ça vient d'où ?
2 - Qui sont ces informaticiens ?
3 - L'alim est très bien, elle n'est pas du tout sous-dimensionnée...  (CPU 100W maxi avec un ptit OC, cg 250W maxi avec oc en bench... je te laisse faire le calcul )
4 - Peux-tu poster les rapport BSOD ? soit une capture d'écran soit tu installes un logiciel pour récupérer les bsod (Google est ton ami )
5 - ça arrive n'importe quand ces bsod ? en jeux ? tu as fait un OCCT ? (cpu, gpu, alim)
Merci

edit :
6 - pourquoi les "informaticiens" disent que ça vient de l'alim sous-dimensionnée alors que c'est assez récent les BSOD ? (ou alors c'est depuis le début ?...) bref, c'est pas logique

Oups, j'avais pas eu de notification ..
 
 
 
1- J'utilise speccy qui me donne toutes les caractéristiques de mon pc en 2s
2-Daltoner et des dépanneurs infos
3-C'est ce que je pensais mais chez Daltoner ils me disent que la 780 peut passer 400W en pic .. pour le calcul j'avais fait le mm que le tien quand j'ai commandé
4-Je peux les poster, j'utilise WhoCrashed pour lire les minidump
5- en jeu les 3, les 2 premiers sous BF et les derniers sous LOL (?!) Je n'ai pas OCCT mais chez Daltoner il me disent que ca peut cramer l'alim si je le tente et que l'alim est bien sous dimensionnée ?!
 
6- en fait j'ai acheté tout mon pc excepté la CG début avril et la CG début mai, et c'est suite à ça que j'ai eu des BSOD

1- ça me parait bien froid comme température, tu as mis ton pc dans le congelo ? pour ça que je te demande d'où ça vient... surtout si tu as le ventirad stock, 28°C pour les cpu, c'est plus que correct...

2- Bah retourne plus chez eux, du grand n'importe quoi...

3- Tu peux effectivement avoir des pics de consommation mais l'alim encaissera sans problème. peut être pas 400w mais 300w en pics oui pourquoi pas

4-bah on attend

5- cramer l'alim Du grand n'importe quoi. Seasonic est LA marque des alims, il y a toutes les protections qu'il faut dedans, pas comme ces mer** d'heden et advance.
Tu ne prends aucun risque à faire des test occt avec une telle alim, tout le monde te le confirmera
Au pire, si il y a un soucis, elle se coupera toute seule mais jamais elle cramera (enfin je l'espere )

6- un soucis avec les drivers peut être alors ?

bon bien sur on est jamais à couvert d'un défaut de fabrication mais bon....

1- Non j'ai un gros bouzin, Dark rock pro 3, et les t°C ici sont au repos
 
4- je les poste
 
6-tout à jour

Voilà les rapports :  
 
Je vais copier coller les 3 analyses de WhoCrashed à suivre, désolé pour le pavé.
 
On Mon 12/05/2014 20:24:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051214-4882-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4211)  
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800D1DD828, 0xFFFFF8800D1DD080, 0xFFFFF880012C3E83)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates a problem occurred in the NTFS file system.  
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.  
 
On Mon 12/05/2014 20:24:11 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: eamonm.sys (eamonm+0x29EA6)  
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800D1DD828, 0xFFFFF8800D1DD080, 0xFFFFF880012C3E83)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\eamonm.sys
product: ESET Smart Security
company: ESET
description: Amon monitor
Bug check description: This indicates a problem occurred in the NTFS file system.  
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: eamonm.sys (Amon monitor, ESET).  
Google query: ESET NTFS_FILE_SYSTEM
 
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
 
2 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:  
 
eamonm.sys (Amon monitor, ESET)
 
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
 
 
Read the topic general suggestions for troubleshooting system crashes for more information.  
 
 
 
On Sat 17/05/2014 20:16:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051714-4867-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)  
Bugcheck code: 0xA (0x831E9D0, 0x2, 0x1, 0xFFFFF800030DFBC4)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.  
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.  
 
On Sat 17/05/2014 20:16:17 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: iusb3xhc.sys (iusb3xhc+0x24140)  
Bugcheck code: 0xA (0x831E9D0, 0x2, 0x1, 0xFFFFF800030DFBC4)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\iusb3xhc.sys
product: USB 3.0 Device Driver
company: Intel Corporation
description: Intel® USB 3.0 eXtensible Host Controller Driver
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.  
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: iusb3xhc.sys (Intel® USB 3.0 eXtensible Host Controller Driver, Intel Corporation).  
Google query: Intel Corporation IRQL_NOT_LESS_OR_EQUAL
 
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
 
3 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:  
 
iusb3xhc.sys (Intel® USB 3.0 eXtensible Host Controller Driver, Intel Corporation)
 
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
 
 
Read the topic general suggestions for troubleshooting system crashes for more information.  
 
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.  
 
 
 
On Mon 26/05/2014 21:14:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052614-4508-01.dmp
This was probably caused by the following module: ks.sys (ks+0x10B60)  
Bugcheck code: 0xBE (0xFFFFF88004CD1B60, 0x800000020E989121, 0xFFFFF88009D4F3F0, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\drivers\ks.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel CSA Library
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.  
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.  
 
On Mon 26/05/2014 21:14:54 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ks.sys (ks!KsPinSetPinClockTime+0x1540)  
Bugcheck code: 0xBE (0xFFFFF88004CD1B60, 0x800000020E989121, 0xFFFFF88009D4F3F0, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\drivers\ks.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel CSA Library
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.  
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.  
 
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
 
4 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.  
 
 
Read the topic general suggestions for troubleshooting system crashes for more information.  
 
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.