I'm getting BSOD every so often

[jimentoez]

I've been getting a lot BSOD's lately mostly when playing games,while Producing music and while rendering videos. I've had them a few times even while idle but rarely while idle.

I've linked the Diagnostic tool results here: View attachment 283020

I've updated all my drivers to the latest drivers I found.

 

[futurista]

huh this is sounding suspicious.. do you have an amd card? I just posted a thread like this. Maybe a driver 12.104.0.0 problem?

 

[jimentoez]

huh this is sounding suspicious.. do you have an amd card? I just posted a thread like this. Maybe a driver 12.104.0.0 problem?

I've got a screenshot here of my specs http://puu.sh/49KHW.png

 

[jimentoez]

This was my latest blue screen if it helps in anyway

View attachment 283056

 

[YoYo155]

jimentoez, welcome to SF .

All your bugchecks are reporting (0x124) a hardware error.

WHEA_UNCORRECTABLE_ERROR (124)

Arguments:
Arg1: [U][B][COLOR=Blue]0000000000000000[/COLOR][/B][/U], Machine Check Exception
Arg2: [COLOR=SeaGreen][U][B]fffffa80086884f8[/B][/U][/COLOR], Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

• A fatal hardware error has occurred.

Argument 1 is telling us that the CPU has detected an error and has risen the red flag
to initiate a bugcheck in-order to protect the data.
Keep in mind that although the the CPU is the one which detected the fault doesn't
mean he is to blame.


We can use !errrec on the second argument to get more information about the error:

2: kd> !errrec fffffa80086884f8
===============================================================================
Common Platform Error Record @ fffffa80086884f8
-------------------------------------------------------------------------------
Record Id     : 01ce9f30519de544
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 8/22/2013 12:08:40 (UTC)
Flags         : 0x00000002 PreviousError

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

Proc. Type    : x86/x64
Instr. Set    : x64
[U][B][COLOR=Red]Error Type    : Cache error[/COLOR][/B][/U]
Operation     : Data Write
Flags         : 0x00
Level         : 1
CPU Version   : 0x0000000000100fa0
Processor ID  : 0x0000000000000004

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

Local APIC Id : 0x0000000000000004
CPU Id        : a0 0f 10 00 00 08 06 04 - 09 20 80 00 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  @ fffffa8008688710

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8008688608
Section       @ fffffa8008688790
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : [COLOR=Red][U][B]Fatal[/B][/U][/COLOR]

Error         : [COLOR=Red][U][B]DCACHEL1_DWR_ERR (Proc 4 Bank 0)[/B][/U][/COLOR]
  Status      : 0xb600400034000145
  Address     : 0x00000001ceadb600
  Misc.       : 0x0000000000000000

We can see that the error type is Cache error and it is Fatal.
Although this doesn't mean much it gives as a clue as to what might be going on.


​

Steps to try before we move on:

• fill out you System Specifications completely.
• If any component of your PC overclocked revert it back to stock settings.
• Check for dust accumulation inside the case and around the fan intakes.
• Download Speccy and post a Screenshot of the summary window, one at idle and another while putting load on the PC using Prime95 for the CPU side and Furmark for the GPU.

Good places to start:

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

 

[jimentoez]

1. I filled out my specification page on my profile.
2. Nothing is overclocked.
3. I've got all of the dust of my pc that I could with compressed air.
4. Screenshots of Speedfan:
While Idle my temps are: http://puu.sh/4a0ts.png
While in game these are my temps: http://puu.sh/4a0e1.png

 

[YoYo155]

Did you clean the PC before or after those Bugchecks occurred?
Also what is the make and model of your PSU?
Is the BIOS set to its optimized defaults?

 

[jimentoez]

1. I cleaned my PC when the BSOD's started happening which was a couple weeks ago but it seems to of done nothing.
2. PSU is FPS Group Inc. Model No. FPS450-60APN
3. I've not changed my BIOS so I'm guessing it will still be default, unless something has changed it.

 

[YoYo155]

The generic nature of the 0x124 (Arg1=0) stop code means we would have to take
the trail & error approach.

Do you have any spear parts (or another PC) to test with, mainly a PSU?
The usual suspect of this kind of BCCode is the CPU but it's often not the the case which is why we need
to test other components to rule them out as the cause.
How old are your components?

Fill out this form and post back the result.

• Power Supply Calculator

Start by opening up the case and re-seating all types of connection.

• SATA Cables (HDD/SSD/ODD).
• SATA-Power.
• Motherboard 24-pin.
• Motherboard 4/8-pin (CPU).
• Re-seat the RAM.
• Re-seat the GPU.

Make sure that every slot / cable head is free of dust or other obstruction.
Make sure that every connection is seating properly and firmly in-place.

I still insist on uploading a screenshot of the summary screen of Speccy.

• Download Speccy and post a Screenshot of the summary window, one at idle and another while putting load on the PC using Prime95 for the CPU side and Furmark for the GPU.

Did you read the links I've linked above?

 

[jimentoez]

Everything but the RAM is just under 3 years old. the RAM is 2 months old. Also I don't have part parts or a PC only a Laptop.

Calculator Result: http://puu.sh/4axGp.png

Reconnected all the leads

Speccy at Idle: http://puu.sh/4axPX.png

Speccy with CPU load: http://puu.sh/4aybf.png

Speccy with GPU load: http://puu.sh/4axZF.png

 

[YoYo155]

The age is a factor we need to keep in mind.
Before accusing the hardware, your CPU is definitely getting hot!
How long did you run the test for?

Apply a new coat of thermal paste.

​

Your GPU is also "warm" but as far as GPU goes it has a bit more leeway
although keeping an eye on it is necessary.

 

[jimentoez]

I left them both on for half an hour and they didn't seem to want to go above 80'c

 

[jimentoez]

I've found out it was the CPU. I just got blue screened again and it came up with a warning saying my CPU overheated.

 

[YoYo155]

OK we have a possible culprit!
Please apply a new coat of thermal paste (as illustrated in the video above)
and see how it goes, for anymore issues you can
always post back here .