Blue Screen after random time of gaming

hello there,

I was searching around the web for my BS issues, found this board and the professional support here, so I'll have a try.

I use the Win7 here mostly for gaming. After some time playing Dawn og War II or similar games concerning hardware requirements, I get a Blue Screen and reboot. This happens not when the system is idle and neither if I run games with lower requirements (e.g. Guild Wars).

Today, I had a look in the most recent dumps, but the "Probably caused by" messages were all quite different. So I started searching and well, found this board.

I own a Win7 Professional 64bit on a self assambled machine, so there was no pre install. The installation is from MSDNAA. My system is about a year old, the OS installation only a few months (upgraded from Vista Business 64 after experiencing the same problem there).

Some hardware specs (if you need them):
Asus P5Q (have some problems with the EPU utils, but they worked back in Vista where I had a similar problem)
Core 2 Quad q9550
2x2GB DDR2 RAM (clean, I've run memtest last night)
500GB WD HDD
GeForce GTX 260
Razer Diamondback mouse (I heard Razer driver cause some problems)



Edit: I just found out who jcgriff2 actually is and I'm very sorry for being so paranoid. Here are the requested files.

Hello ! Welcome to SF !

Seems like it might be Razor because few crashing is pointing to mouclass.sys which is a Microsoft driver for mouse. So find that out more easily we can enable the Driver Verifier and let System catch the rouge driver Using Driver Verifier to identify issues with Drivers

Lets run Hardware Diagnostic to make sure everything is fine. Hardware Diagnostic !! « Captain Debugger

Hope this helps,
Captain

Hello,

Seems like ASACPI.sys has caused the crash. Remove Asus Utilities go to C:\Windows\Drivers and find ASACPI.sys and rename to ASACPI.old and reboot the System.

Bugcheck:

Code:

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 00000000000000ec, Handle value being referenced.
Arg3: fffffa80071ea550, Address of the current process.
Arg4: fffff88004038257, Address inside the driver that is performing the incorrect reference.

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


BUGCHECK_STR:  0xc4_f6

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  SixEngine.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800033593dc to fffff80002ecf740

STACK_TEXT:  
fffff880`07669578 fffff800`033593dc : 00000000`000000c4 00000000`000000f6 00000000`000000ec fffffa80`071ea550 : nt!KeBugCheckEx
fffff880`07669580 fffff800`0336eae4 : 00000000`000000ec fffffa80`071ea550 00000000`00000002 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`076695c0 fffff800`0312ab40 : 00000000`0000a5e3 fffff880`076697f0 00000000`00000000 fffffa80`05c7ad00 : nt!VfCheckUserHandle+0x1b4
fffff880`076696a0 fffff800`031a65f5 : 00000000`00000000 fffff880`000f0001 00000000`00000000 fffffa80`00000000 : nt! ?? ::NNGAKEGL::`string'+0x20e2e
fffff880`07669770 fffff800`0336e878 : fffffa80`0700e3a8 fffff800`03371bcc fffffa80`05c7ac10 fffffa80`05c7ac10 : nt!ObReferenceObjectByHandle+0x25
fffff880`076697c0 fffff880`04038257 : fffff980`1ec98cf0 00000000`00000002 fffffa80`05c7ad60 00000000`00000000 : nt!VerifierObReferenceObjectByHandle+0x48
fffff880`07669810 fffff980`1ec98cf0 : 00000000`00000002 fffffa80`05c7ad60 00000000`00000000 fffffa80`05c7ad88 : ASACPI+0x1257
fffff880`07669818 00000000`00000002 : fffffa80`05c7ad60 00000000`00000000 fffffa80`05c7ad88 00000000`00000000 : 0xfffff980`1ec98cf0
fffff880`07669820 fffffa80`05c7ad60 : 00000000`00000000 fffffa80`05c7ad88 00000000`00000000 00000000`00000001 : 0x2
fffff880`07669828 00000000`00000000 : fffffa80`05c7ad88 00000000`00000000 00000000`00000001 00000000`00000000 : 0xfffffa80`05c7ad60


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ASACPI+1257
fffff880`04038257 83462001        add     dword ptr [rsi+20h],1

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  ASACPI+1257

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ASACPI

IMAGE_NAME:  ASACPI.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a0b72fd

FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_ASACPI+1257

BUCKET_ID:  X64_0xc4_f6_VRF_ASACPI+1257

Followup: MachineOwner

Hope this helps,
Captain

Your Welcome Mate !