BSOD While Playing Games Or Watching movie (3D)

SuperHad · 24 Oct 2012

Hi All,

Many thanks for taking the time to try and help.

My system:

I7 920 CPU
Gigabyte EX58-UD5 MOBO
3 X 2GB G.Skill Trident RAM
ATI 6950 x 2 (Xfire) GPU
1200W Thermaltake PSU

About 5 months ago I started randomly getting BSOD's, initially I thought one of my GPU's was going bad so I removed one to avoid any crossfire complications but still the BSOD'S persisted. My CPU was overclocked to 4ghz so I thought bingo...it could be that and dropped everything back to stock but still the BSOD'S persisted.

So it would seem I am BSOD'ing with or without an overclock and with or without Xfire enabled.

I have since formatted several times to eliminate any software errors but still to no avail as the BSOD'S keep happening while gaming or watching 3D movies (even happened yesterday while browsing the net)

(info snippet, 0x0000009C was the last code I managed to see during the most recent BSOD before it restarted the comp)

Last night I ran memtest all through the night which successfully completed 10 passes with no errors.

I have been running prime95 for the last 6 hours with my overclock enabled and ram running at 1920MHZ 9-9-9-24 and no issues.

It generally only seems to BSOD when playing / watching something 3D intensive.

I have used the SF Diagnostics tool as requested and collected all the information required.

Please for the love of god could someone have a look at this and try and put my out of my misery as I am THIS close to taking my sledge hammer to this damn thing.

Many Thanks :)

Arc · 24 Oct 2012

Welcome aboard.

Code:

....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {0, fffff8800308fc70, 0, 0}

*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : intelppm.sys ( intelppm+39c2 )

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

5: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
    x86 Processors
        If the processor has ONLY MCE feature available (For example Intel
        Pentium), the parameters are:
        1 - Low  32 bits of P5_MC_TYPE MSR
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of P5_MC_ADDR MSR
        4 - Low  32 bits of P5_MC_ADDR MSR
        If the processor also has MCA feature available (For example Intel
        Pentium Pro), the parameters are:
        1 - Bank number
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
        4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
    IA64 Processors
        1 - Bugcheck Type
            1 - MCA_ASSERT
            2 - MCA_GET_STATEINFO
                SAL returned an error for SAL_GET_STATEINFO while processing MCA.
            3 - MCA_CLEAR_STATEINFO
                SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
            4 - MCA_FATAL
                FW reported a fatal MCA.
            5 - MCA_NONFATAL
                SAL reported a recoverable MCA and we don't support currently
                support recovery or SAL generated an MCA and then couldn't
                produce an error record.
            0xB - INIT_ASSERT
            0xC - INIT_GET_STATEINFO
                  SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
            0xD - INIT_CLEAR_STATEINFO
                  SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
            0xE - INIT_FATAL
                  Not used.
        2 - Address of log
        3 - Size of log
        4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
    AMD64 Processors
        1 - Bank number
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
        4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 0000000000000000
Arg2: fffff8800308fc70
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x9C_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

LAST_CONTROL_TRANSFER:  from fffff800034176e0 to fffff800034be5c0

STACK_TEXT:  
fffff880`0308fc38 fffff800`034176e0 : 00000000`0000009c 00000000`00000000 fffff880`0308fc70 00000000`00000000 : nt!KeBugCheckEx
fffff880`0308fc40 fffff800`03416e1f : 00000000`00000008 00000000`00000000 00000000`00000008 00000000`00000000 : hal!HalpMcaReportError+0x164
fffff880`0308fd90 fffff800`0340ae88 : 00000000`00000000 fffff880`03087180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x9f
fffff880`0308fdc0 fffff800`034bce6c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`0308fdf0 fffff800`034bccd3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`0308ff30 fffff880`06d0e9c2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`030afc98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm+0x39c2


STACK_COMMAND:  kb

FOLLOWUP_IP: 
intelppm+39c2
fffff880`06d0e9c2 ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  intelppm+39c2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: intelppm

IMAGE_NAME:  intelppm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc0fd

FAILURE_BUCKET_ID:  X64_0x9C_GenuineIntel_intelppm+39c2

BUCKET_ID:  X64_0x9C_GenuineIntel_intelppm+39c2

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

According to Carrona.org, STOP 0x0000009C: MACHINE_CHECK_EXCEPTION
Usual causes: Hardware error (similar to STOP 0x124)

For Stop 0x124, we try the guide Stop 0x124 - what it means and what to try

You first take these tests:

Uninstall there programs:

Daemon Tools
Catalyst Control Center.

Let us know the situation.