Link to home
Start Free TrialLog in
Avatar of bwask
bwaskFlag for United States of America

asked on

USBPORT.SYS causes XP system to fall into a reboot cycle

Hello,

October 8th Microsoft released update Kb2862330:
https://support.microsoft.com/kb/2862330

This security update installs a newer version of usbport.sys file into the "\windows\system32\drivers" folder, and forces a reboot. Every XP system on my network with XP that ran the update (about 100) went into a reboot loop. Safe mode, or any other options available at F8 would not get me to the drive. I had to pull all the drives hook them up to a system with a USB sled and copy the older version of the file back on to the system.

My guess is the new driver is stepping on memory of another file or vice versa. So, it would seem that I may have some old files and some new ones, as I read it may be due to the way my loads were created on my older Microsoft RIS server.

When we first started making loads on the RIS server we used an XP with SP2 OS disk. As time went on SP3 was released and we started loading it on our new installs. I had this same problem with SP3 rebooting the machines due to usbport.sys, but the fix I found on one of the Microsoft Forums was just to copy the older file back in. So I scripted my SP3 install to do just that and all was fine.

I read an article that only briefly touched on this particular scenario. If you are doing your base install from an XP SP2 disk but your load on the server have been upgraded to SP3, you can get a mixture of driver files.

Is this true?
If so, can I fix it?

Right now I have my critical and security updates disable on all XP systems (200+ across 5 locations.)

Thanks for any help
Eric
SOLUTION
Avatar of ded9
ded9
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of bwask

ASKER

"On a test system install the latest chipset drivers from manufacture website after installing the update. Monitor the system."

I can not get to the system after the update is installed, No safe mode, no safe mode with network support, not even a command prompt, it reboots shortly after post, forever.  This doesn't happen intermittently, it happens on every XP system in our environment as soon as the usbport.sys driver is installed.
After you install the update don't restart the system. Install the latest chipset drivers and then reboot.

Or

First install the latest chipset drivers and then install the update
Avatar of bwask

ASKER

Deb,

I will try this, but I think this is most unlikely. We have many different Chipsets, some current and some that our older versions. However, this will happen on any XP machine I install it on company wide, "Any XP Machine." If it were a chipset problem, I think we'd see a whole lot more personal/business users having problems than just my network.

However, I will give it a try.
1) First create a system restore point.
2) Install latest chipset or usb drivers.
3) Enable the verifier command
4) Install the update

If the issue reoccurs then boot the system in recovery console and uninstall the update. No need to slave the hard drive.

http://windowsxp.mvps.org/spuninst.htm

Upload the new dmp file for analysis.



Ded9
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of bwask

ASKER

Georg49, you can't use the SP3 usbport.sys file, you need to take it back to the SP2 usbport.sys version. If you just drop that file in, the system will come up fine and you can do the other fixes, no need to uninstall KB2862330 which has caused us so much trouble. I did notice on a couple of instances however, that it would reboot a couple of times before it went into windows, and on a couple of occasions for some reason I had to copy the file twice.
Avatar of bwask

ASKER

My comment was more thorough in it's explanation of the fix, as well as fleshing out the whole problem, and why it seems to have taken place in the first place in my particular environment.