Постоянные BSOD с разными ошибками

Основная причина (остальные так, "мелочи"...) это "лекарство" пиратского Офиса LTSC про плюс. На него "реагирует" ядро ОС. Увы, но исправить можно только чистой установкой системы из под BIOS, с удалением всех разделов на системном жестком диске (удаление Офиса и попытка восстановления ОС без переустановки не сработают).

По самой ОС необходимо тоже уточнить. Запустите PowerShell от имени Администратора и выполните команду

wmic path softwarelicensingservice get oa3xoriginalproductkey

(лучше через скопировать/вставить, чтоб не ошибиться при наборе вручную).

Напишите, какой будет результат (сами данные публиковать не надо).

вот скрины

[040125-25984-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: fffff80073239f88, The address that the exception occurred at

Arg3: 0000000000000000, Parameter 0 of the exception

Arg4: ffffe4723905be18, Parameter 1 of the exception

PROCESS_NAME: chrome.exe

MODULE_NAME: nt

IMAGE_VERSION: 10.0.19041.5607

IMAGE_NAME: ntkrnlmp.exe

FAILURE_BUCKET_ID: AV_R_nt!MiUserFault

[040125-22968-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: 0000000000000002, 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: fffff8023a653857, address which referenced memory

PROCESS_NAME: chrome.exe

MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD.sys

FAILURE_BUCKET_ID: IP_MISALIGNED_AuthenticAMD.sys

[033125-23062-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: 0000000e24cbb991, memory referenced

Arg2: 0000000000000002, 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: fffff8044165782b, address which referenced memory

PROCESS_NAME: msedge.exe

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

FAILURE_BUCKET_ID: AV_nt!KiInsertTimerTable

[033125-22781-01.dmp]

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

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 kernel debugger is available get stack backtrace.

Arguments:

Arg1: 0000000000000057, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000001, value 0 = read operation, 1 = write operation

Arg4: fffff80797822686, address which referenced memory

PROCESS_NAME: System

IMAGE_NAME: hardware

ODULE_NAME: hardware

FAILURE_BUCKET_ID: IP_MISALIGNED_rtwlane.sys

[033025-22609-01.dmp]

PAGE_FAULT_IN_NONPAGED_AREA (50)

Invalid system memory was referenced. This cannot be protected by try-except.

Typically the address is just plain bad or it is pointing at freed memory.

Arguments:

Arg1: ffffec04f06027d0, memory referenced.

Arg2: 0000000000000000, X64: bit 0 set if the fault was due to a not-present PTE.

bit 1 is set if the fault was due to a write, clear if a read. 

bit 3 is set if the processor decided the fault was due to a corrupted PTE. 

bit 4 is set if the fault was due to attempted execute of a no-execute PTE. 

- ARM64: bit 1 is set if the fault was due to a write, clear if a read. 

bit 3 is set if the fault was due to attempted execute of a no-execute PTE. 

Arg3: fffff80141411327, If non-zero, the instruction address which referenced the bad memory

address. 

Arg4: 0000000000000002, (reserved)

PROCESS_NAME: VALORANT.exe

MODULE_NAME: vgk (Timestamp: Wed Mar 19 19:43:23 2025)

IMAGE_NAME: vgk.sys

FAILURE_BUCKET_ID: AV_R_(null)_vgk!unknown_function

_____________________

ВIOS Version FA506IU.320

Vendor American Megatrends Inc.

BIOS Release Date 06/01/2022

Manufacturer ASUSTeK COMPUTER INC.

Product Name ASUS TUF Gaming A15 FA506IU_TUF506IU

Version 1.0

Serial Number M4NRCXKK002T

Chassis Type Notebook

Physical Memory:

Size 8192MB

Form Factor 0dh - SODIMM

Device Locator DIMM 0

Bank Locator P0 CHANNEL A

Memory Type 1ah - DDR4

Type Detail 4080h - Synchronous Unbuffered (Unregistered)

Speed 3200MHz

Manufacturer Micron Technology

Part Number 4ATF1G64HZ-3G2E1

Size 8192MB

Form Factor 0dh - SODIMM

Device Locator DIMM 0

Bank Locator P0 CHANNEL B

Memory Type 1ah - DDR4

Type Detail 4080h - Synchronous Unbuffered (Unregistered)

Speed 3200MHz

Manufacturer Micron Technology

Part Number 4ATF1G64HZ-3G2E1

Configured Memory Speed 3200

Minimum Voltage 1200

Maximum Voltage 1200

Configured Voltage 1200

Configured Memory Speed 3200

Minimum Voltage 1200

Maximum Voltage 1200

Configured Voltage 1200

Processor Version AMD Ryzen 7 4800H with Radeon Graphics

Processor Voltage 8ch - 1.2V

External Clock 100MHz

Max Speed 4300MHz

Current Speed 2900MHz

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

1. Сбои ядра ОС. Могут быть вызваны повреждением/видоизменением ядра, либо влиянием стороннего ПО.
2. Сбои в работе драйвера процессора/чипсета при обработке прерываний. Могут быть вызваны как ошибкой самого драйвера, так и аппаратной неисправностью (последнее маловероятно, но нельзя исключать).
3. Аппаратный сбой/неисправность сетевой карты Realtek/
4. "Работа" драйвера античита Riot Vanguard. Синие экраны при его использовании наблюдаются у многих пользователей.

Как видите - проблем много и они разнообразные... Начнем с программных. Выложите здесь скриншоты:

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

Дампы загрузил. Как будут результаты анализа - напишу.

Minidump.rar
вот по пробуйте