witam od miesiąca walczę z problemem bsod dokładniej z memory menagement, system service exception, pfn list corrupt.
Próbowałem pełno metod nic nie działa. Mam najnowszy bios sterowniki zaktualizowałem przełożyłem ram z 2 i 4 gniazdka na 1 i 3 nie wiem co mogę jeszcze zrobić przesyłam również specyfikacje i dane z aplikacji whocrashed. Najczęściej bsod pojawia się jak gram w jakąś grę i po grze włączam przeglądarkę google ale również częściej po prostu wywala mi gry najczęściej w valorant albo w jakieś bardziej wymagające.
System Information (local)
Computer name: DESKTOP-UPDEIAG
Windows version: Windows 10, 10.0, version 2009, build: 19043
Windows dir: C:\WINDOWS
Hardware: Z390 UD, Gigabyte Technology Co., Ltd.
CPU: GenuineIntel Intel(R) Core(TM) i5-9400F CPU @ 2.90GHz 8664, level: 6
6 logical processors, active mask: 63
RAM: 17108201472 bytes (15,9GB)
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Sat 09.10.2021 21:46:49 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\100921-10000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F71C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8063EDF667B, 0xFFFFF00B1E1DE800, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 09.10.2021 21:46:49 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x8259)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8063EDF667B, 0xFFFFF00B1E1DE800, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 09.10.2021 17:15:45 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\100921-9812-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F71C0)
Bugcheck code: 0x1A (0x403, 0xFFFFFE80B1859478, 0x81000004A5AFD867, 0xFFFFFE80B131A018)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred. The page table and PFNs are out of sync . This is probably a hardware error, especially if parameters 3 & 4 differ by only a single bit.
This is likely to be caused by a hardware problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test) and make sure your system is not getting overheated. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 08.10.2021 18:45:23 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\100821-12343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F71C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80225728127, 0xFFFFB408399FE660, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 08.10.2021 18:39:08 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\100821-12656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F71C0)
Bugcheck code: 0x4E (0x99, 0x4131B7, 0x2, 0x6000410004131B6)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 07.10.2021 21:52:53 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\100721-12703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F71C0)
Bugcheck code: 0x1A (0x9696, 0xFFFF900007374F60, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.