Windows 7 - dxgmms1.sys, IRQL_NOT, and win32k.sys BSODS

nintendo2024 · 05-28-2011

So I've been having many BSODS ever since last year around this time, and I haven't been able to find a solution since then. I've had BSODS related to the title, as well as PAGEFILE FOUND IN NONPAGED AREA or some BSOD like that.

At first I thought it was a video card issue, possibly even the drivers associated with it, so I downloaded the newest drivers, uninstalled my video card programs, and erased all the drivers using Driver Sweeper in Safe Mode, reinstalled my drivers, and I still came up with BSODS. I then erased all the drivers again, and let Windows Update update my drivers, and I would still come up with issues. So I ran OCCT and FurMark burn tests and torture tests, and they all came back great with no issues; temperatures were great. But I still had BSODS.

I then suspected that my memory was faulty, so I first ran Windows Memory Diagnostic, and it came back with no errors, so I ran Memtest for 12 hours with each memory stick in its respective slot for 12 hours, and came back with no issues. I then ran the test for 12 hours with both on, and they both came back with no issues. That didn't solve the problem, so I reseated the memory onto the other two slots, and still came up with issues. I then retested the RAM for 24 hours straight, and no issues came up with the test, but I had a BSOD shortly after restarting.

Then I thought the CPU was the culprit, so I cleaned out my computer of dust, took it all apart, and put it all back together, and reapplied thermal paste onto my CPU and made sure the heatsink was seated correctly. I then proceeded to do CPU tests on OCCT for two hours, and it came back with no errors. But the BSODS continued.

I finally thought that maybe my HDD's were the issue, so I ran SeaDisk Diagnostic Test (all 3 of my drives are from Seagate), and did the Long test on all 3, and they all came back with no errors. But the BSODS continued.

I ran MalwareBytes and Avast, but there were no trojans, malware, etc. I ran scannow or whatever that is, and there were no errors. I even went as far as formatting all my drives, and having a fresh reinstall of my OS and programs, and I still face BSODS and random closing of Firefox and games I play.

I am now leaning towards the motherboard being the culprit behind my BSODS, but I still can't be sure; I'll see if you guys can help me out before I spend anymore money on my system. I'll upload the .zip files as specified in the BSOD info thread. Thanks a lot!

Is Windows 7 . . . - x86 (32-bit) or x64 ? - the original installed OS on the system? I upgraded from Home Premium to Professional. - an OEM or full retail version? Full retail. - OEM = came pre-installed on system - Full Retail = you purchased it from retailer - What is the age of system (hardware)? All except the video card is about two years old.
The video card is just a few weeks old.
- What is the age of OS installation (have you re-installed the OS?) I reinstalled the OS a few times; it is a few
days old into reinstallation.

zigzag3143 · 05-28-2011

Quote: Originally Posted by nintendo2024

So I've been having many BSODS ever since last year around this time, and I haven't been able to find a solution since then. I've had BSODS related to the title, as well as PAGEFILE FOUND IN NONPAGED AREA or some BSOD like that.

At first I thought it was a video card issue, possibly even the drivers associated with it, so I downloaded the newest drivers, uninstalled my video card programs, and erased all the drivers using Driver Sweeper in Safe Mode, reinstalled my drivers, and I still came up with BSODS. I then erased all the drivers again, and let Windows Update update my drivers, and I would still come up with issues. So I ran OCCT and FurMark burn tests and torture tests, and they all came back great with no issues; temperatures were great. But I still had BSODS.

I then suspected that my memory was faulty, so I first ran Windows Memory Diagnostic, and it came back with no errors, so I ran Memtest for 12 hours with each memory stick in its respective slot for 12 hours, and came back with no issues. I then ran the test for 12 hours with both on, and they both came back with no issues. That didn't solve the problem, so I reseated the memory onto the other two slots, and still came up with issues. I then retested the RAM for 24 hours straight, and no issues came up with the test, but I had a BSOD shortly after restarting.

Then I thought the CPU was the culprit, so I cleaned out my computer of dust, took it all apart, and put it all back together, and reapplied thermal paste onto my CPU and made sure the heatsink was seated correctly. I then proceeded to do CPU tests on OCCT for two hours, and it came back with no errors. But the BSODS continued.

I finally thought that maybe my HDD's were the issue, so I ran SeaDisk Diagnostic Test (all 3 of my drives are from Seagate), and did the Long test on all 3, and they all came back with no errors. But the BSODS continued.

I ran MalwareBytes and Avast, but there were no trojans, malware, etc. I ran scannow or whatever that is, and there were no errors. I even went as far as formatting all my drives, and having a fresh reinstall of my OS and programs, and I still face BSODS and random closing of Firefox and games I play.

I am now leaning towards the motherboard being the culprit behind my BSODS, but I still can't be sure; I'll see if you guys can help me out before I spend anymore money on my system. I'll upload the .zip files as specified in the BSOD info thread. Thanks a lot!

