New
#1
BSOD only when gaming, drvers new, dmp included
Ok I have a clean install of Windows 7 (as of about 2 months ago). The system is very stable EXCEPT when gaming. I'm not a hardcore gamer, in fact all I play is COD-MW2. However, I get BSOD eventually when playing. Sometimes it takes 5 minutes, sometimes over an hour, but I almost always get it. It did this same thing on two seperate installs of W7, the RC and the RTM which I have now.
I've checked the main culprits: sound, video and network drivers are all updated. Video is to ATI's latest (4-28-10) and sound and network are latest from gigabytes web page. I did try resolving this myself by searching others problems, but they all point to driver issues.
AMD Phenom II X3 710 (3 cores at 2.6ghz)
Gigabyte GA-MA790xt-UD4P (Rev 1.0)
Crucial (?) DDR3 PC1333
Radeon HD4670
On-board Sound (Realtek)
Thanks in advance for your help!
I've never pulled a dump file before, but I think I did it right. here goes:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ryan\Desktop\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: SRV*c:\websymbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c12000 PsLoadedModuleList = 0xfffff800`02e4fe50
Debug session time: Tue May 4 19:49:03.005 2010 (UTC - 7:00)
System Uptime: 0 days 0:14:46.769
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {4, 2, 8, 4}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000004, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000004, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 0000000000000004
CURRENT_IRQL: 2
FAULTING_IP:
+3730383235323163
00000000`00000004 ?? ???
PROCESS_NAME: System
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
TRAP_FRAME: fffff88009233590 -- (.trap 0xfffff88009233590)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800415be30
rdx=0000000000000004 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000004 rsp=fffff88009233720 rbp=fffffa8004231f80
r8=0000000000000000 r9=0000000000000000 r10=fffffa800415bf80
r11=fffff88009233720 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
00000000`00000004 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c81b69 to fffff80002c82600
FAILED_INSTRUCTION_ADDRESS:
+3730383235323163
00000000`00000004 ?? ???
STACK_TEXT:
fffff880`09233448 fffff800`02c81b69 : 00000000`0000000a 00000000`00000004 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff880`09233450 fffff800`02c807e0 : 00000000`00200046 fffffa80`0415be30 00000000`00000001 00000000`00000004 : nt!KiBugCheckDispatch+0x69
fffff880`09233590 00000000`00000004 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0415be30 : nt!KiPageFault+0x260
fffff880`09233720 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`0415be30 00000000`00000032 : 0x4
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiPageFault+260
fffff800`02c807e0 440f20c0 mov rax,cr8
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiPageFault+260
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb
FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260
BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260
Followup: MachineOwner
---------