Firefox crashes
Hi
I have been experiencing problems for a while now & completely at a loss. Please help me fix this so I don't have to go to the dark side...
OK, Firefox started crashing when I first upgraded my computer to Windows 7 64 bit.
You'll have to forgive me because I'm not hugely technically able, but I'll try my best...
I upgraded my PC with a new motherboard & ram & Windows 7 (64bit), this was when the problems started. Firefox (I was running 9 at the time) was crashing 10 or 11 times a day. I tried everything that was advised & it didn't solve anything. I tied in safe mode, disabled by add-ons a separate time & couldn't even get to my profile.
I am a very heavy user of the internet & decided that enough was enough, I wanted a new PC for a while & ended up building a completely new system (with the same RAM). I installed Windows 7 again & used MozBackup so not to lose my data. All was fine for a day then it started again. I'm reporting the crashes frequently but still at complete loss.
Annoyingly, the details of the crash aren't saved & when I go to about:crashes and click on one of the Crash IDs it says: We couldn't find the OOID you're after. If you recently submitted this crash, it may still be in the queue.
If you believe this message is an error, please submit a Bugzilla ticket describing what happened, and please include the URL for this page.
So I've had to copy & paste the details once it's happened, into notepad.
Here is one of the crash reports:
AdapterDeviceID: 0112 AdapterVendorID: 8086 Add-ons: en-GB@dictionaries.addons.mozilla.org:1.19.1,snaplinks@snaplinks.mozdev.org:2.2.1,splitpannel@max.max:1.00,{19503e42-ca3c-4c27-b1e2-9cdb2170ee34}:1.3.8,{BBDA0591-3099-440a-AA10-41764D9DB4DB}:10.1.0.68 - 1,{972ce4c6-7e08-4474-a285-3208198ce6fd}:10.0,{22119944-ED35-4ab1-910B-E619EA06A115}:7.7.0 AvailableVirtualMemory: 3581718528 BuildID: 20120129021758 CrashTime: 1328968305 EMCheckCompatibility: true FramePoisonBase: 00000000f0de0000 FramePoisonSize: 65536 InstallTime: 1328836091 Notes: AdapterVendorID: 8086, AdapterDeviceID: 0112, AdapterSubsysID: 00000000, AdapterDriverVersion: 8.15.10.2509 D2D? D2D+ DWrite? DWrite+ D3D10 Layers? D3D10 Layers+
ProductName: Firefox ReleaseChannel: release SecondsSinceLastCrash: 50210 StartupTime: 1328967064 SystemMemoryUsePercentage: 23 Theme: classic/1.0 Throttleable: 1 TotalVirtualMemory: 4294836224 URL: http://www.halfords.com/webapp/wcs/stores/servlet/product_storeId_10001_catalogId_10151_productId_753273_langId_-1_categoryId_255230 Vendor: Mozilla Version: 10.0 Winsock_LSP: MSAFD Tcpip [TCP/IP] : 2 : 1 : %SystemRoot%\system32\mswsock.dll
MSAFD Tcpip [UDP/IP] : 2 : 2 : MSAFD Tcpip [RAW/IP] : 2 : 3 : %SystemRoot%\system32\mswsock.dll MSAFD Tcpip [TCP/IPv6] : 2 : 1 : MSAFD Tcpip [UDP/IPv6] : 2 : 2 : %SystemRoot%\system32\mswsock.dll MSAFD Tcpip [RAW/IPv6] : 2 : 3 : RSVP TCPv6 Service Provider : 2 : 1 : %SystemRoot%\system32\mswsock.dll RSVP TCP Service Provider : 2 : 1 : RSVP UDPv6 Service Provider : 2 : 2 : %SystemRoot%\system32\mswsock.dll RSVP UDP Service Provider : 2 : 2 :
I'm not even sure if I've done any of this right, but if you need more information then please let me know & I'll do my best :)
Thanks
Chosen solution
Thank you for all your advice. I *finally* ran memtest & turned out I had a bad stick of RAM (4gb out of 8gb G.Skill Ripjaws set). Although the problem wasn't immediately resolved once the defective RAM was removed, it was a lot less frequent. I then removed the second stick of RAM (so to RMA with the bad one) and in it's place I installed 8gb of brand new Kingston RAM. It's been nearly 72 hours now & all the crashes have stopped; there would gave been a few in that time so hoping it's permanent :)
Just thought I would reply with how it was resolved, in case anyone else has this problem. Bad RAM certainly has a lot to answer for!
Read this answer in context 👍 0All Replies (7)
Thank you, I have but absolutely nothing that is there has resolved my problem, hence why I'm on here. I'm desperate now, I really don't want to have to go to Internet explorer :( I just can't see any other option
The crashes seem to be related to garbage collection (i.e. cleanup 'unused' memory, but in this case the memory may still be in use) and such crashes are hard to diagnose.
Do a malware check with some malware scanning programs on the Windows computer.
You need to scan with all programs because each program detects different malware.
Make sure that you update each program to get the latest version of their databases before doing a scan.
- http://www.malwarebytes.org/mbam.php - Malwarebytes' Anti-Malware
- http://www.superantispyware.com/ - SuperAntispyware
- http://www.microsoft.com/security/scanner/en-us/default.aspx - Microsoft Safety Scanner
- http://www.microsoft.com/windows/products/winfamily/defender/default.mspx - Windows Defender: Home Page
- http://www.safer-networking.org/en/index.html - Spybot Search & Destroy
- http://www.lavasoft.com/products/ad_aware_free.php - Ad-Aware Free
See also:
- "Spyware on Windows": http://kb.mozillazine.org/Popups_not_blocked
Could it really be Malware when it did it as soon as I used my completely new PC?
The only thing I kept from my old PC was the RAM, could it be that causing it?
I do run Malwarebytes every evening too.
Thanks :)
I don't know what is causing the crashes in cases like this, so it is best to follow the book and try every possible cause to be sure not to miss possible causes.
You can also try to boot Windows in Safe mode with network support by pressing the F8 key on the boot screen.
Chosen Solution
Thank you for all your advice. I *finally* ran memtest & turned out I had a bad stick of RAM (4gb out of 8gb G.Skill Ripjaws set). Although the problem wasn't immediately resolved once the defective RAM was removed, it was a lot less frequent. I then removed the second stick of RAM (so to RMA with the bad one) and in it's place I installed 8gb of brand new Kingston RAM. It's been nearly 72 hours now & all the crashes have stopped; there would gave been a few in that time so hoping it's permanent :)
Just thought I would reply with how it was resolved, in case anyone else has this problem. Bad RAM certainly has a lot to answer for!
moderator removed spam link
Forum rules and guidelines
Modified by the-edmeister