Blue Screen Help Please

[gcaster]

Hi,

I keep getting a BSOD but only ever when browsing the web. When I'm running more stressful programs I've never had the issue.

Most recent dumps are attached. If anyone could point me in the right direction I'd be very grateful.

Thanks

 

[Maguscreed]

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: fffffa8005327028, 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.

BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`02f6ca58 fffff800`02e26903 : 00000000`00000124 00000000`00000000 fffffa80`0538b028 00000000`be200000 : 0xfffff800`02ecd740
fffff880`02f6ca60 00000000`00000124 : 00000000`00000000 fffffa80`0538b028 00000000`be200000 00000000`0005110a : 0xfffff800`02e26903
fffff880`02f6ca68 00000000`00000000 : fffffa80`0538b028 00000000`be200000 00000000`0005110a fffffa80`05423470 : 0x124


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  CORRUPT_MODULELIST

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

We appear to be looking at either a hardware or driver failure.

0: kd> lm t n
start             end                 module name
00000000`05bd1360 00000000`f335c338   Unknown_Module_00000000_05bd1360 Unknown_Module_00000000`05bd1360 unavailable (00000000)

Unloaded modules:
fffff880`08b9a000 fffff880`08ba6000   GPU-Z.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000C000
fffff880`08b8e000 fffff880`08b9a000   GPU-Z.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000C000
fffff880`08af5000 fffff880`08b66000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00071000
fffff880`0148a000 fffff880`01498000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000E000
fffff880`015ee000 fffff880`015fa000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000C000
fffff880`013e5000 fffff880`013ee000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00009000
fffff880`011dd000 fffff880`011f0000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00013000

The dumps appear to be damaged somehow though, they are not providing the information they should be. The last section of code should contain a full list of drivers loaded at the time the crash occurred but it's blank. I'll point a more experienced member to this post for you.

 

[gcaster]

I have to unplug and then plug my mouse back in every time it happens as it doesn't connect on boot.
Could be the problem?
Mouse is a Mionix Naos 5000.

 

[Maguscreed]

I have forwarded your post to a more experienced user, it's sunday night though it could be awhile, even tomorrow before he sees it. I don't know how to proceed with a damage dump file. More than likely the mouse failing to respond is a symptom and not a cause, though I can't be sure. Be patient.

 

[gcaster]

Thanks.

It seems strange that the dump files are damaged. If it happens again any time soon I'll be sure to post up the new dump.

My processor is overclocked but I've tested under Prime Blend for 16 hours and through 50 passes of IntelBurn Test so I highly doubt this is the problem as the BSODs thus far have only happened while the CPU is at very little load running Chrome. I'm tempted to switch over to Firefox but don't really want to.

Thanks again for your help.

 

[Maguscreed]

It would have helped mentioning that, the first thing you do when experiencing any error while overclocked, is to remove the clock, regardless of how stable you believe it to be. It's just one more item to add to the equation in trying to debug.

 

[DeanP]

Stop overclocking and return to default values.

Also, I would take a look at this Stop 0x124 error: http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html