Logitech HD Pro C920 causing BSOD and GPU to overheat

gshillitani · 24 Jul 2014

I reformatted my computer and reinstalled everything over the last couple of days. I have not changed any hardware or software, its the same stuff that was on it before. I was in a Google Hangout when my computer rebooted twice, all on its own, within 20 minutes. The webcam is Logitech HD Pro C920 with the most current software/drivers, and the GPU is 2047MB NVIDIA GeForce GT 640 (EVGA). After the two reboots, I tested the webcam theory by turning it on record and the GPU goes from 63º C to 83º C within minutes. If I turn off the webcam it cools back down to where it started, also within minutes. The computer has not BSOD'd since I shut off the webcam. I am attaching the requested information in your FAQ.

Arc · 26 Jul 2014

Very interesting.

Try to see how the GPU works/reacts with other operations. Try some games, some movies. See if the temperature increases in the same way or not.

Also observe the overall system heat and let us know it properly. Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

And take one big test. Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

The BSODs are stop 0x116; all possible for the situation that you explained. So the heat and health of the GPU is to determine at first.

Let us know the results.
___________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80190b9010, fffff8800fc41d1c, ffffffffc000009a, 4}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+98bd1c )

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80190b9010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800fc41d1c, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

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


FAULTING_IP: 
nvlddmkm+98bd1c
fffff880`0fc41d1c 48ff25ddb9edff  jmp     qword ptr [nvlddmkm+0x867700 (fffff880`0fb1d700)]

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

STACK_TEXT:  
fffff880`0278aa48 fffff880`04c9a140 : 00000000`00000116 fffffa80`190b9010 fffff880`0fc41d1c ffffffff`c000009a : nt!KeBugCheckEx
fffff880`0278aa50 fffff880`04c6d867 : fffff880`0fc41d1c fffffa80`11629000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0278aa90 fffff880`04c99f4f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`190b9010 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`0278ab40 fffff880`04d6903d : fffffa80`0ef73990 00000000`00000080 00000000`00000000 fffffa80`11628410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`0278abc0 fffff800`02d2073a : 00000000`057fa999 fffffa80`0fe32b50 fffffa80`0c765040 fffffa80`0fe32b50 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`0278ac00 fffff800`02a758e6 : fffff880`031d7180 fffffa80`0fe32b50 fffff880`031e1fc0 fffffa80`0f486c10 : nt!PspSystemThreadStartup+0x5a
fffff880`0278ac40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+98bd1c
fffff880`0fc41d1c 48ff25ddb9edff  jmp     qword ptr [nvlddmkm+0x867700 (fffff880`0fb1d700)]

SYMBOL_NAME:  nvlddmkm+98bd1c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  537a8efc

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x116_image_nvlddmkm.sys

FAILURE_ID_HASH:  {1f9e0448-3238-5868-3678-c8e526bb1edc}

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

3: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f2b6000 fffff880`0ff1a000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Tue May 20 04:38:44 2014 (537A8EFC)
    CheckSum:         00C1EA41
    ImageSize:        00C64000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

gshillitani · 26 Jul 2014

Well, I'm afraid that's not possible. I opened it up to vacuum/blow it out. I took the GPU out because the fan is on the underside and you can't reach it to clean it with it in the slot. Cleaned out the whole tower and the GPU (it had a little dust but not enough to cause it to overheat), reinserted the GPU and... no video. Nothing. Fan came on so it was getting power but it would not display anything. I took it out and put it back a few times, tried a different PCI slot, still no love. I plugged the monitor back into the onboard graphics port and voilà, video.

Since then I have gotten another BSOD, this time it was complaining about a driver. Checked the drivers and sure enough it says the USB 3.0 controller is not recognized. Went to ASUS' site and made sure I had the most current drivers (which I had already installed from the ASUS cd of course) and that seemed to fix that. For now. The next thing; the sound of an external device being connected/disconnected played, looked up and again it doesn't recognize a USB device. Checked in Devicer Manager, this time it showed all of the drivers and devices as good. Checked everything plugged in... my external HD was no longer in the list of drives. Unplugged it, turned it back on, now it shows in the drives again. No more BSOD so far or unexpected reboots, but the HD is doing something odd... once in a while it stops. Well, the sound of it stops, if that makes sense. After a few seconds the sound comes back. I've never heard it stop completely even in hibernate or sleep mode. I'm starting to worry that my MB is failing. Any suggestions?

Arc · 26 Jul 2014

You may check the screws etc attaching the HDD. If all are properly fixed, and if the sound is not a noise, you may overlook it as far as it is not hampering performance or causing any issue.

gshillitani · 26 Jul 2014

The screws are all there and attached correctly. Its not so much a sound as a lack of sound, like the heads stop spinning for a few seconds, then start back up. I don't know what would cause it to "lose" device drivers like that either... I'll just keep my fingers crossed I guess. Thanks for the help!