Hello I have got a 120 Gig HDD (Western Digital), and I have 3 partitions (1 primary and 2 logical). When I'm trying to defragment them, all but 1 do, but the first logical partition doesn't. The error pos up saying "dfrgntfs.exehas generated errors and will be closed by Windows. You will need too restart the program An error log is blah-blah-blah" that and "OK" button. \ When I click "OK" (The only option), Disk Defragmenter says (G:)(the problematic partition) Engine Connection Lost. And I don't know if there is anything I can do. The other 2 partitions depend on the very same engine, and they have no problem derfagmenting. I can still move files to G:\ and run programs from it... My Windows is fully up to date, except Media Player, but that shouldn't hurt right? Any ideas on how to fix the problem would be appreciated. 80% of my programs are on that partition, and i hope it won't get too fragmented... thanx

Have you tried defragging while in the safe mode? Here is a great free tool that should work should the safe mode not work. The link for it can be found under readers suggestions, item 5 (DISKEEPER LITE) at http://www.langa.com/newsletters/2003/2003-09-11.htm If you do not suscribe, it is definitely worth a look and it is free. Take care and all the best!

This prog did not really do as much as as gave me an idea of what I should do - CHECK THE DISK FOR ERRORS!!! There was one that was giving me grief BTW, the prog, while looks cool, does the exact same job as default Win2K/XP Defragging tool, it even uses DFRGNTFS.exe as its main executable for crying out loud. While it has some interesting features, regular biweekly defragmenting should do just about the same. Thanks for the tip though

It's possible that defrag errors are caused by faulty, incompatible or overheated RAM. Please run Memtest86. http://www.memtest86.com

Impossible. There is a heatsink on RAM, and a 9-inch fan blowing air at full speed on ALL of the components (CPU temp's do not exceed 32 C, usually about 40 with closed case). This RAM stick was working for over a year, and there is no sign of it being either incompatible or faulty otherwise. The problem was a file system error that happened when power cord was jerked out of the socked by an accident. Disk checking solved the problem.