XP users alert re BSODs

[waking]

>There was one update a couple of years ago (KB916595) that killed my computer ...
>I'm concerned that patch will be included in SP-3.

It is included, according to this:

List of fixes that are included in Windows XP Service Pack 3
http://support.microsoft.com/kb/946480

[Marc57]

Windows XP with Service Pack 2. This XP version is no longer supported as of July 13, 2010. Microsoft recommends that users upgrade to Service Pack 3 (SP3) or to Windows 7


http://windowsitpro.com/windowspaulthurrott/article/articleid/103556/microsoft-warns-of-windows-version-expirations.html

[YoKenny]

The KB916595 item refers to Stop error message on a Windows XP-based computer: "STOP 0x000000D1" from  June 6, 2006

STOP 0x000000D1(parameter1, parameter2, parameter3, parameter4)
DRIVER_IRQL_NOT_LESS_OR_EQUAL

HTTP.SYS

http://support.microsoft.com/kb/916595

Means that you have not kept your device drivers up to date.

Windows XP Stop Messages
http://www.updatexp.com/stop-messages.html

That was one of the first problems I had with XP that caused BSOD's for me so I learned to make sure I install the latest device drivers from my system manufacturer.

[sunrisecc]

Additional info?

Rootkit blamed for Blue Screen patch update snafu

http://www.theregister.co.uk/2010/02/15/rootkit_blue_screen_culprit_probably/

[Rick F]

YoKenny wrote: That was one of the first problems I had with XP that caused BSOD's for me so I learned to make sure I install the latest device drivers from my system manufacturer.

Interesting. I spent months trying to figure out why my PC would sometimes give me a BSOD.  It was always my modem (Conexant D850 - 56K).  I'd go looking for the lastest driver... even with DELL's help, and no matter what verion drives was installed, it always showed up as driver 7.6.0.50 dated 1/7/2004.  Finally, I just disabled the modem driver so I no longer get BSODs. (I'm not on dial-up).  When I need to send a fax, I re-enable the modem, send the fax, then disable again.

Thanks guys.  Boy, this is really getting off topic though.

[Rick F]

YoKenny wrote: That was one of the first problems I had with XP that caused BSOD's for me so I learned to make sure I install the latest device drivers from my system manufacturer.

Interesting. I spent months trying to figure out why my PC would sometimes give me a BSOD.  It was always my modem (Conexant D850 - 56K).  I'd go looking for the lastest driver... even with DELL's help, and no matter what verion drives was installed, it always showed up as driver 7.6.0.50 dated 1/7/2004 installed.  Finally, I just disabled the modem driver so I no longer get BSODs. (I'm not on dial-up).  When I need to send a fax, I re-enable the modem, send the fax, then disable again.

Thanks guys.  Boy, this is really getting off topic though.

[YoKenny]

@ Rick F

Old dial-up modems where the bain of my existence back then as the makers never kept the drivers updated so I removed the adapter if the system did not need it or purchased a new one if really needed.

The Zoom Model 3035 - PCI Express V.92 can be purchased for as low as $25.00:
http://www.zoom.com/products/dial_up_internal.html

I use my Brother MFC-240C All-In-One to send and receive FAXes.

Its not off topic if the Conexant D850 - 56K modem is causing BSODs though.

[Marc57]

Hackers "fix" XP BSoD rootkit


Good news is that TDL3 authors care about us and they released in a couple hours a new updated version of the rootkit compatible with the Microsoft patch

http://blogs.zdnet.com/hardware/?p=7349&tag=nl.e550


Isn't it nice these Hackers "care" about us?   

[YoKenny]

Update - Restart Issues After Installing MS10-015 and the Alureon Rootkit
Hi,
We wanted to provide you with an update on our ongoing investigation into the “blue screen” issues affecting a limited number of customers who installed MS10-015.  We have been working around the clock with our customers, partners and several teams at Microsoft to determine the cause of these issues.  Our investigation has concluded that the reboot occurs because the system is infected with malware, specifically the Alureon rootkit.  We were able to reach this conclusion after the comprehensive analysis of memory dumps obtained from multiple customer machines and extensive testing against third party applications and software.  The restarts are the result of modifications the Alureon rootkit makes to Windows Kernel binaries, which places these systems in an unstable state.  In every investigated incident, we have not found quality issues with security update MS10-015.  Our guidance remains the same: customers should continue to deploy this month’s security updates and make sure their systems are up-to-date with the latest anti-virus software.
 

http://blogs.technet.com/msrc/archive/2010/02/17/update-restart-issues-after-installing-ms10-015-and-the-alureon-rootkit.aspx

[sunrisecc]

Now the question is - does Avast 5 find the Alureon rootkit?