Problems with my win2k inst. on BP6

[Burning_Ice 0]

I've got a serious problem with my new BP6. Win2k pro. installation bluescreens when "detecting devices". The error message is different every time, from SCSI.SYS and PCI.SYS error to ntoskrnl.exe saying IRQ_NOT_LESS_OR EQUAL.

 

My system: Abit BP6 mobo, 2x 400@400 mhz celery, 256 mb ram, Tekram 390F SCSI controller with Quantum 9.1 GB hd and Pioneer 6x dvd, SBLive!, IntelPRO NIC, G400, HP 9110i IDE burner, floppy and LS120

 

Newest bios on the scsi controller, the udma/66 controller and the mobo. Actually i've tried bp6_qq.b01, bp6_qq.bin and bp6_nj.bin but none of them seems to work.

 

I press F6 and specifies the newest driver for my SCSI controller and the udma/66 under the inst. and i even tried taking my SCSI out and install on a IDE HD. Nothing seems to work.

 

And for ur information. It all worked fine on my old TMC mobo with K6-III 450 mhz.

[BlaZeR2 0]

I get the exact same problem. I have been investigating the situation for quite some time now. i am overclocking dual celery 366 to 550 with 100 mhz fsb. I think this is the problem. I also get some errors in event viewer about the HT366 controllers timing out while waiting for an interupt or something. I think this is an overclocking issue also. I recently declocked my cpu's back down to 366 to test the results, so far, no crashes. However the crashes were not that common in the first place, maybe one a day.

 

If any body knows anything about this, i would appreciate help, I am running two ultra 33 drives on the secondary channel of teh ultra 66 controller because the primary controller won't recognize that i have any drives plugged into it.

 

Thanks

BlaZeR2

[Burning_Ice 0]

Sounds really wierd. But I haven't been overcklocking mine at all. It's pure 400 mhz at 66 mhz fsb. It's very irretating coz I can't use my computer at all.

[Burning_Ice 0]

Okay, now it worked. I moved my SCSI card from PCI3 down to PCI4 and my NIC from PCI5 to PCI1 and then it just worked fine. I'm using the qq bios and windows sees my comp. as an ACPI MPS without any problems at all.

It looks like the HPT controller is using the same IRQ as PCI3 so don't use that one with a card who needs an IRQ

[Burning_Ice 0]

Okay, now it worked. I moved my SCSI card down to PCI4 and my NIC from PCI5 to PCI1 and then it just worked fine. I'm using the qq bios and windows sees my comp. as an ACPI SMP without any problems at all.

So it must have been this IRQ conflict problem with the HPT and PCI3.

Thanx alot for ur help.

[Burning_Ice 0]

Okay, now it worked. I moved my SCSI card down to PCI4 and my NIC from PCI5 to PCI1 and then it just worked fine. I'm using the qq bios and windows sees my comp. as an ACPI SMP without any problems at all.

So it must have been this IRQ conflict problem with the HPT and PCI3.

[Abaddon 0]

The above error is an irq sharing problem, but I thought it only occured with non plug and play oses such as nt4. I recieved it under nt4, pci3 shares its busmastering and irq with the hpt366. Both highpoint and symbios when contacted told me that thier devices share irqs, supposedly there are only problems with shared irqs under non plug and play oses, but I received problems under windows 98 as well. Needless to say I can't get the scsi card to work in any slot now, and I have to leave slot 3 empty because I have yet to find a device that will share with the hpt366 successfully.

[HarU 0]

The best way to do a win2k install is to do it with only your vid card in. I have to do this at work all the time.

 

If you do this, not only will it install fine, but you can spread out your irqs. Put sound in next, reboot, then put in network, reboot, then put in scsi, reboot. Then all of your irqs will be spaced out.