EVGA Precision X shows idle temp @ 33-34 Celsius, and 52 Celsius while running Diablo III in full-screen, obviously lowering to 34 Celsius when in background currently. Note that I changed my power configuration to efficient instead of maximum performance earlier today as well, just in case. I also attached a screenshot of the BIOS hardware profile for starting CPU and Motherboard temperatures as well.
The temperatures look fine, and 52°C under load is good. If you're happy to I'd suggest running Furmark, we need to prove whether or not the GPU is the problem. If your temps get above 70°C get ready to end it if it continually rises above 80°C.
Thanks Boozad, I'm downloading Furmark and Speccy while I can; don't want another crash to interrupt me again. Feel like I'm on a clock if this is truly a hardware issue.
Well, back again. More issues. I have run Seagate Tools and it has shown that the HD is healthy, sfc scannow, and ccleaner. I have rolled back (via clean install) to graphics driver 314.22 for the EVGA GTX 560 which is supposed to be more stable than the newer versions. I flashed the M4N75TD motherboard BIOS to vers. 1701, and noted that via BIOS my RAM was not set @ 1600 and changed it.
I am still getting BSOD's, this time pointing to ks.sys and NTFS.sys. I had another BSOD, but somehow it was corrupted and didn't associate to Windbg, so I couldn't include it. Note I installed hotfix KB 2764302-x64 for the BSOD pointing to NTFS.sys, but got the 2nd BSOD afterward. At this point I have no idea what is causing all these BSOD's, and I have researching these during my interim. Should I consider re-formatting the HD and re-installing Windows 7?
Can I ask what you have installed in your USB ports at the moment? This entry seems problematic:
Code:STACK_TEXT: fffff880`030af528 fffff800`032d08be : fffff800`034e8d68 fffff800`032dc145 fffff800`03425914 fffff880`030b0448 : nt!KeBugCheck fffff880`030af530 fffff800`033046cd : fffff800`034e9398 fffff800`0342222c fffff800`03264000 fffff880`030b0448 : nt!KiKernelCalloutExceptionHandler+0xe fffff880`030af560 fffff800`033034a5 : fffff800`0342a398 fffff880`030af5d8 fffff880`030b0448 fffff800`03264000 : nt!RtlpExecuteHandlerForException+0xd fffff880`030af590 fffff800`03314431 : fffff880`030b0448 fffff880`030afca0 fffff880`00000000 fffffa80`00000007 : nt!RtlDispatchException+0x415 fffff880`030afc70 fffff800`032d8542 : fffff880`030b0448 fffffa80`074bdc90 fffff880`030b04f0 00000000`00000001 : nt!KiDispatchException+0x135 fffff880`030b0310 fffff800`032d6e4a : fffffa80`06ab04f0 fffff880`045458f6 fffffa80`07ea4050 fffffa80`0b122940 : nt!KiExceptionDispatch+0xc2 fffff880`030b04f0 fffff800`032ba464 : fffffa80`0a4b1e00 fffff800`0340efcd fffffa80`0a880b50 00000000`00000040 : nt!KiGeneralProtectionFault+0x10a fffff880`030b0680 fffff800`032ba6d2 : fffff880`03088180 00000000`00000000 00000000`00000001 fffffa80`00000000 : nt!KiExitDispatcher+0x94 fffff880`030b06f0 fffff800`032dca03 : fffffa80`0fab2c80 00000000`a000000c 00000000`00000000 00000000`00000000 : nt!KeInsertQueueApc+0xa2 fffff880`030b0750 fffff880`02d92025 : fffffa80`07209b70 00000000`00000000 fffffa80`06ab0401 00000000`00000000 : nt!IopfCompleteRequest+0xb63 fffff880`030b0840 fffff880`02d905cc : fffffa80`0fa556e0 fffffa80`0c1477f0 00000000`00000000 fffffa80`0bd1a780 : ks!CKsPin::TransferKsIrp+0xf5 fffff880`030b0880 fffff880`02d9171f : 00000000`00000000 00000000`00000000 fffffa80`07ea4050 fffff880`0453456a : ks!KspTransferKsIrp+0x54 fffff880`030b08b0 fffff880`02d917af : fffffa80`0c1477f0 00000000`00000002 00000000`00000000 fffffa80`09c81402 : ks!CKsQueue::ForwardIrp+0x167 fffff880`030b0900 fffff880`02d9217f : fffffa80`0c1477f0 00000000`00000000 fffffa80`0bd1a780 fffffa80`06f8af60 : ks!CKsQueue::ForwardWaitingIrps+0x5f fffff880`030b0930 fffff880`02d91945 : fffffa80`06f8af60 00000000`00000000 fffffa80`06f8afc0 00000000`00000000 : ks!CKsQueue::UnlockStreamPointer+0x123 fffff880`030b0980 fffff880`02c02121 : fffffa80`0c5bb0b0 fffffa80`06f8afc0 00000000`00000000 fffffa80`0c5bb0b0 : ks!CKsQueue::DeleteStreamPointer+0xf5 fffff880`030b09c0 fffff800`032dc1e1 : fffffa80`0c27e7bb 00000000`00000000 00000000`00000000 00000000`00000050 : usbaudio!USBType1CompleteCallback+0x20d fffff880`030b0a30 fffff880`04536631 : fffffa80`07ea4050 fffffa80`09c81400 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x341 fffff880`030b0b20 fffff880`04536b0f : fffffa80`06ce9902 fffffa80`0c27e580 00000000`ffffffff fffffa80`07ea4eb0 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15 fffff880`030b0c00 fffff880`0453466f : fffffa80`07ea4eb0 fffffa80`07ea41a0 fffffa80`07ea5050 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7 fffff880`030b0c60 fffff880`04525f89 : fffffa80`07ea4050 00000000`00000000 fffffa80`07ea4e02 fffffa80`07ea4eb0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3 fffff880`030b0ca0 fffff800`032e47ac : fffff880`03088180 fffffa80`07ea4eb0 fffffa80`07ea4ec8 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9 fffff880`030b0cd0 fffff800`032d0bca : fffff880`03088180 fffff880`03093040 00000000`00000000 fffff880`04525db0 : nt!KiRetireDpcList+0x1bc fffff880`030b0d80 00000000`00000000 : fffff880`030b1000 fffff880`030ab000 fffff880`030b0d40 00000000`00000000 : nt!KiIdleLoop+0x5a
Thanks for replying Boozad.
I have the Logitech Elite Keyboard, Logitech G500 gaming mouse in uppermost USB ports, then the Logitech G330 Headset and a Chillout USB Fan in the ports beneath. The fan is NOT driver enabled, only drawing power via USB. Could that cause any of the issues I'm having?
As an aside, I currently have Verifier enabled, so I am waiting to see if any non-Microsoft drivers give me a BSOD. So far so good.
Ok, done. Running sfc scannow again to see if it picks up anything (did only one scan before). Still have verifier enabled also, going to run some programs, see if that turns up any BSOD's.
If I may interrupt for a little input.
Are you using USB 2.0 or 3.0 for your mouse and keyboard?
I would suggest using USB 2.0.
Is your mouse and keyboard a new addition or have you been using them a while without problems?
Layback Bear,
Good question: I have been using them for quite awhile. As far as USB 2.0 or 3.0, how would I determine that? Would it be under the driver info under Device Manager?
Boozad,
Ok, after running verifier and trying a game (Star Trek Online) I have gotten a couple of BSOD's, but they aren't associating w/ WinDBg, just showing 'MEMORY' dumps under the Windows folder. Note both the Fan and the Logitech headset are not plugged in. I did include another DM log, but not sure it caught the most recent BSOD's. Opening them via WinDBg shows information is 'inconsistent':
Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
************************************************************************
WARNING: Dump file has inconsistent set-bit count. Data may be missing.
************************************************************************
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to read KLDR_DATA_TABLE_ENTRY at fffffa80`069ba890 - NTSTATUS 0xC0000147
"nt" was not found in the image list.
Debugger will attempt to load "nt" at given base 00000000`00000000.
Please provide the full image name, including the extension (i.e. kernel32.dll)
for more reliable results.Base address and size overrides can be given as
.reload <image.ext>=<base>,<size>.
Unable to add module at 00000000`00000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18741.amd64fre.win7sp1_gdr.150202-1526
Machine Name:
Kernel base = 0xfffff800`03218000 PsLoadedModuleList = 0xfffff800`0345c890
Debug session time: Sun Apr 12 14:32:06.379 2015 (UTC - 5:00)
System Uptime: 0 days 0:37:21.705
Unable to read KLDR_DATA_TABLE_ENTRY at fffffa80`069ba890 - NTSTATUS 0xC0000147
"nt" was not found in the image list.
Debugger will attempt to load "nt" at given base 00000000`00000000.
Please provide the full image name, including the extension (i.e. kernel32.dll)
for more reliable results.Base address and size overrides can be given as
.reload <image.ext>=<base>,<size>.
Unable to add module at 00000000`00000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Loading Kernel Symbols
Unable to read KLDR_DATA_TABLE_ENTRY at fffffa80`069ba890 - NTSTATUS 0xC0000147
Page 8b48107f1 too large to be in the dump file.
WARNING: .reload failed, module list may be incomplete
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C1, {fffff9803248ec10, fffff9803248e317, 5103e8, 23}
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Special pool has detected memory corruption. Typically the current thread's
stack backtrace will reveal the guilty party.
Arguments:
Arg1: fffff9803248ec10, address trying to free
Arg2: fffff9803248e317, address where bits are corrupted
Arg3: 00000000005103e8, (reserved)
Arg4: 0000000000000023, caller is freeing an address where nearby bytes within the same page have been corrupted
Debugging Details:
------------------
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
BUGCHECK_STR: 0xC1_23
SPECIAL_POOL_CORRUPTION_TYPE: 23
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
LAST_CONTROL_TRANSFER: from fffff880042f872d to fffff880042f86e4
STACK_TEXT:
fffff800`04824c68 fffff880`042f872d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`042f86e4
fffff800`04824c70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : 0xfffff880`042f872d
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION:
BUCKET_ID: CORRUPT_MODULELIST
FAILURE_BUCKET_ID: CORRUPT_MODULELIST
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:corrupt_modulelist
FAILURE_ID_HASH: {6a10ab2d-36f9-3117-3ae8-89baa6e43dd5}
Followup: MachineOwner
---------
I apologize for the copy/paste post, but I checked to make sure I had the symbol path file still loaded in WinDBg, and it's correct per the WinDBg forum post instructions. It may be redundant, but I wanted you to see the C1 Stop, in case it's not in the DM log.
Quote