Windows 7 X64 SP1 - BSOD (IRQL_NOT LESS OR EQUAL, usbport.sys) RRS feed

  • Question

  • Hi all,

    I have recently had my faulty PSU RMA'd after it kept on crashing (immediate reboot) due to a faulty 12V, this gave a Kernel-Power 41 error with a Bugcheck of 0.

    Now, I am experiencing BSOD, with the following:


    A problem has been detected and Windows has been shut down to prevent damage
    to your computer.
    The problem seems to be caused by the following file: USBPORT.SYS


    The event logs says:


    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
     <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> 
     <TimeCreated SystemTime="2011-05-28T10:32:28.424813900Z" /> 
     <Correlation /> 
     <Execution ProcessID="4" ThreadID="8" /> 
     <Security UserID="S-1-5-18" /> 
    - <EventData>
     <Data Name="BugcheckCode">209</Data> 
     <Data Name="BugcheckParameter1">0xfffffa7f8502a1c0</Data> 
     <Data Name="BugcheckParameter2">0x2</Data> 
     <Data Name="BugcheckParameter3">0x0</Data> 
     <Data Name="BugcheckParameter4">0xfffff88003e88dde</Data> 
     <Data Name="SleepInProgress">false</Data> 
     <Data Name="PowerButtonTimestamp">0</Data> 


    Here are the minidumps, combined into a ZIP folder:

    As you will see, the main offender is USBPORT.SYS, however TCPIP.SYS and HAL.DLL also feature (see minidumps)

    Unfortunately in regards to solving this issue, I am stumped.

    Any help would be much appreciated, cheers guys.

    Saturday, May 28, 2011 11:21 AM


  • Ok, manually changing the RAM voltage to 1.8 in the BIOS instead of AUTO, Disabling Superfetch and upping the NorthBridge voltage to 1.36 seem to have stabilised the system and prevented any crashed from occurring thusfar (hopefully). I will post if the crash occurs again.
    • Marked as answer by Miya Yao Monday, June 6, 2011 9:18 AM
    Tuesday, May 31, 2011 12:16 PM

