Random BSOD on Windows 7

[tozzleozzle]

BSOD randomly happens when doing normal tasks and updating.

0x00000050 (0XFFFFF900C52BB000, 0X0000000000000000, 0XFFFFF960007800D4) CDD.DI11 - Address FFFFF960007800D4 Base at FFFFF96000760000, datestamp 4CE7C546


Hi Guys.

A rather defeted plee for help

Ok so. My little brother and i have built a gaming PC. Hardware is as follows:

Motherboard: Asus M5A97
Processor: AMD FX 6 core
RAM: 4GB (2X2GB)
Graphics Card: Nvidia GTX 560
Hard Drive: 1TB Smamsung
OS: Win 7 Full Retail 64bit

It started when we first installed windows 7 onto the formatted hard drive, during the setup it BSOD'ed and displayed the error as stated above. We then ran the installation again and it worked, horay i thought! Then as i tryed my 1st update it did it again, with the same error mesage. So i tried to update all of the Hardware drivers 1st. did that and ran a few updates, no problems. We then got the BSOD again when steam and tunes downloading finished downloading. So i checked out some forums, wich is how i came across this Forum .

After finding a few little things to do i got back to trying to update the remandor of the updates, at this point where i couldent update 4 last updates, i installed vereous utilities to try and help but nothing worked, Windows sugested that i put the OS disc back in and "update" the PC... so i did. As you "update" the OS it asked to keep the internet on during istalation so it can find updates etc. of corce it BSOD'ed again.

After a bit more diging around on forums i found out that the TP-Link TLWN350G could be to blame as anytime it seemed to BSOD was when internet was involved. So i changed it for a run of the mill 56k dongle and uninstalled the drivers for the TP-Link adaptor.

It went throught the OS update OK and seemed good for a while, only to find the horror of another BSOD when i was updating the windows updates and has done it again a hour or so ago.

I just dont know what to do i was sure it was to do with the TP Link card. But yet the same error that has been apering throughout has happend again. What am i missing?

Thanks for the time and sorry about the long post (and spelling)!

Tom

EDIT: I have just added the zip file as requested

 

[ePeen]

Hello, welcome to SevenForums!

Two dumps, one points to cdd.dll and the other to usbhub.sys. cdd.dll is the Canonical Display Driver, so there may be an issue with your video card drivers. First off, I'd like you to uninstall your current video card drivers and install the latest version from Drivers - Download NVIDIA Drivers

Second, there's a few tests I'd like you to run:

Chkdsk:

1. Open the "Computer" window
2. Right-click on the drive in question
3. Select the "Tools" tab
4. In the Error-checking area, click <Check Now>.

Memtest:

Read the following to test your memory for errors.

Driver Verifier:

Read the following to enable Driver Verifier. Use Driver Second if Memtest finds nothing, as it's likely a software / driver issue, we just aren't being told what it is, and hopefully Driver Verifier will than force a crash if it finds the violating driver.

Before enabling Driver Verifier, my recommendation is to set a backup / restore point as in severe cases Driver Verifier can break your Windows. If you have difficulty getting into Windows, boot into Safe Mode and disable Driver Verifier there.

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\Windows_NT6_BSOD_jcgriff2\022612-51558-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`05809000 PsLoadedModuleList = 0xfffff800`05a4e670
Debug session time: Sun Feb 26 17:24:48.510 2012 (UTC - 5:00)
System Uptime: 0 days 0:06:47.665
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff900c52bb000, 0, fffff960007800d4, 0}


