ACCESS_VIOLATION (the memory could not be read or written)

[MacNetron]

A  bit similar as the recent http://www.mydefrag.com/forum/index.php?topic=2924.0.

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.5
Date: 2009/11/03 12:37:30
Windows version: v5.1 build 2600 S
Commandline: C:\WINDOWS\system32\MYDEFR~1.SCR /s
Working Directory: C:\WINDOWS\system32
Userid: Marco
12:37:30 Starting the screensaver: C:\WINDOWS\system32\MyDefragScreenSaver.exe
12:37:31 Analyzing the commandline.
12:37:31   Commandline argument accepted, added 'OptimizeDaily.MyD' to the scripts.
12:37:31 Running script: Settings.MyD
12:37:31 Running script: OptimizeDaily.MyD
12:37:44 Bezig met disk C:
12:37:46     This is a FAT32 disk.
12:37:46     Please note that the Microsoft defragmentation API cannot move directories on FAT volumes.
I have crashed!
  Command line: "C:\WINDOWS\system32\MyDefragScreenSaver.exe" /s
  Context is not locked.
  Exception: ACCESS_VIOLATION (the memory could not be read or written)
  1. At line (unknown) in (unknown)
  2. At line (unknown) in (unknown)
  3. At line (unknown) in (unknown)
  4. At line (unknown) in (unknown)
  5. At line (unknown) in (unknown)
  6. At line (unknown) in (unknown)
  7. At line (unknown) in (unknown)
  8. At line (unknown) in (unknown)
  9. At line (unknown) in (unknown)
  10. At line (unknown) in (unknown)
  11. At line (unknown) in (unknown)
  12. At line (unknown) in (unknown)
  13. At line (unknown) in (unknown)
  14. At line (unknown) in (unknown)
  15. At line (unknown) in (unknown)
  16. At line (unknown) in (unknown)
  17. At line (unknown) in (unknown)
13:04:20   Klaar met disk C:
13:04:20   Exit with return code 1 so the wrapper will start the alternate screensaver.
13:04:20 Read key 'Control Panel\Screen Saver.MyDefrag\AlternateScreenSaver' from registry: 'C:\WINDOWS\system32\ssmypics.scr'
13:04:20 Running the alternate screensaver: C:\WINDOWS\system32\ssmypics.scr

Running Windows XP Home ed. SP3 NL. Drive C is FAT32.
Putting Debug(495) on to see if I can provide more info

[jeroen]

Putting Debug(495) on to see if I can provide more info

Ok, that would have been my question, yes.

[MacNetron]

Sorry for the delay, but it took me some time getting a time window for creating a full debug report on highest debug settings as it needed to run for almost 10 hours(!) in screensaver mode(!)...

Log file is available here.

About those 10 hours. Looking with Process Explorer, it looks like explorer.exe process is eating more cpu on higher debug settings than no debug at all. No real proof though as the defrag processes get killed on moving a mouse in screensaver mode.

I hope the logging is useful

[jeroen]

Thank you very much for making and posting the logfile, I appreciate it. No, I'm afraid it does not show me what is wrong. The logfile shows that the program was happily analyzing the disk (it was indeed very slow), and then all of a sudden, for no reason that I can see, the windows thread suddenly crashed. It makes no sense. At the moment I am preparing a new version that has some extra debugging code, and I am hoping the logfile will then show me what is happening.

[owen]

Hi jeroen, we have had a few of these occurring also, running v4.2.6 and I have been following this post.

I didnt see any point submitting logs at this stage and was waiting for your updated diag version. Do you have any eta on the next version? Thanks

[jeroen]

Version 4.2.6 is the new version. In case of a crash it will write a line in the debuglog directing you to download a special debug version: MyDefrag debug version