Asus M2N-SLi Deluxe (Socket AM2) BIOS prob

[Akira]

Hi guys I have an Asus M2N-SLi Deluxe (Socket AM2) mobo and it's started to lose system time.

The date is fine, just the time....

Any ideas? I know various issues with the BIOS can cause it to lose track of time & date but one and not the other?

Many thanks,

Akira.

[peterb]

When you say lose time - is it running slowly, or the time resetting? First thought would be the CMOS backup battery, although it must be a fairly new mobo. When did the problem start? How old is the board?

[Akira]

Hello,

The mobo is approx 6 months old. The time is okay for a couple of days and then resets itself.

Cheers,

akira.

[peterb]

When did this start?

[Akira]

About 2 months ago I think

[peterb]

Change the CMOS battery - update the bios (if there is a newer version) Although I'm surprised that the backup battery has failed so soon - so there might be something more fundamental - but for the cost of a new battery, it is worth trying.

[Akira]

Superb, I'll try a new CMOS tonight - thanks for your help peterb.

[peterb]

Just one other thing - I'm assuming that you are getting an error message when you boot, and/or going to the Bios set up pages. If it isn't showing until Windows has booted, it may be that the localisation in Windows has changed, particularly if it is the hours that are wrong but the minutes correct (ie, it is out by a whole number of hours) If that is the case, then check the localisation settings.

[Akira]

Actually, I'm not getting any error messages at all - I'm simply noticing that the time has changed

[peterb]

By how much? Seconds, minutes? Per day, per week?

[Akira]

Whilst swapping the CMOS battery, and I don't know how I missed this, but one of the RAM chips wasn't sat fully in it's slot

Anyway, the system seems to be holding onto it's time now but after re-inserting the RAM, it took a few reboots for the system to start booting again and even now it pauses for a couple of minutes after playing the logon tune...

Another prob for another post I guess - thanks for your help Peter,

Akira.

[peterb]

Glad the one problem is fixed!

As for the memory - worth downloading a copy of memtest86+ and running it to check that the ram that wasn't installed properly hasn't been damaged - although RAM with damaged regions usually results (sooner or later) in a BSOD.

Just burn Memtest onto a CD and boot from it and leave it running for about 30 minutes - if there are any serious problems, they will show up fairly quickly.

What OS is it?

[Akira]

XP SP2 - yes, I've had to deal with a few BSODs down to faulty mem but I can't believe I missed it on my own PC!!