Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.



  • Please log in to reply
2 replies to this topic

#1 TXChetG


  • Members
  • 2 posts
  • Local time:11:05 PM

Posted 13 December 2011 - 11:16 PM

Hello All,

Hopefully someone here will have some great ideas on how to solve my problem. So far I've gone through and found the dump file and run it through Windows Debugger via some instructions I found on this forum. I've tried to remember if there was anything suspect that I've installed recently that could be causing the problem, but I'm coming up empty. Here are the results from the Windows Debugger:

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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c4a000 PsLoadedModuleList = 0xfffff800`02e8f670
Debug session time: Tue Dec 13 20:55:57.058 2011 (UTC - 6:00)
System Uptime: 1 days 3:20:59.494
Loading Kernel Symbols
Loading User Symbols

Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 0, fffff80002ccdc02}

Probably caused by : dxgmms1.sys ( dxgmms1!VidMmiProcessTerminationCommand+5f )

Followup: MachineOwner

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

An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002ccdc02, address which referenced memory

Debugging Details:

READ_ADDRESS:  0000000000000000 


fffff800`02ccdc02 488b3f          mov     rdi,qword ptr [rdi]




TRAP_FRAME:  fffff880041c4a00 -- (.trap 0xfffff880041c4a00)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffff880009e9180
rdx=fffffa800bd92780 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ccdc02 rsp=fffff880041c4b90 rbp=0000000000000000
 r8=0000000000000000  r9=fffffa800bcecc40 r10=fffffa800bcecc40
r11=fffff880041c4c20 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac po cy
fffff800`02ccdc02 488b3f          mov     rdi,qword ptr [rdi] ds:26f0:0000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cc61e9 to fffff80002cc6c40

fffff880`041c48b8 fffff800`02cc61e9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`041c48c0 fffff800`02cc4e60 : fffffa80`00000000 fffff800`02c08ae7 00000000`00000000 fffffa80`0bd92788 : nt!KiBugCheckDispatch+0x69
fffff880`041c4a00 fffff800`02ccdc02 : 00000000`00000000 00000000`00000000 00000000`00000002 fffff800`02ccdbc0 : nt!KiPageFault+0x260
fffff880`041c4b90 fffff800`02ccaca6 : 00000000`00000000 fffff880`06f681cc 00000000`00000000 fffffa80`0ba55410 : nt!KiSignalSynchronizationObject+0x42
fffff880`041c4be0 fffff880`06f7836b : fffffa80`00000000 00000000`00000000 fffffa80`0ed09000 fffff880`041c4ca0 : nt!KeSetEvent+0x106
fffff880`041c4c50 fffff880`06f9616d : fffffa80`00000000 fffffa80`0ba55410 00000000`0000000f fffff880`06f97f09 : dxgmms1!VidMmiProcessTerminationCommand+0x5f
fffff880`041c4ca0 fffff880`06f953f8 : fffff880`009edf40 fffffa80`0c07c700 00000000`00000000 fffffa80`0ba55410 : dxgmms1!VidSchiSubmitDeviceCommand+0x39
fffff880`041c4cd0 fffff880`06f94e96 : 00000000`0000a4ff fffffa80`0c07c700 00000000`00000080 fffffa80`0ba55410 : dxgmms1!VidSchiSubmitQueueCommand+0xb0
fffff880`041c4d00 fffff800`02f61fee : 00000000`05dad85c fffffa80`0b7208c0 fffffa80`0728fb30 fffffa80`0b7208c0 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`041c4d40 fffff800`02cb85e6 : fffff880`009e9180 fffffa80`0b7208c0 fffff880`009f3fc0 fffff880`01622384 : nt!PspSystemThreadStartup+0x5a
fffff880`041c4d80 00000000`00000000 : fffff880`041c5000 fffff880`041bf000 fffff880`041c4680 00000000`00000000 : nt!KxStartSystemThread+0x16


fffff880`06f7836b 33d2            xor     edx,edx


SYMBOL_NAME:  dxgmms1!VidMmiProcessTerminationCommand+5f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys


FAILURE_BUCKET_ID:  X64_0xA_dxgmms1!VidMmiProcessTerminationCommand+5f

BUCKET_ID:  X64_0xA_dxgmms1!VidMmiProcessTerminationCommand+5f

Followup: MachineOwner

Machine Specs:
Dell Studio 1558
Windows 7 Home Premium 64-bit SP1
Intel i5

Let me know if you need anything else from me.

Thanks for the help!

BC AdBot (Login to Remove)


#2 hamluis



  • Moderator
  • 56,379 posts
  • Gender:Male
  • Location:Killeen, TX
  • Local time:11:05 PM

Posted 14 December 2011 - 12:02 PM

Appears to me that your video drivers may be damaged.

I would uninstall them...then reinstall them or more current versions from your system support page at the Dell website.


#3 TXChetG

  • Topic Starter

  • Members
  • 2 posts
  • Local time:11:05 PM

Posted 14 December 2011 - 01:46 PM

Thanks Louis. I'll see if there are any updated video drivers available, and/or try reinstalling them. I've only gotten the error twice, and I haven't been able to purposefully recreate it yet. We'll see how this goes.

Thank you again.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users