Code:
-
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [K:\BSODDmpFiles\Sabrac\Windows_NT6_BSOD_jcgriff2\013012-32011-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c14000 PsLoadedModuleList = 0xfffff800`02e59670
Debug session time: Mon Jan 30 07:38:51.879 2012 (GMT-7)
System Uptime: 0 days 0:07:35.846
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 : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
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) - The operation completed successfully.
FAULTING_IP:
+0
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: System
CURRENT_IRQL: 0
EXCEPTION_RECORD: fffff80000b9ca18 -- (.exr 0xfffff80000b9ca18)
ExceptionAddress: fffff8000322d4f9 (hal!HalpKInterruptHeap+0x00000000000004f9)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff80000b9cac0 -- (.trap 0xfffff80000b9cac0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000001df00 rbx=0000000000000000 rcx=fffffa8003a51f20
rdx=fffffa8003a4d5a8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000322d4f9 rsp=fffff80000b9cc58 rbp=fffff8000321d460
r8=0000000000000000 r9=000000003a4bcf49 r10=000000000001cbbe
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl zr na po nc
hal!HalpKInterruptHeap+0x4f9:
fffff800`0322d4f9 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c885fe to fffff80002c90c10
STACK_TEXT:
fffff800`00b9baf8 fffff800`02c885fe : 00000000`00000000 00000000`00000000 fffff800`00b9c270 fffff800`02cbc830 : nt!KeBugCheck
fffff800`00b9bb00 fffff800`02cbc4fd : fffff800`02e9a488 fffff800`02dd8c8c fffff800`02c14000 fffff800`00b9ca18 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9bb30 fffff800`02cbb2d5 : fffff800`02ddb0fc fffff800`00b9bba8 fffff800`00b9ca18 fffff800`02c14000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9bb60 fffff800`02ccc361 : fffff800`00b9ca18 fffff800`00b9c270 fffff800`00000000 00000000`00000001 : nt!RtlDispatchException+0x415
fffff800`00b9c240 fffff800`02c902c2 : fffff800`00b9ca18 00000000`00000000 fffff800`00b9cac0 fffff800`02e06e80 : nt!KiDispatchException+0x135
fffff800`00b9c8e0 fffff800`02c8ebca : 00000000`00000001 fffff800`03207895 fffff800`0322d460 fffff800`00b9cb80 : nt!KiExceptionDispatch+0xc2
fffff800`00b9cac0 fffff800`0322d4f9 : 00000000`00000000 00000000`0001df00 fffff880`043667f2 00000000`00000010 : nt!KiGeneralProtectionFault+0x10a
fffff800`00b9cc58 00000000`00000000 : 00000000`0001df00 fffff880`043667f2 00000000`00000010 00000000`00000246 : hal!HalpKInterruptHeap+0x4f9
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiKernelCalloutExceptionHandler+e
fffff800`02c885fe 90 nop
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KiKernelCalloutExceptionHandler+e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3
FAILURE_BUCKET_ID: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
BUCKET_ID: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
Followup: MachineOwner
---------
-
Loading Dump File [K:\BSODDmpFiles\Sabrac\Windows_NT6_BSOD_jcgriff2\012812-21325-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c65000 PsLoadedModuleList = 0xfffff800`02eaa670
Debug session time: Sat Jan 28 21:39:43.249 2012 (GMT-7)
System Uptime: 0 days 1:17:47.825
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck FE, {5, fffffa80051f61a0, 10024397, fffffa80040e7e68}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
using a physical memory address that was not allocated by
the USBport driver.
Arg2: fffffa80051f61a0, Device extension pointer of the host controller
Arg3: 0000000010024397, PCI Vendor,Product id for the controller
Arg4: fffffa80040e7e68, Pointer to Endpoint data structure
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xFE
PROCESS_NAME: Wow.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002ce1c40
STACK_TEXT:
fffff880`009b0d18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: ZEROED_STACK
Followup: MachineOwner
---------
-
Loading Dump File [K:\BSODDmpFiles\Sabrac\Windows_NT6_BSOD_jcgriff2\012812-20186-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c15000 PsLoadedModuleList = 0xfffff800`02e5a670
Debug session time: Sat Jan 28 09:57:48.984 2012 (GMT-7)
System Uptime: 0 days 0:16:09.950
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff88004b00000, 8, fffff88004b00000, 0}
Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4611f )
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: fffff88004b00000, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff88004b00000, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec4100
fffff88004b00000
FAULTING_IP:
+0
fffff880`04b00000 ?? ???
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: fffff88002e14520 -- (.trap 0xfffff88002e14520)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800579b000 rbx=0000000000000000 rcx=000000000001467d
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004b00000 rsp=fffff88002e146b0 rbp=0000000000000080
r8=fffff78000000000 r9=0000000000000000 r10=fffffa8003a12400
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
fffff880`04b00000 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c3d9fc to fffff80002c91c40
STACK_TEXT:
fffff880`02e143b8 fffff800`02c3d9fc : 00000000`00000050 fffff880`04b00000 00000000`00000008 fffff880`02e14520 : nt!KeBugCheckEx
fffff880`02e143c0 fffff800`02c8fd6e : 00000000`00000008 fffff880`04b00000 fffff880`02e14c00 fffffa80`0606db60 : nt! ?? ::FNODOBFM::`string'+0x4611f
fffff880`02e14520 fffff880`04b00000 : fffffa80`0579b000 01ccdddd`f7161463 fffff880`02e146f8 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`02e146b0 fffffa80`0579b000 : 01ccdddd`f7161463 fffff880`02e146f8 00000000`00000000 00000000`00000000 : 0xfffff880`04b00000
fffff880`02e146b8 01ccdddd`f7161463 : fffff880`02e146f8 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`0579b000
fffff880`02e146c0 fffff880`02e146f8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1ccdddd`f7161463
fffff880`02e146c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`02e146f8
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+4611f
fffff800`02c3d9fc cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+4611f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3
FAILURE_BUCKET_ID: X64_0x50_nt!_??_::FNODOBFM::_string_+4611f
BUCKET_ID: X64_0x50_nt!_??_::FNODOBFM::_string_+4611f
Followup: MachineOwner
---------
-
Loading Dump File [K:\BSODDmpFiles\Sabrac\Windows_NT6_BSOD_jcgriff2\012812-21918-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c0b000 PsLoadedModuleList = 0xfffff800`02e50670
Debug session time: Sat Jan 28 09:38:13.043 2012 (GMT-7)
System Uptime: 0 days 0:00:31.009
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff80002c99640, 0, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt!ObFastReferenceObject+10 )
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002c99640, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!ObFastReferenceObject+10
fffff800`02c99640 4c8b01 mov r8,qword ptr [rcx]
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eba100
ffffffffffffffff
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: nvvsvc.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002cd3588 to fffff80002c87c40
STACK_TEXT:
fffff880`03fd9e48 fffff800`02cd3588 : 00000000`0000001e ffffffff`c0000005 fffff800`02c99640 00000000`00000000 : nt!KeBugCheckEx
fffff880`03fd9e50 fffff800`02c872c2 : fffff880`03fda628 00000000`00000564 fffff880`03fda6d0 fffffa80`04587398 : nt! ?? ::FNODOBFM::`string'+0x4977d
fffff880`03fda4f0 fffff800`02c85bca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`03fda6d0 fffff800`02c99640 : fffff683`ff7efc00 fffffa80`06223ec8 00000000`79402025 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff880`03fda860 fffff800`02cf2a98 : 00000000`000007c6 00000000`00000564 fffff700`01080000 00000000`00000000 : nt!ObFastReferenceObject+0x10
fffff880`03fda890 fffff800`02ca653f : 7c600000`79402025 00000000`79402121 fffffa80`00000001 20206553`02c8cf32 : nt! ?? ::FNODOBFM::`string'+0x2a15e
fffff880`03fda920 fffff800`02ca5053 : 00000000`000a39cd 000007fe`fdf8072c fffff683`ff7efc00 fffffa80`06223ec8 : nt!MiResolveProtoPteFault+0x1cf
fffff880`03fda9b0 fffff800`02c94f19 : 00000000`00000000 000007fe`fdf8072c 00000000`000000ff 00000000`00000000 : nt!MiDispatchFault+0x1c3
fffff880`03fdaac0 fffff800`02c85d6e : 00000000`00000008 000007fe`fdf8072c 00000000`0033b701 00000000`00398c98 : nt!MmAccessFault+0x359
fffff880`03fdac20 000007fe`fdf8072c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0119ee50 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fdf8072c
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ObFastReferenceObject+10
fffff800`02c99640 4c8b01 mov r8,qword ptr [rcx]
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: nt!ObFastReferenceObject+10
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3
FAILURE_BUCKET_ID: X64_0x1E_nt!ObFastReferenceObject+10
BUCKET_ID: X64_0x1E_nt!ObFastReferenceObject+10
Followup: MachineOwner
---------
-
Loading Dump File [K:\BSODDmpFiles\Sabrac\Windows_NT6_BSOD_jcgriff2\012712-35864-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c5e000 PsLoadedModuleList = 0xfffff800`02ea3670
Debug session time: Fri Jan 27 17:04:30.461 2012 (GMT-7)
System Uptime: 0 days 3:26:47.427
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41790, fffffa80010aa900, ffff, 0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::Free+a2 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa80010aa900
Arg3: 000000000000ffff
Arg4: 0000000000000000
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_41790
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002d4a150 to fffff80002cdac40
STACK_TEXT:
fffff880`038d5768 fffff800`02d4a150 : 00000000`0000001a 00000000`00041790 fffffa80`010aa900 00000000`0000ffff : nt!KeBugCheckEx
fffff880`038d5770 fffff800`02cc80ff : fffffa80`00000000 00000000`04373fff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x36024
fffff880`038d5930 fffff800`02cd9ed3 : ffffffff`ffffffff fffff8a0`08b08d78 fffff8a0`08b08da0 fffffa80`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`038d5a30 fffff800`02cd6470 : fffff880`11dcf4b2 fffff8a0`0efb2390 fffffa80`06528060 fffffa80`06538db0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`038d5bc8 fffff880`11dcf4b2 : fffff8a0`0efb2390 fffffa80`06528060 fffffa80`06538db0 fffff8a0`08b08d70 : nt!KiServiceLinkage
fffff880`038d5bd0 fffff880`11dbaac3 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000001 : dxgmms1!VIDMM_PROCESS_HEAP::Free+0xa2
fffff880`038d5c00 fffff880`11db5153 : 00000000`00000000 fffff8a0`0efb2390 fffff8a0`0efb2390 00000000`00000006 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x7b
fffff880`038d5cb0 fffff880`11d9baa7 : fffff8a0`098e9820 fffff8a0`01cf65e0 fffff880`038d5e20 00000000`00000020 : dxgmms1!VIDMM_GLOBAL::OpenOneAllocation+0x483
fffff880`038d5d90 fffff880`11ce7469 : 00000000`00000000 fffff880`038d6260 00000000`00000000 fffff8a0`0ea060a0 : dxgmms1!VidMmOpenAllocation+0xeb
fffff880`038d5de0 fffff880`11ce0610 : fffff880`038d6048 fffff8a0`02262a40 fffff880`038d6220 fffff880`038d6220 : dxgkrnl!DXGDEVICE::CreateVidMmAllocations<_DXGK_ALLOCATIONINFO>+0x291
fffff880`038d5e70 fffff880`11ce22ef : fffff8a0`01cff000 fffff880`038d64d0 00000000`00000000 fffff8a0`01cff000 : dxgkrnl!DXGDEVICE::CreateAllocation+0xca8
fffff880`038d6470 fffff880`11ce89e0 : 00000000`00009000 fffff900`c00c079c 00000000`00000000 00000000`00000000 : dxgkrnl!DXGDEVICE::CreateStandardAllocation+0x367
fffff880`038d65d0 fffff960`0063682d : fffff900`c00c0020 00000000`00000000 fffff880`038d6cd0 00000000`00000000 : dxgkrnl!DxgkCddEnable+0x904
fffff880`038d6920 fffff960`00635ce1 : ffffffff`00000004 ffffffff`fffd7476 00000000`00000002 fffffa80`00000000 : cdd!CreateAndEnableDevice+0x1e1
fffff880`038d69b0 fffff800`02f75fee : 00000000`045c2d49 fffffa80`06638b60 00000000`00000080 fffffa80`06528060 : cdd!PresentWorkerThread+0x975
fffff880`038d6d40 fffff800`02ccc5e6 : fffff880`02fd5180 fffffa80`06638b60 fffff880`02fdffc0 00000000`00000246 : nt!PspSystemThreadStartup+0x5a
fffff880`038d6d80 00000000`00000000 : fffff880`038d7000 fffff880`038d1000 fffff880`038d5140 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VIDMM_PROCESS_HEAP::Free+a2
fffff880`11dcf4b2 488b0e mov rcx,qword ptr [rsi]
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: dxgmms1!VIDMM_PROCESS_HEAP::Free+a2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799c1
FAILURE_BUCKET_ID: X64_0x1a_41790_dxgmms1!VIDMM_PROCESS_HEAP::Free+a2
BUCKET_ID: X64_0x1a_41790_dxgmms1!VIDMM_PROCESS_HEAP::Free+a2
Followup: MachineOwner
---------
-
Loading Dump File [K:\BSODDmpFiles\Sabrac\Windows_NT6_BSOD_jcgriff2\012412-22339-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c66000 PsLoadedModuleList = 0xfffff800`02eab670
Debug session time: Tue Jan 24 20:09:37.095 2012 (GMT-7)
System Uptime: 0 days 4:56:35.061
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck FE, {5, fffffa80052af1a0, 10024397, fffffa80041286c8}
Probably caused by : usbohci.sys ( usbohci!OHCI_PollIsoEndpoint+5d )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
using a physical memory address that was not allocated by
the USBport driver.
Arg2: fffffa80052af1a0, Device extension pointer of the host controller
Arg3: 0000000010024397, PCI Vendor,Product id for the controller
Arg4: fffffa80041286c8, Pointer to Endpoint data structure
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xFE
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff8801102df7e to fffff80002ce2c40
STACK_TEXT:
fffff880`02ffdae8 fffff880`1102df7e : 00000000`000000fe 00000000`00000005 fffffa80`052af1a0 00000000`10024397 : nt!KeBugCheckEx
fffff880`02ffdaf0 fffff880`11da5ed9 : 00000000`cf440700 00000000`00000000 fffffa80`052af1a0 fffffa80`041286c8 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x18a
fffff880`02ffdb30 fffff880`11da8744 : fffffa80`041286c8 fffffa80`04128480 fffffa80`052af1a0 00000000`ffffff02 : usbohci!OHCI_PollIsoEndpoint+0x5d
fffff880`02ffdb80 fffff880`11001e8b : 00000000`00000002 fffffa80`04128480 fffffa80`052af1a0 00000000`00000000 : usbohci!OHCI_PollEndpoint+0x4c
fffff880`02ffdbb0 fffff880`110069d1 : 00000000`00000070 00000000`00000004 fffffa80`04128480 fffffa80`052af050 : USBPORT!MPf_PollEndpoint+0x9b
fffff880`02ffdbe0 fffff880`11012077 : fffffa80`052af1a0 00000000`00000070 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1
fffff880`02ffdc40 fffff880`11002f89 : fffffa80`052af050 00000000`00000000 fffffa80`052afa02 fffffa80`052afa18 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1c3
fffff880`02ffdca0 fffff800`02cee0ac : fffff880`02fd5180 fffffa80`052afa18 fffffa80`052afa30 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`02ffdcd0 fffff800`02cda96a : fffff880`02fd5180 fffff880`02fdffc0 00000000`00000000 fffff880`11002db0 : nt!KiRetireDpcList+0x1bc
fffff880`02ffdd80 00000000`00000000 : fffff880`02ffe000 fffff880`02ff8000 fffff880`02ffdd40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
usbohci!OHCI_PollIsoEndpoint+5d
fffff880`11da5ed9 8bd3 mov edx,ebx
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: usbohci!OHCI_PollIsoEndpoint+5d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: usbohci
IMAGE_NAME: usbohci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0bff
FAILURE_BUCKET_ID: X64_0xFE_usbohci!OHCI_PollIsoEndpoint+5d
BUCKET_ID: X64_0xFE_usbohci!OHCI_PollIsoEndpoint+5d
Followup: MachineOwner
---------
-
Loading Dump File [K:\BSODDmpFiles\Sabrac\Windows_NT6_BSOD_jcgriff2\012412-17004-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c04000 PsLoadedModuleList = 0xfffff800`02e49670
Debug session time: Tue Jan 24 15:12:06.192 2012 (GMT-7)
System Uptime: 0 days 0:02:01.174
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck FC, {fffff88004c00000, 80000001270f0963, fffff88003e06520, 2}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+45d8c )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory. The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff88004c00000, Virtual address for the attempted execute.
Arg2: 80000001270f0963, PTE contents.
Arg3: fffff88003e06520, (reserved)
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xFC
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: fffff88003e06520 -- (.trap 0xfffff88003e06520)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800567b000 rbx=0000000000000000 rcx=0000000000000953
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004c00000 rsp=fffff88003e066b0 rbp=0000000000000080
r8=fffff78000000000 r9=0000000000000000 r10=fffffa8003a8fb00
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
monitor!WPP_SF_ <PERF> (monitor+0x0):
fffff880`04c00000 4d5a pop r10
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c2c6c4 to fffff80002c80c40
STACK_TEXT:
fffff880`03e063b8 fffff800`02c2c6c4 : 00000000`000000fc fffff880`04c00000 80000001`270f0963 fffff880`03e06520 : nt!KeBugCheckEx
fffff880`03e063c0 fffff800`02c7ed6e : 00000000`00000008 fffff880`04c00000 fffff880`03e06c00 fffffa80`05fbcb60 : nt! ?? ::FNODOBFM::`string'+0x45d8c
fffff880`03e06520 fffff880`04c00000 : fffffa80`0567b000 01ccdae5`35334421 fffff880`03e066f8 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`03e066b0 fffffa80`0567b000 : 01ccdae5`35334421 fffff880`03e066f8 00000000`00000000 00000000`00000000 : monitor!WPP_SF_ <PERF> (monitor+0x0)
fffff880`03e066b8 01ccdae5`35334421 : fffff880`03e066f8 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`0567b000
fffff880`03e066c0 fffff880`03e066f8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1ccdae5`35334421
fffff880`03e066c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`03e066f8
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+45d8c
fffff800`02c2c6c4 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+45d8c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3
FAILURE_BUCKET_ID: X64_0xFC_nt!_??_::FNODOBFM::_string_+45d8c
BUCKET_ID: X64_0xFC_nt!_??_::FNODOBFM::_string_+45d8c
Followup: MachineOwner
---------