locked
BSOD RRS feed

  • Question

  • For the past few months I've been getting BSOD.  Last July I added 6GB RAM and upgraded the video card to a GTX570.  It ran great for 3 or 4 months then the bsod started.   I thought the power supply might have been getting overloaded so I removed the 6GB that I added.  I'm still getting them.  It's a 650W ps so I don't think the new video card alone would cause this.  I've zipped the minidump files and uploaded them to skydrive.

    https://skydrive.live.com/?cid=1d3c8f9bfd25aafe#cid=1D3C8F9BFD25AAFE&id=1D3C8F9BFD25AAFE!133

    I looked at them in BlueScreenView, but it doesn't make a lot of sense to me.

     

    • Moved by Carey FrischMVP Monday, December 26, 2011 1:00 AM Move to more appropriate forum category (From:Windows 7 Miscellaneous)
    Sunday, December 25, 2011 11:39 PM

Answers

  • The exception is due to the developers of the driver not removing a
    breakpoint during the debugging/development process. This is due to an
    extraordinarily sloppy development process. I would recommend that you
    find a different version of the silabser.sys driver, or determine if you
    actually need it. Google identifies this as a "Silicon Labs CP210x USB
    to UART Bridge Driver"
     
    In the future, if you want to analyze dumps like this,
     
     
    If you end up not needing it and want to disable it,
     
     
    The dump from today showed,
     
    5: 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:
    +3132323761623761
    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:  fffff880030b08a8 -- (.exr 0xfffff880030b08a8)
    ExceptionAddress: fffff800030d4a70 (nt!DbgBreakPoint)
       ExceptionCode: 80000003 (Break instruction exception)
      ExceptionFlags: 00000000
    NumberParameters: 1
       Parameter[0]: 0000000000000000
     
    TRAP_FRAME:  fffff880030b0950 -- (.trap 0xfffff880030b0950)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffff88000f60f70
    rdx=fffffa8007ad26b0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800030d4a71 rsp=fffff880030b0ae8 rbp=0000000000000000
     r8=fffffa8007ad26b0  r9=fffff88000f60f40 r10=7efefeff71647261
    r11=fffff880030b0ad0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    nt!DbgBreakPoint+0x1:
    fffff800`030d4a71 c3              ret
    Resetting default scope
     
    LAST_CONTROL_TRANSFER:  from fffff800030d45fe to fffff800030dcc10
     
    STACK_TEXT:
    fffff880`030af988 fffff800`030d45fe : fffffa80`00000001 fffff880`01780800 fffff880`030b0100 fffff800`03108830 : nt!KeBugCheck
    fffff880`030af990 fffff800`031084fd : fffff800`032e671c fffff800`03223c30 fffff800`03060000 fffff880`030b08a8 : nt!KiKernelCalloutExceptionHandler+0xe
    fffff880`030af9c0 fffff800`031072d5 : fffff800`032270fc fffff880`030afa38 fffff880`030b08a8 fffff800`03060000 : nt!RtlpExecuteHandlerForException+0xd
    fffff880`030af9f0 fffff800`03118361 : fffff880`030b08a8 fffff880`030b0100 fffff880`00000000 00000000`c0000010 : nt!RtlDispatchException+0x415
    fffff880`030b00d0 fffff800`030dc2c2 : fffff880`030b08a8 00000000`00000000 fffff880`030b0950 fffffa80`07ad2550 : nt!KiDispatchException+0x135
    fffff880`030b0770 fffff800`030da0f4 : fffffa80`07a5d3f0 fffffa80`0bd82101 fffffa80`07a5d400 fffffa80`0bd82101 : nt!KiExceptionDispatch+0xc2
    fffff880`030b0950 fffff800`030d4a71 : fffff880`00f0d9fc 00000000`00000000 fffffa80`07ad26b0 fffffa80`07ad26b0 : nt!KiBreakpointTrap+0xf4
    fffff880`030b0ae8 fffff880`00f0d9fc : 00000000`00000000 fffffa80`07ad26b0 fffffa80`07ad26b0 fffff880`00f60f40 : nt!DbgBreakPoint+0x1
    fffff880`030b0af0 fffff880`00f2099f : fffffa80`0878b880 00000000`00000002 00000000`00000002 fffffa80`07a5b080 : Wdf01000!FxRequest::VerifierVerifyRequestIsCancelable+0x80
    fffff880`030b0b40 fffff880`00efe428 : 00000000`00000002 0000057f`f7874778 00000000`00000001 fffffa80`07ad2630 : Wdf01000!FxIoQueue::RequestCancelable+0xe7
    fffff880`030b0bb0 fffff880`04dbf319 : fffffa80`0878b880 fffffa80`0878ba10 0000057f`f7874778 0000057f`f7874778 : Wdf01000!imp_WdfRequestUnmarkCancelable+0xbc
    fffff880`030b0c00 fffffa80`0878b880 : fffffa80`0878ba10 0000057f`f7874778 0000057f`f7874778 00000000`00000001 : silabser+0x7319
    fffff880`030b0c08 fffffa80`0878ba10 : 0000057f`f7874778 0000057f`f7874778 00000000`00000001 fffffa80`07038d28 : 0xfffffa80`0878b880
    fffff880`030b0c10 0000057f`f7874778 : 0000057f`f7874778 00000000`00000001 fffffa80`07038d28 00000000`c0000120 : 0xfffffa80`0878ba10
    fffff880`030b0c18 0000057f`f7874778 : 00000000`00000001 fffffa80`07038d28 00000000`c0000120 fffff880`04dc004e : 0x57f`f7874778
    fffff880`030b0c20 00000000`00000001 : fffffa80`07038d28 00000000`c0000120 fffff880`04dc004e fffffa80`0878ba10 : 0x57f`f7874778
    fffff880`030b0c28 fffffa80`07038d28 : 00000000`c0000120 fffff880`04dc004e fffffa80`0878ba10 00000000`00000000 : 0x1
    fffff880`030b0c30 00000000`c0000120 : fffff880`04dc004e fffffa80`0878ba10 00000000`00000000 fffffa80`0798ac40 : 0xfffffa80`07038d28
    fffff880`030b0c38 fffff880`04dc004e : fffffa80`0878ba10 00000000`00000000 fffffa80`0798ac40 fffffa80`0798ac40 : 0xc0000120
    fffff880`030b0c40 fffffa80`0878ba10 : 00000000`00000000 fffffa80`0798ac40 fffffa80`0798ac40 fffffa80`07038d28 : silabser+0x804e
    fffff880`030b0c48 00000000`00000000 : fffffa80`0798ac40 fffffa80`0798ac40 fffffa80`07038d28 fffff880`030930c0 : 0xfffffa80`0878ba10
     STACK_COMMAND:  kb
     
    FOLLOWUP_IP:
    silabser+7319
    fffff880`04dbf319 ??              ???
     
    SYMBOL_STACK_INDEX:  b
     
    SYMBOL_NAME:  silabser+7319
     
    FOLLOWUP_NAME:  MachineOwner
     
    MODULE_NAME: silabser
     
    IMAGE_NAME:  silabser.sys
     
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e83514f
     
    FAILURE_BUCKET_ID:  X64_0x1E_0_silabser+7319
     
    BUCKET_ID:  X64_0x1E_0_silabser+7319
     
    Followup: MachineOwner
    ---------
     
     

    -- Mike Burr
    Technology
    • Marked as answer by Cloud_TS Saturday, December 31, 2011 6:57 AM
    Monday, December 26, 2011 5:07 AM

