3401 with HD boot issue. HELP~

[Accord123]

HELP!!
I being using 3401M for 2 months, and now I have problem.  I can't boot.  Everything work fine for 2 months, and today after I turn off my computer, it won't boot up again.  After the BIOS finish its work, the computer just hang there.  Black screen, right before accessing the HD.

I have:
P4 2.8Ghz
Seagate Barra... 80GB 7200 RPM
Kingstone 256MB x 2

I have the SAME exact problem when I first put the computer together.  At first, I used the IBM 40GB harddrive from the old computer.  The BIOS recognized it, but couldn't install WinXP, because the screen stay black after it attempt to boot from CD.  So, I grab my friend's old Quantum FireBall 15BG harddrive, and plug it in, then it works.  So it seems like the IBM HD might got damage while I was putting things together.
Later, I went out, and bought Seagate, and work fine.  But today, the same thing happen.  Now, I'm running on that old "Quantum FireBall 15GB".   I plug my Seagate on my friends computer as a slave to see if anything is wrong.  Seagate work fine, but I didn't attempt to set it as master, cuz it's not my computer.

So far, this is what I have from BIOS.
Quantum---
LBA Mode: Supported
Async DMA: MultiWord DMA-2
Ultra DMA: Ultra DMA-4
S.M.A.R.T: Supported
Seagate---
LBA Mode: Supported
Async DMA: MultiWord DMA-2
Ultra DMA: Ultra DMA-5
S.M.A.R.T:  Supported

Any clue???  HELP HELP...

[Accord123]

3401 with HD boot issue.  HELP~

[Accord123]

 by the way, I'm using ATA

[eif]

I had a similar problem with my 3401M after I swapped the DVD ROM with a DVD-RW - the BIOS recognised the new drive but wouldn't boot from the hard disk or a bootable CD. The solution I found was to clear/reset the BIOS using the jumper on the motherboard. At the first boot I entered the BIOS and loaded the optimal settings, set boot priority etc. I'm not sure why changing the DVD drive should cause this, but all is well now. Hope this helps.

Gavin

[Erikro]

maybe a bios reset will help.

[Accord123]

hi, eif.
I tried that, but it still doesn't work.
Here's what happen.  As soon as I hook up my Seagate Harddrive, the screen turn black after POST even after I reset the BIOS through jumper.

I tried to isolate the problem, but it's hard.  Here some cases.
--case 1:  the computer run with 15 GB Quantum Drive (5+ yr old drive), and boot up couple time just fine.  I only had HD hook up, no other drive.  So, I attempt to hook up my DVD drive, so I can install some driver from CD.  But then the computer won't boot up at all.  Doesn't even have POST.  I though the monitor might not plug in properly, but it was.   This only happn 2, 3 times.  Cuz after I reset the BIOS, and boot with HD only, and attempt to plug back CD drive, then it works again.  It's odd.  cuz this just happen at random.

--case 2:  If I have 80GB Seagate HD plug in on IDE1 as master, the computer will run through POST, then turn to black screen.  Didn't even load up Windows.  But here again, a weird thing happen.  Few times, only having Seagate HD plug in, the computer won't even start, not even the POST.  But this also happen at RANDOM, only had occur 2, 3 times so far.  I reset BIOS, and plug in Quantum.

--case 3:  I run fine with Quantum on IDE1 as master, and tried to plug in HD on IDE2 as master (do I set it as master on second IDE connector? no, this is the not same connector as Quantum).  Then the computer won't start at all.  so, unplug, still won't start, no POST.  so, reset BIOS, have Quantum plug in only.  work again.

This random "no POST at all" bothers me, because I cannot isolate the problem.  At first, it seem like HD have problems, because the computer simply cannot boot Seagate.  But after different test, the computer "stuck" at random.

Any idea??  Seagate still work fine as a slave on my friend's computer.  I really need helps, this 5+ yr old Quantum HD is SLLLOOOOWWW..

[bogva]

Hey dude, could you fix it?
Cause I have similar problem from last night.
I thought I finaly FINISHED playing with upgrades and when I started it it wouldn't get even in POST

My main experiment was memory - swapping to different modules to find the best I can take from them.
On the last test I also changed the direction of the CPU fan and added again my external PSU fan.
Haven't done anything else that differs much from before - taking innards out and putting them together back.

I tried all kind of combinations. When all drives connected (or the 2 HDDs) the HDD LED is constantly lit. When the primary master only - no light.
I can hear all my components powering up but no POST.
I had similar situation when my RAM timings were wrong. Clearing the CMOS was resolving the BIOS and I could start afresh. Now this doesn't helps so I'm stucked
The only difference is that if I pressed the reset button nothing happened. Now I can hear the DVD drive access (if connected) but again no restart.

Now what? I don't whant to swear here...
I'm to the point to regret I started all that SFF thing. Sonata with IS7 would be cheaper and more relyable!

[Accord123]

