BSOD on shut down. MiniDump attached

#1
View attachment BradsMiniDump.rar

Every time I shut my computer down it sits on the "Shutting Down" screen for 10-15 min or so before getting to the bsod.

This started happening right about the same time I got a couple new monitors for my computer. I initially plugged them into the on board video ports (instead of the video card dvi inputs) by accident when I booted up with them the first time. Not sure if that could have caused something to go wrong, but I figured its worth mentioning.


Some of my system stats if it helps:

OS, Win7 6.1.7601 Service Pack 1 Build 7601
Processor, Intel Core i5-2500K CPU @ 3.30GHz, 3300 Mhz, 4 Cores Logical Processors
8GB Ram
NVIDIA GeForce GTX 560 Ti
 


Trouble

Noob Whisperer
#2
A single dump file is not a lot to go on. Looks like
1394ohci.sys
is getting the blame on this one. Normally I would ignore that since it's a Native Windows 7 (Microsoft) file and would not likely be the actual cause of the Blue Screen I would just like to suggest that if this is an addon card or even integrated onto the Motherboard, you may very well need to check with the specific vendor / manufacturer and see if there is proprietary driver that may be more optimal for that device.
Additionally see if you can't update this driver
wacommousefilter.sys 2/16/2007 from here Drivers | Wacom Americas
DUMP:
Code:
...........................................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff9800840cd60, 2, 0, fffff880111c2b4d}

Unable to load image iaStor.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
Probably caused by : 1394ohci.sys ( 1394ohci!AsyncTx::VerifyGenerationCount+9 )

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

0: 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: fffff9800840cd60, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880111c2b4d, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036ff100
 fffff9800840cd60 

CURRENT_IRQL:  2

