Windows 7: BSOD crash usbport.sys suspected, please help with dump file analysis

Attachment 211554Attachment 211555I have an Asus G53JW notebook that has BSOD failures.
Tried updating all drivers with Driver Reviver, run memtest86+ to check ram and checked disk with SeaTools for Windows but no faults so far.
The notebook has no USB devices connected externally when the BSOD occurs, on most occasions the BSOD occurs when the G53 is doing very little.

Below is a report from Who Crashed software and it repeated states the BSOD was caused by usbport.sys (USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x18A).
I am currently checking usbport.sys using verifier.exe.

I'm not really sure where to go from here, could someone who is good with Windows 7 dump files offer an opinion. Is there a possibility that this is a hardware fault? Asus Support have been less than useful.

John

System Information (local)
computer name: 3DPC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7 CPU Q 740 @ 1.73GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 6363312128 total
VM: 2147352576, free: 1957240832


Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump



Crash dumps are enabled on your computer.


On Sun 13/05/2012 8:34:49 AM your computer crashed
crash dump file: C:\Windows\Minidump\051312-53071-01.dmp
uptime: 00:40:03
This was probably caused by the following module: usbport.sys (USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x18A)
Bugcheck code: 0xFE (0x5, 0xFFFFFA80092761A0, 0x80863B3C, 0xFFFFFA800A87B258)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sun 13/05/2012 8:34:49 AM your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 00:40:03
This was probably caused by the following module: usbport.sys (USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x18A)
Bugcheck code: 0xFE (0x5, 0xFFFFFA80092761A0, 0x80863B3C, 0xFFFFFA800A87B258)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Mon 7/05/2012 8:35:25 AM your computer crashed
crash dump file: C:\Windows\Minidump\050712-36395-01.dmp
uptime: 02:13:18
This was probably caused by the following module: usbport.sys (USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x18A)
Bugcheck code: 0xFE (0x5, 0xFFFFFA8008D5E1A0, 0x80863B3C, 0xFFFFFA800A527C48)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Thu 26/04/2012 4:35:42 PM your computer crashed
crash dump file: C:\Windows\Minidump\042612-20514-01.dmp
uptime: 00:07:08
This was probably caused by the following module: usbport.sys (USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x18A)
Bugcheck code: 0xFE (0x5, 0xFFFFFA8008DD91A0, 0x80863B3C, 0xFFFFFA800A4FA258)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Tue 24/04/2012 1:19:35 PM your computer crashed
crash dump file: C:\Windows\Minidump\042412-17456-01.dmp
uptime: 03:20:47
This was probably caused by the following module: usbhub.sys (usbhub!UsbhHubProcessChangeWorker+0xEC)
Bugcheck code: 0xFE (0x8, 0x6, 0xB, 0xFFFFFA8009F5EB20)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbhub.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Default Hub Driver for USB
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


Conclusion
5 crash dumps have been found and analyzed.

Start by running sfc /verifyonly from and elevated command prompt (Run as Administrator). Report back with any messages.

Then attach the dump files to your next post. (Follow the directions at the top of the page.)
http://www.sevenforums.com/crashes-d...tructions.html

Just run sfc /verifyonly.
The output of sfc indicated "Windows Resource Protection did not find any integrity violations"

Sorry about not including attachments previously, thought I had, must of screwed it up.
The attachments should now be available as part of the original posting.

John

It appears to be a USB hub malfunction but the last dump provides a clue that the others didn't. That dump suggests the hub didn't resume after a selective suspend. This is also hardware and sometimes caused by a faulty BIOS but lets check to see what you have set for Power Settings first.

Open Power Options from the Control Panel. For the plan you've chosen (filled button), click on Change plan settings to the right. In the next window click on Change advanced power settings. In the pop-up, expand all the USB levels until you get to Settings. Set this to Disable for the time being. Click Apply, OK, Save Changes then close CP. Reboot then let the laptop idle or do remedial tasks for while and see if you get another BSOD.

