Main Forum > Tweaking.com Support & Help
Registry backup crashes Win10, auto mode. MSVBVM60.DLL bug?
pol098:
Re: Tweaking Registry Backup crashing, MSVBVM60.DLL faults
I'm repeating something I posted in an existing thread last month.
http://www.tweaking.com/forums/index.php/topic,4281.msg32230.html#msg32230 ,
just in case it got missed there (although I had some responses).
I've been having a problem that others have reported (search the forum for MSVBVM60) with Registry Backup. I had been using ERUNT, successfully, under Win 7 (it didn't back up the Components hive, but I was OK without it), but it didn't behave well under Win 10 so I installed RB. Win 10/64, up-to-date as of now, current 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.
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. It doesn't seem to be a timing issue, with the VSS service not being ready at login time: RegisrtyBackup be default sets up Task Scheduler to delay 5' after login. I don't know if Microsoft provide debugging maps and so on to pin down the MSVBVM60.DLL error.
My machine is a modern laptop sold as suitable for games, has 8GB of RAM and a 4-core 2.5GHz Intel i7 CPU, though using Intel 4600 on-chip graphics instead of a high-performance card, and the backup works perfectly if started manually, so I don't think performance is an issue.
This may well be a program problem that needs addressing; I'm not the only one to report this issue (see
http://www.tweaking.com/forums/index.php?topic=4033.0 )
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.
ADDED LATER: there are many reports of problems and crashes with MSVBVM60.DLL (plus a lot of rubbish sites found by Google). One suggested action that was reported to work for some, but not all, people in 2010 (pre-Win10) was to use an earlier MSVBVM60.DLL from WinXP. I haven't yet followed this up. All the versions of this file that I've found, back to Win98, seem to be about the same size (rounding to 1.32MB), so maybe it hasn't been changed much.
I can't comment on the Registry Backup program and haven't yet tried to restore a backup; if it ultimately works as well as ERUNT did under Win7 I'll be happy. A suggestion I'd make is an option to use "20160510" (or 160510) in file/directory names instead of "10May16", as this form sorts alphanumerically in chronological order. I set ERUNT up to iuse this (not the default), and it's helpful.
Best wishes, pol098
pol098:
Following up to my previous post (nothing new, just unsuccessful debugging), I've checked all files associated with the MSVBVM60 (Microsoft Visual Basic Virtual Machine 6.0). My up-to-date Win10/64 machine had six OCX files (from about 2004) that had been superseded by 2010 versions: comct232.ocx, comctl32.ocx, comdlg32.ocx, mscomctl.ocx, MSFLXGRD.ocx, tabctl32.ocx (the Win10 update doesn't touch these files). The old files were in c:\Windows\SysWOW64\; I overwrote them with the new ones, and also copied the new ones them into the program directory. The VM6 update files, while including several DLLs and other OCXs, didn't have newer versions of any files existing on the Win7/64 system. No change: program still fails when run automatically at logon, still succeeds when invoked manually. The backup directory is owned by Administrator; both Administrators and SYSTEM have full access (unchanged). This is just a no-progress report. Best wishes
Julian:
Huh im gonna test this on my windows 10 vm and see if I can duplicate this.
pol098:
Following up with a bit more (negative) information: additional to everything else, I placed MSVBVM60.DLL version 6.0.98.32 (the latest I could find, 1,426,944 bytes, modified 03 April 2011, 02:26:10) in the c:\Program Files (x86)\Tweaking.com\Registry Backup\ directory. It failed in the same way as before in automatic mode, and succeeded as before invoked manually. the event log entry confirmed that the error occurred in the DLL in the program file, not the original, lower-numbered one that came with Win10. Apart from systematically going through other versions of MSVBVM60.DLL (there have been suggestions that some versions have this sort of bug), I'm out of ideas.
Event log is consistent with the one detailed in a previous post; same Exception code: 0xc0000005 (access violation), location a bit later. Googling <Exception code: 0xc0000005 MSVBVM60.DLL> finds lots of hits.
The machine in general works flawlessly. sfc finds nothing.
Similar issue in Windows Repair:
http://www.tweaking.com/forums/index.php/topic,1619.0/nowap.html
Additional information, report.wer from latest occurrence (today):
Version=1
EventType=APPCRASH
EventTime=131076297106985646
ReportType=2
Consent=1
UploadTime=131076297108548276
ReportIdentifier=dd05f06e-1925-11e6-be0a-80fa5b10fd00
IntegratorReportIdentifier=9bdd3438-a794-4110-972b-06e380034fe5
WOW64=1
NsAppName=TweakingRegistryBackup.exe
Response.BucketId=fa8fce85721c9b478156bc32db31e42b
Response.BucketTable=1
Response.LegacyBucketId=108064292809
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=TweakingRegistryBackup.exe
Sig[1].Name=Application Version
Sig[1].Value=3.4.0.1
Sig[2].Name=Application Timestamp
Sig[2].Value=56f4a2b2
Sig[3].Name=Fault Module Name
Sig[3].Value=MSVBVM60.DLL
Sig[4].Name=Fault Module Version
Sig[4].Value=6.0.98.32
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=4eb1c425
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=000e600f
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.10586.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=2057
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=bfff
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=bfff67c04b3b425f80e6df640b8c2926
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=2944
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=29445af5e8fefb6667ccbdbe9dc6b028
UI[2]=C:\Program Files (x86)\Tweaking.com\Registry Backup\TweakingRegistryBackup.exe
UI[5]=Check online for a solution (recommended)
UI[6]=Check for a solution later (recommended)
UI[7]=Close
UI[8]=Tweaking.com - Registry Backup stopped working and was closed
UI[9]=A problem caused the application to stop working correctly. Windows will notify you if a solution is available.
UI[10]=&Close
LoadedModule[0]=C:\Program Files (x86)\Tweaking.com\Registry Backup\TweakingRegistryBackup.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\SYSTEM32\KERNEL32.DLL
LoadedModule[3]=C:\WINDOWS\SYSTEM32\KERNELBASE.dll
LoadedModule[4]=C:\Program Files (x86)\Tweaking.com\Registry Backup\MSVBVM60.DLL
LoadedModule[5]=C:\WINDOWS\SYSTEM32\USER32.dll
LoadedModule[6]=C:\WINDOWS\SYSTEM32\GDI32.dll
LoadedModule[7]=C:\WINDOWS\SYSTEM32\ADVAPI32.dll
LoadedModule[8]=C:\WINDOWS\SYSTEM32\msvcrt.dll
LoadedModule[9]=C:\WINDOWS\SYSTEM32\sechost.dll
LoadedModule[10]=C:\WINDOWS\SYSTEM32\RPCRT4.dll
LoadedModule[11]=C:\WINDOWS\SYSTEM32\SspiCli.dll
LoadedModule[12]=C:\WINDOWS\SYSTEM32\CRYPTBASE.dll
LoadedModule[13]=C:\WINDOWS\SYSTEM32\bcryptPrimitives.dll
LoadedModule[14]=C:\WINDOWS\SYSTEM32\ole32.dll
LoadedModule[15]=C:\WINDOWS\SYSTEM32\combase.dll
LoadedModule[16]=C:\WINDOWS\SYSTEM32\OLEAUT32.dll
LoadedModule[17]=C:\WINDOWS\SYSTEM32\kernel.appcore.dll
LoadedModule[18]=C:\WINDOWS\SYSTEM32\SXS.DLL
LoadedModule[19]=C:\WINDOWS\SYSTEM32\clbcatq.dll
LoadedModule[20]=C:\WINDOWS\SYSTEM32\coml2.dll
LoadedModule[21]=C:\Program Files (x86)\Tweaking.com\Registry Backup\Codejock.Controls.Unicode.v17.1.0.ocx
LoadedModule[22]=C:\WINDOWS\SYSTEM32\SHELL32.dll
LoadedModule[23]=C:\WINDOWS\SYSTEM32\MFC42u.DLL
LoadedModule[24]=C:\WINDOWS\SYSTEM32\cfgmgr32.dll
LoadedModule[25]=C:\WINDOWS\SYSTEM32\windows.storage.dll
LoadedModule[26]=C:\WINDOWS\SYSTEM32\shlwapi.dll
LoadedModule[27]=C:\WINDOWS\SYSTEM32\shcore.dll
LoadedModule[28]=C:\WINDOWS\SYSTEM32\powrprof.dll
LoadedModule[29]=C:\WINDOWS\SYSTEM32\profapi.dll
LoadedModule[30]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.10586.0_none_811bc0006c44242b\COMCTL32.dll
LoadedModule[31]=C:\WINDOWS\SYSTEM32\OLEPRO32.DLL
LoadedModule[32]=C:\WINDOWS\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.10586.20_none_22adb5eaa762c7fa\gdiplus.dll
LoadedModule[33]=C:\WINDOWS\SYSTEM32\ODBC32.dll
LoadedModule[34]=C:\WINDOWS\SYSTEM32\DPAPI.dll
LoadedModule[35]=C:\WINDOWS\SYSTEM32\UXTHEME.DLL
LoadedModule[36]=C:\Program Files (x86)\Tweaking.com\Registry Backup\TweakingImgCtl.ocx
LoadedModule[37]=C:\WINDOWS\SYSTEM32\WindowsCodecs.dll
LoadedModule[38]=C:\WINDOWS\system32\dataexchange.dll
LoadedModule[39]=C:\WINDOWS\system32\dcomp.dll
LoadedModule[40]=C:\WINDOWS\system32\d3d11.dll
LoadedModule[41]=C:\WINDOWS\system32\dxgi.dll
LoadedModule[42]=C:\WINDOWS\system32\twinapi.appcore.dll
LoadedModule[43]=C:\WINDOWS\system32\bcrypt.dll
LoadedModule[44]=C:\WINDOWS\SYSTEM32\DWrite.dll
LoadedModule[45]=C:\Program Files (x86)\Tweaking.com\Registry Backup\Tweaking_Tabsv2.ocx
LoadedModule[46]=C:\Program Files (x86)\Tweaking.com\Registry Backup\SSubTmr6.dll
LoadedModule[47]=C:\Program Files (x86)\Tweaking.com\Registry Backup\MSINET.OCX
LoadedModule[48]=C:\WINDOWS\SYSTEM32\WININET.dll
LoadedModule[49]=C:\WINDOWS\SYSTEM32\msimg32.dll
LoadedModule[50]=C:\Program Files (x86)\Tweaking.com\Registry Backup\pcwintech_tasksch.dll
LoadedModule[51]=C:\WINDOWS\System32\mstask.dll
LoadedModule[52]=C:\Windows\SYSTEM32\scrrun.dll
LoadedModule[53]=C:\Windows\SYSTEM32\VERSION.dll
LoadedModule[54]=C:\WINDOWS\System32\msxml3.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Tweaking.com - Registry Backup
AppPath=C:\Program Files (x86)\Tweaking.com\Registry Backup\TweakingRegistryBackup.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=01CD94E81CDEFEC0C6D74F5AA290B734
Best wishes, pol098
pol098:
Update of non-progress: from reports I found on the Web I suspected an error in some versions of MSVBVM60.DLL. This doesn't seem to be the case; I've placed versions 6.0.97.82, 6.0.98.15, 6.0.98.21, 6.0.98.31, and 6.0.98.32 (date ranging from 2004 to 2012) in the RegistryBackup program directory. In all cases the automatic backup fails with the same exception (and the event log confirms that the failing version is the one I'm testing, it's not a case of finding the wrong DLL); and the manual backup succeeds. HTH
Clarification added 19My16: I added one of the DLL versions listed to the program directory and rebooted to see if the backup succeeded. I repeated this with each of the others. There was (obviously, they have the same name) only one "c:\Program Files (x86)\Tweaking.com\Registry Backup\msvbvm60.dll" at any one time.
Navigation
[0] Message Index
[#] Next page
Go to full version