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\DMP\031511-19219-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 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x82c51000 PsLoadedModuleList = 0x82d9b850
Debug session time: Tue Mar 15 22:25:17.624 2011 (UTC - 4:00)
System Uptime: 0 days 2:00:43.543
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
..................
Unable to load image \SystemRoot\system32\DRIVERS\igdkmd32.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd32.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd32.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000092, 8f03e586, adee8034, 0}
Probably caused by : igdkmd32.sys ( igdkmd32+200586 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000092, The exception code that was not handled
Arg2: 8f03e586, The address that the exception occurred at
Arg3: adee8034, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000092 - {EXCEPTION} Floating-point stack check.
FAULTING_IP:
igdkmd32+200586
8f03e586 d9ee fldz
TRAP_FRAME: adee8034 -- (.trap 0xffffffffadee8034)
ErrCode = 00000000
eax=00000004 ebx=85d9f000 ecx=adee8124 edx=04070400 esi=85d9f000 edi=adee868c
eip=8f03e58c esp=adee80a8 ebp=adee80bc iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
igdkmd32+0x20058c:
8f03e58c dd5df8 fstp qword ptr [ebp-8] ss:0010:adee80b4=0000000285d9f000
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: VISION~1.SCR
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8f03ebd2 to 8f03e58c
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
adee80bc 8f03ebd2 85d9f000 adee868c 00000000 igdkmd32+0x20058c
adee8140 8f03ee90 01d9f000 adee868c 00000000 igdkmd32+0x200bd2
adee8168 8f03f03e 85d9f000 adee868c adee8670 igdkmd32+0x200e90
adee85d4 8ee6d4ff 85d9f000 adee868c 82c1f6ee igdkmd32+0x20103e
adee8678 8ee6d65c 85d9f000 adee868c 00000000 igdkmd32+0x2f4ff
adee86fc 8ee81e77 85d9f000 adee8718 00000001 igdkmd32+0x2f65c
adee8728 8ee42335 85d9f000 87fd61e8 adee873f igdkmd32+0x43e77
adee8754 8f38526c 85d9f000 adee8794 adee879c igdkmd32+0x4335
adee877c 8f384a0c 00ee8794 8e4911b0 8e49107e dxgkrnl!DXGADAPTER::DdiIsSupportedVidPn+0x102
adee87a4 8f384b6a b06814d8 adee87d3 8e4911b0 dxgkrnl!VIDPN_MGR::_IsSupportedVidPn+0xca
adee87c8 8f3856b1 006814d8 00000005 00000001 dxgkrnl!VIDPN_MGR::FormalizeVidPnChange+0x85
adee880c 8f37d7bc 852ba540 00000001 8e4911b0 dxgkrnl!VIDPN_MGR::PinVidPnTargetMode+0x125
adee8840 8f37d197 908ff3e8 b06814d8 00000000 dxgkrnl!BmlFillPathModalityFromVidPn+0x94a
adee887c 8f37d472 908ff3e8 b06814d8 00000000 dxgkrnl!BmlFillPathModalityFromVidPn+0xc9d
adee88ac 8f37cd57 00000000 b06814d8 00000000 dxgkrnl!BmlFunctionalizeVidPn+0x19e
adee88e0 8f37cb14 00000003 00000003 fe2f2008 dxgkrnl!BmlPreparePathOrderAndVidPn+0x972
adee891c 8f37e306 fe2f2008 86351000 00000001 dxgkrnl!BmlGetPathModalityForAdapterWithCoreAccessHeld+0x41
adee8958 8f382c7b fe2f2008 00007fad 00000000 dxgkrnl!BmlGetPathModalityForAdapter+0x6b
adee8988 8f384e1c 00008000 8e49107e adee8a80 dxgkrnl!CCD_TOPOLOGY::Functionalize+0x8a
adee89d0 82246969 00008000 fe2f2008 8e49107e dxgkrnl!DxgkFunctionalizePathsModality+0x78
adee89f0 82238ac8 00000001 0000900f 00000000 win32k!FreePathsModality+0xf2
adee8adc 8231d874 00000000 ffb8b748 00000000 win32k!DrvChangeDisplaySettings+0x506
adee8b38 8231d9b3 00000000 00000000 884a1f78 win32k!xxxInternalUserChangeDisplaySettings+0x247
adee8ba8 822dd381 00000000 00000000 00000000 win32k!xxxUserChangeDisplaySettings+0x67
adee8c08 822dad58 85108d48 85108d48 00079b68 win32k!xxxDestroyThreadInfo+0x353
adee8c1c 822daea5 85108d48 00000001 85108d48 win32k!UserThreadCallout+0x77
adee8c38 82ebb4e2 85108d48 00000001 b1a949ee win32k!W32pThreadCallout+0x3a
adee8cb4 82ecf051 00000000 adab16f8 00000001 nt!PspExitThread+0x457
adee8ccc 82d028c0 adab16f8 adee8cf8 adee8d04 nt!PsExitSpecialApc+0x22
adee8d1c 82c8fc3b 00000001 00000000 adee8d34 nt!KiDeliverApc+0x28b
adee8d1c 0046ffe8 00000001 00000000 adee8d34 nt!Kei386EoiHelper+0x43
0012f82c 00000000 00000000 00000000 00000000 0x46ffe8
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
igdkmd32+200586
8f03e586 d9ee fldz
SYMBOL_NAME: igdkmd32+200586
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: igdkmd32
IMAGE_NAME: igdkmd32.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4aba7471
FAILURE_BUCKET_ID: 0x8E_igdkmd32+200586
BUCKET_ID: 0x8E_igdkmd32+200586
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\DMP\031511-18688-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 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x82c02000 PsLoadedModuleList = 0x82d4c850
Debug session time: Tue Mar 15 01:44:03.207 2011 (UTC - 4:00)
System Uptime: 0 days 2:22:07.704
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
......
Unable to load image \SystemRoot\system32\DRIVERS\igdkmd32.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd32.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd32.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000092, 8e82d586, b58a7034, 0}
Probably caused by : igdkmd32.sys ( igdkmd32+200586 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000092, The exception code that was not handled
Arg2: 8e82d586, The address that the exception occurred at
Arg3: b58a7034, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000092 - {EXCEPTION} Floating-point stack check.
FAULTING_IP:
igdkmd32+200586
8e82d586 d9ee fldz
TRAP_FRAME: b58a7034 -- (.trap 0xffffffffb58a7034)
ErrCode = 00000000
eax=00000004 ebx=85d5a000 ecx=b58a7124 edx=04070400 esi=85d5a000 edi=b58a768c
eip=8e82d58c esp=b58a70a8 ebp=b58a70bc iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
igdkmd32+0x20058c:
8e82d58c dd5df8 fstp qword ptr [ebp-8] ss:0010:b58a70b4=0000000285d5a000
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: VISION~1.SCR
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8e82dbd2 to 8e82d58c
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b58a70bc 8e82dbd2 85d5a000 b58a768c 00000000 igdkmd32+0x20058c
b58a7140 8e82de90 01d5a000 b58a768c 00000000 igdkmd32+0x200bd2
b58a7168 8e82e03e 85d5a000 b58a768c b58a7670 igdkmd32+0x200e90
b58a75d4 8e65c4ff 85d5a000 b58a768c 830196ee igdkmd32+0x20103e
b58a7678 8e65c65c 85d5a000 b58a768c 00000000 igdkmd32+0x2f4ff
b58a76fc 8e670e77 85d5a000 b58a7718 00000001 igdkmd32+0x2f65c
b58a7728 8e631335 85d5a000 87f3d420 b58a773f igdkmd32+0x43e77
b58a7754 8eb7426c 85d5a000 b58a7794 b58a779c igdkmd32+0x4335
b58a777c 8eb73a0c 008a7794 8e4221b0 8e42207e dxgkrnl!DXGADAPTER::DdiIsSupportedVidPn+0x102
b58a77a4 8eb73b6a b49ee510 b58a77d3 8e4221b0 dxgkrnl!VIDPN_MGR::_IsSupportedVidPn+0xca
b58a77c8 8eb746b1 009ee510 00000005 00000001 dxgkrnl!VIDPN_MGR::FormalizeVidPnChange+0x85
b58a780c 8eb6c7bc 99943fb0 00000001 8e4221b0 dxgkrnl!VIDPN_MGR::PinVidPnTargetMode+0x125
b58a7840 8eb6c197 96b2b9d0 b49ee510 00000000 dxgkrnl!BmlFillPathModalityFromVidPn+0x94a
b58a787c 8eb6c472 96b2b9d0 b49ee510 00000000 dxgkrnl!BmlFillPathModalityFromVidPn+0xc9d
b58a78ac 8eb6bd57 00000000 b49ee510 00000000 dxgkrnl!BmlFunctionalizeVidPn+0x19e
b58a78e0 8eb6bb14 00000003 00000003 fe47b640 dxgkrnl!BmlPreparePathOrderAndVidPn+0x972
b58a791c 8eb6d306 fe47b640 862fe000 00000001 dxgkrnl!BmlGetPathModalityForAdapterWithCoreAccessHeld+0x41
b58a7958 8eb71c7b fe47b640 000084d2 00000000 dxgkrnl!BmlGetPathModalityForAdapter+0x6b
b58a7988 8eb73e1c 00008000 8e42207e b58a7a80 dxgkrnl!CCD_TOPOLOGY::Functionalize+0x8a
b58a79d0 82796969 00008000 fe47b640 8e42207e dxgkrnl!DxgkFunctionalizePathsModality+0x78
b58a79f0 82788ac8 00000001 0000900f 00000000 win32k!FreePathsModality+0xf2
b58a7adc 8286d874 00000000 ffb8b748 00000000 win32k!DrvChangeDisplaySettings+0x506
b58a7b38 8286d9b3 00000000 00000000 88305838 win32k!xxxInternalUserChangeDisplaySettings+0x247
b58a7ba8 8282d381 00000000 00000000 00000000 win32k!xxxUserChangeDisplaySettings+0x67
b58a7c08 8282ad58 851dcd48 851dcd48 00331358 win32k!xxxDestroyThreadInfo+0x353
b58a7c1c 8282aea5 851dcd48 00000001 851dcd48 win32k!UserThreadCallout+0x77
b58a7c38 82e6c4e2 851dcd48 00000001 93362767 win32k!W32pThreadCallout+0x3a
b58a7cb4 82e80051 00000000 85095948 00000001 nt!PspExitThread+0x457
b58a7ccc 82cb38c0 85095948 b58a7cf8 b58a7d04 nt!PsExitSpecialApc+0x22
b58a7d1c 82c40c3b 00000001 00000000 b58a7d34 nt!KiDeliverApc+0x28b
b58a7d1c 00474107 00000001 00000000 b58a7d34 nt!Kei386EoiHelper+0x43
0012f828 00000000 00000000 00000000 00000000 0x474107
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
igdkmd32+200586
8e82d586 d9ee fldz
SYMBOL_NAME: igdkmd32+200586
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: igdkmd32
IMAGE_NAME: igdkmd32.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4aba7471
FAILURE_BUCKET_ID: 0x8E_igdkmd32+200586
BUCKET_ID: 0x8E_igdkmd32+200586
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\DMP\031611-23852-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 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x82c4b000 PsLoadedModuleList = 0x82d95850
Debug session time: Wed Mar 16 16:28:57.254 2011 (UTC - 4:00)
System Uptime: 0 days 4:27:11.298
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
..................
Unable to load image \SystemRoot\system32\DRIVERS\igdkmd32.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd32.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd32.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000092, 8f008953, b966b034, 0}
Probably caused by : igdkmd32.sys ( igdkmd32+1f4953 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000092, The exception code that was not handled
Arg2: 8f008953, The address that the exception occurred at
Arg3: b966b034, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000092 - {EXCEPTION} Floating-point stack check.
FAULTING_IP:
igdkmd32+1f4953
8f008953 d9ee fldz
TRAP_FRAME: b966b034 -- (.trap 0xffffffffb966b034)
ErrCode = 00000000
eax=b966b0f0 ebx=b966b68c ecx=b966b0b8 edx=04070400 esi=85d58000 edi=b966b68c
eip=8f00895a esp=b966b0a8 ebp=85d58000 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
igdkmd32+0x1f495a:
8f00895a dd5c2404 fstp qword ptr [esp+4] ss:0010:b966b0ac=00000000b966b68c
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: VISION~1.SCR
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 00000000 to 8f00895a
STACK_TEXT:
b966b0a4 00000000 b966b68c 00000000 b966b68c igdkmd32+0x1f495a
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
igdkmd32+1f4953
8f008953 d9ee fldz
SYMBOL_NAME: igdkmd32+1f4953
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: igdkmd32
IMAGE_NAME: igdkmd32.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a01d354
FAILURE_BUCKET_ID: 0x8E_igdkmd32+1f4953
BUCKET_ID: 0x8E_igdkmd32+1f4953
Followup: MachineOwner
---------