Bonjour,
J'ai changé investis recemment dans un nouveau processeur et un ventirad (i7 4790k + Cooler Master Hyper 212), je suis repartis du neuf et formatant ma machine et a part 1 plantage que je mettais sur le compte des drivers pas finis de mettre a jour, tous tourné bien.
Mais depuis hier j'ai eu 4 BSOD avec jamais le même code d'erreur ...
Apres chaque plantage, le pc tente de redémarrer seul, les ventilos se lancent 1 secondes pui s'arrette, et retente de se lancer et ainsi de suite. Un peu comme si l'alim n'avais pas assez de pêche pour faire tourné le système. Je suis obliger de débrancher le cordon pour mettre fin a la boucle de redemarrage. Apres le pc se relance impeccable.
Les temperatures sont bonnes, les drivers sont a jours.
Dans l'observateur d'événement, j'ai en erreur critique le Kernel-Power Evenement 41 Catégorie 63, j'ai un peu chercher de mon coté et j'ai l'impression que ça peux être un peu tout est rien.
Voici mon log WhoCrashed :
System Information (local)
Computer name: RMX
Windows version: Windows 10 , 10.0, build: 15063
Windows dir: C:\WINDOWS
Hardware: MS-7823, MSI, B85M-G43 (MS-7823)
CPU: GenuineIntel Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 21330137088 bytes total
Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sat 26/08/2017 19:13:46 your computer crashed
crash dump file: C:\WINDOWS\Minidump\082617-5343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C560)
Bugcheck code: 0x19 (0xE, 0xFFFFE10751626840, 0x0, 0x8FC6B945A816D184)
Error: BAD_POOL_HEADER
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 a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
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 26/08/2017 19:13:46 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x19 (0xE, 0xFFFFE10751626840, 0x0, 0x8FC6B945A816D184)
Error: BAD_POOL_HEADER
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
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 26/08/2017 19:11:39 your computer crashed
crash dump file: C:\WINDOWS\Minidump\082617-5609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C560)
Bugcheck code: 0x192 (0xFFFFA78399A787C0, 0xFFFFA7838F945B40, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 25/08/2017 21:46:00 your computer crashed
crash dump file: C:\WINDOWS\Minidump\082517-6046-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x355E)
Bugcheck code: 0x119 (0x1, 0x6867EE, 0x6867EE, 0xFFFFC70E6EECA010)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\WINDOWS\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
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 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.
Merci d'avance pour votre aide.
J'oubliez, j'ai une gtx 970, une alim 500W Corsair et 20Go de ram
