PC boots once, then refuses to boot until CMOS reset?

vamos

Member
Oct 17, 2001
35
0
0
Hi there, I just built a new pc with athlon quad core cpu and 2 x 4GB sticks of ram. The only other thing plugged in at present is the HDD.

After putting it all together I installed windows etc and everything works fine. However, once I shut down and tried to restart later, everything comes on but it doesnt boot. I get no beeps.

It starts up and runs perfectly fine if I start it up the next day after screwing around with it(fair amount of time elapsed), or if I discharge the CMOS and it starts up in default state.

It will also work fine if i choose 'restart' once in windows so it never actually turns off.

But - if i shut down and turn it off, then turn it on again, everything starts up - fans, lights etc etc but no signal goes to the monitor.

I'm using onboard gfx and this is the first time i've ever come across something like this.

Tried a bigger PS in the hopes that the new CPU needed more juice - no go.

Changed CMOS battery - 2 changes so far so 3 batteries total counting the original

Unplugged everything except HDD and one stick of ram - it started up coz i went from 8Gb of ram to 4GB ie change in BIOS but then shut down and turned on and back to the same thing.

Any thoughts?. The only other remote possibility I can think of is theres a short somewhere?. But why only on the second start vs the initial start?.

Any help appreciated!.
 
Last edited:

vamos

Member
Oct 17, 2001
35
0
0
Hope this helps!

OS - Win 7 Ultimate
Mb - MSI 890GXM-G65
Video - onboard
PSU - generic Bestec 300W
HDD - Seagate 1TB
Ram - G.Skill Ripjaws 2 x 4GB - DDR3-1333 PC3-10666 1.5V CL9-9-9-24
 

Bubbaleone

Golden Member
Nov 20, 2011
1,803
4
76
The latest BIOS Release is V1.13 (7642v1D.zip).

Check yours, as this BIOS update addresses memory compatiblity.

Are you using the VGA or DVI-D port?

Have you installed "Control Center" and used it to modify mobo settings?

Looking through the Users manual I noticed this about Control Center:

Important Note: Every time you turn-off the system, the settings will be restored to the factory default. If you want to use the saved settings, you have to load it every time by clicking the "Load" button.

I'd look at that very closely.
 
Last edited:

vamos

Member
Oct 17, 2001
35
0
0
Thanks for the advice. I flashed the latest BIOS on. Still the same issue.

using VGA port on an old CRT monitor. the monitor itself is fine.

Using stock Win 7. No installation of this Control Center thingie and no overclocking options in the BIOS.

plain vanilla.
 

Bubbaleone

Golden Member
Nov 20, 2011
1,803
4
76
Since it's a "vanilla" hardware and OS build, I'd suggest taking the mobo and power supply out of the case. Set it up on a non-conductive surface (corrugated cardboard works), connect the PSU, HDD, monitor, mouse, and keyboard then test it like that to see if the problem still occurs.

If it behaves normally, check that the mobo mounting screws and/or standoffs are in the right locations, I/O shield is mounted correctly, and nothing conductive on the mobo is grounding anywhere when you reinstall it in the case.
 
Last edited:

Bubbaleone

Golden Member
Nov 20, 2011
1,803
4
76
One other thing; it's confusing that first you state: "everything comes on but it doesnt boot. I get no beeps", and then further on you state: "But - if i shut down and turn it off, then turn it on again, everything starts up - fans, lights etc etc but no signal goes to the monitor". Please clarify the actual situation.

If it's the monitor not turning on, that "old CRT monitor" might be the culprit. A system can boot just fine without a monitor even being connected.
 
Last edited:

vamos

Member
Oct 17, 2001
35
0
0
I mean when I start up after discharging the CMOS, it boots up normally and goes into windows.

When I restart within windows(so that it never actually turns off), it also goes straight into windows with the usual startup beeps.

When i choose "shut down" so the pc turns off, then hit the power button to start up, the light on the mb comes on, the cpu and PS fans turn on etc, but no beeps and no signal to monitor and no boot to windows.

discharge CMOS = works fine again.
 

denis280

Diamond Member
Jan 16, 2011
3,434
9
81
Ok so you have to fix the time and date all the time.if yes that mobo is defective
 

vamos

Member
Oct 17, 2001
35
0
0
I do have to set the time and date but only after resetting the CMOS. It doesnt reset by itself.

The thing I cant figure out is why does it boot up after resetting CMOS and works just fine, but once shut off and turned back on, refuses to boot.
 

denis280

Diamond Member
Jan 16, 2011
3,434
9
81
when you reset cmos. it go in to default.so my opinion is the mobo.or you could try a chkdsk for disk errors.but i doubt it
 

Bubbaleone

Golden Member
Nov 20, 2011
1,803
4
76
I mean when I start up after discharging the CMOS, it boots up normally and goes into windows.

When I restart within windows(so that it never actually turns off), it also goes straight into windows with the usual startup beeps.

When i choose "shut down" so the pc turns off, then hit the power button to start up, the light on the mb comes on, the cpu and PS fans turn on etc, but no beeps and no signal to monitor and no boot to windows.

discharge CMOS = works fine again.

The only time you'll here a beep code is if there's hardware problem with the mobo. You're not going to hear a beep code if the monitor is defective.

What I mean is it sounds like the system is booting just fine, but the monitor isn't turning on. Unless you've already hooked up a different monitor,and tested with it, how do you know there is "....no signal to monitor and no boot to windows."?
 

Matt1970

Lifer
Mar 19, 2007
12,320
3
0
Try running it without a hard drive. Also get it into Windows and run CPUz on it and see if all the voltages are correct on the board.
 

vamos

Member
Oct 17, 2001
35
0
0
I've also used the monitor with another pc and it works just fine. no changes in cabling or anything.

it also works fine on the above build for that first startup. once i turn it off and turn it back on again, then no signal to monitor and no POST beep.
 

dbcooper1

Senior member
May 22, 2008
594
0
76
Are you changing any other BIOS settings from default when you change the time & date? Also might try different RAM to see how it behaves.
 

Bubbaleone

Golden Member
Nov 20, 2011
1,803
4
76
If you've actually followed the suggestions that AT members have offered you here, and you're still in the exact same spot, then perhaps you should consider contacting your reseller and getting an RMA for the MSI mobo.
 

C1

Platinum Member
Feb 21, 2008
2,346
94
91
You need to start trying some things:

- What happens on the second start if you try to immediately enter the BIOS (instead of attempting to complete POST)? That is, do you get video?

- On the second start (and there is no monitor), what happens when you disconnect then immediately reconnect the video cable?

- What happens if you use a different monitor?

- Inspect your BIOS very carefully (including power management area) to see what controls there are involving video. Try changing some settings. You may end up going with a PCI-E video card.

- After the first boot (and you have windows), inspect carefully the video settings in windows for the onboard graphics. If there are capabilities for power management then try changing some settings.

- Usually MB's come with a CD for the OS dependent drivers for the onboard chips (including graphics). Ensure that the MB onboard GPU driver has been properly installed. Verify the correct GPU installation in device manager. Sometime order of installation of drivers can be an issue (eg, windows may have substituted some generic driver for the correct driver that comes with the MB and on shutdown after the first boot sets something in the BIOS or power management that affects the video).
 

vamos

Member
Oct 17, 2001
35
0
0
Thanks for all the help guys.

It turns out of all things it was the ram voltage and/or timings. Never even occurred to me to look at coz I figured if it booted the first time, all hunky dory right?.

wrong.

Anyway, something to add to the knowledge base if anyone else has this issue in future.