I'm getting blue screens of death.

VERIFIED INCOMPLETE

Status

()

--
critical
VERIFIED INCOMPLETE
12 years ago
8 years ago

People

(Reporter: omegaXridley, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

12 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3

This is the fourth time this month that Firefox has caused a blue screen of death restart.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
(Reporter)

Comment 1

12 years ago
Also, my extensions aren't working. I have Adblock Plus and ads are appearing.
What is the error message? The more details you give us, the more we can help you and so far, you've only given us three sentences.
(Reporter)

Comment 3

12 years ago
(In reply to comment #2)
> What is the error message? The more details you give us, the more we can help
> you and so far, you've only given us three sentences.
> 

There are no error messages. Firefox randomly causes the blue screen and then my computer is forced to restart. There's really nothing left to say. Also, my Adblock Plus extension isn't blocking adware at all. I can actually see the advertisements.
(Reporter)

Comment 4

12 years ago
One time I DID get an error saying "Error inferenced at 0x0000####". I forgot the numbers. But this only happened one time. The forced restarts occured twice, and I believe the memory error happened after the first restart but before the fourth.
(Reporter)

Comment 5

12 years ago
Oh, speak of the devil. This happened when I typed in my password and hit enter.
http://i7.tinypic.com/681guwk.jpg
Doug, do you ever see this error when using a new profile?

http://kb.mozillazine.org/Profile_Manager
Incomplete; not enough information.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → INCOMPLETE

Updated

8 years ago
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.