"Eraser has stopped working" in Win 7 64bit

D

DerrikMo

New Member
I just installed Eraser 6.0.6.1376, the latest stable version. I am running Win 7, Home Premium, 64bit. I cannot get it to run. As soon as it attempts to start I get the following error message "Eraser has stopped working". Please help!!

The Problem Details as reported by Windows 7are as follows:

Description:
Stopped working

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: eraser.exe
Problem Signature 02: 6.0.6.1376
Problem Signature 03: 4b26dc33
Problem Signature 04: System.Windows.Forms
Problem Signature 05: 2.0.0.0
Problem Signature 06: 4a275ebd
Problem Signature 07: 16ce
Problem Signature 08: 21
Problem Signature 09: System.InvalidOperationException
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid= ... cid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
 
Yes, I'm trying to debug this. The problem is that it affects only a small proportion of users and it happens that I can't replicate the problem on my development computer.
 
Has any progress been made on this investigation? I am running Win7 Ultimate x64, and am unable to get Eraser to load. I have tried installing to "Program Files" and "Programs Files (x86)". Either install generates the below on load...

Version=1
EventType=CLR20r3
EventTime=129061642978506106
ReportType=2
Consent=1
ReportIdentifier=a586defa-f0d4-11de-830b-90e6ba3d2625
Response.type=4
Sig[0].Name=Problem Signature 01
Sig[0].Value=eraser.exe
Sig[1].Name=Problem Signature 02
Sig[1].Value=6.0.6.1376
Sig[2].Name=Problem Signature 03
Sig[2].Value=4b26dc33
Sig[3].Name=Problem Signature 04
Sig[3].Value=System.Windows.Forms
Sig[4].Name=Problem Signature 05
Sig[4].Value=2.0.0.0
Sig[5].Name=Problem Signature 06
Sig[5].Value=4a275ebd
Sig[6].Name=Problem Signature 07
Sig[6].Value=16ce
Sig[7].Name=Problem Signature 08
Sig[7].Value=21
Sig[8].Name=Problem Signature 09
Sig[8].Value=System.InvalidOperationException
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7600.2.0.0.256.1
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=C:\Program Files\Eraser\Eraser.exe
UI[3]=Eraser has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files\Eraser\Eraser.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\SYSTEM32\MSCOREE.DLL
LoadedModule[3]=C:\Windows\system32\KERNEL32.dll
LoadedModule[4]=C:\Windows\system32\KERNELBASE.dll
LoadedModule[5]=C:\Windows\system32\ADVAPI32.dll
LoadedModule[6]=C:\Windows\system32\msvcrt.dll
LoadedModule[7]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[8]=C:\Windows\system32\RPCRT4.dll
LoadedModule[9]=C:\Windows\system32\SHLWAPI.dll
LoadedModule[10]=C:\Windows\system32\GDI32.dll
LoadedModule[11]=C:\Windows\system32\USER32.dll
LoadedModule[12]=C:\Windows\system32\LPK.dll
LoadedModule[13]=C:\Windows\system32\USP10.dll
LoadedModule[14]=C:\Windows\system32\IMM32.DLL
LoadedModule[15]=C:\Windows\system32\MSCTF.dll
LoadedModule[16]=C:\Windows\system32\guard64.dll
LoadedModule[17]=C:\Windows\system32\fltlib.dll
LoadedModule[18]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorwks.dll
LoadedModule[19]=C:\Windows\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4927_none_88dce9872fb18caf\MSVCR80.dll
LoadedModule[20]=C:\Windows\system32\shell32.dll
LoadedModule[21]=C:\Windows\system32\ole32.dll
LoadedModule[22]=C:\Windows\system32\profapi.dll
LoadedModule[23]=C:\Windows\assembly\NativeImages_v2.0.50727_64\mscorlib\9a017aa8d51322f18a40f414fa35872d\mscorlib.ni.dll
LoadedModule[24]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorsec.dll
LoadedModule[25]=C:\Windows\system32\WINTRUST.dll
LoadedModule[26]=C:\Windows\system32\CRYPT32.dll
LoadedModule[27]=C:\Windows\system32\MSASN1.dll
LoadedModule[28]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7600.16385_none_a44af8ec57f961cf\COMCTL32.dll
LoadedModule[29]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[30]=C:\Windows\system32\rsaenh.dll
LoadedModule[31]=C:\Windows\system32\CRYPTBASE.dll
LoadedModule[32]=C:\Windows\system32\imagehlp.dll
LoadedModule[33]=C:\Windows\system32\ncrypt.dll
LoadedModule[34]=C:\Windows\system32\bcrypt.dll
LoadedModule[35]=C:\Windows\system32\bcryptprimitives.dll
LoadedModule[36]=C:\Windows\system32\USERENV.dll
LoadedModule[37]=C:\Windows\system32\GPAPI.dll
LoadedModule[38]=C:\Windows\system32\cryptnet.dll
LoadedModule[39]=C:\Windows\system32\WLDAP32.dll
LoadedModule[40]=C:\Windows\system32\SensApi.dll
LoadedModule[41]=C:\Windows\system32\Cabinet.dll
LoadedModule[42]=C:\Windows\system32\DEVRTL.dll
LoadedModule[43]=C:\Windows\system32\uxtheme.dll
LoadedModule[44]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorjit.dll
LoadedModule[45]=C:\Windows\system32\shfolder.dll
LoadedModule[46]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[47]=C:\Program Files\Eraser\Eraser.Manager.dll
LoadedModule[48]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System\247913fa7ae6fcf04ea33d28d24ab611\System.ni.dll
LoadedModule[49]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Drawing\10f1e1ffca16e550af8a8fd7685a48ef\System.Drawing.ni.dll
LoadedModule[50]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Windows.Forms\2e0044fa7cabadce65fa8964fe2c90dd\System.Windows.Forms.ni.dll
LoadedModule[51]=C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.VisualBas#\1ec65ef1b8265780b3a6e7f1855db885\Microsoft.VisualBasic.ni.dll
LoadedModule[52]=C:\Program Files\Eraser\Eraser.Util.dll
LoadedModule[53]=C:\Windows\system32\SspiCli.dll
LoadedModule[54]=C:\Windows\system32\Netapi32.dll
LoadedModule[55]=C:\Windows\system32\netutils.dll
LoadedModule[56]=C:\Windows\system32\srvcli.dll
LoadedModule[57]=C:\Windows\system32\wkscli.dll
LoadedModule[58]=C:\Windows\system32\VERSION.dll
LoadedModule[59]=C:\Program Files\Eraser\Plugins\Eraser.DefaultPlugins.dll
LoadedModule[60]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Core\27ed9d7013e71f31cacdf8cc438386b6\System.Core.ni.dll
LoadedModule[61]=C:\Program Files\Eraser\en\Eraser.resources.dll
LoadedModule[62]=C:\Windows\system32\dwmapi.dll
LoadedModule[63]=C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7600.16385_none_2b4f45e87195fcc4\gdiplus.dll
LoadedModule[64]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[65]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16385_none_fa645303170382f6\comctl32.dll
LoadedModule[66]=C:\Program Files\Eraser\BevelLine.dll
LoadedModule[67]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Xml\1fb1b14199d6aec70df1a0626a3ae5f2\System.Xml.ni.dll
LoadedModule[68]=C:\Program Files\Eraser\en\Eraser.Manager.resources.dll
LoadedModule[69]=C:\Windows\system32\oleaut32.dll
LoadedModule[70]=C:\Windows\system32\apphelp.dll
FriendlyEventName=Stopped working
ConsentKey=CLR20r3
AppName=Eraser
AppPath=C:\Program Files\Eraser\Eraser.exe
ReportDescription=Stopped working
 
