zuri
Freshman Member
Posts: 44
OS: Windows 10 1909
Theme: Windows XP Luna
|
Post by zuri on Oct 19, 2023 11:18:53 GMT -8
Hello,
Is there any way to bring back the old Blue Screen of Death from Windows Vista, XP, and 7 onto Windows 10/11. You know the one with just the text and not the one with the sad face emoticon.
Thanks,
Zuri
|
|
|
|
Post by Brawllux on Oct 19, 2023 12:10:13 GMT -8
You should be able to hide the smiley with winaero tweaker.
|
|
Jevil7452
Regular Member
Posts: 434
OS: Windows 7 Enterprise (6.1.7601)
Theme: Windows Aero by Microsoft Corporation
CPU: Intel Core i7-3770k
RAM: 32GB (4x8GB DDR3)
GPU: NVIDIA GeForce GTX 980 Ti + Intel(R) HD Graphics 4000
Computer Make/Model: OEM0
|
Post by Jevil7452 on Oct 19, 2023 12:24:47 GMT -8
Sadly no method is available yet, but you can restore the more detailed codes and hide the smiley Both settings are in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl DisableEmoticon = 1 - disabled the smiley DisplayParameters = 1 - restores the more detailed codes If they do not exist, you need to create them as DWORD values Bonus value: DisplayPreReleaseColor = 1 - Insider Preview BSOD color/text
|
|
CatmanFan
New Member
Posts: 17
OS: Windows 10 Pro 21H1
Theme: Windows 7 Aero/Basic
CPU: Intel Core i5-12400F 250 GHz
RAM: 16GB
GPU: NVIDIA GeForce RTX 4060
|
Post by CatmanFan on Oct 26, 2023 8:19:24 GMT -8
This is going to take a bit to explain, but I'll do what I can to simplify.
The BSOD that you see in classic Windows NT (2000, XP, Vista/7) is actually rendered in 640x480 16-color video mode, the same used for the boot screen in those versions. The driver that handles these functions in System32 is bootvid.dll (VGA Boot Driver).
Both the boot screen and BSOD were redesigned post-Windows 7 to account for larger resolutions using BGFX (Boot Graphics Library). The resources for the leftover Vista boot screen still exist and it can be enabled with bcdedit /set {current} graphicsmodedisabled on, which causes the system to fallback to using VGA mode if it is available (i.e. legacy BIOS or UEFI/CSM hybrid). There is no such fallback for when a BSOD occurs (or even in the case of the non-ACPI "safe to turn off" screen), since the assembly code for it was most likely removed from bootvid, so the screen just freezes.
Perhaps one possible workaround would be to attempt patching bootvid to add support for rendering the BSOD in VGA mode, but I'm not very sure at this point.
|
|
|
|
Post by ephemeralViolette on Oct 26, 2023 15:19:51 GMT -8
This is going to take a bit to explain, but I'll do what I can to simplify. The BSOD that you see in classic Windows NT (2000, XP, Vista/7) is actually rendered in 640x480 16-color video mode, the same used for the boot screen in those versions. The driver that handles these functions in System32 is bootvid.dll (VGA Boot Driver). Both the boot screen and BSOD were redesigned post-Windows 7 to account for larger resolutions using BGFX (Boot Graphics Library). The resources for the leftover Vista boot screen still exist and it can be enabled with bcdedit /set {current} graphicsmodedisabled on, which causes the system to fallback to using VGA mode if it is available (i.e. legacy BIOS or UEFI/CSM hybrid). There is no such fallback for when a BSOD occurs (or even in the case of the non-ACPI "safe to turn off" screen), since the assembly code for it was most likely removed from bootvid, so the screen just freezes. Perhaps one possible workaround would be to attempt patching bootvid to add support for rendering the BSOD in VGA mode, but I'm not very sure at this point. From what I understand, bootvid is only responsible for video output (bitmap images and bitmap fonts) for VGA. Basically all kernel graphics were drawn by ntoskrnl though. That very likely includes the bug check message, but I only know for sure that this is the case for the boot screen (which hasn't really fundamentally changed since Windows 2000, and hasn't changed at all since Vista which was just the XP variant with a different colour palette and replaced bitmaps).
Although with a custom (UEFI-compatible) bootvid driver and some kernel hooking (not fun!), you might get somewhere with restoring the classic bug check screen.
|
|
