Windows 7 BSOD from last few weeks ...

[antz123]

First of all please find the Zip file as required by W7F diagnostics attached. Also my dump

I have Microsoft Windows 7 Ultimate 64 Bit, Intel Core I7, Gigabyte X58USB3, 6GB RAM, Intel 120SSD based System, Nvidia GTX580

Problem am facing is from past few weeks if am playing any games, suddenly screen will go black, and some static sound and PC restarts to Windows Safe Mode. Games i have tried range from COD BOII, old Demonoid, Borderlands2. All games I have tried changing the things to lower resolution but same result.

Steps Already taken:

Registry Cleanup
Removed my Anti-virus and disabled Firewall just in case
Updated my Anti-virus and scanned the system
Reinstallled Nvidia Drivers
Post this
Reinstalled Windows from a fresh source
Reinstalled All drivers
Reinstalled the games
Ran Intel SSD scanner to check for bad drive issues, no issues
Ran S&M stress test for my processor for error , no issues
Ran Furmark , 60 seconds test, no issues.

REst it does not crashes when system is running movies, music or hours of Internet.

Any help would be awesome. Any other info if needed please ask me.

Thank you

Anant

 

[usasma]

You have 3 hard drives. What is the make/model/wattage and age of your Power Supply?

We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:

There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

Here's some suggestions:
- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
- Update the motherboard controllers drivers to the latest available version from the controller manufacturer (NOT the mobo manufacturer unless you can't find any on the controller manufacturer's website)
- Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
- Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
- Update chipset and storage controller drivers to the latest available from the manufacturer of the device (not the manufacturer of the motherboard). Be sure to update ALL controllers on the motherboard!
....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.
- Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
It's my opinion that SSD's aren't reliable enough (with current hardware) to be used on a system that needs to work reliably. Until I see reliability I will not recommend, nor will I use, SSD's for critical applications.
06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum
29 May 2012 - The frequency of BSOD's with SSD's seems to have been decreasing over the last several months. It may be approaching time to re-evaluate my stand on their suitability for use in production systems.
10 Nov 2012 - I'm seeing an upswing in SSD errors - but most appear due to older storage controller drivers. I strongly suggest NOT using storage controller drivers that don't date from 2012 (if none are available, don't connect an SSD to that controller)
05 Jan 2013 - very interesting post about difficulties with the Marvell controllers even when not connected to the SSD drives: https://www.eightforums.com/bsod-cr...-pc-reboots-when-waking-sleep.html#post169956

Please try these troubleshooting steps for the error that you're experiencing: Video TDR Timeout - 0x116 + 0x117

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

Please remove:
mcdbus.sys Mon Jul 28 05:21:04 2008 (488D8F80)
MagicISO SCSI Host Controller driver
Link Removed

Please update:
RtNdPt60.sys Sun Jul 19 22:27:32 2009 (4A63D614)
Realtek NDIS User mode I/O Driver - Ethernet
Link Removed

Please update:
nusb3hub.sys Thu Nov 18 20:34:24 2010 (4CE5D420)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 version)
Link Removed

Please update:
nusb3xhc.sys Thu Nov 18 20:34:25 2010 (4CE5D421)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 version)
Link Removed

