none
KMODE_EXCEPTION_NOT_HANDLED RRS feed

  • Вопрос

  • Добрый день!

    Прошу помощи. На компьютере стал регулярно вылезать BSOD. В чем причина? Самостоятельный поиск ничего не дал.

    ссылка на дамп: https://www.sendspace.com/file/oq567h

    ............

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {ffffffffc0000005, ffffe0003844a36e, 0, 1010}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3aa31 )
    
    Followup:     MachineOwner
    ---------
    
    nt!KeBugCheckEx:
    fffff803`6af62ca0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffd000`22ac5630=000000000000001e
    3: 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: ffffffffc0000005, The exception code that was not handled
    Arg2: ffffe0003844a36e, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 0000000000001010, Parameter 1 of the exception
    
    Debugging Details:
    ------------------
    
    
    KEY_VALUES_STRING: 1
    
    
    STACKHASH_ANALYSIS: 1
    
    TIMELINE_ANALYSIS: 1
    
    
    DUMP_CLASS: 1
    
    DUMP_QUALIFIER: 401
    
    BUILD_VERSION_STRING:  9600.17736.amd64fre.winblue_r9.150322-1500
    
    SYSTEM_MANUFACTURER:  Hewlett-Packard
    
    SYSTEM_PRODUCT_NAME:  HP EliteBook 750 G1
    
    SYSTEM_SKU:  J8Q57EA#ACB
    
    SYSTEM_VERSION:  A3009DD10303
    
    BIOS_VENDOR:  Hewlett-Packard
    
    BIOS_VERSION:  L71 Ver. 01.20
    
    BIOS_DATE:  07/28/2014
    
    BASEBOARD_MANUFACTURER:  Hewlett-Packard
    
    BASEBOARD_PRODUCT:  198F
    
    BASEBOARD_VERSION:  KBC Version 15.55
    
    DUMP_TYPE:  1
    
    BUGCHECK_P1: ffffffffc0000005
    
    BUGCHECK_P2: ffffe0003844a36e
    
    BUGCHECK_P3: 0
    
    BUGCHECK_P4: 1010
    
    READ_ADDRESS:  0000000000001010 
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>
    
    FAULTING_IP: 
    +0
    ffffe000`3844a36e 493313          xor     rdx,qword ptr [r11]
    
    EXCEPTION_PARAMETER2:  0000000000001010
    
    BUGCHECK_STR:  0x1E_c0000005_R
    
    CPU_COUNT: 4
    
    CPU_MHZ: 95a
    
    CPU_VENDOR:  GenuineIntel
    
    CPU_FAMILY: 6
    
    CPU_MODEL: 45
    
    CPU_STEPPING: 1
    
    CPU_MICROCODE: 6,45,1,0 (F,M,S,R)  SIG: 1C'00000000 (cache) 1C'00000000 (init)
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    PROCESS_NAME:  csrss.exe
    
    CURRENT_IRQL:  0
    
    ANALYSIS_SESSION_HOST:  PCS-000402
    
    ANALYSIS_SESSION_TIME:  06-07-2018 10:41:55.0238
    
    ANALYSIS_VERSION: 10.0.17674.1000 amd64fre
    
    TRAP_FRAME:  ffffd00022ac5f00 -- (.trap 0xffffd00022ac5f00)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000001390 rbx=0000000000000000 rcx=000000000000000f
    rdx=7300d804ae6fb427 rsi=0000000000000000 rdi=0000000000000000
    rip=ffffe0003844a36e rsp=ffffd00022ac6090 rbp=ffffd00022ac6100
     r8=0000000000000378  r9=fffff960004e9000 r10=0000000000000378
    r11=0000000000001010 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na po nc
    ffffe000`3844a36e 493313          xor     rdx,qword ptr [r11] ds:00000000`00001010=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff8036afadbf1 to fffff8036af62ca0
    
    STACK_TEXT:  
    ffffd000`22ac5628 fffff803`6afadbf1 : 00000000`0000001e ffffffff`c0000005 ffffe000`3844a36e 00000000`00000000 : nt!KeBugCheckEx
    ffffd000`22ac5630 fffff803`6af6e8c2 : ffffe000`3b596040 ffffd000`22ac5dc0 00000000`00000000 fffff803`6ae653a7 : nt! ?? ::FNODOBFM::`string'+0x3aa31
    ffffd000`22ac5d20 fffff803`6af6d014 : 00000000`00000000 00000000`0000006f fffff800`5eeccf00 00000000`00000009 : nt!KiExceptionDispatch+0xc2
    ffffd000`22ac5f00 ffffe000`3844a36e : fffff803`00000000 ffffc000`7f003000 fffff803`6b4d11e0 00000000`00000000 : nt!KiPageFault+0x214
    ffffd000`22ac6090 fffff803`00000000 : ffffc000`7f003000 fffff803`6b4d11e0 00000000`00000000 00000000`00000000 : 0xffffe000`3844a36e
    ffffd000`22ac6098 ffffc000`7f003000 : fffff803`6b4d11e0 00000000`00000000 00000000`00000000 00000000`00000002 : 0xfffff803`00000000
    ffffd000`22ac60a0 fffff803`6b4d11e0 : 00000000`00000000 00000000`00000000 00000000`00000002 ffffe000`3b7c8268 : 0xffffc000`7f003000
    ffffd000`22ac60a8 00000000`00000000 : 00000000`00000000 00000000`00000002 ffffe000`3b7c8268 fffff800`5c0bb452 : nt!PspActiveProcessLock
    
    
    THREAD_SHA1_HASH_MOD_FUNC:  a6ce12fbef8e79dcedf276841a498743609c6521
    
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  c4d2f1d6c7ffb13f6b0114090af477fb5e9ec1b0
    
    THREAD_SHA1_HASH_MOD:  f08ac56120cad14894587db086f77ce277bfae84
    
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+3aa31
    fffff803`6afadbf1 cc              int     3
    
    FAULT_INSTR_CODE:  7886f7cc
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+3aa31
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  550f41a6
    
    STACK_COMMAND:  .thread ; .cxr ; kb
    
    BUCKET_ID_FUNC_OFFSET:  3aa31
    
    FAILURE_BUCKET_ID:  0x1E_c0000005_R_nt!_??_::FNODOBFM::_string_
    
    BUCKET_ID:  0x1E_c0000005_R_nt!_??_::FNODOBFM::_string_
    
    PRIMARY_PROBLEM_CLASS:  0x1E_c0000005_R_nt!_??_::FNODOBFM::_string_
    
    TARGET_TIME:  2018-06-06T12:20:47.000Z
    
    OSBUILD:  9600
    
    OSSERVICEPACK:  0
    
    SERVICEPACK_NUMBER: 0
    
    OS_REVISION: 0
    
    SUITE_MASK:  272
    
    PRODUCT_TYPE:  1
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 8.1
    
    OSEDITION:  Windows 8.1 WinNt TerminalServer SingleUserTS
    
    OS_LOCALE:  
    
    USER_LCID:  0
    
    OSBUILD_TIMESTAMP:  2015-03-23 01:26:46
    
    BUILDDATESTAMP_STR:  150322-1500
    
    BUILDLAB_STR:  winblue_r9
    
    BUILDOSVER_STR:  6.3.9600.17736.amd64fre.winblue_r9.150322-1500
    
    ANALYSIS_SESSION_ELAPSED_TIME:  742
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0x1e_c0000005_r_nt!_??_::fnodobfm::_string_
    
    FAILURE_ID_HASH:  {8fc04943-cbe8-d7c5-c06f-9b7efeebfcb7}
    
    Followup:     MachineOwner
    ---------


    • Изменено 3abotin 7 июня 2018 г. 8:59 добавил ссылку

Ответы

  • Обновите все драйвера в системе, и проверьте ваш HDD на ошибки, подозреваю, что проблема в нем. Если посмотреть smart счетчики, что показывает?
    • Помечено в качестве ответа Anton Sashev Ivanov 26 июня 2018 г. 11:29
    7 июня 2018 г. 19:28