GTX 470 video card crashes 5-30 minutes in to every game of Starcraft 2. Almost always an IRQL Less Than or Equal Error (see below). Glanced at my IRQs and saw several conflicts involving the GTX 470 - is this normal, and might one or more of these conflicts be causing the BSODs?
System:
Asus P6X58D Premium
i7 930 (cooled by Megahalems Rev. B w/ 2 120mm Yate Loon fans in push/pull config)
6GB Corsair Dominator
eVGA GTX 470 superclocked
Intel X-25 SSD (OS)
WD 1TB black HDD
Samsung DVD-RW/CD-RW
HAF 932 case (stock fans plus Yate Loon 120mm fan on bottom)
Corsair HX850 power supply
Windows 7 Professional 64-bit
(Latest nvidia graphics drivers installed; have had this problem since I've owned the 470, which I bought the first month it was available.)
IRQ report:
I/O Port 0x00000000-0x0000000F Direct memory access controller
I/O Port 0x00000000-0x0000000F PCI bus
IRQ 20 Standard Dual Channel PCI IDE Controller
IRQ 20 Standard Dual Channel PCI IDE Controller
I/O Port 0x000003C0-0x000003DF Intel(R) 5520/5500/X58 I/O Hub PCI Express Root Port 3 - 340A
I/O Port 0x000003C0-0x000003DF NVIDIA GeForce GTX 470
IRQ 23 Intel(R) ICH10 Family USB Enhanced Host Controller - 3A3A
IRQ 23 Intel(R) ICH10 Family USB Universal Host Controller - 3A34
IRQ 16 Intel(R) ICH10 Family USB Universal Host Controller - 3A37
IRQ 16 Intel(R) ICH10 Family PCI Express Root Port 6 - 3A4A
IRQ 17 Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller
IRQ 17 Intel(R) ICH10 Family PCI Express Root Port 1 - 3A40
IRQ 18 Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller #2
IRQ 18 Intel(R) ICH10 Family USB Enhanced Host Controller - 3A3C
IRQ 18 Intel(R) ICH10 Family USB Universal Host Controller - 3A36
IRQ 18 Intel(R) ICH10 Family PCI Express Root Port 3 - 3A44
IRQ 19 Intel(R) ICH10 Family USB Universal Host Controller - 3A39
IRQ 19 Intel(R) ICH10 Family USB Universal Host Controller - 3A35
Memory Address 0xA0000-0xBFFFF Intel(R) 5520/5500/X58 I/O Hub PCI Express Root Port 3 - 340A
Memory Address 0xA0000-0xBFFFF PCI bus
Memory Address 0xA0000-0xBFFFF NVIDIA GeForce GTX 470
I/O Port 0x000003B0-0x000003BB Intel(R) 5520/5500/X58 I/O Hub PCI Express Root Port 3 - 340A
I/O Port 0x000003B0-0x000003BB NVIDIA GeForce GTX 470
Memory Address 0xF8000000-0xFBCFFFFF Intel(R) 5520/5500/X58 I/O Hub PCI Express Root Port 3 - 340A
Memory Address 0xF8000000-0xFBCFFFFF NVIDIA GeForce GTX 470
Memory Address 0xD4000000-0xDFFFFFFF Intel(R) 5520/5500/X58 I/O Hub PCI Express Root Port 3 - 340A
Memory Address 0xD4000000-0xDFFFFFFF NVIDIA GeForce GTX 470
Latest BSOD:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\112810-8034-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e4e000 PsLoadedModuleList = 0xfffff800`0308be50
Debug session time: Sun Nov 28 16:17:55.610 2010 (UTC - 5:00)
System Uptime: 0 days 1:43:04.625
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 4A, {75182dd9, 2, 0, fffff88006be1ca0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: nt
FAULTING_MODULE: fffff80002e4e000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
BUGCHECK_STR: RAISED_IRQL_FAULT
FAULTING_IP:
+3261363038646132
00000000`75182dd9 ?? ???
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002ebdca9 to fffff80002ebe740
STACK_TEXT:
fffff880`06be1a68 fffff800`02ebdca9 : 00000000`0000004a 00000000`75182dd9 00000000`00000002 00000000`00000000 : nt+0x70740
fffff880`06be1a70 00000000`0000004a : 00000000`75182dd9 00000000`00000002 00000000`00000000 fffff880`06be1ca0 : nt+0x6fca9
fffff880`06be1a78 00000000`75182dd9 : 00000000`00000002 00000000`00000000 fffff880`06be1ca0 fffffa80`07890910 : 0x4a
fffff880`06be1a80 00000000`00000002 : 00000000`00000000 fffff880`06be1ca0 fffffa80`07890910 00000000`00000000 : 0x75182dd9
fffff880`06be1a88 00000000`00000000 : fffff880`06be1ca0 fffffa80`07890910 00000000`00000000 00000000`00000000 : 0x2
STACK_COMMAND: kb
FOLLOWUP_IP:
nt+70740
fffff800`02ebe740 48894c2408 mov qword ptr [rsp+8],rcx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt+70740
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntoskrnl.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
System:
Asus P6X58D Premium
i7 930 (cooled by Megahalems Rev. B w/ 2 120mm Yate Loon fans in push/pull config)
6GB Corsair Dominator
eVGA GTX 470 superclocked
Intel X-25 SSD (OS)
WD 1TB black HDD
Samsung DVD-RW/CD-RW
HAF 932 case (stock fans plus Yate Loon 120mm fan on bottom)
Corsair HX850 power supply
Windows 7 Professional 64-bit
(Latest nvidia graphics drivers installed; have had this problem since I've owned the 470, which I bought the first month it was available.)
IRQ report:
I/O Port 0x00000000-0x0000000F Direct memory access controller
I/O Port 0x00000000-0x0000000F PCI bus
IRQ 20 Standard Dual Channel PCI IDE Controller
IRQ 20 Standard Dual Channel PCI IDE Controller
I/O Port 0x000003C0-0x000003DF Intel(R) 5520/5500/X58 I/O Hub PCI Express Root Port 3 - 340A
I/O Port 0x000003C0-0x000003DF NVIDIA GeForce GTX 470
IRQ 23 Intel(R) ICH10 Family USB Enhanced Host Controller - 3A3A
IRQ 23 Intel(R) ICH10 Family USB Universal Host Controller - 3A34
IRQ 16 Intel(R) ICH10 Family USB Universal Host Controller - 3A37
IRQ 16 Intel(R) ICH10 Family PCI Express Root Port 6 - 3A4A
IRQ 17 Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller
IRQ 17 Intel(R) ICH10 Family PCI Express Root Port 1 - 3A40
IRQ 18 Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller #2
IRQ 18 Intel(R) ICH10 Family USB Enhanced Host Controller - 3A3C
IRQ 18 Intel(R) ICH10 Family USB Universal Host Controller - 3A36
IRQ 18 Intel(R) ICH10 Family PCI Express Root Port 3 - 3A44
IRQ 19 Intel(R) ICH10 Family USB Universal Host Controller - 3A39
IRQ 19 Intel(R) ICH10 Family USB Universal Host Controller - 3A35
Memory Address 0xA0000-0xBFFFF Intel(R) 5520/5500/X58 I/O Hub PCI Express Root Port 3 - 340A
Memory Address 0xA0000-0xBFFFF PCI bus
Memory Address 0xA0000-0xBFFFF NVIDIA GeForce GTX 470
I/O Port 0x000003B0-0x000003BB Intel(R) 5520/5500/X58 I/O Hub PCI Express Root Port 3 - 340A
I/O Port 0x000003B0-0x000003BB NVIDIA GeForce GTX 470
Memory Address 0xF8000000-0xFBCFFFFF Intel(R) 5520/5500/X58 I/O Hub PCI Express Root Port 3 - 340A
Memory Address 0xF8000000-0xFBCFFFFF NVIDIA GeForce GTX 470
Memory Address 0xD4000000-0xDFFFFFFF Intel(R) 5520/5500/X58 I/O Hub PCI Express Root Port 3 - 340A
Memory Address 0xD4000000-0xDFFFFFFF NVIDIA GeForce GTX 470
Latest BSOD:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\112810-8034-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e4e000 PsLoadedModuleList = 0xfffff800`0308be50
Debug session time: Sun Nov 28 16:17:55.610 2010 (UTC - 5:00)
System Uptime: 0 days 1:43:04.625
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 4A, {75182dd9, 2, 0, fffff88006be1ca0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: nt
FAULTING_MODULE: fffff80002e4e000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
BUGCHECK_STR: RAISED_IRQL_FAULT
FAULTING_IP:
+3261363038646132
00000000`75182dd9 ?? ???
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002ebdca9 to fffff80002ebe740
STACK_TEXT:
fffff880`06be1a68 fffff800`02ebdca9 : 00000000`0000004a 00000000`75182dd9 00000000`00000002 00000000`00000000 : nt+0x70740
fffff880`06be1a70 00000000`0000004a : 00000000`75182dd9 00000000`00000002 00000000`00000000 fffff880`06be1ca0 : nt+0x6fca9
fffff880`06be1a78 00000000`75182dd9 : 00000000`00000002 00000000`00000000 fffff880`06be1ca0 fffffa80`07890910 : 0x4a
fffff880`06be1a80 00000000`00000002 : 00000000`00000000 fffff880`06be1ca0 fffffa80`07890910 00000000`00000000 : 0x75182dd9
fffff880`06be1a88 00000000`00000000 : fffff880`06be1ca0 fffffa80`07890910 00000000`00000000 00000000`00000000 : 0x2
STACK_COMMAND: kb
FOLLOWUP_IP:
nt+70740
fffff800`02ebe740 48894c2408 mov qword ptr [rsp+8],rcx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt+70740
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntoskrnl.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
Facebook
Twitter
Instagram