If you don't get a BSOD, check to see if there's a BIOS update for your laptop (notebook). Your current BIOS version is G53JW.211, 28/01/2011. Well, check for an update whether you get a BSOD or not. You may want to change the power setting back after a BIOS update. The suspend doesn't really save much power unless you have something connected; And that doesn't make much sense anyway.

Just realized something else but follow the above first.

I checked the Asus web site again and Bios 211 appears to be the latest release.
I'm not really sure whether the BSODs started soon after the last Bios update was installed but it is likely.
Asus Support advised to jump into Bios and select optimised defaults, if that did not stop the BSOD then the G53 required repair via an Asus approved service agent.
Big problem is that I am never sure if this answer came off a flow chart of "maybe" solutions or derived from informed experience. Asus Support did not request the Windows 7 dump files to analyse.

I've adjusted the USB settings for the Balanced power management option, the USB suspend settings for plugin and battery are now set to false. USB on the G53 is mainly used for external drives used during backup.
I have noticed that the USB connectors on the G53 are noisy. If you move the connectors slightly when the disk drive is connected you can clearly see the drive power off. Move again and the power connection is restored. I was going to apply contact cleaner spray assuming gunk on the contacts. The problem seems to affect all four USB connectors spread 2 x 2 on either side of the chasis.

Verifier.exe is still running and targeting usbport.sys. Nothing indicated so far. Might discontinue.

John

Version 211
Description BIOS 211
Firmware change File Size 1,2 (MBytes) 2011.03.28 update Download from Global (DLM) Global

Version 210
Description BIOS 210
Update USB3.0 File Size 1,2 (MBytes) 2010.12.31 update Download from Global (DLM) Global


Version 209
Description BIOS 209
First release File Size 1,2 (MBytes) 2010.10.27 update Download from Global (DLM) Global

I wouldn't attempt a BIOS roll-back. Those can be tricky. It sounds like a loose port or a cable. If you can, try another cable. If a device can't respond to a signal, it will certainly cause a driver to time out. If I recall correctly (it's been more than five minutes since I looked at the dumps), the bug code is hardware related. If the port is loose, there's no amount of software updates that will fix that. It could be that ASUS is aware of a common problem and needs the unit to repair it. This sounds like a hardware issue--As in a loose port(s). Or it could be they don't have the time for individual diagnostics as we do here.

But... changing to a different port and having the same problem sure implicates the cable.

Thanks for all your help.
Looks like I'm looking for an Asus Service Agent somewhere in Sydney Australia, changed USB cables several times and still get power interruptions.
The G53 was purchased in the USA over a year ago, I do not think that Asus Australia ever brought the G53 into the country. I hope that someone knows how to fix it.

If you send a notebook in for repair is there any useful software of which you are aware available to strip the hard disk contents back to only that required to have the notebook serviced and dump user contents to an external hard drive to be restored after servicing?
I use the notebook to run everything and would rather not have any chance of accounts and passwords being discovered.

John

You can create a backup image of your system as is and put that on an external drive:

Backup Complete Computer - Create an Image Backup

Imaging with free Macrium

Free Backup Software: Paragon Backup & Recovery Free Edition - Overview


Then run the Diskpart Clean All command to write 0s to all sectors on the disk; this makes it impossible to recover your data or passwords for all but the most diligent recovery systems. Most of these systems are only obtainable by FBI and similar agencies.

Disk - Clean and Clean All with Diskpart Command


You will want to make your factory recovery discs prior to doing the clean all command. Then restore your system using the factory recovery discs (they do not store any of your important information like passwords, just the factory image for resetting your computer back to how it was when you bought it).

ASUSTeK Computer Inc. -Support- Troubleshooting G51J may help. It isn't exactly your model, but the steps should be the same.

Thanks again.

Since changing the advanced power settings for USB ( balanced power mode setting used ) the G53 has been stable, so far no BSOD.
Can a USB hub malfunction cause a BSOD even if there are no external devices connected to the G53 USB?
Normally I would only use USB to connect an external drive for backup operations and that is only for an hour or so.
I have had the G53 lock up once during a backup to external USB disk but I don't remember a BSOD while a USB disk is connected.

John