Is Windows 7 . . . - x86 (32-bit) or x64 ? - the original installed OS on the system? I upgraded from Home Premium to Professional. - an OEM or full retail version? Full retail. - OEM = came pre-installed on system - Full Retail = you purchased it from retailer - What is the age of system (hardware)? All except the video card is about two years old.
The video card is just a few weeks old.
- What is the age of OS installation (have you re-installed the OS?) I reinstalled the OS a few times; it is a few
days old into reinstallation.

It is a video issue. Either Directx, your video card, heat, or power. I would first re-install the video driver (again) usint this method, re-install directx.

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

Or Phyxion.net - Driver Sweeper

When it is removed then download and install the fresh copy.

How To Find Drivers:

Quote:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference http://www.carrona.org/dvrref.html
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

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\052811-18205-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02a53000 PsLoadedModuleList = 0xfffff800`02c98650
Debug session time: Sat May 28 21:49:52.876 2011 (GMT-4)
System Uptime: 0 days 17:11:32.234
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
...................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88003d8e7ac, fffff880066a3788, fffff880066a2fe0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+fec )

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

1: 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: fffff88003d8e7ac, The address that the exception occurred at
Arg3: fffff880066a3788, Exception Record Address
Arg4: fffff880066a2fe0, 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_MEMORY_SEGMENT::EvictResource+fec
fffff880`03d8e7ac 488b11          mov     rdx,qword ptr [rcx]

EXCEPTION_RECORD:  fffff880066a3788 -- (.exr 0xfffff880066a3788)
ExceptionAddress: fffff88003d8e7ac (dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0x0000000000000fec)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000080000000
Attempt to read from address 0000000080000000

CONTEXT:  fffff880066a2fe0 -- (.cxr 0xfffff880066a2fe0)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000080000000
rdx=fffff8a007ab9e50 rsi=fffff8a007ab9e50 rdi=0000000000000000
rip=fffff88003d8e7ac rsp=fffff880066a39c0 rbp=fffffa8005922000
 r8=0000000000001000  r9=0000000000000000 r10=0000000000000001
r11=fffff8a007ab9f58 r12=0000000000000000 r13=0000000000000001
r14=fffffa80050c0ad0 r15=fffff8a007ab9f58
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_MEMORY_SEGMENT::EvictResource+0xfec:
fffff880`03d8e7ac 488b11          mov     rdx,qword ptr [rcx] ds:002b:00000000`80000000=????????????????
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:  0000000080000000

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d02100
 0000000080000000 

FOLLOWUP_IP: 
dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+fec
fffff880`03d8e7ac 488b11          mov     rdx,qword ptr [rcx]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff88003d7e25d to fffff88003d8e7ac

STACK_TEXT:  
fffff880`066a39c0 fffff880`03d7e25d : fffffa80`050c0ad0 fffff8a0`07ab9e50 fffffa80`04627300 fffffa80`05922000 : dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0xfec
fffff880`066a3b30 fffff880`03d79358 : fffffa80`03b0dba0 00000000`00000000 00000000`00000000 fffff880`066a3ca0 : dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x96d
fffff880`066a3c50 fffff880`03d9716d : fffffa80`00000000 fffffa80`058ec410 00000000`0000000f fffff880`03d98f09 : dxgmms1!VidMmiProcessTerminationCommand+0x4c
fffff880`066a3ca0 fffff880`03d963f8 : fffff800`00b96080 fffffa80`042ba010 00000000`00000000 fffffa80`058ec410 : dxgmms1!VidSchiSubmitDeviceCommand+0x39
fffff880`066a3cd0 fffff880`03d95e96 : 00000000`00000000 fffffa80`042ba010 00000000`00000080 fffffa80`058ec410 : dxgmms1!VidSchiSubmitQueueCommand+0xb0
fffff880`066a3d00 fffff800`02d6f32e : 00000000`04c070f7 fffffa80`058e1b60 fffffa80`0396db30 fffffa80`058e1b60 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`066a3d40 fffff800`02ac4666 : fffff800`02c45e80 fffffa80`058e1b60 fffff800`02c53cc0 fffff880`01265384 : nt!PspSystemThreadStartup+0x5a
fffff880`066a3d80 00000000`00000000 : fffff880`066a4000 fffff880`0669e000 fffff880`066a3680 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+fec

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

STACK_COMMAND:  .cxr 0xfffff880066a2fe0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+fec

BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+fec

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

Maguscreed · 05-28-2011

Disable the hibernation feature on your system if it is on.

This could also be ram or overclock related.
I didn't see any mention that you had checked your memory there.
RAM - Test with Memtest86+
If you try memtest I suggest letting it run overnight 5-7 passes

I didn't see anything that jumped out at me in the driver dump. However I notice you say the card is new, was the previous card a different make?
If so it's possible there are still conflicts within the drivers there. Since most the crashes seem to try to point to direct x, it could simply be a case of the old drivers didn't fully remove properly before installing the drivers for the new card.

Easiest thing to do in that case would be to scrub any drivers this app can find (including your current ones)
Phyxion.net - Driver Sweeper
and doing a fresh resinstall with drivers freshly downloaded from amd/ati.

crash dump follows for reference driver dump included.

Code:

