To start with:
OS: Windows XP SP1
RAM: 1 piece DDR2700 512Mb Kingston (non-o/ced)
CPU: AMD 1662 Mhz (XP 2000+ I think)
CD-Rom: Lite On (ATA 33 Secondary IDE)
DVD-RW: Lite On (ATA 33 Secondary IDE)
Mobo: Aopen AK 75
Sound: SB Live
HDD: Maxtor 250Gb (120Gb each C:, D (ATA100 Primary IDE sole)
Graph: 64Mb NVidia GEForce 4 Ti 4200
P/S : Enermax 350 Watts
Casing: Regular normal
Programs in background normally: MSN messenger, AVG, Zonealarm, Yahoo Messenger
Didn't install any new peripherals/special software/tweaking.
Computer was up and running perfect. Nothing seemed to go wrong. (as usual)
No Heating problems: CPU temp: 50Celcius max, mobo 42 max.
I'm still not 100% sure wat's the exact cause of the error here.
Problems started a month back.
Problem 1:
Start -> Programs -> Restart. Computer will seem to run into an endless loop. Screen will not light up on monitor. The CD/DVD will have the busy indicator and if ejected, it will go back in again (that's how I presume it's just repeatedly restarting). Note there isn't the start up beep (unlike the normal procedure when the mobo boots itself)
Problem 2:
Com just shuts down. Literally. No shut-down screen or anything. I've played around and am attributing this to an overload on the CPU/bad P/S / Bad mobo / RAM. Whenever I try to multitask such as read D: (partioned drive) or if I try to keep jumping tracks on the DVD (Overload buffer), the com will just shut down. If i try to power on straight away, the mobo will switch on up to the point it initiates the AGP(monitor lights up) and then power out again. The only way to power this on is to wait for the HDD to stop completely - wait for 30sec - then power it up.
Most recent test (as I'm typing this):
Took out CD/DVD-drives, Ran CPU_Burn_in(load CPU 100%) - and ran multiple programs for abt an hour. CPU seems to run totally ok. (I am going to assume the same for the RAM and the power supply). 3 left:
Mobo, DVD-ROm (CD totally removed), the cable connecting them.
All this while I'm assuming it's a hardware problem (something burned).
It'll be great if I can get some input from you guys. LMK if u need anymore info.
Thanks in advance.
OS: Windows XP SP1
RAM: 1 piece DDR2700 512Mb Kingston (non-o/ced)
CPU: AMD 1662 Mhz (XP 2000+ I think)
CD-Rom: Lite On (ATA 33 Secondary IDE)
DVD-RW: Lite On (ATA 33 Secondary IDE)
Mobo: Aopen AK 75
Sound: SB Live
HDD: Maxtor 250Gb (120Gb each C:, D (ATA100 Primary IDE sole)
Graph: 64Mb NVidia GEForce 4 Ti 4200
P/S : Enermax 350 Watts
Casing: Regular normal
Programs in background normally: MSN messenger, AVG, Zonealarm, Yahoo Messenger
Didn't install any new peripherals/special software/tweaking.
Computer was up and running perfect. Nothing seemed to go wrong. (as usual)
No Heating problems: CPU temp: 50Celcius max, mobo 42 max.
I'm still not 100% sure wat's the exact cause of the error here.
Problems started a month back.
Problem 1:
Start -> Programs -> Restart. Computer will seem to run into an endless loop. Screen will not light up on monitor. The CD/DVD will have the busy indicator and if ejected, it will go back in again (that's how I presume it's just repeatedly restarting). Note there isn't the start up beep (unlike the normal procedure when the mobo boots itself)
Problem 2:
Com just shuts down. Literally. No shut-down screen or anything. I've played around and am attributing this to an overload on the CPU/bad P/S / Bad mobo / RAM. Whenever I try to multitask such as read D: (partioned drive) or if I try to keep jumping tracks on the DVD (Overload buffer), the com will just shut down. If i try to power on straight away, the mobo will switch on up to the point it initiates the AGP(monitor lights up) and then power out again. The only way to power this on is to wait for the HDD to stop completely - wait for 30sec - then power it up.
Most recent test (as I'm typing this):
Took out CD/DVD-drives, Ran CPU_Burn_in(load CPU 100%) - and ran multiple programs for abt an hour. CPU seems to run totally ok. (I am going to assume the same for the RAM and the power supply). 3 left:
Mobo, DVD-ROm (CD totally removed), the cable connecting them.
All this while I'm assuming it's a hardware problem (something burned).
It'll be great if I can get some input from you guys. LMK if u need anymore info.
Thanks in advance.