Hello, I currently have a Pentium III (700 mhz, 384MB ram, Asus motherboard) computer that I purchased from a local vendor. I recently upgraded to Win2K Professional from Windows98 and am very pleased with the new OS, with one exception: When I use my DVD drive (an Afreey DD-4010E DVD-ROM) to read data from disks (run external programs, such a various CD-based reference packages) or copy files from a CD to my harddrive, CPU usage skyrockets to 100% and can only be reduced to normal levels by rebooting the machine. The high CPU usage remains even after the copying / reading process is completed and the disk removed from the drive. I checked the Task Manager to see what processes were demanding the processing power and was surprised to find that the basic "System" process was the culprit. My other CD drive, a Samsung CD-RW, does not exhibit this behavior. In order to remedy the problem, I have: - installed all Win2K service packs / patches (with the exception of the latest security package) - turned off the indexing services - installed the latest DVD programs and drivers for my drive (I use the ATI package that is compatible with my ATI video card). Any clue as to what is causing the high CPU usage and how I can remedy the situation? Thanks in advance for you help.

Type "high cpu usage" in the search box at the top right of this page against Win 2000 - there are lots of references. It may be normal - DVD has a much greater data density than CD and W2K is more complex than Win 98. It may be clearing swap space or processing other legitimate instructions even after the main task is completed. You could time the high usage to see just how long it does last. More memory may help. Also do a virus sweep as a precaution.

Is there any possibilty that DMA could cause this problem? I suggest u reinstall your mother board patch/IDE driver. As to a PIII 700 + 384 MB RAM configuration, it should not caused by resouce limited. Since your w2k was upgraded from w98, maybe u can try a clean install of w2k to identify this problem.

Could be a memroy leak, make sure your drivers are fully compatible with win2k. Drivers that are not quite compatible can hang in the memory space and suck up processer space. Not really use it, just squat there waiting for commands.