I get a black screen when I'm more than halfway done with running the Windows Experience Index. When I turn my computer back on I get a message saying I got a blue screen. I created the DM Log and attached it, any help is appreciated.
Stress test the Graphics Card using Furmark.Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.
Is the computer hot? 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 .
__________________________________________
Code:BugCheck 116, {fffffa800471a010, fffff8800f1b9568, 0, 2} *** 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+14c568 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: fffffa800471a010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff8800f1b9568, The pointer into responsible device driver module (e.g. owner tag). Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation. Arg4: 0000000000000002, Optional internal context dependent data. Debugging Details: ------------------ FAULTING_IP: nvlddmkm+14c568 fffff880`0f1b9568 4055 push rbp 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.17237 (debuggers(dbg).140716-0327) amd64fre STACK_TEXT: fffff880`041b3a28 fffff880`03f0b134 : 00000000`00000116 fffffa80`0471a010 fffff880`0f1b9568 00000000`00000000 : nt!KeBugCheckEx fffff880`041b3a30 fffff880`03f0ae3e : fffff880`0f1b9568 fffffa80`0471a010 fffffa80`064d8c50 fffffa80`0558a190 : dxgkrnl!TdrBugcheckOnTimeout+0xec fffff880`041b3a70 fffff880`03fb2f13 : fffffa80`0471a010 00000000`00000000 fffffa80`064d8c50 fffffa80`0558a190 : dxgkrnl!TdrIsRecoveryRequired+0x1a2 fffff880`041b3aa0 fffff880`03fdccf1 : 527cc3a7`ffffffff 00000000`0054b587 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiReportHwHang+0x40b fffff880`041b3b80 fffff880`03fae2e1 : fffffa80`0558a190 fffffa80`00000002 00000000`0054b587 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71 fffff880`041b3bb0 fffff880`03fdaff6 : 00000000`00000000 fffffa80`03bd7650 00000000`00000080 fffffa80`0558a190 : dxgmms1!VidSchiScheduleCommandToRun+0x1e9 fffff880`041b3cc0 fffff800`02b6baba : 00000000`fffffc32 fffffa80`055a5060 fffffa80`039cc040 fffffa80`055a5060 : dxgmms1!VidSchiWorkerThread+0xba fffff880`041b3d00 fffff800`028c3426 : fffff800`02a51e80 fffffa80`055a5060 fffff800`02a5fcc0 00000000`00000221 : nt!PspSystemThreadStartup+0x5a fffff880`041b3d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: nvlddmkm+14c568 fffff880`0f1b9568 4055 push rbp SYMBOL_NAME: nvlddmkm+14c568 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 54cc1748 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 --------- 1: kd> lmvm nvlddmkm start end module name fffff880`0f06d000 fffff880`0fd84000 nvlddmkm T (no symbols) Loaded symbol image file: nvlddmkm.sys Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys Image name: nvlddmkm.sys Timestamp: Sat Jan 31 05:14:08 2015 (54CC1748) CheckSum: 00D02940 ImageSize: 00D17000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
It seems like I know what the problem is now, I just don't know how to fix it. My video driver crashes when I play 2 of the 8 videos used by Windows Experience Index located in "C:\Windows\Performance\WinSAT", the videos that crash my video driver are called Clip_1080_5sec_MPEG2_HD_15mbps & Clip_1080_5sec_VC1_15mbps. I have ran the Furmark stress test and my computer didn't crash and I didn't see any artifacts, I will attach a picture with the Furmark results. I first tried sfc /scannow to fix the issue but that didn't work so then I tried taking out my graphics card and playing the videos again and they work without the graphics card installed. This leads me to believe this is a video card driver issue instead of the graphics card itself being broken since it does not crash on the Furmark test. I first had the GEFORCE 309.08 DRIVER installed and then I tried installing a older version of the driver (GEFORCE 307.83 DRIVER) but the videos still crash that driver too. Any help is appreciated, I've also published a screenshot of Speccy here http://speccy.piriform.com/results/G...WncTS3a1fcCdOX
The things I noticed usernamenottake you have dozens of failed Windows 7 Updates. You will need those updates.
Next thing I noticed is you 3.3v is very low (1.394v).
Check your 12V, 5V and 3.3V in your bios and post results.
Next lets start with a basic. Complete this tutorial by Brink and post results here.
Windows Genuine and Activation Issue Posting Instructions
Attachment 357491I kept trying to install the updates and they eventually installed successfully. I attached the picture with my voltages. I still think this is windows media player or my video driver causing this, because as I said before it only crashes when the graphics card is installed, but the only times my computer crashes is when running windows experience index not when playing games.
Quote