My two week old computer went down early this afternoon. I've been working all day to fix it with no luck, I'd really appreciate any help or advice that you can offer.

I'll also mention that I am seeing tons of pages on this issue when I search, but none of the fixes I've found so far have done the trick. I have an OEM Windows license so unfortunately contacting MS will be fairly costly at this point.

The window load screen appears as normal and then my screen goes completely blank except for a white mouse pointer. The mouse pointer moves as normal but clicks / key combos / etc do nothing.

It is a new system so there have been a lot of new program installs and changes recently, however I have been too distracted by Dragon Age to have done much since the last restart.

Known changes since the last restart- Joined system to home network
Installed a Saitek joystick
Installed daemon tools immediately proceeding the crash

I can't find any similar issues related specific to either product so I assume that this is a general windows install issue, or a registry corruption that occurred during one of the installs.

Steps taken so far-

  1. Attempted to boot to safe mode & safe mode w/ cmd prompt - Same result
  2. Tried ctrl-shift-tab // ctrl-alt-delete // shift *5 - no results
  3. Attempted to boot to Low res mode - Same result
  4. Removed secondary monitor and peripherals
  5. Ran diagnostics on Memory & Hard drive - Tested Ok
  6. Ran system restore / System repair from disk
  7. Checked that Reg key @ HKEY_LOCAL_MACHINE\MySYSTEM \ControlSet00X\Services\RpcSs is set to NT AUTHORITY\NetworkService
  8. Underclocked RAM - Just in case
  9. Used RegEdit > load to get access to log files - temporally moved them
    1. Tried to view events in system32\winevt\logs\ but I can only work with command prompt / note pad so the contents are pretty garbled.
    2. Swore at computer / threatened computer - Swore at computer while threatening it

I can access command prompt using my windows disk - but i can't seem to do much as most of the system tools use dependencies that aren't loaded yet.

I am completely at a loss - Any help you can give would be greatly appreciated. The system is less than two weeks old and has been rock solid up until this point. My husband is running a system with identical hardware / OS, and has not experienced any issues to date.

Obviously I can't rule too much out at this point but I'll also mention that this is a fairly low risk computer as far as malware goes. Less than two weeks since the last install - OS / AV always up to date - no file-sharing or pirated apps.

System specs

  • OS: Windows 7 pro 64bit- Version: 61.7600.
  • AV: Nod-32

  • Radeon HD5770 Sapphire video card

  • Core I7-860
  • Gigabyte P55-UD4P Motherboard
  • 4GB Ram : 2 X 2GB 240-PIN DIMM 256Mx64 DDR3PC3 -10600 Unbuff


Edit: Sorry for the lack of updates on this. I'm a bit afraid of reboots seeing that they haven't been going well for me. The problem has been reoccurring with pretty much every reboot although leaving the system off for a while solves the issue regardless of what I leave plugged in.

I removed and reseated the video card yesterday which immediately let me boot. I've done one reboot since and it actually worked although I haven't had the courage to try it again. I will keep updating as I know whether this worked or not.

Thanks again for all of the help- I can't tell you how much I appreciate it.

  • After working until four in the morning last night trying to get this resolved I finally shut down and went to bed. This morning the damn thing is working fine. I shut down for 10 minutes or so at a time last night just in case but apparently that wasn't long enough. I also did that before I unplugged the secondary monitor but I'm not sure why that would make a difference. Thank you to everyone who posted an answer last night. I guess this is pointing to a hardware issue but I'm at a complete loss as to what that could be. Continuing to look into it so I can restart again without fear. – user20389 Dec 6 '09 at 16:18
  • 3
    Did you try shouting/ swearing while it is both turned on and off? – Jonno_FTW Dec 9 '09 at 14:08
  • I've seen Saitek drivers do bad things, so that could be a cause there too. – Broam Dec 9 '09 at 17:40
  • @Jonno_FTW - heh, yes I did. I also swore at it during every stage of the boot process. I even came up with a few new swearwords but to no avail. – user20389 Dec 13 '09 at 19:44

This Lifehacker article (probably) covers the issue which you are facing. The article gives a link to a fix. But yeah, the whole issue is a little confused at the moment.

the cause of this recent crop of Black Screen appears to be a change in the Windows Operating Systems lock down of registry keys.


According to the Microsoft Security Response Center, Microsoft hasn't released any updates that could have caused the Black Screen problem described by Prevx, so if you're experiencing this problem, it's very unlikely that it was caused by a Microsoft update.

The fix is to (via task manager- new task)

"C:\Program Files\Internet Explorer\iexplore.exe" "http://info.prevx.com/download.asp?GRAB=BLACKSCREENFIX"

| improve this answer | |

Daemon tools installs a device driver, in order to run images as virtual drives. An incompatible device driver would lead to a crash.

Although the latest version has support for Windows 7, the question is if it has support for x64, or if you are using the latest version (4.35.5).


Edit: It seems to have support for x64:


| improve this answer | |

Last night after updating a Intel Driver from Windows Update I had something like this happening. POST would pass but after the little Windows Logo all I would get was a black screen.

All I did was restarted my computer and clicked F8. Selected Repair my computer and did a system restore from 3 days.. The one that it created that day before installing didn’t work and neither the one from the day before.

I have Win7 64Bit..

| improve this answer | |
  • I left my system off overnight with the secondary monitor disconnected, when I started it up this morning it worked. More details in my edit above, and I'll let you know if I find a solid fix. Good luck. – user20389 Dec 6 '09 at 17:32

Regarding your Fix... Perhaps the first time you rebooted the Joystick was connected to a USB port. It probably isn't a failed driver, since you're getting the mouse, which is past the when the drivers get loaded. I would say windows was installing your joystick, perhaps - unless it wasn't plugged in on startup.

PS - decent system, you got there.

| improve this answer | |
  • I'll have to pay attention to that on the next reboot- I've been focusing on the video card so I didn't really note whether it was hooked up on the last reboot that succeeded. Good idea! – user20389 Dec 13 '09 at 19:41

(OS: Win7 x64 - Event 4 - black-screen-of-death - Daemon Tools/sptd installed - Saitek keyboard & mouse)

I had the great pleasure to experience that very problem after an update of Saitek Keyboard/Mouse drivers through Windows Update [NEW RULE (#34): Never do such a thing, always use constructor files from their websites] , and let me tell you that I was beginning to lose my computer "latin" (as I'm a computer engineer...) and all the related comments on the net weren't of a nature to relieve the stress...

I tried system restorations on the last operations (but there was nothing detected as modified in those, so... nothing to restore either) and it didn't work.

As a lot of posts refered to Daemon Tools and sptd.sys driver (I also had the event 4 on it), I did uninstall/deactivate those two, without any more success.

Finally, it's a simple 'Use last-known good configuration' in Safe-Mode menu options (F8 on reboot) that did the trick and everything came up fine again.

I'm gonna finish this with Saitek drivers files installation and make sure everything works fine after that.

I'll keep you up if anything else goes wrong.

Hope that'll help and relieve someone :) Scalino

| improve this answer | |

I had this issue as well with my laptop when I installed 7. In the end it turned out to be that Win7 had improperly identified my video card and installed incorrect drivers for it. When I manually installed a correct driver, the issue stopped.

| improve this answer | |

I had this problem after my windows 7 did an automated update last night, today I had no luck login in, I then restored the computer to the state before this update and the issue is now resolved, turning off windows auto updater for now untill a proper resolution is found.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.