BSOD, first in a long time

nietzescher · 29 Nov 2010

Hello,

Back from Thanksgiving break. I booted into Windows and was messing with the new Google Earth 6 beta when I got a BSOD. I haven't checked the dump, but the blue screen itself blamed "dxgmms1.sys", a DirectX driver.

It is looking more and more likely that I have a video card driver issue. I've installed the latest drivers from ATI, but I want to completely remove all ATI drivers and reinstall them fresh (since each time I update my video card drivers, I simply install them on top of the previous drivers). Is there a program that I can use to remove the existing ATI drivers/files easily?

I've also considered the possibility that I have a hardware issue, of course, but if that were the case, it seems like I'd also have issues with my Ubuntu install (which has never given me any issues, aside from the fact that I'm not very good at using it). Is this not correct? In particular, could a faulty (read: bad hardware) video card work perfectly in Ubuntu but cause Windows to crash?

EDIT: Forgot to actually ask a question in the second paragraph. Has been fixed.

CarlTR6 · 29 Nov 2010

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

nietzescher · 06 Dec 2010

Hello,

I updated my graphics driver after first removing the old driver using Driver Sweeper. I got a BSOD soon after, while the computer was idle.

I'm not sure how much I'm going to be able to work on this for the next couple of weeks, since I have finals (and finals in grad school are wee bit more intense than they were in undergrad). So I'm running Ubuntu, which is, as always, crash-free (which is the reason I'm inclined to think my issue is NOT a hardware problem; if it were, wouldn't I be having problems with Ubuntu as well?).

Just for fun, here are the most recent crash dumps, if anyone wants to look at them. Seems like they haven't been incredibly helpful in the past, but it wouldn't hurt to take a look.

Thanks again for your time and patience...

nietzescher · 13 Dec 2010

So, like I said, I'm waiting until after finals are over (Tuesday) to start working seriously on my computer again... but I did accidentally discover something sort of interesting yesterday.

I had been using Windows for two days with no bluescreens. My system finally crashed (as I knew it would) last night during a game; the driver "atikmpag.sys" (a video driver) was to blame. I booted into Ubuntu, mounted my Windows partition and did a search for that file. (I'm not sure what I was planning on doing when I located the file.)

Ubuntu's search function works perhaps too well; I found eight copies of atikmpag.sys, all in various locations in my "C:\Windows" folder. This is after running Driver Sweeper and reinstalling ATI drivers from scratch. Only one of those copies was actually in the "drivers" folder. I proceeded to search for other ATI driver components and found multiple copies of most, if not all, of the files. Is it possible that one of these rogue copies is what's causing my system instability? I'm not at all sure how OSes (in particular, Windows) work, so maybe this idea is totally ridiculous; I would appreciate some feedback. (FWIW, I did read on some forum that a guy fixed his video driver issues by deleting all copies of "atikmpag.sys" on his HD and then reinstalling ATI drivers, but I'm not sure I should trust it.)

Oh, I also ran Furmark for about an hour. Hilariously, everything checked out fine; my temps topped out at around 82C, and I never saw any artifacts. Perhaps I need to let it run longer?

CarlTR6 · 13 Dec 2010

No, once the temp levels out and you are getting no artifacts, the video card has passed the Furmark. The extra copies of drivers and other system files is perfectly normal. Do not delete any of them unless you know precisely what your are doing. Deleting duplicate system files can quickly lead to reinstall (don't ask me how I know this :) ). For example, if you have uninstalled something and you know the drivers belong to what you uninstalled, you are safe in deleting them.

Even though you can run Ubuntu without a crash, it does not rule out a hardware issue. Win 7 puts a lot more stress on system components than does Ubuntu.

Did you run Prime95? And did you run Memtest from a cold boot after you computer has been off for a while? If not please try both starting with the cold boot of Memtest. All of your latest dumps blame or indicate memory corruption.

I wish you the best with your finals. Been there, done that and I am glad it is not me! :)

Code:

Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a1d000 PsLoadedModuleList = 0xfffff800`02c5ae50
Debug session time: Mon Nov 22 18:55:45.530 2010 (GMT-5)
System Uptime: 0 days 0:00:21.560
Loading Kernel Symbols
...............................................................
.........
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88002c9864e, fffff880009a93a8, fffff880009a8c10}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88002c9864e, The address that the exception occurred at
Arg3: fffff880009a93a8, Exception Record Address
Arg4: fffff880009a8c10, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
discache!ScpGetHiveLimits+4e
fffff880`02c9864e ff00            inc     dword ptr [rax]

EXCEPTION_RECORD:  fffff880009a93a8 -- (.exr 0xfffff880009a93a8)
ExceptionAddress: fffff88002c9864e (discache!ScpGetHiveLimits+0x000000000000004e)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880009a8c10 -- (.cxr 0xfffff880009a8c10)
rax=ffff000002508186 rbx=fffffa80064732a0 rcx=fffff880009a9618
rdx=0000000000020019 rsi=fffffa8006481000 rdi=fffffa8006481000
rip=fffff88002c9864e rsp=fffff880009a95e0 rbp=0000000000000000
 r8=fffe000004a1034c  r9=0000000000000020 r10=fffff80002a1d000
r11=fffff880009a96a8 r12=0000000000000001 r13=ffffffff80000110
r14=fffff980017acfd0 r15=000000000000001c
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
discache!ScpGetHiveLimits+0x4e:
fffff880`02c9864e ff00            inc     dword ptr [rax] ds:002b:ffff0000`02508186=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc50e0
 ffffffffffffffff 

FOLLOWUP_IP: 
discache!ScpGetHiveLimits+4e
fffff880`02c9864e ff00            inc     dword ptr [rax]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff88002c98035 to fffff88002c9864e

STACK_TEXT:  
fffff880`009a95e0 fffff880`02c98035 : fffffa80`064732a0 00000000`00000000 fffffa80`06481000 fffffa80`06481000 : discache!ScpGetHiveLimits+0x4e
fffff880`009a96b0 fffff800`02e75917 : fffffa80`064732a0 ffffffff`80000110 fffff980`017acfd0 00000000`00000001 : discache!DriverEntry+0x2d
fffff880`009a96e0 fffff800`02fbaad6 : fffffa80`063e6958 fffffa80`063e6958 fffffa80`063e68b0 fffff980`00000020 : nt!IopLoadDriver+0xa07
fffff880`009a99b0 fffff800`02fbbc92 : fffff800`00000000 fffff980`015cefd0 ffffffff`80000104 fffff8a0`00506d60 : nt!IopInitializeSystemDrivers+0x1d6
fffff880`009a9a40 fffff800`02fbecec : 00000000`00000000 00000000`00000010 ffffffff`80000028 fffff800`00812850 : nt!IoInitSystem+0x9b2
fffff880`009a9b40 fffff800`02f0f8c9 : 00000000`00000000 fffffa80`03ceb040 00000000`00000080 fffffa80`03cea5f0 : nt!Phase1InitializationDiscard+0x129c
fffff880`009a9d10 fffff800`02d31c06 : 00000000`00000000 00000000`00000080 00000000`00000000 fffff800`02a6bc19 : nt!Phase1Initialization+0x9
fffff880`009a9d40 fffff800`02a6bc26 : fffff800`02c07e80 fffffa80`03ceb040 fffff800`02c15c40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d80 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a7b60 00000000`00000000 : nt!KxStartSystemThread+0x16


CHKIMG_EXTENSION: !chkimg -lo 50 -db !discache
215 errors : !discache (fffff88002c98047-fffff88002c98fff)
fffff88002c98040  0f  00  00  48  8d  0d  c6 *00  00  00  4c  89  1d  bf  93  00 ...H......L.....
fffff88002c98050  00  48  89  05  c0  93  00  00  e8  59  6a  00  00  85  c0 *00 .H.......Yj.....
fffff88002c98060  1a  48  8d  0d  98  93  00  00  ff  15  1a  80  00  00  48 *00 .H............H.
fffff88002c98070  05  17  00  00  00  48  89 *00  68  33  c0  48  8b  5c  24 *00 .....H..h3.H.\$.
...
fffff88002c980d0  ff  15  ca  7f  00  00  48 *00  0d  5b  91  00  00  48  85 *00 ......H..[...H..
fffff88002c980e0  74  05  e8  d9  1e  00  00 *00  8b  0d  32  91  00  00  48 *00 t.........2...H.
fffff88002c980f0  c9  74  0b  ba  53  74  53 *00  ff  15  4a  7f  00  00  83 *00 .t..StS...J.....
...
fffff88002c98140  8b  d7  8b  ce  66  89  44 *00  42  ff  15  d9  7e  00  00 *00 ....f.D.B...~...
fffff88002c98150  8b  e8  48  3b  c3  75  0a *00  9a  00  00  c0  e9  df  01  00 ..H;.u..........
fffff88002c98160  00  66  a1  30  00  00  00 *00  f7  ff  ff  4c  8d  25  b6 *00 .f.0.......L.%..
fffff88002c98170  00  00  48  8d  15  27  90  00  00  49  8b  cc  66  89  1d *00 ..H..'...I..f...
...
fffff88002c981c0  74  7e  00  00  3b  c3  8b *00  0f  8c  09  01  00  00  49 *00 t~..;.........I.
fffff88002c981d0  cc  ff  15  69  7e  00  00 *00  c3  8b  f8  0f  8c  f6  00  00 ...i~...........
...
fffff88002c981f0  00  3b  c3  8b  f8  0f  8c *00  00  00  00  48  8d  05  ee *00 .;.........H....
...
fffff88002c98240  90  00  00  48  89  05  4e *00  00  00  48  8d  05  3f  90  00 ...H..N...H..?..
fffff88002c98250  00  83  e1  1f  48  0b  c6 *00  89  1d  42  90  00  00  0f *00 ....H.....B.....
...
fffff88002c98270  00  48  8d  8f  00  02  00  00  48  3b  f9  73  10  48  2b *00 .H......H;.s.H+.
...
fffff88002c982c0  33  c0  33  d2  ff  15  86 *00  00  00  3a  c3  0f  85  81  00 3.3.......:.....
fffff88002c982d0  00  00  bf  01  00  00  c0 *00  53  43  53  48  48  8b  cd *00 ........SCSHH...
fffff88002c982e0  15  63  7d  00  00  48  8b *00  4c  8f  00  00  45  33  db *00 .c}..H..L...E3..
fffff88002c982f0  89  1d  32  8f  00  00  4c *00  1d  33  8f  00  00  48  3b *00 ..2...L..3...H;.
...
fffff88002c98340  48  8b  5c  24  48  48  8b *00  24  50  48  83  c4  20  41 *00 H.\$HH..$PH.. A.
fffff88002c98350  5f  5e  c3  48  89  1d  86 *00  00  00  87  35  e4  8e  00  00 _^.H.......5....
fffff88002c98360  8b  fb  87  1d  d8  8e  00  00  eb  c7  cc  cc  cc  cc  cc *00 ................
fffff88002c98370  4c  8b  dc  49  89  5b  08 *00  48  83  ec  70  49  83  63 *00 L..I.[..H..pI.c.
...
fffff88002c983c0  32  48  8d  05  08  6c  00  00  49  89  43  c0  49  8d  43 *00 2H...l..I.C.I.C.
fffff88002c983d0  49  89  43  d8  ff  15  de *00  00  00  85  c0  78  6d  48 *00 I.C.........xmH.
fffff88002c983e0  8c  24  88  00  00  00  48 *00  64  24  28  00  48  8d  84 *00 .$....H.d$(.H...
fffff88002c983f0  90  00  00  00  45  33  c9 *00  33  c0  ba  00  00  10  00 *00 ....E3..3.......
...
fffff88002c98440  ff  15  da  7b  00  00  e8 *00  fc  ff  ff  48  8b  9c  24 *00 ...{.......H..$.
fffff88002c98450  00  00  00  48  83  c4  70 *00  c3  cc  cc  cc  cc  cc  cc *00 ...H..p.........
fffff88002c98460  40  53  48  83  ec  20  33 *00  8b  c3  87  05  e0  8d  00  00 @SH.. 3.........
fffff88002c98470  48  39  1d  f1  8d  00  00 *00  08  8b  c3  89  5c  24  38 *00 H9..........\$8.
...
fffff88002c984c0  27  48  8d  4c  24  38  e8 *00  1d  00  00  3b  c3  7c  19 *00 'H.L$8.....;.|..
fffff88002c984d0  05  3f  8d  00  00  39  44 *00  38  76  0d  b8  01  00  00  00 .?...9D.8v......
fffff88002c984e0  87  05  66  8d  00  00  eb *00  87  1d  5e  8d  00  00  48 *00 ..f.......^...H.
fffff88002c984f0  0d  0b  8f  00  00  48  83 *00  20  5b  48  ff  25  4f  7b  00 .....H.. [H.%O{.
...
fffff88002c98540  32  b8  01  00  00  00  87 *00  04  8d  00  00  85  c0  75 *00 2.............u.
fffff88002c98550  48  8d  0d  a9  8e  00  00 *00  15  fb  7a  00  00  84  c0 *00 H.........z.....
fffff88002c98560  12  48  8d  0d  d8  8e  00  00  ba  01  00  00  00  ff  15 *00 .H..............
fffff88002c98570  7a  00  00  48  83  c4  28 *00  cc  cc  cc  cc  cc  cc  cc *00 z..H..(.........
...
fffff88002c985c0  00  48  89  05  88  8e  00  00  48  8d  05  a1  fd  ff  ff *00 .H......H.......
fffff88002c985d0  89  05  5a  8e  00  00  ff *00  7c  7a  00  00  84  c0  74 *00 ..Z.....|z....t.
fffff88002c985e0  48  8d  0d  39  8e  00  00 *00  01  00  00  00  ff  15  6e *00 H..9..........n.
fffff88002c985f0  00  00  48  83  c4  28  c3 *00  cc  cc  cc  cc  cc  cc  cc *00 ..H..(..........
...
fffff88002c98640  8d  4c  24  38  4c  8d  44 *00  40  ba  19  00  02  00  ff *00 .L$8L.D.@.......
fffff88002c98650  14  7a  00  00  85  c0  0f *00  eb  00  00  00  48  8d  15 *00 .z..........H...
fffff88002c98660  69  00  00  48  8d  4c  24 *00  ff  15  02  7a  00  00  48 *00 i..H.L$....z..H.
fffff88002c98670  44  24  38  48  83  64  24 *00  00  48  83  64  24  68  00 *00 D$8H.d$..H.d$h..
...
fffff88002c986d0  48  8b  4c  24  30  4c  8d *00  24  70  4c  89  5c  24  28 *00 H.L$0L..$pL.\$(.
WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view  entire output.

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

STACK_COMMAND:  .cxr 0xfffff880009a8c10 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

Debug session time: Sun Nov 21 19:32:46.075 2010 (GMT-5)
System Uptime: 0 days 8:07:48.090
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002a59700, fffff88002e9df50, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

6: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002a59700, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88002e9df50, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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!ExReleaseFastMutexUnsafeAndLeaveCriticalRegion+0
fffff800`02a59700 48895c3e08      mov     qword ptr [rsi+rdi+8],rbx

CONTEXT:  fffff88002e9df50 -- (.cxr 0xfffff88002e9df50)
rax=fffff960002da4a0 rbx=fffffa8004f470d0 rcx=fffffa8005ffd780
rdx=000000000000067b rsi=000000000000ad00 rdi=0000000000000000
rip=fffff80002a59700 rsp=fffff88002e9e928 rbp=0000000000000001
 r8=0000000000000801  r9=fffff80002a1f000 r10=fffff880030f7be0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=2000000000008000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!ExReleaseFastMutexUnsafeAndLeaveCriticalRegion:
fffff800`02a59700 48895c3e08      mov     qword ptr [rsi+rdi+8],rbx ds:002b:00000000`0000ad08=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x3B

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002a59700

STACK_TEXT:  
fffff880`02e9e928 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExReleaseFastMutexUnsafeAndLeaveCriticalRegion


CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
8 errors : !nt (fffff80002a59703-fffff80002a5973b)
fffff80002a59700  48  89  5c *3e  08  57  48  83  ec  20  33 *5c  48  8b  d1  8d H.\>.WH.. 3\H...
fffff80002a59710  5f  01  48 *76  79  08  8b  c3  f0  0f  c1 *8f  3b  c7  0f  85 _.Hvy.......;...
fffff80002a59720  4c  d5  fc *d6  65  48  8b  0c  25  88  01 *0c  00  66  01  99 L...eH..%....f..
fffff80002a59730  c4  01  00 *23  74  0b  48  8b  5c  24  30 *60  83  c4  20  5f ...#t.H.\$0`.. _

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

STACK_COMMAND:  .cxr 0xfffff88002e9df50 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

Debug session time: Mon Nov 22 18:57:25.357 2010 (GMT-5)
System Uptime: 0 days 0:00:35.387
Loading Kernel Symbols
...............................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc000001d, fffff88004857c5e, b, fffffa8006bfbb00}

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
Probably caused by : hardware ( atikmdag+55c5e )

