Computer Hope

Microsoft => Microsoft Windows => Windows XP => Topic started by: Kando on August 31, 2009, 09:29:45 AM

Title: i/o card parity interrupt at f000:f188
Post by: Kando on August 31, 2009, 09:29:45 AM
Now this is something I have not seen before. Turned on the computer and got this error message: i/o card parity interrupt at f000:f188. I was given the option to shut down or reboot, shut down turned off the computer and reboot gave the same message. I checked online to see what this could be and found it might be a new hardware installation (no new hardware was installed), it might have something to do with the bios needing to be updated (computer right next to it with same version, installed at same time boots with no errors).

I checked in the case and all cards are secure, the ram in secure and the cables are tight. I was able to get the computer to boot fully by tapping the DEL key, but when restarted it went to the error message again. There are only two cards installed, a video card and a firewire card. The video is on a riser, firewire into a pci slot.

Fiddled with it some more and it has now booted fully again. Going to put a big sign on it "DO NOT TURN OFF".

Still looking for the reason for the error.

Dell Optiplex 755
WinXP Pro sp3
core2 duo, 2.53ghz
2gb ram
bios version A11 dated 8/4/08

Thanks
Title: Re: i/o card parity interrupt at f000:f188
Post by: patio on August 31, 2009, 10:10:35 AM
List all addon cards you have in this machine...
Title: Re: i/o card parity interrupt at f000:f188
Post by: Kando on August 31, 2009, 10:33:26 AM
Like I said, there are two cards installed, a video card in a riser and a firewire card installed directly into the pci slot. The riser is in pci slot 1 and the firewire is in pci slot 3.

Ok, got back to the machine and pulled the cards. The video is a Dell branded DVI installed in an agp slot on the riser card. The firewire card  has pca-00214-01-a and e175975 but no name on it. That is installed in the pci slot on the motherboard.

hope this helps.
Title: Re: i/o card parity interrupt at f000:f188
Post by: patio on August 31, 2009, 11:18:05 AM
Remove the firewire card and do a few consecutive cold boots...
Title: Re: i/o card parity interrupt at f000:f188
Post by: Kando on August 31, 2009, 11:18:48 AM
ok will try it and let you know.
Title: Re: i/o card parity interrupt at f000:f188
Post by: patio on August 31, 2009, 11:47:16 AM
Also you said the vid card is on a riser card...is this accurate ? ?
Title: Re: i/o card parity interrupt at f000:f188
Post by: Kando on August 31, 2009, 12:39:10 PM
Ok, took out the firewire card, rebooted and it came up fine. shut down and rebooted 4 times and came up each time.

Yes, the video card is on a riser. The gx755 we have is a small form factor desktop and the video card is full height. The riser is in the agp and pci slots on the motherboard and the video card is in the agp slot on the riser. That makes the card parallel to the motherboard. Not my idea of good planning, but then my name is not Mike Dell.

Well it looks like that has fixed the problem for now. I will keep an eye on it and when I get the chance will put the card in another machine and see if the error message comes back.

Thanks
Title: Re: i/o card parity interrupt at f000:f188
Post by: patio on August 31, 2009, 05:10:56 PM
My guess is the firewire card has taken a dump...
Good to hear you are temporarily fixed up though and Welcome Aboard ! !
Title: Re: i/o card parity interrupt at f000:f188
Post by: mrdell on January 19, 2010, 04:52:26 PM
ummmm i have the same problem but i got no cards and it just happened out of the blue





i have:
Windows xp
1 Gb of ram
92 Gb of hard drive
3.2 ghz
pentium 4
Title: Re: i/o card parity interrupt at f000:f188
Post by: Steinhwe on March 17, 2011, 11:24:31 AM
I just experienced the "I/O parity" problem on my Dell XPS running XP.  I took the suggestion of tapping the F12 key and got into setup.  On the Boot up option it was factory set at "fast boot up."  On a whim I changed it to "slow boot up" ( "Fast" and "slow" boot up terms may not be the exact terminology on the screen but you should have no problem identifying the actual terms.)  That change allowed a full boot up and appears to have solved the problem.  Why?  I have no idea but it has now worked for several boot ups.