BSOD after clean OS install

digitcon · 05 Aug 2013

Hello all,
I have been trying for a while to deal with a few PC issues. I had a few different issues with BSOD and USB devices losing power apparently randomly. I tried a reinstall of Win7 without doing a reformat of the drive and that was just a headache.
After 2 weeks of trying to fix that install and working around it, I just reformatted the drive and did a clean install, but the problems are still here. Slowdowns, hanging randomly, and now BSOD.
The install is less than 48 hours old, and I have tried to put all of the drivers on ASAP and up to date.
I didnt have any installation issues really, and I am just trying to figure out if it is a Hardware issue.
chkdsk and memtest all came back clean.
Please let me know what I should do next, Im pretty lost.
Two year old PC at this point, btw.
Thanks.

ICIT2LOL · 05 Aug 2013

Hello and welcome digitcon mate have you checked out the PSU yet? If not try these - be careful not to open up the device no need to remove it in any case.
PSU - Jump Start

then

https://www.sevenforums.com/vip/257690-psu-how-test.html#post2130086

just remember that correct volts do not mean correct current.

digitcon · 05 Aug 2013

Thanks! Ive had a PSU go bad years and years ago. Only way I figured it out then was to replaced every component until I had it by process of elimination. I will give that thread a try and see how it goes.

J

ICIT2LOL · 05 Aug 2013

Ok mate let us know how you go.

digitcon · 05 Aug 2013

PSU checks out. I have the jump start running now and the case fans work nicely.
I wouldn't see how the pSU issue would cause Windows to forget uSB devices that I had already installed or my boot priorities in the bIOS. Both of which have been happening. Several of these have been related to coming back from sleep mode and crashes from sleep.
Like I mentioned, clean install here 48 hours old.

digitcon · 05 Aug 2013

Checked a few other threads, and someone also mentioned running
cmd powercfg -energy
which I did. Basically it said that several devices are not entering Suspend state, power management would be effected.
Also "The current power policy for PCI Express Active State Power Management (ASPM) is configured to Off."
Not sure if that is why the video card is failing to recover from sleep modes.
Is that any help?

ICIT2LOL · 06 Aug 2013

Now digitcon mate try looking in your power settings as it is getting beyond me a bit ere and I can only find refs to power settings in searches.

Might be worth trying a sfc SFC /SCANNOW Command - System File Checker

and Disk Check won't take long maybe the clean install didn't go that well??

Arc · 06 Aug 2013

Hello digitcon.

Your BSOD is a stop 0x116; which is typically a display/graphics related issue.

You have the latest version of nvidia display driver installed. This one is known to be buggy in some cases. I would suggest you to uninstall it totally and perform a clean install using the 314.22 WHQL display driver.

Uninstall All nvidia items in Control Panel > Programs and features
- 3D Vision Control Driver
- 3D Vision Driver
- Graphics Driver
- HD Audio Driver
- PhysX
- nvidia Update
(Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
Now follow Drivers - Clean Left over Files after Uninstalling
Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:

It appears that you are somehow overclocking.

Code:

CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3310

As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.
How To Clear CMOS (Reset BIOS)

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know about the wattage of your PSU.

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.

Let us know the results.
__________________________________________________________________________
BSOD ANALYSIS:

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800b465010, fffff8800596be30, ffffffffc00000b5, a}

*** 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+13be30 )

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: fffffa800b465010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800596be30, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc00000b5, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000a, Optional internal context dependent data.

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


FAULTING_IP: 
nvlddmkm+13be30
fffff880`0596be30 4055            push    rbp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`047fb888 fffff880`04292054 : 00000000`00000116 fffffa80`0b465010 fffff880`0596be30 ffffffff`c00000b5 : nt!KeBugCheckEx
fffff880`047fb890 fffff880`04291e2f : fffff880`0596be30 fffffa80`0b465010 00000000`00000000 fffffa80`084ea410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`047fb8d0 fffff880`04338f13 : fffffa80`0b465010 00000000`c00000b5 00000000`00000000 fffffa80`084ea410 : dxgkrnl!TdrIsRecoveryRequired+0x273
fffff880`047fb900 fffff880`04362d50 : fffffa80`00000000 00000000`0006b9fe 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`047fb9e0 fffff880`04361437 : 00000000`00000102 00000000`00000000 00000000`0006b9fe 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0xd0
fffff880`047fba10 fffff880`043342d2 : ffffffff`ff676980 fffffa80`084ea410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`047fbab0 fffff880`04360ff6 : 00000000`00000000 fffffa80`08f7c850 00000000`00000080 fffffa80`084ea410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`047fbbc0 fffff800`0e977ede : 00000000`0576e6de fffffa80`08f368b0 fffffa80`0667e890 fffffa80`08f368b0 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`047fbc00 fffff800`0e6ca906 : fffff800`0e854e80 fffffa80`08f368b0 fffff800`0e862cc0 fffffa80`08bbee20 : nt!PspSystemThreadStartup+0x5a
fffff880`047fbc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+13be30
fffff880`0596be30 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+13be30

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  51c41788

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

3: kd> lmvm nvlddmkm
start             end                 module name
fffff880`05830000 fffff880`06315000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Fri Jun 21 14:36:16 2013 (51C41788)
    CheckSum:         00AB87FF
    ImageSize:        00AE5000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

digitcon · 06 Aug 2013

Thanks for the tips guys. I will check a few of those out, but let me clear a few things up since I did leave some of my past testing out.
Before this clean install I did a furmark burnin and while the graphics card temps were in the 90 degree range they held there and did not spike higher. No anomalies.
I have never OCd this chip so I will check that out, thanks for noticing. The bIOs has been acting strange before
The PC had been running hot which is what I thought the problem was 2 weeks ago before I even did that first non clean windows reinstall. I found lots of dust and when removed it took care of all the heat issues. Imagine that. :P
Once I get a little free time i will try to get more specs try the previous nvidia drivers and get the bios looked at.
I really appreciate the help. I had no other ideas.
FWIW I fiddled with some of the sleep settings after reading a thread between here and another board. PC has at least come back from sleep stable three times in a row
I also uninstalled all the Asus software that people generally agree is buggy as crap an have memory leaks.
J

digitcon · 06 Aug 2013

Before i forget I think it's a 700 W psu. I have a UPS running as wells