Unfortunately, what you may also discover is that if the source of the CRC or Bad Pool Call errors continues, the device will again be reset to PIO mode, or even "turned off", forcing you to continue to reinstall the device over time as the errors accumulate.
Here's an example URL where a similar situation occurred with several Plextor models:
<A HREF="
http://www.plextor.com/english/support/faqs/G00012.htm" target="_new">Why do I get data corruption or CRC errors with Windows XP or NT?</A>
However, in my experience, there are other possible reasons for this kind of error to occur, which may have nothing to do with damage to the IDE cable, the ATAPI controller, or jumpering the UDMA connector.
1.) Poorly written or incompatible chipset drivers.
2.) An out-of-date or buggy BIOS version
3.) The Imapi CD Burning COM Service causing time-outs while using software such as Nero.
4.) Incompatibilities with the Advanced Programmable Interrupt Controller in the BIOS and Win2K/WinXP, mostly found on newer mainboards, and not activated until a 32-bit OS is installed, as Win9x does not use this kind of controller.
My Current Working Solutions:
1.) Intel boards ... update the chipset drivers. VIA boards, install only the AGP GART driver, instead of the complete 4in1's.
2.) Flash the BIOS to the latest version.
3.) Disable the service.
4.) Change the Interrupt Controller in the BIOS to PIC, and then either freshly reinstall the OS (my preference), or run a repair from the Recovery Console or the OS CD. The APIC allocates 255 virtual IRQ's through just one IRQ for the system devices, and this single IRQ is used as a "gateway". While this is not always a concern, occasionally the BIOS on certain mainboards will attempt to interfere with the way Windows allocates the IRQ addresses at the hardware level, and this causes conflicts which may not always be detectable in the Device Manager. I have found this to be especially apt when referring to older Intel Socket 423 mainboards, but the problem is definitely not exclusive to these boards. Flashing the BIOS does not always correct the problem ... sometimes the only solution is physically changing the type of controller in the BIOS so that only the "actual" hardware IRQ addresses are used.
If none of this works, you may be looking at a replacement mainboard.
That's my two cents.
Toey
<font color=red>First Rig:</font color=red> <A HREF="
http://www.anandtech.com/mysystemrig.html?rigid=17935" target="_new"><font color=green>Toejam31's Devastating Dalek Destroyer</font color=green></A>
<font color=red>Second Rig:</font color=red> <A HREF="
http://www.anandtech.com/mysystemrig.html?rigid=15942" target="_new"><font color=green>Toey's Dynamite DDR Duron</font color=green></A>
________________________________________
<A HREF="
http://www.btvillarin.com/phpBB/index.php" target="_new"><b><font color=purple>BTVILLARIN.com</font color=purple></b></A> - <i><font color=orange>A better place to be</font color=orange></i>. :wink: