Another BSoD 124 minidump - Windows 7 x64

[giztschmo]

Hello, this is my first post, regrettably it comes with attachments, yes, that's right, a pun :hysterical:, the perfmon and the collected info are attached.

The system seems to BSoD when any GPU related stress is imposed on the system, not all the time, three times this month, nothing unusual about those three times, have tried driver clean reinstall and different gpus :banghead:.

Thanks for taking your time to look into this, greatly appreciated .

 

[Jared]

Hello, welcome to Sysnative.

[B]WHEA_UNCORRECTABLE_ERROR (124)[/B]
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, [COLOR="#FF0000"]Machine Check Exception[/COLOR]
Arg2: [COLOR="#008000"]fffffa8021416028[/COLOR], Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000000[COLOR="#800080"]20005[/COLOR], Low order 32-bits of the MCi_STATUS value.

This bugcheck indicates a severe hardware error was detected and the systenm was shut down to prevent any corruption.
Lets dive a little deeper into the cause.

7: kd> [COLOR="#008000"]!errrec fffffa8021416028[/COLOR]
===============================================================================
Common Platform Error Record @ fffffa8021416028
-------------------------------------------------------------------------------
Record Id     : 01cfea1574054933
Severity      : Fatal (1)
Length        : 864
Creator       : Microsoft
Notify Type   : [COLOR="#0000FF"]Machine Check Exception[/COLOR]
Timestamp     : 10/17/2014 16:00:58 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa80214160a8
Section       @ fffffa8021416180
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   : 0x00000000000206c0
Processor ID  : 0x0000000000000011

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa80214160f0
Section       @ fffffa8021416240
Offset        : 536
Length        : 64
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000011
CPU Id        : [COLOR="#00FFFF"]c[/COLOR]0 0[COLOR="#0000FF"]6[/COLOR] 0[COLOR="#00FFFF"]2[/COLOR] 00 00 08 20 11 - ff e3 9e 02 ff fb eb bf [COLOR="#800080"]// Intel Family 6 Model 2C, this seems to be unknown.[/COLOR]
                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

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8021416138
Section       @ fffffa8021416280
Offset        : 600
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : [COLOR="#FF0000"]Unknown (Proc 7 Bank 2)[/COLOR]
  Status      : 0xb2000000000[COLOR="#800080"]20005[/COLOR]

So we have an unknown error occur, a machine check exception was initated because the CPU found some sort of hardware failure.

So lets translate the Intel MCi_STATUS error status code from hex into binary, we get the following.

00[COLOR="#008000"]1[/COLOR]0 0000 0000 0000 0[COLOR="#FF0000"]101[/COLOR]

The code is too long to match any of the Intel documented error code, this is why we're recieving an unknown error.
However, the error is conistsent in that it's the same MCi_STATUS code that occurs meaning there's some sort of connection, the processor which reports this error isn't consistent so I don't think we're dealing with a failing CPU here.

You mention that it crashes when performing graphical intensive tasks, therefore a failing GPU is probable.
Although you said you have changed GPUs, it would seem more like a failing motherboard.

Have you tried removing a GPU altogether and using the Intel integrated graphics?

 

[x BlueRobot]

I would like to suggest checking the PCI/PCIe slots on the motherboard, are they clear from dust and other debris? A simple issue like a disrupted connection can cause problems.

 

[Jared]

I missed that bit, thanks for the input, Harry.