Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD 0x00000124 caused by hal.dll & ntoskrnl.exe

07 Jun 2014   #1
Bluescreenhelp

7, 64bit
 
 
BSOD 0x00000124 caused by hal.dll & ntoskrnl.exe

I've cleaned my computer with an air compressor within the last week and I have no overclocking. CPU temps are on idle at around 30C and I've never seen GPU temps above 60C when I run World of Warcraft.

But I still get BSOD 0x00000124 sometimes...

Thanks for any help.


My System SpecsSystem Spec
.
08 Jun 2014   #2
Bluescreenhelp

7, 64bit
 
 

Any advice?
My System SpecsSystem Spec
09 Jun 2014   #3
Bluescreenhelp

7, 64bit
 
 

bump..
My System SpecsSystem Spec
.

10 Jun 2014   #4
Bluescreenhelp

7, 64bit
 
 

Bump..
My System SpecsSystem Spec
11 Jun 2014   #5
Bluescreenhelp

7, 64bit
 
 

bump
My System SpecsSystem Spec
13 Jun 2014   #6
Bluescreenhelp

7, 64bit
 
 

bump
My System SpecsSystem Spec
13 Jun 2014   #7
Tews

64-bit Windows 8.1 Pro
 
 
Stop 0x124 - what it means and what to try

Synopsis:

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.


Generic "Stop 0x124" Troubleshooting Strategy:
1) Ensure that none of the hardware components are overclocked. Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable ways.

2) Ensure that the machine is adequately cooled. If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues.

3) Update all hardware-related drivers: video, sound, RAID (if any), NIC... anything that interacts with a piece of hardware. It is good practice to run the latest drivers anyway.

4) Update the motherboard BIOS according to the manufacturer's instructions. Their website should provide detailed instructions as to the brand and model-specific procedure.

5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought otherwise (because of the bug). At the time of writing, Windows 7 is not known to suffer from any such defects, but it is nevertheless important to always keep Windows itself updated.

6) Attempt to (stress) test those hardware components which can be put through their paces artificially. The most obvious examples are the RAM and HDD(s). For the RAM, use the in-built memory diagnostics (run MDSCHED) or the 3rd-party memtest86 utility to run many hours worth of testing. For hard drives, check whether CHKDSK /R finds any problems on the drive(s), notably "bad sectors". Unreliable RAM, in particular, is deadly as far as software is concerned, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result from the diagnostics utilities does not guarantee that the RAM is free from defects - only that none were encountered during the test passes.

7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: just the OS itself without any additional applications, games, utilities, updates, or new drivers - NOTHING AT ALL that is not sourced from the Windows 7 disc. Should that fail to mitigate the 0x124 problem, jump to the next steps. Otherwise, if you run the "vanilla" installation long enough to convince yourself that not a single 0x124 crash has occurred, start installing updates and applications slowly, always pausing between successive additions long enough to get a feel for whether the machine is still free from 0x124 crashes. Should the crashing resume, obviously the very last software addition(s) may be somehow linked to the root cause.
If stop 0x124 errors persist despite the steps above, and the harware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events. Be aware that attempting the subsequent harware troubleshooting steps may, in some cases, void your warranty:
8) Clean and carefully remove any dust from the inside of the machine. Reseat all connectors and memory modules. Use a can of compressed air to clean out the RAM DIMM sockets as much as possible.

9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed. Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.
My System SpecsSystem Spec
Reply

 BSOD 0x00000124 caused by hal.dll & ntoskrnl.exe




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
0x00000124 ntoskrnl.exe ntoskrnl.exe+4a63cc BSOD Error runninganygame
i keep getting BSOD when playing game new graphics i dont know where to start when its comes to BSOD stuff 110414-10576-01.dmp 11/4/2014 10:48:39 PM 0x00000124 00000000`00000000 fffffa80`0af318f8 00000000`00000000 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+4a63cc ...
BSOD Help and Support
BSOD random, error 0x00000124, caused by address ntoskrnl.exe+4adb3c
Hi, This problem started in Flight Simulator, but now its random. I have run memtest twice for four hours each, all is fine. I have a Western Digital HD, and ran their diagnostic tool for it from their site. I have reset the RAM after cleaning it also. I dust out the machine regularly. I...
BSOD Help and Support
BSOD bugcheck code 0x00000124 Caused By Driver ntoskrnl.exe
My computer crashed every time I run experiment(NI equipment connects to the computer). My experiment needs to run two or three days, but every twelve hours it got crash(shut down automatically). The max work hour I got is 15 hours. When I reboot the computer, I got the following information: ...
BSOD Help and Support
BSOD - 0x00000124 - caused by ntoskrnl.exe dump attached
Hi guys, Having BSOD issues. I thought initially it was scaned from hardware issue maybe loose connectors but my build is less than 30 days old and i've reseated all parts about 4 days ago. It didnt BSOD for 4 days but today it BSOD while browsing the internet, the next BSOD was when trying to...
BSOD Help and Support
Random BSODs, error 0x00000124, caused by ntoskrnl.exe
Randomly happens, sometimes in a game, sometimes when browsing, sometimes when RDP'ed in, sometimes when unattended. No repro steps yet, just be patient and it will happen. Sometimes when it blue screens, it takes the whole network down spamming the switches and router with packets.
BSOD Help and Support
BSOD Event ID 1001 Bug Check 0x00000124 caused by ntoskrnl.exe driver
Hello, When I first started to encounter BSOD issues I was originally getting event id 18, Machine check exception, Translation Lookaside Buffer errors which I assumed was an issue with my CPU. I contacted Intel and they stated to me that Windows 7 was not correctly dumping the right information...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 11:26.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App