Постоянные синие экраны из-за ntoskrnl.exe

Question

Постоянно синие экраны с разными ошибками. В утилите BluesreenView пишет, что вызывает ошибку файл ntoskrnl.exe https://learn-attachment.microsoft.com/api/attachments/d0468f3b-376a-46c9-a012-0ef6fa2cf4fe?platform=QnA&fud_access=hC1SxZhn7m%2FZQJkOIiOVstu10yTQgXS4A%2FDBzZTg8nbaCgIogkrcDydMeI5Y4za2dOqDdWtsG2JNS3E35V60i9TiGHR7STMpJHheeXuDvO8nwjUlqCBHhJ0NDvuYN7OSO6g0oVd%2FGPZGf1MtLKsqsgXLt1fy7L1o5nyy1UagHvo%2B3ZBMVheCW8Zn6xdTE%2F1d3sCVuzWC%2FTo7xVwfV%2B38GJxFgKU%2BdrLoJPmV91qVAdyFhkugpTRa9f%2BBF26ywznyt3oVtRfjuqTC89A2NnFCxbwO2y9IJM%2BXeNyRSL125qvrnGVfaQaL3SqMCx5W4CsLQLGOiTe6eT8f%2FZVjRme%2FhJfCdJDxwqBNXhgO5I8Y88dhp%2FZUwmCedRM%2FxUog690UpGGsvn7EqA82tQ5XLvrOycAvUvEeSrbqiB7k6CAFC7w%3D
В просмотре событий пишет источник kernel power
Помогите избавиться с этой проблемой. Буду очень благодарен.

Answer 1

и еще скриншот

Answer 2

Вот скриншоты

Answer 3

[082624-7609-01.dmp]

UNEXPECTED_KERNEL_MODE_TRAP (7f)

This means a trap occurred in kernel mode, and it's a trap of a kind

that the kernel isn't allowed to have/catch (bound trap) or that

is always instant death (double fault). The first number in the

BugCheck params is the number of the trap (8 = double fault, etc)

Consult an Intel x86 family manual to learn more about what these

traps are. Here is a *portion* of those codes:

If kv shows a taskGate

    use .tss on the part before the colon, then kv.

Else if kv shows a trapframe

    use .trap on that value

Else

    .trap on the appropriate frame will show where the trap was taken

    (on x86, this will be the ebp that goes with the procedure KiTrap)

Endif

kb will then show the corrected stack.

Arguments:

Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT

Arg2: fffff80762690e70

Arg3: ffff8a8aa9735e90

Arg4: fffff8075f4393ab

PROCESS_NAME: explorer.exe

SYMBOL_NAME: nt!KiDoubleFaultAbort+2d2

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.4717

AILURE_BUCKET_ID: 0x7f_8_nt!KiDoubleFaultAbort

[082624-7562-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: 00000000000000e1, memory referenced

Arg2: 000000000000000d, 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: fffff80410065e50, address which referenced memory

PROCESS_NAME: System

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

FAILURE_BUCKET_ID: AV_nt!HalpTimerGetInternalData

[082624-7484-01.dmp]

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)

An attempt was made to write to readonly memory. The guilty driver is on the

stack trace (and is typically the current instruction pointer).

When possible, the guilty driver's name (Unicode string) is printed on

the BugCheck screen and saved in KiBugCheckDriver.

Arguments:

Arg1: fffff8067dfb69c0, Virtual address for the attempted write.

Arg2: 0900000003db6121, PTE contents.

Arg3: fffff8067f682db0, (reserved)

Arg4: 000000000000000a, (reserved)

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

FAILURE_BUCKET_ID: CORRUPT_MODULELIST_AV

[082624-7468-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: 0000000000000000, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000001, 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: fffff8027f45d1b2, address which referenced memory

PROCESS_NAME: chrome.exe

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

FAILURE_BUCKET_ID: AV_dxgmms2!VidSchIsVSyncEnabled

[082624-6406-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: fffff8037329cd39, The address that the exception occurred at

Arg3: 0000000000000000, Parameter 0 of the exception

Arg4: ffffffffffffffff, Parameter 1 of the exception

PROCESS_NAME: chrome.exe

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

FAILURE_BUCKET_ID: AV_R_nt!MiDecommitPages

[082624-6375-01.dmp]

APC_INDEX_MISMATCH (1)

This is a kernel internal error. The most common reason to see this

BugCheck is when a filesystem or a driver has a mismatched number of

calls to disable and re-enable APCs. The key data item is the

Thread->CombinedApcDisable field. This consists of two separate 16-bit

fields, the SpecialApcDisable and the KernelApcDisable. A negative value

of either indicates that a driver has disabled special or normal APCs

(respectively) without re-enabling them; a positive value indicates that

a driver has enabled special or normal APCs (respectively) too many times.

Arguments:

Arg1: 00007ffd5858d624, Address of system call function or worker routine

Arg2: 0000000000000000, Thread->ApcStateIndex

Arg3: 0000000000000001, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable

Arg4: fffff48179406b80, Call type (0 - system call, 1 - worker routine)

PROCESS_NAME: Discord.exe

26 errors : !USBXHCI (контроллер узла USB 3.0)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

MEMORY_CORRUPTOR: LARGE

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE

_______________________________________________________

BIOS Version F64

BIOS Release Date 06/08/2023

Manufacturer Gigabyte Technology Co., Ltd.

Product Name B450M S2H

Processor Version AMD Ryzen 5 3500X 6-Core Processor

Processor Voltage 8bh - 1.1V

External Clock 100MHz

Max Speed 4100MHz

Current Speed 3600MHz

Memory Device:

Size 8192MB

Form Factor 09h - DIMM

Device Locator DIMM 1

Bank Locator P0 CHANNEL A

Memory Type 1ah - DDR4

Speed 2400MHz

Manufacturer Kingston

Part Number KHX3000C15D4/8GX

Configured Memory Speed 2400

Minimum Voltage 1200

Maximum Voltage 1200

Configured Voltage 1200

Size 8192MB

Form Factor 09h - DIMM

Device Locator DIMM 1

Bank Locator P0 CHANNEL B

Memory Type 1ah - DDR4

Speed 2400MHz

Manufacturer Kingston

Part Number KHX3000C15D4/8GX

Configured Memory Speed 2400

Minimum Voltage 1200

Maximum Voltage 1200

Configured Voltage 1200

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

Проблемы с ядром ОС, с памятью и локально с API DirectX.

Выложите здесь скриншоты:

1. Окна Панель управления-Программы и компоненты со списком всех установленных программ.
2. Окна команды slmgr.vbs /dlv

Answer 4

Вот ссылка https://drive.google.com/drive/folders/1m5vQGhAWe7g5NYmIvj2C0ho32DK3RQ4j?usp=drive_link За минут 30 было 4 синих экрана

Answer 5

Здравствуйте.

Ошибка 41(63) в большинстве случаев указывает на наличие аппаратных (не программных) неисправностей в цепях питания, начиная с вилки/розетки/кабеля и заканчивая повреждениями компонентов микроэлектроники. Реже - некорректной работой драйверов чипсета.

Настройте систему на получение минидампов, как на рисунке внизу. После каждого сбоя будет записан отдельный дамп в папке c:\Windows\Minidump. Когда их "накопится" 3-4 шт. - залейте файлы дампов (с расширением .DMP) на какой-нибудь файлообменник, а ссылку напишите здесь. Если дампы не будут создаваться - дайте знать об этом.

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