BSOD STOP error 0x00000124

Neil Sanders · 04 Nov 2013

Hey Guys,

I have been getting the BSOD (STOP error 0x00000124) when ever I reboot my PC. I have to reset the PC when the BSOD happens and have Windows repair then I can access windows. This happens in a loop when ever I restart my PC.

I have tested my HDD's and one of them has failed Seatools long fix test alsoI ran a chkdsk/f/r and no errors came up . Thus I disconnected this HDD and still the BSOD happens.

The CPU is not overheating all Cores are at low to mid 40's.

Not sure what to do next please help.

I have attached most recent dump reports using SF_Diagnostic_Tool.

Arc · 04 Nov 2013

A stop ox124 is usually thought to be a hardware related issue. Do some basic hardware tests.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know the wattage of your PSU.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

And, we need to see some more info. Upload your MSINFO32.nfo file.

Click on the start button
Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
Give the time for processing, it will save a .nfo file on your desktop.
Zip it, and upload it following the instruction.

Fill up your system specs.
See your system specs and fill it up here.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800768a028, f2000040, 800}

Probably caused by : GenuineIntel

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