Please remove. Reinstall if needed once the system is stabilized.
AppleCharger.sys Mon Jan 10 04:57:29 2011 (4D2AD809)
GIGABYTE On/Off Charge driver. See here for details - Link Removed [br] May cause BSOD on Win7/8 systems - uninstall to test (haven't seen recently (15Jan2013))
Link Removed



Analysis:
The following is for informational purposes only.

[font=lucida console]**************************Tue Feb  5 13:27:55.748 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\020513-9438-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:53:16.700[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+929adc )[/B]
BugCheck [B]116, {fffffa800926b4e0, fffff88005372adc, ffffffffc000009a, 4}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffffa800926b4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88005372adc, 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.
BUGCHECK_STR:  0x116
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0x116_IMAGE_nvlddmkm.sys[/B]
CPUID:        "Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz"
MaxSpeed:     2670
CurrentSpeed: [B]2664[/B]
  BIOS Version                  F4
  BIOS Release Date             04/29/2011
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  X58-USB3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Feb  5 12:31:43.186 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\020513-11746-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]1 days 0:56:16.014[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+929adc )[/B]
BugCheck [B]116, {fffffa800a876280, fffff8800539badc, ffffffffc000009a, 4}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffffa800a876280, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800539badc, 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.
BUGCHECK_STR:  0x116
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0x116_IMAGE_nvlddmkm.sys[/B]
CPUID:        "Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz"
MaxSpeed:     2670
CurrentSpeed: [B]2664[/B]
  BIOS Version                  F4
  BIOS Release Date             04/29/2011
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  X58-USB3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[font=lucida console]**************************Tue Feb  5 13:27:55.748 2013 (UTC - 5:00)**************************
[COLOR=RED][B]mcdbus.sys                  Mon Jul 28 05:21:04 2008 (488D8F80)[/B][/COLOR]
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
[COLOR=RED][B]RtNdPt60.sys                Sun Jul 19 22:27:32 2009 (4A63D614)[/B][/COLOR]
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
[COLOR=RED][B]nusb3hub.sys                Thu Nov 18 20:34:24 2010 (4CE5D420)[/B][/COLOR]
[COLOR=RED][B]nusb3xhc.sys                Thu Nov 18 20:34:25 2010 (4CE5D421)[/B][/COLOR]
[COLOR=RED][B]AppleCharger.sys            Mon Jan 10 04:57:29 2011 (4D2AD809)[/B][/COLOR]
cmudaxp.sys                 Thu Mar 10 02:44:15 2011 (4D78814F)
SCDEmu.SYS                  Wed Jun 15 04:29:27 2011 (4DF86D67)
CORSGKB.sys                 Mon Jun 20 22:38:24 2011 (4E000420)
Rt64win7.sys                Tue Sep 27 10:50:33 2011 (4E81E2B9)
kdhacker64.sys              Thu Feb 23 01:15:16 2012 (4F45D974)
GEARAspiWDM.sys             Thu May  3 15:56:17 2012 (4FA2E2E1)
nvhda64v.sys                Tue Jul  3 11:25:04 2012 (4FF30ED0)
kisknl.sys                  Wed Aug 15 06:40:00 2012 (502B7C80)
kusbquery64.sys             Wed Sep  5 06:19:34 2012 (50472736)
K7FWHlpr.sys                Wed Nov 21 10:00:46 2012 (50ACEC9E)
K7Sentry.sys                Wed Dec 19 01:58:19 2012 (50D1658B)
nvlddmkm.sys                Sat Dec 29 01:47:52 2012 (50DE9218)
[/font]

Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
kdhacker64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
kisknl.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
kusbquery64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
K7FWHlpr.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
K7Sentry.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed

 

[antz123]

All right lot to absorb . First of all thank you.

Now I have 2 Hdd and 1 SSd.

I ran deep checks on my SSD and HDDs. All well there too. Passed with flying colors.

Now updated 5-6 drivers you suggested.
1) Realtek High Def Audi driver
2) Logitech Gaming Software
3) Renesas USB 3 Driver
4) Nvidia reinstalled
5) Realtek RTL Network Drivers
6) Intel Chipset Device Softwares
7) Magic ISO driver updated.
8) Gigabyte on/off usb driver

As for my Power Supply is HX 850 Corsair. Its around 14-16 Months old. HX is considered pretty safe, however you never know.

My Cabinet is Silverstone FT02, which is pretty well ventilated. Also today opened and gave it a strong flow of vacuum. unplugged and cleaned up my Graphic card nicely (GTX560). Wanted to see if its overheating due to dust or something.

I am gonna do some heavy test like AntiVirus Check and Keep CPUID open, would post temperatures and Voltages just in case if its culprit.

 

[antz123]

Post todays updates and cleaning

played old game Demigod,(which isnt heavy on which earlier had faced crash, 1hr no crashes )

Anyways adding reports from system monitor. if you feel there is any voltage or heat issues please point those out.

 

[usasma]

Please don't use a vacuum cleaner on your PC. It generates static electricity which has been known to damage systems.

I'm not that familiar with these reports, but the first one seems to point at CPU overheating:

+- Intel Core i7 920 (/intelcpu/0)
|  |
|  +- CPU Core #1 (/intelcpu/0/temperature/0)
|  |  +- TjMax [°C] : [COLOR=#ff0000]100[/COLOR] : 100
|  |  +- TSlope [°C] : 1 : 1
|  |
|  +- CPU Core #2 (/intelcpu/0/temperature/1)
|  |  +- TjMax [°C] : [COLOR=#ff0000]100 [/COLOR]: 100
|  |  +- TSlope [°C] : 1 : 1
|  |
|  +- CPU Core #3 (/intelcpu/0/temperature/2)
|  |  +- TjMax [°C] : [COLOR=#ff0000]100[/COLOR] : 100
|  |  +- TSlope [°C] : 1 : 1
|  |
|  +- CPU Core #4 (/intelcpu/0/temperature/3)
|  |  +- TjMax [°C] : [COLOR=#ff0000]100[/COLOR] : 100
|  |  +- TSlope [°C] : 1 : 1

And the second one to mainboard overheating:

Hardware monitor    NVIDIA NVAPI
    Voltage 0    0.96 Volts [0x3C3] (VIN0)
    Temperature 0    [COLOR=#ff0000]71°C[/COLOR] (159°F) [0x47] (TMPIN0)
    Fan 0        0 RPM [0x0] (FANIN0)
    Fan PWM 0    54 pc [0x36] (FANPWMIN0)

Please double check this, it's way, way too hot and may be damaging your system!!!
Make sure that your fans are plugged in and working when the system is on.
Another test is to open up the case and use a house fan to blow cool air into the case.