Hi, few things to go through here.
Two attached dumps are of the FE: BUGCODE_USB_DRIVER bugcheck - The first paramter is 0x5, as we can see here:
Right off the bat, FE bugcheck usual causes are: USB hardware (motherboard or attachments) or the USB device driver has a bug. We can possibly rule out the chipset or USB drivers themselves being the issue as you've already navigated to Lenovo's website and ensured you had the latest drivers. We can also rule out any devices connected via USB as the only device you have connected is the M & K, correct? Do you normally attach any other device via USB, or have you previously at a time?
Ultimately, usbehci.sys is the culprit, which is a Windows component / driver. Something else, whether it's a device or driver (or hardware), is faulting it.
You can give disabling and re-enabling the USB controller(s) in DevMan a try, this will allow the drivers to recover the controller(s) from their unresponsive state. The USB controllers represent the USB ports in DevMan:
start > search > device manager
As the usual cases state as well, it's possible this is a board issue as well, or even a hub / port issue. It's not uncommon for a port to give out, it's happened on previous systems I have owned. It happens sometimes over time. Are there any other USB ports you can try and connect your devices to, to rule out a specific port issue?
Drivers that need to be updated:
Regards,
Patrick
Two attached dumps are of the FE: BUGCODE_USB_DRIVER bugcheck - The first paramter is 0x5, as we can see here:
Code:
Arg1: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS [B]The host controller is
using a physical memory address that was not allocated by
the USBport driver.[/B]Right off the bat, FE bugcheck usual causes are: USB hardware (motherboard or attachments) or the USB device driver has a bug. We can possibly rule out the chipset or USB drivers themselves being the issue as you've already navigated to Lenovo's website and ensured you had the latest drivers. We can also rule out any devices connected via USB as the only device you have connected is the M & K, correct? Do you normally attach any other device via USB, or have you previously at a time?
Ultimately, usbehci.sys is the culprit, which is a Windows component / driver. Something else, whether it's a device or driver (or hardware), is faulting it.
You can give disabling and re-enabling the USB controller(s) in DevMan a try, this will allow the drivers to recover the controller(s) from their unresponsive state. The USB controllers represent the USB ports in DevMan:
start > search > device manager
As the usual cases state as well, it's possible this is a board issue as well, or even a hub / port issue. It's not uncommon for a port to give out, it's happened on previous systems I have owned. It happens sometimes over time. Are there any other USB ports you can try and connect your devices to, to rule out a specific port issue?
Drivers that need to be updated:
Regards,
Patrick