User-Agent: Mozilla/5.0 (Windows; U; Win98; en-GB; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-GB; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 Can you please help as I am NOT a programmer, just a computer user with a BIG problem. I have downloaded and installed last week the latest FIREFOX and a couple of days ago I got a message come up stating I should download the latest extensions. I saw NOSCRIPT 1.0.4 which seemed a good idea so downloaded and installed as directed. After a couple of days working O.K. I have found that when I try to use FIREFOX I get the following error. I can run in SAFE MODE but what is the problem and how do I cure it? As I still had the original download I tried to UNINSTALL FIREFOX and then re-install the original but I keep getting the same message unless I load in SAFE MODE. HELP!! FIREFOX caused an invalid page fault in module <unknown> at 0000:c085d6ff. Registers: EAX=00610072 CS=0177 EIP=c085d6ff EFLGS=00010283 EBX=80000000 SS=017f ESP=00e3e88c EBP=00e3e8a4 ECX=01014470 DS=017f ESI=01014470 FS=219f EDX=01013e54 ES=017f EDI=00000000 GS=0000 Bytes at CS:EIP: Stack dump: 00a7efc7 01014470 00a12f6c 00000000 00000000 80000000 00e3e95c 004a17dd 01014470 00a12f6c 00000000 00f6b0b0 80000000 00000000 00000000 00e3e940 Reproducible: Always Steps to Reproduce: 1.Run FIREFOX 2.See above 3. Actual Results: Closed the window and I am looking at the DESKTOP screen Expected Results: RUN!! This problem has occurred ONLY after I loaded NOSCRIPT. FIREFOX works perfectly in SAFE MODE
Reporter: Can you please reproduce the crash with talkback enabled and get us the Talkback ID?
>I can run in SAFE MODE but what is the problem and how do I cure it? That means that an extension is causing this. You can uninstall the extensions under tools/Extensions. -> invalid Bugzilla is not for user support. Please ask such questions for example in the mozillazine.org Forums or on IRC.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.