All replies

  • The exception is due to the developers of the driver not removing a
    breakpoint during the debugging/development process. This is due to an
    extraordinarily sloppy development process. I would recommend that you
    find a different version of the silabser.sys driver, or determine if you
    actually need it. Google identifies this as a "Silicon Labs CP210x USB
    to UART Bridge Driver"
     
    In the future, if you want to analyze dumps like this,
     
     
    If you end up not needing it and want to disable it,
     
     
    The dump from today showed,
     
    5: 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:
    +3132323761623761
    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:  fffff880030b08a8 -- (.exr 0xfffff880030b08a8)
    ExceptionAddress: fffff800030d4a70 (nt!DbgBreakPoint)
       ExceptionCode: 80000003 (Break instruction exception)
      ExceptionFlags: 00000000
    NumberParameters: 1
       Parameter[0]: 0000000000000000
     
    TRAP_FRAME:  fffff880030b0950 -- (.trap 0xfffff880030b0950)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffff88000f60f70
    rdx=fffffa8007ad26b0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800030d4a71 rsp=fffff880030b0ae8 rbp=0000000000000000
     r8=fffffa8007ad26b0  r9=fffff88000f60f40 r10=7efefeff71647261
    r11=fffff880030b0ad0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    nt!DbgBreakPoint+0x1:
    fffff800`030d4a71 c3              ret
    Resetting default scope
     
    LAST_CONTROL_TRANSFER:  from fffff800030d45fe to fffff800030dcc10
     
    STACK_TEXT:
    fffff880`030af988 fffff800`030d45fe : fffffa80`00000001 fffff880`01780800 fffff880`030b0100 fffff800`03108830 : nt!KeBugCheck
    fffff880`030af990 fffff800`031084fd : fffff800`032e671c fffff800`03223c30 fffff800`03060000 fffff880`030b08a8 : nt!KiKernelCalloutExceptionHandler+0xe
    fffff880`030af9c0 fffff800`031072d5 : fffff800`032270fc fffff880`030afa38 fffff880`030b08a8 fffff800`03060000 : nt!RtlpExecuteHandlerForException+0xd
    fffff880`030af9f0 fffff800`03118361 : fffff880`030b08a8 fffff880`030b0100 fffff880`00000000 00000000`c0000010 : nt!RtlDispatchException+0x415
    fffff880`030b00d0 fffff800`030dc2c2 : fffff880`030b08a8 00000000`00000000 fffff880`030b0950 fffffa80`07ad2550 : nt!KiDispatchException+0x135
    fffff880`030b0770 fffff800`030da0f4 : fffffa80`07a5d3f0 fffffa80`0bd82101 fffffa80`07a5d400 fffffa80`0bd82101 : nt!KiExceptionDispatch+0xc2
    fffff880`030b0950 fffff800`030d4a71 : fffff880`00f0d9fc 00000000`00000000 fffffa80`07ad26b0 fffffa80`07ad26b0 : nt!KiBreakpointTrap+0xf4
    fffff880`030b0ae8 fffff880`00f0d9fc : 00000000`00000000 fffffa80`07ad26b0 fffffa80`07ad26b0 fffff880`00f60f40 : nt!DbgBreakPoint+0x1
    fffff880`030b0af0 fffff880`00f2099f : fffffa80`0878b880 00000000`00000002 00000000`00000002 fffffa80`07a5b080 : Wdf01000!FxRequest::VerifierVerifyRequestIsCancelable+0x80
    fffff880`030b0b40 fffff880`00efe428 : 00000000`00000002 0000057f`f7874778 00000000`00000001 fffffa80`07ad2630 : Wdf01000!FxIoQueue::RequestCancelable+0xe7
    fffff880`030b0bb0 fffff880`04dbf319 : fffffa80`0878b880 fffffa80`0878ba10 0000057f`f7874778 0000057f`f7874778 : Wdf01000!imp_WdfRequestUnmarkCancelable+0xbc
    fffff880`030b0c00 fffffa80`0878b880 : fffffa80`0878ba10 0000057f`f7874778 0000057f`f7874778 00000000`00000001 : silabser+0x7319
    fffff880`030b0c08 fffffa80`0878ba10 : 0000057f`f7874778 0000057f`f7874778 00000000`00000001 fffffa80`07038d28 : 0xfffffa80`0878b880
    fffff880`030b0c10 0000057f`f7874778 : 0000057f`f7874778 00000000`00000001 fffffa80`07038d28 00000000`c0000120 : 0xfffffa80`0878ba10
    fffff880`030b0c18 0000057f`f7874778 : 00000000`00000001 fffffa80`07038d28 00000000`c0000120 fffff880`04dc004e : 0x57f`f7874778
    fffff880`030b0c20 00000000`00000001 : fffffa80`07038d28 00000000`c0000120 fffff880`04dc004e fffffa80`0878ba10 : 0x57f`f7874778
    fffff880`030b0c28 fffffa80`07038d28 : 00000000`c0000120 fffff880`04dc004e fffffa80`0878ba10 00000000`00000000 : 0x1
    fffff880`030b0c30 00000000`c0000120 : fffff880`04dc004e fffffa80`0878ba10 00000000`00000000 fffffa80`0798ac40 : 0xfffffa80`07038d28
    fffff880`030b0c38 fffff880`04dc004e : fffffa80`0878ba10 00000000`00000000 fffffa80`0798ac40 fffffa80`0798ac40 : 0xc0000120
    fffff880`030b0c40 fffffa80`0878ba10 : 00000000`00000000 fffffa80`0798ac40 fffffa80`0798ac40 fffffa80`07038d28 : silabser+0x804e
    fffff880`030b0c48 00000000`00000000 : fffffa80`0798ac40 fffffa80`0798ac40 fffffa80`07038d28 fffff880`030930c0 : 0xfffffa80`0878ba10
     STACK_COMMAND:  kb
     
    FOLLOWUP_IP:
    silabser+7319
    fffff880`04dbf319 ??              ???
     
    SYMBOL_STACK_INDEX:  b
     
    SYMBOL_NAME:  silabser+7319
     
    FOLLOWUP_NAME:  MachineOwner
     
    MODULE_NAME: silabser
     
    IMAGE_NAME:  silabser.sys
     
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e83514f
     
    FAILURE_BUCKET_ID:  X64_0x1E_0_silabser+7319
     
    BUCKET_ID:  X64_0x1E_0_silabser+7319
     
    Followup: MachineOwner
    ---------
     
     

    -- Mike Burr
    Technology
    • Marked as answer by Cloud_TS Saturday, December 31, 2011 6:57 AM
    Monday, December 26, 2011 5:07 AM
  • *******************************************************************************
    *                                                                             *
    *                        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: 
    +3461313638633965
    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:  fffff88002f8c8a8 -- (.exr 0xfffff88002f8c8a8)
    ExceptionAddress: fffff800030cda70 (nt!DbgBreakPoint)
       ExceptionCode: 80000003 (Break instruction exception)
      ExceptionFlags: 00000000
    NumberParameters: 1
       Parameter[0]: 0000000000000000
    TRAP_FRAME:  fffff88002f8c950 -- (.trap 0xfffff88002f8c950)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffff88000ea7f70
    rdx=fffffa800c23ebd0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800030cda71 rsp=fffff88002f8cae8 rbp=0000000000000000
     r8=fffffa800c23ebd0  r9=fffff88000ea7f40 r10=7efefeff71647261
    r11=fffff88002f8cad0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    nt!DbgBreakPoint+0x1:
    fffff800`030cda71 c3              ret
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff800030cd5fe to fffff800030d5c10
    STACK_TEXT:  
    fffff880`02f8b988 fffff800`030cd5fe : fffffa80`0bf02330 fffffa80`00000004 fffff880`02f8c100 fffff800`03101830 : nt!KeBugCheck
    fffff880`02f8b990 fffff800`031014fd : fffff800`032df71c fffff800`0321cc30 fffff800`03059000 fffff880`02f8c8a8 : nt!KiKernelCalloutExceptionHandler+0xe
    fffff880`02f8b9c0 fffff800`031002d5 : fffff800`032200fc fffff880`02f8ba38 fffff880`02f8c8a8 fffff800`03059000 : nt!RtlpExecuteHandlerForException+0xd
    fffff880`02f8b9f0 fffff800`03111361 : fffff880`02f8c8a8 fffff880`02f8c100 fffff880`00000000 00000000`c0000010 : nt!RtlDispatchException+0x415
    fffff880`02f8c0d0 fffff800`030d52c2 : fffff880`02f8c8a8 00000000`00000000 fffff880`02f8c950 fffffa80`0c23ea70 : nt!KiDispatchException+0x135
    fffff880`02f8c770 fffff800`030d30f4 : fffffa80`0b865e40 fffffa80`13253e01 fffffa80`0b865e50 fffffa80`13253e01 : nt!KiExceptionDispatch+0xc2
    fffff880`02f8c950 fffff800`030cda71 : fffff880`00e549fc 00000000`00000000 fffffa80`0c23ebd0 fffffa80`0c23ebd0 : nt!KiBreakpointTrap+0xf4
    fffff880`02f8cae8 fffff880`00e549fc : 00000000`00000000 fffffa80`0c23ebd0 fffffa80`0c23ebd0 fffff880`00ea7f40 : nt!DbgBreakPoint+0x1
    fffff880`02f8caf0 fffff880`00e6799f : fffffa80`0e32a9d0 00000000`00000002 00000000`00000002 fffffa80`0b7a4850 : Wdf01000!FxRequest::VerifierVerifyRequestIsCancelable+0x80
    fffff880`02f8cb40 fffff880`00e45428 : 00000000`00000002 0000057f`f1cd5628 00000000`00000001 fffffa80`0c23eb50 : Wdf01000!FxIoQueue::RequestCancelable+0xe7
    fffff880`02f8cbb0 fffff880`04e63319 : fffffa80`0e32a9d0 fffffa80`0e32ab60 0000057f`f1cd5628 0000057f`f1cd5628 : Wdf01000!imp_WdfRequestUnmarkCancelable+0xbc
    fffff880`02f8cc00 fffffa80`0e32a9d0 : fffffa80`0e32ab60 0000057f`f1cd5628 0000057f`f1cd5628 00000000`00000001 : silabser+0x7319
    fffff880`02f8cc08 fffffa80`0e32ab60 : 0000057f`f1cd5628 0000057f`f1cd5628 00000000`00000001 fffffa80`0b979d28 : 0xfffffa80`0e32a9d0
    fffff880`02f8cc10 0000057f`f1cd5628 : 0000057f`f1cd5628 00000000`00000001 fffffa80`0b979d28 00000000`c0000120 : 0xfffffa80`0e32ab60
    fffff880`02f8cc18 0000057f`f1cd5628 : 00000000`00000001 fffffa80`0b979d28 00000000`c0000120 fffff880`04e6404e : 0x57f`f1cd5628
    fffff880`02f8cc20 00000000`00000001 : fffffa80`0b979d28 00000000`c0000120 fffff880`04e6404e fffffa80`0e32ab60 : 0x57f`f1cd5628
    fffff880`02f8cc28 fffffa80`0b979d28 : 00000000`c0000120 fffff880`04e6404e fffffa80`0e32ab60 00000000`00000000 : 0x1
    fffff880`02f8cc30 00000000`c0000120 : fffff880`04e6404e fffffa80`0e32ab60 00000000`00000000 fffffa80`0b862c40 : 0xfffffa80`0b979d28
    fffff880`02f8cc38 fffff880`04e6404e : fffffa80`0e32ab60 00000000`00000000 fffffa80`0b862c40 fffffa80`0b862c40 : 0xc0000120
    fffff880`02f8cc40 fffffa80`0e32ab60 : 00000000`00000000 fffffa80`0b862c40 fffffa80`0b862c40 fffffa80`0b979d28 : silabser+0x804e
    fffff880`02f8cc48 00000000`00000000 : fffffa80`0b862c40 fffffa80`0b862c40 fffffa80`0b979d28 fffff880`02f6f0c0 : 0xfffffa80`0e32ab60
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    silabser+7319
    fffff880`04e63319 ??              ???
    SYMBOL_STACK_INDEX:  b
    SYMBOL_NAME:  silabser+7319
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: silabser
    IMAGE_NAME:  silabser.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e83514f
    FAILURE_BUCKET_ID:  X64_0x1E_0_silabser+7319
    BUCKET_ID:  X64_0x1E_0_silabser+7319
    Followup: MachineOwner
    -----------------------------------------------------------------------------------------------------------------------------------------------------------------
    The Blue Screen Caused By ( silabser.sys
    Silabser.sys  : with description Silicon Labs CP210x USB to UART Bridge Driver is a driver file from company Silicon Laboratories belonging to product .
    Try To Update it to the latest Version or previous version you're installed it.
    Regards,

    MCP ✦ MCTS ✦ MCITP
    Monday, December 26, 2011 9:46 AM
  • Thanks!  I've disabled the driver and will have to look for a workaround.
    • Edited by CP_28 Monday, December 26, 2011 5:51 PM
    Monday, December 26, 2011 1:10 PM