BSOD while 3D gaming, Stop 0x00000124

eisenkrote · 15 Oct 2014

Hello all.

I've got a computer I bought a few years back from CyberPowerPC. Its been a pretty good performer, but started acting up this year. For most light tasks I don't have any issues, but when I'm 3D gaming it tends to crash and BSOD with error code 0x00000124. My undertstanding is that this is a hardware error. I've run a memory check, using memtest86+ and it ran without issue. I haven't done any diagnosing beyond that, though.

I've attached a zip of my DM log collector run. Any help would be really appreciated. If theres any more info I can provide, please ask.

eisenkrote · 17 Oct 2014

I'm not sure if it helps, but here's a snapshot of the BSOD screen.

eisenkrote · 18 Oct 2014

Update:

I was browsing other threads, and found a suggestion to run "SFC /scannow" to look for driver errors. I ran that, and it came through clean. I've run 3rd party driver update software in the past, so it seemed like a possible candidate. Those programs are uninstalled, and the drivers seem to be up to date.

Arc · 18 Oct 2014

Code:

BugCheck 124, {0, fffffa8004e59028, b6004000, dc000135}

Probably caused by : AuthenticAMD

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

It is usually said that a stop ox124 is a hardware error, but actually it may be anything and everything.

Best you follow this guide: Stop 0x124 - what it means and what to try

For any questions about the process, feel free to ask us. Also let us know about your advancements.

eisenkrote · 01 Nov 2014

Progress! (of a sort...)

I clean installed Windows 7, and installed nothing else, except Steam. I ran Civilization (Beyond Earth) and got a BSOD again. This time the stop error is 0x0000000A. So I ran the DM collector logs program and will include them with the post.

Hopefully a different BSOD error will make it easier to "triangulate" the source of the problem?

Arc · 01 Nov 2014

Yes, progress!

Code:

BugCheck A, {fffff98024723fd0, 0, 1, fffff80002a9abe0}

Probably caused by : memory_corruption ( nt!MmUnmapViewInSystemCache+2b1 )

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

Though a memory corruption does not necessarily mean that the RAM is doing bad, but it is the best to have a test. Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+

Run memtest86+ for at least 8 consecutive passes.

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

Let us know the result. Our next step will depend on it.

eisenkrote · 02 Nov 2014

After some difficulty getting the USB stick to boot up, I ran memtest last night for a total of 8 passes. No errors occurred during the test. I also checked my BIOS settings just to be sure, and I don't have any overclocking enabled.

Arc · 02 Nov 2014

Ok, then let us try the alternative ppossibility of memory corruption, a driver passing bad information to the memory.

Enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

eisenkrote · 02 Nov 2014

Arc:

I got verifier up and running, and loaded up the game that seems to like to make it crash. While loading a savegame, I got another BSOD. After rebooting, I got a second BSOD after entering my password to login to Windows. Attached is the DM Collector logs from that.

Arc · 03 Nov 2014

We are searching the cause of the issue in the wrong place. It is not a driver relate issue at all.

Code:

BugCheck 101, {21, 0, fffff880009b2180, 4}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

Code:

BugCheck 7F, {8, 80050031, 6f8, fffff80002ad0b90}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

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

Code:

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

I will point you to an old forum post by an old member H2SO4 :

H2SO4 said:

What you're looking for will be in one of the following categories:

a) BIOS bug
b) a driver whose activity is causing the target processor to lock up
c) a hardware defect (temperature, voltage, dust, RFI, outright borkedness...)

If you changed any hardware component, dont apply it.

Stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark

Take a screenshot of the furmark window before closing it. Upload the screenshot for us.

Stress test the CPU.

Hardware - Stress Test With Prime95

It saves the result as a .txt file in the prime95's folder. Upload the file for us.

If you are overclocking, stop. Run the computer with stock hardware settings.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator - The most trusted PSU Wattage Calculator
Also let us know the wattage of the 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. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

But, I am afraid about one thing .... the motherboard, M5A97 (Rev 1.xx) is discontinued by ASUS, most probably. So no BIOS update will be available. If a BIOS bug is the cause of the BSOD, that will not be rectified.