Windows 7 Random Restarting at Idle

[jbguillo]

Hi guys! I've been lurking here for awhile, it just sucks that my first post is with some crappy error.

So...I'm killing myself over what could be wrong right now. Basically, Windows restarts randomly when I leave it idle; It could be that I get up to use the bathroom and come back, or I get a phone call and then come back to the computer. When I come back I see where I left off or a black screen, then I move the mouse and my computer restarts; as if I pushed the restart button. No BSOD

This happens at total random, but ~ once a day. I ran Memtest first, everything checked out 100%. I then replaced my PSU and went with a better one...no change. I also disabled auto-restart in advanced options, still no change. Everything is already set to "always on" in power settings. I just disabled all startup programs to see if that helps with anything. BTW, all of my temps are perfect; CPU idling ~33c. I've also run the Prime95 CPU Torture Test for ~30mins with no problems. My CPU is slightly OC'd, but the problem was still happening prior to OC.

I'm thinking it may be a problem with my mobo? CPU? Maybe even my GPU? I just built this pc a few days ago, and kept my old GPU; so I wouldn't think it would be faulty because it worked perfectly prior.

I'm really just trying to narrow this down to something without going crazy; I finally spent a ton of money on my dream system, and this problem is the only thing that's making me want to pull out my hair. ANY help or suggestions would be much appreciated.

System Specs
Win7 Ultimate x64
AMD Phenom 2 Quad 965 BE 3.4ghz (Running @ 3.8ghz)
Gigabyte GA-MA790GPT-UD3H Motherboard
Gskill 4x2gb (8gb) DDR3 1600 Memory
EVGA 1gb 285GTX Superclocked GPU
650 & 500gb WD Caviar HHDs
BFG 1000w PSU

I'm getting 2 errors, one right after the other, after the restart:

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 11/16/2009 9:48:56 AM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (2)
User: SYSTEM
Computer: Jeff-PC
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.



Log Name: System
Source: EventLog
Date: 11/16/2009 9:49:05 AM
Event ID: 6008
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Jeff-PC
Description:
The previous system shutdown at 9:47:34 AM on ‎11/‎16/‎2009 was unexpected.

 

[torrentg]

Run all components at default speeds with no overclocking and then you may follow this if another bsod happens.

 

[jbguillo]

I'm not getting any BSOD's though; it's literally just restarting as if I'm pushing the restart button, which I'm not. There are no minidump files present in windows\minidump.

I don't think that the CPU OC settings matter, as this was happening prior to me oc'ing the CPU.

 

[torrentg]

I'm not getting any BSOD's though; it's literally just restarting as if I'm pushing the restart button, which I'm not. There are no minidump files present in windows\minidump.

I don't think that the CPU OC settings matter, as this was happening prior to me oc'ing the CPU.

That's even more of a reason to not OC then. It's shutting off so abruptly it doesn't have time.

Basically, also what I'm trying to say is that I don't troubleshoot overclocked machines. It's just not wise. Once I or others figure out the problem, then you can overclock as much as you want.

 

[zigzag3143]

I'm not getting any BSOD's though; it's literally just restarting as if I'm pushing the restart button, which I'm not. There are no minidump files present in windows\minidump.

I don't think that the CPU OC settings matter, as this was happening prior to me oc'ing the CPU.

Hi and welcome

TG is correct about overclocking. DONT DO IT

I examine and analyze BSOD's constantly and abt 40% of them are from OC something especially in 64bit.

Even if there isnt a BSOD crash there would be a log of the event in event viewer. Type event viewer in search go to the windows log>application tab and look for errors (red in left column) that relate to app crash, app hang, unexpected restarts, etc. It will be there in spades. when you find them note the event ID and source and tell us what they are

Ken J

 

[jbguillo]

Sorry guys I've thrown it back to 3.4ghz for the time being.

As for the applications tab in log viewer, I am consistently getting two errors happening at the same time together; although, they do not correlate with the times that my computer restarted.

Error 11/14/2009 4:21:25 PM SideBySide 63 None
Log Name: Application
Source: SideBySide
Date: 11/14/2009 4:21:25 PM
Event ID: 63
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Jeff-PC
Description:
Activation context generation failed for "c:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "c:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll" on line 3. The value "MAJOR_VERSION.MINOR_VERSION.BUILD_NUMBER_MAJOR.BUILD_NUMBER_MINOR" of attribute "version" in element "assemblyIdentity" is invalid.

Error 11/14/2009 4:22:13 PM SideBySide 35 None
Log Name: Application
Source: SideBySide
Date: 11/14/2009 4:22:13 PM
Event ID: 35
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Jeff-PC
Description:
Activation context generation failed for "c:\program files (x86)\windows live\photo gallery\MovieMaker.Exe".Error in manifest or policy file "c:\program files (x86)\windows live\photo gallery\WLMFDS.DLL" on line 8. Component identity found in manifest does not match the identity of the component requested. Reference is WLMFDS,processorArchitecture="AMD64",type="win32",version="1.0.0.1". Definition is WLMFDS,processorArchitecture="x86",type="win32",version="1.0.0.1". Please use sxstrace.exe for detailed diagnosis.