FAULTING_IP: 
1394ohci!AsyncTx::VerifyGenerationCount+9
fffff880`111c2b4d 418b00          mov     eax,dword ptr [r8]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff80004d55af0 -- (.trap 0xfffff80004d55af0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8013a0e990 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa8013a0e990 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880111c2b4d rsp=fffff80004d55c88 rbp=0000000000000003
 r8=fffff9800840cd60  r9=fffffa80135d03d0 r10=0000000000000028
r11=fffff80004d55c10 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
1394ohci!AsyncTx::VerifyGenerationCount+0x9:
fffff880`111c2b4d 418b00          mov     eax,dword ptr [r8] ds:fffff980`0840cd60=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800034cc1e9 to fffff800034ccc40

STACK_TEXT:  
fffff800`04d559a8 fffff800`034cc1e9 : 00000000`0000000a fffff980`0840cd60 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`04d559b0 fffff800`034cae60 : 00000000`00000000 fffff800`04d55c10 00000000`0000000b fffffa80`135d03d0 : nt!KiBugCheckDispatch+0x69
fffff800`04d55af0 fffff880`111c2b4d : fffff880`111c2d35 fffffa80`135d03d0 00000000`00000003 00000000`00000002 : nt!KiPageFault+0x260
fffff800`04d55c88 fffff880`111c2d35 : fffffa80`135d03d0 00000000`00000003 00000000`00000002 fffff880`111e7a17 : 1394ohci!AsyncTx::VerifyGenerationCount+0x9
fffff800`04d55c90 fffff880`111c180b : 00000000`00008411 00000000`00000000 fffff880`111e9600 fffffa80`135d03d0 : 1394ohci!AsyncTx::StateMachine+0x181
fffff800`04d55d30 fffff880`111e1210 : 00000000`00000001 00000000`0000000a 00000000`00000001 00000000`0000000a : 1394ohci!AsyncTx::BusResetHandler+0x7b
fffff800`04d55d80 fffff880`111e00cf : fffffa80`136a3d00 fffffa80`136a3e00 00000000`00000001 fffff800`04d55e00 : 1394ohci!Topology::BuildTopologyMap+0xaa4
fffff800`04d55e50 fffff880`111ca0ef : fffffa80`136a3dd0 00000000`00010000 fffffa80`136a3e00 fffffa80`136a3f70 : 1394ohci!Topology::InterruptHandler+0x2f
fffff800`04d55e80 fffff880`00fae8a7 : 0000057f`ec95c228 fffffa80`136a3dd0 fffffa80`136a3e60 fffffa80`083707f8 : 1394ohci!Interrupt::WdfEvtInterruptDpc+0x177
fffff800`04d55ed0 fffff800`034d80ac : fffff800`03642e80 fffffa80`000002a0 fffffa80`13602d40 00000000`000000a0 : Wdf01000!FxInterrupt::_InterruptDpcThunk+0x8f
fffff800`04d55f00 fffff800`034cf765 : 00000000`00000000 fffffa80`082fc040 00000000`00000000 fffff880`00fae818 : nt!KiRetireDpcList+0x1bc
fffff800`04d55fb0 fffff800`034cf57c : 00000000`00000002 fffff800`034f8830 00000000`00000000 fffffa80`06991ba0 : nt!KyRetireDpcList+0x5
fffff880`039788c0 fffff800`0351885c : 00000000`00000000 fffff880`03978a10 00000000`0000000b fffff880`03978b10 : nt!KiDispatchInterruptContinue
fffff880`039788f0 fffff800`039645c8 : fffffa80`0837c768 fffff880`0105d9e3 fffffa80`09874a00 00000000`00000002 : nt!KiDpcInterrupt+0xcc
fffff880`03978a80 fffff880`0105d9e3 : fffff880`01089430 fffffa80`0894e1b8 fffffa80`0894e101 fffffa80`09874a48 : nt!VerifierKeReleaseSpinLock+0xd8
fffff880`03978ac0 fffff880`01089430 : fffffa80`0894e1b8 fffffa80`0894e101 fffffa80`09874a48 fffffa80`0894e101 : iaStor+0x249e3
fffff880`03978ac8 fffffa80`0894e1b8 : fffffa80`0894e101 fffffa80`09874a48 fffffa80`0894e101 fffff880`0103c2a9 : iaStor+0x50430
fffff880`03978ad0 fffffa80`0894e101 : fffffa80`09874a48 fffffa80`0894e101 fffff880`0103c2a9 fffffa80`0894e1b8 : 0xfffffa80`0894e1b8
fffff880`03978ad8 fffffa80`09874a48 : fffffa80`0894e101 fffff880`0103c2a9 fffffa80`0894e1b8 fffffa80`0894e101 : 0xfffffa80`0894e101
fffff880`03978ae0 fffffa80`0894e101 : fffff880`0103c2a9 fffffa80`0894e1b8 fffffa80`0894e101 fffffa80`0894e1b8 : 0xfffffa80`09874a48
fffff880`03978ae8 fffff880`0103c2a9 : fffffa80`0894e1b8 fffffa80`0894e101 fffffa80`0894e1b8 fffff800`0396458b : 0xfffffa80`0894e101
fffff880`03978af0 fffffa80`0894e1b8 : fffffa80`0894e101 fffffa80`0894e1b8 fffff800`0396458b 400a17e0`10608027 : iaStor+0x32a9
fffff880`03978af8 fffffa80`0894e101 : fffffa80`0894e1b8 fffff800`0396458b 400a17e0`10608027 000000c0`00000002 : 0xfffffa80`0894e1b8
fffff880`03978b00 fffffa80`0894e1b8 : fffff800`0396458b 400a17e0`10608027 000000c0`00000002 fffffa80`00000000 : 0xfffffa80`0894e101
fffff880`03978b08 fffff800`0396458b : 400a17e0`10608027 000000c0`00000002 fffffa80`00000000 fffffa80`0894e1b8 : 0xfffffa80`0894e1b8
fffff880`03978b10 fffff880`01089ab6 : fffffa80`09874a00 fffffa80`09874a48 fffffa80`0894e1b8 fffffa80`08370b90 : nt!VerifierKeReleaseSpinLock+0x9b
fffff880`03978b50 fffffa80`09874a00 : fffffa80`09874a48 fffffa80`0894e1b8 fffffa80`08370b90 fffffa80`082fc000 : iaStor+0x50ab6
fffff880`03978b58 fffffa80`09874a48 : fffffa80`0894e1b8 fffffa80`08370b90 fffffa80`082fc000 00000000`00000000 : 0xfffffa80`09874a00
fffff880`03978b60 fffffa80`0894e1b8 : fffffa80`08370b90 fffffa80`082fc000 00000000`00000000 00000000`00000000 : 0xfffffa80`09874a48
fffff880`03978b68 fffffa80`08370b90 : fffffa80`082fc000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`0894e1b8
fffff880`03978b70 fffffa80`082fc000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0764f4c0 : 0xfffffa80`08370b90
fffff880`03978b78 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`0764f4c0 fffff800`035d18ee : 0xfffffa80`082fc000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
1394ohci!AsyncTx::VerifyGenerationCount+9
fffff880`111c2b4d 418b00          mov     eax,dword ptr [r8]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  1394ohci!AsyncTx::VerifyGenerationCount+9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: 1394ohci

