I know the GTX 470 routinely runs in the 90s under load; I've seen such on countless others' systems as reported on various websites. I've also seen online reviewers of the card show it running in low 90s under 100% load for sustained durations. However, if the card exceeds 75 degrees Celsius on my computer I get a very loud buzzing through my speakers/headphones, BSOD (usually IRQL error) and reboot.
Understanding the BSOD may not be temp related (and I've pasted latest dump file below; would greatly appreciate help with that, too), how to I get my computer to allow the GTX 470 to run hotter than 75C?
2d question:
What are the cause and solution to the BSOD that generated following minidump?
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\112610-7784-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`02e11000 PsLoadedModuleList = 0xfffff800`0304ee50
Debug session time: Fri Nov 26 09:19:41.217 2010 (UTC - 5:00)
System Uptime: 0 days 8:08:00.168
*********************************************************************
* 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, {75452dd9, 2, 0, fffff88006c7cca0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
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: fffff80002e11000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
BUGCHECK_STR: RAISED_IRQL_FAULT
FAULTING_IP:
+3261363038646132
00000000`75452dd9 ?? ???
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002e80ca9 to fffff80002e81740
STACK_TEXT:
fffff880`06c7ca68 fffff800`02e80ca9 : 00000000`0000004a 00000000`75452dd9 00000000`00000002 00000000`00000000 : nt+0x70740
fffff880`06c7ca70 00000000`0000004a : 00000000`75452dd9 00000000`00000002 00000000`00000000 fffff880`06c7cca0 : nt+0x6fca9
fffff880`06c7ca78 00000000`75452dd9 : 00000000`00000002 00000000`00000000 fffff880`06c7cca0 fffffa80`06953b70 : 0x4a
fffff880`06c7ca80 00000000`00000002 : 00000000`00000000 fffff880`06c7cca0 fffffa80`06953b70 05408804`00000000 : 0x75452dd9
fffff880`06c7ca88 00000000`00000000 : fffff880`06c7cca0 fffffa80`06953b70 05408804`00000000 00686769`68000000 : 0x2
STACK_COMMAND: kb
FOLLOWUP_IP:
nt+70740
fffff800`02e81740 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
---------
Understanding the BSOD may not be temp related (and I've pasted latest dump file below; would greatly appreciate help with that, too), how to I get my computer to allow the GTX 470 to run hotter than 75C?
2d question:
What are the cause and solution to the BSOD that generated following minidump?
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\112610-7784-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`02e11000 PsLoadedModuleList = 0xfffff800`0304ee50
Debug session time: Fri Nov 26 09:19:41.217 2010 (UTC - 5:00)
System Uptime: 0 days 8:08:00.168
*********************************************************************
* 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, {75452dd9, 2, 0, fffff88006c7cca0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
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: fffff80002e11000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
BUGCHECK_STR: RAISED_IRQL_FAULT
FAULTING_IP:
+3261363038646132
00000000`75452dd9 ?? ???
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002e80ca9 to fffff80002e81740
STACK_TEXT:
fffff880`06c7ca68 fffff800`02e80ca9 : 00000000`0000004a 00000000`75452dd9 00000000`00000002 00000000`00000000 : nt+0x70740
fffff880`06c7ca70 00000000`0000004a : 00000000`75452dd9 00000000`00000002 00000000`00000000 fffff880`06c7cca0 : nt+0x6fca9
fffff880`06c7ca78 00000000`75452dd9 : 00000000`00000002 00000000`00000000 fffff880`06c7cca0 fffffa80`06953b70 : 0x4a
fffff880`06c7ca80 00000000`00000002 : 00000000`00000000 fffff880`06c7cca0 fffffa80`06953b70 05408804`00000000 : 0x75452dd9
fffff880`06c7ca88 00000000`00000000 : fffff880`06c7cca0 fffffa80`06953b70 05408804`00000000 00686769`68000000 : 0x2
STACK_COMMAND: kb
FOLLOWUP_IP:
nt+70740
fffff800`02e81740 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
---------