Submission + - SPAM: Windows Update/Defender BSOD's HP Desktops
xmas2003 writes: For Thanksgiving Black Friday, I bought this nifty HP Desktop. It has worked great since then ... until a couple of weeks ago ... when it started spontaneous Blue Screens of Death with a KMODE_EXCEPTION_NOT_HANDLED error. After some WTF is going on, I stumbled across this (growing fast) 25+ page thread on the HP support forums — a LOT of people are having the same PIA problem.
The posters have done some great research and since the Internet is not awash with BSOD reports from other vendors, this appears to be particular to (a broad range of AMD/Intel) HP Desktops. While HP has failed to chime in (HELLO!), other posters report that HP has told them it is a Microsoft problem. But all indications are this is brand specific and some sort of weird interaction that is related to Windows Defender.
Disabling Windows Defender seems to stop the BSOD's, but this is not easy to do because the machine can get into a BSOD reboot loop and you have to get into the recovery console to do some manual registry entries — see post #47 from Salty Lager — which is not something the average Joe User will know to do. So for the majority of owners, their machines are currently worthless. And even when a fix is available, they'll have great difficulty applying it.
This highlights several things. Software is complex — what could be specific about HP Desktops that would cause this BSOD? Also, it's cool how some technically astute end users can troubleshoot the problem and share their findings for others. Finally, the lack of customer communication is pathetic as the silence from HP/Microsoft is deafening ... so it's unknown if they even recognize there is a problem, much less working on it.
The posters have done some great research and since the Internet is not awash with BSOD reports from other vendors, this appears to be particular to (a broad range of AMD/Intel) HP Desktops. While HP has failed to chime in (HELLO!), other posters report that HP has told them it is a Microsoft problem. But all indications are this is brand specific and some sort of weird interaction that is related to Windows Defender.
Disabling Windows Defender seems to stop the BSOD's, but this is not easy to do because the machine can get into a BSOD reboot loop and you have to get into the recovery console to do some manual registry entries — see post #47 from Salty Lager — which is not something the average Joe User will know to do. So for the majority of owners, their machines are currently worthless. And even when a fix is available, they'll have great difficulty applying it.
This highlights several things. Software is complex — what could be specific about HP Desktops that would cause this BSOD? Also, it's cool how some technically astute end users can troubleshoot the problem and share their findings for others. Finally, the lack of customer communication is pathetic as the silence from HP/Microsoft is deafening