Fun idea: replacing the newer BSOD with the older one

Discuss Windows Vista/Server 2008 to Windows 10.
Post Reply
AS95678
Posts: 115
Joined: Sat Jan 16, 2016 5:06 pm

Fun idea: replacing the newer BSOD with the older one

Post by AS95678 »

Here's a fun idea: replacing the newer BSOD introduced in Windows 8 with the older BSOD style used in Windows XP-7. Where is the BSOD and its resources stored? Is there anything that's been cut from newer versions of the BSOD that will have to be hacked in?

Vova23
Posts: 23
Joined: Wed Feb 19, 2014 5:09 pm
Contact:

Re: Fun idea: replacing the newer BSOD with the older one

Post by Vova23 »

ntoskrnl.exe

Zv45Beta
User avatar
Donator
Posts: 513
Joined: Wed Jun 22, 2011 10:27 am
Location: North-eastern Croatia
Contact:

Re: Fun idea: replacing the newer BSOD with the older one

Post by Zv45Beta »

The only resources that are stored in ntoskrnl.exe are hibernation, "It's now safe to turn off your computer", and some black bitmaps that were used for the XP bootscreen.

Image

It looks like the sad face from the Win10 BSOD is hardcoded: I'm not sure of its format in the file (probably some kind of a BMP file...)

The strings like "Your PC ran into a problem..." are actually hardcoded and are not found in Resource Hacker.

Image
Main computer: HP 820 G4 | i5-7500U | 16GB DDR4 | 256GB M.2 SATA SSD & 2TB 2.5" HDD | Linux Mint 21.3 Xfce
XP PC: ASUS P5QPL-AM | Xeon L5408 | 4GB DDR2-800 | 250GB 870 EVO SSD | ATi HD 6450 | XP SP4
9x PC: MSI MS-6368 v5 | Pentium III-S 1266 | 640MB PC133 | ATi 7000 PCI | 10GB HDD | WinMe
Other PCs: 2x EeePC 701 (1x spare, 1x XP SP3), HP 800 G2 DM (Win11 23H2), Wyse Cx0 (XP SP1a)
I collect Windows CE devices.

3155ffGd
User avatar
Posts: 391
Joined: Wed May 02, 2012 12:57 am

Re: Fun idea: replacing the newer BSOD with the older one

Post by 3155ffGd »

I've been under the impression the sad face in Windows 8/10 is simply a plain-text ":(", and thus it should also be found as a string within the file. But as with the rest of the text, it would be hardcoded and not found as a resource viewable with Resource Hacker.

Zv45Beta
User avatar
Donator
Posts: 513
Joined: Wed Jun 22, 2011 10:27 am
Location: North-eastern Croatia
Contact:

Re: Fun idea: replacing the newer BSOD with the older one

Post by Zv45Beta »

3155ffGd wrote:I've been under the impression the sad face in Windows 8/10 is simply a plain-text ":(", and thus it should also be found as a string within the file. But as with the rest of the text, it would be hardcoded and not found as a resource viewable with Resource Hacker.
I did find bytes that may actually be the sad face that is printed on the screen (and it's all in the Segoe font, including the text with the error, so it makes sense)
Main computer: HP 820 G4 | i5-7500U | 16GB DDR4 | 256GB M.2 SATA SSD & 2TB 2.5" HDD | Linux Mint 21.3 Xfce
XP PC: ASUS P5QPL-AM | Xeon L5408 | 4GB DDR2-800 | 250GB 870 EVO SSD | ATi HD 6450 | XP SP4
9x PC: MSI MS-6368 v5 | Pentium III-S 1266 | 640MB PC133 | ATi 7000 PCI | 10GB HDD | WinMe
Other PCs: 2x EeePC 701 (1x spare, 1x XP SP3), HP 800 G2 DM (Win11 23H2), Wyse Cx0 (XP SP1a)
I collect Windows CE devices.

AS95678
Posts: 115
Joined: Sat Jan 16, 2016 5:06 pm

Re: Fun idea: replacing the newer BSOD with the older one

Post by AS95678 »

Hmm, where's the color of the BSOD stored and how did older versions of the Blue Screen dump the text on the screen and how does it differ from newer versions?

Zv45Beta
User avatar
Donator
Posts: 513
Joined: Wed Jun 22, 2011 10:27 am
Location: North-eastern Croatia
Contact:

Re: Fun idea: replacing the newer BSOD with the older one

Post by Zv45Beta »

AS95678 wrote:Hmm, where's the color of the BSOD stored and how did older versions of the Blue Screen dump the text on the screen and how does it differ from newer versions?
You'd have to disassemble ntoskrnl.exe to find the exact procedure/operation used for color filling of the BSOD. (haven't tried it with Win32Dasm yet, I'll have a look tomorrow)

I think older versions did a fallback to 640x480 16-color mode (in case the native driver goes berzerk) and that the text was bitmapped. I'm not sure about that either, but I'll try to compare NT5 and NT6 with a disassembler and with a hex editor.
Main computer: HP 820 G4 | i5-7500U | 16GB DDR4 | 256GB M.2 SATA SSD & 2TB 2.5" HDD | Linux Mint 21.3 Xfce
XP PC: ASUS P5QPL-AM | Xeon L5408 | 4GB DDR2-800 | 250GB 870 EVO SSD | ATi HD 6450 | XP SP4
9x PC: MSI MS-6368 v5 | Pentium III-S 1266 | 640MB PC133 | ATi 7000 PCI | 10GB HDD | WinMe
Other PCs: 2x EeePC 701 (1x spare, 1x XP SP3), HP 800 G2 DM (Win11 23H2), Wyse Cx0 (XP SP1a)
I collect Windows CE devices.

XaddaGamer
User avatar
Posts: 20
Joined: Wed May 23, 2018 8:17 pm
Location: at Longhorn

Re: Fun idea: replacing the newer BSOD with the older one

Post by XaddaGamer »

I don't think about more this older BSOD from Windows XP, Vista and 7.

Post Reply