Bad luck with this eMachine and cmos?

Joined
Jan 15, 2004
Messages
47
So I got a new pc, yes a low budget eMachine (around $600).

athlon 2.2 ghz, 1 gb ram, geforce onboard graphics, 160 gb hdd, windows vista home basic

literally had it less than 24 hours and i've noticed two hardware issues;

windows clock falls behind in time. which i'm guessing means a bad or dying cmos battery (already?)

the monitor has a "no signal" error that randomly appears. sometimes if I reboot or boot up, the monitor (a 19' widescreen lcd, HD) gives me a RGB screen that says "no signal" then goes black and kinda shuts off. If i leave the system off for a few minutes then turn it back on, this error goes away and I can boot into windows. I find this one strange cause when I am in windows the machine is whisper quiet in terms of fan noise and such, but when i reboot/boot up sometimes and get that error, the machine makes a lot more noise.

I literally unpacked this machine less than 24 hours ago, could I just have gotten bad luck on the draw with a faulty machine off the line?

I did the following software wise after unpacking;

Did Windows Update, got 25 new updates for Vista Home Basic w/ SP1
Turned off unneeded processes via Blackviper's Vista guide
Uninstalled a few of the bloatware app's that came with the PC (google desktop, etc)
Tweaked some of the UI (set it to Windows Classic, turned off the fancy graphics for the menus like dropback shadows etc)
Installed Firefox 3
Installed AVG free edition

now during that, I rebooted maybe half a dozen times with no monitor error issues, and I didn't notice the clock problem till maybe 8 or 9 hours later, it falls very far behind the time even after I sync it up.

The monitor error first occurred when I turned off System Restore, just another tweak to save resources. I rebooted after this, that's when I first got the "no signal" thing. (Yes, I checked the connections, even replugged them).

Aside from a fluke of a bad pc off the assembly, I'm stumped.
 
It could be that one of your tweaks have messed something up somewhere. I think it is good to uninstall as much bloatware as you can, but I would not bother with the Black Viper stuff as far as shutting off services, its really not needed on todays systems running Vista.

First thing I would do is set all your services back to default and see if that clears it up the clock and monitor problem. Next thing I would do is get some more ram, its cheap and Vista will run much snappier on your new PC.
 
The CMOS battery is an easy fix -- it's just a CR2032 watch battery. Replace the battery, reset the CMOS using its motherboard jumper (there should be instructions handy to show you how), and go into the BIOS to reconfigure your setttings. (But hold off on replacing the CMOS battery until after you complete CpuMan's recommendations.)

A "low budget eMachine"... are you using a Socket AM2 motherboard with DDR2 RAM, or a Socket 754/939 board with DDR RAM? (If you don't know, download and utilize CPU-Z to find out.)

If you're still having these problems after following our steps, return the eMachines system.
 
Well I'm looking through services to see if anything is causing it, nothing I know of that I turned off does. Even the w32tm service says it has no dependent or required services to run, and it's running, set on automatic.

The monitor I think is fine. What little, and I do mean little, documentation that came with the monitor says the error is somewhere else if the monitor receives power but nothing from the pc when it displays the no signal error (meaning it could be a random thing like a bad cord, or something).

I'll give another day or two, see if I can't hammer out the cause, if not then I'll exchange it.
 
Back
Top