BSOD playing Starcraft 2 only system thread exception not handled

flipstorm · 09 Oct 2011

Ok so I didn't have any crashing problems for about a month or so and things were going really good. I was using my onboard video since I was waiting for my graphics card replacement to come in. It came in but basically was still messed up (fan in terrible shape, causing it to overheat) so I switched back to using my onboard video and since then I have been having constant BSOD. However, I have noticed that the BSOD only occur now when I play Starcraft 2. They also were not happening before I switched video cards. The onboard video is Radeon HD 4200 and the card I was using was a Radeon HD 4870. They both use the same ATI catalyst suite according to the AMD website so I'm not sure if there is a driver issue here.

According to whocrashed, these crashes are being caused by dxgmms1.sys so I'm thinking I may have a DirectX problem? I have 11.1 which is the latest version I believe so I am a bit confused.

Awhile I believed I had hardware problems, and I'm still not entirely sure but my computer is no longer crashing at random times, only when I play Starcraft 2 now. I ran Memtest and there were no errors. I've also included a crash report I found on notepad that I can't make sense of but indicates that SC2 caused the crash.

usasma · 11 Oct 2011

NOTE: I have severe eye problems. If I do not respond to your postings, please PM another staff member for assistance.

The memory dumps point out where the error occurred, not what the root cause was. For example, a problem with StarCraft may have crashed dxgkrnl.sys - so the dump would point to it (dxgkrnl.sys) but the actual cause was a problem with StarCraft.

Since it only crashes on Starcraft, then Starcraft may be the issue. Please uninstall Starcraft, then download and install the latest, Win7 compatible version (with all patches) from the StarCraft website.

You have the AMD Overdrive/EasyTune6 driver installed. This program is known to cause BSOD's in Win7 systems. Please uninstall it. Also, if overclocking, please return the system to stock values while we're testing.

I'd also uninstall your ATI drivers and reinstall a fresh copy from the ATI website (there are differences between the 2 versions of the card that you've been using).

OLDER DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please update these drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers:

Code:


amdxata.sys       Fri Mar 19 12:18:18 2010 (4BA3A3CA)
AsIO.sys          Mon Apr 06 03:21:08 2009 (49D9AD64)
amdiox64.sys      Thu Feb 18 10:17:53 2010 (4B7D5A21)
GEARAspiWDM.sys   Mon May 18 08:17:04 2009 (4A1151C0)
ASACPI.sys        Wed May 13 21:25:17 2009 (4A0B72FD)
viahduaa.sys      Mon Aug 17 07:20:43 2009 (4A893D0B)
ladfSBVMamd64.sys Fri Sep 24 15:13:10 2010 (4C9CF846)
rtl8187.sys       Wed Dec 09 04:16:39 2009 (4B1F6AF7)
ladfDHP2amd64.sys Fri Sep 24 13:06:44 2010 (4C9CDAA4)
AODDriver2.sys    Wed Jun 15 04:38:35 2011 (4DF86F8B)
cpuz135_x64.sys   Tue Nov 09 08:33:36 2010 (4CD94DB0)
Rt64win7.sys      Wed Jun 23 05:10:45 2010 (4C21CF95)
NisDrvWFP.sys     Wed Apr 06 16:08:53 2011 (4D9CC855)
atikmpag.sys      Thu Sep 08 12:52:41 2011 (4E68F2D9)
ASACPI.sys        Sun Mar 27 22:30:36 2005 (42476C4C)
MpFilter.sys      Wed Apr 06 16:07:29 2011 (4D9CC801)

