Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox only goes to Mozilla Crash Reporter -- even in Safe Mode

  • 5 replies
  • 1 has this problem
  • 12 views
  • Last reply by georgew1

more options

Good Morning,

Two days ago -- out of the blue -- Firefox suddenly had a completely blank screen and when I tried to re-start it, it would not come up but instead brought me to the crash box. I have uninstalled it three or four time and re-installed it with the latest Windows download. (I'm running Win10.) I deleted it from the Registry, deleted the folders on the computer, ran disk cleanup, etc., all to no avail -- same crash box even in Safe mode.

Latest Crash ID: Crash ID: bp-5ce177fa-6bb4-4af3-b84c-dc97f0200827

Here's the copy of the latest info from the crash box:


AdapterDeviceID: 0x1382 AdapterDriverVersion: 26.21.14.3107 AdapterSubsysID: 6893103c AdapterVendorID: 0x10de Add-ons: doh-rollout%40mozilla.org:2.0.0,formautofill%40mozilla.org:1.0,screenshots%40mozilla.org:39.0.0,webcompat%40mozilla.org:13.0.1 AppInitDLLs: %ProgramFiles% (x86)\KeyCryptSDK\KeyCrypt64(7).dll BIOS_Manufacturer: AMI BreakpadReserveAddress: 2937223446528 BreakpadReserveSize: 83886080 BuildID: 20200818235255 CPUMicrocodeVersion: 0x42e CrashTime: 1598541540 DOMIPCEnabled: 1 EMCheckCompatibility: true Email: georgew@frontier.com FramePoisonBase: 9223372036600889344 FramePoisonSize: 65536 GraphicsSanityTest: 1 InstallTime: 1598470923 MemoryErrorCorrection: None ModuleSignatureInfo: {"Mozilla Corporation":["nss3.dll"]} Notes:

ProductID: {ec8030f7-c20a-464f-9b0e-13a3a9e97384} ProductName: Firefox ReleaseChannel: release SafeMode: 0 SecondsSinceLastCrash: 3337 StartupCrash: 1 StartupTime: 1598541538 ThreadIdNameMapping: 23516:"Gecko_IOThread",16580:"Timer",12884:"Link Monitor #1",23084:"Socket Thread",24360:"Permission",5176:"BackgroundThreadPool #1",22876:"JS Watchdog",13052:"JS Helper",19596:"JS Helper",21124:"JS Helper",22412:"JS Helper",3112:"JS Helper",5908:"JS Helper",9092:"JS Helper",25468:"JS Helper",24244:"Cache2 I/O",15592:"Cookie",12588:"StreamTrans #1",18808:"DOM Worker",780:"IPDL Background",9308:"Untrusted Modules",3420:"StreamTrans #2",15588:"StreamTrans #3",21096:"StreamTrans #4",25480:"Worker Launcher", Throttleable: 1 URL: UptimeTS: 20.91965 Vendor: Mozilla Version: 80.0 Winsock_LSP: Hyper-V RAW : 2 : 34 : 1 : 1 : 0x20026 : 0x8 : %SystemRoot%\system32\mswsock.dll :  : 1234191b-4bf7-4ca7-86e0-dfd7c32b5445

AF_UNIX : 2 : 1 : 1 : 0 : 0x20026 : 0x8 : %SystemRoot%\system32\mswsock.dll :  : a00943d9-9c2e-4633-9b59-0057a3160994 
MSAFD Tcpip [TCP/IP] : 2 : 2 : 1 : 6 : 0x20066 : 0x8 : %SystemRoot%\system32\mswsock.dll :  : e70f1aa0-ab8b-11cf-8ca3-00805f48a192 
MSAFD Tcpip [UDP/IP] : 2 : 2 : 2 : 17 : 0x20609 : 0x8 : %SystemRoot%\system32\mswsock.dll :  : e70f1aa0-ab8b-11cf-8ca3-00805f48a192 
MSAFD Tcpip [RAW/IP] : 2 : 2 : 3 : 0 : 0x20609 : 0xc : %SystemRoot%\system32\mswsock.dll :  : e70f1aa0-ab8b-11cf-8ca3-00805f48a192 
MSAFD Tcpip [TCP/IPv6] : 2 : 23 : 1 : 6 : 0x20066 : 0x8 : %SystemRoot%\system32\mswsock.dll :  : f9eab0c0-26d4-11d0-bbbf-00aa006c34e4 
MSAFD Tcpip [UDP/IPv6] : 2 : 23 : 2 : 17 : 0x20609 : 0x8 : %SystemRoot%\system32\mswsock.dll :  : f9eab0c0-26d4-11d0-bbbf-00aa006c34e4 
MSAFD Tcpip [RAW/IPv6] : 2 : 23 : 3 : 0 : 0x20609 : 0xc : %SystemRoot%\system32\mswsock.dll :  : f9eab0c0-26d4-11d0-bbbf-00aa006c34e4 
RSVP TCPv6 Service Provider : 2 : 23 : 1 : 6 : 0x22066 : 0x8 : %SystemRoot%\system32\mswsock.dll :  : 9d60a9e0-337a-11d0-bd88-0000c082e69a 
RSVP TCP Service Provider : 2 : 2 : 1 : 6 : 0x22066 : 0x8 : %SystemRoot%\system32\mswsock.dll :  : 9d60a9e0-337a-11d0-bd88-0000c082e69a 
RSVP UDPv6 Service Provider : 2 : 23 : 2 : 17 : 0x22609 : 0x8 : %SystemRoot%\system32\mswsock.dll :  : 9d60a9e0-337a-11d0-bd88-0000c082e69a 
RSVP UDP Service Provider : 2 : 2 : 2 : 17 : 0x22609 : 0x8 : %SystemRoot%\system32\mswsock.dll :  : 9d60a9e0-337a-11d0-bd88-0000c082e69a 
MSAFD L2CAP [Bluetooth] : 2 : 32 : 1 : 256 : 0x20006 : 0x8 : %SystemRoot%\system32\mswsock.dll :  : 9fc48064-7298-43e4-b7bd-181f2089792a 
MSAFD RfComm [Bluetooth] : 2 : 32 : 1 : 3 : 0x20026 : 0x8 : %SystemRoot%\system32\mswsock.dll :  : 9fc48064-7298-43e4-b7bd-181f2089792a

This report also contains technical information about the state of the application when it crashed.


Any ideas? I really much prefer Firefox -- but . . . it has to work to use it!

My thanks,

George Wilkinson

Chosen solution

The KeyCrypt64.dll file seems to be part of Zemana AntiLogger Free that inject this file in Firefox via the Windows Registry

  • AppInitDLLs : %ProgramFiles% (x86)\KeyCryptSDK\KeyCrypt64(7).dll
Read this answer in context 👍 1

All Replies (5)

more options

Hi,

for me it looks like a conflict between Firefox and MalwareBytes or KeyCrypt/Antilogger.

Helpful?

more options

I had not thought of that -- but the problem with that hypothesis is that I have been using Firefox for years with MalwareBytes and all the other software on my computer, so I don't THINK that's it. That said, what KeyCrypt/Antilogger are you thinking of? I have had MalwareBytes on the computer, Perfect Guard, ESET Anti-Virus, and Dashlane (password manager) -- all of which have been on the computer for a long time, along with Acronis True Image (which I updated shortly before the Firefox problem). Acronis may be a problem here because it has just added features that address Ransmware attacks, Illicit Cryptomining, and more. I will see if I can disable some of those extra and new features to see if that makes a difference.

Thank you for your thoughts!

George W

Helpful?

more options

Update MalwareBytes. If the problem continues, disable it.

Helpful?

more options

Chosen Solution

The KeyCrypt64.dll file seems to be part of Zemana AntiLogger Free that inject this file in Firefox via the Windows Registry

  • AppInitDLLs : %ProgramFiles% (x86)\KeyCryptSDK\KeyCrypt64(7).dll

Helpful?

more options

It turned out to be the KeyCryptSDK\KeyCrypt64(7).dll. I got rid of the Registry Key and the file (saving them in case it turned out not to be correct) after I checked to see what I could find out about that file.

When I re-started Firefox, it came up correctly.

The interesting thing is that the file folder date is back in 2017 -- so I cannot account for the sudden failure of Firefox to load with KeyCrypt64 as the sole -- sudden and recent -- cause of the problem. Still, if it works now, that's a good start.

At any rate, my thanks for the tip. It's made it possible for me to restore Firefox to working status.  :-)

George W.

Helpful?

Ask a question

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.