Repeated BSOD in graphics intensive environments

Xelvonar · 29 Dec 2009

Hi y'all,

Build my first system and its running well except it sometimes crashes when running graphics intensive programs. The most frequent crash is IRQL_LESS_THAN_EQUAL but I've also seen some others, including something about an attempt to write read-only memory. I've updated all drives repeatedly and used memtest86 on both sticks of memory separately (but not together). The crashes are intermittent: sometimes I can get 20-30 minutes of game play in, other times its only a minute or two. I attached a zip of 5 recent dumps.
Any help is appreciated! Thanks

-Bill

zigzag3143 · 29 Dec 2009

Xelvonar said:

Hi y'all,

Build my first system and its running well except it sometimes crashes when running graphics intensive programs. The most frequent crash is IRQL_LESS_THAN_EQUAL but I've also seen some others, including something about an attempt to write read-only memory. I've updated all drives repeatedly and used memtest86 on both sticks of memory separately (but not together). The crashes are intermittent: sometimes I can get 20-30 minutes of game play in, other times its only a minute or two. I attached a zip of 5 recent dumps.
Any help is appreciated! Thanks

-Bill

Bill Its pretty clear that there us a memory problem here

I would
download memtestx86 nd run 5 passes on it

Ken J+

part one

Code:

122409-15490-01.dmp    12/24/2009 8:47:57 AM    ATTEMPTED_WRITE_TO_READONLY_MEMORY    0x000000be    0x8dbad1bc    0x7b233121    0x807e5cf8    0x0000000a    mouclass.sys    mouclass.sys+41bc                    
122409-15397-01.dmp    12/24/2009 5:40:44 PM    DRIVER_IRQL_NOT_LESS_OR_EQUAL    0x000000d1    0xc8eff240    0x00000002    0x00000000    0x8e96231d    mouclass.sys    mouclass.sys+131d                    
122809-23431-01.dmp    12/28/2009 7:57:03 AM    DRIVER_IRQL_NOT_LESS_OR_EQUAL    0x000000d1    0xcdf82324    0x00000002    0x00000000    0x88eb07c4    tcpip.sys    tcpip.sys+7d7c4                    
122709-17596-01.dmp    12/27/2009 5:12:11 PM    IRQL_NOT_LESS_OR_EQUAL    0x0000000a    0x00000000    0x00000002    0x00000000    0x82b344bf    ntkrnlpa.exe    ntkrnlpa.exe+467eb                    
minidump.dmp    12/30/2009 2:17:54 AM    MEMORY_MANAGEMENT    0x0000001a    0x00041284    0x0b5ce001    0x00000000    0xc0802000    ntkrnlpa.exe    ntkrnlpa.exe+dcd10                    
122409-15771-01.dmp    12/24/2009 11:08:35 AM    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED    0x1000007e    0xc0000005    0x8dc8ed47    0x8aad2a1c    0x8aad2600    dxgmms1.sys    dxgmms1.sys+9d47

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\122409-15490-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82a4f000 PsLoadedModuleList = 0x82b97810
Debug session time: Thu Dec 24 11:46:27.502 2009 (GMT-5)
System Uptime: 0 days 2:23:49.938
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.....
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory.  The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: 8dbad1bc, Virtual address for the attempted write.
Arg2: 7b233121, PTE contents.
Arg3: 807e5cf8, (reserved)
Arg4: 0000000a, (reserved)

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xBE

PROCESS_NAME:  hl2.exe

CURRENT_IRQL:  2

TRAP_FRAME:  807e5cf8 -- (.trap 0xffffffff807e5cf8)
ErrCode = 00000003
eax=807e5d88 ebx=00000000 ecx=a1ff6e58 edx=00000000 esi=882310e8 edi=8dbad1bc
eip=8dbab5cc esp=807e5d6c ebp=807e5d88 iopl=0         nv up ei ng nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
mouclass!MouseClassServiceCallback+0x2e6:
8dbab5cc f08945f0        lock mov dword ptr [ebp-10h],eax ss:0010:807e5d78=a1ff6e58
Resetting default scope

MISALIGNED_IP: 
mouclass!MouseClassServiceCallback+2e6
8dbab5cc f08945f0        lock mov dword ptr [ebp-10h],eax

LAST_CONTROL_TRANSFER:  from 82a955f8 to 82ad48e3

STACK_TEXT:  
807e5ce0 82a955f8 00000001 8dbad1bc 00000000 nt!MmAccessFault+0x106
807e5ce0 8dbab5cc 00000001 8dbad1bc 00000000 nt!KiTrap0E+0xdc
807e5d88 8ff11664 000000f0 88235f88 00000018 mouclass!MouseClassServiceCallback+0x2e6
807e5dbc 82ab7b33 00000000 02000000 01235ea0 mouhid!MouHid_ReadComplete+0x53a
807e5e04 8fef3424 807e5e0c 807e5e0c 88222020 nt!IopfCompleteRequest+0x128
807e5e20 8fef35df 02222008 848a2180 00000007 HIDCLASS!HidpDistributeInterruptReport+0xce
807e5e5c 82ab7b33 00000000 8489e268 88217a54 HIDCLASS!HidpInterruptReadComplete+0x1a7
807e5ea0 8db3d868 82a8f334 9e6ed760 00000000 nt!IopfCompleteRequest+0x128
807e5ed0 8db3e178 883c37c8 8489e268 8802d640 USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x6e0
807e5efc 8db419af 86140028 861400f0 86140a98 USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x33b
807e5f24 8db3bd18 86140028 86140a98 86140002 USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xbc
807e5f48 82ab73b5 86140aa4 86140002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
807e5fa4 82ab7218 807c5120 88318030 00000000 nt!KiExecuteAllDpcs+0xf9
807e5ff4 82ab69dc a0ca7ce4 00000000 00000000 nt!KiRetireDpcList+0xd5
807e5ff8 a0ca7ce4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
WARNING: Frame IP not in any known module. Following frames may be wrong.
82ab69dc 00000000 0000001a 00d6850f bb830000 0xa0ca7ce4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
mouclass!MouseClassServiceCallback+2e6
8dbab5cc f08945f0        lock mov dword ptr [ebp-10h],eax

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  mouclass!MouseClassServiceCallback+2e6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  IP_MISALIGNED_mouclass.sys

BUCKET_ID:  IP_MISALIGNED_mouclass.sys

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

Xelvonar · 30 Dec 2009

Well, I ran 5 passes and all five came up clean. I'll try some more tomorrow. Thanks again.

Xelvonar · 30 Dec 2009

5 more passes this morning and all clean. TF2 ran smoothly so far today, Sims 3 crashed almost immediately (not a BSOD, but it hung and I had to power down). I'm not sure what to do. I'm attaching the entire Minidump folder.

Once again, any suggestions are more than welcome. Thanks

-Bill

usasma · 31 Dec 2009

Lot's of different errors. Start with this:

H/W Diagnostics:
Please start by running these hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

More to follow after running the 28 memory dump files.....

Another thought, please try running this graphics stress/stability test: http://www.ozone3d.net/benchmarks/fur/

usasma · 31 Dec 2009

Errors all over the place - most likely a hardware issue (could be compatibility also)
Gigabyte 45 series boards seem to have issues with memory - Please check the Gigabyte and Crucial forums for advice on adjusting the settings/timings/voltages on your RAM.

Next, please replace these drivers with the latest Win7 drivers available from the manufacturer's website (NOT Windows Update or the Update drivers function in Device Manager):

Code:

SCDEmu.SYS   Thu Jun 12 02:28:49 2008
ctac32k.sys  Wed Jul 02 03:42:27 2008

Summary of the BSOD's:

Code:

BugCheck D1, {1, 2, 0, 8e09c3cd}
Probably caused by : hardware ( USBPORT!USBPORT_TxCsqRemoveIrp+4b )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck D1, {0, 4, 1, 8e0a7de5}
Probably caused by : nvlddmkm.sys ( nvlddmkm+6bde5 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck D1, {3e8, 2, 1, 8dd32fc4}
Probably caused by : Rt86win7.sys ( Rt86win7+10fc4 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck D1, {3e8, 2, 1, 8d93ffc4}
Probably caused by : Rt86win7.sys ( Rt86win7+10fc4 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 1000008E, {c000001d, 8f801644, 8078ad04, 0}
Probably caused by : hidusb.sys ( hidusb!HumReadReport+ef )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck D1, {8eddcce1, 2, 0, 8e4b5f5f}
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+122 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 1000008E, {c0000005, 887bbdc0, a6ccbb94, 0}
Probably caused by : fltmgr.sys ( fltmgr!FltpPerformFastIoCall+2 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck D1, {3e8, 2, 1, 8e105fc4}
Probably caused by : Rt86win7.sys ( Rt86win7+10fc4 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck D1, {1, 2, 1, 8f1166cd}
Probably caused by : nvlddmkm.sys ( nvlddmkm+1156cd )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck D1, {ffffffff, 2, 1, 8d901fbf}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiProcessDpcVSyncCookie+3c7 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 1000008E, {c000001d, 8ee7ee40, 8078aac8, 0}
Probably caused by : nvlddmkm.sys ( nvlddmkm+6be40 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck D1, {3e8, 2, 1, 8ee10fc4}
Probably caused by : Rt86win7.sys ( Rt86win7+10fc4 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck D1, {71d7e547, 2, 8, 71d7e547}
Probably caused by : Rt86win7.sys ( Rt86win7+ce8a )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck D1, {1, 2, 1, 84c56008}
Probably caused by : tcpip.sys ( tcpip!WfpAleMatchStatefulEndpoint+95 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 1000008E, {c0000005, 56795911, 9d67f3a4, 0}
Probably caused by : nvlddmkm.sys ( nvlddmkm+93388 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck D1, {0, 2, 1, 8c137bc6}
Probably caused by : ctaud2k.sys ( ctaud2k+5bc6 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck D1, {c8eff240, 2, 0, 8e96231d}
Probably caused by : mouclass.sys ( mouclass!WPP_RECORDER_SF_sd+33 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 1000007E, {c0000005, 8dc8ed47, 8aad2a1c, 8aad2600}
Probably caused by : hardware ( dxgmms1!VidSchiSendToExecutionQueue+33 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck A, {0, 2, 0, 82b344bf}
Probably caused by : ntkrpamp.exe ( nt!PpmPerfSelectDomainStates+bd )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck D1, {cdf82324, 2, 0, 88eb07c4}
Probably caused by : tcpip.sys ( tcpip!WfpAleFindRemoteEndpoint+137 )