DarkwingDuck
n00b
- 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.
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.