BSoD error, which is related to ntoskrnl.exe

Hello. I have been experiencing some occasional BSoDs, all of them related to ntoskrnl.exe. Two of them were 0x124, while the latest was a 0x101. I already ran Ccleaner in case it was a registry problem, but I doubt it. I also did a BIOS update a couple of months ago. My specs are:

Windows 7 x64

CPU: AMD FX-6300

GPU: AMD Radeon HD 7750

Motherboard: Asus M5A78L-M LX3

I ran Bluescreenview, so I'll post the reports here. Thanks for  your help.

==================================================
Dump File         : 111614-47096-01.dmp
Crash Time        : 15/11/2014 07:37:06 p.m.
Bug Check String  :
Bug Check Code    : 0x00000101
Parameter 1       : 00000000`00000021
Parameter 2       : 00000000`00000000
Parameter 3       : fffff880`02f65180
Parameter 4       : 00000000`00000002
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18526 (win7sp1_gdr.140706-1506)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\111614-47096-01.dmp
Processors Count  : 6
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 275,608
Dump File Time    : 16/11/2014 09:36:27 a.m.
==================================================

==================================================
Dump File         : 111314-38657-01.dmp
Crash Time        : 13/11/2014 06:35:27 p.m.
Bug Check String  :
Bug Check Code    : 0x00000124
Parameter 1       : 00000000`00000000
Parameter 2       : fffffa80`07fa3038
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4adb5c
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18526 (win7sp1_gdr.140706-1506)
Processor         : x64
Crash Address     : ntoskrnl.exe+4adb5c
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\111314-38657-01.dmp
Processors Count  : 6
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 262,144
Dump File Time    : 13/11/2014 06:35:49 p.m.
==================================================

==================================================
Dump File         : 110514-33540-01.dmp
Crash Time        : 05/11/2014 07:49:30 p.m.
Bug Check String  :
Bug Check Code    : 0x00000124
Parameter 1       : 00000000`00000000
Parameter 2       : fffffa80`07f7e6c8
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4adb5c
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18526 (win7sp1_gdr.140706-1506)
Processor         : x64
Crash Address     : ntoskrnl.exe+4adb5c
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\110514-33540-01.dmp
Processors Count  : 6
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 262,144
Dump File Time    : 05/11/2014 07:49:52 p.m.
==================================================

Answer
Answer

GT

Both were BCC124 both hardware

Stop 0x124 is a hardware error
If you are overclocking try resetting your processor to standard settings and see if that helps.
If you continue to get BSODs here are some more things you may want to consider.
This is usually heat related, defective hardware, memory or even processor though it is"possible" that it is driver related (rare).

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 and clear the CMOS.
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 3rd-party memtest86 utility to run many hours worth of testing. (6-8 passes to stress the ram out)
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.
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 hardware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events.
Be aware that attempting the subsequent hardware 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.

Should you find yourself in the situation of having performed all of the steps above without a resolution of the symptom, unfortunately the most likely reason is because the error message is literally correct - something is fundamentally wrong with the machine's hardware.

More advanced reading can be found here from a MS MVP IT PRO

Cat herder
Windows Insider MVP
MVP-Windows and Devices for IT
http://www.zigzag3143.com/

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Answer
Answer

Hi Gabriel,

Thanks for posting on Microsoft Community.

I am sorry to know that you are getting BSOD very often, which is related to ntoskrnl.exe error. It could occur due to corrupted drivers or software issue.

Once you receive the blue screen error, are you able to get into the system by restarting it?

You can try the below methods and check.

Method 1.

Run the fix-it below. It helps to diagnose and fix problems with hardware.
Hardware devices are not working or are not detected in Windows:
http://support2.microsoft.com/mats/hardware_device_problems

Method 2.

If you are still facing the issue, then boot into safe mode and check again.

Start your computer in safe mode: http://windows.microsoft.com/en-us/windows7/Start-your-computer-in-safe-mode

Method 3.

I also suggest you to update all the drivers.

http://windows.microsoft.com/en-us/windows7/Update-a-driver-for-hardware-that-isnt-working-properly  

You can also download updated drivers from the manufacturer’s website and install on your computer.

Method 4.

Resolving stop (blue screen) errors in Windows 7:
http://windows.microsoft.com/en-US/windows7/Resolving-stop-blue-screen-errors-in-Windows-7

System Restore disclaimer: When you use System Restore to restore the computer to a previous state, programs and updates that you installed are removed.

Hope this helps in resolving the issue. If issue persists do contact us. We will be glad to assist you.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 
 

Question Info

Last updated March 18, 2019 Views 2,420 Applies to: