[4.2.3] Crashed and weird problems?

[meepmeep]

I had used successfully jkdefrag for a long time and recently have switched to MyD, always running the fast algorithm and later the fast update script. A couple days ago I upgraded from one of the 4.1 to 4.2.3.

Since the old scheduled job no longer works but just brings up a script selection window, I took my time to read about the various choices and figured out the new scripts are called Weekly/Daily/Monthly.

I never used the slow optimization algorithm, so I decided to give Monthly a spin. Completed with no error, so I keep using my PC and eventually hibernate it as usual.

Today I turn it on and found Grub wasn't able to boot XP anymore. Please note I had not made any changes to grub, the partition table or anything else in a long time. Luckily I managed to fix the trouble and booted again into windows. I was quite worried the disk could be about to give up its soul so I ran a quick check with smartmontools which reassured me everything was OK.

Later MyD pops up again and this time I select the Daily script. MyD hangs and pleads me to post here the debuglog. The idea that the disk could be about to fail came to mind again and I ran a chkdsk. Which found some errors, so I schedule a check for the next reboot. Quite surprisingly chkdsk /F finds no error and fixes nothing.

So I log in and run chkdsk again and this is what I get:

Code:

C:\Program Files>chkdsk c:
The type of the file system is NTFS.
Volume label is XYZ.

WARNING!  F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
CHKDSK is recovering lost files.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
Correcting errors in the master file table's (MFT) BITMAP attribute.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.

  33551716 KB total disk space.
  24240044 KB in 166135 files.
     59236 KB in 14904 indexes.
         0 KB in bad sectors.
    775640 KB in use by the system.
     65536 KB occupied by the log file.
   8476796 KB available on disk.

      4096 bytes in each allocation unit.
   8387929 total allocation units on disk.
   2119199 allocation units available on disk.

This time the errors are different from the old ones. This is the debug log.

Code:

