Gravity Crashes - Access Past EOF

  • SpinRite v6.1 is Released!
    That's right. SpinRite v6.1 is finished and released. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in:

    This forum does not automatically send notices of new content. So if, for example, you would like to be notified by mail when Steve posts an update to his blog (or of any other specific activity anywhere else), you need to tell the system what to “Watch” for you. Please checkout the “Tips & Tricks” page for details about that... and other tips!

  • Announcing “BootAble” – GRC's New Boot-Testing Freeware
    Please see the BootAble page at GRC for the whole story.
  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)


New member
Oct 30, 2023
The exact error msg from Gravity is :

"Attempted to access an unnamed file past its end."

A 2nd msg had something about a "Tasker" thread.

Now Gravity crashes every time it's launched with the same errors msgs. I've had no problems for the last year.

It outputs a ...\AppData\Local\CrashDumps\gravity.exe.*.dmp on every crash but I don't know how to interpret it.

I tried renaming the ...\AppData\Roaming\Gravity\newsdb3.0\GRC\ g where I was trying to Reply to a post when it first crashed, but it still crashes.

How do I find out what file it's trying to read past the EOF?
I know this doesn't answer your question directly, but a while back I decided to ditch Gravity and settled for Xana News Reader instead. A decision I did not regret.
Now Gravity crashes every time it's launched with the same errors msgs. I've had no problems for the last year.
I've never seen this, nor have I seen it reported before. My guess is that Gravity's database of files was messed up somehow. You could abandon Gravity for some other newsreader, but I don't ever plan to. I've looked at all of the others and none of them suit me as well as Gravity. I can't diagnose the trouble. But you might try renaming the "GRC" directory to "GRC-OLD" then starting Gravity.