BSOD playing Dark Souls, error 0x00000124

Solus · 31 Oct 2015

Greetings, forum people.

Hopefully, someone can help me with this issue and hopefully I'm doing this right.
I've been experiencing Blue Screens ever since I've started playing Dark Souls. They only happen with this game and only when certain particle effects appear (although somewhat randomly; one effect may cause the BSoD once and then not again the next time it happens).
I can sometimes play the game for 3-4 hours with not even a lag, other times I play for five minutes and it explodes on me.

What happens exactly is that the game freezes for a split-second, then the last bit of sound played starts looping (kind of a stuttering noise) and I get vertical stripes on my screen. Following that, Windows reboots.

Before I take any drastic measures (like exchanging hardware), maybe someone can pinpoint the actual problem for me.
I'm quite computer illiterate so I might be missing something obvious, but I can follow basic instructions.
_____

Hardware:
AMD Radeon HD 7770 1GB
AMD FX-6300 @3.5 GHz
2x 4GB DDR3 RAM
500GB WD5000AAKS-60WWPA0 HDD
400 Watt be quiet! Power Non-Modular 80+ Bronze
_____

What I've tried:
SeaTools, HD Tune, chdsk
memtest86+ over night twice
Prime95 + FurMark simultaneously for 1 hour
OCCT, all tests for 20min - 1 hour
sfc /scannow
> none of these showed any errors

updated/re-installed GPU + audio drivers
scanned with MalwareBytes AntiMalware + avast
verified game files, un-installed and re-installed game
played around with all the in-game settings (of which there aren't many in DS anyway) + various resolutions

with and without CCC/RadeonPro
with only Steam (necessarily) running alongside the game

no overheating according to HWMonitor
no overclocking
no massive dust collection inside case
_____

Excuse the long-ish post. Just trying to give as much information as possible. + DM Log Collector File.
Side note: I've set Windows to not automatically restart when BSoD occurs, yet it always does. Why is that?

**axe0** · 01 Nov 2015

Hi Solus,

Welcome to the 7forums.

The 0x124(WHEA_UNCORRECTABLE_ERROR) is usually related to hardware problems, however it could also being caused by overclocked hardware, driver related problems, BIOS problems like a misconfiguration and in some rare cases software.
Unfortunately with 0x124's, there is usually not enough information that could actually reveal what is causing the crashes. As this crash is related to hardware, below is a troubleshooting guide for hardware. Please read the instructions carefully, if you have any questions please ask them.

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.

The problem:
There is too much delay between data in a bus.
This means that a component is not responding to a request of the CPU, so the CPU can't execute the data as it is incomplete.

Code:

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

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

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : BUS error
Operation     : Generic
Flags         : 0x00
Level         : 3
CPU Version   : 0x0000000000600f20
Processor ID  : 0x0000000000000000

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

Local APIC Id : 0x0000000000000000
CPU Id        : 20 0f 60 00 00 08 06 00 - 0b 32 98 3e ff fb 8b 17
                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  @ fffffa8007e1fa50

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

Error         : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)
  Status      : 0xfe00000000070f0f
  Address     : 0x00000000febf8024
  Misc.       : 0xc00a0fff01000000

Solus · 01 Nov 2015

Thanks for the welcome and the reply.

axe0 said:

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

Hm, yes.

Solus said:

What I've tried:
SeaTools, HD Tune, chdsk
memtest86+ over night twice
Prime95 + FurMark simultaneously for 1 hour
OCCT, all tests for 20min - 1 hour
sfc /scannow
> none of these showed any errors

Edit; When running Prime95, CPU temps don't go much higher than 50°C (according to HWMonitor) and with FurMark, the highest GPU temp was ~72°C.
_____

axe0 said:

The problem:
There is too much delay between data in a bus.
This means that a component is not responding to a request of the CPU, so the CPU can't execute the data as it is incomplete.

That sounds like the kind of pinpointing I was hoping for. So here comes my silly follow-up question: Does that indicate a software or hardware problem?

Solus · 02 Nov 2015

Well, I'm out of things to try due to my lack of knowledge and also inappropriately desperate after one or two weeks of googling. Is this an obscure problem? I seem to be susceptible to those. Or am I just being impatient?

In the meantime, I've looked around in the BIOS but everything appears to be in order (like I would know).
At this point I can only assume the game (and only this one) is still doing that, I'm actually kind of wary of even touching it anymore. (But would still like to know what's going on.)

Uh, here's a CPU-Z validator shot which may or may not be of further use.

**axe0** · 02 Nov 2015

Solus said:

axe0 said:

The problem:
There is too much delay between data in a bus.
This means that a component is not responding to a request of the CPU, so the CPU can't execute the data as it is incomplete.

That sounds like the kind of pinpointing I was hoping for. So here comes my silly follow-up question: Does that indicate a software or hardware problem?

As you have tested most of the hardware components, it usually indicates a driver issue.
Usually, because it could also mean the motherboard is failing/faulty, or a problem with a cable.

What I would like to try is driver verifier to test the drivers, it might cause a different bugcheck what I am hoping for.

Diagnostic Test

DRIVER VERIFIER

Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

Solus · 02 Nov 2015

Ah, impatience. Sorry about that.

axe0 said:

As you have tested most of the hardware components, it usually indicates a driver issue.
Usually, because it could also mean the motherboard is failing/faulty, or a problem with a cable.

What I would like to try is driver verifier to test the drivers, it might cause a different bugcheck what I am hoping for.

Hopefully not the MoBo, that would seem like a pain in the rear.
Will do driver verifier as soon as I have made my obligatory twelve backups of everything and noted down what to do in case things go sideways; will report back with results. Thanks for the help so far, sir.

**axe0** · 02 Nov 2015

It could be really difficult to narrow down the problem with a 0x124 as there are so many things that could cause this.

Hardware,
hardware settings like settings for the GPU and CPU,
BIOS version,
BIOS setting,
firmware of SSD,
driver problem,
software like Gigabyte can cause this crash,
dust,
overheating which would cause hardware damage
etc.

So it is kinda difficult to get to the mobo sometimes as there are so many things you can try.

Solus · 02 Nov 2015

axe0 said:

It could be really difficult to narrow down the problem with a 0x124 as there are so many things that could cause this.

It would be. Apparently I can't just have a simple problem.

For all the diagnostic utilities, from what I gather, there's no actual way to check a motherboard for faults, is there?

**axe0** · 02 Nov 2015

Before we can check for certain the mobo is the cause we would have to check everything else.
But that will be time consuming if properly done, lets for now focus on the drivers.

Solus · 04 Nov 2015

So ... I've had Driver Verifier on for about 24 hours now and nothing happened (except for the horrendous slowdown mentioned in the guide). Suppose this would be a rare circumstance under which a BSoD would actually be a good sign as it would help identifying what's wrong.

Should I leave it for another 24 hours?

Plus, out of curiosity, is there any chance of a faulty GPU even after surviving FurMark and OCCT's GPU test? ... Wishful thinking. Seems like a GPU would be easier to replace than a MoBo, if that does turn out to be the problem here. On that note, how likely is it that a crash/BSoD resulting from one specific effect in a game points to a faulty board? (I did mention I was quite clueless.)