BSOD STOP 0x00000124 caused by ntoskrnl.exe

[MattTG12]

Hello, I have been having a BSOD problem for a while now and i have figured out it is caused by ntoskrnl.exe. This BSOD has been going on since April when I built my PC. I have already completely replaced my RAM, done a full virus scan, and checked to make sure there are no overclocks on any hardware. It usually happens when gaming, but sometimes it will happen randomly (like when web browsing and other applications). Please help.

Thanks!

 

[MattTG12]

Has another BSOD, same error code, this time while on reddit.

 

[axe0]

Hi MattTG12,

Please remove Advanced SystemCare 8 and MSI Afterburner, these software are known for causing BSOD's.

   Warning

Programs that claim to update your drivers install either the wrong or corrupted drivers.
If you have installed any driver with Driver Booster 2, please remove them as it may cause trouble.

There is everytime a generic data write error in the level 0 cache, meaning something tries to write corrupted data to the CPU.
Please follow instructions below for troubleshooting the hardware as the 0x124 is usually caused by hardware, although it could also being caused by driver problems, the BIOS, overclocking and in rare cases software.
Please check for BIOS updates, yours is dating from 2013 and there are newer versions available.

STOP 0x124 Troubleshooting

Read carefully before proceeding.

   Warning

If you're overclocking your system, revert back to stock clocks now.

   Note

Test the system once the overclock is removed before continuing with the steps outlined below.

Part One: CPU Stress Test
Part Two: MemTest86+ RAM Diagnostic
Part Three: Hard Drive Diagnostics
Part Four: GPU Stress Test

ONE

 CPU TEST

Run Prime95 to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 7 Help Forums

   Warning

Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.

TWO

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Help Forums

   Note

MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

THREE

 HDD TEST

Run SeaTools to check the integrity of your HDD. SeaTools - HDD test - Windows 7 Help Forums

   Note

Do not run SeaTools on an SSD as the results will be invalid.

Run chkdsk Chkdsk - HDD Test - Windows 7 Help Forums

FOUR

 GPU TEST

Run Furmark to stress test your GPU. FurMark - GPU Stress Test - Windows 7 Help Forums

   Note

Run Furmark for around 30 minutes.

   Warning

Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if overheating occurs.

0: kd> !errrec fffffa800fee85f8\
===============================================================================
Common Platform Error Record @ fffffa800fee85f8
-------------------------------------------------------------------------------
Record Id     : 01d109b72479f2e3
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 10/18/2015 15:10:37 (UTC)
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa800fee8678
Section       @ fffffa800fee8750
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
[COLOR="red"]Error Type    : Cache error
Operation     : Generic[/COLOR]
Flags         : 0x00
Level         : 0
CPU Version   : 0x00000000000306c3
Processor ID  : 0x0000000000000002

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa800fee86c0
Section       @ fffffa800fee8810
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000002
CPU Id        : c3 06 03 00 00 08 10 02 - bf fb da 7f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa800fee8810

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa800fee8708
Section       @ fffffa800fee8890
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

[COLOR="Red"]Error         : DCACHEL0_WR_ERR (Proc 1 Bank 1)[/COLOR]
  Status      : 0xbf80000000000124
  Address     : 0x0000000417866d00
  Misc.       : 0x0000000000000086

 

[MattTG12]

Thanks for responding axe0, I did what you asked

Uninstalled MSI Afterburner and Advanced SystemCare 8, had a BSOD installing Seatools.

After that I ran Furmark for 20 minutes, no BSOD.

Ran Prime95, no BSOD

Ran Seatools, no errors and no BSOD

Decided to play Cities: Skylines, BSOD while loading.

I'm going to run Memtest overnight, but there should be no errors since I completely replaced my RAM back in July.

Minidumps below

 

[axe0]

The newest dumps are having the same problem, but the cause is unknown with this kind of crashes.

 

[MattTG12]

I did check it in BlueScreenView and it says the cause is ntoskrnl.exe.

Is there a way to fix this?

 

[axe0]

The Windows file is blamed because it is the last active, the main problem with such programs.
If there is no other file to blame, the ntoskrnl.exe file is the one blamed, but I have never seen this one as the real cause for 2 main reasons:

• You would have much more problems
• With bad luck you wouldn't be able to boot as this file is used in the boot process

 

[MattTG12]

So, what steps should I take or should I just do a repair install?

 

[axe0]

Please try following my instructions.

That file is NOT actually the cause, it is blamed because it is the last file active at that moment.
There are so many BSOD's where that file is blamed but drivers from other software are the actual cause.

 

[MattTG12]

Sorry for the delay, been really busy.

Ran Memtest for 13 passes and had no errors

Had a BSOD playing Shadow of Mordor

Files Below

 

[axe0]

Have you installed drivers with Driver Booster 2?
What tests have you performed with SeaTools?
What tests have you performed with Prime95?
Is the BIOS optimized for optimal default settings? Sometimes after optimizing you need to tweak a little for stability.

Please visit Windows Update and install every update available, it may take a couple of times to get them all.