locked
BSOD caused by ntkrnlmp.exe RRS feed

  • Question

  • HI all,

    I have Windows 7 Pro x64 sp1 installed on Toshiba R50-B-119 with i5 processor, 8GB ram, and Hdd 500Gb

    Recently I have BSOD's that are occuring 1-8 times per day, sometime it's 1-2 days break between BSOD's and often there is no BSOD, machine just crush and restart.

    I would appreciate if someone could give me a hint what could be the causing these BSODS. The problem exists on 2 machines with same specification (Toshiba R50 + Win7 Pro x64 sp1). I checked memory dumps from both machines and results are pretty the same. 


    I run WinDBG on memory dump file and results are posted below.

    STACK_TEXT:  
    fffff800`00ba06f8 fffff800`0332e740 : 00000000`0000009f 00000000`00000003 fffffa80`0bb2d070 fffff800`00ba0748 : nt!KeBugCheckEx
    fffff800`00ba0700 fffff800`032ca41c : fffff800`00ba0830 fffff800`00ba0830 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x324c0
    fffff800`00ba07a0 fffff800`032ca2b6 : fffff800`03474fe0 00000000`0016a138 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
    fffff800`00ba0810 fffff800`032ca19e : 00000035`de1b407d fffff800`00ba0e88 00000000`0016a138 fffff800`03441988 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00ba0e60 fffff800`032c9f87 : fffff800`0343eec1 fffffa80`0016a138 00000000`00000000 00000000`00000038 : nt!KiTimerExpiration+0x1be
    fffff800`00ba0f00 fffff800`032c1035 : 00000000`00000000 fffffa80`06765580 00000000`00000000 fffff880`05ee6588 : nt!KiRetireDpcList+0x277
    fffff800`00ba0fb0 fffff800`032c0e4c : fffff6fc`40004508 fffff800`0320c895 fffff800`03232460 fffff880`009a9970 : nt!KxRetireDpcList+0x5
    fffff880`009a98b0 fffff800`03309653 : fffff800`032bab40 fffff800`032babac ffffffff`ffffffff fffff880`009a9970 : nt!KiDispatchInterruptContinue
    fffff880`009a98e0 fffff800`032babac : ffffffff`ffffffff fffff880`009a9970 fffff6fc`40004508 00000000`00000040 : nt!KiDpcInterruptBypass+0x13
    fffff880`009a98f0 fffff800`033065a3 : fffff800`032811c4 00000000`00000040 00000000`0000003f fffff800`0343ee80 : nt!KiInterruptDispatchNoLock+0x1fc
    fffff880`009a9a88 fffff800`032811c4 : 00000000`00000040 00000000`0000003f fffff800`0343ee80 00000000`00000040 : nt!KeZeroPages+0x23
    fffff880`009a9a90 fffff800`03281a67 : 00000000`00117c00 00000000`0000003f 00000000`00000000 00000000`00000000 : nt!MiZeroPageChain+0xf9
    fffff880`009a9ad0 fffff800`035578e2 : fffffa80`06765580 00000000`00000080 fffffa80`06765b10 00000000`00000282 : nt!MmZeroPageThread+0x83a
    fffff880`009a9c00 fffff800`032aff46 : fffff800`0343ee80 fffffa80`06765580 fffff800`0344ccc0 084b8b48`505d8b48 : nt!PspSystemThreadStartup+0x5a
    fffff880`009a9c40 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a75c0 00000000`00000000 : nt!KxStartSystemThread+0x16


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt! ?? ::FNODOBFM::`string'+324c0
    fffff800`0332e740 cc              int     3

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+324c0

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  55a6901f

    IMAGE_VERSION:  6.1.7601.18933

    FAILURE_BUCKET_ID:  X64_0x9F_3_nt!_??_::FNODOBFM::_string_+324c0

    BUCKET_ID:  X64_0x9F_3_nt!_??_::FNODOBFM::_string_+324c0

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:x64_0x9f_3_nt!_??_::fnodobfm::_string_+324c0

    FAILURE_ID_HASH:  {92e7540c-a4dd-14a1-a425-c7144852e47c}

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

    0: kd> .trap 0x3f
    Unable to read trap frame at 00000000`0000003f
    0: kd> lmvm nt
    start             end                 module name
    fffff800`0324b000 fffff800`03836000   nt         (pdb symbols)          DownstreamStore\ntkrnlmp.pdb\6ECA9A4801E74C44A2021EA387E737FA2\ntkrnlmp.pdb
        Loaded symbol image file: ntkrnlmp.exe
        Image path: ntkrnlmp.exe
        Image name: ntkrnlmp.exe
        Timestamp:        Wed Jul 15 18:53:51 2015 (55A6901F)
        CheckSum:         00556CB2
        ImageSize:        005EB000
        File version:     6.1.7601.18933
        Product version:  6.1.7601.18933
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        1.0 App
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     ntkrnlmp.exe
        OriginalFilename: ntkrnlmp.exe
        ProductVersion:   6.1.7601.18933
        FileVersion:      6.1.7601.18933 (win7sp1_gdr.150715-0600)
        FileDescription:  NT Kernel & System
        LegalCopyright:   © Microsoft Corporation. All rights reserved.


    • Edited by Kacper_tsn Monday, August 17, 2015 10:30 AM
    Monday, August 17, 2015 10:29 AM