*******************************************************************************
*                                                                             *
*                        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: fffff88003d8e7ac, The address that the exception occurred at
Arg3: fffff880066a3788, Exception Record Address
Arg4: fffff880066a2fe0, 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_MEMORY_SEGMENT::EvictResource+fec
fffff880`03d8e7ac 488b11          mov     rdx,qword ptr [rcx]

EXCEPTION_RECORD:  fffff880066a3788 -- (.exr 0xfffff880066a3788)
ExceptionAddress: fffff88003d8e7ac (dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0x0000000000000fec)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000080000000
Attempt to read from address 0000000080000000

CONTEXT:  fffff880066a2fe0 -- (.cxr 0xfffff880066a2fe0)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000080000000
rdx=fffff8a007ab9e50 rsi=fffff8a007ab9e50 rdi=0000000000000000
rip=fffff88003d8e7ac rsp=fffff880066a39c0 rbp=fffffa8005922000
 r8=0000000000001000  r9=0000000000000000 r10=0000000000000001
r11=fffff8a007ab9f58 r12=0000000000000000 r13=0000000000000001
r14=fffffa80050c0ad0 r15=fffff8a007ab9f58
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_MEMORY_SEGMENT::EvictResource+0xfec:
fffff880`03d8e7ac 488b11          mov     rdx,qword ptr [rcx] ds:002b:00000000`80000000=????????????????
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:  0000000080000000

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d02100
 0000000080000000 

FOLLOWUP_IP: 
dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+fec
fffff880`03d8e7ac 488b11          mov     rdx,qword ptr [rcx]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff88003d7e25d to fffff88003d8e7ac

