Black Screen (KSOD) Vista Solutions

Before I get started, some resources:

I’m looking at a friend’s laptop for him. It boots, gets past the progress bar, but before login or a desktop, the screen goes black with a cursor present which can be moved. There are multitudes of threads and posts about this issue over the internet, ranging as far back as 2006 and as recently as last month (May 1010). Although the symptoms are similar, from what I can see there are several causes each with different fixes.

For example, if the login screen comes up and there is a black screen after, it may be possible to hit Ctrl+Shit+Esc together to bring up Task Manager, from there do File->New Task (Run…), explorer.exe. This will bring up the desktop etcaetera, from where you can run other tools to repair the issue.

Advanced Startup Options Menu

Hit F8 while the computer is booting to bring up this menu. It has a number of potentially useful options, and is probably the easiest and lowest-impact to try first. The following options from that menu have been reported to work for some:

  • Safe Mode (with Networking / Command Prompt)
  • Enable low-resolution video (seems to help with nVidia driver update issues)
  • Last Known Good Configuration
  • Disable Driver Signature Enforcement (helps with some other driver errors in HP laptops, if I remember correctly)

It may also help to choose the Enable Boot Logging option, which should create a file called ntbtlog.txt containing info that might point to the driver or component that is causing issues.

Using the Windows System Recovery tool

The first option on the advanced startup menu listed above is “Repair your computer”. This starts a graphical interface with a number of options which may help.

System Restore

You should try to do a system restore first, if it is enabled. If it isn’t enabled, make sure to enable it when you fix the problem! Click the “System Restore” option on the menu (second item) and choose a restore point from when you believe your computer was previously functional.

Registry Fix

It may be a registry issue. In some cases, it would appear the Shell entry is corrupted. You can sort it by doing the following:

  1. Turn on the computer
  2. As it boots, press F8 to bring up the advanced boot options menu
  3. Select “Repair Your Computer”
  4. From there, login to an admin account (eg Administrator)
  5. Select the bottom option to launch a command prompt
  6. type regedit and hit enter
  7. Navigate through the following keys: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\Current\Winlogon
  8. One you are at Winlogon, there should be an item on the right panel that says “Shell“. Right click this, and select edit.
  9. Change the value to explorer.exe. If this is already present, this is not your issue!

NOTE: If you try this from the “Repair Windows” option on a Windows Vista install DVD or recovery DVD it won’t work, as that seems to edit the registry on the disc (you will see cmd.exe /k start cmd.exe or similar for the Shell key). For me the “load hive” option was greyed out, if isn’t for you, you can open C:\Windows\system32\config and edit the local registry).

Startup Repair

It might be a long shot, but the startup repair option might help. It is the first option on the System Recovery menu.


It is unlikely that your RAM is causing this problem, but it is useful to know that Vista does have a tool to check memory, and it can be accessed through the System Recovery tool. I didn’t know this until today, having previously used memtest+ x86 included on Ubuntu LiveCDs.

Chkdsk / SFC (Updated 2011-07-16)

From the command prompt provided by the System Recovery tool, you can also try running chkdsk /r C: to run a disk check. Running sfc /scannow /offbootdir=c:\ /offwindir=C:\windows should do a verification of ‘critical windows files and components’, but I could not get this to run as it complained about needing to reboot with an active recovery ongoing – I guess it can’t be run via the system recovery tool.

Renaming Event Viewer Log Folder / Prefetch Folder

(See the good post by ubman on technet here)

There are reports that a problem with the event viewer service can cause this black screen on login. To work around this, start up a command prompt through the recovery tool as above. Then execute:

cd \windows\system32\winevt
ren Logs LogsBad
mkdir Logs

Another report claims PreFetch can cause the issue. Now, the folder for PreFetch can be deleted as Windows will recreate its contents as needed. However, should you wish to keep a backup, start p a command prompt as above and run:

cd \windows\
ren Prefetch PrefetchBad
mkdir Prefetch

Other Options

Apologies for the brevity here, these items I quickly jotted down but I am not able to try some of them myself.

Also on technet, zorglub1789 claims broken file permissions were the cause of his woes. Using icacls to fix these apparently worked. He booted to the recovery console and ran:

icacls C:\* /grant builtin\users:(RX) /T

to grant read and execute permissions to all users.

If you can start safe mode, it may be worthwhile temporarily disabling UAC. If the security centre won’t run in safe mode from the control panel, I think it is accessible via the management console. Hold the windows key + R, then type in mmc. I think you may need to add the Group Policy plugin / manager to MMC.

Another file to check on is C:\wialog.txt. This may contain useful information for troubleshooting what is causing the problem.

Again, if safe mode works, msconfig may prove useful. Hold windows key + R, and type msconfig. Then try disabling services, startup options and so forth until you get a working startup. From there you can work back to the cause of the problem. Apparently one to try is “Low Graphics Boot” (or similar), although I don’t know if there is a difference between this and the advanced startup (F8) option.


Basic Command-line Backup

If you have an external hard drive, and want to back up the C:\ drive, the following command will do that from a command prompt (see above for how to get a command prompt).
xcopy /h /i /c /k /e /r /y C: E:\backup

Where E: is the drive letter for your external hard drive.

Reset Administrator or other Windows Passwords

There is a tool at which is very handy for resetting Windows passwords should you not know them. I had to do it in this case as there was no documentation on the default password for this laptop (an Acer), and I can vouch for its utility. Note that you don’t need to know the password for this tool to work.

9 Replies to “Black Screen (KSOD) Vista Solutions”

  1. I know this post is over a year old, but for those who are reading it, chkdsk needs to be specified with a C: (chkdsk /r C:) to run correctly from a cd and sfc requires the /offbootdir=C:\ and /offwindir=C:\windows switches to work correctly from cd.

    The two commands would then be(assuming your windows install is on c):
    chkdsk /r C:
    sfc /scannow /offbootdir=c:\ /offwindir=C:\windows
    P.S. (/r implies /f so /f /r is unnecessary just /r will work fine)

  2. Thanks a lot for giving us this vista black screen problem solution. I am having this problem recently. Your post is really helped me. Dude thanks for allocation 🙂

  3. I was having the Black Screen of Death with mouser pointer and realised through Event Viwer (eventvwr.msc) that the explorer.exe crash was associated to the propsys.dll located in windows\system32 folder.

    So, I managed to emulate a mini WinXP via Hiren’s Boot, loaded a “health” propsys.dll from my other Windows 7 system and overwrote the corrupted one. Problem solved to me!

  4. Thanks for summorizing all this as the only suggestion that is comming from Microsoft is to reinstall windows…

    I’m going to try the rest of the methods that you listed later tonight.

    btw regarding regedit, load hive option is only available when you select HKEY_USERS or HKEY_LOCAL_MACHINE root keys as those are the only places a new hive can be mounted

  5. Hi Robert!

    I know it was a long time ago since you posted this.
    The problem is that i’m experiencing this issue now :/
    Everything started because of this:

    So, the system was destroyed.
    As I’m running a Mac, this is a Windows partition.
    Many issues before this final issue appears happened… I had to rewrite my MBR, BCD etc etc…. 99% of suggested solutions on net were not effective, passed more than 3/4 days and nights asleep researching and studying what to do to solve.
    At the end, I had a success on may things, until stuck now on this thread You talked about.
    Tried all the suggestions here, none effective.
    But I went curious on something, that I found out You were right, and is suggest by Microsoft engineers:

    NOTE: If you try this from the “Repair Windows” option on a Windows Vista install DVD or recovery DVD it won’t work, as that seems to edit the registry on the disc (you will see cmd.exe /k start cmd.exe or similar for the Shell key). For me the “load hive” option was greyed out, if isn’t for you, you can open C:\Windows\system32\config and edit the local registry).

    The question is: How make this work, trying this through the “Repair Windows” option on a Windows Vista install DVD? Isn’t it possible to edit the damaged system registry through this way?



Leave a Reply