Skip to main content

Unsolved

This post is more than 5 years old

whitmanj4

1 Rookie

 • 

1 Message

101734

May 18th, 2002 21:00

I/O Card Parity Interrupt

Upon turning on the machine this error often pops up and locks up the whole thing:

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


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





Message Edited on 05/18/02 05:33PM by whitmanj4

1 person also has this problem

whole9yard

2 Intern

 • 

279 Posts

May 18th, 2002 21:00

I had something like this with my computer and it was a bad network card. I don't know if you have one but you can remove it and see if this clears the problem and you can do this to your modem and sound card to see which card is the problem

whole9yard

2 Intern

 • 

279 Posts

May 18th, 2002 22:00

I did a search with microsoft and this is what I found http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q312927

govenator

2 Posts

October 27th, 2003 03:00

I know your message was posted quite some time ago, but I am having the same problem and cannot get much help from the tech support. Was a cure for this issue ever found? If so I would be very happy to hear it. Thanks.

Navin kurian

526 Posts

October 27th, 2003 06:00

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

Explanation: An expansion card has generated an error indicating incorrect operation.

Diagnosis: This is most probably an expansion card problem, particularly if it is associated with

only one expansion card in a system in which others are working properly. It could also be a

resource conflict of some sort.

Recommendation:

    * Troubleshoot the expansion cards in the system.
http://www.pcguide.com/ts/x/comp/mbsys/sys_ExpansionCards.htm
    * Troubleshoot the motherboard.
http://www.pcguide.com/ts/x/comp/mbsys/gen_Failure.htm

NMex Ron

5 Posts

July 28th, 2006 18:00

Had this same problem message:   "I/O parity card interrupt at F000:FEA5...".

Lightening apparently came in through the phone line. (It also burned up two phones and a DSL modem)

I checked out other discussions on this forum, removed the modem, and Thank God - it is working again.

Hope this message may help someone else out there

Thanks for your help.

Ron

Was this post helpful?

View All

No Events found!

Top