[KoRn]

It would have been nice if they would post exactly which updates that are causing the problems. So far, we haven’t seen this happen with any of our machines.

[frankenMonkey]

So, Windows 7 upgraded from the ‘Blue Screen of Death’ to the ‘Black Screen of Death’?

[Yo-Yo]

More PC FUD...

</sarc>

[napscoordinator]

Better than the blue screen of death.../sarc.

[DYngbld]

I had a Vista machine do this a few months back, don’t know if it was related to this patch or not. It was a real pain to fix it. I wish I could get everybody in the house to migrate away from MS. I have one of the kids running Linux, I need to get the others to as well.

[Pistolshot]

It’s not the BLACK screen of Death.....it’s just DARK GRAY.

[DannyTN]

For what operating systems?

[listenhillary]

Ping!

Drag your feet on some of those upgrades maybe.

[smokingfrog]

Never heard of Prevx.

If I have it right, it sounds like they had a patch for the ACL vulnerability before Microsoft, and then when Microsoft released a patch for the same thing, it messed up some computers with the Prevx software.

[aMorePerfectUnion]

“We fixed all the problems, trust me.”

- Bill Gates

[Dallas59]

7 still going here. Haven’t any problems yet.

[ShadowAce]

[wbill]

This article doesn't pass the sniff test.

For instance, it doesn't detail which MS patch causes the problem....just one of "15 released on Nov 10th".

And, the only fix is to go to a website of a company that I've never heard of (Prevx) and download an executable that will "patch" my system? And....the only two comments regarding this patch on the Prevx site are from the same person?

Something stinks, here. I'll believe it when I see MS address the issue.

[Rightly Biased]

They should at least sell adspace on it.

[RichardW]

Hmmmm. This has happened to me several times. Very annoying. Necessary to shut down the machine and restart it but it fixes itself when restarted and you won’t lose what you were working on. But it shouldn’t be happening. I thought there was something wrong my laptop.

[w1andsodidwe]

Happened to one of my salesmen on his home computer running Vista.

[RJS1950]

Really? How come I haven’t seen this on any of my three up-to-date PCs at home or any of the hundreds here at work? I have observed little to no issues with Vista and XP gave me few if any problems. Yes, at home and at work these machines are power user machines so they take a beating.

The small number of Apple confusers we have and the actual and virtual Linux installs have infinitely more problems.

[rahbert]

If the app is running in user space and not in kernel mode,
and causes Windows to blue screen with non-priveleged code
then I would say that is a Windows problem. However over the years former MS devs leave with knowlege of the kernel
mode APIs and incorporate hacks into products.

I know this because I worked at such a company in the misty past. One could determine the owner of the problem
by simply enabling the crash dump feature, repeat the crash, then look at the dumpfile with WinDBG (free from the MS Download site). Look for a .sys file name at the head of the last stack frame.

99.9% of these BSOD events are driver-generated. HW drivers
must run in kernel space, and any generated exception will bring Windows crashing down (excepting some video rivers with recovery features).

Lots of older HW do not have Win7 drivers available. Win7
should know to exclude drivers not signed for Win7
(and no Win7 is not XP with lipstick - it differs fundamentally)

[Vinnie]

The Black Death! Haven’t seen that in what, 500 years?
We’re regressing

[PubliusMM]

Ping