All replies

  • Interestingly, I have discovered the Intel Chipset software was not updating the drivers. Have done it manually and will let you know the results
    Saturday, May 28, 2011 12:04 PM
  • *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arg1: fffffa7f8502a1c0, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff88003e88dde, address which referenced memory
    Debugging Details:
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cfc100
    fffff880`03e88dde 8b4a20          mov     ecx,dword ptr [rdx+20h]
    PROCESS_NAME:  svchost.exe
    TRAP_FRAME:  fffff88002f22ce0 -- (.trap 0xfffff88002f22ce0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=00000000ffae7f75 rbx=0000000000000000 rcx=0000000000000000
    rdx=fffffa800502a1a0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88003e88dde rsp=fffff88002f22e70 rbp=fffffa8005b745b0
     r8=fffffa800502a1a0  r9=00000000ffffffff r10=fffffa800502a1a0
    r11=fffffa800502a1a0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz ac po cy
    fffff880`03e88dde 8b4a20          mov     ecx,dword ptr [rdx+20h] ds:aeb0:fffffa80`0502a1c0=000003ff
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff80002acc2a9 to fffff80002accd00
    fffff880`02f22b98 fffff800`02acc2a9 : 00000000`0000000a fffffa7f`8502a1c0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`02f22ba0 fffff800`02acaf20 : fffffa80`058c94d0 00000000`000007ff fffffa80`05b0dc80 fffffa80`0502a050 : nt!KiBugCheckDispatch+0x69
    fffff880`02f22ce0 fffff880`03e88dde : fffffa80`0502a050 fffffa80`05cc5c30 fffffa80`04e5d0f0 fffffa80`0502a1a0 : nt!KiPageFault+0x260
    fffff880`02f22e70 fffff880`03e79f89 : fffffa80`0502a050 00000000`00000000 fffffa80`0502ad02 fffffa80`0502ad28 : USBPORT!USBPORT_Core_UsbMapDpc_Worker+0x1ce
    fffff880`02f22ed0 fffff800`02ad810c : fffff880`009e9180 fffffa80`0502ad28 fffffa80`0502ad40 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
    fffff880`02f22f00 fffff800`02acf765 : 00000000`00000000 fffffa80`03f29060 00000000`00000000 fffff880`03e79db0 : nt!KiRetireDpcList+0x1bc
    fffff880`02f22fb0 fffff800`02acf57c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
    fffff880`08bbdba0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
    fffff880`03e88dde 8b4a20          mov     ecx,dword ptr [rdx+20h]
    SYMBOL_NAME:  USBPORT!USBPORT_Core_UsbMapDpc_Worker+1ce
    FOLLOWUP_NAME:  MachineOwner
    FAILURE_BUCKET_ID:  X64_0xD1_USBPORT!USBPORT_Core_UsbMapDpc_Worker+1ce
    BUCKET_ID:  X64_0xD1_USBPORT!USBPORT_Core_UsbMapDpc_Worker+1ce
    Followup: MachineOwner
    1: kd> lmvm USBPORT
    start             end                 module name
    fffff880`03e77000 fffff880`03ecd000   USBPORT    (pdb symbols)          c:\symbols\usbport.pdb\71BCD350024D47208D5EA216690A7BFF1\usbport.pdb
        Loaded symbol image file: USBPORT.SYS
        Mapped memory image file: c:\symbols\USBPORT.SYS\4CE7A67056000\USBPORT.SYS
        Image path: \SystemRoot\system32\drivers\USBPORT.SYS
        Image name: USBPORT.SYS
        Timestamp:        Sat Nov 20 11:44:00 2010 (4CE7A670)
        CheckSum:         00059BC8
        ImageSize:        00056000
        File version:     6.1.7601.17514
        Product version:  6.1.7601.17514
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        2.0 Dll
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     usbport.sys
        OriginalFilename: usbport.sys
        ProductVersion:   6.1.7601.17514
        FileVersion:      6.1.7601.17514 (win7sp1_rtm.101119-1850)
        FileDescription:  USB 1.1 & 2.0 Port Driver
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
    I suspect that you have a faulty USB port. Please check that with your manufacturer.
    Please also start updating all possible drivers especially NIC ones.
    You can also contact Microsoft CSS.

    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration

    Saturday, May 28, 2011 12:07 PM
  • Please also refer to:

    Binary files in some USB drivers are not updated after you install Windows 7 SP1 or Windows Server 2008 R2 SP1




    This posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Monday, May 30, 2011 5:37 AM
  • Brilliant, cheers.

    The problems have stopped now I've disconnected my USB External Hard Drive...although I shall reinstall the drivers and see if it stops the HDD from causing the BSOD. Fingers crossed eh.

    Monday, May 30, 2011 3:49 PM
  • Alright, I thought I had isolated the issue, but apparently not. Have even managed to update USB drivers now.

    Interestingly, the BSOD only seems to occur when playing Football Manager 2011, I will attempt to test another game when I install one, but could this point to a GFX card issue? Possibly linked to the faulty PSU I had that rebooted when playing 3D games? Or are we still looking at a fubar mobo?

    My RAM (2 x 2GB DDR2-6400) did 2 passes on Memtest86+ (I was being lazy), but I will attempt to use some other sticks to confirm that it is not the RAM. And my CPU is OC'ed up from 3.00 to 3.60, not attempted to undo the OC, because I doubt it's a factor.

    The BSOD has stopped referencing any particular system file as a cause, but the error remains the same.

    The latest .dmp file can be found here, if anyone would be so kind as to take a look:



    EDIT: Ok, I just got a random BSOD with 'usbport.sys' when browsing, so my paranoia over the GFX card was shortlived it seems.

    I should point out that it still only seems to occur with the external hard drive plugged in.

    Monday, May 30, 2011 11:38 PM
  • Ok, manually changing the RAM voltage to 1.8 in the BIOS instead of AUTO, Disabling Superfetch and upping the NorthBridge voltage to 1.36 seem to have stabilised the system and prevented any crashed from occurring thusfar (hopefully). I will post if the crash occurs again.
    • Marked as answer by Miya Yao Monday, June 6, 2011 9:18 AM
    Tuesday, May 31, 2011 12:16 PM