Newly built, will not boot

[nuscande]

The system boots, attempts to load, talks to the HDD(s), but will not continue.

I bought an ECS GF6100-M754 mobo.

I'm using an AMD Sempron 64 2800
[SDA2800AIO3BX courtesy of CPUWorld] in it.
I checked the link in the Sticky thread for compatibility
[http://www.ecs.com.tw/ECSWebSite/Support/CPU_Support_Model.aspx?detailid=820&
CategoryID=1&MenuID=69&LanID=0 courtesy of CPUWorld] and the list claims compatibility.

My choices of DDR RAM were/are:
Kingston KVR333X64C25/256, 256MB, Standard 32M X 64 Non-ECC 333MHz 184-pin Unbuffered DIMM and
Buffalo DD4333-S256/MG Non-ECC, Unbuffered, 400Mhz.
I have 6 decent to crappy HDDs to choose from ranging from an 80Gb Maxtor down to a 1.6GB Seagate.
This is just stash stuff at my disposal.

Observation?
I should use reservation about saying "boots".
The system lit meaning I arrived at the BIOS ok.
The unit continues, looks for the operating system, then gives a generic paragraph about hardware error -on all six HDDs which contain OSs ranging from 98 to XP.
It doesn't state anything specific.
This makes me think that a setting in the BIOS may not cover the items listed above.

