Solved Monitor standby/shutdown during most games

[writhziden]

Problem Devices:

AODDriver4.01	ROOT\LEGACY_AODDRIVER4.01\0000	This device is not present, is not working properly, or does not have all its drivers installed.
Video Controller	PCI\VEN_8086&DEV_0102&SUBSYS_01021849&REV_09\3&11583659&1&10	The drivers for this device are not installed.

The first is software that is known to cause problems on Windows 7. I would recommend removing the software rather than just the driver. The second appears to be your onboard graphics, and disabling it should not cause any problems. Considering your crash code, you may consider installing its drivers and then disabling it, though, just to test whether it helps.

Loading Dump File [D:\Kingston\BSODDmpFiles\amswickard\Windows_NT6_BSOD_jcgriff2\042312-30373-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`03811000 PsLoadedModuleList = 0xfffff800`03a55650
Debug session time: Mon Apr 23 08:40:13.530 2012 (UTC - 6:00)
System Uptime: 0 days 0:11:33.545
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {3c, 16c, 0, 0}

Unable to load image \??\C:\Program Files (x86)\Lavasoft\Ad-Aware\KernExplorer64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for KernExplorer64.sys
*** ERROR: Module load completed but symbols could not be loaded for KernExplorer64.sys
Probably caused by : KernExplorer64.sys ( KernExplorer64+1277 )

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

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

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: 000000000000003c, ObReferenceObjectByHandle is being called with a bad handle.
Arg2: 000000000000016c, Handle value specified by the caller.
Arg3: 0000000000000000, Object type specified by the caller.
Arg4: 0000000000000000

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


BUGCHECK_STR:  0xc4_3c

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80003d163dc to fffff8000388dd40

STACK_TEXT:  
fffff880`0b068718 fffff800`03d163dc : 00000000`000000c4 00000000`0000003c 00000000`0000016c 00000000`00000000 : nt!KeBugCheckEx
fffff880`0b068720 fffff800`03d2b90f : 00000000`0000026c fffffa80`094b9b60 fffff880`0b0687f0 fffff880`0a3ccb32 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0b068760 fffff880`0a3cc277 : 00000000`00000000 fffffa80`0b9c1000 fffffa80`094b9b60 00000000`00000000 : nt!VerifierObReferenceObjectByHandle+0xdf
fffff880`0b0687b0 00000000`00000000 : fffffa80`0b9c1000 fffffa80`094b9b60 00000000`00000000 fffff880`0b068870 : KernExplorer64+0x1277


STACK_COMMAND:  kb

FOLLOWUP_IP: 
KernExplorer64+1277
fffff880`0a3cc277 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  KernExplorer64+1277

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: KernExplorer64

IMAGE_NAME:  KernExplorer64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d4abb8a

FAILURE_BUCKET_ID:  X64_0xc4_3c_VRF_KernExplorer64+1277

BUCKET_ID:  X64_0xc4_3c_VRF_KernExplorer64+1277

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

Verifier Enabled crashes implicate Ad-Aware. Recommend uninstalling using the steps in How to uninstall Ad-Aware Antivirus and replace it with either of these two options:

• Microsoft Security Essentials - Free Antivirus for Windows
  
  
• http://www.sevenforums.com/system-s...-system-security-combination.html#post1732627

 

[amswickard]

uninstalled Ad-Aware and installed drivers for the onboard graphics (then disabled it). Didn't seem to help any. Should I re-enable verifier and try again?

 

[writhziden]

What software is using AODDriver? It is usually part of AMD Overdrive, EasyTune6, or Catalyst Control Center/AMD Vision Engine Control Center

 

[amswickard]

I would assume it to be one of those. I'll see if driver cleaner can scrub it since I can't get to it myself.

edit: actually forget that, I figured it out. Let's see if it worked

 

[amswickard]

looks like that wasn't it either. I deleted it from the device manager as well as removing it from the registry and still got the crash.

 

[writhziden]

What software was AODDriver part of?


Proceed with enabling Verifier again. Hopefully we can sort out the cause with some more info after new crash reports are generated.

 

[amswickard]

The driver just stated ATI Technologies, no specific application though. Bad news of the verifier front, even with it running it refuses to BSOD and instead simply crashes normally with the sudden monitor shutdown followed by the computer, which results in no dumps being made 99% of the time.

 

[writhziden]

The problem is likely a bad graphics card or bad PSU. Can you get ahold of one or the other to test? Possibly borrow from a friend? Disable Verifier before testing, and if you borrow an NVIDIA card, make sure to uninstall all AMD/ATI software through Start Menu -> Control Panel -> Uninstall a program. You may want to do so anyway if you switch to a different card to make sure no driver/software conflicts are present.

 

[amswickard]

Yeah I can get a hold of them, they'd be lower powered compared to the ones I have in now though. Thanks for the help, I'll be back in a few days with the results

 

[amswickard]

It must be the card. I stuck a 5750 in to replace the 6870 and played about a half hour of Skyrim with no crash. I cranked the settings way up after that and it lagged like crazy but no crash a half hour later. Time to go bargain hunting

 

[writhziden]

Keep us updated on how the system runs once you've replaced the card. Best wishes!

 

[amswickard]

Update on the situation. A new Nvidia GTX 560ti seemed to fix the problem. It's a shame that the 6870 was the problem, it was probably bad from the moment I got it and I just never knew because of the lack of problems with Battlefield 3.

 

[writhziden]

That is too bad. I know some graphics cards have a three year limited warranty, so you may look into doing an RMA.

 

[amswickard]

Unfortunately I don't think that will be possible since I opened the card up to clean it. I believe that in itself voids the warranty.

 

[writhziden]

Yes, opening the card does void the warranty. At least you now have a working system.