Code:
-
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\gruber12\012112-13244-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Machine Name:
Kernel base = 0x82851000 PsLoadedModuleList = 0x8299a4d0
Debug session time: Sat Jan 21 23:47:01.887 2012 (UTC - 7:00)
System Uptime: 0 days 13:10:27.886
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000006, 82ac9b51, 999038f4, 0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::Free+75 )
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: c0000006, The exception code that was not handled
Arg2: 82ac9b51, The address that the exception occurred at
Arg3: 999038f4, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
FAULTING_IP:
nt!MiUnsecureVirtualMemory+ef
82ac9b51 8b4b0c mov ecx,dword ptr [ebx+0Ch]
TRAP_FRAME: 999038f4 -- (.trap 0xffffffff999038f4)
ErrCode = 00000000
eax=00000000 ebx=96308289 ecx=86b06f4a edx=86ab0130 esi=86aecb18 edi=86b06f2a
eip=82ac9b51 esp=99903968 ebp=99903978 iopl=0 nv up ei ng nz ac po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010292
nt!MiUnsecureVirtualMemory+0xef:
82ac9b51 8b4b0c mov ecx,dword ptr [ebx+0Ch] ds:0023:96308295=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: legends.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 907a0f17 to 82ac9b51
STACK_TEXT:
99903978 907a0f17 86b06f4b a8877948 889642b8 nt!MiUnsecureVirtualMemory+0xef
99903994 907924f3 a1113f00 a8877948 853cebc0 dxgmms1!VIDMM_PROCESS_HEAP::Free+0x75
999039cc 9079b6d1 009642b8 00000001 00000000 dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0xd1
99903a10 9079bf53 00000000 00000000 894275b0 dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x12b
99903a30 9077f32b a1180a18 00000000 99903abc dxgmms1!VIDMM_GLOBAL::CloseAllocation+0x37
99903a40 906ee491 86489000 a1180a18 00000000 dxgmms1!VidMmCloseAllocation+0x13
99903abc 906e4ac8 00000000 00000000 9a006940 dxgkrnl!DXGDEVICE::DestroyAllocations+0x19a
99903ae4 906eed0e 00000000 00000001 00000000 dxgkrnl!DXGDEVICE::ProcessTerminationList+0x89
99903b08 906eebb8 00000000 00000000 a9ee1658 dxgkrnl!DXGDEVICE::TerminateAllocations+0x13b
99903b64 906ef441 99903b98 00000001 09fe2cff dxgkrnl!DXGDEVICE::DestroyAllocation+0x2d6
99903d28 8288f21a 0739fccc 0739fcdc 77cd7094 dxgkrnl!DxgkDestroyAllocation+0x6d1
99903d28 77cd7094 0739fccc 0739fcdc 77cd7094 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0739fcdc 00000000 00000000 00000000 00000000 0x77cd7094
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VIDMM_PROCESS_HEAP::Free+75
907a0f17 6800800000 push 8000h
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: dxgmms1!VIDMM_PROCESS_HEAP::Free+75
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d4a24c1
FAILURE_BUCKET_ID: 0x8E_dxgmms1!VIDMM_PROCESS_HEAP::Free+75
BUCKET_ID: 0x8E_dxgmms1!VIDMM_PROCESS_HEAP::Free+75
Followup: MachineOwner
---------
-
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\gruber12\011812-12324-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Machine Name:
Kernel base = 0x8283d000 PsLoadedModuleList = 0x829864d0
Debug session time: Wed Jan 18 20:06:32.500 2012 (UTC - 7:00)
System Uptime: 0 days 6:33:29.874
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.....
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: 853b82e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 906a9d68, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 00000002, Optional internal context dependent data.
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
FAULTING_IP:
atikmpag+5d68
906a9d68 8bff mov edi,edi
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
91e54ba4 9077107b 00000116 853b82e0 906a9d68 nt!KeBugCheckEx+0x1e
91e54bc8 90765937 906a9d68 00000000 00000002 dxgkrnl!TdrBugcheckOnTimeout+0x8d
91e54bec 907a192c 00000000 00000000 91e54cb0 dxgkrnl!TdrIsRecoveryRequired+0xb8
91e54c64 907c8c1d fffffcfb 0017175a 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
91e54c90 907a8993 85634788 91e54cb0 00000102 dxgmms1!VidSchWaitForCompletionEvent+0x16f
91e54d28 907cd3c9 00000000 82874509 85634788 dxgmms1!VidSchiScheduleCommandToRun+0x14d
91e54d3c 907cd485 85634788 00000000 8648f510 dxgmms1!VidSchiRun_PriorityTable+0xf
91e54d50 82a45fda 85634788 b6387152 00000000 dxgmms1!VidSchiWorkerThread+0x7f
91e54d90 828ee1f9 907cd406 85634788 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
atikmpag+5d68
906a9d68 8bff mov edi,edi
SYMBOL_NAME: atikmpag+5d68
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME: atikmpag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4dae3541
FAILURE_BUCKET_ID: 0x116_IMAGE_atikmpag.sys
BUCKET_ID: 0x116_IMAGE_atikmpag.sys
Followup: MachineOwner
---------
- Related to DirectX/display card. Other possible causes are Memory problems... Viruses... Corrupted hard disk system files... Corrupted System Files... Lack of Windows updates... Drivers...
Thanks to JMH for helping with my understanding of this crash. - This is a display card or display card driver problem. It means the display card did not respond to the system within an acceptable period of time.
Use the following steps to resolve each of the crashes. We will start with the related factors.
- If you are overclocking anything, please stop.
- Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.
- Download the latest drivers for your display card(s)
- Click Start Menu
- Right Click My Computer/Computer
- Click Manage
- Click Device Manager from the list on the left
- Expand Display adapters
- Do the following for each adapter (in case you have multiple display cards)
- Right click the adapter
- Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
- Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
- Restart your computer after uninstalling drivers for all display cards
- Install the latest driver for the display cards once Windows starts
Alternatively:
- Login as an adminstrative user
- Download the latest drivers for your display card(s)
- Click Start Menu
- Click Control Panel
- Click Hardware and Sound
- Click Device Manager (the last link under Devices and Printers)
- Expand Display adapters
- Do the following for each adapter (in case you have multiple display cards)
- Right click the adapter
- Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
- Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
- Restart your computer after uninstalling drivers for all display cards
- Install the latest driver for the display cards once Windows starts
- Do the steps for STOP 0x116: VIDEO_TDR_ERROR troubleshooting by following the first three posts of that thread by usasma very carefully.
Quote