I decided to try using a WinXP install cd to try to aid in troubleshooting.
The mobo has only one IDE channel and one SATA channel so already,
mounting a cdrom drive presented the second hurdle.
(I had to order a Samsung SATA DVD-RW drive)
[SH-S203N/BSBN @ NowDirect.com@$15.00+S/H if you're interested]

I have a StarTech PCI2IDE-100 dual channel PCI IDE controller.
I did manage to disable the primary channel inlieu of the mobo's primary control.
The system won't boot into the install.
It reads, loads, then halts.

The order was supposed to be a mobo/cpu combo.
They "sent" me this one.
I only have "tid-bits" in my stash to try out.
I have 9 days left to figure it out or return it.

[Chiefish]

Go back to the bare minmum, with one hard drive and one crom or dvd drive. Run it like that to make sure the rig is in working condition. Then if you want to have all those hard drives check to see if youre power supply is enough for it. And add them one by one to see if they are any good or whatever the problem may be. I dont know what the max that mother board can take.

[nuscande]

I've given you the wrong impression.
I used only one HDD at a time.
Ideally, I will have ever only had two HDDs in the system.
I used the 6 drives one at a time to determine that the drive didn't poop (cause the error).

[nuscande]

I pulled the RAM and restarted the unit.
POST worked fine - 4 long beeps.
Replaced the RAM - system lights.
After allowing the unit to continue loading, a menu displaying the partitions
on a 3.4Gb Seagate HDD display:
1 Windows Professional
2 Windows 98se.
Both yield the same result.
Bad or missing command interpreter and prompts me to path to file.

I have a Raidmax Sporpion case with a 320 watt ps.
It contains a FDD.
I enabled it and set it to begin the boot sequence.
Now I have a declared path for the command.com.
Nope, no good.
Keep in mind that these hard drives all have a known good OS on them.

Of note here is each HDD yields results unique to what OS it holds.
Win98se halts to a blank screen.
Win2000Pro blanks to a restart.
WinXP posts the generic error msg, then halts.
When I plug them back into the Dell Optiplex 810 that I long ago resurrected from the trash,
the HDDs all light, rather boot ok.

In the BIOS (of the ECS mobo), there is an Advanced Chipset Features header.
In this category there is a CPU Frequency entry - 200.0 to 300.0
with increments of .x or "in tenths".
Additionally, there is a: K8<->SB HT Speed
entry that re-occurrs here in other threads, but does not EXACTLY relate to my
particular case.
I am re-reading them to learn what I can.
I don't want you to think I'm lazy.
I'm just smart enough to know that I am stupid.

[nuscande]

I downloaded a recent version of Ultimate Boot CD (UBCDv5 Beta6 i believe) and it has provided me with a most
disturbing revelation.
Can you say "correcting pci irq routing table".
I' m saying all this gibberish to keep from using harsh language.
I suppose if even I have to return the board, I owe the authors of UBCD thanks and a debt of gratitude.

TABLE CHECKSUM 5Eh - Failed!
The ROM PCI IRQ routing table appears to be faulty!!

For anyone interested, I used the PCI (Low level PCI tool) to find it.
Phoenix Technologies, Award, Nvidia - one of these sonsa bitches are guilty.
I went to the ECSUSA.com site to find flash BIOS files.
After trying that, I only managed to loose the graphic of the BIOS, then return it.
Still no resolution to defective table.
Boy did I find a lot of stuff on the issue.
Still no resolution.
Still looking.

[Neon]

[nuscande]

The present system in question is a newly built one using an ECS mobo.
The hard drives in question ALL came from AMD systems.
I happed by them because people seem to think they need to have an Intel
driven system.
Hell yeah I'll take it.
I have a long history with AMDs.
Two of these hard drives came from systems I found in my dumpster.
Yep you guessed it, AMD.
I kept three of them (the actual AMD processors).
This unit I'm attempting unsuccessfully to build is a second unit, hence
my ability to reply here.
No Intel processors have touched these, at least since I've had them.

The problem I'm having exists before Windows has a chance.
It exists IN THE BIOS.
Take your BIOS chip out (if your motherboard allowed so), and try to
install Windows.
You'll find yourself in the same psych ward I'm in now.

Above, I explained that I found, on the shoulders of some great raw OS programs, the following error:

TABLE CHECKSUM 5Eh - Failed!
The ROM PCI IRQ routing table appears to be faulty!

I also explained that each HDD is fine and reboots into the hockey machines I pulled them from>> stash stuff at my disposal.

PCI routing table is used to make order of items, in their place, in their time.
The "routing table" exists in the PCI bus system and creates a "latch" from which the hard drives are even allowed to boot.
Now you can add Windows.
According to Mark Ludwig<<http://vx.netlux.org/lib/vml00.html>>
(yeah, I didn't know him until yesterday either),
this malfunction shares characteristics of a virus infected computer, as this is one of the outcomes of an infection.
INFECTED......., RIGHT OUT OF THE BOX?
Perhaps, but more than likely human error.

The remedy seems to point toward buying a re-flash:
<<http://www.phoenix.com/en/Customer+Services/BIOS/BIOS+FAQ/default.htm#Q31>>, or just throwing in the towel and starting again.
I've learned more in two days ...........
Replies like yours keep me plumbed up, make me go back and check myself, so thanks.

[vezhlys]

It is not a processor fault that your windows doesn't boot from other system (it doesn't matter AMD or Intel it was). It should be the same chipset at least (drive controller too). Otherwise windows won't boot even if you took your hard disk from other AMD system. Why don't you want just to reinstall a system? It might solve your problem.

[nuscande]

I'm guessing here, that my posts are too long, because none of the responses relate to my dilemma.
I may be out of line, but not ungrateful.

Vezhyls: That's an impressive collection of mpu's there.
You have all that in your stash?
I'm using an AMD Sempron 64 2800
[SDA2800AIO3BX - courtesy of CPU-World].
[http://www.cpu-world.com/CPUs/K8/AMD-Sempron%2064%202800%2B%20-%20SDA2800AIO3BX%20(SDA2800BXBOX).html0 - courtesy of CPU-World.com]
I'm hurt that I didn't see it in your collection.

"windows doesn't boot" does not apply to my post.
*.........TABLE CHECKSUM 5Eh - Failed!
*.........The ROM PCI IRQ routing table appears to be faulty!
The chipset uses comparative instruction against the BIOS.
If the system does not boot, there is no system, there is no Windows, there is no spoon.

"not a processor fault"
I stated above the I had/have been running a diag, so know that the unit "lights" or turns on ok.
I explained that I returned the units back to their original systems to check them.

Wait........, are you guys prankin' me?
I'm the village idiot here and you guys won't even read my posts.
Give up the gorram mobo and start again?
Is that what you are telling me?

[vezhlys]

You didn't understand me too. It is obvious that your system starts ok . I never stated that it is not. How can you get error messages then . If you can start Ultimate Boot CD (which is based on linux if I am not mistaken) you should be able to start other OS. However, windows will not start if you just took hard drive from other system. This is what we tried to say after your first post that you tried six different hard drives with "working" windows systems. You need to reinstall it. If you know this where is your problem? Regarding your error what have you done already to resolve it (you mentioned that you found a lot of information about this?) It is probably not BIOS problem either. It might be some hardware problem.

[nuscande]

The system only attempts to load.
How do I get error messages?
While I can not yet answer that, they seem to only originate from attempts
to apply or install the software(s).

You referenced UBCD and it being based in Linux.
At that point I started pounding my head on the desk.
I did not think to try Linux, so I did.

No good - it didn't work either.
It hangs at the marque.
Being familiar with release 7.0, 8.1, and now 10.1, I would say it is hanging
in the second stage.

I have Windows 98{98se, 98me, 98ce}, Windows 2000{2K, 2K Pro, and 2K Server}, XP{Home and Pro}, Windows Vista(Ultimate or some other
superlative title suffix).
So far NONE of these have successfully completed it's designed operation.

These diagnostics have all booted:
UBCD ver4.11
UBCD ver5 beta6
Hiren's Boot CD Ver9.0.

I mentioned above that I ordered a sata DVD-RW.
It came today.
I've installed it and will attempt to revisit a Windows install.
Our test (your suggestion and my effort) will work.
I've been working on it while typing this to give you the "up to the minute", "play by play" account of events.

While we're waiting, let me inform you that I committed the cardinal sin of connecting the IDE CDROM drive on the IDE Primary cable as a Pri-slave.
I tried this when NOTHING else worked.
Now having the SATA DVD-RW drive means going back to attempt the proper
arrangement.

OK.
After 4 minutes, 37 seconds, the XP Pro install has hung at 81%
(Copying: d3dx9_34.dll) of the "Copying necessary files to your computer"
phase of the install.
Your thoughts.

[Qwerty]

Hi,

it's my turn to give you stupid advises
It looks like the motherboard is damaged or there is a serious ressource conflict.

You can try to do the following steps:

- Plug a P-ATA HDD as primary master drive
- Connect a P-ATA CDROM as primary slave
- Remove all additional plug-in cards
- Reset BIOS to <SAFE> default settings - it's called "load fail-safe defaults" in your BIOS version.
- Deactivate ALL additional integrated devices like SATA, RAID, USB, FIREWIRE, network card and sound sytem.
- Clean the HDD (delete all partitions, repartition and reformat it)
- Install Windows XP

If you won't be able to install Win XP in this case - your motherboard is certainly damaged and must be replaced. If windows installs then you can carefully activate the build-in devices and adjust BIOS settings one by one. So you'll find the culprit.

And what's about your PSU? If its too weak the symptoms could be similar.
IMHO a noname 320W PSU is a weak one. Can you borrow and test a 500 - 600W one?

[D.8080]

Your sentences are heavy, you got me sleeping half way... like in 1st grade: keep it simple, short and straight to the point.

If you have a problem and come here, don't expect full support: we are giving help for free.

Calling people stupid isn't wise, and shows little respect.

If you feel that your problem can't be solved here just move to some other forum, we won't cry for you leaving.

[nuscande]

Hmmmmmmmmmmm, yet another worthy adversarial collegaue.....indeed.

The way you used the term "advices" made me think of a character in
Dark Forces2: Jedi Outcast

Let's set the bar here before we proceed.
Are we defining "damaged" as it ain't workin' right?
Or do we say UBCD has indicated faulty ROM IRQ routing table?
I'm trying to see how to apply your suggestions.
I only ask because my "find" for the last three days has been a third party re flash.
I still have 6 days.
I'm taking this to the wire before I get my piddly little credit
$50.00

You suggested hosting both HDD and CDROM drives on the same bus.
While I am quite guilty of this supposed no-no, it didn't complete the install.
P-ATA is parallel advanced technology attachment, correct?
I've never seen this written as such - good one.
I have performed the start-up with nothing in, and nothing on.
Not nude, deactivated. Little humor there.

Nothing except mobo mpu, ddr, hdd, cdrom, and power supply.
I loaded fail-safe AND default settings at the BIOS.
You are correct about it's substandard.
It came out of my stash.

Don't think ill of me and I don't mean to play with your terms.
Actually, this has me thinking a bit.
I have attempted 17 installs since my last post.
So far Windows 2003 Server got the farthest through an install.

[Qwerty]

If a clean install with minimum hardware and safe BIOS settings fails - the motherboard is defect and need to be replaced!