Windows 7 (64bit) random system crashes

[Afck91]

Hi guys, new to the forum - appears to be a very helpful place!

Hopefully someone could help me find out what's causing my random system crashes.

Every so often, my system will freeze totally, can't move the mouse, ctrl+alt+del or anything, totally freezes up on me. I have to use the reset button on my case to restart the whole system, and then it will be fine again up until it freezes again.

I have opened event viewer, and under Critical it says that kernel power was the source of the last critical event, but is this just where I had to use the reset button?

Where do I find the log or dump on what caused the system to crash? How do I export it and post it up on here? Which ones do you guys need to debug the problem?

I'm totally new to this whole dump viewing etc, so any help would be greatly appreciated.

My system specs are filled in on my profile, and my bios settings are default so there's no over clocking done.

Cheers,
Adam

EDIT: Ok, so I downloaded Windows_NT6_BSOD_v3.03_jcgriff2_, ran that and ran perfmon /report and uploaded both reports/dumps into one .zip which I have attached here.

I am not sure how many days back these dumps go, but there was quite a lot of turning the computer straight off with the power button a few days ago, due to an unstable over clock.

 

[yowanvista]

Dump blames your Nvidia Display driver
Uninstall the driver then use driver sweeper to remove leftover files
Guru3D - Driver Sweeper

Then install the latest driver
NVIDIA DRIVERS 260.99 WHQL

If the above does not work test your RAM
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

BugCheck 116, {fffffa8008d184e0, fffff88004949e64, ffffffffc00000b5, a}

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+12ee64 )

 

[Afck91]

Thanks for the reply!

I have just done what you said to do.

Uninstalled driver, cleaned up with Driver Sweeper.
Installed driver you linked me to, and restarted.

My system froze once it had restarted on the 'Welcome' screen.

Should I redo a dump file and upload that?

Whilst I wait for a reply, I will run memtest86 and let it run a few passes. (Hopefully!)

Many thanks
Adam

 

[Afck91]

Memtest86 reported no errors with my RAM.

I have just got a BSOD whilst in Windows too.
6.1.7600.2.0.0.256.1

I have uploaded another dump file here

Thanks
Adam

 

[yowanvista]

Were you having this issue since you bought that GTX470?

 

[Afck91]

Hi, nope it has only started recently.

I think I might have found out where I went wrong.

When I cleaned the leftovers, I think I only cleaned the NVIDIA Display and NVIDIA Physx leftovers, but not the NVIDIA Chipset. The file 'nvlddmkm.sys' which is causing my problems, is only cleaned by the NVIDIA Chipset which I didn't do, and the un-installation of the drivers doesn't remove that file.

Going to attempt it again now, and hopefully that will fix my problem.

Many thanks for your help Yowan, I have repped you. (and friend requested!)

Cheers
Adam

 

[yowanvista]

nvlddmkm.sys is related to your GPU/Nvidia driver

Ensure that the card is not overheating, clean out the dust

 

[Afck91]

The card is pretty new, so there is no signs of dust etc.

I have checked that my card is not overheating, my GPU temp is currently at 43degree @ idle.

Im lost on what this could be now? Is there nothing else in the dump files you could find for me Yowan?

Thanks
Adam

 

[Afck91]

Ok, so I still reckon its a driver problem.

I just loaded CS:S, and it froze. I used alt + tab to minimize CS:S, and a little popup showed saying the Nvidia driver crashed, but has recovered.

This is really pissin me off now!

 

[Jonathan_King]

Hello,

I suspect a bad graphics card, honestly. Do you have another card you can test with? If not, I recommend that you purchase one from a computer parts store. Check on their return policy, though, so you can return the card if need be.

...Summary of the dumps:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Dec  7 14:34:20.218 2010 (UTC - 5:00)
System Uptime: 0 days 3:42:33.358
*** 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+12ee64 )
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Dec  6 08:32:30.805 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:15.788
*** 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+75a028 )
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[TVeblen]

Based on many posts I have seen in the forum regarding this problem there are a few things you need to consider beyond the video driver. (When it's the video driver it's easy!)

FYI, the nVidia chipset driver is for your motherboard, not the video card.

First, check all your connections. Re-seat video card and memory modules. Make sure the contacts are clean. Check all the electrical connections.

You could be dealing with a defective video card. The best way to test for this is to borrow a replacement card and try it out. If the problem goes away it would be clear.

You could try running with just one stick of RAM in slot A1. Memtest will pick up most common RAM errors, but it is not an end-all. The one-stick-at-a-time diagnostic eliminates bad slots and voltage issues as causes.

