It never BSODed.
Some PCs were infected by a rootkit. The
rootkit called into the kernel using absolute
addresses at system startup.
When the patch caused the kernel functions to
shift addresses, the rootkit jumped into the
middle of functions which caused it to BSOD.
It was the rootkit which BSODed, not
the patch and nor the Windows kernel.
If you need to bash Windows or Ed Bott, please
make sure to understand the issues first.
Otherwise you end up looking foolish.
Glad I could help you.
Discussion on:
Message 12 of 1
IBM Sponsored Resources
Resources from our Sponsor
- Oracle Exadata vs IBM: Netezza Compared
- Forrester TEI Report
- CIA Whitepaper
- Harnessing the Power of Advanced Analytics
- Tapping into Unleashed Business Potential with Advanced Analytics
- Unlock Analytic Performance with Revolution R for Enterprise and IBM: Netezza Data Warehouse Appliance
The best of ZDNet, delivered
ZDNet Newsletters
Get the best of ZDNet delivered straight to your inbox




