gosh Posted August 5, 2010 Share Posted August 5, 2010 Anyone else have this problem? Since installing the critical windows update on tuesday, every couple mins i get a message that a usb device is not detected. And yet, all my usb devices work fine. Ive tried reconnecting my usb devices. Device manager is fine. No errors in event viewer. I got a blue screen this morning in usbstor.systhe update is http://support.microsoft.com/kb/2286198Im using windows xp sp2 x64Anyone else see this?Error code 00000000000000d1, parameter1 0000000000000000, parameter2 0000000000000002, parameter3 0000000000000001, parameter4 fffffadebfc9cf68. Link to comment Share on other sites More sharing options...
user_hidden Posted August 5, 2010 Share Posted August 5, 2010 I have not nor have any users of my update pack for XP-SP3(x86) experience any issues with KB2289168.As for x64 perhaps 5eraph can shed some more light as he deals with that OS version. Link to comment Share on other sites More sharing options...
cluberti Posted August 5, 2010 Share Posted August 5, 2010 Can't say I'm seeing it on two machines, but that's only two. Perhaps you can get a complete dump the next time it crashes out? Link to comment Share on other sites More sharing options...
MagicAndre1981 Posted August 5, 2010 Share Posted August 5, 2010 the update changes the Shell32.dll (usermode code), so the crash must have other causes. Link to comment Share on other sites More sharing options...
johnhc Posted August 5, 2010 Share Posted August 5, 2010 (edited) Anyone else have this problem? Since installing the critical windows update on tuesday, every couple mins i get a message that a usb device is not detected. And yet, all my usb devices work fine. Ive tried reconnecting my usb devices. Device manager is fine. No errors in event viewer. I got a blue screen this morning in usbstor.systhe update is http://support.microsoft.com/kb/2286198Im using windows xp sp2 x64Anyone else see this?Error code 00000000000000d1, parameter1 0000000000000000, parameter2 0000000000000002, parameter3 0000000000000001, parameter4 fffffadebfc9cf68.gosh, Google gets lots of hits on a BSOD with this KB, but I found none for Stop 0D1. If you are running ESET NOD32, then some hits say be sure it is updated. I also run XP x64 but will refrain from installing this update till I feel better about it. Enjoy, John.EDIT: Found this many times in my searching. Many are having problems with this update.For home users, no-charge support is available by calling 1-866-PCSAFETY (1-866-727-2338; and/or 1-866-234-6020 and/or 1-800-936-5700) in the United States and in Canada Edited August 5, 2010 by johnhc Link to comment Share on other sites More sharing options...
Guest Posted August 6, 2010 Share Posted August 6, 2010 I wonder if this is similar to the issue with KB977165 in February:This problem [with KB977165] may be caused by a conflict between the security update and malware that is resident on the system. This problem is not a quality issue with the security update, and the issue is not specific to any OEM.I've had no problems with KB2286198, either on my own XP x64 machine or in VM when testing my update pack. Admittedly, I don't have many USB devices. But attaching my 2GB USB thumb drive causes no problems. The other USB devices on my machine are a Razer Lycosa keyboard, Logitech G9 Laser mouse and an XBox 360 controller. Link to comment Share on other sites More sharing options...
johnhc Posted August 6, 2010 Share Posted August 6, 2010 I installed the KB this morning and all seems to be OK. I have tried a USB stick and my USB printer and am still running just fine. Enjoy, John. Link to comment Share on other sites More sharing options...
ITPhoenix Posted August 9, 2010 Share Posted August 9, 2010 System restore and then reinstall update. Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now