Closed
Bug 24447
Opened 25 years ago
Closed 25 years ago
Bad Crash on NT Following Install and Reboot
Categories
(SeaMonkey :: Installer, defect, P3)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
M14
People
(Reporter: sol, Assigned: ssu0262)
Details
(Keywords: crash)
[Build ID 2000011909]
I'm running Windows NT 4.0 (Service Pack 5, I think), with 128 MB RAM.
I ran the installer for today's build, and was prompted to reboot following
installation. I rebooted, and before the windows desktop came up, I got a *blue
screen of death* (details below). I did a hard reboot of the machine, and was
able to get to the windows desktop. Seamonkey, however, fails to launch - I
start up the build, the console starts up and then stops. The Seamonkey chrome
never displays.
Information from the blue screen of death:
Stop: 0x0000000A
IRQL_NOT_LESS_OR_EQUAL*** Address 801174a4 has base at 80100000 - ntoskrnl.exe
CPUID: GenuineIntal 6.6.a irql:1c Sysver 0xf000565
DLL Base Datestamp Name
80100000 371cd681 ntoskrnl.exe
80013000
Sorry - the bug got away from me before I finished entering the blue screen of
death info :-)
Information from the blue screen of death:
Stop: 0x0000000A
IRQL_NOT_LESS_OR_EQUAL*** Address 801174a4 has base at 80100000 - ntoskrnl.exe
CPUID: GenuineIntal 6.6.a irql:1c Sysver 0xf000565
DLL Base Datestamp Name
80100000 371cd681 ntoskrnl.exe
80013000 359be340 Pcmcia.sys
801e1000 36d72c79 SCSIport.sys
801f1000 353e319e Disk.app
801f9000 36fc4fb5 fastfat.sys
80001000 3640d6a7 hal.dll
801da000 3656211c atapi.sys
801ea000 354df951 Atdisk.sys
801f5000 3643604f Class2.sys
Updated•25 years ago
|
Severity: normal → critical
Comment 2•25 years ago
|
||
Sol,
Can you try with the later build for 1/19- 2000011913- I was successful in
launching this build
I did not crash with the earlier build but it had 'hanging' problems (I did not
restart) and wonder if that may be related- after a restart, seamonkey should
launch immediately
Thanks,
Grac
Sol, does your machine work okay?
Can you help and try install with tomorrow's build? Sean has checked in a
fix for bug 24373 in installer, so no reboot is needed.
thanks!
Target Milestone: M14
My machine is OK, but I'm in North Carolina. I will install a new build on
Monday, and let you know how I do.
Adding "crash" keyword to all known open crasher bugs.
Keywords: crash
This is not an installer problem. It could be in the profile manager, or other
startup code. I haven't heard anyone else report this crash problem. I can't
reproduce this either.
I'm marking this as worksforme. if you still see this problem, please feel free
to reopen this bug.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Comment 7•25 years ago
|
||
.
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•