BSOD during Crysis 3

Your bugcheck is reporting (0x124) which is a hardware error:

Code:

WHEA_UNCORRECTABLE_ERROR (124)

Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800770e028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b0800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000040151, 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 truly the one to blame.

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

Code:

!errrec fffffa800770e028
===============================================================================
Common Platform Error Record @ fffffa800770e028
-------------------------------------------------------------------------------
Record Id     : 01cea1363cb3f688
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 8/25/2013 2:25:31 (UTC)
Flags         : 0x00000000

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

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Instruction Execute
Flags         : 0x00
Level         : 1
CPU Version   : 0x0000000000600f20
Processor ID  : 0x0000000000000004

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

Local APIC Id : 0x0000000000000004
CPU Id        : 20 0f 60 00 00 08 08 04 - 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  @ fffffa800770e240

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

Error         : ICACHEL1_IRD_ERR (Proc 4 Bank 1)
  Status      : 0xb080000000040151

We can see that the error type is Fatal meaning the CPU couldn't
correct it and had to crash the machine.
The crash happened in the L1 CACHE.


Although this doesn't mean much it gives as a clue as to what might be going on.

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.

• 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.

Reset the BIOS back to default as it seems that your CPU is overclocked:

Code:

!sysinfo cpuinfo
[CPU Information]
~MHz = REG_DWORD 4334

• CLR CMOS

   Note

If any component is overclocked reset it back to stock speeds!

Good places to read more:

• Stop 0x124 - what it means and what to try
• Stop 0x124 Troubleshooting - 'New Method'

Jeremiahrt said:

Could a CPU error cause it to do this?

Also, since I have built this pc it has shown a CPU fan error. The fan is a cooler master, and it runs fine. I read that this is a common error for an after market cooler, could this be part of the issue?

Thanks for your time.

Yes, the CPU also has the potential to be at fault in this case although it is rare.

The CPU Fan Error occurs when no fan is plugged into the the header on the motherboard
labeled CPU_Fan, it is especially important if your fan has PWM conrtol (you can determine by counting
the pin it recessives which is 4 for PWM) because it allows for the fan to speed up when necessary.

• Fan control - Wikipedia, the free encyclopedia

Complete the steps suggested above that way we will have better understanding of the situation :) .

Jeremiahrt said:

This is what I have done so far.

I have opened my case and unplugged then replugged everything.

I filled out the Power Supply Calculator form (picture attached). I have a XFX Pro550W.

I also have run the stress test on my GPU and have pictures attached of idle and under stress.

I also reset my BIOS. One thing I do not understand is that it showed my goal CPU speed to be 4000ghz, but the actual running speed was around 4370ghz. Once I reset my BIOS it was running at 4000ghz and the goal speed was 4000ghz. Like I said before, I have never messed with overclocking anything, and I am not sure what could have caused this. Any ideas?

I also fixed my CPU fan error.

As soon as this posts I am going to run the stress test on my CPU. How long do you recommend that I run the CPU stress test?

Thanks again for everything!

Great job, the temperatures are normal as well.

I do have an idea.
You have several overclocking software installed:

Code:

AODDriver4.2    c:\program files\ati technologies\ati.ace\fuel\amd64\aoddriver2.sys
\Programs\ASUS\AI Suite II
\Programs\MSI Afterburner

• AMD OverDrive.

Remove those software utilities.




There is no actual time limit in regards to testing the CPU, the most important thing is,
Keep an eye on the temperature!!!. Don't let it exceed 82°C which is my personal limit
everyone has their own though.

   Tip

While stress testing the CPU open the Event Viewer and refresh (F5) every 5 minutes or so
and shearch for any WHEA-Logger event 18/19 errors that the CPU is correcting on the go.
If you do get those stop the testing session.

To open the Event Viewer and look for WHEA errors:

• Search the Start Menu for Event Viewer and hit Enter
• Expand Windows Logs and select the subcategory System
• Use Ctrl+F to search (searching WHEA as the keyword is enough)
• Refresh periodically using F5
• Attachment 283278

Those temperatures can't be correct.
It seems that the CPU is almost not being taxed at all.

• Download CPU-Z CPUID launch the program and keep it in sight.
• Run Prime95 again but this time just for a couple of minutes in order to check if the CPU is hitting its Boost Clock.
• Attachment 283309
• If it doesn't boost up then follow these tutorial in order, and select the Balanced power plan.
  
  1. Power Plan - Restore Default Settings
  2. Power Plan Settings - Change
  
  

Upload a picture of CPU-Z while stress testing the CPU.
If it still doesn't boost up after all of the above we need look at BIOS.

Yes it is, but the temperature I find hard to believe.
What is your cooling solution?
What is the ambient room temperature?

Download HWmonitor what does this software read?

BTW, since post #5 did you try Crysis again?
Did you bugcheck?