Followup: MachineOwner
---------

3: 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: ffffffffc000001d, The exception code that was not handled
Arg2: fffff88004857c5e, The address that the exception occurred at
Arg3: 000000000000000b, Parameter 0 of the exception
Arg4: fffffa8006bfbb00, Parameter 1 of the exception

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
atikmdag+55c5e
fffff880`04857c5e c4              ???

EXCEPTION_PARAMETER1:  000000000000000b

EXCEPTION_PARAMETER2:  fffffa8006bfbb00

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  b

EXCEPTION_RECORD:  fffff88002ffd7c8 -- (.exr 0xfffff88002ffd7c8)
ExceptionAddress: fffff88004857c5e (atikmdag+0x0000000000055c5e)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

TRAP_FRAME:  fffff88002ffd870 -- (.trap 0xfffff88002ffd870)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88002ffdaa8 rbx=0000000000000000 rcx=fffffa80067f6000
rdx=fffff88002ffda50 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004857c5e rsp=fffff88002ffda00 rbp=fffff88002ffdb10
 r8=fffff88002ffdb10  r9=0000000000000018 r10=fffffa8006bfbbd0
r11=fffff88002ffdad0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe cy
atikmdag+0x55c5e:
fffff880`04857c5e c4              ???
Resetting default scope

