Log in

View Full Version : Solution: Slow DVD Ripping & 100% CPU


the godfather
20th September 2006, 21:58
while browsing the forum looking for an answer to why it was taking me extremely long to rip a DVD to the hard disk using DVD Shrink. Normally it would take me 15-30 minutes depending on the length of the DVD, encrpytion and whether i used deep analysis. Then suddenly it took a lot longer (at least 1 hour usually nearly two.) I also noticed that opening other programs was becoming extremly slow as well and when i opened task manager the CPU was running about 100% all the time. Even when i used another program DVDFabDecrypter the ripping process still took nearly 2 hours. It drove me mad. i looked around the internet for ages to try and find a solution. Everybody just said check that DMA is enabled. DMA was enabled so i was at a dead end. Then i suddenly decided to uninstall the primary IDE channel where the DVD Drives were. Then install them back on. And guess what? It worked i can now rip DVD's to my computer in 15-30 minutes again. If anyone else has this problem and is lost just try going into device manager (start, control panel, system, hardware tab) then locate the IDE chanel where your DVD drive is located (usually primary) right click on it and click 'uninstall' (ignore the warning). if it says restart then restart your computer. Then go back into device manger and click under the IDE chanel tab 'scan for hardware changes'. It should find your DVD drive again and then install the drivers automatically and then your ripping speed should increase and your CPU level should drop back so that you can use your computer again while backing up a DVD (or it did for me anyway)

hope this helps

the godfather

VWRacer
22nd September 2006, 14:13
Best guess on this is your drives have shifted into PIO mode. You have all the symptoms. Solution:
Go into device manager and pull up your IDE/ATE controllers. Check both channels Advanced settings. They are probably reading PIO, instead of DMA. Uninstall the offending channel, and reboot. It will reacquire the channels, as DMA, and you're back in business.

When you're done, check your Event log, and see if there any telltale red flags that might point to a repetative problem causing the change in modes.

Racer