Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\121910-23868-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a02000 PsLoadedModuleList = 0xfffff800`02c3fe50
Debug session time: Sun Dec 19 09:28:25.402 2010 (UTC - 5:00)
System Uptime: 0 days 13:32:50.681
Loading Kernel Symbols
..
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
.............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {424c5324968, 2, 0, fffff880011160ed}
*** WARNING: Unable to verify timestamp for nvstor.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor.sys
Probably caused by : storport.sys ( storport!StorPortNotification+3d )
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: 00000424c5324968, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880011160ed, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002caa0e0
00000424c5324968
CURRENT_IRQL: 2
FAULTING_IP:
storport!StorPortNotification+3d
fffff880`011160ed 488b4268 mov rax,qword ptr [rdx+68h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: csrss.exe
TRAP_FRAME: fffff80000ba2b00 -- (.trap 0xfffff80000ba2b00)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8800a1b46b0 rbx=0000000000000000 rcx=0000000000000000
rdx=00000424c5324900 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880011160ed rsp=fffff80000ba2c90 rbp=fffffa8004634220
r8=fffff8800a1b46b0 r9=fffff80000ba2d20 r10=fffffa80046e2008
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
storport!StorPortNotification+0x3d:
fffff880`011160ed 488b4268 mov rax,qword ptr [rdx+68h] ds:2000:00000424`c5324968=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002a73469 to fffff80002a73f00
STACK_TEXT:
fffff800`00ba29b8 fffff800`02a73469 : 00000000`0000000a 00000424`c5324968 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00ba29c0 fffff800`02a720e0 : fffffa80`071a3000 fffffa80`046db600 fffffa80`0767f010 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba2b00 fffff880`011160ed : 00000000`00000004 00000424`c530c0ae fffffa80`046e2000 00000000`00000004 : nt!KiPageFault+0x260
fffff800`00ba2c90 fffff880`011029ed : 00000424`c5325a9a fffffa80`046e2008 fffff880`0a1b46b0 00000000`00000000 : storport!StorPortNotification+0x3d
fffff800`00ba2d10 00000424`c5325a9a : fffffa80`046e2008 fffff880`0a1b46b0 00000000`00000000 00000000`00000000 : nvstor+0x189ed
fffff800`00ba2d18 fffffa80`046e2008 : fffff880`0a1b46b0 00000000`00000000 00000000`00000000 fffff880`010f22f1 : 0x424`c5325a9a
fffff800`00ba2d20 fffff880`0a1b46b0 : 00000000`00000000 00000000`00000000 fffff880`010f22f1 fffff880`0370b380 : 0xfffffa80`046e2008
fffff800`00ba2d28 00000000`00000000 : 00000000`00000000 fffff880`010f22f1 fffff880`0370b380 00000000`00000000 : 0xfffff880`0a1b46b0
STACK_COMMAND: kb
FOLLOWUP_IP:
storport!StorPortNotification+3d
fffff880`011160ed 488b4268 mov rax,qword ptr [rdx+68h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: storport!StorPortNotification+3d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: storport
IMAGE_NAME: storport.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcace
FAILURE_BUCKET_ID: X64_0xD1_storport!StorPortNotification+3d
BUCKET_ID: X64_0xD1_storport!StorPortNotification+3d
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\121810-23946-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a07000 PsLoadedModuleList = 0xfffff800`02c44e50
Debug session time: Sat Dec 18 19:27:20.896 2010 (UTC - 5:00)
System Uptime: 0 days 0:25:32.175
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : storport.sys ( storport!RaidpAdapterDpcRoutine+4d )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (Win32) 0 (0) - .
FAULTING_IP:
+6362626438326530
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
BUGCHECK_STR: 0x1E_0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: lpremove.exe
CURRENT_IRQL: 2
EXCEPTION_RECORD: fffff800054c4c88 -- (.exr 0xfffff800054c4c88)
ExceptionAddress: fffff880010028cd (storport!RaidpAdapterDpcRoutine+0x000000000000004d)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff800054c4d30 -- (.trap 0xfffff800054c4d30)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800772db30 rbx=0000000000000000 rcx=fffffa800772db10
rdx=fffffa800772db10 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880010028cd rsp=fffff800054c4ec0 rbp=fffffa8004936060
r8=fffffa800772db30 r9=0000000000000000 r10=fffffa8004936290
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
storport!RaidpAdapterDpcRoutine+0x4d:
fffff880`010028cd ff9250020000 call qword ptr [rdx+250h] ds:4ea0:fffffa80`0772dd60=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002a70c2e to fffff80002a78ed0
STACK_TEXT:
fffff800`054c3d68 fffff800`02a70c2e : fffffa80`00000000 fffffa80`06edac88 fffff800`054c44e0 fffff800`02aa5e28 : nt!KeBugCheck
fffff800`054c3d70 fffff800`02a9ebed : fffff800`02c85c24 fffff800`02bbea3c fffff800`02a07000 fffff800`054c4c88 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`054c3da0 fffff800`02aa6250 : fffff800`02bc6a88 fffff800`054c3e18 fffff800`054c4c88 fffff800`02a07000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`054c3dd0 fffff800`02ab31b5 : fffff800`054c4c88 fffff800`054c44e0 fffff800`00000000 fffffa80`049361b0 : nt!RtlDispatchException+0x410
fffff800`054c44b0 fffff800`02a78542 : fffff800`054c4c88 00000000`00000000 fffff800`054c4d30 fffff780`00000320 : nt!KiDispatchException+0x135
fffff800`054c4b50 fffff800`02a76e4a : 00000000`00000000 fffff880`011a32f1 fffff880`03709380 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff800`054c4d30 fffff880`010028cd : fffff800`02bf1e80 fffff880`011b13dd 00000000`ffffffed fffffa80`04936060 : nt!KiGeneralProtectionFault+0x10a
fffff800`054c4ec0 fffff800`02a845dc : fffff800`02bf1e80 fffffa80`00000000 fffffa80`04936128 00000000`000000a1 : storport!RaidpAdapterDpcRoutine+0x4d
fffff800`054c4f00 fffff800`02a7f065 : 00000000`00000000 fffffa80`042beb60 00000000`00000000 fffff880`01002880 : nt!KiRetireDpcList+0x1bc
fffff800`054c4fb0 fffff800`02a7ee7c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`0949b450 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
STACK_COMMAND: kb
FOLLOWUP_IP:
storport!RaidpAdapterDpcRoutine+4d
fffff880`010028cd ff9250020000 call qword ptr [rdx+250h]
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: storport!RaidpAdapterDpcRoutine+4d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: storport
IMAGE_NAME: storport.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcace
FAILURE_BUCKET_ID: X64_0x1E_0_storport!RaidpAdapterDpcRoutine+4d
BUCKET_ID: X64_0x1E_0_storport!RaidpAdapterDpcRoutine+4d
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\121810-23275-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a65000 PsLoadedModuleList = 0xfffff800`02ca2e50
Debug session time: Sat Dec 18 19:54:14.776 2010 (UTC - 5:00)
System Uptime: 0 days 0:25:31.664
Loading Kernel Symbols
..
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
.............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {357bff05d68, 2, 0, fffff8800106e0ed}
*** WARNING: Unable to verify timestamp for nvstor.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor.sys
Probably caused by : storport.sys ( storport!StorPortNotification+3d )
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: 00000357bff05d68, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800106e0ed, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0d0e0
00000357bff05d68
CURRENT_IRQL: 2
FAULTING_IP:
storport!StorPortNotification+3d
fffff880`0106e0ed 488b4268 mov rax,qword ptr [rdx+68h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff88002f92b00 -- (.trap 0xfffff88002f92b00)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880076286b0 rbx=0000000000000000 rcx=0000000000000000
rdx=00000357bff05d00 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800106e0ed rsp=fffff88002f92c90 rbp=fffffa8004616220
r8=fffff880076286b0 r9=fffff88002f92d20 r10=fffffa80046c3008
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
storport!StorPortNotification+0x3d:
fffff880`0106e0ed 488b4268 mov rax,qword ptr [rdx+68h] ds:3000:00000357`bff05d68=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002ad6469 to fffff80002ad6f00
STACK_TEXT:
fffff880`02f929b8 fffff800`02ad6469 : 00000000`0000000a 00000357`bff05d68 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f929c0 fffff800`02ad50e0 : fffffa80`04988190 fffffa80`046bd600 00000000`00000002 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02f92b00 fffff880`0106e0ed : 00000000`00000004 00000357`bfef4ead fffffa80`046c3000 00000000`00000004 : nt!KiPageFault+0x260
fffff880`02f92c90 fffff880`0105a9ed : 00000357`bff1007c fffffa80`046c3008 fffff880`076286b0 00000000`00000000 : storport!StorPortNotification+0x3d
fffff880`02f92d10 00000357`bff1007c : fffffa80`046c3008 fffff880`076286b0 00000000`00000000 00000000`00000000 : nvstor+0x189ed
fffff880`02f92d18 fffffa80`046c3008 : fffff880`076286b0 00000000`00000000 00000000`00000000 fffff880`0104a2f1 : 0x357`bff1007c
fffff880`02f92d20 fffff880`076286b0 : 00000000`00000000 00000000`00000000 fffff880`0104a2f1 fffff880`0370c380 : 0xfffffa80`046c3008
fffff880`02f92d28 00000000`00000000 : 00000000`00000000 fffff880`0104a2f1 fffff880`0370c380 00000000`00000000 : 0xfffff880`076286b0
STACK_COMMAND: kb
FOLLOWUP_IP:
storport!StorPortNotification+3d
fffff880`0106e0ed 488b4268 mov rax,qword ptr [rdx+68h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: storport!StorPortNotification+3d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: storport
IMAGE_NAME: storport.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcace
FAILURE_BUCKET_ID: X64_0xD1_storport!StorPortNotification+3d
BUCKET_ID: X64_0xD1_storport!StorPortNotification+3d
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\121910-27721-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a04000 PsLoadedModuleList = 0xfffff800`02c41e50
Debug session time: Sun Dec 19 14:52:50.973 2010 (UTC - 5:00)
System Uptime: 0 days 0:01:42.252
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
Unable to load image \SystemRoot\system32\DRIVERS\nvstor.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvstor.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor.sys
Probably caused by : storport.sys ( storport!StorPortNotification+46 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (Win32) 0 (0) - .
FAULTING_IP:
+6362626438326530
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
BUGCHECK_STR: 0x1E_0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: wow_helper.exe
CURRENT_IRQL: 2
EXCEPTION_RECORD: fffff80000ba2a58 -- (.exr 0xfffff80000ba2a58)
ExceptionAddress: fffff880010d00f6 (storport!StorPortNotification+0x0000000000000046)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff80000ba2b00 -- (.trap 0xfffff80000ba2b00)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=02b917eb0004fe31 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff80002a718e3 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880010d00f6 rsp=fffff80000ba2c90 rbp=fffffa80048e1220
r8=fffff880028eb6b0 r9=fffff80000ba2d20 r10=fffffa8004926008
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
storport!StorPortNotification+0x46:
fffff880`010d00f6 c6808d000000ab mov byte ptr [rax+8Dh],0ABh ds:6000:02b917eb`0004febe=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002a6dc2e to fffff80002a75ed0
STACK_TEXT:
fffff800`00ba1b38 fffff800`02a6dc2e : fffffa80`06ec34f0 fffffa80`04fb91a0 fffff800`00ba22b0 fffff800`02aa2e28 : nt!KeBugCheck
fffff800`00ba1b40 fffff800`02a9bbed : fffff800`02c82c24 fffff800`02bbba3c fffff800`02a04000 fffff800`00ba2a58 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00ba1b70 fffff800`02aa3250 : fffff800`02bc3a88 fffff800`00ba1be8 fffff800`00ba2a58 fffff800`02a04000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00ba1ba0 fffff800`02ab01b5 : fffff800`00ba2a58 fffff800`00ba22b0 fffff800`00000000 fffff880`028eb6b0 : nt!RtlDispatchException+0x410
fffff800`00ba2280 fffff800`02a75542 : fffff800`00ba2a58 fffffa80`048d81b0 fffff800`00ba2b00 fffffa80`04926008 : nt!KiDispatchException+0x135
fffff800`00ba2920 fffff800`02a73e4a : fffffa80`04bf8190 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff800`00ba2b00 fffff880`010d00f6 : 00000000`00000004 00000039`58d24133 fffffa80`04926000 00000000`00000004 : nt!KiGeneralProtectionFault+0x10a
fffff800`00ba2c90 fffff880`00c429ed : 00000039`58d3ca48 fffffa80`04926008 fffff880`028eb6b0 00000000`00000000 : storport!StorPortNotification+0x46
fffff800`00ba2d10 00000039`58d3ca48 : fffffa80`04926008 fffff880`028eb6b0 00000000`00000000 00000000`00000000 : nvstor+0x189ed
fffff800`00ba2d18 fffffa80`04926008 : fffff880`028eb6b0 00000000`00000000 00000000`00000000 fffff880`00c322f1 : 0x39`58d3ca48
fffff800`00ba2d20 fffff880`028eb6b0 : 00000000`00000000 00000000`00000000 fffff880`00c322f1 fffff880`0370c380 : 0xfffffa80`04926008
fffff800`00ba2d28 00000000`00000000 : 00000000`00000000 fffff880`00c322f1 fffff880`0370c380 00000000`00000000 : 0xfffff880`028eb6b0
STACK_COMMAND: kb
FOLLOWUP_IP:
storport!StorPortNotification+46
fffff880`010d00f6 c6808d000000ab mov byte ptr [rax+8Dh],0ABh
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: storport!StorPortNotification+46
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: storport
IMAGE_NAME: storport.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcace
FAILURE_BUCKET_ID: X64_0x1E_0_storport!StorPortNotification+46
BUCKET_ID: X64_0x1E_0_storport!StorPortNotification+46
Followup: MachineOwner
---------