Windows 7 Random Freezes Requiring Hard Reboot (no minidump files)

[Britton30]

OK, that's a very good PSU. I have two HX650s and one HX 850.

 

[sosowie]

Update:
- I ran Prime95 overnight, and no errors.
- I installed the 43 optional windows updates I had neglected to do.

Not going to jinx anything, but so far I haven't had issues. I will continue to monitor and post updates. Many thanks to those that have pitched in on my behalf. Will update again soon.

 

[gregrocker]

So unless I missed a post the issue might have been resolved by those 43 Optional Updates you installed?

If that is the case it's not surprising because I've found important Performance Updates queued there that solved issues, making me wonder why they were classed "Optional." But then again Drivers are mainly classed Optional too and those are all needed almost without exception.

I've come to the conclusion to always install all Updates except Bing and Essentials unless you need one or more.

 

[sosowie]

I spoke too soon: Computer crashed overnight, no dump file written...

 

[gregrocker]

Confirm you've had a reinstall that closely matches the steps, uses only the tools and methods compiled here to get a perfect Clean Reinstall - Factory OEM Windows 7 especially how drivers are handled.

In addition I'd wipe the HD first with Diskpart Clean Command after testing it to confirm its good, test RAM again overnight to stress it.

Then I'd make it a diagnostic install by first only installing all rounds of Windows Updates, after enabling Automatically deliver drivers via Windows Update (Step 3),
testing performance adequately between each group of Updates after requested reboots. Then go back to Check for UPdates until all rounds are completed.

Only then would I start installing programs in order of need, leaving enough time between each to again check performance adequately.

This can pinpoint the Update, Program or setting that is causing the issue. If it's present at WIn7 install it points to hardware. You can also try running with a Linux live CD to test this.

 

[sosowie]

Hi Greg,

When you write "testing performance adequately between each group of Updates after requested reboots", are you suggesting that I don't install all the updates right away? That after every reboot prompt, I should monitor my computer performance for a couple of days? The problem is this issue doesn't reliably happen on a daily basis (sometimes I get multiple times a day... others, like the latest occurrence, happened after close to 3 days of respite). So potentially after many many days of bringing the windows updates current, I should then move on to programs with the same strategy?

Just making sure I'm understanding your advice correctly, thanks.

 

[gregrocker]

Yes, run for awhile after only the OS is installed. Then you can install each group selecting all Important and Optional Updates, but after reboot use the PC for a day to see if issue recurs.

I would run a Linux live disk for a day or so to see if the problem recurs when the OS or HD isn't even involved. If so unplug the HDD to see if it's still interfering. This is also why to wipe the HDD of boot code since that can sometimes interfere until wiped.

 

[sosowie]

Thanks Greg.

Do you have a good link that details the steps involved in running a "Linux live disk"? Should I do this before my clean reinstall? Should I detach my HDD (my OS is in my SSD) now to rule out that possibility now?

So I'm thinking, following your posts:

1) Detach HDD and monitor
2) Meanwhile run tests on SSD and Memtest again
3) Run Linux Live disk and monitor
4) Clean reinstall, monitor after each round of updates (careful to just install LAN driver and nothing else manually)
5) Install programs one by one and monitor

Is this plan on the right track?

 

[gregrocker]

http://www.sevenforums.com/tutorial...ate-live-cd-dvd-usb-use-emergency-backup.html

You'd only need to detach the HDD if it interferes or the problem surfaces while using the Linux live CD OS. This way you can cut it out and know that it's not interfering or the cause of the issue.

If the problem persists using Linux Live CD then it is likely hardware.