Ahhh.. computer dying again??

Joined
May 25, 2005
Messages
1,006
Okay, so first I'll explain my old problem and how I thought I fixed it.

First, when I would boot, it would get through the Windows XP loading screen, then the screen would go black (monitor would go to standby), and after 20 seconds it would all die.
However, it would boot in safe mode. I eventually figured out that turning off the Nvidia Display Service (under services in msconfig) fixed the issue.
A few days later, right at the initial boot screen, it would sometimes not detect my hard drive (Western Digital Caviar 250gb). Either it would say "Disk Read Error" or it would say there is no hard drive.
At the point, safe mode wouldn't help.. nothing would. Reinstalling worked once, but then the XP install disc couldn't see the hard drive after a while.

So, I went out and purchased a new hard drive (the same one but brand new.. this drive has been great while I've had it..). Everything worked perfectly.. so I just assumed it was the hard drive failing early, and all was well.

It's been about two weeks now, and all of a sudden it's doing the same thing. Difference is, I can't get into safe mode at all. No matter what, computer decides to turn off when it gets past XP loading.

I guess I can try reinstalling, but I don't want to lose everything yet. Any other ideas?
(I do have an Acronis True Image backup image, but I never made the rescue cd.. I'm brilliant)
 
Data cable? Could that really be causing the Nvidia service failure?
And the PSU.. I know PSU issues can cause tons of random issues.

Hmm.. I forget how many watts I have, I know its between 500-600w. Should I use a stronger PSU due to the 7950gx2?
 
I don't believe not being to read the hard drive has anything to do with the Invdia service failure. A bad cable could indeed cause read errors.

As far as the PSU, the number of amps available on the 12 v. rail is much more important than the number of watts it's rated for. Tell us the make and model of the PSU.
 
Okay the PSU is a Enermax Noisetaker EG701AX-VE(W) (24P).
(I realized thats probably not the normal model name, that's just what it says on the side.
 
It seems like a pretty good PSU however, there are much more knowledgable people on these forums for PSU's than I. I did note that there is only 18 amps on each rail. It shouldn't be a problem if both rails are in use.

Try replaceing the cable to your drive and maybe even trying the drive in another computer. If the drive checks out, the MB may be the problem.
 
Yea, I'm thinking the mobo could be the problem.

Incase it is, I haven't looked into Core2Duo mobo's in a long while (I got my P5B Vanilla right when the e6600 was released).
If I'm interested in a bit of overclocking, but I would rather have more reliability, what should I go for?
 
Foxconn
Gigabyte
'Course I'm partial to Asus boards but these should give a few choices ranging from cheaper (Foxconn) to more expensive (Asus).
 
First, does anyone have any other ideas on how to try and fix this?

As far as the motherboards go, I'll spend $200 if I need to, I just still don't get the deal with C2D mobos. I've seen in many threads that the nvidia 680i boards are the best, but then in other threads apparently it has MANY problems. Does the DS3 have problems?
I just want a very reliable stable motherboard, with a bit of overclocking capability.
 
Its your PSU or motherboard. Check your voltages in your bios. If the voltages are jumping around or really high or low. They should all be within 20% about of the normal voltage(5V, 3.3V, 12V). If your voltages are fine then its your motherboard.
 
Are you overclocking your system?

If you are, set everything back to stock speeds. The problems you are describing could easily be explained by an unstable OC.
 
Voltages are all fine, and I even reset the BIOS settings and I still have the same problems.

I guess it's off to buy a motherboard..
 
Wait, one thing.

How come I am able to reinstall the system and have everything work perfectly for a few weeks... I mean this always ends up happening, but if it were the motherboard causing this issue, wouldn't it make it so no matter what, even if I reinstalled the system, it wouldn't boot?

I just don't want to go out and buy a mobo and realize that I never needed one because it was really some software issue..

Is there not some sort of test I can do to make sure that it IS the motherboard, and not software?
 
Back
Top