BSOD caused by ntoskrnl.exe and hal.dll

clammy77 · Apr 29, 2017

Hi! would really need help w/ this super annoying BSOD issue.

Windows 7 64 bit/i7-4790K/16GB/GTX 1060 6GB

Graphics card was recently upgraded, and BSOD existed prior to upgrading.

CPU/RAM not overclocked. Here are the minidump files:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\042717-7285-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`05064000 PsLoadedModuleList = 0xfffff800`052a6730
Debug session time: Thu Apr 27 12:10:30.011 2017 (GMT+8)
System Uptime: 0 days 0:00:03.776
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................

Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800d4e58f8, 0, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
Unable to load image PSHED.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PSHED.dll
*** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : hardware

Followup: MachineOwner
---------

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\042117-96876-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23714.amd64fre.win7sp1_ldr.170307-1800
Machine Name:
Kernel base = 0xfffff800`05008000 PsLoadedModuleList = 0xfffff800`0524a730
Debug session time: Fri Apr 21 11:09:34.030 2017 (GMT+8)
System Uptime: 2 days 15:59:29.795
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
.....................
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800d67b028, be000000, 800400}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
Unable to load image \SystemRoot\system32\PSHED.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PSHED.dll
*** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : hardware

Followup: MachineOwner

johnbl · Apr 30, 2017

your graphics card pulled too much power from the pci/e motherboard slot, your motherboard logic detected this and reset the CPU to stop the power draw. Your PSU failed to prevent the CPU from restarting and lied that the power was good so the motherboard restarted with bad CPU power, then the CPU started running and got an internal error on its bus and called a bugcheck 0x124.

I would be looking for a under rated power supply, or failure to connect PSU to GPU power connections.

I would ignore this bugcheck and focus on why the CPU was reset.
(IE power problem to GPU)

clammy77 · Apr 30, 2017

johnbl :

Thanks so much man! i actually suspected this. Just to make sure this is what you're suggesting:

1. check the GPU power connection with the PSU or
2. replace the PSU to a higher output one?

Also can the CPU be resetting due to a faulty motherboard? like voltage regulator failure?

johnbl · May 1, 2017

check the power connections first. Then check the rating for the power connection for your PSU
most often the better rated supplies will be single rail power supplies but the bronze/gold/... rating will have an effect when you start to push the limits. IE a GPU heats up it pulls more power, if it pulls too much then the GPU takes the extra power from the motherboard slot. if still too much, the motherboard logic will reset the CPU.

Sometimes you can remove your overclocking drivers for your GPU, or even underclock the GPU to see if it helps.
if you don't get audio to your monitor by the GPU HDMI or displayport cable you can disable the GPU audio support and save a little power and driver overhead.

you can turn up the fans on the GPU and reduce the power requirements also.
(less power if it is cooler)

you could also get this with a faulty motherboard but most of the time I just see people putting in a new low power CPU without updating the BIOS. The bios has to be modified for certain CPUs that use low power or it will provide too high voltage to the CPU and can lead to this error also.
(generally make sure your BIOS release date is newer than the date that your CPU was released.)

clammy77 :

clammy77 · May 5, 2017

Here's my specs:
Asrock Z97 Killer
i7-4790k
GTX 1060 6GB
16GB
Xclio PSU - 750W 80Plus Gold Max AMP is 62A

PSU wise should be okay, checked all connections too, will try to underclock and see if that will stabilize it. Will report back!

clammy77 · May 24, 2017

Hi, I bought a new PSU, 92%+ efficiency, coolermaster 750W. Comp still continues to crash. Any other ideas? Can be motherboard issue?

clammy77 · Jun 3, 2017

johnbl :

check the power connections first. Then check the rating for the power connection for your PSU
most often the better rated supplies will be single rail power supplies but the bronze/gold/... rating will have an effect when you start to push the limits. IE a GPU heats up it pulls more power, if it pulls too much then the GPU takes the extra power from the motherboard slot. if still too much, the motherboard logic will reset the CPU.

