BSOD, especially while playing Skyrim

I am having frequent BSOD's while playing Skyrim, and sometimes shortly after. The most common one involves the file dxgmms1.sys.

I have attached my computer specs and the minidump file. Thank you for your help!

 

Hi, Rob.

It looks very much like a driver issue, a misbehaving, old, or badly written driver, perhaps, interfering with the DirectX/graphics.

Most likely drivers:

UsbFltr.sys Mon Apr 9 11:09:44 2007 (461A10E8)
Ortek USB Keypad Driver by Waytech Development (may be a part of Razer Tarantula drivers also)
http://www.carrona.org/drivers/driver.php?id=UsbFltr.sys

AODDriver2.sys Thu Sep 12 04:36:40 2013 (523136C8)
AMD Overdrive; also in EasyTune6 for Gigabyte motherboard [br] Known BSOD issues in Win7
http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys

IOMap64.sys Tue Feb 19 09:29:22 2013 (512345F2)
ASUS Kernel Mode Driver ?Asus Smart Doctor/iTracker 2
http://www.carrona.org/drivers/driver.php?id=IOMap64.sys

Symantec/Norton suite's involvement is possible, too.

Try to find a later USB/mouse driver and uninstall the motherboard/graphics utilities for the lower two drivers. Uninstalling Norton during troubleshooting is often a good plan, use MSE x64 instead.

Code:

5: kd> !analyze -v; !sysinfo cpuspeed; !sysinfo SMBIOS; lmtsmn; q
*******************************************************************************
*                                                                             *
*                        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: fffff88011223eb0, The address that the exception occurred at
Arg3: fffff8800413c688, Exception Record Address
Arg4: fffff8800413bee0, 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::IsPagingOperationPending+4c
fffff880`11223eb0 4939040a        cmp     qword ptr [r10+rcx],rax

EXCEPTION_RECORD:  fffff8800413c688 -- (.exr 0xfffff8800413c688)
.exr 0xfffff8800413c688
ExceptionAddress: fffff88011223eb0 (dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+0x000000000000004c)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff8800413bee0 -- (.cxr 0xfffff8800413bee0)
.cxr 0xfffff8800413bee0
rax=000000000000e6c0 rbx=fffff8a003e71340 rcx=ffcff8a003e7a060
rdx=0000000000000004 rsi=0000000000000004 rdi=000000000000000a
rip=fffff88011223eb0 rsp=fffff8800413c8c8 rbp=0000000000000000
 r8=0000000000000004  r9=000000000000000a r10=0000000000000020
r11=fffffa800a6ae3c8 r12=0000000000000002 r13=0000000000000000
r14=fffffa80069acb40 r15=0000000000000019
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+0x4c:
fffff880`11223eb0 4939040a        cmp     qword ptr [r10+rcx],rax ds:002b:ffcff8a0`03e7a080=????????????????
.cxr
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_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 fffff80003101100
GetUlongFromAddress: unable to read from fffff800031011c0
 ffffffffffffffff 

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+4c
fffff880`11223eb0 4939040a        cmp     qword ptr [r10+rcx],rax

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff88011221162 to fffff88011223eb0

STACK_TEXT:  
fffff880`0413c8c8 fffff880`11221162 : fffff8a0`03e71340 fffffa80`0b5df190 fffffa80`0a6ad000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+0x4c
fffff880`0413c8d0 fffff880`1121e9d3 : 00000000`00000000 fffffa80`0b53c010 00000000`00000017 fffffa80`0b79e038 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xda
fffff880`0413c910 fffff880`112387d9 : fffffa80`00000000 fffff8a0`03e787e0 fffffa80`00000000 fffffa80`069acb40 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b
fffff880`0413cae0 fffff880`11238514 : fffff880`0328cfc0 fffff880`11237f00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`0413ccd0 fffff880`11238012 : 00000000`00000000 fffffa80`074a9b20 00000000`00000080 fffffa80`0a448410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`0413cd00 fffff800`031662ea : 00000000`12f86e75 fffffa80`0a1528b0 fffffa80`06a0a840 fffffa80`0a1528b0 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`0413cd40 fffff800`02eba8e6 : fffff880`03288180 fffffa80`0a1528b0 fffff880`03293040 576d474c`6a555032 : nt!PspSystemThreadStartup+0x5a
fffff880`0413cd80 00000000`00000000 : fffff880`0413d000 fffff880`04137000 fffff880`0413c680 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13

STACK_COMMAND:  .cxr 0xfffff8800413bee0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+4c

BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+4c

Followup: MachineOwner

 

Thanks!

I uninstalled the GPU software and Norton. I updated all my drivers, but I'm not sure if I got the USB driver. Is there a way to check that?

 

DriverView (x64) will allow you to check driver dates, View > Hide Microsoft drivers and under Choose columns, select Modified date.

You want as few 3rd party drivers pre -dating SP1 as possible so aim for 2012 onwards for hardware drivers and try to keep utility/software drivers loaded to a minimum.