I did speak with a Microsoft rep today, and he was thinking it may be the Realtek network card that is on-board my motherboard; any thoughts on this?

 

[torrentg]

Adobe Air is for deveopers I believe, so you can safely uninstall that and not worry about it any further.

I don't think it's the onboard lan, but anything is possible especially if they're saying that with the resources they have.

So to rule it out, update the bios to latest and install latest chipset drivers from manufacturer's site, if available.

 

[jbguillo]

I updated the BIOS and Realtek drivers about a week ago; so firmware-wise, I'm up to date. The rep seemed to believe that the onboard card was malfunctioning, as he said that he'd seen it happen in both newer Gigabyte and Asus boards. I'm going to rule it out by just disabling it and picking up a Linksys ethernet card.

I guess he believes that if the onboard card goes idle, when I come back it somehow restarts the computer. At least that's the jist of what I caught; does this seem logical?

 

[torrentg]

There's a setting in the driver to disallow the computer to turn it off to save power.

Double click it in the device manager, then go to power management tab.

Check the box for that, save, then reboot. Wait for bsod to happen. If Microsoft is right about their explanation, this will fix it for you then.

I'd also inspect the motherboard by eye to see if there are any blown capacitors leaking brown substance or with rounded tops instead of flat. Kernel power usually means something along the cpu being affected in regards to power. This is definitely one example that can cause it. Check, even if board is brand new.

 

[jbguillo]

I just checked it, saved, and restarted; no BSOD. Is this the expected result, or should I wait it out to see if I get a restart/BSOD?

I checked the mobo, and all of the caps seem to be perfect. In regards to the Kernal/CPU comment, could it maybe be a bad CPU?

 

[torrentg]

I don't think anything is "bad."

You probably wouldn't have a bsod yet anyhow. Let the computer run overnight without touching it and see after that.

 

[jbguillo]

Cool, and thanks a ton for the help so far.

I'll keep you guys updated on how everything goes.

 

[jbguillo]

Well, I left it on all night. Woke up, moved around the mouse, no problems. I went and had breakfast and was staring at the screen...as soon as I touched the mouse the computer restarted!

Same event errors as before (ID 6008 and 41) and no minidump files!

I replaced my network card last night and disabled the onbaord card. There also aren't any startup processes running, and nothing besides my mouse and keyboard is plugged in.

Any ideas? I'm dying here...

 

[torrentg]

Update the driver for the mouse. Like if it's Logitech, see that the latest driver is installed.

Other than that, I'd check all the settings related to any type of power at all anywhere on the system, in the bios.

I would say some hardware is defective but the fact it only happens when you just touched the mouse suggests otherwise. However, it's not impossible that the psu is too erratic or some other hardware cause. Or even improper installation or something like that.

If you're very comforatable pulling stuff apart, rebuild the system from scratch. Sometimes, this actually fixes things if you feel you're competent enough.

Ensure proper heat dissipation from the CPU. Use a high quality thermal paste like Arctic Silver or similar. Only a very small amount to cover is needed. Anything more goes against its purpose.

 

[jbguillo]

I'll try the Mouse driver, but this was happening even when I tried a different mouse.

The PSU I'm currently using is an 80+ Bronze Certified, and really gets great reviews. The same goes for the Corsair I replaced.

With pulling the computer apart, I practically already have with everything I've already replaced. I used AC5 upgrading the CPU cooler, and before I upgraded it was still doing it.

I'll try calling MS again to see what happens...I really dont' want to start the RMA process with the CPU and mobo...because that's all that's left that I haven't replaced.

Could it just be Windows?? The copy is a fresh install...so in my mind I wouldn't think so.

 

[jbguillo]

Wow, so I'm on the phone with MS tech support again, and he's basically telling me to replaced both the mobo and cpu because something electrically in one of them is messed up.

The hilarious thing is right after I got off the phone with him about 2 minutes ago, my PC restarted without me even touching anything...

I guess it's time to start the RMA process with the mobo and processor

 

[torrentg]

I guess it's time to start the RMA process with the mobo and processor

It's such a pain, I know. But ya, those error 41s are more of the serious type so there are high chances that replacing the motherboard is going to fix this.

I'd hold off on RMA the cpu for the moment, unless Microsoft instructs you to do otherwise. My guess is CPU is fine, motherboard is not.

When it's all fixed, you'll be very glad. It'll happen.

 

[jbguillo]

Wow, just restarted again! I have no clue what's happening.

Time to buy an Asus mobo. Just RMA'd my CPU through Newegg.

I'm just going to replace both to be on the safe side...I really just want to finish this problem.

 

[torrentg]

Knowing nothing of the specs, you'll probably get better power consumption (less) using an Asus board. EVGA boards usually draw more power.

 

[jbguillo]

Well, it was a gigabyte board..I've had pretty good luck with them in the past, but Asus has always been reliable to me.

I picked up this guy
Newegg.com - ASUS M4A78T-E AM3 AMD 790GX HDMI ATX AMD Motherboard - AMD Motherboards

Well, time to start taking everything apart...again. I guess I'll let you guys know what happens when I'm up and running again in a few days.

Torrentg, thanks for your time and help!