The support case of a customer who said that all they could see was a black screen

The Old New Thing (Raymond Chen) News

Summary

Raymond Chen recounts a Windows 3.1-era support case where a customer set every system color to black for a goth theme and couldn't see anything, plus background on how Windows classifies emergency 'black screen LPBH' kernel dumps triggered by long power-button holds.

<p>If you hold a PC&#8217;s power button for 12 seconds, it will turn off at the hardware level without notifying the operating system. This is a safety feature so that you can turn of the computer even if the operating system&#8217;s &#8220;Shut down&#8221; command isn&#8217;t working.</p> <p>After eight seconds of the power button being held down, the Windows kernel realizes that the user is trying to do a force-power-off of the system, and it quickly takes a kernel dump that can be uploaded to the Windows Error Reporting service the next time you turn the system on. (Sometimes four seconds isn&#8217;t enough time to get enough information, and the kernel dump is incomplete. I believe that on Windows Insider builds of Windows, you get a message that says something like &#8220;Please let go of the power button so we can collect more information, and then we will turn off the computer.&#8221; This gives the kernel more time to finish capturing its kernel dump.)</p> <p>These emergency kernel dumps are internally classified as &#8220;long power button hold&#8221; (LPBH) failures. One of the pieces of information recorded in these emergency kernel dumps is whether the screen consists entirely of black pixels. Those failures are sub-classified as &#8220;black screen LPBH&#8221;, and they go to a special virtual team for analysis. (I happen to be a member of this black screen LPBH team.)</p> <p>Sometimes the problem is a broken video driver. Sometimes the video driver is doing just fine, but the desktop compositor is just handing black pixels to the video driver. Sometimes the desktop compositor is doing just fine, but nobody is drawing anything to the screen. And those cases are further subdivided further into cases like &#8220;there is nobody around to draw anything&#8221; or &#8220;the person who normally draws stuff is hung.&#8221;</p> <p>Back in the Windows 3.1 days, there was a customer product support call that would today have been classified as a &#8220;black screen&#8221; bug: The customer reported that they turned on the computer, and Windows started up, but when the logo went away, all they saw was a blank screen.</p> <p>After some questioning, the customer support engineer put the story together: It turned out that this customer really liked the color black, so they decided to set up a <a href="https://en.wikipedia.org/wiki/Gothic_fashion"> goth</a> theme. They set the wallpaper color to black. They set the title bar color to black. They set the button color to black. They set the window background color to black. They set the window text color to black. Every possible color you could pick in the Colors control panel was set to black.</p> <p>Once you get yourself into this situation, it&#8217;s hard to get out because you can&#8217;t see anything.</p> <p>I don&#8217;t know how the customer support engineer fixed the problem, but I&#8217;m guessing that they booted into MS-DOS, ran <code>EDIT.COM</code>, and <a href="https://jeffpar.github.io/kbarchive/kb/083/Q83433/"> deleted the <tt>[colors]</tt> section from the <tt>win.ini</tt> file</a>, thereby returning all the system colors to defaults.</p> <p>The post <a href="https://devblogs.microsoft.com/oldnewthing/20261029-00/?p=112808/">The support case of a customer who said that all they could see was a black screen</a> appeared first on <a href="https://devblogs.microsoft.com/oldnewthing">The Old New Thing</a>.</p>
Original Article
View Cached Full Text

Cached at: 10/30/26, 03:06 PM