Could not read faulting driver name
Probably caused by : cdd.dll ( cdd!memcpy+b4 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff900c52bb000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff960007800d4, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

OVERLAPPED_MODULE: Address regions for 'nvlddmkm' and 'nvlddmkm.sys' overlap

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80005ab8100
 fffff900c52bb000 

FAULTING_IP: 
cdd!memcpy+b4
fffff960`007800d4 4c8b540a08      mov     r10,qword ptr [rdx+rcx+8]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800b12cf50 -- (.trap 0xfffff8800b12cf50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000e2ea38
rdx=fffff900c448c5c0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960007800d4 rsp=fffff8800b12d0e8 rbp=000000000000009a
 r8=000000000000093c  r9=0003fffffffd6251 r10=0000000000000000
r11=00000000008f2b34 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cdd!memcpy+0xb4:
fffff960`007800d4 4c8b540a08      mov     r10,qword ptr [rdx+rcx+8] ds:d180:fffff900`c52bb000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800058319fc to fffff80005885c40

STACK_TEXT:  
fffff880`0b12cde8 fffff800`058319fc : 00000000`00000050 fffff900`c52bb000 00000000`00000000 fffff880`0b12cf50 : nt!KeBugCheckEx
fffff880`0b12cdf0 fffff800`05883d6e : 00000000`00000000 fffff900`c52bb000 fffff8a0`01343a00 fffff900`c4d7f0f4 : nt! ?? ::FNODOBFM::`string'+0x4611f
fffff880`0b12cf50 fffff960`007800d4 : fffff960`00764281 00000000`00000000 fffff8a0`01400000 00000000`00000001 : nt!KiPageFault+0x16e
fffff880`0b12d0e8 fffff960`00764281 : 00000000`00000000 fffff8a0`01400000 00000000`00000001 00000000`00000000 : cdd!memcpy+0xb4
fffff880`0b12d0f0 fffff960`00764c26 : fffff900`c00de020 00000000`00000030 fffff900`c1da6130 fffff900`c01d02b0 : cdd!CopyBits+0xed
fffff880`0b12d130 fffff960`0076606c : ffffffff`fffd7476 00000000`0b0407d8 00000000`00000001 00000000`00000000 : cdd!CddPresentBlt+0x2ae
fffff880`0b12d870 fffff800`05b20fee : fffff880`00000004 fffffa80`06251b60 00000000`00000080 fffffa80`071ceaa0 : cdd!PresentWorkerThread+0xd00
fffff880`0b12dc00 fffff800`058775e6 : fffff880`02fe3180 fffffa80`06251b60 fffff880`02fee040 fffff880`01259cb0 : nt!PspSystemThreadStartup+0x5a
fffff880`0b12dc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
cdd!memcpy+b4
fffff960`007800d4 4c8b540a08      mov     r10,qword ptr [rdx+rcx+8]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  cdd!memcpy+b4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: cdd

IMAGE_NAME:  cdd.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7c546

FAILURE_BUCKET_ID:  X64_0x50_cdd!memcpy+b4

BUCKET_ID:  X64_0x50_cdd!memcpy+b4

Followup: MachineOwner

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\Windows_NT6_BSOD_jcgriff2\022612-32261-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`0581d000 PsLoadedModuleList = 0xfffff800`05a62670
Debug session time: Sun Feb 26 18:01:20.399 2012 (UTC - 5:00)
System Uptime: 0 days 0:25:15.554
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffa80ab4a52d0, 2, 1, fffff88004d39077}

Probably caused by : usbhub.sys ( usbhub!Log+6f )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffffa80ab4a52d0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88004d39077, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80005acc100
 fffffa80ab4a52d0 

CURRENT_IRQL:  2

FAULTING_IP: 
usbhub!Log+6f
fffff880`04d39077 8901            mov     dword ptr [rcx],eax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff8800318b6d0 -- (.trap 0xfffff8800318b6d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000002d2d7170 rbx=0000000000000000 rcx=fffffa80ab4a52d0
rdx=0000000000001cc1 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004d39077 rsp=fffff8800318b868 rbp=fffffa8005ea3050
 r8=0000000070712d2d  r9=0000000000000003 r10=fffffa8005ea31a0
r11=0000000000000482 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
usbhub!Log+0x6f:
fffff880`04d39077 8901            mov     dword ptr [rcx],eax ds:0b00:fffffa80`ab4a52d0=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800058991e9 to fffff80005899c40

STACK_TEXT:  
fffff880`0318b588 fffff800`058991e9 : 00000000`0000000a fffffa80`ab4a52d0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0318b590 fffff800`05897e60 : 00000000`00000000 00000001`05ea3050 fffff880`0318b8f0 fffffa80`05ed0b20 : nt!KiBugCheckDispatch+0x69
fffff880`0318b6d0 fffff880`04d39077 : fffff880`04d43901 00000000`00000010 fffff880`2d2d7170 fffffa80`05ea3050 : nt!KiPageFault+0x260
fffff880`0318b868 fffff880`04d43901 : 00000000`00000010 fffff880`2d2d7170 fffffa80`05ea3050 fffff880`0318b8f8 : usbhub!Log+0x6f
fffff880`0318b870 fffff880`04d4796c : fffffa80`05ed0b20 00000000`00000000 00000000`00000000 00000000`000007ff : usbhub!UsbhUnlockPcqWithTag+0x35
fffff880`0318b8b0 fffff880`04d43cf6 : 00000000`00000000 00000000`50447100 fffffa80`05ed0b20 fffffa80`05ea3050 : usbhub!Usbh_PCE_wChange_Action+0x20c
fffff880`0318b8f0 fffff880`04d4a6b0 : fffffa80`05ed0b20 fffffa80`05ed0b38 00000000`00000002 fffffa80`05ea3050 : usbhub!UsbhDispatch_PortChangeQueueEventEx+0x22a
fffff880`0318b930 fffff880`04d46c79 : 00000000`00000000 00000000`00000004 fffffa80`00000100 fffffa80`05ea3050 : usbhub!UsbhHubRunPortChangeQueue+0x188
fffff880`0318ba00 fffff880`04d43b8c : 00000000`00000001 fffffa80`50447100 fffffa80`05ed0b20 fffffa80`05ea3050 : usbhub!Usbh_PCE_wRun_Action+0x1ed
fffff880`0318ba50 fffff880`04d4899a : fffffa80`05ed0b20 fffff800`05a3a2b8 fffffa80`05ed0b38 fffffa80`05ea3050 : usbhub!UsbhDispatch_PortChangeQueueEventEx+0xc0
fffff880`0318ba90 fffff880`04d4aab1 : 00000000`00000002 fffffa80`05ea3050 fffffa80`00000000 00000000`00000002 : usbhub!UsbhPCE_wRun+0x82
fffff880`0318bae0 fffff800`05b909e3 : fffffa80`05ea3050 00000000`00000001 ffffffff`dc3a58a0 fffff800`05a3a2b8 : usbhub!UsbhHubProcessChangeWorker+0x13d
fffff880`0318bb40 fffff800`058a4001 : fffff800`05a3a200 fffff800`05b90901 fffffa80`03a45000 00000000`00000000 : nt!IopProcessWorkItem+0x23
fffff880`0318bb70 fffff800`05b34fee : 00000000`00000000 fffffa80`03a45040 00000000`00000080 fffffa80`03946b30 : nt!ExpWorkerThread+0x111
fffff880`0318bc00 fffff800`0588b5e6 : fffff880`030a4180 fffffa80`03a45040 fffff880`030af040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0318bc40 00000000`00000000 : fffff880`0318c000 fffff880`03186000 fffff880`0318b8a0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbhub!Log+6f
fffff880`04d39077 8901            mov     dword ptr [rcx],eax

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  usbhub!Log+6f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbhub

IMAGE_NAME:  usbhub.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a68e

FAILURE_BUCKET_ID:  X64_0xD1_usbhub!Log+6f

BUCKET_ID:  X64_0xD1_usbhub!Log+6f

Followup: MachineOwner

 

[tozzleozzle]

Thanks for this, i will have a go later on today

 

[tozzleozzle]

OK i have done the Chkdsk, is there a file i need to upload? it dident give me anything i could take copy down, just tested and restarted, is that correct?

I am now doing the Memtest, big thanks to Dave76 for an exelant tutorial i will let you know the outcome.

 

[ePeen]

Great!

And yes, here's a great tutorial on how to find the chkdsk log after running one.

http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html

 

[tozzleozzle]

I have attached the result of the Chkdsk

As for the Memtest - It came back as no errors after 8 passes (6.5 hours)

Just about to do the "Driver Verifier"

I should aslo mention that i have fully updated the motherboard and graphics card. I did encounter a BSOD when i tried to update the graphics card, so i updated the mother board first (to its latest version) then the graphics card, no BSOD that time

 

[ePeen]

Chkdsk detected no bad sectors. Yes, please enable Driver Verifier now, but remember to make a backup / restore point

 

[tozzleozzle]

Driver Verifier enabled. Although it the PC now wont let me get on the internet - EDIT its working now, odd!

If it BSOD's during the 24 hour period what shall i do? make another Windows_NT6_BSOD_jcgriff2 report? also how do it check if the Driver Verifier is definatly enabled?

 

[ePeen]

If Driver Verifier finds a fault in a driver it will force a BSOD and create a verifier enabled dump. I can't remember, but this will be located in either C:/Windows or C:/Windows/Minidump. You can tell which one it is normally by checking the time & date of the file's creation.

Once you found it, simply attach that BSOD itself, or you can re-add it to your original attachment

To check the status of Driver Verifier you can do one of two ways, at least that's all I am familiar with:

1.

The Driver Verifier Manager tool (Verifier.exe) is the preferred way to create and modify Driver Verifier settings and to gather statistics from Driver Verifier. Verifier.exe is located in the %WinDir%\System32 folder for every Windows installation. Driver Status

The Driver Status property page gives you an image of the current status of Driver Verifier. You can see what drivers the verifier detects. The status can be one of the following:

• Loaded: The driver is currently loaded and verified.
• Unloaded: The driver is not currently loaded but it was loaded at least once since you restarted the computer.
• Never Loaded: The driver was never loaded. This status can indicate that the driver's

2.

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

verifier /query

 

[tozzleozzle]

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?

 

[ePeen]

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.

 

[tozzleozzle]

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?

 

[ePeen]

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.

 

[tozzleozzle]

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

 

[ePeen]

Sounds great.

 

[tozzleozzle]

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....

 

[tozzleozzle]

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

 

[ePeen]

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.

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
---------

 

[tozzleozzle]

Cheers for that. Yeah i was in the ASUS hardware monitoring software when it happened so that would make sense!

I downloaded the latest BIOS update yesterday but it comes as a ".rom" file, wich i could only use when i opened it in the ASUS hardware monitoring software... so are you saying that i need to update the ASUS hardware monitoring software then?

Can you help me find what to download? There are so many to choose from! here is the link to the drivers:

ASUSTeK Computer Inc. -Support- Drivers and Download M5A97 PRO

If you just select windows 7 64 bit in the drop down menu.

 

[ePeen]

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