IMAGE_NAME:  1394ohci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a6a8

FAILURE_BUCKET_ID:  X64_0xD1_1394ohci!AsyncTx::VerifyGenerationCount+9

BUCKET_ID:  X64_0xD1_1394ohci!AsyncTx::VerifyGenerationCount+9

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

0: kd> lmvm 1394ohci
start             end                 module name
fffff880`111b7000 fffff880`111f5000   1394ohci   (pdb symbols)          c:\symbols\1394OHCI.pdb\39D04E6E457F4C9E8001D7FAF62CDBE51\1394OHCI.pdb
    Loaded symbol image file: 1394ohci.sys
    Mapped memory image file: c:\symbols\1394ohci.sys\4CE7A6A83e000\1394ohci.sys
    Image path: 1394ohci.sys
    Image name: 1394ohci.sys
    Timestamp:        Sat Nov 20 04:44:56 2010 (4CE7A6A8)
    CheckSum:         0003B054
    ImageSize:        0003E000
    File version:     6.1.7601.17514
    Product version:  6.1.7601.17514
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     1394ohci.sys
    OriginalFilename: 1394ohci.sys
    ProductVersion:   6.1.7601.17514
    FileVersion:      6.1.7601.17514 (win7sp1_rtm.101119-1850)
    FileDescription:  1394 OpenHCI Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.
If Blue Screens persist;
Please read the first post in this sticky thread here How to ask for help with a BSOD problem
Do your best to accumulate the data required.
Run the SF Diagnostic tool (download and right click the executable and choose run as administrator)
Download and run CPUz. Use the Windows snipping tool to gather images from all tabs including all slots populated with memory under the SPD tab.
Likewise RAMMon. Export the html report, put everything into a desktop folder that you've created for this purpose, zip it up and attach it to your next post (right click it and choose send to, compressed (zipped) folder.
Good luck
Randy
 


#3
View attachment Seven Forums.rar

Ahh, sorry for my negligence. I should have read the sticky post first :p

I ran CPUz, Rammon and the SF Diag tool. All the results and screenshots are in the attached rar file on this reply.
Thank you!
 


Trouble

