BSOD playing GTA IV

[popsuk]

Random BSOD

Hi
just started to get random bsod, last time this happen PC went back testing and power supply was blamed for the bsod.

Windows 7 Ultimate x64
Intel Core i5-2500K 3.30GHz
ASUS P8P67-M PRO Intel P67
8GB Corsair Memory XMS3 DDR3 1600 MHz
MSI GeForce GTX 580
1920 x 1080
500gb sata
730W be quiet!
Corsair 600T
Arctic Cooling Freezer 13 Pro
Razer Arctosa
Logitech MX518 Optical Gaming Mouse

 

[Wishmaster]

Sounds like something is unstable or faulty.

How long did you let Prime run?
Have you ran Memtest86? If so, how many passes?

 

[Maguscreed]

I think driver verifier is actually causing the bsod's you are getting. (it's tagged in every one of the minidumps)
You could try just disabling it.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[popsuk]

Sounds like something is unstable or faulty.

How long did you let Prime run?
Have you ran Memtest86? If so, how many passes?

prime95 ran for about 1 min if that before BSOD while overclocked, memtest86 ran that for 1 hour not sure how many passes, but no errors

 

[popsuk]

I think driver verifier is actually causing the bsod's you are getting. (it's tagged in every one of the minidumps)
You could try just disabling it.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

i ran driver-verifier and just BSOD left it trying to boot up 4 or 5 times before disable it in safe mode

 

[Maguscreed]

ah okay let me dig back into the dumps a little further then.
It kind of gets in the way when it just keeps crashing on hidclass.sys
...though it could be pointing to a mouse or keyboard driver problem if you are using a fancy mouse or keyboard.

 

[Maguscreed]

Sorry I was wrong, you got the worst debugger message you can get. You have a overclocked device that needs the clock removed. Or you have failing hardware, it's pretty much the only two possibilities with this error type.
http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  prime95.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff800`0440aa98 fffff800`035ef903 : 00000000`00000124 00000000`00000000 fffffa80`07cac028 00000000`be200000 : nt!KeBugCheckEx
fffff800`0440aaa0 fffff800`03187293 : 00000000`00000001 fffffa80`07d14300 00000000`00000000 fffffa80`07d14350 : hal!HalBugCheckSystem+0x1e3
fffff800`0440aae0 fffff800`035ef5c8 : 00000000`00000728 fffffa80`07d14300 fffff800`0440ae70 fffff800`0440ae00 : nt!WheaReportHwError+0x263
fffff800`0440ab40 fffff800`035eef1a : fffffa80`07d14300 fffff800`0440ae70 fffffa80`07d14300 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`0440ac90 fffff800`035eedd5 : 00000000`00000004 00000000`00000001 fffff800`0440aef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`0440acd0 fffff800`035e2e88 : 00000000`01dfe000 00000000`3cd8f4c0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`0440ad00 fffff800`0306fe6c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`0440ad30 fffff800`0306fcd3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`0440ae70 00000001`4099d346 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`03afe010 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1`4099d346


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

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

 

[popsuk]

ah okay let me dig back into the dumps a little further then.
It kind of gets in the way when it just keeps crashing on hidclass.sys
...though it could be pointing to a mouse or keyboard driver problem if you are using a fancy mouse or keyboard.

its same keyboard & mouse ive used now for the pass 2 years, never installed driver for them just PnP, i noticed in the perfmon reports there is a issue with virus program, could that be coursing the driver verifier to BSOD?

but that really doesn't explain the BSOD when i over clock PC and run Prime95, cause it as BSOD within 30 seconds of start Prime95.

 

[Maguscreed]

the the post just above your last one.

 

[popsuk]

Thanks Maguscreed i really appreciate your time & input, will be returning PC first thing Monday morning and let them stress over it.
thx

 

[Maguscreed]

You can copy paste that code segment and print it if you like.
Anyone that knows anything about the subject should be able to tell what that means.