PFN_LIST_CORRUPT mavi ekran hatası

Ekran kartınızın sürücüsünü DDU ile kaldırıp WHQL sürümünü kurun. Onun dışında özellikle bir hata göremedim. Yine mavi ekran alırsanız yeni minidump dosyalarını paylaşın.
 
Kim size ASrock A320 anakart sattı?

RAM testi yapın:


Kod:
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: 0000000000119a91, page frame number
Arg3: 0000000000000002, current page state
Arg4: 0e0003c0003c1690, 0

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2608

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-1IBQR0U

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 8795

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 74

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: 19h1_release

    Key  : WER.OS.Timestamp
    Value: 2019-03-18T12:02:00Z

    Key  : WER.OS.Version
    Value: 10.0.18362.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  4e

BUGCHECK_P1: 99

BUGCHECK_P2: 119a91

BUGCHECK_P3: 2

BUGCHECK_P4: e0003c0003c1690

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
ffffe981`f6bbd9a8 fffff802`4ec09343     : 00000000`0000004e 00000000`00000099 00000000`00119a91 00000000`00000002 : nt!KeBugCheckEx
ffffe981`f6bbd9b0 fffff802`4ea694a4     : ffffe400`00000000 fffff802`4ee6a340 00000000`00000000 ffffa32e`1a025ba0 : nt!MiDecrementShareCount+0x19fbd3
ffffe981`f6bbd9f0 fffff802`4eb5eedd     : 810cfebc`f5a004c0 00000000`00000001 00000000`00000000 ffffe400`0b5ba800 : nt!MiRestoreTransitionPte+0x194
ffffe981`f6bbda60 fffff802`4eb5ec65     : 00000000`00000000 ffffe400`0b4a3d10 00000000`00002000 00000000`00000002 : nt!MiRemoveLowestPriorityStandbyPage+0x1bd
ffffe981`f6bbdb00 fffff802`4eb5e748     : ffff810c`f5aa0b20 00000000`00000007 ffff810c`00000000 ffff810c`f5aa7d70 : nt!MiPurgePartitionStandby+0x49
ffffe981`f6bbdb40 fffff802`4ea83965     : ffff810c`fc00a040 fffff802`4eb5e700 ffff810c`f5a74cb0 00000000`00000000 : nt!MiFinishResume+0x48
ffffe981`f6bbdb70 fffff802`4eb1e155     : ffff810c`fc00a040 00000000`00000080 ffff810c`f5a76300 00000000`00000001 : nt!ExpWorkerThread+0x105
ffffe981`f6bbdc10 fffff802`4ebc99c8     : ffffb881`53ac0180 ffff810c`fc00a040 fffff802`4eb1e100 00000000`00200246 : nt!PspSystemThreadStartup+0x55
ffffe981`f6bbdc60 00000000`00000000     : ffffe981`f6bbe000 ffffe981`f6bb8000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  nt!MiDecrementShareCount+19fbd3

MODULE_NAME: nt

IMAGE_VERSION:  10.0.18362.1016

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  19fbd3

FAILURE_BUCKET_ID:  0x4E_99_nt!MiDecrementShareCount

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {add373c4-2fe4-723e-d1db-12fcb6adef02}

Followup:     MachineOwner
---------

4: kd> !sysinfo machineid
Machine ID Information [From Smbios 3.2, DMIVersion 0, Size=1348]
BiosMajorRelease = 5
BiosMinorRelease = 14
BiosVendor = American Megatrends Inc.
BiosVersion = P4.00
BiosReleaseDate = 07/16/2020
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
SystemFamily = To Be Filled By O.E.M.
SystemVersion = To Be Filled By O.E.M.
SystemSKU = To Be Filled By O.E.M.
BaseBoardManufacturer = ASRock
BaseBoardProduct = A320M-HDV R4.0
BaseBoardVersion =                       
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: 0000050000000000, The address that the exception occurred at
Arg3: 0000000000000008, Parameter 0 of the exception
Arg4: 0000050000000000, Parameter 1 of the exception

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5140

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-1IBQR0U

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 39377

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 75

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: 50000000000

BUGCHECK_P3: 8

BUGCHECK_P4: 50000000000

WRITE_ADDRESS: fffff80543cfa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80543c0f2f0: Unable to get Flags value from nt!KdVersionBlock
fffff80543c0f2f0: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
 0000050000000000

EXCEPTION_PARAMETER1:  0000000000000008

EXCEPTION_PARAMETER2:  0000050000000000

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  csgo.exe

TRAP_FRAME:  ffffd1033ba67b50 -- (.trap 0xffffd1033ba67b50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffd1033ba67d10 rbx=0000000000000000 rcx=fffff80551dbe950
rdx=fffff80551d8fdc8 rsi=0000000000000000 rdi=0000000000000000
rip=0000050000000000 rsp=ffffd1033ba67ce8 rbp=ffffd1033ba67d61
 r8=0000000000000008  r9=0000000000000007 r10=fffff80543317bf0
r11=ffffe607ed7a8260 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
00000500`00000000 ??              ???
Resetting default scope

STACK_TEXT: 
ffffd103`3ba672a8 fffff805`4342efc5     : 00000000`0000001e ffffffff`c0000005 00000500`00000000 00000000`00000008 : nt!KeBugCheckEx
ffffd103`3ba672b0 fffff805`433eff6c     : ffffd103`3ba67bd0 00000000`00001000 ffffd103`3ba67b50 ffff8000`00000000 : nt!KiDispatchException+0x1b4955
ffffd103`3ba67970 fffff805`433ec103     : ffffc108`23f53dc0 fffff805`51f89a70 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x12c
ffffd103`3ba67b50 00000500`00000000     : 00000001`000003c0 ffffd103`3ba67e88 00000001`00000000 ffffd103`3ba67d10 : nt!KiPageFault+0x443
ffffd103`3ba67ce8 00000001`000003c0     : ffffd103`3ba67e88 00000001`00000000 ffffd103`3ba67d10 00000000`00000000 : 0x00000500`00000000
ffffd103`3ba67cf0 ffffd103`3ba67e88     : 00000001`00000000 ffffd103`3ba67d10 00000000`00000000 00000000`00000000 : 0x00000001`000003c0
ffffd103`3ba67cf8 00000001`00000000     : ffffd103`3ba67d10 00000000`00000000 00000000`00000000 00000000`0fa6c000 : 0xffffd103`3ba67e88
ffffd103`3ba67d00 ffffd103`3ba67d10     : 00000000`00000000 00000000`00000000 00000000`0fa6c000 ffffd103`3ba67db8 : 0x00000001`00000000
ffffd103`3ba67d08 00000000`00000000     : 00000000`00000000 00000000`0fa6c000 ffffd103`3ba67db8 00000000`00000008 : 0xffffd103`3ba67d10


SYMBOL_NAME:  nt!KiDispatchException+1b4955

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.450

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1b4955

FAILURE_BUCKET_ID:  0x1E_c0000005_X_nt!KiDispatchException

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {72b01280-60ea-6404-b5e3-077cb4799617}

Followup:     MachineOwner
---------
 
Uyarı! Bu konu 6 yıl önce açıldı.
Muhtemelen daha fazla tartışma gerekli değildir ki bu durumda yeni bir konu başlatmayı öneririz. Eğer yine de cevabınızın gerekli olduğunu düşünüyorsanız buna rağmen cevap verebilirsiniz.

Bu konuyu görüntüleyen kullanıcılar

Technopat Haberler

Yeni konular

Geri
Yukarı