MISALIGNED_IP: 
atikmdag+55c5e
fffff880`04857c5e c4              ???

LAST_CONTROL_TRANSFER:  from fffff80002ab5a39 to fffff80002a7b740

FAILED_INSTRUCTION_ADDRESS: 
atikmdag+55c5e
fffff880`04857c5e c4              ???

STACK_TEXT:  
fffff880`02ffcff8 fffff800`02ab5a39 : 00000000`0000001e ffffffff`c000001d fffff880`04857c5e 00000000`0000000b : nt!KeBugCheckEx
fffff880`02ffd000 fffff800`02a7ad82 : fffff880`02ffd7c8 fffffa80`06bda3f8 fffff880`02ffd870 fffffa80`067f6000 : nt!KiDispatchException+0x1b9
fffff880`02ffd690 fffff800`02a78edf : fffff880`02ffd870 00000000`0000000b 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02ffd870 fffff880`04857c5e : fffffa80`06bd2540 00000008`00000004 fffffa80`06bb7c50 fffff880`048dfe58 : nt!KiInvalidOpcodeFault+0x11f
fffff880`02ffda00 fffffa80`06bd2540 : 00000008`00000004 fffffa80`06bb7c50 fffff880`048dfe58 00000000`000000a7 : atikmdag+0x55c5e
fffff880`02ffda08 00000008`00000004 : fffffa80`06bb7c50 fffff880`048dfe58 00000000`000000a7 ff0677e0`048d8a66 : 0xfffffa80`06bd2540
fffff880`02ffda10 fffffa80`06bb7c50 : fffff880`048dfe58 00000000`000000a7 ff0677e0`048d8a66 00000000`00000000 : 0x8`00000004
fffff880`02ffda18 fffff880`048dfe58 : 00000000`000000a7 ff0677e0`048d8a66 00000000`00000000 00000000`00000000 : 0xfffffa80`06bb7c50
fffff880`02ffda20 00000000`000000a7 : ff0677e0`048d8a66 00000000`00000000 00000000`00000000 00000003`00000030 : atikmdag+0xdde58
fffff880`02ffda28 ff0677e0`048d8a66 : 00000000`00000000 00000000`00000000 00000003`00000030 fffff880`0000000a : 0xa7
fffff880`02ffda30 00000000`00000000 : 00000000`00000000 00000003`00000030 fffff880`0000000a 00000007`00000048 : 0xff0677e0`048d8a66


STACK_COMMAND:  kb

FOLLOWUP_IP: 
atikmdag+55c5e
fffff880`04857c5e c4              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  atikmdag+55c5e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_atikmdag.sys

