VOGONS


First post, by Gemini000

User metadata
Rank l33t
Rank
l33t

I don't think there's a single person here who isn't familiar with the Win9x Blue Screen of Death.

However, a long while back when doing some reformatting and reinstalling of things, I encountered a different BSOD from Windows 98 SE. It still had a blue background and white (or grey, forget which) text, but instead of a whole page worth with an fg/bg inverted program/driver name, centred in the middle of the screen, it simply had only a couple short lines of text, non-centred, near the bottom.

I'm curious if anyone else has seen this before or if anyone has any screen captures of this. I'm pretty sure the only way to generate this screen is to have a critical failure before the kernel can be fully loaded, as I believe when I got this error the problem file which couldn't be loaded at all was KERNEL32.DLL or something like that.

--- Kris Asick (Gemini)
--- Pixelmusement Website: www.pixelships.com
--- Ancient DOS Games Webshow: www.pixelships.com/adg

Reply 1 of 5, by Snayperskaya

User metadata
Rank Member
Rank
Member

Interesting. Never saw this one, actually, but I've somehow managed to produce a Red Screen of Death once while trying to run a 16-bit Windows app on XP or 7. Can't remember the circumstances, though. 🙁

Reply 2 of 5, by Jorpho

User metadata
Rank l33t++
Rank
l33t++

It makes me think of aclock, which was posted about a couple of times on os2museum.com ; there's even an NT kernel mode device driver version that outputs to the Windows NT BSOD.
http://www.os2museum.com/wp/windows-nt-bsod-aclock-port/

Maybe the thing you saw was actually a unique feature of whatever drivers you were using.

Reply 3 of 5, by Gemini000

User metadata
Rank l33t
Rank
l33t
Jorpho wrote:

Maybe the thing you saw was actually a unique feature of whatever drivers you were using.

Maybe... but given that it would come up BEFORE Windows was loaded completely, and the fact that it was pointing out Windows-critical files, I'm more inclined to believe it was a Windows thing, especially since it was doing this before I installed any third-party drivers. :o

--- Kris Asick (Gemini)
--- Pixelmusement Website: www.pixelships.com
--- Ancient DOS Games Webshow: www.pixelships.com/adg

Reply 5 of 5, by calvin

User metadata
Rank Member
Rank
Member

Maybe ScanDisk checking the disk for errors?

2xP2 450, 512 MB SDR, V3 2000, Asus P2B-D, Windows 2000
P4 2.6, 2 GB DDR1, Radeon 9600 Pro, P4P800, Windows XP
Alpha 21164, 512 MB, Permedia 2, KZPCM, AlphaPC 164, NT 4.0