Sometimes you can remove your overclocking drivers for your GPU, or even underclock the GPU to see if it helps.
if you don't get audio to your monitor by the GPU HDMI or displayport cable you can disable the GPU audio support and save a little power and driver overhead.

you can turn up the fans on the GPU and reduce the power requirements also.
(less power if it is cooler)

you could also get this with a faulty motherboard but most of the time I just see people putting in a new low power CPU without updating the BIOS. The bios has to be modified for certain CPUs that use low power or it will provide too high voltage to the CPU and can lead to this error also.
(generally make sure your BIOS release date is newer than the date that your CPU was released.)

clammy77 :

Hi there, after changing PSU, same thing happens. Any other solutions?

clammy77 · Sep 7, 2017

Hi guys, I was unable to fix the computer, I've now replaced the GPU, power supply, 16GB Ram, SSD, ethernet card, but the BSOD remains.

Here's my last 5 dumps, please help!

https://www.dropbox.com/sh/8vk3por8e906oix/AAAov8haUU4ydbmqSi3qkZtfa?dl=0

johnbl · Sep 9, 2017

could not read the bios info.
update the bios or reset it to defaults if it is already up to date.
it looks like the motherboard logic reset the CPU because of a power or heating problem. On the reboot the cpu detected a error and called a bugcheck 0x124

first question: do you think the system was running longer than 4.7 seconds. if so, then most likely you have a power issue detected by the motherboard logic. You will want to check the temps and maybe run the intel cpu diagnostics. most likely the bugcheck 0x124 is a secondary effect, IE the motherboard detects a power issue, resets the CPU to protect the motherboard. The CPU restarts because the power supply does not put out a proper power_ok signal. This causes the CPU to restart with incorrect power, the CPU detects a internal error and calls the bugcheck 0x124. the cpu could be hot (and use too much power) bios settings can be corrupted (happens with auto overclocking, or battery backup failures on old motherboard) update or clear and reconfigure the bios would be my first attempt at a fix. generally, the bios has to be very old or really messed up for the debugger not to be able to read it.

System Uptime: 0 days 0:00:04.759
system was up for 4.7 seconds
bugcheck 0x124 called by the cpu
Error : Internal timer (Proc 0 Bank 4)
Proc. Type : x86/x64
Instr. Set : x64
Error Type : Micro-Architectural Error
Severity : Fatal
Error : Internal timer (Proc 0 Bank 4)
Status : 0xbe00000000800400

clammy77 · Sep 9, 2017

johnbl :

Oh hey, to answer your question, the BSOD happens randomly, but never after 4.7s. It usually happens after half a day, or a day of use, and I've been trying to test to see when it happens, but can never pinpoint it.

The bios is updated quite recently, and my CPU is never overclocked, and I have turned on temp monitor as well, and the temp is very normal.

