New
#11
In the Start Search field type event and click Event Viewer. You might look, from the left pane, in Windows logs/Applications and Applications and Services logs/Hardware events. There may be a clue in one of those.
In the Start Search field type event and click Event Viewer. You might look, from the left pane, in Windows logs/Applications and Applications and Services logs/Hardware events. There may be a clue in one of those.
Hmm, it reported that the system shut down unexpectedly, but it didn't report any BSODs. Usually this means a power issue or some system hardware (most often your CPU) suffered overheating and reached a critical temperature threshold so your mobo restarted.
I recommend you turn automatic restarting from BSODs off and try the Prime run again. To do so, type advanced system settings' in start menu, and then go to Startup & Recovery and uncheck the 'automatic restart' option.
Just so you know, if your system still restarts spontaneously despite changing this setting (remember to restart after the change), then we're dealing with hardware failure, most likely the PSU or some short circuit, or CPU/GPU overheating. Only software-related exception would be hibernation problems for Windows, which you should have hibernating turned off by typing powercfg -h off in the Command Prompt (type cmd in start menu to access it). Remember to restart after that change, too!
Thanks to all...I finally broke down and reinstalled the OS. *sigh* Freakin' windows... Anyways, I noticed that Easy Tune 6 never actually brought up a dialog box. Then, I checked out the Task Manager and it looked like 3 instances of it were running. I am thinking that it was running in the background unbeknownst to me and THAT was causing the BSOD. I am leaving the PC on for about a week straight to see if it will BSOD. If not, I will mark this solved. Thanks for everyone's help. :)
Okay, it still seems to be having issues. I wish I could read these so as to not keep bugging you guys, but here are my files...
Yeah, as I originally suspected, we're dealing with hardware failure here. These crashes are reporting single bit corruptions in Windows kernel code just like before. Either Windows itself did not install as cleanly as it should've (again, prolly cuz of hardware problems) or some bad hardware is bugging it out. Given your previous experience, I say we're dealing with a bad PSU or mobo, with CPU also having some chance. Unfortunately, unless you got another stable system to swap this pieces into and test for stability, there's no other definitive manner to determine what's causing it. Better get your warranties ready.
Thanks again Vir for the info. I have an RMA # for my mobo and will be sending it off soon. They say 2 to 3 weeks before it will be returned. Anyways, expect a reply in about a month as to whether this is solved by a new mobo or not.
mobo was RMA'd to Gigabyte and returned. No mention of whether they actually fixed anything or not btw. I found their whole RMA process to be pretty lacking. Anyway, I have reinstalled Win7 Pro from scratch and am still having problems. What gives? Is my CPU bad? Latest dumps should be attached.