Noob Whisperer
#4
The newest dump file is indicating an issue with
EtronHub3.sys
Check here GIGABYTE - Motherboard - Socket 1155 - GA-Z68X-UD3H-B3 (rev. 1.3) use the links at the top to make sure you have the right Rev. # (1.0 or 1.3)
select your version of Windows 7 (32 or 64 bit) and update your board's drivers including Chipset if needed. The Etron USB 3.0 driver listed there looks slightly newer than the one you are using.
Also there looks like there might have been 3 or 4 BIOS updates for that board you might consider updating.
Code:
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa8013c752a0, fffff80000b9c3d8, fffffa80138308c0}
*** WARNING: Unable to verify timestamp for EtronHub3.sys
*** ERROR: Module load completed but symbols could not be loaded for EtronHub3.sys
Probably caused by : [B][U][COLOR=#ff0000]EtronHub3.sys[/COLOR][/U][/B]
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
[COLOR=#ff0000][U][B]DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.[/B][/U][/COLOR]
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8013c752a0, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, Functional Device Object of the stack
Arg4: fffffa80138308c0, The blocked IRP
Debugging Details:
-----------------
DRVPOWERSTATE_SUBCODE:  3
DRIVER_OBJECT: fffffa80130236f0
IMAGE_NAME:  EtronHub3.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4d67ec3b
MODULE_NAME: EtronHub3
FAULTING_MODULE: fffff88007e6a000 EtronHub3
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
CURRENT_IRQL:  2
STACK_TEXT:  
fffff800`00b9c388 fffff800`03546cd2 : 00000000`0000009f 00000000`00000003 fffffa80`13c752a0 fffff800`00b9c3d8 : nt!KeBugCheckEx
fffff800`00b9c390 fffff800`034e45fc : fffff800`00b9c4c0 fffff800`00b9c4c0 00000000`00000000 00000000`00000003 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`00b9c430 fffff800`034e4496 : fffffa80`12cb4588 00000000`001fc365 00000000`00000000 fffff880`11191095 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`034e437e : 0000004b`9bddff93 fffff800`00b9cb18 00000000`001fc365 fffff800`03651f28 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`034e4167 : 00000018`4fa7f8c3 00000018`001fc365 00000018`4fa7f8ff 00000000`00000065 : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`034d096a : fffff800`0364ee80 fffff800`0365ccc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_EtronHub3.sys
BUCKET_ID:  X64_0x9F_3_IMAGE_EtronHub3.sys
Followup: MachineOwner
The following actions might prevent an error like this from happening again:

Download and install updates and device drivers for your computer from Windows Update.
Scan your computer for computer viruses.
Check your hard disk for errors.
SOURCE: Bug Check 0x9F: DRIVER_POWER_STATE_FAILURE
 


#5
I updated the eTron usb 3.0 driver first and that seems to have done the trick!
I may still go ahead and update some of the other things that you mentioned just for good measure, but for now Im happy with a computer that will shut down with no bsod.
I have no idea how this could have gone awry, seeing as now I havent installed any new usb devices lately... Stuff happens I guess.

Thanks!
 


Trouble

Noob Whisperer
#6
Glad to hear that you have made some progress. Thanks for the followup and posting back to update your thread with that information.
Keep us posted as to how you may be progressing.
Regards
Randy
 


#7
So after updating the eTron drivers, my usb multi card reader came up as a non responding device. I guess the previous drivers didnt handle it very well, the new ones just tell me that its delinquent.
Anyway, I've removed that device from my machine, all is well now.
 


Trouble

Noob Whisperer
#8
Good to know you are up and running without problem now.
The issue with the Etron device is likely something you will have to reconcile at a later date as newer drivers become available.
Have you considered starting a trouble ticket with your manufacturer GIGABYTE GTS
Perhaps they will have a recommendation as to how you might proceed.
I noticed that your motherboard has a couple more recent BIOS updates (including their latest beta bios) but I don't see any reference among them indicating a possible fix for your particular issue. So while I wouldn't necessarily recommend a BIOS flash, it might be something to consider.
You may also want to try their "Official" forums Motherboards with Intel processors
Unfortunately it doesn't include a search function that I could find but you might want to start a thread there and see if anyone else has similar issues and or a possible solution you might try.
Regards
Randy
 


Trouble

Noob Whisperer
#9
Registered and searched their forum and found this Z68X-UD3H-B3 USB 3.0 BSOD and some others as well. Possibly worth looking into, it does discus a specific hotfix from microsoft that may address your issue "STOP 0x000000D1" error message when you try to access a device that is not a PCI device in Windows 7 or in Windows Server 2008 R2
May be worth looking into since one of your two dump files was a D1
DUMP:
Code:
BugCheck D1, {fffff9800840cd60, 2, 0, fffff880111c2b4d}
Unable to load image iaStor.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
Probably caused by : 1394ohci.sys ( 1394ohci!AsyncTx::VerifyGenerationCount+9 )
Followup: MachineOwner
---------
0: 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: fffff9800840cd60, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880111c2b4d, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036ff100
 fffff9800840cd60 
CURRENT_IRQL:  2
FAULTING_IP: 
1394ohci!AsyncTx::VerifyGenerationCount+9
fffff880`111c2b4d 418b00          mov     eax,dword ptr [r8]
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
TRAP_FRAME:  fffff80004d55af0 -- (.trap 0xfffff80004d55af0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8013a0e990 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa8013a0e990 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880111c2b4d rsp=fffff80004d55c88 rbp=0000000000000003
 r8=fffff9800840cd60  r9=fffffa80135d03d0 r10=0000000000000028
r11=fffff80004d55c10 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
1394ohci!AsyncTx::VerifyGenerationCount+0x9:
fffff880`111c2b4d 418b00          mov     eax,dword ptr [r8] ds:fffff980`0840cd60=????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff800034cc1e9 to fffff800034ccc40
STACK_TEXT:  
fffff800`04d559a8 fffff800`034cc1e9 : 00000000`0000000a fffff980`0840cd60 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`04d559b0 fffff800`034cae60 : 00000000`00000000 fffff800`04d55c10 00000000`0000000b fffffa80`135d03d0 : nt!KiBugCheckDispatch+0x69
fffff800`04d55af0 fffff880`111c2b4d : fffff880`111c2d35 fffffa80`135d03d0 00000000`00000003 00000000`00000002 : nt!KiPageFault+0x260
fffff800`04d55c88 fffff880`111c2d35 : fffffa80`135d03d0 00000000`00000003 00000000`00000002 fffff880`111e7a17 : 1394ohci!AsyncTx::VerifyGenerationCount+0x9
fffff800`04d55c90 fffff880`111c180b : 00000000`00008411 00000000`00000000 fffff880`111e9600 fffffa80`135d03d0 : 1394ohci!AsyncTx::StateMachine+0x181
fffff800`04d55d30 fffff880`111e1210 : 00000000`00000001 00000000`0000000a 00000000`00000001 00000000`0000000a : 1394ohci!AsyncTx::BusResetHandler+0x7b
fffff800`04d55d80 fffff880`111e00cf : fffffa80`136a3d00 fffffa80`136a3e00 00000000`00000001 fffff800`04d55e00 : 1394ohci!Topology::BuildTopologyMap+0xaa4
fffff800`04d55e50 fffff880`111ca0ef : fffffa80`136a3dd0 00000000`00010000 fffffa80`136a3e00 fffffa80`136a3f70 : 1394ohci!Topology::InterruptHandler+0x2f
fffff800`04d55e80 fffff880`00fae8a7 : 0000057f`ec95c228 fffffa80`136a3dd0 fffffa80`136a3e60 fffffa80`083707f8 : 1394ohci!Interrupt::WdfEvtInterruptDpc+0x177
fffff800`04d55ed0 fffff800`034d80ac : fffff800`03642e80 fffffa80`000002a0 fffffa80`13602d40 00000000`000000a0 : Wdf01000!FxInterrupt::_InterruptDpcThunk+0x8f
fffff800`04d55f00 fffff800`034cf765 : 00000000`00000000 fffffa80`082fc040 00000000`00000000 fffff880`00fae818 : nt!KiRetireDpcList+0x1bc
fffff800`04d55fb0 fffff800`034cf57c : 00000000`00000002 fffff800`034f8830 00000000`00000000 fffffa80`06991ba0 : nt!KyRetireDpcList+0x5
fffff880`039788c0 fffff800`0351885c : 00000000`00000000 fffff880`03978a10 00000000`0000000b fffff880`03978b10 : nt!KiDispatchInterruptContinue
fffff880`039788f0 fffff800`039645c8 : fffffa80`0837c768 fffff880`0105d9e3 fffffa80`09874a00 00000000`00000002 : nt!KiDpcInterrupt+0xcc
fffff880`03978a80 fffff880`0105d9e3 : fffff880`01089430 fffffa80`0894e1b8 fffffa80`0894e101 fffffa80`09874a48 : nt!VerifierKeReleaseSpinLock+0xd8
fffff880`03978ac0 fffff880`01089430 : fffffa80`0894e1b8 fffffa80`0894e101 fffffa80`09874a48 fffffa80`0894e101 : iaStor+0x249e3
fffff880`03978ac8 fffffa80`0894e1b8 : fffffa80`0894e101 fffffa80`09874a48 fffffa80`0894e101 fffff880`0103c2a9 : iaStor+0x50430
fffff880`03978ad0 fffffa80`0894e101 : fffffa80`09874a48 fffffa80`0894e101 fffff880`0103c2a9 fffffa80`0894e1b8 : 0xfffffa80`0894e1b8
fffff880`03978ad8 fffffa80`09874a48 : fffffa80`0894e101 fffff880`0103c2a9 fffffa80`0894e1b8 fffffa80`0894e101 : 0xfffffa80`0894e101
fffff880`03978ae0 fffffa80`0894e101 : fffff880`0103c2a9 fffffa80`0894e1b8 fffffa80`0894e101 fffffa80`0894e1b8 : 0xfffffa80`09874a48
fffff880`03978ae8 fffff880`0103c2a9 : fffffa80`0894e1b8 fffffa80`0894e101 fffffa80`0894e1b8 fffff800`0396458b : 0xfffffa80`0894e101
fffff880`03978af0 fffffa80`0894e1b8 : fffffa80`0894e101 fffffa80`0894e1b8 fffff800`0396458b 400a17e0`10608027 : iaStor+0x32a9
fffff880`03978af8 fffffa80`0894e101 : fffffa80`0894e1b8 fffff800`0396458b 400a17e0`10608027 000000c0`00000002 : 0xfffffa80`0894e1b8
fffff880`03978b00 fffffa80`0894e1b8 : fffff800`0396458b 400a17e0`10608027 000000c0`00000002 fffffa80`00000000 : 0xfffffa80`0894e101
fffff880`03978b08 fffff800`0396458b : 400a17e0`10608027 000000c0`00000002 fffffa80`00000000 fffffa80`0894e1b8 : 0xfffffa80`0894e1b8
fffff880`03978b10 fffff880`01089ab6 : fffffa80`09874a00 fffffa80`09874a48 fffffa80`0894e1b8 fffffa80`08370b90 : nt!VerifierKeReleaseSpinLock+0x9b
fffff880`03978b50 fffffa80`09874a00 : fffffa80`09874a48 fffffa80`0894e1b8 fffffa80`08370b90 fffffa80`082fc000 : iaStor+0x50ab6
fffff880`03978b58 fffffa80`09874a48 : fffffa80`0894e1b8 fffffa80`08370b90 fffffa80`082fc000 00000000`00000000 : 0xfffffa80`09874a00
fffff880`03978b60 fffffa80`0894e1b8 : fffffa80`08370b90 fffffa80`082fc000 00000000`00000000 00000000`00000000 : 0xfffffa80`09874a48
fffff880`03978b68 fffffa80`08370b90 : fffffa80`082fc000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`0894e1b8
fffff880`03978b70 fffffa80`082fc000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0764f4c0 : 0xfffffa80`08370b90
fffff880`03978b78 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`0764f4c0 fffff800`035d18ee : 0xfffffa80`082fc000
STACK_COMMAND:  kb
FOLLOWUP_IP: 
1394ohci!AsyncTx::VerifyGenerationCount+9
fffff880`111c2b4d 418b00          mov     eax,dword ptr [r8]
SYMBOL_STACK_INDEX:  3
SYMBOL_NAME:  1394ohci!AsyncTx::VerifyGenerationCount+9
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: 1394ohci
IMAGE_NAME:  1394ohci.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a6a8
FAILURE_BUCKET_ID:  X64_0xD1_1394ohci!AsyncTx::VerifyGenerationCount+9
BUCKET_ID:  X64_0xD1_1394ohci!AsyncTx::VerifyGenerationCount+9
Followup: MachineOwner
Regards
Randy
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.