Random BSOD on Windows 7

tozzleozzle said:

ePeen said:

2.

Alternatively, you can check the status of it via elevated command prompt (running cmd as admin). Type

verifier /query

When i did this option it flashed up with loads of code and then went back to normal, does that mean its working?

Is the info that was dumped in command prompt still there or does it disappear after it shows? If it's still there, you can copy & paste it here.

Regardless, it's probably enabled.. I wouldn't worry! But of course, you're welcome to check.

Nah, it disappears right after it shows. I went through the steps correcly so im hoping its on

Am i able to turn my PC off for the night or should i leave it on for the 24 hours?

tozzleozzle said:

Nah, it disappears right after it shows. I went through the steps correcly so im hoping its on

Am i able to turn my PC off for the night or should i leave it on for the 24 hours?

Use it as you would regularly, but don't shut it off. Generally you'd like to keep Driver Verifier enabled for at least ~48 hours.

Cool. My Brother is downloading his games, playing games, on Facebook and organising his music. I will keep you informed :)

Sounds great.

Does the verifier slow down the PC's proformence? we have noticed it takes a bit longer for programs to open, such as photoshop and it doesn't run games as well....

Gah! I so thought it wouldent do it but heck, i have attached the DMP file:)

It happened when i was fiddling about with fan speeds on the Asus AI Suite II 1.01.34 and then clicked Update.


Aswell here is the code that came up when i restarted the PC:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057

Additional information about the problem:
BCCode: c4
BCP1: 00000000000000F6
BCP2: 0000000000000118
BCP3: FFFFFA8005402B30
BCP4: FFFFF88003FE8766
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\022812-63773-01.dmp
C:\Users\Sam's PC\AppData\Local\Temp\WER-81713-0.sysdata.xml

Hi,

The verified dump you've attached shows AsUpIO.sys as the culprit, this is ASUS hardware monitoring software related. Please update that driver here or uninstall the program using this driver.

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Icarus\Downloads\Dumps\022812-63773-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`05808000 PsLoadedModuleList = 0xfffff800`05a4d670
Debug session time: Tue Feb 28 10:00:49.489 2012 (UTC - 5:00)
System Uptime: 0 days 15:52:45.362
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {f6, 118, fffffa8005402b30, fffff88003fe8766}

Unable to load image \SystemRoot\SysWow64\drivers\AsUpIO.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for AsUpIO.sys
*** ERROR: Module load completed but symbols could not be loaded for AsUpIO.sys
Probably caused by : AsUpIO.sys ( AsUpIO+1766 )

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: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 0000000000000118, Handle value being referenced.
Arg3: fffffa8005402b30, Address of the current process.
Arg4: fffff88003fe8766, 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:  PEUpdater.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80005d0e3dc to fffff80005884c40

STACK_TEXT:  
fffff880`049a9448 fffff800`05d0e3dc : 00000000`000000c4 00000000`000000f6 00000000`00000118 fffffa80`05402b30 : nt!KeBugCheckEx
fffff880`049a9450 fffff800`05d23ae4 : 00000000`00000118 fffffa80`05402b30 00000000`00000002 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`049a9490 fffff800`05adc210 : fffff800`05b7af90 fffff880`049a96c0 00000000`00000000 00000000`00000000 : nt!VfCheckUserHandle+0x1b4
fffff880`049a9570 fffff800`05b5f375 : 00000000`00000000 00000000`000f001f 00000000`00000000 fffff800`05b5f300 : nt! ?? ::NNGAKEGL::`string'+0x212ce
fffff880`049a9640 fffff800`05d23878 : 00000000`00000001 00000000`00000002 fffff880`049a9730 fffff800`05880470 : nt!ObReferenceObjectByHandle+0x25
fffff880`049a9690 fffff880`03fe8766 : 00000000`00000000 00000000`00000002 00000000`00000001 fffff800`05d0e14e : nt!VerifierObReferenceObjectByHandle+0x48
fffff880`049a96e0 00000000`00000000 : 00000000`00000002 00000000`00000001 fffff800`05d0e14e fffff880`049a9768 : AsUpIO+0x1766


STACK_COMMAND:  kb

FOLLOWUP_IP: 
AsUpIO+1766
fffff880`03fe8766 8bd8            mov     ebx,eax

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  AsUpIO+1766

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AsUpIO

IMAGE_NAME:  AsUpIO.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c57835f

FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_AsUpIO+1766

BUCKET_ID:  X64_0xc4_f6_VRF_AsUpIO+1766

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

I would assume it's one of the ones under Utilities.