Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Blue Screen of Death Caused by USBPORT.SYS


  • Please log in to reply
8 replies to this topic

#1 iamz3r0

iamz3r0

  • Members
  • 27 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Virginia Beach, Virginia
  • Local time:03:13 PM

Posted 21 September 2009 - 08:08 AM

At random times, my computer will restart, and on the reboot, give me "Windows has recovered..." with the miniXXXXXX-XX.dmp file. I've used WinDbg in attempt to debug this issue, but no matter what I do, I can't seem to get rid of these annoying blue crash screens (restarts). All crashes are said to be caused by ipnat.sys, USBPORT.sys, or ntoskrnl.exe. This is a fresh installation of Windows XP Professional.

System Information:

Windows XP Professional SP3
Intel Pentium 4 (3.20 GHz)
960 RAM at 3.19 GHz
V2 Premier PM800-2 (Nvidia If I'm not mistaken...)

All drivers are up-to-date and working.
RAM has been tested.
USB Ports work correctly.

The .dmp files are attached to the post.
I know I've posted on this before, but this is a fresh installation and a different OS than before.

I'm not sure what's left to check! Any help is greatly appreciated!

Attached Files


Edited by iamz3r0, 21 September 2009 - 08:26 AM.

!@#$ this! I'm getting Windows 7, and if that doesn't work, a Mac!
Posted Image

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 56,131 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:02:13 PM

Posted 21 September 2009 - 09:28 AM

Rather than depositing the .dmp files here...you need to try to go through the following procedures with each...and post the results here.

Help Diagnosing BSODs And Crashes (BC) - http://www.bleepingcomputer.com/forums/t/176011/how-to-receive-help-diagnosing-blue-screens-and-windows-crashes/

Louis

#3 iamz3r0

iamz3r0
  • Topic Starter

  • Members
  • 27 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Virginia Beach, Virginia
  • Local time:03:13 PM

Posted 21 September 2009 - 09:54 AM

Rather than depositing the .dmp files here...you need to try to go through the following procedures with each...and post the results here.

Help Diagnosing BSODs And Crashes (BC) - http://www.bleepingcomputer.com/forums/t/176011/how-to-receive-help-diagnosing-blue-screens-and-windows-crashes/

Louis


This is from the most common, USBPORT.SYS crash:

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

Debugging Details:
------------------


BUGCHECK_STR: 0x7f_d

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from 804db746 to f7265e8e

STACK_TEXT:
f7911c8c 804db746 84188c58 8424b028 5444706c USBPORT!USBPORT_InterruptService+0x3a
f7911ca4 804db6e6 00000000 f7911cc0 804db6f3 nt!KiChainedDispatch2ndLvl+0x44
f7911ca4 804e7923 00000000 f7911cc0 804db6f3 nt!KiChainedDispatch+0x1c
f7784e2c f7784e30 f7784e30 f7912000 f790f000 nt!PopProcessorIdle+0xa9
WARNING: Frame IP not in any known module. Following frames may be wrong.
f7784e30 00000000 f7912000 f790f000 00000000 0xf7784e30


STACK_COMMAND: kb

FOLLOWUP_IP:
USBPORT!USBPORT_InterruptService+3a
f7265e8e ff505c call dword ptr [eax+5Ch]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: USBPORT!USBPORT_InterruptService+3a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: USBPORT

IMAGE_NAME: USBPORT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 480254ce

FAILURE_BUCKET_ID: 0x7f_d_USBPORT!USBPORT_InterruptService+3a

BUCKET_ID: 0x7f_d_USBPORT!USBPORT_InterruptService+3a

Followup: MachineOwner
---------


!@#$ this! I'm getting Windows 7, and if that doesn't work, a Mac!
Posted Image

#4 hamluis

hamluis

    Moderator


  • Moderator
  • 56,131 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:02:13 PM

Posted 21 September 2009 - 10:11 AM

It appears that this system included a MS XP install CD for users.

If so, then I suggest running the sfc /scannow command. The SP level of the CD must match the SP level of the install...if you have SP3 installed on the system, then you need to use a CD which also reflects SP3.

How To Use Sfc.exe To Repair System Files - http://www.bleepingcomputer.com/forums/t/43051/how-to-use-sfcexe-to-repair-system-files/

If the original disk requires updating to include SP3, then I suggest using the nLite site to accomplish the update.

nLite - Deployment Tool for Unattended Windows - Guide - http://www.nliteos.com/guide/index.html

Slipstreaming Windows XP To Create a Bootable Windows XP CD or DVD - http://www.bleepingcomputer.com/tutorials/slipstreaming-windows-xp-to-create-bootable-cd/

Louis

#5 iamz3r0

iamz3r0
  • Topic Starter

  • Members
  • 27 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Virginia Beach, Virginia
  • Local time:03:13 PM

Posted 21 September 2009 - 10:15 AM

It appears that this system included a MS XP install CD for users.

If so, then I suggest running the sfc /scannow command. The SP level of the CD must match the SP level of the install...if you have SP3 installed on the system, then you need to use a CD which also reflects SP3.


I'll do that (If I can make it through without a crash... :thumbsup:)

If the original disk requires updating to include SP3, then I suggest using the nLite site to accomplish the update.

nLite - Deployment Tool for Unattended Windows - Guide - http://www.nliteos.com/guide/index.html

Slipstreaming Windows XP To Create a Bootable Windows XP CD or DVD - http://www.bleepingcomputer.com/tutorials/slipstreaming-windows-xp-to-create-bootable-cd/


I've already upgraded my Windows XP disc to SP3, so that shouldn't be a problem.
!@#$ this! I'm getting Windows 7, and if that doesn't work, a Mac!
Posted Image

#6 hamluis

hamluis

    Moderator


  • Moderator
  • 56,131 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:02:13 PM

Posted 21 September 2009 - 11:03 AM

Hopefully...it's a damaged usbport.sys file, which the sfc /scannow command ought to catch and replace.

Louis

#7 iamz3r0

iamz3r0
  • Topic Starter

  • Members
  • 27 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Virginia Beach, Virginia
  • Local time:03:13 PM

Posted 21 September 2009 - 11:21 AM

Okay, I ran sfc /scannow and it completed, without giving me any errors, etc.

I'm guessing it's not a damaged usbport.sys?

EDIT: After another crash, I debugged the mini.dmp, and instead of a DRIVER_FAULT, I got COMMON_SYSTEM_FAULT. This is driving me nuts, and I'm hoping it can be fixed in the software instead of replacing the on board USB (or more than likely replacing the MoBo/Computer).

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

Debugging Details:
------------------


BUGCHECK_STR: 0x7f_d

CUSTOMER_CRASH_COUNT: 19

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from 804db746 to f72e9e8e

STACK_TEXT:
f7995c8c 804db746 85468270 85756028 f7995cb4 USBPORT!USBPORT_InterruptService+0x3a
f7995ca4 804db6e6 00000000 f7995cc0 804db6f3 nt!KiChainedDispatch2ndLvl+0x44
f7995ca4 00000000 00000000 f7995cc0 804db6f3 nt!KiChainedDispatch+0x1c


STACK_COMMAND: kb

FOLLOWUP_IP:
USBPORT!USBPORT_InterruptService+3a
f72e9e8e ff505c call dword ptr [eax+5Ch]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: USBPORT!USBPORT_InterruptService+3a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: USBPORT

IMAGE_NAME: USBPORT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 480254ce

FAILURE_BUCKET_ID: 0x7f_d_USBPORT!USBPORT_InterruptService+3a

BUCKET_ID: 0x7f_d_USBPORT!USBPORT_InterruptService+3a

Followup: MachineOwner
---------


Edited by iamz3r0, 21 September 2009 - 11:45 AM.

!@#$ this! I'm getting Windows 7, and if that doesn't work, a Mac!
Posted Image

#8 hamluis

hamluis

    Moderator


  • Moderator
  • 56,131 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:02:13 PM

Posted 21 September 2009 - 01:47 PM

Well...I'm not optimistic.

http://www.v2premier.com/cgi-bin/mainboard_db.cgi

I would download the above chipset drivers...and install same. If problem continues...I would turn off the onboard USB function and install a PCI USB 2.0 card. If the USB onboard functionality is disabled, I'm curious as to what driver will be pointed to, if any, during STOP errors/BSODs.

I would download and run the appropriate hard drive utility...from the correct respective drive manufacturer's website, long/extended test if long/short are offered.

Hard Drive Installation and Diagnostic Tools - http://www.bleepingcomputer.com/forums/t/28744/hard-drive-installation-and-diagnostic-tools/

You say that the RAM has been checked...using Memtest86+? If not, I would do so.

Methodology: Icrontic Diagnose with Memtest86+ - http://icrontic.com/articles/diagnose_with_memtest86 AND MemTest Manual - http://hcidesign.com/memtest/manual.html

Memtest86+ - Advanced Memory Diagnostic Tool - http://www.memtest.org/#downiso

Basic stuff.

You say that you just did a clean install...that pretty much precludes XP/Windows from consideration. The driver in question appears to be a system file and we've checked for damage, nothing there.

Louis

#9 iamz3r0

iamz3r0
  • Topic Starter

  • Members
  • 27 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Virginia Beach, Virginia
  • Local time:03:13 PM

Posted 26 September 2009 - 04:39 PM

Well...I'm not optimistic.

http://www.v2premier.com/cgi-bin/mainboard_db.cgi

I would download the above chipset drivers...and install same. If problem continues...I would turn off the onboard USB function and install a PCI USB 2.0 card. If the USB onboard functionality is disabled, I'm curious as to what driver will be pointed to, if any, during STOP errors/BSODs.

I would download and run the appropriate hard drive utility...from the correct respective drive manufacturer's website, long/extended test if long/short are offered.

Hard Drive Installation and Diagnostic Tools - http://www.bleepingcomputer.com/forums/t/28744/hard-drive-installation-and-diagnostic-tools/

You say that the RAM has been checked...using Memtest86+? If not, I would do so.

Methodology: Icrontic Diagnose with Memtest86+ - http://icrontic.com/articles/diagnose_with_memtest86 AND MemTest Manual - http://hcidesign.com/memtest/manual.html

Memtest86+ - Advanced Memory Diagnostic Tool - http://www.memtest.org/#downiso

Basic stuff.

You say that you just did a clean install...that pretty much precludes XP/Windows from consideration. The driver in question appears to be a system file and we've checked for damage, nothing there.

Louis


I've done just about everything I could have done to fix this. Memtest came up clean, the drivers are up-to-date. The only thing not installed is the RAID controller. I can't find the drivers for it. That wouldn't cause the restart, would it?
!@#$ this! I'm getting Windows 7, and if that doesn't work, a Mac!
Posted Image




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users