usbport.sys problems xp pro

[gghartman]

about once a week i am getting a bsod on the usbport.sys with the following info.

stop: 0x0000008e (0xc0000005,0xf7e99cff,0xf410b9c0,0x00000000)
usbport.sys - address f7e99cff base at f7e92000, date stamp 41107d62

i am totally baffelled about this. have xp pro sp2 with all current updates. the board manufacturer says a microsoft problem. the version of my usbport.sys in system32/drivers is 5.1.2600.2180.

have run 3 different diags programs on memory, h.d., board, cpu everything and nothing comes back as a problem. have run these tests in multiple loops.

driving me nuts could anyone please have a answer.

thanks. greg

[macko72]

0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED

A kernel mode program generated an exception which the error handler didn’t catch. These are nearly always hardware compatibility issues (which sometimes means a driver issue or a need for a BIOS upgrade).


Faulty device driver or system service. In addition, a faulty device driver or system service might be responsible for this error. Hardware issues, such as BIOS incompatibilities, memory conflicts, and IRQ conflicts can also generate this error.

If a driver is listed by name within the bug check message, disable or remove that driver. Disable or remove any drivers or services that were recently added. If the error occurs during the startup sequence and the system partition is formatted with NTFS file system, you might be able to use Safe Mode to rename or delete the faulty driver. If the driver is used as part of the system startup process in Safe Mode, you need to start the computer by using the Recovery Console to access the file.

http://www.usb-drivers.com/drivers/240/240747.htm

http://aumha.org/win5/kbestop.php

[gghartman]

the driver from the link you sent me is newer than my usbport.sys so will try installing that and see what happens.

i assume all i need to do is copy file to system32/driver folder - true not true ?

thanks.

p.s. logs mentions mrtrate service failed to start - file not found. not sure what that means but only error in system log at the time of bsod.