Hello, I was downloading updates to Battlefield Bad Company 2, which i just installed, and left the room for a bit. I came back to find my computer restarted. I logged in and that lovely window that told me i got a BSOD came up.
OS: Windows 7 Ultimate x86 Retail
Original OS: See above
Hardware: Built this last summer. New parts were my motherboard, ram, hard drive, and power supply. I used an old video card at that time, and just upgraded 2 days ago. (ATI HD 5770) I did uninstall drivers for the previous card. And lastly, my Core 2 Duo E6300 that I bought used.
Thanks!
This one was caused by your video driver. Please remove and re-install using the below.
When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper
When it is removed then download and install the fresh copy.
Ken J
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\011411-18579-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82a0b000 PsLoadedModuleList = 0x82b53810
Debug session time: Fri Jan 14 03:06:19.994 2011 (GMT-5)
System Uptime: 0 days 6:48:41.493
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.........
Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 92a732a7, 8a3b6794, 0}
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmdag.sys ( atikmdag+4a2a7 )
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: c0000005, The exception code that was not handled
Arg2: 92a732a7, The address that the exception occurred at
Arg3: 8a3b6794, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
atikmdag+4a2a7
92a732a7 ff7020 push dword ptr [eax+20h]
TRAP_FRAME: 8a3b6794 -- (.trap 0xffffffff8a3b6794)
ErrCode = 00000000
eax=00000000 ebx=92d91194 ecx=84aaa008 edx=92d93e78 esi=84aaa008 edi=863c6008
eip=92a732a7 esp=8a3b6808 ebp=8a3b6814 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
atikmdag+0x4a2a7:
92a732a7 ff7020 push dword ptr [eax+20h] ds:0023:00000020=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: dwm.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 92cd8515 to 92a732a7
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
8a3b6814 92cd8515 00000000 00000015 86302000 atikmdag+0x4a2a7
8a3b6864 92cd871c 85c7c700 00000000 00000000 atikmdag+0x2af515
8a3b6884 92a3850b 8a3b68e8 00000000 85b78940 atikmdag+0x2af71c
8a3b68a0 8dd9dd34 85c5d600 8a3b68e8 82e206ee atikmdag+0xf50b
8a3b6a0c 930d14f2 85c5d600 8a3b6a4c 00000000 atikmpag+0x5d34
8a3b6a34 93105213 8a3b6a4c 00000000 a02cb2e0 dxgkrnl!DXGADAPTER::DdiSetVidPnSourceAddress+0x65
8a3b6b88 931038f8 a4665390 0000000f a02cb2e0 dxgkrnl!DXGADAPTER::UpdateModeWithPrimary+0xf1
8a3b6c68 931033d9 00000000 00000001 00000001 dxgkrnl!DXGDEVICE::SetDisplayMode+0x2be
8a3b6d18 941181f0 01b3f304 01b3f2f0 8a3b6d34 dxgkrnl!DxgkSetDisplayMode+0x6a4
8a3b6d28 82a4e44a 01b3f304 01b3f330 77b964f4 win32k!NtGdiDdDDISetDisplayMode+0x14
8a3b6d28 77b964f4 01b3f304 01b3f330 77b964f4 nt!KiFastCallEntry+0x12a
01b3f330 00000000 00000000 00000000 00000000 0x77b964f4
STACK_COMMAND: kb
FOLLOWUP_IP:
atikmdag+4a2a7
92a732a7 ff7020 push dword ptr [eax+20h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: atikmdag+4a2a7
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmdag
IMAGE_NAME: atikmdag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4cef1ec1
FAILURE_BUCKET_ID: 0x8E_atikmdag+4a2a7
BUCKET_ID: 0x8E_atikmdag+4a2a7
Followup: MachineOwner
---------
ALSO SPTD.SYS USED IN ALCOHOL AND DAEMON TOOLS IS A HUGE BSOD SOURCE.
Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: http://www.duplexsecure.com/en/downloads
Quote