´╗┐# See the 'MyDefrag.log' file for information intended for endusers. This is the debug
# logfile. The contents is highly technical and not documented. See the 'Debug' setting
# or the '-d' commandline option to control the level of information in this file.
#
Version: MyDefrag v4.2.3
Date: 2009/10/20 20:00:00
Windows version: v5.1 build 2600 S
Commandline: "C:\Program Files\mydefrag\MyDefrag.exe" c: e:
Working Directory: C:\Program Files\mydefrag
Userid: jsparrow
InstallPath = C:\Program Files\MyDefrag\
20:00:00 Analyzing the commandline.
20:00:00   Commandline argument accepted, added 'c:' to the list of CommandlineVolumes.
20:00:00   Commandline argument accepted, added 'e:' to the list of CommandlineVolumes.
20:00:00 Running script: Settings.MyD
20:00:00 Showing the WhatToDo dialog.
20:07:37 Added 'C:' to the list of CommandlineVolumes.
20:07:37 Selected script = C:\Program Files\mydefrag\Scripts\OptimizeDaily.MyD
20:07:37 Running script: C:\Program Files\mydefrag\Scripts\OptimizeDaily.MyD
20:07:37 Processing disk C:
20:07:49   Loading list of unmovable files
20:08:44   Reclaiming the NTFS reserved area
20:08:44   Zone 1 of 5
20:08:44     SortBy
20:09:37     Vacating free area
20:09:37   Zone 2 of 5
20:09:37     Defragment
20:09:37     FastFill
20:10:15     Vacating free area
20:10:24   Zone 3 of 5
20:10:24     Analyzing the boot optimization file
20:10:29       1959 files selected.
20:10:29     Defragment
20:10:52     FastFill
20:11:21     Vacating free area
20:11:23   Zone 4 of 5
20:11:23     Looking for: $RECYCLE.BIN
20:11:23     Looking for: RECYCLED
20:11:24     Looking for: RECYCLER
20:11:24     Looking for: $*
20:11:24     Looking for: Downloaded Installations
20:11:24     Looking for: Ehome
20:11:25     Looking for: Fonts
20:11:25     Looking for: Help
20:11:25     Looking for: I386
20:11:25     Looking for: IME
20:11:26     Looking for: Installer
20:11:26     Looking for: ServicePackFiles
20:11:26     Looking for: SoftwareDistribution
20:11:26     Looking for: Speech
20:11:27     Looking for: Symbols
20:11:27     Looking for: ie?updates
20:11:27     Looking for: dllcache
20:11:27     Looking for: Installshield Installation Information
20:11:28     Looking for: System Volume Information
20:11:28     Looking for: windows.old
20:11:28     Looking for: *.7z
20:11:28     Looking for: *.arj
20:11:28     Looking for: *.avi
20:11:28     Looking for: *.bak
20:11:28     Looking for: *.bup
20:11:29     Looking for: *.bz2
20:11:29     Looking for: *.cab
20:11:29     Looking for: *.chm
20:11:29     Looking for: *.dvr-ms
20:11:29     Looking for: *.gz
20:11:29     Looking for: *.ifo
20:11:29     Looking for: *.iso
20:11:29     Looking for: *.log
20:11:29     Looking for: *.lzh
20:11:29     Looking for: *.mp3
20:11:30     Looking for: *.msi
20:11:30     Looking for: *.old
20:11:30     Looking for: *.pdf
20:11:30     Looking for: *.rar
20:11:30     Looking for: *.rpm
20:11:30     Looking for: *.tar
20:11:30     Looking for: *.wav
20:11:30     Looking for: *.wmv
20:11:30     Looking for: *.vob
20:11:31     Looking for: *.z
20:11:31     Looking for: *.zip
20:11:31     Defragment
20:37:09             Timeout 1 while waiting to get a read lock for: ShowItemInfo
20:38:09             Timeout 2 while waiting to get a read lock for: ShowItemInfo
20:39:09             Timeout 3 while waiting to get a read lock for: ShowItemInfo
20:40:09             Timeout 4 while waiting to get a read lock for: ShowItemInfo
20:41:09             Timeout 5 while waiting to get a read lock for: ShowItemInfo
20:42:09             Timeout 6 while waiting to get a read lock for: ShowItemInfo
20:43:09             Timeout 7 while waiting to get a read lock for: ShowItemInfo
20:44:09             Timeout 8 while waiting to get a read lock for: ShowItemInfo
20:45:09             Timeout 9 while waiting to get a read lock for: ShowItemInfo
20:46:09             Timeout 10 while waiting to get a read lock for: ShowItemInfo
20:47:09             Timeout 11 while waiting to get a read lock for: ShowItemInfo
20:48:09             Timeout 12 while waiting to get a read lock for: ShowItemInfo
20:49:09             Timeout 13 while waiting to get a read lock for: ShowItemInfo
20:50:09             Timeout 14 while waiting to get a read lock for: ShowItemInfo
20:50:09 Too many timeouts, the computer is too busy. Forcing a crash for debugging purposes.
I have crashed!
  Command line: "C:\Program Files\mydefrag\MyDefrag.exe" c: e:
  Current context locks:
    GetFragments
  Exception: ACCESS_VIOLATION (the memory could not be read or written)
  1. At line (unknown) in (unknown)
  2. At line (unknown) in (unknown)

[jeroen]

Thanks for posting the logfile, I appreciate it. Don't worry about your harddisk, it's a bug in MyDefrag. I have looked at the problem several times before but it makes no sense to me, the program should never lock up at that location. I am overlooking something....

[meepmeep]

You're welcome. So the problems with grub and the errors detected chkdsk had been caused by MyDefrag?

[jeroen]

So the problems with grub and the errors detected chkdsk had been caused by MyDefrag?

No. MyDefrag is totally safe and cannot damage your disk in any way. I was referring to the MyDefrag debuglog that you posted.

[meepmeep]

Then it'd be just a coincidence... quite weird though 

So while we wait for the bug to be hunted down and squished, what's the recommended version to go back to?

[jeroen]

So while we wait for the bug to be hunted down and squished, what's the recommended version to go back to?

The bug only happens occasionally. Just run again.

[TAC109]

A chkdsk on the c: drive while Windows is running will often show spurious errors. This is quite normal and occurs because chkdsk cannot complete properly unless it has exclusive access to the disk.

If you run chkdsk with the /f parameter (to fix any problems) you will get a message that this cannot be done now, and asking if you want to do this on the next reboot. As you have found, when you did this there were in reality no problems.