BSOD BUGCHECK SUMMARY

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\100811-16036-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Oct  9 00:04:57.815 2011 (UTC - 4:00)
System Uptime: 0 days 0:09:52.251
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`04820d90 fffff880`021bd6a8 fffff880`021bcf00
BiosVersion = 0211   
BiosReleaseDate = 07/08/2009
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\100711-16723-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Fri Oct  7 23:27:26.385 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:13.993
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+53a )
BUGCHECK_STR:  0x19_20
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x19_20_nt!PoIdle+53a
Bugcheck code 00000019
Arguments 00000000`00000020 fffff8a0`001118a0 fffff8a0`001118e0 00000000`05040110
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092811-28610-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Wed Sep 28 18:16:40.399 2011 (UTC - 4:00)
System Uptime: 0 days 1:52:43.006
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2be39 )
BUGCHECK_STR:  0x1a_782
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1a_782_nt!_??_::FNODOBFM::_string_+2be39
Bugcheck code 0000001A
Arguments 00000000`00000782 fffffa80`037ec818 fffff980`0c4c0000 fffff8a0`017bbb80
BiosVersion = 0211   
BiosReleaseDate = 07/08/2009
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092811-14851-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Wed Sep 28 03:51:44.337 2011 (UTC - 4:00)
System Uptime: 0 days 0:04:23.679
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+78f0 )
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
Bugcheck code 00000116
Arguments fffffa80`038f6010 fffff880`034808f0 ffffffff`c0000001 00000000`00000003
BiosVersion = 0211   
BiosReleaseDate = 07/08/2009
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092811-15693-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Wed Sep 28 03:46:51.429 2011 (UTC - 4:00)
System Uptime: 0 days 5:45:06.772
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+233 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!ExDeferredFreePool+233
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02bfb0bf fffff880`033ba370 00000000`00000000
BiosVersion = 0211   
BiosReleaseDate = 07/08/2009
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

flipstorm · 12 Oct 2011

I reinstalled my graphics card's drivers and most recently I got my first crash while not playing SC2 (just browsing the internet). It wasn't a BSOD either, my comp just crashed and restarted itself as well. Supposedly it was a Page fault in nonpaged area crash.

usasma · 12 Oct 2011

Interesting set of errors. Please zip up the MEMORY.dmp file located in C:\Windows and upload it to a file-hosting service - and post the link to it here.

Event[111]:
Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 2011-10-12T11:11:17.000
Event ID: 1001
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Phillip-PC
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xffffffffffffff8c, 0x0000000000000001, 0xfffff9600017bfe5, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: .

Event[112]:
Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 2011-10-12T11:11:16.000
Event ID: 1005
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Phillip-PC
Description:
Unable to produce a minidump file from the full dump file.

Please run Driver Verifier according to these instructions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool" and "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Code:

Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

flipstorm · 12 Oct 2011

Ok, I ran verifier and got my computer to crash pretty fast. Here's the dump report.

MEMORY.zip

usasma · 12 Oct 2011

Sorry, but the memory dump is partially corrupted. Please try uploading it again - maybe try another free file-hosting services?

flipstorm · 12 Oct 2011

http://www.filedropper.com/memory_6 Hopefully this one works

usasma · 13 Oct 2011

File Dropper says the file size is 0 bytes.
You can try this to get us some info also. It seems complicated, but just follow it step by step until you've done step H (I haven't updated this page in a while, so post back if the links don't work): WinDbg Analysis Report

flipstorm · 13 Oct 2011

Here is what I got from the debugger. I've also started to get more BSOD now when just using my computer regularly. I also get different errors each time it seems I dunno whats wrong.

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e5b000 PsLoadedModuleList = 0xfffff800`030a0670
Debug session time: Thu Oct 13 16:00:44.404 2011 (UTC - 7:00)
System Uptime: 0 days 0:48:40.840
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`fffdf018). Type ".hh dbgerr001" for details
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff960000dfbdd, fffff8800292bf80, 0}

Page 71406 not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : win32k.sys ( win32k!RGNOBJ::bCopy+29 )

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

1: 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: fffff960000dfbdd, Address of the instruction which caused the bugcheck
Arg3: fffff8800292bf80, 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:
win32k!RGNOBJ::bCopy+29
fffff960`000dfbdd 44394018 cmp dword ptr [rax+18h],r8d

CONTEXT: fffff8800292bf80 -- (.cxr 0xfffff8800292bf80)
rax=0000000000000080 rbx=fffff8800292ca80 rcx=fffff900c070e010
rdx=00000000000000d8 rsi=0000000000000001 rdi=fffff8800292cae8
rip=fffff960000dfbdd rsp=fffff8800292c960 rbp=00000000000000a0
r8=00000000000000d8 r9=0000000000000000 r10=fffffa8005933d00
r11=0000000000000001 r12=fffff900c59fd630 r13=0000000000000078
r14=0000000080000000 r15=000000007fffffff
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
win32k!RGNOBJ::bCopy+0x29:
fffff960`000dfbdd 44394018 cmp dword ptr [rax+18h],r8d ds:002b:00000000`00000098=????????
Resetting default scope

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: plugin-contain

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff960001475c4 to fffff960000dfbdd