# The support case of a customer who said that all they could see was a black screen - The Old New Thing Source: [https://devblogs.microsoft.com/oldnewthing/20261029-00/?p=112808/](https://devblogs.microsoft.com/oldnewthing/20261029-00/?p=112808/) If you hold a PC’s power button for 12 seconds, it will turn off at the hardware level without notifying the operating system\. This is a safety feature so that you can turn of the computer even if the operating system’s “Shut down” command isn’t working\. After eight seconds of the power button being held down, the Windows kernel realizes that the user is trying to do a force\-power\-off of the system, and it quickly takes a kernel dump that can be uploaded to the Windows Error Reporting service the next time you turn the system on\. \(Sometimes four seconds isn’t enough time to get enough information, and the kernel dump is incomplete\. I believe that on Windows Insider builds of Windows, you get a message that says something like “Please let go of the power button so we can collect more information, and then we will turn off the computer\.” This gives the kernel more time to finish capturing its kernel dump\.\) These emergency kernel dumps are internally classified as “long power button hold” \(LPBH\) failures\. One of the pieces of information recorded in these emergency kernel dumps is whether the screen consists entirely of black pixels\. Those failures are sub\-classified as “black screen LPBH”, and they go to a special virtual team for analysis\. \(I happen to be a member of this black screen LPBH team\.\) Sometimes the problem is a broken video driver\. Sometimes the video driver is doing just fine, but the desktop compositor is just handing black pixels to the video driver\. Sometimes the desktop compositor is doing just fine, but nobody is drawing anything to the screen\. And those cases are further subdivided further into cases like “there is nobody around to draw anything” or “the person who normally draws stuff is hung\.” Back in the Windows 3\.1 days, there was a customer product support call that would today have been classified as a “black screen” bug: The customer reported that they turned on the computer, and Windows started up, but when the logo went away, all they saw was a blank screen\. After some questioning, the customer support engineer put the story together: It turned out that this customer really liked the color black, so they decided to set up a[goth](https://en.wikipedia.org/wiki/Gothic_fashion)theme\. They set the wallpaper color to black\. They set the title bar color to black\. They set the button color to black\. They set the window background color to black\. They set the window text color to black\. Every possible color you could pick in the Colors control panel was set to black\. Once you get yourself into this situation, it’s hard to get out because you can’t see anything\. I don’t know how the customer support engineer fixed the problem, but I’m guessing that they booted into MS\-DOS, ran`EDIT\.COM`, and[deleted the\[colors\]section from thewin\.inifile](https://jeffpar.github.io/kbarchive/kb/083/Q83433/), thereby returning all the system colors to defaults\. ### Category ### Topics ## Author ![Raymond Chen](https://devblogs.microsoft.com/oldnewthing/wp-content/uploads/sites/38/2019/02/RaymondChen_5in-150x150.jpg) Raymond has been involved in the evolution of Windows for more than 30 years\. In 2003, he began a Web site known as The Old New Thing which has grown in popularity far beyond his wildest imagination, a development which still gives him the heebie\-jeebies\. The Web site spawned a book, coincidentally also titled The Old New Thing \(Addison Wesley 2007\)\. He occasionally appears on the Windows Dev Docs Twitter account to tell stories which convey no useful information\.

Similar Articles

Windows brings out the Rorschach test in everyone

Hacker News Top

The blog post recounts humorous incidents where Windows 95 and XP packaging and wallpapers were misinterpreted by the public, leading to design changes. Author Raymond Chen shares these stories from Microsoft's history.

The case of the hang when the user changed keyboard layouts

The Old New Thing (Raymond Chen)

A debugging story about a Windows program hanging when the user changes keyboard layouts due to a background thread that created a window but wasn't pumping messages. The fix is to either pump messages or destroy the window.

Who’s 0xabadbabe and why? (2011)

Lobsters Hottest

Daniel Stenberg shares a 2011 debugging war story about chasing the mysterious 0xABADBABE value written to an EHCI register during Windows 7 boot while working on Intel system simulation software, ultimately discovering it was an intentional debugger breakpoint and unrelated to a blue-screen bug.

A compatibility note on the abuse of Windows window class extra bytes

The Old New Thing (Raymond Chen)

Raymond Chen discusses a historical Windows compatibility issue where some 16-bit programs abused window class extra bytes to store private data, and how Microsoft blocked the loophole for 32-bit and 64-bit programs while maintaining backward compatibility.