BSOD playing Guild Wars 2 (mostly), error 0x00000124

[xCrusadentx]

BSODs Occuring While Playing A Variety of Games

For months, I have been dealing with BSODs nonstop. I have gotten a variety of error codes,
and simply do not know how to make them stop. I have sent the computer back to the company i got it from (Cyberpower PC) a total of three times, and all three times they did not fix the errors. I am hoping someone on this forums can enlighten me on what is causing my computer to crash, as this is becoming beyond irritating. The crashes only occur while playing any video game, it doesn't matter which it is. The games I have been playing recently include Guild Wars 2 and the newly released Cube World. Games that I haven't played in a while that also caused crashes were Call of Duty games.

Three of the error codes I can remember include:

0x00000124
0x00000101
0x0000001e
0x00000003B

I have updated my video card drivers which did not solve the issue at all. I am not necessarily tech savy when it comes to hardware so this is difficult for me. I put some of my computers info below, as well as placed the files from the SF Diagnostics Tool. ANy help would be greatly appreciated here, as I cannot play gany games without the fear of my computer crashing. Thank You.

GPU: GeForce GTX 660
CPU: Intel(R) Core(TM) i7 CPU 960@ 3.20GHz
Memory: 12GB RAM

 

[VistaKing]

Try updating the Video Card drivers .

The BSOD 124 is a hardware issue .

 

[xCrusadentx]

Try updating the Video Card drivers .

The BSOD 124 is a hardware issue .

My video card drivers are fully up to date. I should have mentioned that I have also gotten 0x00000101 and 0x0000001e as an error as well. Which message actually shows up out of those 3 is random each time it happens.

 

[xCrusadentx]

I updated the main post of the topic to greater reflect and clarify the issue at hand.

 

[VistaKing]

I have asked Northernsoul55 to take a look at the .dmp files he's in the UK so it will be a while . Sorry about that .

 

[xCrusadentx]

I have asked Northernsoul55 to take a look at the .dmp files he's in the UK so it will be a while . Sorry about that .

Thanks for that. Also, I received a brand new Blue Screen error code I haven't seen so far just minutes ago:

0x0000003B

I've included this dump in this post.

 

[x BlueRobot]

Welcome to the forums,

[COLOR=Red]BugCheck 124[/COLOR], {[COLOR=Blue]0[/COLOR], [COLOR=SeaGreen]fffffa800bcef028[/COLOR], be000000, 800400}

Probably caused by : GenuineIntel

0: kd> [COLOR=SeaGreen]!errrec fffffa800bcef028[/COLOR]
===============================================================================
Common Platform Error Record @ fffffa800bcef028
-------------------------------------------------------------------------------
Record Id     : 01ce7b3663fc3ac3
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 7/7/2013 17:26:24 (UTC)
Flags         : 0x00000000

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

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000106a5
Processor ID  : 0x0000000000000000

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

Local APIC Id : 0x0000000000000000
CPU Id        : a5 06 01 00 00 08 10 00 - bd e3 98 00 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  @ fffffa800bcef240

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

Error         : [COLOR=Red]Internal timer (Proc 0 Bank 5)[/COLOR]
  Status      : 0xbe00000000800400
  Address     : 0x00000000006f6dd8
  Misc.       : 0x0000000000000000

The Internal Timer error seems to be consistent with all the Stop 0x124 BSODs.

In such a situation, it is best to use these steps:

• http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html

Enable "Round off checking" before the test (see first post below tutorial).

• 
  http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

All the hardware seeming to be running stable and tests reporting no errors, could mean a bad motherboard.

 

[xCrusadentx]

Thank You, I'll leave the test going for a bit and report back my findings.

 

[x BlueRobot]

Thanks, will look forward to your results

 

[xCrusadentx]

6hrs, 21 minutes, total of 389 tests, no errors from Prime95:

 

[x BlueRobot]

Okay, have you tried running the Large FFT's and the Blend Test with Prime95?

 

[xCrusadentx]

Okay, have you tried running the Large FFT's and the Blend Test with Prime95?

No, I have not; I did Small FFT's cause thats what tutorial had. I shall run both of those tests and come back with what I find.

 

[x BlueRobot]

Thanks, the Small FFT's tested the caches primarily, the Blend test tests everything (including RAM) and the Large FFT's tests the memory controller.

 

[xCrusadentx]

Tested both, no errors at all.

 

[x BlueRobot]

Okay, I'll next logical step would be to test the RAM -

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run Memtest86+ for least 9-10 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

 

[xCrusadentx]

Thank you. This test may take me a little bit longer to upload the results, depending on if it detects anything wrong. I'll post ASAP.

 

[x BlueRobot]

Okay, don't worry, take your time