BSOD over last couple of weeks, games or updating drivers.

[Rhynik]

Well gentlemen, I sincerely hope someone can help me out. My computer had been running smoothly up until the past couple of weeks. I've been trying to figure out the problem with my very limited modern computer knowledge. Needless to say, it hasn't worked out so well.

I get BSOD's when playing video games such as Rift. Whenever I try to update to the newest NVIDIA video card driver it either goes to a black screen to which I have to manually turn off, or a BSOD. I've tried searching for the BSOD on the internet, but from what I can tell, the limited knowledge I have of these errors it looks like it could be several different problems.

I've run malware, ccleaner, scandisk, antivirus and anything else I could think of.

I found the Sevenforums utility for uploading my info so here goes.

And thanks in advance for any help you guys can provide.

Windos 7 Premium Home 64bit
OEM
Hardware and software is approximately 2 years old.

 

[zigzag3143]

Well gentlemen, I sincerely hope someone can help me out. My computer had been running smoothly up until the past couple of weeks. I've been trying to figure out the problem with my very limited modern computer knowledge. Needless to say, it hasn't worked out so well.

I get BSOD's when playing video games such as Rift. Whenever I try to update to the newest NVIDIA video card driver it either goes to a black screen to which I have to manually turn off, or a BSOD. I've tried searching for the BSOD on the internet, but from what I can tell, the limited knowledge I have of these errors it looks like it could be several different problems.

I've run malware, ccleaner, scandisk, antivirus and anything else I could think of.

I found the Sevenforums utility for uploading my info so here goes.

And thanks in advance for any help you guys can provide.

Windos 7 Premium Home 64bit
OEM
Hardware and software is approximately 2 years old.

These were caused by a memory exception. Please run these two tests to verify your memory and find which driver is causing the problem.


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-Driver verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[Rhynik]

Thank you ZigZag, I'll get working on these solutions ASAP. If for some reason I can no longer use this PC for further help, I'll be using my Ipad to check the forum.

Could you help me and tell me what you looked at that showed you the problem? Thanks

 

[zigzag3143]

Thank you ZigZag, I'll get working on these solutions ASAP. If for some reason I can no longer use this PC for further help, I'll be using my Ipad to check the forum.

Could you help me and tell me what you looked at that showed you the problem? Thanks

A tool called win debugger. Its the gold standard for BSOD's but requires training.

 

[Rhynik]

Well I ran the memtest for almost 10 hours, 5 passes and no errors. Similar to a test I had to do when I first got the computer to figure out which ram stick was bad. It was replaced a long time ago.

Before starting the verifier phase of testing, I tried to use the windows backup service to an external HD. That gave me a BSOD and a crash. So I manually loaded my pictures and libraries to the HD.

Started the verifier and I had a few crashes and odd things happen but not many BSODs. For example the PC would just freeze and I would have to turn off the power to restart it. It did crash and do a CHKDISK which I haven't seen it do in the past. Anyways 12 hours later and several errors, 2 BSOD's I figured I'd upload the info I do have. One of the BSOD's mentioned something about a driver.

Again, thanks in advance for any help you guys can provide.

 

[maxseven]

My computer had been running smoothly up until the past couple of weeks.

Any chance you have a System Restore point from before when the problem started?

Most likely IMO one of two things happened: you changed a driver to one W7 doesn't like (nvidia?) or a hardware component failed. I'm betting "driver" myself.

 

[Rhynik]

Unfortunately I don't have a system restore from before 9-26, which based on the event logs is when problems started occurring. While there was some difficulty installing the new Nvidia driver, I didn't attempt to install that until last week after the problem was already there, I was hoping it would fix the crashes and freezes.

With all of these diagnostic tools is there no way to narrow down what is causing the problems?

 

[zigzag3143]

Unfortunately I don't have a system restore from before 9-26, which based on the event logs is when problems started occurring. While there was some difficulty installing the new Nvidia driver, I didn't attempt to install that until last week after the problem was already there, I was hoping it would fix the crashes and freezes.

With all of these diagnostic tools is there no way to narrow down what is causing the problems?

Most recent blamed on fastfat.SYS part of the OS. If you havent please run a system file check.

Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

Read here for more information http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Let us know the results from the report at the end.

 

[Rhynik]

Sorry ZigZag, been stuck at work and no time for my computer at home the last couple of days. Ran the scannow and got the message some files were corrupted but could not be repaired.

All that my untrained brain could pick out from this jumbled log is something to do with the pku2u file. I've attached the CBS log with the results. Again, thanks for your time.

 

[zigzag3143]

Sorry ZigZag, been stuck at work and no time for my computer at home the last couple of days. Ran the scannow and got the message some files were corrupted but could not be repaired.

All that my untrained brain could pick out from this jumbled log is something to do with the pku2u file. I've attached the CBS log with the results. Again, thanks for your time.

If the files cant be repaired its time for a repair install

 

[Rhynik]

Well I attempted to slipstream a disk for repair install with SP1, since it was saying my windows was newer then the disk that came with my PC. After doing so, I tried that DVD I burned and it said it could not open the install.wim. I double checked to make sure it was on the disk, it was, tried running as an administrator but still it was a no-go.

Figured I'd try this tutorial.

http://www.sevenforums.com/tutorials/3413-repair-install.html

And it mentions you can uninstall SP1, which I went to do and noticed it was installed the day that my computer became unstable and started getting BSODs. I'm waiting for it to complete the uninstall, then I will try and run some programs and see if I continue to have problems. If I do, I'll just use the original windows disk I got with the computer.

 

[Rhynik]

Here's the problem now... Windows will never complete the uninstall of SP1. The progress bar will slide all the way over to complete, but it will go nowhere unless I hit cancel or close it, then when I re-open programs and look at updates it's still there. Is there another way to remove SP1?