Spinrite 6.1 Rc5.05 500gb HDD Attempt to execute illegal opcode

  • Release Candidate 6
    Guest:
    We are at a “proposed final” true release candidate with nothing known remaining to be changed or fixed. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
    /Steve.
  • 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!

    /Steve.

Noswal

New member
Jan 1, 2024
3
1
Hi, This happened, it is my D: drive, it is admittedly old and has miscellaneous data on it. It was about halfway through first row of dots. I was scrolling through the screens and error occurred.

op code.jpg
20240101_155036.jpg
20240101_155040.jpg
 
@Noswal : THANK YOU for the report!

I'm glad that you provided the extra detail that this occurred when you were scrolling through the screens. That gives me a good clue about where to look for the trouble... and maybe the opportunity to recreate it. I've opened an “Issue” for this over in GRC's GitLab so I will pursue it! Thanks again!
 
@Noswal: I just found and fixed a bug I introduced (along with a new feature) back with RC4. The new feature added logging of the number of over-temperature events that occurred on a drive between other log entries while SpinRite is running. That bug messed up SpinRite's screen display code. So I'm wondering whether that drive might have experienced an over temperature event while you were running it? That event would queue up a pending log entry that definitely would mess up SpinRite's code. If you don't recall ever seeing that I'll setup an automatic screen switching test to see whether I can make SpinRite misbehave. But, for what it's worth, we haven't seen in instance of a crash like you've reported before... and the over-temp event would definitely have been a likely cause. Thanks!
 
Hi, I ran SpinRrite again on that drive yesterday, without viewing the other screens, found 3 errors at end of drive.
HWinfo64 records drive maximum at 43C, average 39C. Whatever it was on my drive that caused the error am very glad to have been able to contribute to SpinRite's development.
 
  • Like
Reactions: Steve