Bonjour,
Depuis plusieurs jour j'ai des soucis de bluescreen, ça a commencer avec une Whea Uncorrectable error, j'ai donc fais des test hardware, j'ai pu test la CM (remplacer par une neuve de la meme marque), la ram(remplacer par des neuves de la meme marque), le GPU(remplacer par une 770GTX que j'avais en rab) et tester mes disques dur(M2 samsung Evo, 2 SSD et 1 SSHD) , mais les bluescreen on persistés, avec plein de message d'erreur différent.
Ces bluescreen qui apparaissait juste apres le logo de ma CM, donc sur le logo Windows. J'ai réussi a boot en changeant en voltage de mon CPU de 1.2V à 1.4V. J'arrive donc sur le bureau mais ça pas changer grand chose vu que dès que je fais un peu travailler l'ordinateur les bluescreen reviennent. J'ai juste une fois réussi a lancer un jeu mais là l'ordinateur c'est coupé net sans bluescreen, comme une coupure d'electricité. Je vais pouvoir bientot tester une nouvelle alimentation pour voir si ça pourrait venir de ça.... Mais l'histoire du voltage m'intérroge vraiment.
Merci de m'avoir lu.
Carte Mere Z390 Aorus Ultra
Carte Graphique 1070 Nvidia
Ram Vengeance DDR4 LPX 3000 mhz 32go
Proc I9-9900K
Alimentation Antec 650W (2012) (bientot remplacer par une 750W neuve)
Je vous joins également les rapports de Whocrashed que j'ai pu avoir.
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Tue 30/04/2019 18:57:33 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\043019-5609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B3730)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8014533CF32, 0x1, 0xFFFFDA8D400E0068)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 30/04/2019 18:57:33 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: fltmgr.sys (FLTMGR!FltDecodeParameters+0x98D)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8014533CF32, 0x1, 0xFFFFDA8D400E0068)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
On Tue 30/04/2019 18:40:01 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\043019-5578-01.dmp
This was probably caused by the following module: hal.dll (hal+0x42C77)
Bugcheck code: 0x124 (0x0, 0xFFFFB70ABF3C5028, 0xBE000000, 0x800400)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is 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 Tue 30/04/2019 18:24:20 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\043019-6453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B3730)
Bugcheck code: 0x101 (0xC, 0x0, 0xFFFF95001FD12180, 0xC)
Error: CLOCK_WATCHDOG_TIMEOUT
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 an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (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 Tue 30/04/2019 18:22:44 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\043019-6843-02.dmp
This was probably caused by the following module: Unknown (0x000000000000000C)
Bugcheck code: 0x101 (0xC, 0x0, 0xFFFFCC016B0E8180, 0xC)
Error: CLOCK_WATCHDOG_TIMEOUT
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (thermal issue).
A third party driver was identified as the probable root cause of this system error.
Google query: CLOCK_WATCHDOG_TIMEOUT
On Tue 30/04/2019 18:21:15 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\043019-6859-01.dmp
This was probably caused by the following module: hal.dll (hal+0x42C77)
Bugcheck code: 0x124 (0x0, 0xFFFFA6882DB4D028, 0xBE000000, 0x800400)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is 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.
