Unsolved
This post is more than 5 years old
1 Rookie
•
5 Posts
0
72147
August 3rd, 2009 16:00
i/o card parity interrupt at 1000:00B3
Dad's computer is locked up and says the following:
I/O card parity interrupt at 1000:B3
Can any one help me out there?
Thank you,
Jay
No Events found!
RoHe
10 Elder
•
45.2K Posts
0
August 3rd, 2009 17:00
Always include the PC model number and version of Windows in your posts! :emotion-5:
When do you see that message?
Has any new hardware or software been installed recently?
Have you tried booting in Safe Mode (F8 before Windows starts to load)?
Have you tried "last known good" (F8 before Windows starts to load)?
Might be a bum video card.
Ron
richardylight
4 Posts
0
March 12th, 2010 08:00
I have exactly the same problem on my dell xps 210.
RoHe
10 Elder
•
45.2K Posts
0
March 12th, 2010 10:00
Richard -
Remove all PCI cards, except video card. Then remove the motherboard battery and press/hold the power button on the tower for ~30 sec. Reinstall the battery (right-side-up!) and see if it boots with only mouse, monitor and keyboard attached. If the problem persists, then your video card may have failed...
NOTE: Always power off, unplug, and press/hold the power button on the tower for ~15 sec before opening the case.
Ron
lancifer77
1 Message
0
March 28th, 2010 10:00
Dell xps210 windows home xp sp3
I have the exact same problem. This is the first screen you see, there is no "DELL" screen when this happens, and no "beep". The hard drive is never seen, it is not a software issue. Pulling out every card and piece of hardware does not make any difference. Even the battery and power switch trick makes no difference., The only video is onboard the M/B. The only thing that makes any difference, is if I pull out all the memory, then it will beep! Put it back, and its back to the i/o error. I can only assume this is a M/B problem and the machine is dead. Problem is, usually, it comes back to life and acts as if nothing is wrong, until the problem happens again 2 weeks later.
This last time, it worked great for a week, until I shut it down, and it hasn't come back since.
Lance