not been able to open firefox for days just keep getting crash reporter, tried everything, no joy
for the past few days, a week at most, i've been unable to open firefox, it just keeps giving me the crash reporter.. i always use firefox, i've not installed any add ons (i did install dropbox lately but thats about it), i always have adblockplus running, have done for months never had a problem
having to use Opera at the minute cos Chrome is the slowest browser known to man (why everyone sings its praises i'll never know)
then one day, i tried opening firefox, it said checking compatibility of add-ons, then gave the crash reporter box, not been able to do anything since
i've followed all guides on here, i've reset all settings, i've updated the add-ons it said i had, i've tried booting in safe mode.. ..all with the same result, crash reporter
so please dont tell me to go into firefox and change settings as i cant even open firefox
here is my latest crash report ID Crash ID: bp-27aa708f-12d0-4b17-ac96-0961a2130115
被選擇的解決方法
It is a malware problem see Firefox 18 crashes on startup due to malware - how to fix
從原來的回覆中察看解決方案 👍 1所有回覆 (4)
選擇的解決方法
It is a malware problem see Firefox 18 crashes on startup due to malware - how to fix
Further info
Please follow the instructions in the article from the above post. In fct you have a second suspicious file showing on your report so look specifically at and scan files gblrofmx.dll & sprotector.dll
If possible I suggest you quarantine the files rather than deleting them immediately. Also note that you may need to start Windows in safe mode (or Windows safemode with network access) in order to find and move or delete the files.
- Use F8 to access Windows safe mode
http://windows.microsoft.com/en-US/windows7/Start-your-computer-in-safe-mode
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/boot_failsafe.mspx?mfr=true
For forum cross referencing purposes
- Report for CrashID 27aa708f-12d0-4b17-ac96-0961a2130115
- Crash Signature: nsInputStreamPump::OnInputStreamReady(nsIAsyncInputStream*)
- related bug 801394, and contributors thread nsInputStreamPump::OnInputStreamReady Crashes (Malware)
- files without ID RocketDock.dll , gblrofmx.dll , sprotector.dll
- sprotector.dll some suspicions about this being possible malware trojan
Bug 785940 - Firefox startup crash in SECMOD_GetModuleSpecList @ __hash_open with SProtector.dll (Safend Protector, Sophos SafeGuard or TrojanDownloader:HTML/Sprotector.A?)
thread Firefox crashes - gblrofmx.dll likely to be the malware responsible for current crashes
由 John99 於
righto, first off.. thanks, my Firefox now loads up again :D woo!
secondly, i did a search for the 2 .dll files, only found the sprotector.dll one, found the containing folder and uninstalled the program (whatever it was).. so thats one gone..
as for the other one (gblrofmx.dll), it didn't show up in a search, so does that mean its already been removed?
i dont know what i'm doing in Windows Safe Mode, but if i have to, i'll try..
do you think i could try to just see how it goes or do i absolutely NEED to find and remove that file?
Thanks man!!! speedy browsing again :D
Glad you fixed it, thanks for posting back.
as for the other one (gblrofmx.dll), it didn't show up in a search, so does that mean its already been removed?
The file may be hidden or in a hidden or system folder so you should ensure you are searching for such files.
Windows safe mode
is easy to use, the only problem is sometimes not easy to get in to as it may require pressing the F8 key at a particular moment. The usual trick is to press the key about twice a second whilst in the reboot/post situation. If you use the option with network support you get the familiar menus, and do not have to resort to DOS commands as you may in the Recovery Console.
do i absolutely NEED to find and remove that file?
You do not absolutely have to remove the file as Firefox is now working.
If I were in your position I would quarantine or remove it.
A file with no web search results is almost always malware, especially when found from a malware related crash report. We have no idea what the file could do, but it is unlikely to be anything good. Conceivably it could for instance open backdoors and allow your computer to be used as a botnet or start dialling out premium rate numbers.
You really need to do multiple scans on your compute with up to date tools to find out what you may have. See