I've got a debug build a few people are getting, but that's not ready for release yet.
 
Hi,

I am not sure if I can add to this any or not?

Using version 6.0.10.2620. I clicked to check if there were any updates, it said there was. I clicked to update it and it turns out the version I am using is the same as the "update". The computer (Win x64 Home) then had the update process lock up. I had to click cancel.

Now every time I start the computer, Eraser seems to load fine, even a right-context menu. I set all the permissions to allow all control in desperation, but still what happens is that you get one go at it. Eraser will work once perfectly well, but throw up the "Eraser Has Stopped Working" warning and says it is checking for solutions. It does not find any. Whether I let it finish checking, or click on cancel, there then appears two Eraser symbols on the bottom of the screen, sometimes one will disappear, sometimes not. If you try to use Eraser again through the right-click menu, the Eraser symbol(s) will disappear and the file to be deleted is not erased.

I tried uninstalling it, restarting the computer and it made no difference at all to the problem.

I tried uninstalling it again, running RegEdit to manually remove any remaining traces and restarted the computer, but that made no difference at all to the computer.

I tried rolling back the computer to the day before I clicked to manually check for updates, but still the problem is exactly the same.

I have even run CCleaner and it's registry cleaner, but again no difference to the problem.

What on Earth could Eraser be doing that persists after a restore? Could it possibly be something that was installed or done on earlier versions of Eraser, that gets left behind when the program is updated? So that the updates work perfectly until you click on update and it crashes as the new update is the same as the current version? Thereafter the problem persists as the required "setting" or whatever has been deleted?

Or could it possibly be some sort of "update" is left behind after the initial crash and it tries to run every time Eraser is run, so it crashes it again?

It is just a guess based on my observations of the peculiar persistence of the problem even after a restore.

Keep restarting the computer to get just one use out of Eraser is getting seriously annoying, please is there any hope?
 
You must log in or register to reply here.
Back
Top