Answers

  • These were all Related to ftser2k.sys USB Serial Port Driver from FTDI Ltd.  Yours is from 2009

    Completely remove the current driver and install the newest driver available.  For instructions on how to do that Read all about updating drivers by my partner JMH3143 here http://answers.microsoft.com/en-us/windows/wiki/windows_other-hardware/updating-a-driver/a5e6345e-af9b-4099-bef0-8d22254aa1c1?tm=1436753520149

    Microsoft (R) Windows Debugger Version 10.0.10240.9 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\zigza\Desktop\080415-20342-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`0022ca82?
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`01a27922?
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00ba0730?
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*E:\Symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*E:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    No .natvis files found at C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers.
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18798.amd64fre.win7sp1_gdr.150316-1654
    Machine Name:
    Kernel base = 0xfffff800`03207000 PsLoadedModuleList = 0xfffff800`0344c890
    Debug session time: Tue Aug  4 08:09:17.095 2015 (UTC - 4:00)
    System Uptime: 0 days 5:51:07.880
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................................
    ..
    Loading User Symbols
    Loading unloaded module list
    ............
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {3, fffffa800bb02070, fffff80000ba0748, fffffa80117c8010}
    
    *** WARNING: Unable to verify timestamp for ftdibus.sys
    *** ERROR: Module load completed but symbols could not be loaded for ftdibus.sys
    Probably caused by : ftdibus.sys
    
    Followup:     MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver has failed to complete a power IRP within a specific time.
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa800bb02070, Physical Device Object of the stack
    Arg3: fffff80000ba0748, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: fffffa80117c8010, The blocked IRP
    
    Debugging Details:
    ------------------
    
    
    SYSTEM_SKU:  PSSG0E
    
    SYSTEM_VERSION:  PSSG0E-00700YPL
    
    BIOS_DATE:  08/19/2014
    
    BASEBOARD_PRODUCT:  Satellite Pro R50-B
    
    BASEBOARD_VERSION:  Version A0
    
    BUGCHECK_P1: 3
    
    BUGCHECK_P2: fffffa800bb02070
    
    BUGCHECK_P3: fffff80000ba0748
    
    BUGCHECK_P4: fffffa80117c8010
    
    DRVPOWERSTATE_SUBCODE:  3
    
    IMAGE_NAME:  ftdibus.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ae075df
    
    MODULE_NAME: ftdibus
    
    FAULTING_MODULE: fffff88007d99000 ftdibus
    
    CPU_COUNT: 4
    
    CPU_MHZ: 95a
    
    CPU_VENDOR:  GenuineIntel
    
    CPU_FAMILY: 6
    
    CPU_MODEL: 45
    
    CPU_STEPPING: 1
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  node.exe
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 10.0.10240.9 amd64fre
    
    DPC_STACK_BASE:  FFFFF80000BA0FB0
    
    STACK_TEXT:  
    fffff800`00ba06f8 fffff800`032e9312 : 00000000`0000009f 00000000`00000003 fffffa80`0bb02070 fffff800`00ba0748 : nt!KeBugCheckEx
    fffff800`00ba0700 fffff800`0328591c : fffff800`00ba0830 fffff800`00ba0830 00000000`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x32980
    fffff800`00ba07a0 fffff800`032857b6 : fffffa80`067d8148 fffffa80`067d8148 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
    fffff800`00ba0810 fffff800`0328569e : 00000031`0d6f7443 fffff800`00ba0e88 00000000`00149b60 fffff800`033fce88 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00ba0e60 fffff800`03285487 : fffff800`033f9ec4 fffffa80`00149b60 00000000`00000000 00000000`00000060 : nt!KiTimerExpiration+0x1be
    fffff800`00ba0f00 fffff800`0327c535 : 00000000`00000000 fffffa80`0ff91060 00000000`00000000 fffff880`05acf588 : nt!KiRetireDpcList+0x277
    fffff800`00ba0fb0 fffff800`0327c34c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
    fffff880`0c5ba140 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    FAILURE_BUCKET_ID:  X64_0x9F_3_POWER_DOWN_ftser2k_IMAGE_ftdibus.sys
    
    BUCKET_ID:  X64_0x9F_3_POWER_DOWN_ftser2k_IMAGE_ftdibus.sys
    
    PRIMARY_PROBLEM_CLASS:  X64_0x9F_3_POWER_DOWN_ftser2k_IMAGE_ftdibus.sys
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x9f_3_power_down_ftser2k_image_ftdibus.sys
    
    FAILURE_ID_HASH:  {b9241089-5764-b9d7-9d11-8a7d4fc5543c}
    
    Followup:     MachineOwner
    ---------
    
    0: kd> !irp fffffa80117c8010
    Irp is active with 4 stacks 2 is current (= 0xfffffa80117c8128)
     No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
         cmd  flg cl Device   File     Completion-Context
     [N/A(0), N/A(0)]
                0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
    >[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
                0  0 fffffa800baf2070 00000000 00000000-00000000    
    	      Unable to load image \SystemRoot\system32\drivers\ftser2k.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ftser2k.sys
    *** ERROR: Module load completed but symbols could not be loaded for ftser2k.sys
     \Driver\FTSER2K
    			Args: 00014400 00000001 00000003 00000002
     [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
                0 e1 fffffa800bb08870 00000000 00000000-00000000    pending
    	       \Driver\Serenum
    			Args: 00014400 00000001 00000003 00000002
     [N/A(0), N/A(0)]
                0  0 00000000 00000000 00000000-fffffa800c92f710    
    
    			Args: 00000000 00000000 00000000 00000000
    


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by Kacper_tsn Thursday, August 20, 2015 9:31 AM
    Tuesday, August 18, 2015 10:53 AM

All replies

  • We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  

    Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here

    .

    As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios.  

    If the issue still persists and you want to return to this question, please reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish.  

    In addition, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems.  

    Thanks!


    Arnav Sharma | http://arnavsharma.net/ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Monday, August 17, 2015 11:03 PM
  • These crashes were related to memory corruption (probably caused by a driver). 

    Please run these two tests to verify your memory and find which driver is causing the problem.  Please run verifier first.  You do not need to run memtest yet unless verifier does not find the cause, or you want to.


    If you are over-clocking anything reset to default before running these tests.
    In other words STOP!!!  If you do not know what this means you probably are not


    1-Driver verifier (for complete directions see our wiki here)

    2-Memtest. (You can read more about running memtest here)

    Wanikiya and Dyami--Team Zigzag

    Monday, August 17, 2015 11:44 PM
  • Hi,

    Sorry for the delay,

    Here's the link to mini dumps, full dump + MSInfo32

    https://onedrive.live.com/redir?resid=499D5C23CDE1AFBF!114&authkey=!AJWUBDuXA4kYo_E&ithint=folder%2c


    It's Toshiba R50-B-119
    Processor is i5-4210U (4x1.7)
    8G Ram (2x4Gb)
    Intel® HD Graphics 4400

    I didn't made any changes with clocks, it's all on default settings.

    Soft which have been used by me during that issue earlier:
    Windows 7 Pro x64 Sp1
    Komodo IDE
    Can Simulator
    Google Chrome
    node.js
    git
    M$ Lync
    Notepad++
    tkLogger



    • Edited by Kacper_tsn Tuesday, August 18, 2015 10:52 AM
    Tuesday, August 18, 2015 10:49 AM
  • I run Memtest earlier and it didn't show that anything is wrong with ram memory. It made 10 complete passes.

    I tried to make verifier and it made bsod but it disappear so fast I am unable to read anything and there is no dump file nor mini dump.

    Hardware settings are on default. I didn't change clock speed.

    Tuesday, August 18, 2015 10:51 AM
  • These were all Related to ftser2k.sys USB Serial Port Driver from FTDI Ltd.  Yours is from 2009

    Completely remove the current driver and install the newest driver available.  For instructions on how to do that Read all about updating drivers by my partner JMH3143 here http://answers.microsoft.com/en-us/windows/wiki/windows_other-hardware/updating-a-driver/a5e6345e-af9b-4099-bef0-8d22254aa1c1?tm=1436753520149

    Microsoft (R) Windows Debugger Version 10.0.10240.9 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\zigza\Desktop\080415-20342-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`0022ca82?
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`01a27922?
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00ba0730?
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*E:\Symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*E:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    No .natvis files found at C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers.
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18798.amd64fre.win7sp1_gdr.150316-1654
    Machine Name:
    Kernel base = 0xfffff800`03207000 PsLoadedModuleList = 0xfffff800`0344c890
    Debug session time: Tue Aug  4 08:09:17.095 2015 (UTC - 4:00)
    System Uptime: 0 days 5:51:07.880
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................................
    ..
    Loading User Symbols
    Loading unloaded module list
    ............
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {3, fffffa800bb02070, fffff80000ba0748, fffffa80117c8010}
    
    *** WARNING: Unable to verify timestamp for ftdibus.sys
    *** ERROR: Module load completed but symbols could not be loaded for ftdibus.sys
    Probably caused by : ftdibus.sys
    
    Followup:     MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver has failed to complete a power IRP within a specific time.
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa800bb02070, Physical Device Object of the stack
    Arg3: fffff80000ba0748, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: fffffa80117c8010, The blocked IRP
    
    Debugging Details:
    ------------------
    
    
    SYSTEM_SKU:  PSSG0E
    
    SYSTEM_VERSION:  PSSG0E-00700YPL
    
    BIOS_DATE:  08/19/2014
    
    BASEBOARD_PRODUCT:  Satellite Pro R50-B
    
    BASEBOARD_VERSION:  Version A0
    
    BUGCHECK_P1: 3
    
    BUGCHECK_P2: fffffa800bb02070
    
    BUGCHECK_P3: fffff80000ba0748
    
    BUGCHECK_P4: fffffa80117c8010
    
    DRVPOWERSTATE_SUBCODE:  3
    
    IMAGE_NAME:  ftdibus.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ae075df
    
    MODULE_NAME: ftdibus
    
    FAULTING_MODULE: fffff88007d99000 ftdibus
    
    CPU_COUNT: 4
    
    CPU_MHZ: 95a
    
    CPU_VENDOR:  GenuineIntel
    
    CPU_FAMILY: 6
    
    CPU_MODEL: 45
    
    CPU_STEPPING: 1
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  node.exe
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 10.0.10240.9 amd64fre
    
    DPC_STACK_BASE:  FFFFF80000BA0FB0
    
    STACK_TEXT:  
    fffff800`00ba06f8 fffff800`032e9312 : 00000000`0000009f 00000000`00000003 fffffa80`0bb02070 fffff800`00ba0748 : nt!KeBugCheckEx
    fffff800`00ba0700 fffff800`0328591c : fffff800`00ba0830 fffff800`00ba0830 00000000`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x32980
    fffff800`00ba07a0 fffff800`032857b6 : fffffa80`067d8148 fffffa80`067d8148 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
    fffff800`00ba0810 fffff800`0328569e : 00000031`0d6f7443 fffff800`00ba0e88 00000000`00149b60 fffff800`033fce88 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00ba0e60 fffff800`03285487 : fffff800`033f9ec4 fffffa80`00149b60 00000000`00000000 00000000`00000060 : nt!KiTimerExpiration+0x1be
    fffff800`00ba0f00 fffff800`0327c535 : 00000000`00000000 fffffa80`0ff91060 00000000`00000000 fffff880`05acf588 : nt!KiRetireDpcList+0x277
    fffff800`00ba0fb0 fffff800`0327c34c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
    fffff880`0c5ba140 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    FAILURE_BUCKET_ID:  X64_0x9F_3_POWER_DOWN_ftser2k_IMAGE_ftdibus.sys
    
    BUCKET_ID:  X64_0x9F_3_POWER_DOWN_ftser2k_IMAGE_ftdibus.sys
    
    PRIMARY_PROBLEM_CLASS:  X64_0x9F_3_POWER_DOWN_ftser2k_IMAGE_ftdibus.sys
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x9f_3_power_down_ftser2k_image_ftdibus.sys
    
    FAILURE_ID_HASH:  {b9241089-5764-b9d7-9d11-8a7d4fc5543c}
    
    Followup:     MachineOwner
    ---------
    
    0: kd> !irp fffffa80117c8010
    Irp is active with 4 stacks 2 is current (= 0xfffffa80117c8128)
     No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
         cmd  flg cl Device   File     Completion-Context
     [N/A(0), N/A(0)]
                0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
    >[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
                0  0 fffffa800baf2070 00000000 00000000-00000000    
    	      Unable to load image \SystemRoot\system32\drivers\ftser2k.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ftser2k.sys
    *** ERROR: Module load completed but symbols could not be loaded for ftser2k.sys
     \Driver\FTSER2K
    			Args: 00014400 00000001 00000003 00000002
     [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
                0 e1 fffffa800bb08870 00000000 00000000-00000000    pending
    	       \Driver\Serenum
    			Args: 00014400 00000001 00000003 00000002
     [N/A(0), N/A(0)]
                0  0 00000000 00000000 00000000-fffffa800c92f710    
    
    			Args: 00000000 00000000 00000000 00000000
    


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by Kacper_tsn Thursday, August 20, 2015 9:31 AM
    Tuesday, August 18, 2015 10:53 AM
  • Thanks a lot, It seems that application Ferrari that works as COM simulator has those drivers and it crashes the system, I updated it to latest version and now wait to see whats going to happen. Once more Thanks a lot for help.
    Thursday, August 20, 2015 9:33 AM