BUCKET_ID:  X64_IP_MISALIGNED_atikmdag.sys

Followup: MachineOwner
---------

Debug session time: Mon Nov 29 19:05:11.953 2010 (GMT-5)
System Uptime: 0 days 0:09:43.136
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880041d5fe8, fffff88002166698, fffff88002165f00}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+98 )

Followup: MachineOwner
---------

6: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880041d5fe8, The address that the exception occurred at
Arg3: fffff88002166698, Exception Record Address
Arg4: fffff88002165f00, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+98
fffff880`041d5fe8 48035020        add     rdx,qword ptr [rax+20h]

EXCEPTION_RECORD:  fffff88002166698 -- (.exr 0xfffff88002166698)
ExceptionAddress: fffff880041d5fe8 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x0000000000000098)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88002165f00 -- (.cxr 0xfffff88002165f00)
rax=00fff8a00f1293a0 rbx=fffff8a011871010 rcx=fffffa8007236760
rdx=0000000000000060 rsi=fffffa8003fff4f0 rdi=fffffa80060e7000
rip=fffff880041d5fe8 rsp=fffff880021668d0 rbp=0000000000000000
 r8=fffffa8003fff540  r9=0000000000000001 r10=0000000000000000
r11=fffffa80060e83c0 r12=000000000000009a r13=0000000000000000
r14=fffffa8005f021d0 r15=0000000000000974
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x98:
fffff880`041d5fe8 48035020        add     rdx,qword ptr [rax+20h] ds:002b:00fff8a0`0f1293c0=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc70e0
 ffffffffffffffff 

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+98
fffff880`041d5fe8 48035020        add     rdx,qword ptr [rax+20h]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff880041d38af to fffff880041d5fe8

STACK_TEXT:  
fffff880`021668d0 fffff880`041d38af : 00000000`00000000 fffffa80`057d74d0 00000000`000001a7 fffffa80`06f46e78 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x98
fffff880`02166910 fffff880`041ed65d : 00000000`00000000 fffff8a0`0f1293a0 fffffa80`00000000 fffffa80`05f021d0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b
fffff880`02166ae0 fffff880`041ed398 : fffff800`00b96080 fffff880`041ecd00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`02166cd0 fffff880`041ece96 : 00000000`00000000 fffffa80`04f38520 00000000`00000080 fffffa80`03d2b410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`02166d00 fffff800`02d33c06 : 00000000`02c1d154 fffffa80`05dc6b60 fffffa80`03c71b30 fffffa80`05dc6b60 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`02166d40 fffff800`02a6dc26 : fffff800`02c09e80 fffffa80`05dc6b60 fffff800`02c17c40 fffff880`0120e534 : nt!PspSystemThreadStartup+0x5a
fffff880`02166d80 00000000`00000000 : fffff880`02167000 fffff880`02161000 fffff880`02166690 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+98

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

STACK_COMMAND:  .cxr 0xfffff88002165f00 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+98

BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+98

Followup: MachineOwner
---------