BSOD When Gaming, STOP: 0x00000124

verzion2 · 18 Jun 2014

* UPDATE :
HERE'S THE DM LOG CREATOR .ZIP IT CREATED (when running the stress test recommended in the replies to this thread ! :
Attachment 322493

* UPDATE :
HERE'S THE DM LOG COLLECTOR .ZIP IT CREATED (when running "South Park: The Stick of Truth") ! :
Attachment 322312

I have a basically BRAND new computer, and every time I game or put the computer under pressure (more notable that it will always BSOD after playing "South Park: The Stick of Truth" for a little)
It's been happening for a while. Here's a screenshot of the BSOD itself (It's one of the attachments)
Attachment 322304

My PC info is on my account.
(https://www.sevenforums.com/members/verzion2.html > System Specs)

Here is the .dmp file that it gave me the last time it BSOD'd (I found it at C:\Windows\minidump\. I put the file in a .zip folder because it wouldn't let me upload a .dmp file, it's one of the attachments)
Attachment 322305

THANK YOU SO MUCH IF YOU COULD HELP ME AND TELL ME WHAT IS THE ISSUE W/ MY PC!!!

Boozad · 18 Jun 2014

We need more information to analyze your logs. Follow Blue Screen of Death (BSOD) Posting Instructions, let the tool run until it has completely finished and then upload the new logs.

verzion2 · 18 Jun 2014

I ran DM LOG COLLECTOR.exe and I recieved this .zip file.
I hope this is enough information now, sorry I'm new. (y)
Attachment 322310

PeregrineX · 18 Jun 2014

Hello, and welcome to SevenForums!

Your Intel processor seems to be causing the issue here:

Code:

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8007870028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000005110a, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`0316da58 fffff800`037f9a3b : 00000000`00000124 00000000`00000000 fffffa80`07870028 00000000`be200000 : nt!KeBugCheckEx
fffff880`0316da60 fffff800`0338e463 : 00000000`00000001 fffffa80`07871d30 00000000`00000000 fffffa80`07871d80 : hal!HalBugCheckSystem+0x1e3
fffff880`0316daa0 fffff800`037f9700 : 00000000`00000728 fffffa80`07871d30 fffff880`0316de30 fffff880`0316de00 : nt!WheaReportHwError+0x263
fffff880`0316db00 fffff800`037f9052 : fffffa80`07871d30 fffff880`0316de30 fffffa80`07871d30 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`0316dc50 fffff800`037f8f0d : 00000000`00000004 00000000`00000001 fffff880`0316deb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`0316dc90 fffff800`037ece88 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`0316dcc0 fffff800`032764ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`0316dcf0 fffff800`03276313 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`0316de30 fffff800`03279e13 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`0a0d8a08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!memset+0x83


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

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

The 0x124 error comes from a hardware complaint, and by the looks of your dump files, it's your CPU that's causing the trouble.

Try to stress test your CPU by following this tutorial, and inform us of the results.

Best of luck,

PeregrineX

verzion2 · 20 Jun 2014

I ran the stress test (I followed all the instructions and got the correct bit version, as well as closed all my running programs before opening it) within less than 2 minutes my computer froze and then I received another blue screen of death (y) !
Here is the file with the information about the new BSOD I received. .-.
Attachment 322492

Layback Bear · 20 Jun 2014

I noticed in your System Specs the power supply is unknown.
Could you look and see what it is and inform us?

verzion2 · 21 Jun 2014

Corsair 500 CX is my power supply. It's pretty new, only like a year or two old. I bought it myself.

Boozad · 21 Jun 2014

Your logs are showing signs of hardware errors. Follow the trouble shooting steps below.

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

Run Prime95 to stress test your CPU. Hardware - Stress Test With Prime95

Warning

Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them.

Run MemTest86+ to analyse your RAM. RAM - Test with Memtest86+

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.

Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use

Run Furmark to stress test your GPU. Video Card - Stress Test with Furmark

Note

Run Furmark for around 30 minutes.

Warning

Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them.

verzion2 · 21 Jun 2014

So I know it isn't my graphics card (If it

was , I have two so I'd just switch them

out)
I know it is most likely my CPU even

though it is seriously BRAND NEW. My old

computer had a bad CPU and would overheat

after moments of boot up, so I got a new

one to find out I cannot game without

BSOD's...
And I ran the stress test for the CPU and

it BSOD'd (I have the dmp files for it

above) after less than two minutes into

the test
So I'm thinking it's the CPU
(I used Prime95 to check it)

Here are the other tests I've ran that you

told me to and here are its results

This is for my HDD
in SeaTools windows i ran the short

generic test on my current HDD and it came out as "Short Generic - Pass" , so I think it's fine

Ram takes several hours to do so i'll post results tomorrow (ill do it over night)
however, I'm not too sure it's my ram.