HELP!! Problem with PC I just built.

Williamea

Junior Member
Apr 23, 2004
13
0
0
I?m having a problem with a PC I built last night.
1<SUP>st</SUP> let me list what I?m working with.
<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:eek:ffice:eek:ffice" /><o:p></o:p>
Mobo ? Asus P4P800 E Deluxe
SATA HDD ? Seagate 80gig
IDE HDD ? WD 120gig
<?xml:namespace prefix = st1 ns = "urn:schemas-microsoft-com:eek:ffice:smarttags" /><st1:Street><st1:address>DVD Drive</st1:address></st1:Street>
WinXP Pro SP1
<o:p></o:p>
I had the <st1:Street><st1:address>Sata Drive</st1:address></st1:Street> plugged into the Sata 1 port.
I had the IDE HDD and <st1:Street><st1:address>DVD Drive</st1:address></st1:Street> plugged into the Primary IDE Controller set as Master/Slave.
I am Install XP onto the Sata drive. That will be my primary drive.
<o:p></o:p>
The install seemed to work fine. The only odd thing was that it only allowed me to use NTFS, no option for Fat32.
<o:p></o:p>
Once Windows was booted it was fine for about 1-2 min then the screen would blur, it looked like desktop and icons were smeared, and the system hard locked. I would have to power Off/ON.
<o:p></o:p>
At first I thought it was a heat issue but I ruled that out after checking fans and the XP Install was fine.
<o:p></o:p>
I had been running this same setup for about 2 weeks minus the Sata drive. I took the old IDE drive I was using and hooked it up. It still had the Old XP image and it booted and performed fine.
<o:p></o:p>
I reconnected the Sata drive in its place and same issue.
<o:p></o:p>
I then moved the 120gig and DVD from Primary IDE to the Secondary IDE Controller and the system seemed fine. It ran for about 20 min and I was able to install a couple of apps.
<o:p></o:p>
Now I did not install any drivers and have not done any of the Windows updates.
<o:p></o:p>
Anyone have any ideas as to why the Sata drive seems to be locking up with the other drives plugged into the Primary IDE Controller?
<o:p></o:p>
<o:p></o:p>
<o:p></o:p>
Oh sorry about the long post.
 

DanTMWTMP

Lifer
Oct 7, 2001
15,908
19
81
my first guess/culprit --> power supply. See if a higher rated power supply will fix the problem.

I always get my power supplies at directron.com..chk them out