[080624-11140-01.dmp]
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: fffff8042e04e96b, The address that the exception occurred at
Arg3: ffffffffffffffff, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
PROCESS_NAME: System
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.4355
FAILURE_BUCKET_ID: AV_nt!PpmIdlePrepare
[080624-10718-01.dmp]
IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000001, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8064044bb2c, address which referenced memory
PROCESS_NAME: System
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
FAILURE_BUCKET_ID: AV_nt!PoIdle
[080624-10109-01.dmp]
RQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000860, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000024, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8035060d7fc, address which referenced memory
*** WARNING: Check Image - Checksum mismatch - Dump: 0x3f5b5, File: 0x43ab9 - C:\ProgramData\Dbg\sym\intelppm.sys\3E03C5E841000\intelppm.sys
PROCESS_NAME: System
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
FAILURE_BUCKET_ID: AV_nt!KiPageFault
[080624-9859-01.dmp]
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff8066502c2ca, Address of the instruction which caused the BugCheck
Arg3: fffffe06d5205950, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.
PROCESS_NAME: ctfmon.exe
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
FAILURE_BUCKET_ID: AV_nt!IopCloseFile
..........................................................
Дампы указывают на некорректную работу ядра ОС, связанную с ошибками с доступом к страницам памяти и обработкой прерываний. Вероятно повреждение ядра либо в результате его изменения, либо под влиянием стороннего ПО.
Выложите здесь скриншоты:
- Окна Панель управления-Программы и компоненты со списком всех установленных программ.
- Окна команды slmgr.vbs /dlv