Dell Inspiron 15 3521 blue screen of death - General Hardware - Laptop - Dell Community

Dell Inspiron 15 3521 blue screen of death

Laptop

Laptop
Laptop computer Forums (Audio, General Hardware, Video)

Dell Inspiron 15 3521 blue screen of death

This question is not answered

Hi,

Over the past few weeks I've gotten the same blue screen error. It says 'Driver_IRQL_not_less_or_equal (Smb Driver Intel.sys). I've just been browsing the internet while i'm doing this.

I'm not sure what additional info is needed but i'm running the Windows 8 that the laptop came with, it's a brand new laptop (only around a month old and not refurbished) and i'm running Norton Security Suite as my antivirus. Also the last time this happened i tried updating my BIOS and obviously it didn't fix the issue.

All Replies
  • Hi MV1228,

    This error is due to incompatible drivers installed for some hardware on the system. Please perform the system restore on the system to previous state when the operating system was working fine. Please follow the steps mentioned below to perform the system restore on the system

    1. Swipe in from the right edge of the screen, and then tap Search.
      (If you're using a mouse, point to the upper-right corner of the screen, move the mouse pointer down, and then click Search.) Enter Recovery in the search box, tap or click Settings, and then tap or click Recovery.
    2. Tap or click Open System Restore, and follow the prompts.

    Please let me know if this helps.

  • Actually, I have the same issue. But it is happening with a brand new Inspiron 15, so no way to go to a previous version.

    What is the best version to use?

  • Hi Peter,

    Please provide details of the BSOD, inc Stop Error etc as per screen shot below

      

    Details of the minidump file would be handy too. 

    http://forums.lenovo.com/t5/General-Discussion-Knowledge/What-is-Minidump-What-is-it-used-for/ta-p/324485

    Robin

  • Hi Peter Stevens,

    As suggested by Paul please let us know the BSOD error so that we can assist you further.

    Also, I would suggest that you run the diagnostics on the computer by following the steps mentioned below and check if there is any issue with the hardware on your system.

    1. Turn on or restart the computer.
    2. Immediately at the Dell logo screen, starting tapping the <F12> key once a second until the One Time Boot menu appears (if the computer boots to Windows turn the computer off and try again).
    3. At the One Time Boot menu, press the <Down> arrow key to highlight Diagnostics, PSA+ or Enter ePSA, then press <Enter> to begin the hardware Diagnostics.
    4. Write down any error codes listed. Reply to us with the error codes.
  • Happened to me too laptop has 2 months

    This is what the crash dump contains

    *******************************************************************************

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

    *******************************************************************************

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

    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.

    Arguments:

    Arg1: 0000000000000000, memory referenced

    Arg2: 0000000000000008, IRQL

    Arg3: 0000000000000001, value 0 = read operation, 1 = write operation

    Arg4: fffff880053cb167, address which referenced memory

    Debugging Details:

    ------------------

    Page 249fbe not present in the dump file. Type ".hh dbgerr004" for details

    WRITE_ADDRESS:  0000000000000000

    CURRENT_IRQL:  8

    FAULTING_IP:

    Smb_driver_Intel+4167

    fffff880`053cb167 408830          mov     byte ptr [rax],sil

    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

    BUGCHECK_STR:  AV

    PROCESS_NAME:  System

    TAG_NOT_DEFINED_c000000f:  FFFFF88002E95FB0

    TRAP_FRAME:  fffff88002e8e880 -- (.trap 0xfffff88002e8e880)

    NOTE: The trap frame does not contain all registers.

    Some register values may be zeroed or incorrect.

    rax=0000000000000000 rbx=0000000000000000 rcx=00000000ffffffe0

    rdx=0000000000004040 rsi=0000000000000000 rdi=0000000000000000

    rip=fffff880053cb167 rsp=fffff88002e8ea10 rbp=0000000000000000

    r8=fffff880053ce190  r9=fffff8038849bb00 r10=fffffa800af3c7d0

    r11=0000000000000010 r12=0000000000000000 r13=0000000000000000

    r14=0000000000000000 r15=0000000000000000

    iopl=0         nv up ei ng nz na pe nc

    Smb_driver_Intel+0x4167:

    fffff880`053cb167 408830          mov     byte ptr [rax],sil ds:00000000`00000000=??

    Resetting default scope

    EXCEPTION_RECORD:  fffff88002e65180 -- (.exr 0xfffff88002e65180)

    ExceptionAddress: fffffa80087155c0

      ExceptionCode: 00001f80

     ExceptionFlags: 01000002

    NumberParameters: 48696896

      Parameter[0]: 0000000200000001

      Parameter[1]: fffff88002e8ec90

      Parameter[2]: 0000000000000000

      Parameter[3]: 0000000000000000

      Parameter[4]: 0000000080050033

      Parameter[5]: 0000000000000000

      ParameterDevil: 0000000000187000

      Parameter[7]: 00000000001526f8

      ParameterMusic: 0000000000000000

      Parameter[9]: 0000000000000000

      Parameter[10]: 0000000000000000

      Parameter[11]: 0000000000000000

      Parameter[12]: 00000000ffff4ff0

      Parameter[13]: 0000000000000400

      Parameter[14]: 007f000000000000

    LAST_CONTROL_TRANSFER:  from fffff80388261769 to fffff80388262440

    STACK_TEXT:  

    fffff880`02e8e738 fffff803`88261769 : 00000000`0000000a 00000000`00000000 00000000`00000008 00000000`00000001 : nt!KeBugCheckEx

    fffff880`02e8e740 fffff803`8825ffe0 : 00000000`00000001 fffffa80`0ad11b30 ffff7118`ff277600 fffff880`02e8e880 : nt!KiBugCheckDispatch+0x69

    fffff880`02e8e880 fffff880`053cb167 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260

    fffff880`02e8ea10 fffff880`053c8fd2 : 0000057f`f50f31b8 fffff880`02e8eb50 fffffa80`0ad11ae0 fffff880`033d4900 : Smb_driver_Intel+0x4167

    fffff880`02e8ea60 fffff880`0109d7a3 : 0000057f`f50f31b8 fffff880`033d4900 ffff5de1`3658e939 fffffa80`08779710 : Smb_driver_Intel+0x1fd2

    fffff880`02e8ea90 fffff803`8825ac76 : fffff880`02e65180 fffff880`02e65180 fffff880`02e8eb50 fffffa80`08779010 : Wdf01000!FxInterrupt::_InterruptThunk+0xcf

    fffff880`02e8ead0 fffff803`8828b992 : fffff880`02e65180 fffff880`02e65180 00000000`00000000 fffff880`02e70e40 : nt!KiInterruptDispatch+0x1d6

    fffff880`02e8ec60 00000000`00000000 : fffff880`02e8f000 fffff880`02e89000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x32

    STACK_COMMAND:  kb

    FOLLOWUP_IP:

    Smb_driver_Intel+4167

    fffff880`053cb167 408830          mov     byte ptr [rax],sil

    SYMBOL_STACK_INDEX:  3

    SYMBOL_NAME:  Smb_driver_Intel+4167

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: Smb_driver_Intel

    IMAGE_NAME:  Smb_driver_Intel.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  50d3fb27

    FAILURE_BUCKET_ID:  AV_Smb_driver_Intel+4167

    BUCKET_ID:  AV_Smb_driver_Intel+4167

    Followup: MachineOwner

    ---------

  • @Inspiron15r5521

    Re-install the Touchpad drivers

    www.dell.com/.../inspiron-15r-5521

    Robin

  • Re-Installed from the link you gave me
    passed some days and now i got this:


    Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\082713-21015-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 8 Kernel Version 9200 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 9200.16628.amd64fre.win8_gdr.130531-1504
    Machine Name:
    Kernel base = 0xfffff802`5d018000 PsLoadedModuleList = 0xfffff802`5d2e4a20
    Debug session time: Mon Aug 26 23:01:25.956 2013 (UTC + 2:00)
    System Uptime: 0 days 4:28:47.659
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ........................................
    Loading User Symbols
    Loading unloaded module list
    .......................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000007E, {ffffffffc0000005, fffff880010d1861, fffff880009de1f8, fffff880009dda30}

    *** WARNING: Unable to verify timestamp for Smb_driver_Intel.sys
    *** ERROR: Module load completed but symbols could not be loaded for Smb_driver_Intel.sys
    Probably caused by : Smb_driver_Intel.sys ( Smb_driver_Intel+1ef3 )

    Followup: MachineOwner
    ---------

    2: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    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: fffff880010d1861, The address that the exception occurred at
    Arg3: fffff880009de1f8, Exception Record Address
    Arg4: fffff880009dda30, Context Record Address

    Debugging Details:
    ------------------


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a 0x%08lx ha fatto riferimento alla memoria a 0x%08lx. La memoria non poteva essere %s.

    FAULTING_IP:
    Wdf01000!FxRequest::CompleteInternal+21
    fffff880`010d1861 498b9db8000000 mov rbx,qword ptr [r13+0B8h]

    EXCEPTION_RECORD: fffff880009de1f8 -- (.exr 0xfffff880009de1f8)
    ExceptionAddress: fffff880010d1861 (Wdf01000!FxRequest::CompleteInternal+0x0000000000000021)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 0000000000000000
    Parameter[1]: 00000000000000b8
    Attempt to read from address 00000000000000b8

    CONTEXT: fffff880009dda30 -- (.cxr 0xfffff880009dda30)
    rax=0000000000000000 rbx=fffffa80073dc020 rcx=fffffa80073dc020
    rdx=00000000c0000120 rsi=0000000000000000 rdi=fffffa80090f6c40
    rip=fffff880010d1861 rsp=fffff880009de430 rbp=00000000c0000120
    r8=00000000c0000120 r9=fffff780000003b0 r10=fffffa8009196010
    r11=0000000000000000 r12=0000057ff8c23fd8 r13=0000000000000000
    r14=0000000000000000 r15=fffffa8009196010
    iopl=0 nv up ei pl zr na po nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
    Wdf01000!FxRequest::CompleteInternal+0x21:
    fffff880`010d1861 498b9db8000000 mov rbx,qword ptr [r13+0B8h] ds:002b:00000000`000000b8=????????????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 1

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    ERROR_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a 0x%08lx ha fatto riferimento alla memoria a 0x%08lx. La memoria non poteva essere %s.

    EXCEPTION_PARAMETER1: 0000000000000000

    EXCEPTION_PARAMETER2: 00000000000000b8

    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8025d370168
    GetUlongFromAddress: unable to read from fffff8025d3701f8
    00000000000000b8 Nonpaged pool

    FOLLOWUP_IP:
    Smb_driver_Intel+1ef3
    fffff880`0730fef3 ?? ???

    BUGCHECK_STR: AV

    DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

    LAST_CONTROL_TRANSFER: from fffff880010e4b02 to fffff880010d1861

    STACK_TEXT:
    fffff880`009de430 fffff880`010e4b02 : fffffa80`090b85b0 fffff880`010c63c0 fffffa80`090b85b0 fffffa80`073dc020 : Wdf01000!FxRequest::CompleteInternal+0x21
    fffff880`009de4c0 fffff880`0730fef3 : fffffa80`073dc020 fffffa80`090f6ef0 00000000`00000000 0000057f`f8c23fd8 : Wdf01000!imp_WdfRequestComplete+0x176
    fffff880`009de520 fffffa80`073dc020 : fffffa80`090f6ef0 00000000`00000000 0000057f`f8c23fd8 fffffa80`090c6c50 : Smb_driver_Intel+0x1ef3
    fffff880`009de528 fffffa80`090f6ef0 : 00000000`00000000 0000057f`f8c23fd8 fffffa80`090c6c50 fffff880`010dfa22 : 0xfffffa80`073dc020
    fffff880`009de530 00000000`00000000 : 0000057f`f8c23fd8 fffffa80`090c6c50 fffff880`010dfa22 00000000`00000000 : 0xfffffa80`090f6ef0


    SYMBOL_STACK_INDEX: 2

    SYMBOL_NAME: Smb_driver_Intel+1ef3

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: Smb_driver_Intel

    IMAGE_NAME: Smb_driver_Intel.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 50d3fb27

    STACK_COMMAND: .cxr 0xfffff880009dda30 ; kb

    FAILURE_BUCKET_ID: AV_Smb_driver_Intel+1ef3

    BUCKET_ID: AV_Smb_driver_Intel+1ef3

    Followup: MachineOwner
    ---------

    2: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    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: fffff880010d1861, The address that the exception occurred at
    Arg3: fffff880009de1f8, Exception Record Address
    Arg4: fffff880009dda30, Context Record Address

    Debugging Details:
    ------------------


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a 0x%08lx ha fatto riferimento alla memoria a 0x%08lx. La memoria non poteva essere %s.

    FAULTING_IP:
    Wdf01000!FxRequest::CompleteInternal+21
    fffff880`010d1861 498b9db8000000 mov rbx,qword ptr [r13+0B8h]

    EXCEPTION_RECORD: fffff880009de1f8 -- (.exr 0xfffff880009de1f8)
    ExceptionAddress: fffff880010d1861 (Wdf01000!FxRequest::CompleteInternal+0x0000000000000021)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 0000000000000000
    Parameter[1]: 00000000000000b8
    Attempt to read from address 00000000000000b8

    CONTEXT: fffff880009dda30 -- (.cxr 0xfffff880009dda30)
    rax=0000000000000000 rbx=fffffa80073dc020 rcx=fffffa80073dc020
    rdx=00000000c0000120 rsi=0000000000000000 rdi=fffffa80090f6c40
    rip=fffff880010d1861 rsp=fffff880009de430 rbp=00000000c0000120
    r8=00000000c0000120 r9=fffff780000003b0 r10=fffffa8009196010
    r11=0000000000000000 r12=0000057ff8c23fd8 r13=0000000000000000
    r14=0000000000000000 r15=fffffa8009196010
    iopl=0 nv up ei pl zr na po nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
    Wdf01000!FxRequest::CompleteInternal+0x21:
    fffff880`010d1861 498b9db8000000 mov rbx,qword ptr [r13+0B8h] ds:002b:00000000`000000b8=????????????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 1

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    ERROR_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a 0x%08lx ha fatto riferimento alla memoria a 0x%08lx. La memoria non poteva essere %s.

    EXCEPTION_PARAMETER1: 0000000000000000

    EXCEPTION_PARAMETER2: 00000000000000b8

    READ_ADDRESS: 00000000000000b8 Nonpaged pool

    FOLLOWUP_IP:
    Smb_driver_Intel+1ef3
    fffff880`0730fef3 ?? ???

    BUGCHECK_STR: AV

    DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

    LAST_CONTROL_TRANSFER: from fffff880010e4b02 to fffff880010d1861

    STACK_TEXT:
    fffff880`009de430 fffff880`010e4b02 : fffffa80`090b85b0 fffff880`010c63c0 fffffa80`090b85b0 fffffa80`073dc020 : Wdf01000!FxRequest::CompleteInternal+0x21
    fffff880`009de4c0 fffff880`0730fef3 : fffffa80`073dc020 fffffa80`090f6ef0 00000000`00000000 0000057f`f8c23fd8 : Wdf01000!imp_WdfRequestComplete+0x176
    fffff880`009de520 fffffa80`073dc020 : fffffa80`090f6ef0 00000000`00000000 0000057f`f8c23fd8 fffffa80`090c6c50 : Smb_driver_Intel+0x1ef3
    fffff880`009de528 fffffa80`090f6ef0 : 00000000`00000000 0000057f`f8c23fd8 fffffa80`090c6c50 fffff880`010dfa22 : 0xfffffa80`073dc020
    fffff880`009de530 00000000`00000000 : 0000057f`f8c23fd8 fffffa80`090c6c50 fffff880`010dfa22 00000000`00000000 : 0xfffffa80`090f6ef0


    SYMBOL_STACK_INDEX: 2

    SYMBOL_NAME: Smb_driver_Intel+1ef3

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: Smb_driver_Intel

    IMAGE_NAME: Smb_driver_Intel.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 50d3fb27

    STACK_COMMAND: .cxr 0xfffff880009dda30 ; kb

    FAILURE_BUCKET_ID: AV_Smb_driver_Intel+1ef3

    BUCKET_ID: AV_Smb_driver_Intel+1ef3

    Followup: MachineOwner
    ---------

    2: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    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: fffff880010d1861, The address that the exception occurred at
    Arg3: fffff880009de1f8, Exception Record Address
    Arg4: fffff880009dda30, Context Record Address

    Debugging Details:
    ------------------


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a 0x%08lx ha fatto riferimento alla memoria a 0x%08lx. La memoria non poteva essere %s.

    FAULTING_IP:
    Wdf01000!FxRequest::CompleteInternal+21
    fffff880`010d1861 498b9db8000000 mov rbx,qword ptr [r13+0B8h]

    EXCEPTION_RECORD: fffff880009de1f8 -- (.exr 0xfffff880009de1f8)
    ExceptionAddress: fffff880010d1861 (Wdf01000!FxRequest::CompleteInternal+0x0000000000000021)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 0000000000000000
    Parameter[1]: 00000000000000b8
    Attempt to read from address 00000000000000b8

    CONTEXT: fffff880009dda30 -- (.cxr 0xfffff880009dda30)
    rax=0000000000000000 rbx=fffffa80073dc020 rcx=fffffa80073dc020
    rdx=00000000c0000120 rsi=0000000000000000 rdi=fffffa80090f6c40
    rip=fffff880010d1861 rsp=fffff880009de430 rbp=00000000c0000120
    r8=00000000c0000120 r9=fffff780000003b0 r10=fffffa8009196010
    r11=0000000000000000 r12=0000057ff8c23fd8 r13=0000000000000000
    r14=0000000000000000 r15=fffffa8009196010
    iopl=0 nv up ei pl zr na po nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
    Wdf01000!FxRequest::CompleteInternal+0x21:
    fffff880`010d1861 498b9db8000000 mov rbx,qword ptr [r13+0B8h] ds:002b:00000000`000000b8=????????????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 1

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    ERROR_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a 0x%08lx ha fatto riferimento alla memoria a 0x%08lx. La memoria non poteva essere %s.

    EXCEPTION_PARAMETER1: 0000000000000000

    EXCEPTION_PARAMETER2: 00000000000000b8

    READ_ADDRESS: 00000000000000b8 Nonpaged pool

    FOLLOWUP_IP:
    Smb_driver_Intel+1ef3
    fffff880`0730fef3 ?? ???

    BUGCHECK_STR: AV

    DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

    LAST_CONTROL_TRANSFER: from fffff880010e4b02 to fffff880010d1861

    STACK_TEXT:
    fffff880`009de430 fffff880`010e4b02 : fffffa80`090b85b0 fffff880`010c63c0 fffffa80`090b85b0 fffffa80`073dc020 : Wdf01000!FxRequest::CompleteInternal+0x21
    fffff880`009de4c0 fffff880`0730fef3 : fffffa80`073dc020 fffffa80`090f6ef0 00000000`00000000 0000057f`f8c23fd8 : Wdf01000!imp_WdfRequestComplete+0x176
    fffff880`009de520 fffffa80`073dc020 : fffffa80`090f6ef0 00000000`00000000 0000057f`f8c23fd8 fffffa80`090c6c50 : Smb_driver_Intel+0x1ef3
    fffff880`009de528 fffffa80`090f6ef0 : 00000000`00000000 0000057f`f8c23fd8 fffffa80`090c6c50 fffff880`010dfa22 : 0xfffffa80`073dc020
    fffff880`009de530 00000000`00000000 : 0000057f`f8c23fd8 fffffa80`090c6c50 fffff880`010dfa22 00000000`00000000 : 0xfffffa80`090f6ef0


    SYMBOL_STACK_INDEX: 2

    SYMBOL_NAME: Smb_driver_Intel+1ef3

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: Smb_driver_Intel

    IMAGE_NAME: Smb_driver_Intel.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 50d3fb27

    STACK_COMMAND: .cxr 0xfffff880009dda30 ; kb

    FAILURE_BUCKET_ID: AV_Smb_driver_Intel+1ef3

    BUCKET_ID: AV_Smb_driver_Intel+1ef3

    Followup: MachineOwner
    ---------

  • Looks like the touch pad drivers are causing a conflict again.

    Try the Synaptics driver

    http://www.synaptics.com/resources/drivers/

    Alternatively, it could well be another driver conflicting with the touch pad driver, in which case you will need to ensure all your other hardware drivers are up to date.

    Robin