Unsolved

This post is more than 5 years old

3 Posts

73570

January 13th, 2004 07:00

Disable parity checking in BIOS?

On boot up, I am receiving the error:

I/O card parity interrupt at 6000:1B38, Type (S)hut off NMI, (R)eboot, other keys to continue

Hitting 'S' brings up:

I/O card parity interrupt at F000:2403, Type (S)hut off NMI, (R)eboot, other keys to continue

Hitting 'S' starts the computer into Windows correctly.  I am using a Dell Dimension 4600i Series with BIOS version A07 and WinXP.  The boot up error only occurs when I have a National Instruments (www.ni.com) PCI expansion card (PXI-MXI-3) installed.  The card allows me to communicate with 8 two channel Gage digital acquisition cards.  Gage (www.gage-applied.com) use the National Instruments cards as they are the industry standard.  I have no other PCI cards installed, and have removed the AGP graphics card (I am connecting the monitor directly to port on mother board). 

I need the computer to boot into Windows without user intervention.  Is there a way to disable parity checking on Dell computers??

I have connected the National Instruments card into a Viglen 200MHz computer running Win98.  No boot up error occurs, and the digital acquistion cards work correctly.

I have connected the National Instruments card into a Dell Dimension 8250 with BIOS version A03 and WinXP.  The parity interrupt boot up error occurs.

Any help you can provide on this issue would be appreciated, thanks.

1.9K Posts

January 13th, 2004 14:00

Whups, one more thing:  get a replacement card to be sure the one you have is not faulty.

Sorry for the second post....

1.9K Posts

January 13th, 2004 14:00

Not to be short or even harsh, but you've only a single option here, and that is to try the card in every available slot in an attempt to stop the error.

If that doesn't work, then the card is just plain incompatible with your system.  (You might attempt to e-mail the vendor to see if they've seen this with other Dell systems like yours.)

Good luck and I hope I'm wrong.  (And, no, there's no way to 'turn off' parity checking in BIOS due to a PCI conflict)

3 Posts

January 15th, 2004 07:00

Thanks for the reply, much appreciated. 

Unfortunately the boot up error occurs with the National Instruments card installed in any of the 3 PCI slots.  I will try calling National Instruments again today. 

Both Dell and NI are saying there is nothing physically wrong with their products, just an incompatability between the two!! 

I am leading towards having to buy a different make of computer.  Dell however will not allow the computer to be returned for a refund if there is nothing physcially wrong.  The other option is to look into other possible PCI to PCI expansion cards.

251 Posts

January 15th, 2004 20:00

I've got a couple of questions. Does the error happen on EVERY boot, and always with the same locations?

I'm guessing that your PCI card has a ROM, and it is being stuck into the memory map where there is active system RAM. That's bad. When the system BIOS accesses RAM, both the RAM and the PCI card answer, which causes the parity error. Check with the card MFGR, and see if the ROM can be disabled (or moved to a new location). That may fix it.

3 Posts

January 19th, 2004 08:00

Yes the error happens on every boot, and always with the same address locations.

I have contacted National Instruments, and they are looking into it.  They are talking with the people in their main office in the US, where the cards are built.  I have asked about any onboard ROM as you suggest.  They have not replied yet, but hopefully soon!!  Interestingly, NI admitted they have had some problems with their cards and both Dell and Compaq computers.  It is in their interest to resolve this...

251 Posts

January 19th, 2004 13:00

They are having trouble with Dell and Compaq computers? I think they should say they are having trouble in computers that actually check for PCI errors. I don't have one of these cards, so I can't test it myself, but I'll bet the card is generating errors on the PCI bus. The error message you get might just mislead you (it might not be a parity error (PERR), but it might be a system error (SERR) that is being reported as PERR. The old system you tested it on where it didn't fail may not be reporting the error.

I hope they can solve the problem for you.

0 events found

No Events found!

Top