Bluescreen Error D1

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by YourShadowDani, Mar 6, 2010.

  1. YourShadowDani

    YourShadowDani New Member

    Joined:
    Mar 6, 2010
    Messages:
    8
    Likes Received:
    0
    This is the error message I get after the bluescreen and restart:

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.256.1
    Locale ID: 1033

    Additional information about the problem:
    BCCode: d1
    BCP1: 0000000000000018
    BCP2: 0000000000000002
    BCP3: 0000000000000000
    BCP4: FFFFF88001F0C77E
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 256_1

    Files that help describe the problem:
    C:\Windows\Minidump\030510-21886-01.dmp
    C:\Users\YSD\AppData\Local\Temp\WER-38859-0.sysdata.xml

    Read our privacy statement online:
    Windows 7 Privacy Statement - Microsoft Windows

    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt

    Anyone have any Ideas what is causing this?
     
  2. Captain Jack

    Captain Jack Extraordinary Member

    Joined:
    Mar 6, 2010
    Messages:
    1,952
    Likes Received:
    139
    Hello,

    Post us the Dump file.
    Copy the contents of C:\Windows\Minidump to another (temporary) location somewhere on your machine.
    Zip up the copy and attach it here we will analysis it :)

    Good Luck,
    Captain
     
    ickymay and (deleted member) like this.
  3. ickymay

    ickymay New Member

    Joined:
    Jan 12, 2009
    Messages:
    1,689
    Likes Received:
    113
    some system information would help too please ??

    and weeeee hiya and welcome capn jack great to see ya :razz: :cool:
     
  4. YourShadowDani

    YourShadowDani New Member

    Joined:
    Mar 6, 2010
    Messages:
    8
    Likes Received:
    0
    Dump Files

    Here are the dump files, what program do you usually use to view these?
     

    Attached Files:

  5. Captain Jack

    Captain Jack Extraordinary Member

    Joined:
    Mar 6, 2010
    Messages:
    1,952
    Likes Received:
    139
    I guess the issue is with your USB Driver USBPORT.SYS or some USB device that is connected to your Computer. Disconnected the Device and remove their driver and see whether that makes any difference. If you have any third party Antivirus / Firewall uninstall it and see whether that makes an difference. If your Overclocking please stop doing. Check with your vendor and see whether you have any latest BIOS Firmware updates

    Update the Following Drivers

    Code:
    [FONT=\\\"Courier New\\\"]
    Lachesis.sys Fri Aug 17 13:18:44 2007
    jswpslwfx.sys Thu May 15 15:58:50 2008
    [/FONT]
    
    Bugcheck Analysis

    Code:
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    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.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff80002ad68d6, The address that the exception occurred at
    Arg3: fffff880009e64f8, Exception Record Address
    Arg4: fffff880009e5d50, Context Record Address
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    nt!KiInsertTimerTable+c6
    fffff800`02ad68d6 4c894008        mov     qword ptr [rax+8],r8
    
    EXCEPTION_RECORD:  fffff880009e64f8 -- (.exr 0xfffff880009e64f8)
    ExceptionAddress: fffff80002ad68d6 (nt!KiInsertTimerTable+0x00000000000000c6)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff
    
    CONTEXT:  fffff880009e5d50 -- (.cxr 0xfffff880009e5d50)
    rax=9007008000000000 rbx=fffffa80054f5320 rcx=000000044dfca590
    rdx=fffffa80062b2840 rsi=0000000000002020 rdi=fffff80002c42e80
    rip=fffff80002ad68d6 rsp=fffff880009e6730 rbp=fffffa80062b2840
     r8=fffffa80054f5340  r9=00000000000000f1 r10=fffff88002f63180
    r11=0000000000000000 r12=fffff80002c470a8 r13=0000000000000001
    r14=fffffa80054f5200 r15=000000044dfca590
    iopl=0         nv up ei pl nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
    nt!KiInsertTimerTable+0xc6:
    fffff800`02ad68d6 4c894008        mov     qword ptr [rax+8],r8 ds:002b:90070080`00000008=????????????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  ffffffffffffffff
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d000e0
     ffffffffffffffff 
    
    FOLLOWUP_IP: 
    USBPORT!USBPORT_InvalidateController+103
    fffff880`11e0539b e995000000      jmp     USBPORT!USBPORT_InvalidateController+0x19d (fffff880`11e05435)
    
    BUGCHECK_STR:  0x7E
    
    LAST_CONTROL_TRANSFER:  from fffff80002ad65e0 to fffff80002ad68d6
    
    STACK_TEXT:  
    fffff880`009e6730 fffff800`02ad65e0 : ffffffff`fffd7790 fffff880`02f63180 fffffa80`054f5320 00000000`00000000 : nt!KiInsertTimerTable+0xc6
    fffff880`009e6790 fffff800`02ad64e0 : fffffa80`07d941e0 ffffffff`fffd7790 00000000`496d6973 fffffa80`07d941e0 : nt!KiSetTimerEx+0xf0
    fffff880`009e6820 fffff880`11e0539b : 00000000`00000000 fffffa80`054f41a0 fffffa80`054f4050 00000000`00000005 : nt!KeSetTimer+0x14
    fffff880`009e6860 fffff880`11e01738 : fffffa80`06438a02 fffffa80`054f41a0 fffffa80`054f41a0 fffffa80`06438a10 : USBPORT!USBPORT_InvalidateController+0x103
    fffff880`009e6890 fffff880`11e07327 : fffffa80`06438a10 fffffa80`054f4050 fffffa80`054f4050 00000000`00000004 : USBPORT!MPf_InterruptNextSOF+0x74
    fffff880`009e68c0 fffff880`11e06402 : 00000000`00000000 00000000`00000004 fffffa80`06438a10 00000000`00000000 : USBPORT!USBPORT_SetEp_PAUSE+0xf3
    fffff880`009e6900 fffff880`11e06046 : fffffa80`054f41a0 00000000`00000000 fffffa80`00000005 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x212
    fffff880`009e6960 fffff880`11e17722 : fffffa80`06438a10 fffffa80`054f4050 fffffa80`054f5108 fffff880`00000000 : USBPORT!USBPORT_SetGlobalEndpointStateAndWait+0xa2
    fffff880`009e69b0 fffff880`11e1c229 : 00000000`00000000 fffffa80`054f4050 fffffa80`054f4050 00000000`00000003 : USBPORT!USBPORT_Core_FlushController+0x242
    fffff880`009e6a10 fffff880`11e1bb35 : 00000000`00000000 00000000`00000003 fffffa80`04139010 fffffa80`057fb050 : USBPORT!USBPORT_SuspendController+0x51
    fffff880`009e6a40 fffff880`11e1bf73 : 00000000`50524969 ffffffff`c00000bb fffffa80`054f4050 fffffa80`04139001 : USBPORT!USBPORT_PdoDevicePowerIrp+0xc9
    fffff880`009e6a90 fffff880`11e04ab2 : 00000000`00000000 fffffa80`057fb050 fffffa80`049adc20 fffffa80`04139010 : USBPORT!USBPORT_PdoPowerIrp+0x18b
    fffff880`009e6ac0 fffff800`02bcb502 : fffffa80`04139010 00000000`00000000 00000000`00000800 fffffa80`05818050 : USBPORT!USBPORT_Dispatch+0x1ba
    fffff880`009e6b00 fffff880`041c164e : 00000000`00000001 00000000`00000000 00000000`00000800 fffffa80`05818050 : nt!IopPoHandleIrp+0x32
    fffff880`009e6b30 fffff880`041bfa7a : fffffa80`05818050 fffffa80`05818708 fffffa80`05818708 00000000`00000003 : usbhub!UsbhFdoSetPowerDx_Action+0x39e
    fffff880`009e6b90 fffff880`041be70b : fffffa80`041391b8 fffffa80`058181a0 fffffa80`05818050 fffffa80`04139010 : usbhub!UsbhFdoDevicePowerState+0x206
    fffff880`009e6be0 fffff880`041bd9c7 : fffffa80`04139010 00000000`00000000 fffffa80`05818050 00000000`00000000 : usbhub!UsbhFdoPower_SetPower+0x93
    fffff880`009e6c20 fffff880`041a4fdf : 00000000`00000001 fffffa80`05818050 00000000`00000000 fffffa80`040f7c10 : usbhub!UsbhFdoPower+0xaf
    fffff880`009e6c60 fffff800`02be3e55 : 00000000`00000000 00000000`00000002 00000000`00000001 fffffa80`041390b8 : usbhub!UsbhGenDispatch+0x7f
    fffff880`009e6c90 fffff800`02d6d166 : 000003c6`00000000 fffffa80`039ef680 00000000`00000080 000003c6`00000000 : nt!PopIrpWorker+0x3c5
    fffff880`009e6d40 fffff800`02aa8486 : fffff880`02f63180 fffffa80`039ef680 fffff880`02f6df80 000003c6`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`009e6d80 00000000`00000000 : fffff880`009e7000 fffff880`009e1000 fffff880`009e66b0 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  USBPORT!USBPORT_InvalidateController+103
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: USBPORT
    
    IMAGE_NAME:  [B][COLOR=\\\"red\\\"]USBPORT.SYS[/COLOR][/B]
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc07
    
    STACK_COMMAND:  .cxr 0xfffff880009e5d50 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x7E_USBPORT!USBPORT_InvalidateController+103
    
    BUCKET_ID:  X64_0x7E_USBPORT!USBPORT_InvalidateController+103
    
    
    Hope this helps,
    Captain
     
  6. YourShadowDani

    YourShadowDani New Member

    Joined:
    Mar 6, 2010
    Messages:
    8
    Likes Received:
    0
    Actually I just unplugged my POS wireless USB adapter so that may fix the problem though I have a Cheap USB Hub that may be causing the issue though I wont be sure until another BSOD, I dont actually know what
    [FONT=\\\"Courier New\\\"]jswpslwfx.sys

    is but I am updating my Razer Lycosa and Lachesis drivers right now, any idea what that jswpslwfx.sys driver might be?
    [/FONT]
     
  7. Captain Jack

    Captain Jack Extraordinary Member

    Joined:
    Mar 6, 2010
    Messages:
    1,952
    Likes Received:
    139
    jswpslwfx.sys is related to JumpStart WPS Filter Driver

    Hope this helps,
    Captain
     
  8. YourShadowDani

    YourShadowDani New Member

    Joined:
    Mar 6, 2010
    Messages:
    8
    Likes Received:
    0
    Thanks for the help I appreciate it!
     
  9. Captain Jack

    Captain Jack Extraordinary Member

    Joined:
    Mar 6, 2010
    Messages:
    1,952
    Likes Received:
    139
    Your Most Welcome .. Happy i could help

    Good Luck,
    Captain
     

Share This Page

Loading...