Синий экран в случайный момент времени с разными кодами ошибок

Question

Синий экран вылетает во время работы браузера. Но он у меня запущен постоянно, так что это сомнительный(?) показатель. Чаще всего вылетает когда параллельно с браузером, я во что-то играю, но пару раз было исключительно во время просмотра видео. Пару раз видел, как сначала крашится страница в браузере, а потом и синий экран вылетает.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

FAULTY_HARDWARE_CORRUPTED_PAGE (12b)
This BugCheck indicates that a single bit error was found in this page.  This is a hardware memory error.
Arguments:
Arg1: ffffffffc00002c4, virtual address mapping the corrupted page
Arg2: 0000000000000c8b, physical page number
Arg3: 000002aabecfca50, zero
Arg4: ffff8b00ee1c5000, zero

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 00000000002ac7f2, page frame number
Arg3: 0000000000000002, current page state
Arg4: 0200035000359ff1, 0

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: fffffffffffff010, 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: fffff8007fb66ef7, address which referenced memory

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure.  The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 000000000000001d, An RTL_BALANCED_NODE RBTree entry has been corrupted.
Arg2: ffff850728baee80, Address of the trap frame for the exception that caused the BugCheck
Arg3: ffff850728baedd8, Address of the exception record for the exception that caused the BugCheck
Arg4: 0000000000000000, Reserved

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: ffffa9800dd05c88, 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: fffff8045273ec91, address which referenced memory

Answer 1

Файлы дампа:
https://drive.google.com/drive/folders/1ENRgO-2lVT-S18w2aaZdXKdnI7DnSFVv?usp=sharing

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

Анализ дампов показывает, что на Вашем компьютере довольно высокая вероятность наличия аппаратных проблем с памятью, и возможно есть проблемы с драйверами:

On Thu 21.03.2024 16:41:59 your computer crashed or a problem was reported

Crash dump file: C:\TMP\DUMP\032124-14437-01.dmp (Minidump)

Bugcheck code: 0x4E(0x99, 0x2AC7F2, 0x2, 0x200035000359FF1)

Bugcheck name: PFN_LIST_CORRUPT

Bug check description: This indicates that the page frame number (PFN) list is corrupted.

Analysis: This is possibly a software problem. This is likely a case of memory corruption.

Memory corruption can be caused by a faulty driver, faulty RAM, overheating and more. Read this article on memory corruption. Read this article on thermal issues

On Thu 21.03.2024 18:12:01 your computer crashed or a problem was reported

Crash dump file: C:\TMP\DUMP\032124-13000-01 (1).dmp (Minidump)

Bugcheck code: 0x12B(0xFFFFFFFFC00002C4, 0xC8B, 0x2AABECFCA50, 0xFFFF8B00EE1C5000)

Bugcheck name: FAULTY_HARDWARE_CORRUPTED_PAGE

Bug check description: This bug check indicates that a single-bit error was found in this page. This is a hardware memory error.

Analysis: This is possibly a software problem. This is likely a case of memory corruption.

Memory corruption can be caused by a faulty driver, faulty RAM, overheating and more. Read this article on memory corruption. Read this article on thermal issues

On Thu 21.03.2024 18:12:01 your computer crashed or a problem was reported

Crash dump file: C:\TMP\DUMP\032124-13000-01.dmp (Minidump)

Bugcheck code: 0x12B(0xFFFFFFFFC00002C4, 0xC8B, 0x2AABECFCA50, 0xFFFF8B00EE1C5000)

Bugcheck name: FAULTY_HARDWARE_CORRUPTED_PAGE

Bug check description: This bug check indicates that a single-bit error was found in this page. This is a hardware memory error.

Analysis: This is possibly a software problem. This is likely a case of memory corruption.

Memory corruption can be caused by a faulty driver, faulty RAM, overheating and more. Read this article on memory corruption. Read this article on thermal issues

On Wed 20.03.2024 22:29:31 your computer crashed or a problem was reported

Crash dump file: C:\TMP\DUMP\032024-17781-01.dmp (Minidump)

Bugcheck code: 0xA(0xFFFFFFFFFFFFF010, 0x2, 0x0, 0xFFFFF8007FB66EF7)

Bugcheck name: IRQL_NOT_LESS_OR_EQUAL

Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.

Analysis: This is a typical software problem. Most likely this is caused by a bug in a driver.

On Wed 20.03.2024 4:57:12 your computer crashed or a problem was reported

Crash dump file: C:\TMP\DUMP\032024-17562-01.dmp (Minidump)

Bugcheck code: 0x139(0x1D, 0xFFFF850728BAEE80, 0xFFFF850728BAEDD8, 0x0)

Bugcheck name: KERNEL_SECURITY_CHECK_FAILURE

Bug check description: The kernel has detected the corruption of a critical data structure.

Analysis: This particular bugcheck may be caused by malware or a security product that does not follow programming guidelines. This can also be caused by memory corruption. This is possibly a software problem. There is a possibility that this is caused by memory corruption. Memory corruption can be caused by a faulty driver, faulty RAM, overheating and more. Read this article on memory corruption. Read this article on thermal issues

On Mon 18.03.2024 23:55:40 your computer crashed or a problem was reported

Crash dump file: C:\TMP\DUMP\031824-19812-01.dmp (Minidump)

Bugcheck code: 0xA(0xFFFFA9800DD05C88, 0x2, 0x0, 0xFFFFF8045273EC91)

Bugcheck name: IRQL_NOT_LESS_OR_EQUAL

Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.

Analysis: This is a typical software problem. Most likely this is caused by a bug in a driver.

Попробуйте загрузить и установить все необходимые для Вашего компьютера драйвера с официального сайта технической поддержки производителя Вашего компьютера.

Если после чистой переустановки драйверов проблема останется, то обратитесь в авторизованный сервис, для диагностики и, возможно, ремонта Вашего компьютера.

Answer 2

Файлы дампа:
https://drive.google.com/drive/folders/1ENRgO-2lVT-S18w2aaZdXKdnI7DnSFVv?usp=sharing