System Restore doesn't work: "rstrui.exe - application error"

[highstream]

System Restore doesn't work: "rstrui.exe - application error"

My Win 7x64 desktop was off for several days, with the console unplugged. Upon first start up today, I was prompted to update the AMD driver to Catalyist 12.10, which I did. It seemed to have an effect on another app that I wanted to reverse, so I ran System Restore to right before the computer was last shut down. It returned an error message, and again after a normal reboot: It read that System Restore didn't complete running. "The data is invalid (0x8007000D)." Running System Restore to later time points got the same result.

Later, I tried a cold boot into System Repair, F8 (nothing found). The System Restore error message now was as follows:

"rstrui.exe - Application error
The instruction at 0xfb30584d referenced memory at
0x00000008. The memory could not be read."

I did a google search on rstrui.exe error, but didn't find a lot and so far none of it has worked. The last system image backup before today was two weeks ago, so that's not a welcome option. Any ideas what the problem might be and how to get Sys Restore going again? Thanks,

 

[marsmimar]

By chance, do you have Agnitum Outpost firewall on your machine? Other forum threads indicate this could cause problems for system restore. The recommended solution was to disable a function called Self Protection.

You could also see if there are any damaged or corrupt system files by running a system file checker scan from and elevated command prompt (option two.) If problems are found run the scan 3 times and reboot your computer after each scan.

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

 

[highstream]

The answer to Agnitum is no, and I didn't find any problems running scannow.

Update: I decided to restore the last drive image and that seems to have solved the Sys Restore issue; i.e., I just set a restore point and then restored to it successfully. One strange thing was that the time in the file was 1:35pm (correct), while the time showing for it on the Windows repair module (F8) was 11:35am. System clock was correct, so not sure where that came from. But it did work well enough.

 

[marsmimar]

Glad to hear you got it sorted out. Another testimonial to the benefit of making system images. Thanks for posting back.

 

[Kaktussoft]

The answer to Agnitum is no, and I didn't find any problems running scannow.

Update: I decided to restore the last drive image and that seems to have solved the Sys Restore issue; i.e., I just set a restore point and then restored to it successfully. One strange thing was that the time in the file was 1:35pm (correct), while the time showing for it on the Windows repair module (F8) was 11:35am. System clock was correct, so not sure where that came from. But it did work well enough.

Time was correct .. exactly 2 hours difference. F8 recovery uses mini win7 that doesn't know your timezone!