STACK_TEXT:  
fffff880`066a39c0 fffff880`03d7e25d : fffffa80`050c0ad0 fffff8a0`07ab9e50 fffffa80`04627300 fffffa80`05922000 : dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0xfec
fffff880`066a3b30 fffff880`03d79358 : fffffa80`03b0dba0 00000000`00000000 00000000`00000000 fffff880`066a3ca0 : dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x96d
fffff880`066a3c50 fffff880`03d9716d : fffffa80`00000000 fffffa80`058ec410 00000000`0000000f fffff880`03d98f09 : dxgmms1!VidMmiProcessTerminationCommand+0x4c
fffff880`066a3ca0 fffff880`03d963f8 : fffff800`00b96080 fffffa80`042ba010 00000000`00000000 fffffa80`058ec410 : dxgmms1!VidSchiSubmitDeviceCommand+0x39
fffff880`066a3cd0 fffff880`03d95e96 : 00000000`00000000 fffffa80`042ba010 00000000`00000080 fffffa80`058ec410 : dxgmms1!VidSchiSubmitQueueCommand+0xb0
fffff880`066a3d00 fffff800`02d6f32e : 00000000`04c070f7 fffffa80`058e1b60 fffffa80`0396db30 fffffa80`058e1b60 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`066a3d40 fffff800`02ac4666 : fffff800`02c45e80 fffffa80`058e1b60 fffff800`02c53cc0 fffff880`01265384 : nt!PspSystemThreadStartup+0x5a
fffff880`066a3d80 00000000`00000000 : fffff880`066a4000 fffff880`0669e000 fffff880`066a3680 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+fec

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

STACK_COMMAND:  .cxr 0xfffff880066a2fe0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+fec

BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+fec

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

1: kd> lm t n
start             end                 module name
fffff800`00bc5000 fffff800`00bcf000   kdcom    kdcom.dll    Sat Feb 05 10:52:49 2011 (4D4D8061)
fffff800`02a0a000 fffff800`02a53000   hal      hal.dll      Sat Nov 20 07:00:25 2010 (4CE7C669)
fffff800`02a53000 fffff800`0303c000   nt       ntkrnlmp.exe Fri Apr 08 23:15:23 2011 (4D9FDD5B)
fffff880`00c0b000 fffff880`00c5a000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Sat Nov 20 07:03:51 2010 (4CE7C737)
fffff880`00c5a000 fffff880`00c6e000   PSHED    PSHED.dll    Mon Jul 13 20:32:23 2009 (4A5BE027)
fffff880`00c6e000 fffff880`00ccc000   CLFS     CLFS.SYS     Mon Jul 13 18:19:57 2009 (4A5BC11D)
fffff880`00ccc000 fffff880`00d8c000   CI       CI.dll       Sat Nov 20 07:12:36 2010 (4CE7C944)
fffff880`00d8c000 fffff880`00d9c000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 18:19:48 2009 (4A5BC114)
fffff880`00d9c000 fffff880`00db6000   mountmgr mountmgr.sys Sat Nov 20 03:19:21 2010 (4CE79299)
fffff880`00db6000 fffff880`00de0000   ataport  ataport.SYS  Sat Nov 20 03:19:15 2010 (4CE79293)
fffff880`00de0000 fffff880`00deb000   amdxata  amdxata.sys  Fri Mar 19 11:18:18 2010 (4BA3A3CA)
fffff880`00e00000 fffff880`00e09000   WMILIB   WMILIB.SYS   Mon Jul 13 18:19:51 2009 (4A5BC117)
fffff880`00e09000 fffff880`00e13000   msisadrv msisadrv.sys Mon Jul 13 18:19:26 2009 (4A5BC0FE)
fffff880`00e13000 fffff880`00e46000   pci      pci.sys      Sat Nov 20 03:19:11 2010 (4CE7928F)
fffff880`00e46000 fffff880`00e53000   vdrvroot vdrvroot.sys Mon Jul 13 19:01:31 2009 (4A5BCADB)
fffff880`00e53000 fffff880`00e68000   partmgr  partmgr.sys  Sat Nov 20 03:20:00 2010 (4CE792C0)
fffff880`00e68000 fffff880`00e7d000   volmgr   volmgr.sys   Sat Nov 20 03:19:28 2010 (4CE792A0)
fffff880`00e7d000 fffff880`00ed9000   volmgrx  volmgrx.sys  Sat Nov 20 03:20:43 2010 (4CE792EB)
fffff880`00ed9000 fffff880`00ee0000   pciide   pciide.sys   Mon Jul 13 18:19:49 2009 (4A5BC115)
fffff880`00ee0000 fffff880`00ee9000   atapi    atapi.sys    Mon Jul 13 18:19:47 2009 (4A5BC113)
fffff880`00eee000 fffff880`00f92000   Wdf01000 Wdf01000.sys Mon Jul 13 18:22:07 2009 (4A5BC19F)
fffff880`00f92000 fffff880`00fa1000   WDFLDR   WDFLDR.SYS   Mon Jul 13 18:19:54 2009 (4A5BC11A)
fffff880`00fa1000 fffff880`00ff8000   ACPI     ACPI.sys     Sat Nov 20 03:19:16 2010 (4CE79294)
fffff880`01000000 fffff880`0102f000   ndiswan  ndiswan.sys  Sat Nov 20 04:52:32 2010 (4CE7A870)
fffff880`0102f000 fffff880`01050000   raspptp  raspptp.sys  Sat Nov 20 04:52:31 2010 (4CE7A86F)
fffff880`01050000 fffff880`0106a000   rassstp  rassstp.sys  Mon Jul 13 19:10:25 2009 (4A5BCCF1)
fffff880`01081000 fffff880`010cd000   fltmgr   fltmgr.sys   Sat Nov 20 03:19:24 2010 (4CE7929C)
fffff880`010cd000 fffff880`010e1000   fileinfo fileinfo.sys Mon Jul 13 18:34:25 2009 (4A5BC481)
fffff880`010e1000 fffff880`0113f000   msrpc    msrpc.sys    Sat Nov 20 03:21:56 2010 (4CE79334)
fffff880`0113f000 fffff880`011b1000   cng      cng.sys      Sat Nov 20 04:08:45 2010 (4CE79E2D)
fffff880`011b1000 fffff880`011d5000   rasl2tp  rasl2tp.sys  Sat Nov 20 04:52:34 2010 (4CE7A872)
fffff880`01200000 fffff880`0121b000   ksecdd   ksecdd.sys   Sat Nov 20 03:21:15 2010 (4CE7930B)
fffff880`0121b000 fffff880`0122c000   pcw      pcw.sys      Mon Jul 13 18:19:27 2009 (4A5BC0FF)
fffff880`0122c000 fffff880`01236000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 18:19:45 2009 (4A5BC111)
fffff880`01236000 fffff880`01251000   raspppoe raspppoe.sys Mon Jul 13 19:10:17 2009 (4A5BCCE9)
fffff880`01252000 fffff880`013f5000   Ntfs     Ntfs.sys     Sat Nov 20 03:20:57 2010 (4CE792F9)
fffff880`01400000 fffff880`01450000   atikmpag atikmpag.sys Tue Apr 19 20:22:32 2011 (4DAE3558)
fffff880`01450000 fffff880`01466000   AgileVpn AgileVpn.sys Mon Jul 13 19:10:24 2009 (4A5BCCF0)
fffff880`01466000 fffff880`01475000   mouclass mouclass.sys Mon Jul 13 18:19:50 2009 (4A5BC116)
fffff880`0147b000 fffff880`0156e000   ndis     ndis.sys     Sat Nov 20 03:23:30 2010 (4CE79392)
fffff880`0156e000 fffff880`015ce000   NETIO    NETIO.SYS    Sat Nov 20 03:23:13 2010 (4CE79381)
fffff880`015ce000 fffff880`015f9000   ksecpkg  ksecpkg.sys  Sat Nov 20 04:10:34 2010 (4CE79E9A)
fffff880`01600000 fffff880`0162a000   cdrom    cdrom.sys    Sat Nov 20 03:19:20 2010 (4CE79298)
fffff880`0162e000 fffff880`01832000   tcpip    tcpip.sys    Sat Nov 20 03:25:52 2010 (4CE79420)
fffff880`01832000 fffff880`0187c000   fwpkclnt fwpkclnt.sys Sat Nov 20 03:21:37 2010 (4CE79321)
fffff880`0187c000 fffff880`018c8000   volsnap  volsnap.sys  Sat Nov 20 03:20:08 2010 (4CE792C8)
fffff880`018c8000 fffff880`018d0000   spldr    spldr.sys    Mon May 11 11:56:27 2009 (4A0858BB)
fffff880`018d0000 fffff880`0190a000   rdyboost rdyboost.sys Sat Nov 20 03:43:10 2010 (4CE7982E)
fffff880`0190a000 fffff880`0191c000   mup      mup.sys      Mon Jul 13 18:23:45 2009 (4A5BC201)
fffff880`0191c000 fffff880`01925000   hwpolicy hwpolicy.sys Sat Nov 20 03:18:54 2010 (4CE7927E)
fffff880`01925000 fffff880`0195f000   fvevol   fvevol.sys   Sat Nov 20 03:24:06 2010 (4CE793B6)
fffff880`0195f000 fffff880`01975000   disk     disk.sys     Mon Jul 13 18:19:57 2009 (4A5BC11D)
fffff880`01975000 fffff880`019a5000   CLASSPNP CLASSPNP.SYS Sat Nov 20 03:19:23 2010 (4CE7929B)
fffff880`019a5000 fffff880`019c0000   USBSTOR  USBSTOR.SYS  Sat Nov 20 04:44:05 2010 (4CE7A675)
fffff880`019db000 fffff880`019eb000   CompositeBus CompositeBus.sys Sat Nov 20 04:33:17 2010 (4CE7A3ED)
fffff880`019eb000 fffff880`019f7000   ndistapi ndistapi.sys Mon Jul 13 19:10:00 2009 (4A5BCCD8)
fffff880`02662000 fffff880`02698000   fastfat  fastfat.SYS  Mon Jul 13 18:23:28 2009 (4A5BC1F0)
fffff880`02698000 fffff880`026a4000   dump_dumpata dump_dumpata.sys Mon Jul 13 18:19:47 2009 (4A5BC113)
fffff880`026a4000 fffff880`026ad000   dump_atapi dump_atapi.sys Mon Jul 13 18:19:47 2009 (4A5BC113)
fffff880`026ad000 fffff880`026c0000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 18:21:51 2009 (4A5BC18F)
fffff880`026c0000 fffff880`026ce000   monitor  monitor.sys  Mon Jul 13 18:38:52 2009 (4A5BC58C)
fffff880`026ce000 fffff880`026f1000   luafv    luafv.sys    Mon Jul 13 18:26:13 2009 (4A5BC295)
fffff880`026f1000 fffff880`0272b000   aswMonFlt aswMonFlt.sys Tue May 10 06:59:47 2011 (4DC928B3)
fffff880`0272b000 fffff880`02734000   aswFsBlk aswFsBlk.SYS Tue May 10 06:59:36 2011 (4DC928A8)
fffff880`02734000 fffff880`02755000   WudfPf   WudfPf.sys   Sat Nov 20 04:42:44 2010 (4CE7A624)
fffff880`02755000 fffff880`0276a000   lltdio   lltdio.sys   Mon Jul 13 19:08:50 2009 (4A5BCC92)
fffff880`0276a000 fffff880`02782000   rspndr   rspndr.sys   Mon Jul 13 19:08:50 2009 (4A5BCC92)
fffff880`03a00000 fffff880`03a26000   tunnel   tunnel.sys   Sat Nov 20 04:51:50 2010 (4CE7A846)
fffff880`03a26000 fffff880`03a3c000   intelppm intelppm.sys Mon Jul 13 18:19:25 2009 (4A5BC0FD)
fffff880`03a40000 fffff880`03ad8000   aswSnx   aswSnx.SYS   Tue May 10 07:04:06 2011 (4DC929B6)
fffff880`03ad8000 fffff880`03ae1000   Null     Null.SYS     Mon Jul 13 18:19:37 2009 (4A5BC109)
fffff880`03ae1000 fffff880`03ae8000   Beep     Beep.SYS     Mon Jul 13 19:00:13 2009 (4A5BCA8D)
fffff880`03ae8000 fffff880`03af6000   vga      vga.sys      Mon Jul 13 18:38:47 2009 (4A5BC587)
fffff880`03af6000 fffff880`03b1b000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 18:38:51 2009 (4A5BC58B)
fffff880`03b1b000 fffff880`03b2b000   watchdog watchdog.sys Mon Jul 13 18:37:35 2009 (4A5BC53F)
fffff880`03b2b000 fffff880`03b34000   RDPCDD   RDPCDD.sys   Mon Jul 13 19:16:34 2009 (4A5BCE62)
fffff880`03b34000 fffff880`03b3d000   rdpencdd rdpencdd.sys Mon Jul 13 19:16:34 2009 (4A5BCE62)
fffff880`03b3d000 fffff880`03b46000   rdprefmp rdprefmp.sys Mon Jul 13 19:16:35 2009 (4A5BCE63)
fffff880`03b46000 fffff880`03b51000   Msfs     Msfs.SYS     Mon Jul 13 18:19:47 2009 (4A5BC113)
fffff880`03b51000 fffff880`03b62000   Npfs     Npfs.SYS     Mon Jul 13 18:19:48 2009 (4A5BC114)
fffff880`03b62000 fffff880`03b84000   tdx      tdx.sys      Sat Nov 20 03:21:54 2010 (4CE79332)
fffff880`03b84000 fffff880`03b91000   TDI      TDI.SYS      Sat Nov 20 03:22:06 2010 (4CE7933E)
fffff880`03b91000 fffff880`03ba1000   aswTdi   aswTdi.SYS   Tue May 10 07:02:40 2011 (4DC92960)
fffff880`03ba1000 fffff880`03bb2000   blbdrive blbdrive.sys Mon Jul 13 18:35:59 2009 (4A5BC4DF)
fffff880`03bb2000 fffff880`03bff000   aswSP    aswSP.SYS    Tue May 10 07:04:06 2011 (4DC929B6)
fffff880`03c00000 fffff880`03c56000   USBPORT  USBPORT.SYS  Sat Nov 20 04:44:00 2010 (4CE7A670)
fffff880`03c56000 fffff880`03c67000   usbehci  usbehci.sys  Sat Nov 20 04:43:54 2010 (4CE7A66A)
fffff880`03c6a000 fffff880`03d5e000   dxgkrnl  dxgkrnl.sys  Sat Nov 20 03:50:50 2010 (4CE799FA)
fffff880`03d5e000 fffff880`03da4000   dxgmms1  dxgmms1.sys  Sat Nov 20 03:49:53 2010 (4CE799C1)
fffff880`03da4000 fffff880`03dc8000   HDAudBus HDAudBus.sys Sat Nov 20 04:43:42 2010 (4CE7A65E)
fffff880`03dc8000 fffff880`03dd5000   usbuhci  usbuhci.sys  Mon Jul 13 19:06:27 2009 (4A5BCC03)
fffff880`03dd5000 fffff880`03de2000   fdc      fdc.sys      Mon Jul 13 19:00:54 2009 (4A5BCAB6)
fffff880`03de2000 fffff880`03dee000   serenum  serenum.sys  Mon Jul 13 19:00:33 2009 (4A5BCAA1)
fffff880`03dee000 fffff880`03dfd000   kbdclass kbdclass.sys Mon Jul 13 18:19:50 2009 (4A5BC116)
fffff880`03dfd000 fffff880`03dfe480   swenum   swenum.sys   Mon Jul 13 19:00:18 2009 (4A5BCA92)
fffff880`03e00000 fffff880`03e1b000   wanarp   wanarp.sys   Sat Nov 20 04:52:36 2010 (4CE7A874)
fffff880`03e1b000 fffff880`03e2f000   termdd   termdd.sys   Sat Nov 20 05:03:40 2010 (4CE7AB0C)
fffff880`03e2f000 fffff880`03e80000   rdbss    rdbss.sys    Sat Nov 20 03:27:51 2010 (4CE79497)
fffff880`03e80000 fffff880`03e8c000   nsiproxy nsiproxy.sys Mon Jul 13 18:21:02 2009 (4A5BC15E)
fffff880`03e8c000 fffff880`03e97000   mssmbios mssmbios.sys Mon Jul 13 18:31:10 2009 (4A5BC3BE)
fffff880`03e97000 fffff880`03ea6000   discache discache.sys Mon Jul 13 18:37:18 2009 (4A5BC52E)
fffff880`03ea6000 fffff880`03ec4000   dfsc     dfsc.sys     Sat Nov 20 03:26:31 2010 (4CE79447)
fffff880`03ec7000 fffff880`03f50000   afd      afd.sys      Sat Nov 20 03:23:27 2010 (4CE7938F)
fffff880`03f50000 fffff880`03f5a000   aswRdr   aswRdr.SYS   Tue May 10 06:59:58 2011 (4DC928BE)
fffff880`03f5a000 fffff880`03f9f000   netbt    netbt.sys    Sat Nov 20 03:23:18 2010 (4CE79386)
fffff880`03f9f000 fffff880`03fa8000   wfplwf   wfplwf.sys   Mon Jul 13 19:09:26 2009 (4A5BCCB6)
fffff880`03fa8000 fffff880`03fce000   pacer    pacer.sys    Sat Nov 20 04:52:18 2010 (4CE7A862)
fffff880`03fce000 fffff880`03fdd000   netbios  netbios.sys  Mon Jul 13 19:09:26 2009 (4A5BCCB6)
fffff880`03fdd000 fffff880`03ffa000   serial   serial.sys   Mon Jul 13 19:00:40 2009 (4A5BCAA8)
fffff880`04200000 fffff880`04222000   drmk     drmk.sys     Mon Jul 13 20:01:25 2009 (4A5BD8E5)
fffff880`04222000 fffff880`04227200   ksthunk  ksthunk.sys  Mon Jul 13 19:00:19 2009 (4A5BCA93)
fffff880`04228000 fffff880`04236000   hidusb   hidusb.sys   Sat Nov 20 04:43:49 2010 (4CE7A665)
fffff880`04236000 fffff880`0424f000   HIDCLASS HIDCLASS.SYS Sat Nov 20 04:43:49 2010 (4CE7A665)
fffff880`0424f000 fffff880`04257080   HIDPARSE HIDPARSE.SYS Mon Jul 13 19:06:17 2009 (4A5BCBF9)
fffff880`04258000 fffff880`04259f00   USBD     USBD.SYS     Mon Jul 13 19:06:23 2009 (4A5BCBFF)
fffff880`0425a000 fffff880`04268000   kbdhid   kbdhid.sys   Sat Nov 20 04:33:25 2010 (4CE7A3F5)
fffff880`04268000 fffff880`04274000   Dxapi    Dxapi.sys    Mon Jul 13 18:38:28 2009 (4A5BC574)
fffff880`04280000 fffff880`042c3000   ks       ks.sys       Sat Nov 20 04:33:23 2010 (4CE7A3F3)
fffff880`042c3000 fffff880`042d5000   umbus    umbus.sys    Sat Nov 20 04:44:37 2010 (4CE7A695)
fffff880`042d5000 fffff880`0432f000   usbhub   usbhub.sys   Sat Nov 20 04:44:30 2010 (4CE7A68E)
fffff880`0432f000 fffff880`0433a000   flpydisk flpydisk.sys Mon Jul 13 19:00:54 2009 (4A5BCAB6)
fffff880`0433a000 fffff880`0434f000   NDProxy  NDProxy.SYS  Sat Nov 20 04:52:20 2010 (4CE7A864)
fffff880`0434f000 fffff880`043ab000   HdAudio  HdAudio.sys  Sat Nov 20 04:44:23 2010 (4CE7A687)
fffff880`043ab000 fffff880`043e8000   portcls  portcls.sys  Mon Jul 13 19:06:27 2009 (4A5BCC03)
fffff880`043e8000 fffff880`043f6000   crashdmp crashdmp.sys Mon Jul 13 19:01:01 2009 (4A5BCABD)
fffff880`04800000 fffff880`04832000   Rt64win7 Rt64win7.sys Thu Feb 26 03:04:13 2009 (49A65B0D)
fffff880`04832000 fffff880`04870000   1394ohci 1394ohci.sys Sat Nov 20 04:44:56 2010 (4CE7A6A8)
fffff880`04870000 fffff880`0488d000   parport  parport.sys  Mon Jul 13 19:00:40 2009 (4A5BCAA8)
fffff880`0488d000 fffff880`048ab000   i8042prt i8042prt.sys Mon Jul 13 18:19:57 2009 (4A5BC11D)
fffff880`048ab000 fffff880`048b6000   rdpbus   rdpbus.sys   Mon Jul 13 19:17:46 2009 (4A5BCEAA)
fffff880`048b6000 fffff880`051ea000   atikmdag atikmdag.sys Tue Apr 19 20:53:29 2011 (4DAE3C99)
fffff880`051ea000 fffff880`051f7000   GEARAspiWDM GEARAspiWDM.sys Mon May 18 07:17:04 2009 (4A1151C0)
fffff880`06e2c000 fffff880`06ef5000   HTTP     HTTP.sys     Sat Nov 20 03:24:30 2010 (4CE793CE)
fffff880`06ef5000 fffff880`06f13000   bowser   bowser.sys   Tue Feb 22 22:55:04 2011 (4D649328)
fffff880`06f13000 fffff880`06f2b000   mpsdrv   mpsdrv.sys   Mon Jul 13 19:08:25 2009 (4A5BCC79)
fffff880`06f2b000 fffff880`06f58000   mrxsmb   mrxsmb.sys   Tue Feb 22 22:56:22 2011 (4D649376)
fffff880`06f58000 fffff880`06fa5000   mrxsmb10 mrxsmb10.sys Tue Feb 22 22:55:12 2011 (4D649330)
fffff880`06fa5000 fffff880`06fc9000   mrxsmb20 mrxsmb20.sys Tue Feb 22 22:55:12 2011 (4D649330)
fffff880`08e1a000 fffff880`08ec0000   peauth   peauth.sys   Mon Jul 13 20:01:19 2009 (4A5BD8DF)
fffff880`08ec0000 fffff880`08ecb000   secdrv   secdrv.SYS   Wed Sep 13 08:18:38 2006 (4508052E)
fffff880`08ecb000 fffff880`08efc000   srvnet   srvnet.sys   Tue Feb 22 22:55:44 2011 (4D649350)
fffff880`08efc000 fffff880`08f0e000   tcpipreg tcpipreg.sys Sat Nov 20 04:51:48 2010 (4CE7A844)
fffff880`08f0e000 fffff880`08f78000   srv2     srv2.sys     Tue Feb 22 22:56:00 2011 (4D649360)
fffff880`0929c000 fffff880`09334000   srv      srv.sys      Tue Feb 22 22:56:21 2011 (4D649375)
fffff880`093a0000 fffff880`093ad000   mouhid   mouhid.sys   Mon Jul 13 19:00:20 2009 (4A5BCA94)
fffff880`093d6000 fffff880`093e1000   asyncmac asyncmac.sys Mon Jul 13 19:10:13 2009 (4A5BCCE5)
fffff960`00020000 fffff960`00332000   win32k   win32k.sys   unavailable (00000000)
fffff960`004b0000 fffff960`004ba000   TSDDD    TSDDD.dll    unavailable (00000000)
fffff960`00750000 fffff960`00777000   cdd      cdd.dll      unavailable (00000000)

Unloaded modules:
fffff880`09271000 fffff880`0927d000   hiber_atapor
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000C000
fffff880`0927d000 fffff880`09286000   hiber_atapi.
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00009000
fffff880`09286000 fffff880`09299000   hiber_dumpfv
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00013000
fffff880`09200000 fffff880`09271000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00071000
fffff880`09334000 fffff880`09365000   WUDFRd.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00031000
fffff880`09378000 fffff880`09384000   hiber_atapor
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000C000
fffff880`09384000 fffff880`0938d000   hiber_atapi.
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00009000
fffff880`0938d000 fffff880`093a0000   hiber_dumpfv
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00013000
fffff880`093e1000 fffff880`093ee000   mouhid.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000D000
fffff880`0927a000 fffff880`09286000   hiber_atapor
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000C000
fffff880`09286000 fffff880`0928f000   hiber_atapi.
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00009000
fffff880`09365000 fffff880`09378000   hiber_dumpfv
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00013000
fffff880`09200000 fffff880`09271000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00071000
fffff880`09271000 fffff880`0927a000   cpuz135_x64.
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00009000
fffff880`09365000 fffff880`093d6000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00071000
fffff880`019a5000 fffff880`019b3000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000E000
fffff880`019b3000 fffff880`019bf000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000C000
fffff880`019bf000 fffff880`019c8000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00009000
fffff880`019c8000 fffff880`019db000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00013000

nintendo2024 · 05-28-2011

I actually already ran Memtest86+, as I stated above.
I ran it for 12 hours on each stick on it's respective slot, and there were no errors. When BSODS continued, I moved the RAM to other slots on the motherboard, and errors still arose, so I did a 12 hour test with them together, and no errors arose. I still continued to have BSODs, so I tested them both at the same time for 24 hours, and there were no errors, but I still continued to have issues, so I'm not sure if the memory is at fault?

I have cleaned all the drivers off from the computer before I installed my new drivers from the website, and I still continued to have BSODs, but I will try it again and hope that it works this time.

Maguscreed · 05-28-2011

If that does not work we will probably want to try the driver verifier route as one last attempt to solve the problem from a software perspective.
I would hold off on this until the very last item as it can be a major pain to deal with in some circumstances. It would however create some new more detailed memory dumps for us to look at.
Driver Verifier - Enable and Disable
I suggest reading that entire post before attempting it, as it can leave the system unbootable in extreme instances and you'll need to know how to recover it to normal state before starting.

nintendo2024 · 05-29-2011

Quote: Originally Posted by Maguscreed

If that does not work we will probably want to try the driver verifier route as one last attempt to solve the problem from a software perspective.
I would hold off on this until the very last item as it can be a major pain to deal with in some circumstances. It would however create some new more detailed memory dumps for us to look at.
Driver Verifier - Enable and Disable
I suggest reading that entire post before attempting it, as it can leave the system unbootable in extreme instances and you'll need to know how to recover it to normal state before starting.

Ok, so I uninstalled all of the software for the video card, as well as used Driver Sweeper in Safe Mode to uninstall the drivers, and then rebooted and ONLY installed the drivers for the video card straight from the ATI website, and rebooted, but after an hour or so of use, it BSOD again with the dxgmms1.sys BSOD.

Should I go ahead and do the driver verification route?

Maguscreed · 05-29-2011

What I'm seeing around the net is a consistent suggestion to actually use the previous driver and not the most current.
The only other things I've seen that ended well for people involved were replace graphics card, replace motherboard.
In several cases even replacing the hardware didn't seem to solve this issue though.

I would try using a older ati driver version first.

nintendo2024 · 05-29-2011

Quote: Originally Posted by Maguscreed

What I'm seeing around the net is a consistent suggestion to actually use the previous driver and not the most current.
The only other things I've seen that ended well for people involved were replace graphics card, replace motherboard.
In several cases even replacing the hardware didn't seem to solve this issue though.

I would try using a older ati driver version first.

How would I go about rolling back my driver to an older version? And if no older version is able to fix my issue, is there any surefire way to know whether my motherboard is the culprit? Does that mean I won't need to use the previous advice?

Maguscreed · 05-29-2011

I suggest trying absolutely everything before replacing hardware obviously.
here's the previous drivers that should be functional for your card, though I wouldn't go more than 2 versions back
Previous Catalyst

nintendo2024 · 05-29-2011

Quote: Originally Posted by Maguscreed

I suggest trying absolutely everything before replacing hardware obviously.
here's the previous drivers that should be functional for your card, though I wouldn't go more than 2 versions back
Previous Catalyst

So I would just repeat the process I did for removing drivers and reinstalling drivers, but instead install the older versions? And then if I have a similar issue with the previous version, then just try with the one before it?

I'll give it a go and report back, hopefully with good news.

Windows 7 - dxgmms1.sys, IRQL_NOT, and win32k.sys BSODS

dxgmms1.sys, IRQL_NOT, and win32k.sys BSODS problems?