Closed
Bug 324089
Opened 20 years ago
Closed 19 years ago
Seemingly random Blue screen of death crash when using firefox
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: lostboyz69, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5
After reboot Windows reported with their bug report that the error was caused in:
Intel PRO/Wireless LAN 2200BG adapter software (w22n51.sys)
Restarting Firefox after that causes same crash. Using Firefox Bugzilla report causes same crash. Can only bring Firefox back up in safe mode.
Reproducible: Sometimes
Comment 1•20 years ago
|
||
BSODs indicate a problem with drivers, hardware, or OS. How is it related to Firefox?
| Reporter | ||
Comment 2•20 years ago
|
||
Firefox is the trigger, as is bugzilla. It is the interaction of these programs with the drivers, os, hardward that is causing a critical crash. I included the driver that failed so that interaction between os/driver/ firefox could be investigated.
Comment 3•19 years ago
|
||
Reporter, do you still see this problem with the latest Firefox 2? If not, can you please close this bug as WORKSFORME. Thanks!
Whiteboard: CLOSEME 06/27
Version: unspecified → 1.5.0.x Branch
Comment 4•19 years ago
|
||
I'm afraid this problem is reported to the wrong place. If Firefox is the trigger, and the problem is with certain driver or hardware, the problem should be reported to the driver/hardware vendor in charge.
http://downloadcenter.intel.com/Product_Filter.aspx?ProductID=1637
if you google for w22n51.sys, you'll see lots of reports about it causing blue screens.
if you want to get help, collect a minidump and try to complain to intel, but first figure out if you have the latest version. it seems people didn't like the 8.x drivers.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
Whiteboard: CLOSEME 06/27
You need to log in
before you can comment on or make changes to this bug.
Description
•