STACK_TEXT:
fffff880`0292c960 fffff960`001475c4 : fffff900`c070e010 00000000`00000001 00000000`00000001 00000000`00000001 : win32k!RGNOBJ::bCopy+0x29
fffff880`0292c9a0 fffff960`00146c7f : 00000000`00000001 fffff900`c070e010 fffff900`c1ec41b0 fffff880`0292cb80 : win32k!DC::bCompute+0x274
fffff880`0292cae0 fffff960`00272d9a : fffff900`c00c0010 fffff880`0292cc00 fffff880`0292cca0 00000000`04f48da0 : win32k!DEVLOCKOBJ::bLock+0x2e7
fffff880`0292cb20 fffff960`002ba663 : 00000000`004aef08 fffff880`0292cca0 00000000`04f48da0 00000000`00000001 : win32k!GreGetAppClipBox+0x7a
fffff880`0292cbe0 fffff800`02ed6ed3 : fffffa80`0618cb60 00000000`04f48da0 00000000`0964ec00 00000000`0d3c8618 : win32k!NtGdiGetAppClipBox+0x13
fffff880`0292cc20 00000000`73992e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`001beab8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73992e09

FOLLOWUP_IP:
win32k!RGNOBJ::bCopy+29
fffff960`000dfbdd 44394018 cmp dword ptr [rax+18h],r8d

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!RGNOBJ::bCopy+29

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4e658d5a

STACK_COMMAND: .cxr 0xfffff8800292bf80 ; kb

FAILURE_BUCKET_ID: X64_0x3B_win32k!RGNOBJ::bCopy+29

BUCKET_ID: X64_0x3B_win32k!RGNOBJ::bCopy+29

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

flipstorm · 13 Oct 2011

Here is another dump report of a crash I had yesterday where the error was dxgmms1.sys

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\101211-13494-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c13000 PsLoadedModuleList = 0xfffff800`02e58670
Debug session time: Wed Oct 12 13:56:26.618 2011 (UTC - 7:00)
System Uptime: 0 days 2:45:27.054
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880053afcf7, fffff880021bd6a8, fffff880021bcf00}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b )

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

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: fffff880053afcf7, The address that the exception occurred at
Arg3: fffff880021bd6a8, Exception Record Address
Arg4: fffff880021bcf00, 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::ReferenceAllocationForPreparation+2b
fffff880`053afcf7 0fba63540d bt dword ptr [rbx+54h],0Dh

EXCEPTION_RECORD: fffff880021bd6a8 -- (.exr 0xfffff880021bd6a8)
ExceptionAddress: fffff880053afcf7 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x000000000000002b)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000000780001b8
Attempt to read from address 00000000780001b8

CONTEXT: fffff880021bcf00 -- (.cxr 0xfffff880021bcf00)
rax=fffff8a00dadca30 rbx=0000000078000164 rcx=fffffa8005a37000
rdx=fffffa8005a88290 rsi=fffffa8005a37000 rdi=fffffa8005a37000
rip=fffff880053afcf7 rsp=fffff880021bd8e0 rbp=fffffa80046f26b0
r8=fffffa8006463601 r9=0000000000000000 r10=0000000000000000
r11=0000000000000048 r12=fffffa8005a88290 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x2b:
fffff880`053afcf7 0fba63540d bt dword ptr [rbx+54h],0Dh ds:002b:00000000`780001b8=????????
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: 00000000780001b8

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec2100
00000000780001b8

FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b
fffff880`053afcf7 0fba63540d bt dword ptr [rbx+54h],0Dh

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from fffff880053aced3 to fffff880053afcf7

STACK_TEXT:
fffff880`021bd8e0 fffff880`053aced3 : 00000000`00000000 fffffa80`0662f238 00000000`00000001 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x2b
fffff880`021bd910 fffff880`053c765d : 00000000`00000000 fffff8a0`0b1d7780 fffffa80`00000000 fffffa80`06463640 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
fffff880`021bdae0 fffff880`053c7398 : fffff880`02f67f00 fffff880`053c6d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`021bdcd0 fffff880`053c6e96 : 00000000`00000000 fffffa80`03ca9010 00000000`00000080 fffffa80`058ba410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`021bdd00 fffff800`02f2afee : 00000000`01fa247f fffffa80`05597b60 fffffa80`03670b30 fffffa80`05597b60 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`021bdd40 fffff800`02c815e6 : fffff880`02f63180 fffffa80`05597b60 fffff880`02f6df80 fffff880`0124ecb0 : nt!PspSystemThreadStartup+0x5a
fffff880`021bdd80 00000000`00000000 : fffff880`021be000 fffff880`021b8000 fffff880`021bd680 00000000`00000000 : nt!KxStartSystemThread+0x16

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME: dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799c1

STACK_COMMAND: .cxr 0xfffff880021bcf00 ; kb

FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b

BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b

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

Let me know if you want me to post more. Thanks!