Attachment 730205 Details for Bug 946992 – windbg information

windbg information

windbg information.txt (text/plain), 13.59 KB, created by lijin on 2013-04-01 06:46:56 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: lijin

Created: 2013-04-01 06:46:56 UTC

Size: 13.59 KB

patch

obsolete

>
>Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
>Copyright (c) Microsoft Corporation. All rights reserved.
>
>
>Loading Dump File [C:\Users\Administrator\Desktop\Memory.dmp]
>Kernel Bitmap Dump File: Only kernel address space is available
>
>Symbol search path is: SRV*C:\symbols\*http://msdl.microsoft.com/download/symbols
>Executable search path is: 
>Windows 8 Kernel Version 9200 MP (4 procs) Free x64
>Product: WinNt, suite: TerminalServer SingleUserTS
>Built by: 9200.16384.amd64fre.win8_rtm.120725-1247
>Machine Name:
>Kernel base = 0xfffff801`32406000 PsLoadedModuleList = 0xfffff801`326d0a60
>Debug session time: Mon Apr  1 05:40:32.784 2013 (UTC - 7:00)
>System Uptime: 0 days 0:00:03.412
>Loading Kernel Symbols
>...............................................................
>.............................................
>Loading User Symbols
>
>Loading unloaded module list
>.....
>*******************************************************************************
>*                                                                             *
>*                        Bugcheck Analysis                                    *
>*                                                                             *
>*******************************************************************************
>
>Use !analyze -v to get detailed debugging information.
>
>BugCheck D1, {fffff88004033000, 8, 1, fffff88003f3f0d0}
>
>*** ERROR: Module load completed but symbols could not be loaded for vioscsi.sys
>Probably caused by : vioscsi.sys ( vioscsi+20d0 )
>
>Followup: MachineOwner
>---------
>
>3: kd> .reload
>Loading Kernel Symbols
>...............................................................
>.............................................
>Loading User Symbols
>
>Loading unloaded module list
>.....
>3: 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: fffff88004033000, memory referenced
>Arg2: 0000000000000008, IRQL
>Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
>Arg4: fffff88003f3f0d0, address which referenced memory
>
>Debugging Details:
>------------------
>
>*** ERROR: Module load completed but symbols could not be loaded for vioscsi.sys
>
>WRITE_ADDRESS:  fffff88004033000 
>
>CURRENT_IRQL:  8
>
>FAULTING_IP: 
>vioscsi+20d0
>fffff880`03f3f0d0 488911          mov     qword ptr [rcx],rdx
>
>DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
>
>BUGCHECK_STR:  AV
>
>PROCESS_NAME:  System
>
>TRAP_FRAME:  fffff88002d47370 -- (.trap 0xfffff88002d47370)
>NOTE: The trap frame does not contain all registers.
>Some register values may be zeroed or incorrect.
>rax=fffff88004033000 rbx=0000000000000000 rcx=fffff88004033000
>rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
>rip=fffff88003f3f0d0 rsp=fffff88002d47508 rbp=fffffa80051aa4f0
> r8=0000000000000000  r9=0000000000000005 r10=fffff88002d47540
>r11=fffff88002d474b0 r12=0000000000000000 r13=0000000000000000
>r14=0000000000000000 r15=0000000000000000
>iopl=0         nv up ei pl nz na po nc
>vioscsi+0x20d0:
>fffff880`03f3f0d0 488911          mov     qword ptr [rcx],rdx ds:fffff880`04033000=????????????????
>Resetting default scope
>
>LOCK_ADDRESS:  fffff801326dc740 -- (!locks fffff801326dc740)
>
>Resource @ nt!PiEngineLock (0xfffff801326dc740)    Exclusively owned
>    Contention Count = 1
>    NumberOfExclusiveWaiters = 1
>     Threads: fffffa800371c500-01<*> 
>     Threads Waiting On Exclusive Access:
>              fffffa8003718040       
>
>1 total locks, 1 locks currently held
>
>PNP_TRIAGE: 
>	Lock address  : 0xfffff801326dc740
>	Thread Count  : 1
>	Thread address: 0xfffffa800371c500
>	Thread wait   : 0xda
>
>LAST_CONTROL_TRANSFER:  from fffff80132480369 to fffff80132481040
>
>STACK_TEXT:  
>fffff880`02d47228 fffff801`32480369 : 00000000`0000000a fffff880`04033000 00000000`00000008 00000000`00000001 : nt!KeBugCheckEx
>fffff880`02d47230 fffff801`3247ebe0 : 00000000`00000001 fffff880`04033000 00000000`00000000 fffff880`02d47370 : nt!KiBugCheckDispatch+0x69
>fffff880`02d47370 fffff880`03f3f0d0 : fffff880`03f3e2b6 00000000`00000000 fffff880`03f51826 00000000`00000001 : nt!KiPageFault+0x260
>fffff880`02d47508 fffff880`03f3e2b6 : 00000000`00000000 fffff880`03f51826 00000000`00000001 fffffa80`052272c8 : vioscsi+0x20d0
>fffff880`02d47510 fffff880`03f3ecf3 : fffff880`00005000 fffffa80`058eeab0 fffffa80`051aa4f0 fffff880`02d47564 : vioscsi+0x12b6
>fffff880`02d47540 fffff880`03f53c04 : fffffa80`052272c8 00000000`00000000 ffffb4d1`5c9cb575 00000000`00000040 : vioscsi+0x1cf3
>fffff880`02d47570 fffff880`03f519cb : fffffa80`052271a0 00000000`00000040 fffffa80`052272c8 00000000`00000040 : storport!RaCallMiniportHwInitialize+0x28
>fffff880`02d475a0 fffff880`03f51e96 : fffffa80`0518e150 00000000`00000040 fffffa80`052271a0 fffff880`03f4d1a1 : storport!RaidAdapterStartMiniport+0x187
>fffff880`02d47600 fffff880`03f524ec : fffffa80`051aa4f0 fffff880`02d476c0 00000000`00000000 fffffa80`052271a0 : storport!RaidAdapterStartDeviceIrp+0x14e
>fffff880`02d47650 fffff880`03f56f68 : fffff880`02d477a0 fffff801`3250bb2c fffffa80`051aa4f0 fffffa80`03bfa880 : storport!RaidAdapterPnpIrp+0x1ac
>fffff880`02d476f0 fffff801`3288f832 : fffffa80`051aa4f0 fffffa80`05380150 fffffa80`05227050 fffff880`02acf180 : storport!RaDriverPnpIrp+0x94
>fffff880`02d47730 fffff801`3250b5d6 : fffffa80`03bfa880 fffff880`02d477d9 00000000`00000000 fffffa80`03bf9490 : nt!PnpAsynchronousCall+0xce
>fffff880`02d47770 fffff801`32882cb7 : fffffa80`03bf9490 fffffa80`03bf9490 fffffa80`05380150 fffff801`327aa2fb : nt!PnpStartDevice+0xc2
>fffff880`02d47840 fffff801`32882b2f : fffffa80`03bf9490 fffffa80`03bf9490 00000000`00000000 fffff801`3248a700 : nt!PnpStartDeviceNode+0x147
>fffff880`02d47910 fffff801`3288f336 : fffffa80`03bf9490 00000000`00000001 00000000`00000001 00000000`00000000 : nt!PipProcessStartPhase1+0x5f
>fffff880`02d47940 fffff801`32902c07 : fffffa80`0370d250 00000000`00000001 fffff801`32689f00 fffffa80`050756b0 : nt!PipProcessDevNodeTree+0x3e2
>fffff880`02d47bc0 fffff801`3250c81f : fffffa01`00000003 00000000`00000000 fffff801`326d96e0 00000001`32706e50 : nt!PiProcessStartSystemDevices+0x87
>fffff880`02d47c10 fffff801`324b9391 : fffffa80`0371c500 fffff801`3250c4bc fffff801`326d96e0 fffff801`3248a700 : nt!PnpDeviceActionWorker+0x363
>fffff880`02d47cc0 fffff801`32428521 : 8d483548`8d442b75 00000000`00000080 fffff801`324b9250 fffffa80`0371c500 : nt!ExpWorkerThread+0x142
>fffff880`02d47d50 fffff801`32466dd6 : fffff801`326fc180 fffffa80`0371c500 fffff801`32756880 fffffa80`036891c0 : nt!PspSystemThreadStartup+0x59
>fffff880`02d47da0 00000000`00000000 : fffff880`02d48000 fffff880`02d42000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
>
>
>STACK_COMMAND:  kb
>
>FOLLOWUP_IP: 
>vioscsi+20d0
>fffff880`03f3f0d0 488911          mov     qword ptr [rcx],rdx
>
>SYMBOL_STACK_INDEX:  3
>
>SYMBOL_NAME:  vioscsi+20d0
>
>FOLLOWUP_NAME:  MachineOwner
>
>MODULE_NAME: vioscsi
>
>IMAGE_NAME:  vioscsi.sys
>
>DEBUG_FLR_IMAGE_TIMESTAMP:  515821f8
>
>FAILURE_BUCKET_ID:  AV_vioscsi+20d0
>
>BUCKET_ID:  AV_vioscsi+20d0
>
>Followup: MachineOwner
>---------
>
>3: kd> .reload
>Loading Kernel Symbols
>...............................................................
>.............................................
>Loading User Symbols
>
>Loading unloaded module list
>.....
>3: 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: fffff88004033000, memory referenced
>Arg2: 0000000000000008, IRQL
>Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
>Arg4: fffff88003f3f0d0, address which referenced memory
>
>Debugging Details:
>------------------
>
>*** ERROR: Module load completed but symbols could not be loaded for vioscsi.sys
>
>WRITE_ADDRESS:  fffff88004033000 
>
>CURRENT_IRQL:  8
>
>FAULTING_IP: 
>vioscsi+20d0
>fffff880`03f3f0d0 488911          mov     qword ptr [rcx],rdx
>
>DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
>
>BUGCHECK_STR:  AV
>
>PROCESS_NAME:  System
>
>TRAP_FRAME:  fffff88002d47370 -- (.trap 0xfffff88002d47370)
>NOTE: The trap frame does not contain all registers.
>Some register values may be zeroed or incorrect.
>rax=fffff88004033000 rbx=0000000000000000 rcx=fffff88004033000
>rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
>rip=fffff88003f3f0d0 rsp=fffff88002d47508 rbp=fffffa80051aa4f0
> r8=0000000000000000  r9=0000000000000005 r10=fffff88002d47540
>r11=fffff88002d474b0 r12=0000000000000000 r13=0000000000000000
>r14=0000000000000000 r15=0000000000000000
>iopl=0         nv up ei pl nz na po nc
>vioscsi+0x20d0:
>fffff880`03f3f0d0 488911          mov     qword ptr [rcx],rdx ds:fffff880`04033000=????????????????
>Resetting default scope
>
>LOCK_ADDRESS:  fffff801326dc740 -- (!locks fffff801326dc740)
>
>Resource @ nt!PiEngineLock (0xfffff801326dc740)    Exclusively owned
>    Contention Count = 1
>    NumberOfExclusiveWaiters = 1
>     Threads: fffffa800371c500-01<*> 
>     Threads Waiting On Exclusive Access:
>              fffffa8003718040       
>
>1 total locks, 1 locks currently held
>
>PNP_TRIAGE: 
>	Lock address  : 0xfffff801326dc740
>	Thread Count  : 1
>	Thread address: 0xfffffa800371c500
>	Thread wait   : 0xda
>
>LAST_CONTROL_TRANSFER:  from fffff80132480369 to fffff80132481040
>
>STACK_TEXT:  
>fffff880`02d47228 fffff801`32480369 : 00000000`0000000a fffff880`04033000 00000000`00000008 00000000`00000001 : nt!KeBugCheckEx
>fffff880`02d47230 fffff801`3247ebe0 : 00000000`00000001 fffff880`04033000 00000000`00000000 fffff880`02d47370 : nt!KiBugCheckDispatch+0x69
>fffff880`02d47370 fffff880`03f3f0d0 : fffff880`03f3e2b6 00000000`00000000 fffff880`03f51826 00000000`00000001 : nt!KiPageFault+0x260
>fffff880`02d47508 fffff880`03f3e2b6 : 00000000`00000000 fffff880`03f51826 00000000`00000001 fffffa80`052272c8 : vioscsi+0x20d0
>fffff880`02d47510 fffff880`03f3ecf3 : fffff880`00005000 fffffa80`058eeab0 fffffa80`051aa4f0 fffff880`02d47564 : vioscsi+0x12b6
>fffff880`02d47540 fffff880`03f53c04 : fffffa80`052272c8 00000000`00000000 ffffb4d1`5c9cb575 00000000`00000040 : vioscsi+0x1cf3
>fffff880`02d47570 fffff880`03f519cb : fffffa80`052271a0 00000000`00000040 fffffa80`052272c8 00000000`00000040 : storport!RaCallMiniportHwInitialize+0x28
>fffff880`02d475a0 fffff880`03f51e96 : fffffa80`0518e150 00000000`00000040 fffffa80`052271a0 fffff880`03f4d1a1 : storport!RaidAdapterStartMiniport+0x187
>fffff880`02d47600 fffff880`03f524ec : fffffa80`051aa4f0 fffff880`02d476c0 00000000`00000000 fffffa80`052271a0 : storport!RaidAdapterStartDeviceIrp+0x14e
>fffff880`02d47650 fffff880`03f56f68 : fffff880`02d477a0 fffff801`3250bb2c fffffa80`051aa4f0 fffffa80`03bfa880 : storport!RaidAdapterPnpIrp+0x1ac
>fffff880`02d476f0 fffff801`3288f832 : fffffa80`051aa4f0 fffffa80`05380150 fffffa80`05227050 fffff880`02acf180 : storport!RaDriverPnpIrp+0x94
>fffff880`02d47730 fffff801`3250b5d6 : fffffa80`03bfa880 fffff880`02d477d9 00000000`00000000 fffffa80`03bf9490 : nt!PnpAsynchronousCall+0xce
>fffff880`02d47770 fffff801`32882cb7 : fffffa80`03bf9490 fffffa80`03bf9490 fffffa80`05380150 fffff801`327aa2fb : nt!PnpStartDevice+0xc2
>fffff880`02d47840 fffff801`32882b2f : fffffa80`03bf9490 fffffa80`03bf9490 00000000`00000000 fffff801`3248a700 : nt!PnpStartDeviceNode+0x147
>fffff880`02d47910 fffff801`3288f336 : fffffa80`03bf9490 00000000`00000001 00000000`00000001 00000000`00000000 : nt!PipProcessStartPhase1+0x5f
>fffff880`02d47940 fffff801`32902c07 : fffffa80`0370d250 00000000`00000001 fffff801`32689f00 fffffa80`050756b0 : nt!PipProcessDevNodeTree+0x3e2
>fffff880`02d47bc0 fffff801`3250c81f : fffffa01`00000003 00000000`00000000 fffff801`326d96e0 00000001`32706e50 : nt!PiProcessStartSystemDevices+0x87
>fffff880`02d47c10 fffff801`324b9391 : fffffa80`0371c500 fffff801`3250c4bc fffff801`326d96e0 fffff801`3248a700 : nt!PnpDeviceActionWorker+0x363
>fffff880`02d47cc0 fffff801`32428521 : 8d483548`8d442b75 00000000`00000080 fffff801`324b9250 fffffa80`0371c500 : nt!ExpWorkerThread+0x142
>fffff880`02d47d50 fffff801`32466dd6 : fffff801`326fc180 fffffa80`0371c500 fffff801`32756880 fffffa80`036891c0 : nt!PspSystemThreadStartup+0x59
>fffff880`02d47da0 00000000`00000000 : fffff880`02d48000 fffff880`02d42000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
>
>
>STACK_COMMAND:  kb
>
>FOLLOWUP_IP: 
>vioscsi+20d0
>fffff880`03f3f0d0 488911          mov     qword ptr [rcx],rdx
>
>SYMBOL_STACK_INDEX:  3
>
>SYMBOL_NAME:  vioscsi+20d0
>
>FOLLOWUP_NAME:  MachineOwner
>
>MODULE_NAME: vioscsi
>
>IMAGE_NAME:  vioscsi.sys
>
>DEBUG_FLR_IMAGE_TIMESTAMP:  515821f8
>
>FAILURE_BUCKET_ID:  AV_vioscsi+20d0
>
>BUCKET_ID:  AV_vioscsi+20d0
>
>Followup: MachineOwner
>---------
>

Actions: View

Attachments on bug 946992: 730205 | 730679