Firefox crashes
Firefox crashes on opening, but will open in Safe Mode (after a while). Crash report talks about related Bugs : 973138 VERIFIED FIXED startup crash in_fnNCDESTROY (mostly with MovieMode 48CA2AEFA22D.dll).
How do fix this problem and stop Firefox from crashing ?
I am not aware of having any installed program called Movie or MovieMode, only Windows Media Player. Your help would be much appreciated. John M
Wybrane rozwiązanie
the offending library on your pc which is triggering the crash is named "Websteroids.B324755F3F87.2.6.80.dll" - please run a full scan of your system with different security tools like the free version of malwarebytes, adwcleaner, microsoft safety scanner & kaspersky security scan.
Troubleshoot Firefox issues caused by malware
Przeczytaj tę odpowiedź w całym kontekście 👍 0Wszystkie odpowiedzi (7)
Just Reinstall Firefox And See What Happens, Also I'm Guessing You Have Windows, They All Mostly Have A Movie Maker Good Luck, Mitch!
Dear Mitch,
Thanks for your reply.
I have reinstalled Firefox 3 times over the last week. Same problem each time. Not only did I uninstall Firefox the last time, I also removed all trace that I could find of its records, logs and old files. Only the last time did I try reading the crash report, and hence the approach that I am now trying. Have searched for the .dll file, but cannot find one with the reported name. I will keep trying. John M
hello, could you provide your latest few submitted crash reports? please enter about:crashes into the location bar, copy the latest few report ids from there starting with bp- & paste them here into a forum reply...
Philipp, Thanks for your reply. Crash report is presented below. Last 10 reports seem all the same cause.
Firefox 29.0.1 Crash Report [@ __fnNCDESTROY ]
Search Mozilla Support for Help
ID: d1a9bd89-ac57-4e9e-abba-f92e32140531
Signature: __fnNCDESTROY
Details Metadata Modules Raw Dump Extensions Correlations
Signature __fnNCDESTROY More Reports Search UUID d1a9bd89-ac57-4e9e-abba-f92e32140531 Date Processed 2014-05-31 12:10:03.891055 Uptime 1 Last Crash 729 seconds before submission Install Age 98798 since version was first installed. Install Time 2014-05-30 08:41:49 Product Firefox Version 29.0.1 Build ID 20140506152807 Release Channel release OS Windows NT OS Version 6.0.6002 Service Pack 2 Build Architecture x86 Build Architecture Info GenuineIntel family 6 model 23 stepping 10 | 2 Crash Reason EXCEPTION_ACCESS_VIOLATION_READ Crash Address 0x0 User Comments Processor Notes sp-processor07_phx1_mozilla_com.26426:2012; HybridCrashProcessor EMCheckCompatibility
True
Winsock LSP
Adapter Vendor ID
Adapter Device ID
Total Virtual Memory
2147352576
Available Virtual Memory
1941254144
System Memory Use Percentage
57
Available Page File
2902003712
Available Physical Memory
917528576
Bugzilla - Report this bug in Firefox Core Plugins Toolkit Related Bugs
973138 VERIFIED FIXED startup crash in __fnNCDESTROY (mostly with MovieMode.48CA2AEFA22D.dll)
Crashing Thread Frame Module Signature Source 0 user32.dll __fnNCDESTROY 1 ntdll.dll KiUserCallbackDispatcher 2 ntdll.dll KiUserApcDispatcher
Show/hide other threads
Many thanks for your help. John M
edit: sorry your last post actually already contained the id: bp-d1a9bd89-ac57-4e9e-abba-f92e32140531
Zmodyfikowany przez philipp w dniu
Wybrane rozwiązanie
the offending library on your pc which is triggering the crash is named "Websteroids.B324755F3F87.2.6.80.dll" - please run a full scan of your system with different security tools like the free version of malwarebytes, adwcleaner, microsoft safety scanner & kaspersky security scan.
Thank you Philipp, I tried to remove Websteroids a month ago but it refused to uninstall using Windows, so I removed any files that I could find individually, but missed the .dll file. Tried to remove it again today but it refuses to be deleted, so I shifted the .dll file to another file. Firefox seems to be opening ok for now. I will try some of the cleaners tomorrow. Norton 360 and Macfee both say the protection is working ok, but I know the other cleaners pick up problems that Norton misses. Many thanks, John m