Win7 Crashes. Not sure why. Please help.

[WRCLA]

My computer with win7 pro 64bit is crashing once or twice a day. I tried - win memory diagnostic, virus scan, sys file checker, registry cleaner (winaso). None worked. I think registry cleaner made it worse. Also I used registry cleaner (ccleaner) last month. So I think something is wrong with me registry.

 

[Arc]

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

 

[WRCLA]

I tried the SF - Diagnostic Tool. It gathered my dump files. They are attach. Please take a look at them.

 

[carwiz]

The dumps are caused by a hardware error but the WHEA record doesn't contain any parameters. This could be caused by catastrophic failure, memory faults in CPU cache or memory faults. Check your system temperatures, especially CPU temps. Also, follow the directions to capture system files and event logs. If you are overclocking, stop!

 

[WRCLA]

Probably not the temps. I got a huge thermo transfer for the cpu, gpu, psu. Also, I am not overclocking. When I checked the temps with SpeedFan, they all check out fine, way below the 100's (c), around the 33's (c).

Could you reply with what are in the dumps? For some reason, WinDbg does not install in my computer. Could it because of the VS12 installed in my computer?

 

[WRCLA]

A moment ago, my computer was about to crash. It stop for a while. Then it came back.

When it came back, Windows notified me the video card driver (Nvidia) recovered. Does this mean the video driver is the problem? Last driver update was on 9/12/13.

 

[Arc]

This one?

In 90% of the cases, it is a hardware error. But that error is not possible to found by stress test, coz it is random in nature.

From the limited data you supplied, we cannot see the model of the card and the driver in use. You are suggested to post following the Blue Screen of Death (BSOD) Posting Instructions, once again; after post http://www.sevenforums.com/bsod-hel...hes-not-sure-why-please-help.html#post2570714.

 

[carwiz]

I wouldn't rely on Speed Fan. Even your voltages are whacked according to that. Intel processors can fail if you exceed the +/-5% limit on voltages. Download and install HWInfo64 and see what that says but DO NOT run more than ONE temp monitor program at the same time.

Use the "Grab All" option in the BSOD instructions.

 

[WRCLA]

Arc - Yes. It was that, "Display driver stopped responding and has recovered".

 

[WRCLA]

Carwiz -

Wow! HWiNFO64 is thoroughly complete. Attached are the computer specs and readouts.

 

[WRCLA]

I was away from my computer for a week 10/9-10/13 since the crashes started. Could there have been an update that I missed?

 

[carwiz]

No way to tell unless you attach the files as instructed. Help here as ended until you do. Everything else is just a guess.

 

[WRCLA]

Carwiz - I did as instructed in that tread. I only was able to get the minidumps out of it. They are in the SF_20-10-2013.zip file. Is there another way to gather the necessary information? Could I do this manually?

 

[Arc]

View attachment 290794

 

[carwiz]

http://www.sevenforums.com/tutorials/92394-sf-diagnostic-tool-using-troubleshooting.html

Did you download the tool?

Be sure to run the diagnostic tool as Administrator. It's proven technology that works. If you get any error messages, snip and paste them here but follow the instructions item by item. It takes to long to explain and gather the info individually. That's why the utility was created. It collects no personal information. The only thing we could possibly see is the name you assigned your computer. And that never gets posted on the forum. I was inactive here for the summer (heavy workload) so I lost my BSOD Badge but those that carry the badges like Archie are the cream of the crop of this forum. They are a trusted asset with thousands of references.

 

[Arc]

Thank you, Ken.

We learned by following you. And, it is sure that the badge will be back to the place rightly ... may be just a matter of time

 

[WRCLA]

Got it working with administrator. Duh.

It could not do CPUID properly though. Some reason it could not connect to the internet to download CPUID. So I manually saved the CPUID report that CPUID gives.

Hoping you could nail the coffin now.

 

[carwiz]

Sorry it took so long to get back. There wasn't much help in the system log--It stops after August of this year. You should change the option to overlay old event logs. (Or not delete them.) The application event log has a number of strange looking entries and you are correct that your Registry file is damaged. This may take a few steps to get to the root cause but let's make sure your system files are intact then we'll tackle the VMware/Blackberry/Daemon problems. You also have a missing service driver that may be part of USB services.

Start by running SFC /scannow from an elevated command prompt. The inline link points to the directions for running. Use Option Two. Be sure to run the command prompt "As Administrator". If you get errors during the scan, it may take several runs to fix the system files and sync the Registry. If you get a BSOD before SFC completes, reboot in safe mode and uninstall the Daemon Tools through Programs and Features. Reboot and try SFC again until no errors are shown on the console screen. It shouldn't take more than four runs so if you still get errors, report back with a copy of the console screen.

 

[WRCLA]

I did the sfc /scannow.

On the first run, I got verificatioin 100%.

 

[WRCLA]

Is this a good thing?