I can reset the BIOS (I've done that before as well). As mentioned, I've swapped out everything but the CPU/motherboard.

The fan seems relatively clean, not a lot of dust. I'll report back. Also, could this be due to a faulty CPU?

johnbl · Sep 10, 2017

the system timer is not going to be wrong. Your system rebooted and was up only 4.7 seconds before the cpu detected a internal error and called a bugcheck 0x124 to shutdown.

The bugcheck is only a secondary symptom of your problem. You have to find out why the system rebooted.

google " Intel® Processor Diagnostic Tool " and see if it shows any problem
generally, for a problem like this it will be the motherboard protection circuits that rebooted the machine.
these circuits just send a signal to the cpu reset pin and the cpu just starts to boot again even if the power is not stable. if the power is not stable, the cpu memory controller gets errors and tells windows to shutdown with a bugcheck 0x124

you might check temps before your system bugchecks. you have to check the temp of the CPU and gpu
I mention the GPU because it is the most likely cause of this problem. GPU pull more power if they are overclocked, have large amounts of memory or are hot. if the GPU pulls too much power from the motherboard slot. a good motherboard will reset your machine to save the motherboard and gpu from burning up. A bad motherboard will just let the slot and graphics card catch fire. (happened to me, when I tried to make a really cheap build for someone)

-you might also pull the CPU and look for bent or burnt pins and reaply new thermal paste.
- you might make sure your cpu, gpu and power suppy fans are working ok
- you might underclock your GPU to reduce power consumption
- reset or update the BIOS to get the best bios default settings for your cpu and memory.

check the age of your motherboard, the electronics start to fail between 5-7 years of age.

also if your gpu uses a external psu to gpu power check the cable. if the cable is bad or not connected then too much power will be used from the pci/e slot and the motherboard logic will reset the cpu to stop the problem.

I would think it is not likely going to be a faulty CPU. if it were then the CPU would call a bugcheck 0x124 but the system timer would be much longer. Something reset the CPU reset pin before the cpu detected a problem and called your bugcheck.
it is something that the motherboard logic would do if something is wrong with power on the motherboard.

clammy77 · Sep 12, 2017

johnbl :

-you might also pull the CPU and look for bent or burnt pins and reaply new thermal paste.
ANS: Ok, will try this next, though I checked, thermal paste and CPU temperature seem very normal
- you might make sure your cpu, gpu and power suppy fans are working ok
ANS: yeap, checked
- you might underclock your GPU to reduce power consumption
ANS: I upgraded to a stronger PSU, 200W more, same issue
- reset or update the BIOS to get the best bios default settings for your cpu and memory.
ANS: Yeap, done this, and reset all to default. Any other ideas? perhaps motherboard fault? This started happening randomly, so probably also just MB issue...

octavian_hiu · Nov 28, 2017

i have the same issuses and i think is from windows update 10 pro 1709 and his update video driver to last version, and when i play games and watch youtube video hi crash. look at this forum maybe resolve for you: https://forums.geforce.com/default/topic/1029852/bsod-video_scheduler_internal-error/?offset=3 .... i have 382 driver and same thing now try to instal the driver from original cd. if you resolve this pls tell me how , a good day

octavian_hiu · Nov 29, 2017

ty a lot to all, yesterday after the last bsdo i instal a old version of windows 10 pro build 1607 and stop all update and i put nvidia driver from cd card 372.7 and after 15h no bsdo. the windows creator 10 1709 is the problem with the new driver at nvidia, make the ntoskrnl.exe to crash when i play games and have chrome open with more tabs and look at the movie online or youtube video. have a good day and if i was helpfull thanks

octavian_hiu · Nov 30, 2017

wft i think i insane

(( give me again after 2 day when i think i resolve it

==================================================
Dump File : 113017-6218-01.dmp
Crash Time : 30-Nov-17 11:12:07
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : ffffd686`57540028
Parameter 3 : 00000000`be000000
Parameter 4 : 00000000`00800400
Caused By Driver : hal.dll
Caused By Address : hal.dll+3627f
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.14393.1378 (rs1_release.170620-2008)
Processor : x64
Crash Address : ntoskrnl.exe+14f790
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\113017-6218-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 14393
Dump File Size : 750,596
Dump File Time : 30-Nov-17 11:12:56
==================================================

pls help me

Search

BSOD caused by ntoskrnl.exe and hal.dll

clammy77

Prominent

johnbl

Polypheme

clammy77

Prominent

johnbl

Polypheme

clammy77

Prominent

clammy77

Prominent

clammy77

Prominent

clammy77

Prominent

johnbl

Polypheme

clammy77

Prominent

johnbl

Polypheme

clammy77

Prominent

octavian_hiu

Prominent

octavian_hiu

Prominent

octavian_hiu

Prominent

TRENDING THREADS

Latest posts

Moderators online

Share this page