Random Crashes

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by gimpson, Jan 14, 2012.

  1. gimpson

    gimpson New Member

    Joined:
    Jan 14, 2012
    Messages:
    6
    Likes Received:
    0
    I have looked at the dump file but I don't know how to fix it.

    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Windows\Minidump\011412-48266-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Machine Name:
    Kernel base = 0xfffff800`02c57000 PsLoadedModuleList = 0xfffff800`02e9c670
    Debug session time: Sat Jan 14 10:31:32.646 2012 (UTC - 6:00)
    System Uptime: 0 days 0:16:13.191
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...........................
    Loading User Symbols
    Loading unloaded module list
    ............
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {0, 0, 0, 0}
    
    Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iRemovePriorityTransfer+7a )
    
    Followup: MachineOwner
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: 0000000000000000, The exception code that was not handled
    Arg2: 0000000000000000, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 0000000000000000, Parameter 1 of the exception
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
    
    FAULTING_IP: 
    +3534363563383837
    00000000`00000000 ??              ???
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  0000000000000000
    
    ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
    
    BUGCHECK_STR:  0x1E_0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    EXCEPTION_RECORD:  fffff88002ffd9b8 -- (.exr 0xfffff88002ffd9b8)
    ExceptionAddress: fffff88004252172 (USBPORT!USBPORT_Core_iRemovePriorityTransfer+0x000000000000007a)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff
    
    TRAP_FRAME:  fffff88002ffda60 -- (.trap 0xfffff88002ffda60)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=00000000fcfef5c5 rbx=0000000000000000 rcx=fffffa80093138a0
    rdx=fffffa8007b5e1a0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88004252172 rsp=fffff88002ffdbf0 rbp=fffffa8007b5e050
     r8=0000000063706458  r9=0000000000000000 r10=fffffa8007b5e1a0
    r11=fffffa8007b5e1a0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    USBPORT!USBPORT_Core_iRemovePriorityTransfer+0x7a:
    fffff880`04252172 8b5710          mov     edx,dword ptr [rdi+10h] ds:e1a0:00000000`00000010=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002ccb5fe to fffff80002cd3c10
    
    STACK_TEXT:  
    fffff880`02ffca98 fffff800`02ccb5fe : 00000103`00000001 00000000`00000000 fffff880`02ffd210 fffff800`02cff830 : nt!KeBugCheck
    fffff880`02ffcaa0 fffff800`02cff4fd : fffff800`02edd71c fffff800`02e1ac30 fffff800`02c57000 fffff880`02ffd9b8 : nt!KiKernelCalloutExceptionHandler+0xe
    fffff880`02ffcad0 fffff800`02cfe2d5 : fffff800`02e1e0fc fffff880`02ffcb48 fffff880`02ffd9b8 fffff800`02c57000 : nt!RtlpExecuteHandlerForException+0xd
    fffff880`02ffcb00 fffff800`02d0f361 : fffff880`02ffd9b8 fffff880`02ffd210 fffff880`00000000 00fffa80`07b5eeb0 : nt!RtlDispatchException+0x415
    fffff880`02ffd1e0 fffff800`02cd32c2 : fffff880`02ffd9b8 fffffa80`07b5e1a0 fffff880`02ffda60 fffffa80`070d8010 : nt!KiDispatchException+0x135
    fffff880`02ffd880 fffff800`02cd1bca : fffffa80`07b5ea18 fffff880`0424c231 fffffa80`0a3eb4f0 fffffa80`07b5e050 : nt!KiExceptionDispatch+0xc2
    fffff880`02ffda60 fffff880`04252172 : 00000000`00000000 00000000`ffffffff fffffa80`07b5eba0 fffff880`04243f5d : nt!KiGeneralProtectionFault+0x10a
    fffff880`02ffdbf0 fffff880`0424e9dc : fffffa80`070d8010 fffffa80`07b5e1a0 fffffa80`07b5eba0 fffffa80`07b5e1a0 : USBPORT!USBPORT_Core_iRemovePriorityTransfer+0x7a
    fffff880`02ffdc40 fffff880`0423ff89 : fffffa80`07b5e050 00000000`00000000 fffffa80`07b5eb02 fffffa80`07b5eba0 : USBPORT!USBPORT_Core_UsbDoneDpc_Worker+0x2bc
    fffff880`02ffdca0 fffff800`02cdf0ac : fffff880`02fd5180 fffffa80`07b5eba0 fffffa80`07b5ebb8 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
    fffff880`02ffdcd0 fffff800`02ccb96a : fffff880`02fd5180 fffff880`02fdffc0 00000000`00000000 fffff880`0423fdb0 : nt!KiRetireDpcList+0x1bc
    fffff880`02ffdd80 00000000`00000000 : fffff880`02ffe000 fffff880`02ff8000 fffff880`02ffdd40 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    USBPORT!USBPORT_Core_iRemovePriorityTransfer+7a
    fffff880`04252172 8b5710          mov     edx,dword ptr [rdi+10h]
    
    SYMBOL_STACK_INDEX:  7
    
    SYMBOL_NAME:  USBPORT!USBPORT_Core_iRemovePriorityTransfer+7a
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: USBPORT
    
    IMAGE_NAME:  USBPORT.SYS
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a670
    
    FAILURE_BUCKET_ID:  X64_0x1E_0_USBPORT!USBPORT_Core_iRemovePriorityTransfer+7a
    
    BUCKET_ID:  X64_0x1E_0_USBPORT!USBPORT_Core_iRemovePriorityTransfer+7a
    
    Followup: MachineOwner
    ---------
    
    
     

    Attached Files:

  2. gimpson

    gimpson New Member

    Joined:
    Jan 14, 2012
    Messages:
    6
    Likes Received:
    0
    After further testing I have figured out the problem. 611errors in Memtest86. Bad RAM :(
     
  3. Elmer

    Elmer Extraordinary Member

    Joined:
    Mar 5, 2010
    Messages:
    3,873
    Likes Received:
    284
    Hey Gimpson and Welcome to The Forum.

    I think you may have bad ram! :D

    Seriously though, well done in figuring out the issue for yourself. Fancy sticking around? All hands welcome to help other people out.
     

Share This Page

Loading...