Bon bon bon.. la c'est la depression ^^
Meme constat avec un autre alim, la question c'est est ce que c'est "le même" soucis ou est ce que c'est juste mon ali "test" qui fourni pas assez de watts pour ma config, comment faire le différence ?
( test Whocrashed 17h00 ancienne alim. 19h50 nouvelle alim.
Welcome to WhoCrashed (HOME EDITION) v 6.01
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution.
Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows a lot of system crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue or black screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
To obtain technical support visit
www.resplendence.com/support
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report ...
Home Edition Notice
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.
Please note that this version of WhoCrashed is not licensed for use by professional support engineers.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
System Information (local)
Computer name: DESKTOP-AHQCKML
Windows version: Windows 10 , 10.0, build: 16299
Windows dir: C:\Windows
Hardware: ASRock, P67 Pro
CPU: GenuineIntel Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17141714944 bytes total
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Mon 16/04/2018 19:57:29 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\041618-4828-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x175930)
Bugcheck code: 0x101 (0x18, 0x0, 0xFFFF9001117A9180, 0x4)
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 Mon 16/04/2018 19:57:29 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module:
hal.dll (hal!halperformendofinterrupt+0x186)
Bugcheck code: 0x101 (0x18, 0x0, 0xFFFF9001117A9180, 0x4)
Error:
CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\hal.dll
product:
Microsoft® Windows® Operating System
company:
Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 Mon 16/04/2018 17:02:44 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\041618-6500-01.dmp
This was probably caused by the following module:
hal.dll (hal+0x3BEFF)
Bugcheck code: 0x124 (0x0, 0xFFFF948E81AF0028, 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 Mon 16/04/2018 16:28:24 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\041618-5484-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x175930)
Bugcheck code: 0x101 (0x18, 0x0, 0xFFFF8C80B290F180, 0x6)
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 Mon 16/04/2018 15:19:08 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\041618-5437-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x175930)
Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFAB0105F0F180, 0x6)
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 Sun 15/04/2018 17:37:23 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\041518-5250-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x1640E0)
Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFBE8014479180, 0x5)
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.
Conclusion
6 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.
