Jump to content

John Gray

Experienced Members
  • Posts

    43
  • Joined

  • Last visited

Posts posted by John Gray

  1. Windows 7 SP1 fully-patched, 64-bit.

    Disk is 2 TB, 30% full.

    Defrag takes place, apparently successfully, but on re-execution it crashes at 43%.

    CHKDSK has been run on the offending disk, but the Defraggler crash still occurs.

    Here's the brief crash info.

    Can I get you any more information?

     

    Problem signature:

    Problem Event Name: BEX64

    Application Name: Defraggler64.exe

    Application Version: 2.6.0.328

    Application Timestamp: 4e13ff88

    Fault Module Name: Defraggler64.exe

    Fault Module Version: 2.6.0.328

    Fault Module Timestamp: 4e13ff88

    Exception Offset: 00000000001c82c8

    Exception Code: c000000d

    Exception Data: 0000000000000000

    OS Version: 6.1.7601.2.1.0.256.48

    Locale ID: 2057

    Additional Information 1: c6e0

    Additional Information 2: c6e0e25c260d29f75ab13edbfaa32dea

    Additional Information 3: 4006

    Additional Information 4: 40061da3d83c2933fcd424e21ba4489f

  2. I'm surprised that nobody appears to have commented on the unusual and rapidly-changing chequer-board-type screen pattern which often takes place shortly before the end of fragmentation. This has happened over several recent versions of Defraggler, on XP SP3 and Win7 64-bit computers, at least. It usually lasts 5-10 seconds with the pattern changing, and occupying all of the "free space" area. Eventually it stops and the defragging finishes normally.

     

    Can I do anything to assist in debugging this?

     

    (Here's one 'frame' of the pattern...)

     

    post-25172-0-17932400-1307447151_thumb.png

  3. On the first run on a 280 GB disk with only 4% free space, Defraggler v2 beta crashed shortly after it put up the coloured disk map. On the second run it seems to be working.

     

    Is there any dump information that I can provide to assist?

     

    The only difference I can see with the new beta is that the squares in the disk map are pastel coloured!

  4. I set Defraggler to exclude certain files and folders and set a schedule. I noticed the scheduler invokes df.exe so I was just wondering if it uses the ini file.

    If you rename the INI file, try it, and rename the INI file back to its original name, you will have your answer oh so quickly!

  5. i have been using defraggler for a few years now.

    I have a few suggestions that, to me, would improve my experience with defraggler:

    - Auto shutdown when completed a defrag (for those overnight 'tune-ups')

    That's already there! Click on Settings at the top, then in the drop-down menu click on the final option "Shutdown after Defrag"... When finished it counts down from about 60 seconds before shutting the PC down.

  6. It's a memory leak... It doesn't affect your defrag times or stability. It's simply an issue caused by the number of drives listed.

    It's a bug.

    Well, my Defraggler memory usage has stayed fairly constant at 361,024 KB (give or take a MB or so) for about half an hour while defragging.

     

    Memory leaks cause the amount of memory used to increase with time, and (some of) the memory is not returned to the memory pool when the leaky program terminates. Is this what you observe?

  7. I use defraggler and it shows no files fragmented when it's finished. I restart the PC and I have like a 100 files fragmented? Is this software a hoax or is this a Windows issue. I have 32 bit Windows 7. Anybody????

    What do you think happens when a computer starts up? Yes, files get written! All over the hard disk. So some will inevitably be fragmented. That's the way it works...

  8. It wouldn't surprise me if any active program would try to use as much memory space as it needs, if nothing else is running. Surely that's the way Windows memory allocation/optimisation is supposed to work?

  9. I restarted an almost completely finished defrag (97%) to get some diagnostics, and left it overnight, but was amazed to find that it didn't finish for over 12 hours!

     

    The debug file is about 15 MB uncompressed, 1,1 MB zipped, and after the first 8/9 pages each line terminates with "Destination block is not free." I don't know if that has any significance...

     

    Is there an address to which I can send the debug zip file, please, so that it can be looked at? Thanks!

  10. I'm running an XP laptop and have an external hard drive that is connected to my network so that my wife and I can backup our files.

    That sounds a bit vague to me. Is the external hard drive connected to one of your PCs via a USB interface, and shared on that PC , so that the other PC can see it?

    Or are you talking about a NAS device?

  11. I run chkdsk /f every few months or so, I don't think there's anything wrong with this. Most of the time it will detect several problems that need to be corrected. Ounce of prevention, pound of cure . . .

    Much the same as most people, then, if they run it at any time when there are no obvious disk problems!

     

    The snag is that it can take a variable amount of time - but usually hours. The bigger your hard disk is, usually the longer it will take. But 15-20 years ago, under NT 3.5, we would wonder whether a CHKDSK we set off on a server's Storageworks drives on a Friday evening would finish before start of work on Monday morning! Nail-biting stuff...

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.