Black Screen woes

Are you really this thick, The Updates are what triggered it. I'm not saying they are directly what caused it but those updates are what triggered it. Anyways this is going nowhere so Ill just stop with this post.

 

I know of at least three people using Eset AV who had the problem almost immediately after their first reboot after installing the last set of MS updates - all were using Vista so how people can say it is not connected to the updates I do not know

 

Vista 32bit here.
After updates I had weirdness, not black screen.
Like another poster I had judder with card games (dealing)
Windows animation juddered.

I applied the reg 'fix' (repointed explorer.exe) turned off animation and it is a lot better.

 

Like Microsoft says, "My lawyers are bigger than your lawyers". Still lack explanations that fit the observations of those affected by it immediately after the updates. Like me. Hope investigation will continue rather than simply burying it. In the meantime, will start making an extra incremental image just prior to installing new Windows updates.

 

Good practice, that. And I used to create those images, each and every time, but the overall good quality of MS Critical Updates must have lulled me into complacency. I'll take this as a reminder to start imaging my HD again before applying MS Updates.

 

I actually had an image from the previous Saturday, so not really too much makeup. And had run MBAM and SAS the next day, and was running latest Prevx, Avast!5, OA with Opera Run Safer lowered privileges at the time of the updates. Next boot after the update boot, though, saw nothing but a black screen with a running copy of Windows Explorer in the center of it. Never saw the mysterious virus that no one can detect. Was a bit surprised that a restore wasn't good enough, but I guess that's one reason we do imaging.

 

The one virus that will never be detected..... Microsoft. You just thought those system updates were meant to help you!

 

You may also enjoy the thread at http://www.dslreports.com/forum/r23...Nov-10-patches-causing-BSOD-problems~start=20 that actually has an "official" response from a Microsoft representative.

 

And where in the article, pray tell, does it say what you claim it does?

Your posts are simply baseless attempts, biased by passion, to imply that the blame somehow lies with Microsoft. And THAT is why this is going nowhere. And just to refresh your memory:

 

So who's problem is it? M$ of course but I'm glad Prevx made and showed us how to fix the problem!

IMHO

TH

 

You "claim" someone else is thick, a complete personal attack, and now you come up with something, well let's say, "dull", as this statement? Are you serious?

It's already obvious that this is Prevx's fault for claiming something that doesn't exist, without the proper research, they obviously do not have the manpower that Microsoft do to properly research these things, and should review their blogs and research in future far more thoroughly.

Completely correct in my opinion, it seems Prevx aren't the only people that need to "think before commenting".

 

/faceplam.

 

Some update articles: http://redmondmag.com/articles/2009/12/04/...-a-mystery.aspx

Black Screen Of Death Hits 50,000 PCs says Prevx as they download there fix tool http://www.informationweek.com/news/window...cleID=222000502

TH

 

As I understand it... ..., BSOD's are different from the black screen issue being discussed here, a BSOD is a Blue Screen of Death which indicates a system crash.

Black screens are primarily caused by video drivers or something delaying the video drivers from loading because to start the system shell (explorer.exe) with Aero (transparency) enabled (in Vista), the DWM process (Desktop Window Manager) needs to be running, and requires the VGA drivers to be loaded to start.

If I am wrong, I hope somebody will correct me.....

 

I cannot say you are wrong, but what has that event string to do with WinXP
The one common thing is however explorer.exe