Welcome guest. Before posting on our computer help forum, you must register. Click here it's easy and free.

Author Topic: Black Screen of Death after recent Microsoft updates  (Read 6244 times)

0 Members and 1 Guest are viewing this topic.

02bin3

  • Guest
Black Screen of Death after recent Microsoft updates
« on: November 30, 2009, 08:02:53 PM »
If any of you experienced, as I did, the Black Screen of Death after Microsoft's recent automatic updates, this article that I ran across today may help you get your computer up and running again.  It was a little late for me because I ended up buying a new computer that I apparently REALLY didn't need after reading this article.  Anyway, for those of you that might be helped, you can read this article and try their fix.

http://www.computerworld.com/s/article/9141568/Latest_Microsoft_patches_cause_black_screen_of_death

rthompson80819



    Specialist

    Thanked: 94
  • Experience: Experienced
  • OS: Windows 7
Re: Black Screen of Death after recent Microsoft updates
« Reply #1 on: November 30, 2009, 08:33:35 PM »
I guess MS wanted to keep the acronym the same (BSOD) but they should have used some creativity and created something new and created the red screen of death, or the green screen of death.

BC_Programmer


    Mastermind
  • Typing is no substitute for thinking.
  • Thanked: 1140
    • Yes
    • Yes
    • BC-Programming.com
  • Certifications: List
  • Computer: Specs
  • Experience: Beginner
  • OS: Windows 11
Re: Black Screen of Death after recent Microsoft updates
« Reply #2 on: December 01, 2009, 03:38:47 AM »
"BSOD" was coined by people working with the computers. the real name is called a "STOP" error.

a "Black screen of death" is completely meaningless. One could simply call a computer where one has forgotten to turn the monitor on by that moniker.

But, anyway.


As usual, their technical staff are apparently on vacation.

Quote
Prevx was alerted to the problem by users of its security software last week, Morris said. Microsoft apparently made changes to the Access Control List (ACL), a list of permissions for a logged-on user. The ACL interacts with registry keys, creating visible desktop features such as a sidebar.

Access Control Lists are a feature of the NTFS file system and apply to files, not users. each user is identified by a Security Token, or SID. Access Control Lists likely reference specific user SIDs as well as the generic SIDs for such things as the everything group and "backup operators" and so forth.

Registry keys also have Permissions settings as well- this is likely what is being referred to. Although being that the Access Control List is therefore stored in the registry it doesn't really interact with anything. This is one of my pet peeves, "technical" journals saying that data is interacting with anything. That simply doesn't happen; programs interact. Data is simply presented in some way which may or may not be interactive. The Sidebar is created by sidebar.exe, they are instead referring to the ACL of the registry keys that sidebar accesses as having incorrect permissions settings causing sidebar to not function. the data does not create the sidebar. the sidebar uses the data to determine what will be shown IN the sidebar.

Aside from their completely incorrect technical representation of the problem though, I really have nothing to complain about it.
I was trying to dereference Null Pointers before it was cool.