Sign in with
Sign up | Sign in
Your question

PC restarts 0.5s after being turned on, but otherwise works fine

Last response: in Systems
Share
June 13, 2009 8:43:56 PM

Hi,

As per the title really.. I have a homebuilt PC, with a Gigabyte EP-43-DS3L motherboard, and an E7400. I have noticed lately that sometimes, the computer will turn off within 0.5s of pressing the ON button. It will then wait for another half second, and then proceed to boot to windows and work normally. This happens so fast the bios screen dosent even appear. Once on, everything works perfectly.

In all fairness, I think this began after I overclocked the computer. This never happend at stock settings. FSB is now 333MHz (up from 266MHz), Multipler is now 10x (down from 10.5x), and FSB strap is 2.4B (was 3.0A), Fcpu is now 3.33GHz (up from 2.8GHz).

Any suggestions as to what I can do to rectify this? I am well aware that removing the overlock fixes it! but I would like advice on how to proceed, keeping a similar overlock, seeing that it works fine otherwise. (Reasonable tempertaures, stable etc)

Thanks
June 13, 2009 11:44:49 PM

What is your PSU?
a b B Homebuilt system
June 13, 2009 11:56:43 PM

It looks like the BIOS is trying to re-set itself because it thinks it's unstable. Also, you OCed via the BIOS right? Also, did you install DES (Dynamic Energy Saver) software that came with the driver DVD?
Related resources
June 14, 2009 11:44:26 AM

AKM880 said:
What is your PSU?


PSU is an OCZ stealthxtreme 500W
June 14, 2009 11:49:29 AM

Shadow703793 said:
It looks like the BIOS is trying to re-set itself because it thinks it's unstable. Also, you OCed via the BIOS right? Also, did you install DES (Dynamic Energy Saver) software that came with the driver DVD?


Yes, the overclock is set via the BIOS. I Have not installed the dynamic energy saver thing, I assumed that it would just add extra drivers and bloat that I would not want; perhaps I am wrong on that front!

I should also add that this seems to have something to do with FSB speed. I have tried a few combinations of overclock settings to asses each one. In my previous attempt, I achieved a similar cpu speed, but using a slightly lower FSB, and using the full 10.5x cpu multipler. I was using a 266MHz strap, and after reading about a bit i found that choosing a lower strap tightens MCH-FSB timings, so I changed the strap to the 333MHz one, and at the same time thought it best to set 333MHz FSB and lower the multipler to get the same overclock. Hoping it would be more stable...
June 14, 2009 3:18:11 PM

Could be your mobo deciding it doesn't like the OC and trying to reset. Never used a Gigabyte mobo, but my Asus board gives me an error message and resets to stock settings when something like that happens. I expect Gigabyte would do something similar. Any Gigabyte users out there?

I'm curious about what GPU do you have? If you have a beastly card(and your OC) the PSU might not be able to give enough amps from a cold boot. Thats why it starts, resets, warms up and then starts again with enough power to run fine. Just a thought.



a b B Homebuilt system
June 14, 2009 8:11:54 PM

Quote:
I am wrong on that front!

You are actually right in not loading DES. It makes system unstable.
June 14, 2009 11:18:23 PM

calinkula said:
Could be your mobo deciding it doesn't like the OC and trying to reset. Never used a Gigabyte mobo, but my Asus board gives me an error message and resets to stock settings when something like that happens. I expect Gigabyte would do something similar. Any Gigabyte users out there?

I'm curious about what GPU do you have? If you have a beastly card(and your OC) the PSU might not be able to give enough amps from a cold boot. Thats why it starts, resets, warms up and then starts again with enough power to run fine. Just a thought.


No beastly GPUs for me I'm afraid! I have by todays standards a fairly outdated Nvidia 8600GTS. The PSU idea sounds plausible; I think I will have to do some more experimentation is to see what the overclock threshold is for the problem appearing.
June 14, 2009 11:23:40 PM

Shadow703793 said:
Quote:
I am wrong on that front!

You are actually right in not loading DES. It makes system unstable.


Ahh good good. I assumed that logically without the drivers loaded the board would simply default to using all phases of the CPU regulator to guarantee that it could supply enough current to feed the processor otherwise the thing would likely die before it even got to windows.
!