Имя пользователя:
Пароль:  
Помощь | Регистрация | Забыли пароль?  

Название темы: 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Показать сообщение отдельно

Пользователь


Сообщения: 149
Благодарности: 9

Профиль | Отправить PM | Цитировать


Доброго дня, в последнее время стал часто появляться BSOD при загрузке компа (на логотипе). Со 2-го раза комп стартует и в процессе работы проблем нет.
Из интересного - винда стоит на SSD Samsung Pro 850 (прошивка последняя), и в системе стоит WinRamTech RAMDisk, где лежит кэш хрома. Из последнего, что делал с компом - установил teamviewer последний.
Начал с теста накопителей и памяти - всё в порядке. Может есть идеи что дальше делать?
Анализ дампа ниже.
WinDbg
Код: Выделить весь код
WARNING: Whitespace at start of path element

Loading Dump File [D:\HOME_061318-10530-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at start of path element
Symbol search path is: srv*; 
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23915.amd64fre.win7sp1_ldr.170913-0600
Machine Name:
Kernel base = 0xfffff800`04813000 PsLoadedModuleList = 0xfffff800`04a55750
Debug session time: Wed Jun 13 17:16:41.175 2018 (UTC + 3:00)
System Uptime: 0 days 0:00:09.424
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, 0, 8, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiDispatchException+1c7 )

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

1: 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: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000008, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>

FAULTING_IP: 
+6665373539313531
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000008

EXCEPTION_PARAMETER2:  0000000000000000

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80004abf100
 0000000000000000 

ERROR_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>

BUGCHECK_STR:  0x1E_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

EXCEPTION_RECORD:  fffff880063fc7b8 -- (.exr 0xfffff880063fc7b8)
ExceptionAddress: 0000000000000000
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000008
   Parameter[1]: 0000000000000000
Attempt to execute non-executable address 0000000000000000

TRAP_FRAME:  fffff880063fc860 -- (.trap 0xfffff880063fc860)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000100 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff88003769750 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=fffff880063fc9f0 rbp=0000000000000000
 r8=fffffa80096f49c0  r9=000000000000000d r10=fffff80004813000
r11=fffff880063fc6f0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
00000000`00000000 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800048c0107 to fffff80004883e00

STACK_TEXT:  
fffff880`063fbfe8 fffff800`048c0107 : 00000000`0000001e ffffffff`c0000005 00000000`00000000 00000000`00000008 : nt!KeBugCheckEx
fffff880`063fbff0 fffff800`0488348e : fffff880`063fc7b8 00000000`10000004 fffff880`063fc860 00000000`00000000 : nt!KiDispatchException+0x1c7
fffff880`063fc680 fffff800`04881ffa : 00000000`00000008 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xce
fffff880`063fc860 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiDispatchException+1c7
fffff800`048c0107 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiDispatchException+1c7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  59b946d1

FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!KiDispatchException+1c7

BUCKET_ID:  X64_0x1E_c0000005_nt!KiDispatchException+1c7

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

Отправлено: 15:40, 14-06-2018 | #239

Название темы: 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED