Main Forum > Tweaking.com Support & Help

Tweaking Registry Backup crashing

<< < (2/3) > >>

pol098:
I've been having a problem that others have reported (search for MSVBVM60) with Registry Backup. I had been using ERUNT, successfully, under Win 7, but it didn't behave well under Win 10 so I installed RB. Win 10/64, up-to-date as of now, RB 3.4.0.1. As it wasn't working I changed the VSS executable from automatic to vss_7_8_2008_2012_64.exe, same behaviour.
Another relevant post: http://www.tweaking.com/forums/index.php?topic=4033.0

I have set up RB to run as System on login of any user, saving to a non-standard location and not more than once per day. The VSS service was initially set to run manually, but I changed it to automatic. RB runs fine manually, but does not back up automatically. I looked at the event log and found Error, event ID 1000, details:

Faulting application name: TweakingRegistryBackup.exe, version: 3.4.0.1, time stamp: 0x56f4a2b2
Faulting module name: MSVBVM60.DLL, version: 6.0.98.15, time stamp: 0x49b01fc3
Exception code: 0xc0000005
Fault offset: 0x000c9ba6
Faulting process id: 0x2040
Faulting application start time: 0x01d19a3622cb4882
Faulting application path: C:\Program Files (x86)\Tweaking.com\Registry Backup\TweakingRegistryBackup.exe
Faulting module path: C:\WINDOWS\SYSTEM32\MSVBVM60.DLL
Report Id: 6b50db5c-33de-48da-9eb6-f3e412c3c5d8
Faulting package full name:
Faulting package-relative application ID:

MSVBVM60.DLL is a Visual Basic Virtual Machine. On running manually a shadow copy is created, with a progress indicator; the automatic invocation doesn't seem to have created a shadow copy. The only guess I can make is a timing issue, the VSS service not being ready at login time (as RB works when invoked manually after login), but it's only a guess. I don't know if Microsoft provide debugging maps and so on to pin down the MSVBVM60.DLL error.

I can't comment on the program; if it ultimately works as well as ERUNT did under Win7 I'll be happy. The only suggestion I'd make is an option to use "20160419" (or 160419) in file/directory names instead of "19Apr16", as this form sorts alphanumerically in chronological order.

Best wishes, pol098

Willy2:
- One thing regarding ERUNT. Windows 7 and newer have a registry hive called "Components". ERUNT doesn't backup that hive whereas Registry Backup does backup that hive.

pol098:
"... Windows 7 and newer have a registry hive called "Components" ..." Thanks, I hadn't realised; fortunately I never had any trouble.

By the way, following up to my posting of earlier today, Task Scheduler was set up to delay 5' after login, so the problem doesn't seem to be due to trying to back up before the system was ready.

Best wishes

Willy2:
- I know the 5 minute delay was added to Task Scheduler to avoid overburdening the system upon start up. Windows needs to do A LOT OF things upons start up. You Always can change that, of course.
- The crashing occurs because RB is designed to be as fast as possible. That trick works when one has a (very) fast graphics card. But the average user doesn't have such a fast graphics CPU. And then RB wants to move on before the graphics card has finished. Hence the crash.
- Perhaps Windows Vista has such a hive as well but I don't know. Never used Vista.
- The development of ERUNT was stopped before Windows 7 came to market. (As far as I know).
- The vast majority of users don't know of the existence of "Components".

pol098:

--- Quote ---The crashing occurs because RB is designed to be as fast as possible. That trick works when one has a (very) fast graphics card. But the average user doesn't have such a fast graphics CPU. And then RB wants to move on before the graphics card has finished. Hence the crash.
--- End quote ---
Thanks for that. I'm using a recent laptop machine (Clevo) with an Intel i7 CPU, using built-in rather than add-on graphics. I would describe this as a fast machine for anything except extreme game-playing. I would expect (and do find!) that most programs would run well on it. And why does RB run fine in manual mode, but not automatically 5' after boot? This may well be a program problem that needs addressing; I'm not the only one to report this issue (link in a previous post of mine). Does RB make any calls to the Visual Basic Virtual Machine DLL MSVBVM60.DLL in automatic mode that it doesn't make in manual mode? The Event Viewer error message gives a specific exception 0xc0000005 - an access violation - in that module, at 0x000c9ba6. Best wishes, pol098

Navigation

[0] Message Index

[#] Next page

[*] Previous page