You also could be dealing with a defective power supply. If the amperage is dipping under load it will cause the card to fault. If you have a multimeter you could test the supply to measure for a steady 12v to the card's power connectors. (The only true way to test a power supply would be to use the very expensive diagnostic equipment used in labs). But for us regular folks: I test my power supply by hooking up my multimeter to the PCI-E connectors used to power the video card (I used a spare pair from the power supply to run the card while I was testing). I then observe the meter while I use the computer, first watching the voltage, then the amps, to see if there is any drop-off or erratic behavior while booting or using the computer. My readings were rock solid. So I declared my power supply good.
Otherwise you need to replace the supply to eliminate this possibility. Or borrow one from another computer.

If you are overclocking, this can be a trial and error process. The clocks and/or multipliers you set or change for CPU, Memory, or GPU could be unstable. Eliminate this as a possibility by resetting these to their defaults to see if that clears the video problems. The simplest way to do this is to "Restore Bios Defaults", or Clear CMOS.

Some people have reported that by going into the video cards control panel and "down-clocking" the cards performance settings they were able to clear up the video problem. Since W7 does not seem to tolerate any hiccups in the GPU, this would allow you to run a poor performing card in the W7 environment.
So for instance, you could set the GPU clock from a 777 MHz factory setting to 750MHz, and the ram clock from a 1126MHz factory setting to 1050Mhz, or similar small change for your particular card.

Hope that helps!

 

[OEM]

Based on many posts I have seen in the forum regarding this problem there are a few things you need to consider beyond the video driver. (When it's the video driver it's easy!)

FYI, the nVidia chipset driver is for your motherboard, not the video card.

First, check all your connections. Re-seat video card and memory modules. Make sure the contacts are clean. Check all the electrical connections.

You could be dealing with a defective video card. The best way to test for this is to borrow a replacement card and try it out. If the problem goes away it would be clear.

You could try running with just one stick of RAM in slot A1. Memtest will pick up most common RAM errors, but it is not an end-all. The one-stick-at-a-time diagnostic eliminates bad slots and voltage issues as causes.

You also could be dealing with a defective power supply. If the amperage is dipping under load it will cause the card to fault. If you have a multimeter you could test the supply to measure for a steady 12v to the card's power connectors. (The only true way to test a power supply would be to use the very expensive diagnostic equipment used in labs). But for us regular folks: I test my power supply by hooking up my multimeter to the PCI-E connectors used to power the video card (I used a spare pair from the power supply to run the card while I was testing). I then observe the meter while I use the computer, first watching the voltage, then the amps, to see if there is any drop-off or erratic behavior while booting or using the computer. My readings were rock solid. So I declared my power supply good.
Otherwise you need to replace the supply to eliminate this possibility. Or borrow one from another computer.

If you are overclocking, this can be a trial and error process. The clocks and/or multipliers you set or change for CPU, Memory, or GPU could be unstable. Eliminate this as a possibility by resetting these to their defaults to see if that clears the video problems. The simplest way to do this is to "Restore Bios Defaults", or Clear CMOS.

Some people have reported that by going into the video cards control panel and "down-clocking" the cards performance settings they were able to clear up the video problem. Since W7 does not seem to tolerate any hiccups in the GPU, this would allow you to run a poor performing card in the W7 environment.
So for instance, you could set the GPU clock from a 777 MHz factory setting to 750MHz, and the ram clock from a 1126MHz factory setting to 1050Mhz, or similar small change for your particular card.

Hope that helps!

+1

Great post TVeblen,

To the OP, if you do find the need to check amps, make sure you understand what ports to your mult-meter you need to connect to & understand how to connect meter leads in order to read amps.

TVeblen has some great ideas about checking connections, fans, dust & voltage first, And checking bios/overclocking R we??? ... including graphics card???

 

[Afck91]

Hi guys, thanks for the replies.

I have just noticed my DRAM led on my motherboard is on?? This never used to happen??

EDIT: Reseated my 3 ram modules, and pressed MemOK button on my motherboard, the light only appears at start-up like it used to do.

I might do a whole clean install of Windows tomorrow, to eliminate any driver conflicts etc.

Thanks for your time guys
Adam

 

[OEM]

Hi guys, thanks for the replies.

I have just noticed my DRAM led on my motherboard is on?? This never used to happen??

EDIT: Reseated my 3 ram modules, and pressed MemOK button on my motherboard, the light only appears at start-up like it used to do.

I might do a whole clean install of Windows tomorrow, to eliminate any driver conflicts etc.

Thanks for your time guys
Adam

Do you have a recovery program like Acronis to run a system recovery point first?

There are free versions of Acronis from Western Digital if you have a Western Digital Drive....

Western Digital Acronis True Image Full Version

There's a free one with Seagate too if you have a seagate drive...

Seagates Free Agent Utilities Download Page

 

[Afck91]

Just to let you guys know, and in case anyone comes across this thread in search of a solution, this was fixed by a clean install of Windows 7 - I guess it was a driver clash.

Cheers for the help guys

Adam