尘梦幽然 发表于 2013-6-24 00:40
我也这么怀疑,感觉显卡驱动主导的蓝屏不少见,但是directx主导的蓝屏可能显卡故障的因素更大?
您帮着看 ... *******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 92d42493, a3643698, 0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::DestroyAllocation+17 )
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: c0000005, The exception code that was not handled
Arg2: 92d42493, The address that the exception occurred at
Arg3: a3643698, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx
FAULTING_IP:
dxgmms1!VIDMM_GLOBAL::DestroyAllocation+17
92d42493 8b36 mov esi,dword ptr [esi]
TRAP_FRAME: a3643698 -- (.trap 0xffffffffa3643698)
ErrCode = 00000000
eax=a3c44210 ebx=886a8000 ecx=886a8000 edx=ff38456f esi=ff384663 edi=a3e3d4b0
eip=92d42493 esp=a364370c ebp=a3643718 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
dxgmms1!VIDMM_GLOBAL::DestroyAllocation+0x17:
92d42493 8b36 mov esi,dword ptr [esi] ds:0023:ff384663=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: firefox.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 92d257ed to 92d42493
STACK_TEXT:
a3643718 92d257ed a3c44210 a3e3d4b0 a3643738 dxgmms1!VIDMM_GLOBAL::DestroyAllocation+0x17
a3643728 92c6ffe7 a3c44210 a3e3d4b0 a36437b4 dxgmms1!VidMmDestroyAllocation+0x13
a3643738 92c9473b 86e2b410 a3c44210 a3e3d4b0 dxgkrnl!VIDMM_EXPORT::VidMmDestroyAllocation+0x14
a36437b4 92c939ca a1f86528 00000001 a1cdb080 dxgkrnl!DXGDEVICE::DestroyAllocations+0x3f0
a36437d4 92c8aab9 9eddccb0 00000000 b3d963d8 dxgkrnl!DXGDEVICE::DestroyResource+0x4d
a36437f4 92c8dede 00000001 00000000 00000000 dxgkrnl!DXGDEVICE::ProcessTerminationList+0x7a
a3643a04 92c9061e a3643a28 a3643cdc a3643cb8 dxgkrnl!DXGCONTEXT::Present+0x1c3
a3643d18 9902b9c0 00000010 a3dec990 a3643d34 dxgkrnl!DxgkPresent+0x2dd
a3643d28 840898a6 001ad368 001ad5f8 77247094 win32k!NtGdiDdDDIPresent+0x19
a3643d28 77247094 001ad368 001ad5f8 77247094 nt!KiSystemServicePostCall
WARNING: Frame IP not in any known module. Following frames may be wrong.
001ad5f8 00000000 00000000 00000000 00000000 0x77247094
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::DestroyAllocation+17
92d42493 8b36 mov esi,dword ptr [esi]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::DestroyAllocation+17
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5164d8b5
FAILURE_BUCKET_ID: 0x8E_dxgmms1!VIDMM_GLOBAL::DestroyAllocation+17
BUCKET_ID: 0x8E_dxgmms1!VIDMM_GLOBAL::DestroyAllocation+17
Followup: MachineOwner |