Computer turned off by itself and wouldn't turn on...

Pulsedriver

Pulsedriver

Pulsedriver

Soldato
Joined
19 Dec 2003
Posts
3,105
Location
UK
Hey folks,

I was using my PC then I went downstairs for my dinner earlier, and when I came back up, my PC was off.

I pressed the power switch on the case, and it turned on, then turned off, then turned on, then turned off all by itself repeatedly. It kept doing this until I turned the power switch on the back of the PSU off, then back on, and now it loads up OK.

I've noticed when I start my PC anyway, it always turns on, for one second, then turns off, and then powers itself on and then works fine, I always thought it was to do with my motherboard...

What do you reckon? How can I check if its the PSU at fault? Is that what it looks like? (Spec in sig)
Temp seems ok as well...
 
I would guess mobo. but its just a guess could as easily be the psu. try loading a program like speedfan which will display your PSU volts then you can check if anything is out of place in the 12v 5v 3.3v etc.
 
Hi guys, I've just done installed speedfan, here is a screenshot;

Power.jpg


Anything out of the ordinary?
 
well the 3.3v is fine the 5v is fine the 12v though is... ummm not ok lol it could be an eronius reading though.

also isn't your vcore rather low for a q6600 @3.2ghz? 1.15v? i have very little experiance with c2d cpus so it could be fine. seems low though.
 
My overclock returns to standard Q6600 speeds at random, I don't think im a fan of this Gigabyte motherboard.

At the moment its just running at stock speeds.
 
The thing about the computer turning on, then off for one second, then back on and powering up normally is a system feature. I've never really understood this feature but never did get it when not overclocking although not sure if this is the case with some people. Maybe your overclock is not as stable as you originally thought. If the system shut down by itself and was actually off when you came back upstairs then it's probably not the result of a BSOD, although it's worthwhile checking C:\Windows\Minidump to see if you have any recent BSOD information and then if you do, examining it with the Microsoft Debugging Tools for Windows to see the cause. You might also want to check out the Event Viewer and look for any issues around the time the machine turned itself off.

SpeedFan is massively incorrect for reading rails, and the only decent programs are Everest, the BIOS itself, PC Wizard 2007 and maybe some others. They aren't 100% accurate as the only thing that can be is hardware (such as a multimeter or something like the Zalman Fan Controller that monitors volts).

BIOS resetting itself to stock speeds from an overclock is also another sign that the board doesn't like the overclock, even if you did get it 8hrs+ Prime/Orthos stable. You could maybe look at newer/alternative BIOS's for your motherboard in case the one you are using is old or not very good. Turning off then on then off then on can also be caused by an overclock, although more normaly associated with a hardware failure.

3 things that you've mentioned for me point towards your overclock, as mentioned even if it was Prime/Orthos stable for most of a day your motherboard may still not like the overclock and could just be kicking up a fuss.
 
Hi mate,

Thing is, my board doesnt even remember it's overclock settings.

There was no minidump file from today :(

It was all working fine @ 3.2ghz, then maybe a week later it will boot up at stock settings. Then randomly decide to go to stock settings or 3.2ghz

I've googled the issue, and it seems to be a problem with the Gigabyte boards.

They also suffer a cold boot issue, which is similar to the whole on-off thing...
 
Sorry to bump this thread up,

But it's just happened again! I was downstairs, my comp was on in windows, not even doing anything! Not downloading etc just idle.

And it was off! Same thing happened!

I wonder has this something to do with my 8800GT crashing and freezing during 3dmark06?

PSU? 700W Surely is enough!?
 
I have a cheap one somewhere but it has no SATA power connectors, so that rules that out.

For the record, I posted that post above, then went downstairs, came back and comp was off again!
What I noticed was, to get the comp to start again, I had to actually disconnect the kettle plug at the back, and turn the psu rocker switch off then back on.

This is pointing at PSU, but surely at MOBO also?

I think it happens only when the PC is idling... It didn't happen at all when I was running memtest for 5 or 6 hours last night, but then that is a low power utility I guess...
 
SeanyK said:
What I noticed was, to get the comp to start again, I had to actually disconnect the kettle plug at the back, and turn the psu rocker switch off then back on.
Click to expand...

Classic PSU problem.
For the sake of a tenner its worth it.
If it doesn't work then you can pull faces.
Over the last year I've had 5 PC's in front of me with what you're describing and all 5 were PSU problems.
 
Forget the tenner im just gonna get a new PSU, i'd rather spend the money and get a decent PSU, if it isnt that, i'll just make sure the PSU I get is better than the one I have lol.

However;

I got a BSOD a minute ago! With the error

avg7core.sys

at the bottom;

So I thought immediately, AVG.

Completely removed it from my system, tried a 3dmark06 and then got a BSOD after the CPU benchmark, and that BSOD says;

watchdog.sys

Bizarre!!!
 
im not expert but why is the vcore so low?? oh ok I guess its because the CPU is running at a lower speed if you have that thing enabled in the BIOS so it doesn't need as much voltage?
 
im not sure what the default vcore for your processor is but it does look low.
 
Q6600 G0 has a default vcore of 1.262v (according to Everest) - from googling:

also, says 1.325v is the default on another site.
 
You must log in or register to reply here.
Back
Top Bottom