sorry to hear that.  I know how you feel, because as a student with little $$, I couldn't afford this type of problem.

check this post, I reply to that post with some explination.
http://forums.sudhian.com/messageview.cfm?catid=102&threadid=58462

I think, we have one of those "weird" motherboard.  Cuz only few of us have this problem.  And it's not really defected, because it only happen once in a while.

Does not even have POST??  Reset BIOS from motherboard, see what happen.  If it still doesn't enter POST, wait for 2-3 hours, then it should work.  Do you have to wait for 2-3 hours??  NOPE, not on most computer, but for some unknown reason, 3401 "sometime" need to wait for couple hours to work right.  it is REALLY weird, but that's what I find out so far.

After your are able to enter POST, work from BIOS, try to isolate the problem.  For me, I end up knowing there's a problem between HD and Motherboard.  For what specific reason?  I don't know, because it just doesn't make sense.

hope this help

[bogva]

Yeah, it worked later but I don't think it need the 2-3 hours wait.
May be at least a minute wait after swapping the jumper for the CMOS.
I found that putting it to clear while mains is disconnected from the PSU, then connecting the mains, changing the jumper to the default (remember) position and disconect the mains again. Here wait a little and connect and start.
I had to do this as my memory modules when set up manually (timings or fsb ratio) I couldn't POST.

[Accord123]

OH WOW...  I'm finally back again...  my computer died 4 hours after I post my messages..  after more than a day later, it finally start running again.

Why am I pointing out the importance of "time"??  because that's the problem I'm facing.  Here's what it had been.

3/29/04, bought 3401, built it few days later, encounter problem, computer stuck after POST, can't load my old IBM HD, BIOS indicated the existance of my HD, POST had it too, after few restart, the computer "DIED", the screen remain black, monitor is not getting singal, HDD light remain on, so can't even enter BIOS.  waited 4 hrs later, without doing anything, computer start normally again.  couple restart, same thing, "DIED", waited couple hours, work again.....

see why I'm stressing so much on the time issue??  It does NOT make sense at all , but this IS what's happening.  Even when I was working with my Seagate HD.

I'm am familiar with upgrading, cuz I had been dealing with computer for 10 years.  And I have cousins who are in computer industry.

Okay, back to the thing that just happen yesterday.  All of a sudden, my computer "DIED" again.  monitor is getting no signal, HDD light remain on, so, I reset CMOS, still the same.  with my experience, I thought I'll have to wait couple hours to get it work again....  and nope, it didn't work...  so I tried every couple hours...  nope, none...  until just hour ago, monitor get singal, HDD light flash normally, the computer run again.

WEIRD WEIRD WEIRD...  and no virus in computer.  It's my final week right now, have lots of homework and test, but once I'm done with all the school work, I'll have to look into the problem.  cuz I can't stand computer dying for no reason every 4 weeks or so.

At this point, I believe I might have "defect" soltek.  or maybe soltek's motherboard just isn't relaible..

[DesertMouse]

Changed behavior after resting for a time can mean power leak or temperature change - pains in the butt to go after.  Good luck...

[Accord123]

I'm pretty sure heat is not the causes, cuz I always keep my eye on the temp, and CPU range between 37-44.  Motherboard temp hardly pass 40.

Consider I encounter this problem as soon as I built it, i'm pretty sure heat is not the cause.

I just bought ANOTHER Harddrive.  Just to make sure my 3 months new Seagate HD is not what causing the problem.  I'll swap out HD, and wait for couple weeks to see if the problem will occur again.

DeserMouse, can you explain more on powerleak?  The house is only 3 years old, and pretty high-tech (has CAT5 build in).  I have being using the same method to plug my computer and accessary for 2 years.  Prevoius computer work fine.

[Accord123]

I just remember another thing.
Under BIOS, for the IDE setting, where you get to set LBA, DMA mode, etc.  I set "32Bit Data Transfer" to enable.  I think I did that 2 months after I build the computer and encounter my "HD issue".  I swap to my old IBM drive, and set "32Bit Data Tansfer" to enable, and everything work again.  No problem with it, well, at least until last week.

Right now, I set it back to "disable".  I search couple site, and it seems like I should have it on "disable".  but I'm not 100% sure..  Anyone know?

[DesertMouse]

Power leak refers to capaciters or other elements capable of electrical storage that keep a circuit energized for a while past the point you think it is not energized.  This refers to system components, not external power sources.  The power "leaks" out over time, and the circuit is then truly "off".

Heat related issues can exist when observed temps seem OK.  If you sometimes find something working after a period of being "OFF", thermal issues are always my first consideration.  Energizing a circuit causes heat to be generated, and expansion to occur, and this expansion, within a packaged component or between components, is often the reason marginal components or connections fail.  When the system cools suffuciently, contraction occurs, and components return to functioning [this can take quite a while, as the components can 'stick' as they try to contract, and they may take time to 'snap' into place].  This does not require a great deal of heat - just more than the component or connection handles correctly.