BSOD & SWTOR (Dump Inside)


  1. Posts : 58
    Windows 7 Ultimate x64
       #1

    BSOD & SWTOR (Dump Inside)


    So the BSOD has only happened once but i have had 2 weird graphical issues where swtor crashed and both monitors flashed then my right monitor gets covered in GREEN SNOW. drivers are up to date and the BSOD came after the second time i got the green snow screen and had to reset the pc to get the snow off the screen. Heres the dump file. I also ran Memtest immediately after the BSOD just to check and it ran for almost 3 hours with no errors. 8gigs of ram and it made it through 2 full passes in that timeframe.
      My Computer


  2. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #2

    Code:
    Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\projectdwnshft\010712-20968-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`03002000 PsLoadedModuleList = 0xfffff800`03247670
    Debug session time: Sat Jan  7 14:18:10.236 2012 (GMT-7)
    System Uptime: 0 days 0:04:32.845
    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 : usbuhci.sys ( usbuhci!UhciProcessDoneIsochTd+27 )
    
    Followup: MachineOwner
    ---------
    
    1: 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: 
    +0
    00000000`00000000 ??              ???
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  0000000000000000
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x1E
    
    PROCESS_NAME:  swtor.exe
    
    CURRENT_IRQL:  2
    
    EXCEPTION_RECORD:  fffff88002f22ad8 -- (.exr 0xfffff88002f22ad8)
    ExceptionAddress: fffff88006e29f63 (usbuhci!UhciProcessDoneIsochTd+0x0000000000000027)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff
    
    TRAP_FRAME:  fffff88002f22b80 -- (.trap 0xfffff88002f22b80)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff88002f22d58 rbx=0000000000000000 rcx=fffffa80082586a0
    rdx=fffff8800c2b3c80 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88006e29f63 rsp=fffff88002f22d10 rbp=0000000000007a80
     r8=0000000000000324  r9=fffffa80082586a0 r10=0000000000000324
    r11=000000000003ff24 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    usbuhci!UhciProcessDoneIsochTd+0x27:
    fffff880`06e29f63 015e04          add     dword ptr [rsi+4],ebx ds:7170:00000000`00000004=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff800030765fe to fffff8000307ec10
    
    STACK_TEXT:  
    fffff880`02f21bb8 fffff800`030765fe : 00000000`f6b95bd0 fffffa80`094b5030 fffff880`02f22330 fffff800`030aa830 : nt!KeBugCheck
    fffff880`02f21bc0 fffff800`030aa4fd : fffff800`0328871c fffff800`031c5c30 fffff800`03002000 fffff880`02f22ad8 : nt!KiKernelCalloutExceptionHandler+0xe
    fffff880`02f21bf0 fffff800`030a92d5 : fffff800`031c9028 fffff880`02f21c68 fffff880`02f22ad8 fffff800`03002000 : nt!RtlpExecuteHandlerForException+0xd
    fffff880`02f21c20 fffff800`030ba361 : fffff880`02f22ad8 fffff880`02f22330 fffff880`00000000 fffff880`0c2b3c80 : nt!RtlDispatchException+0x415
    fffff880`02f22300 fffff800`0307e2c2 : fffff880`02f22ad8 00000000`ffffffff fffff880`02f22b80 04d0ffff`fa80078d : nt!KiDispatchException+0x135
    fffff880`02f229a0 fffff800`0307cbca : fffffa80`082571a0 fffff880`06e4531d fffffa80`082571a0 00000000`00000000 : nt!KiExceptionDispatch+0xc2
    fffff880`02f22b80 fffff880`06e29f63 : fffffa80`08880220 fffff880`06e5e208 fffffa80`085faf60 fffff880`06e2a2b2 : nt!KiGeneralProtectionFault+0x10a
    fffff880`02f22d10 fffff880`06e2a256 : fffffa80`082586a0 00000000`00007a80 fffffa80`07d62258 fffff880`0c2b3c80 : usbuhci!UhciProcessDoneIsochTd+0x27
    fffff880`02f22d60 fffff880`06e262dd : 00000000`00000002 fffffa80`07d62010 fffffa80`082571a0 00000000`ffffff02 : usbuhci!UhciPollIsochEndpoint+0x126
    fffff880`02f22db0 fffff880`06e32e8b : fffffa80`082571a0 00000000`00000002 00000000`00000000 00000000`00000020 : usbuhci!UhciPollEndpoint+0x21
    fffff880`02f22de0 fffff880`06e379d1 : 00000000`00000020 00000000`00000004 fffffa80`07d62010 fffffa80`08257050 : USBPORT!MPf_PollEndpoint+0x9b
    fffff880`02f22e10 fffff880`06e43077 : fffffa80`082571a0 00000000`00000020 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1
    fffff880`02f22e70 fffff880`06e33f89 : fffffa80`08257050 00000000`00000000 fffffa80`08257a02 fffffa80`08257a18 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1c3
    fffff880`02f22ed0 fffff800`0308a0ac : fffff880`009e7180 fffffa80`08257a18 fffffa80`08257a30 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
    fffff880`02f22f00 fffff800`03081765 : 00000000`00000000 fffffa80`06cee060 00000000`00000000 fffff880`06e33db0 : nt!KiRetireDpcList+0x1bc
    fffff880`02f22fb0 fffff800`0308157c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
    fffff880`0c3b9be0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    usbuhci!UhciProcessDoneIsochTd+27
    fffff880`06e29f63 015e04          add     dword ptr [rsi+4],ebx
    
    SYMBOL_STACK_INDEX:  7
    
    SYMBOL_NAME:  usbuhci!UhciProcessDoneIsochTd+27
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: usbuhci
    
    IMAGE_NAME:  usbuhci.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c0bff
    
    FAILURE_BUCKET_ID:  X64_0x1E_usbuhci!UhciProcessDoneIsochTd+27
    
    BUCKET_ID:  X64_0x1E_usbuhci!UhciProcessDoneIsochTd+27
    
    Followup: MachineOwner
    ---------
    First, update the following drivers. See Driver Reference and manufacturers for drivers and driver manufacturers respectively.
    Code:
    uGuru	fffff880`06b5d000	fffff880`06b61000	Wed Sep 20 02:06:44 2006 (4510f694)	00006efa		uGuru.sys
    nvoclk64	fffff880`0a669000	fffff880`0a677000	Tue Sep 04 20:26:33 2007 (46de13d9)	0000b0c1		nvoclk64.sys
    MTiCtwl	fffff880`01473000	fffff880`0147c000	Tue Nov 04 00:40:50 2008 (490ffc82)	0000b926		MTiCtwl.sys
    ALSysIO64	fffff880`0a695000	fffff880`0a69d000	Sun Apr 19 13:41:04 2009 (49eb7e50)	0000bbad		ALSysIO64.sys
    Then, follow the steps in USB Driver - General Fix for Problems since your problem was USB related.
      My Computer


  3. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #3

    Also, please remove Daemon Tools, as it uses a driver called dtsoftbus01.sys that is known to cause BSODs.

    I prefer TotalMounter as my CD/DVD virtualization software as it allows me to burn images to a virtual CD/DVD if I just want an ISO file instead of a disc, and it is free.

    Many use MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor as well, which is also free.
      My Computer


  4. Posts : 58
    Windows 7 Ultimate x64
    Thread Starter
       #4

    so your saying one of my USB devices caused the BSOD?
      My Computer


  5. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #5

    projectdwnshft said:
    so your saying one of my USB devices caused the BSOD?
    That's what the .dmp file is saying. I'm saying that is one of the more probable reasons.
      My Computer


  6. Posts : 58
    Windows 7 Ultimate x64
    Thread Starter
       #6

    usb drivers are cleaned and those 4 drivers have been updated/removed a few of them werent even needed. I shall see if this fixes anything over the next few days. thanks again for the help
      My Computer


  7. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #7

    No problem. Best wishes! :)

    Let us know if you need help in the future.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 12:13.
Find Us