Event Viewver
-
Hi everyone, I got these errors at Event Viewver and I must be wait about 3 or 4 minutes for loading Windows "The driver detected a controller error on \Device\Harddisk0\D." "A parity error was detected on \Device\Ide\IdePort0." "An error was detected on device \Device\Harddisk0\D during a paging operation." I searched on the internet and saw people had this problem but I couldnt find any helpful answer for myself I scaned my harddisk with some tools and they didnt find any problem on the harddisk this problem is very wonderful for me for example when I turn on my computer and after boot up and loading windows I see that windows cant detect my graphic card and when I want to install graphic driver it hangs. Harddisk is Western digital(500GB) and Motherboard P35-DS3R and graphic Leadteck 8600GTS and OS xp2(I saw these errors on other windows)
-
Hi everyone, I got these errors at Event Viewver and I must be wait about 3 or 4 minutes for loading Windows "The driver detected a controller error on \Device\Harddisk0\D." "A parity error was detected on \Device\Ide\IdePort0." "An error was detected on device \Device\Harddisk0\D during a paging operation." I searched on the internet and saw people had this problem but I couldnt find any helpful answer for myself I scaned my harddisk with some tools and they didnt find any problem on the harddisk this problem is very wonderful for me for example when I turn on my computer and after boot up and loading windows I see that windows cant detect my graphic card and when I want to install graphic driver it hangs. Harddisk is Western digital(500GB) and Motherboard P35-DS3R and graphic Leadteck 8600GTS and OS xp2(I saw these errors on other windows)
The most common cause of this problem is using a 40-way cable on an ATA-66 (or faster) parallel ATA drive. These drives require an 80-way cable (every other wire being a ground wire) to run at the highest speeds. To prevent the problem Windows drops the bus speed further and further down and eventually reverts to Programmed I/O, which is incredibly slow. This generally causes timeouts when doing I/O. New Serial ATA wiring does not have this problem, but Windows treats any disk error on an ATA-compatible drive in the same way if using the standard ATA driver (atapi.sys/pciide.sys). Check that the cable is the correct type, is not damaged and is correctly installed. Also check that it's relatively short, just long enough to reach between the controller and disk. If you can, swap the cable with a known good one. If you still have problems the disk or motherboard may be faulty. Another source of problems that can manifest in many different ways is component overheating, due to inadequate ventilation or blocked ventilation holes. It's common to get a build-up of dust in fans and other confined spaces.
DoEvents: Generating unexpected recursion since 1991
-
The most common cause of this problem is using a 40-way cable on an ATA-66 (or faster) parallel ATA drive. These drives require an 80-way cable (every other wire being a ground wire) to run at the highest speeds. To prevent the problem Windows drops the bus speed further and further down and eventually reverts to Programmed I/O, which is incredibly slow. This generally causes timeouts when doing I/O. New Serial ATA wiring does not have this problem, but Windows treats any disk error on an ATA-compatible drive in the same way if using the standard ATA driver (atapi.sys/pciide.sys). Check that the cable is the correct type, is not damaged and is correctly installed. Also check that it's relatively short, just long enough to reach between the controller and disk. If you can, swap the cable with a known good one. If you still have problems the disk or motherboard may be faulty. Another source of problems that can manifest in many different ways is component overheating, due to inadequate ventilation or blocked ventilation holes. It's common to get a build-up of dust in fans and other confined spaces.
DoEvents: Generating unexpected recursion since 1991
-
The most common cause of this problem is using a 40-way cable on an ATA-66 (or faster) parallel ATA drive. These drives require an 80-way cable (every other wire being a ground wire) to run at the highest speeds. To prevent the problem Windows drops the bus speed further and further down and eventually reverts to Programmed I/O, which is incredibly slow. This generally causes timeouts when doing I/O. New Serial ATA wiring does not have this problem, but Windows treats any disk error on an ATA-compatible drive in the same way if using the standard ATA driver (atapi.sys/pciide.sys). Check that the cable is the correct type, is not damaged and is correctly installed. Also check that it's relatively short, just long enough to reach between the controller and disk. If you can, swap the cable with a known good one. If you still have problems the disk or motherboard may be faulty. Another source of problems that can manifest in many different ways is component overheating, due to inadequate ventilation or blocked ventilation holes. It's common to get a build-up of dust in fans and other confined spaces.
DoEvents: Generating unexpected recursion since 1991
I dont get this error repeated I get this error when I want to run a program or when I want to sacan my harddisk with Anivirus I get this error on the XP pack2 on the XP pack1 when I want to uninstall a program or delete some files my computer is freezed but on the Vista I can delete files. And another question do you have any idea about graphic driver that windows shows me this device has problem but when I restart it,it doesnt show any problem