PUBG oynarken PAGE_FAULT_IN_NONPAGED_AREA (50) mavi ekran hatası

X

xunqui

Uzman
Katılım
28 Ocak 2025
Mesajlar
105
Çözümler
1
Beğeniler
44
  • Anakart: MSI Z790 Gaming Plus Wi-Fi
  • İşlemci: i7-14700KF
  • Ekran kartı: RTX 4070 Ti.
  • İşletim sistemi: Windows 10.
Merhaba. Sadece PUBG oynarken mavi ekran oluyor başka oyunlarda bu sorunu yaşamıyorum. Ayrıca Intel Extreme Tuning Utility üzerinden automatic overclock ayarını açık şekilde kullanıyorum. Ne zaman mavi ekran yesem automatic overclock ayarı kendiliğinden kapanıyor. Bu ayarla alakalı olabileceğini düşündüğüm için belirtmek istedim. Şimdiden yardımcı olacak arkadaşlara teşekkür ederim.

 
Son düzenleyen: Moderatör:
Tarihe göre sırala Puana göre sırala
Son düzenleyen: Moderatör:
Artı 0 Eksi
Bu sorun ilk gün ortaya çıkan bir durum değil kimisi 6 ay kimisi daha uzun süre sonra çıkabiliyor. Ama siz yine de değişim için uğraşın bence.
 
Artı 0 Eksi
Tüm dosyalarda sorun BattlEye anti cheat sürücüsü olarak gözüküyor. Öncelikle AC'i güncelleyip sistemini kontrol etmeni isteyeceğim. Sorun devam ederse güncel dosyalarınızı tekrar paylaşın.

Rich (BB code): 
2: kd> lmvmBEDaisy
Browse full module list
start end module name
fffff807`6c000000 fffff807`6c53f000 BEDaisy T (no symbols)
 Loaded symbol image file: BEDaisy.sys
 Image path: BEDaisy.sys
 Image name: BEDaisy.sys
 Browse all global symbols functions data
 Timestamp: Wed Oct 9 06:15:06 2024 (6705F53A)
 CheckSum: 00540AE4
 ImageSize: 0053F000
 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
 Information from resource tables:
 
Artı 0 Eksi

AC'i manuel olarak güncelleyemem fakat oyunu sil yükle yapabilirim aynı işlemi görmüş olur mu?
 
Artı 0 Eksi
Oyun yerine AC'i bulunduğu konumdan silerek ve tekrar oyuna girerek sil/yükle yapmış olacaksın. AC'i bu hataya yapılan OC ayarı da itiyor olabilir. Bunu unutma.
 
Artı 0 Eksi
bicy dedi:
Oyun yerine AC'i bulunduğu konumdan silerek ve tekrar oyuna girerek sil/yükle yapmış olacaksın. AC'i bu hataya yapılan OC ayarı da itiyor olabilir. Bunu unutma.
Genişletmek için tıkla...

Dediğiniz gibi yaptım, deniyorum. Yaklaşık 4-5 saat aralıksız oynamam gerekiyor, daha az oynarsam mavi ekran vermiyor. Ayrıca OC ayarı açık konumdayken yüzde bir ve binde bir değerleri daha iyi olduğu için oyunlar daha akıcı oluyor ve gözle görülür şekilde FPS artıyor. Sırf bu sebepten ötürü bu ayarı kullanıyorum.

bicy dedi:
Oyun yerine AC'i bulunduğu konumdan silerek ve tekrar oyuna girerek sil/yükle yapmış olacaksın. AC'i bu hataya yapılan OC ayarı da itiyor olabilir. Bunu unutma.
Genişletmek için tıkla...

Hocam tekrardan merhaba. AC dosyasını sildim ve otomatik overclock ayarını devre dışı bıraktım sonuç hala aynı tekrar mavi ekran yedim:


Oyunda değilken 2 sefer daha yedim.

@Recep Baltaş hocam bir yardımcı olma şansınız var mı? 1 seneden fazladır sorunsuz kullandığım sistem son bir haftadır mavi ekran vermeye başladı. Özellikle Steam PUBG oyununu oynarken bu durum daha fazla oluyor.
 
Son düzenleyen: Moderatör:
Artı 0 Eksi
Bütün hatalar RAM'e işaret ediyor gibi. Bir Memtes86 ile bellek testi yapar mısın?

Kod: 
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: fffff80507c53132, memory referenced.
Arg2: 0000000000000010, 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: fffff80507c53132, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, (reserved)

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


KEY_VALUES_STRING: 1

    Key  : AV.Type
    Value: Execute

    Key  : Analysis.CPU.mSec
    Value: 734

    Key  : Analysis.Elapsed.mSec
    Value: 4181

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 265

    Key  : Analysis.Init.Elapsed.mSec
    Value: 3975

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27829.1001

    Key  : Analysis.Version.Description
    Value: 10.2503.24.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2503.24.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x50

    Key  : Bugcheck.Code.TargetModel
    Value: 0x50

    Key  : Dump.Attributes.AsUlong
    Value: 0x8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: AV_X_(null)_BAD_IP_nt!MiSystemFault

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff80507c53132

    Key  : Failure.Hash
    Value: {519102ae-339f-c953-2278-3f0bfcf5aa85}


BUGCHECK_CODE:  50

BUGCHECK_P1: fffff80507c53132

BUGCHECK_P2: 10

BUGCHECK_P3: fffff80507c53132

BUGCHECK_P4: 0

FILE_IN_CAB:  061925-9218-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffff8407d0a170c0

READ_ADDRESS: fffff802314fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 fffff80507c53132

MM_INTERNAL_CODE:  0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

FAILED_INSTRUCTION_ADDRESS:
+0
fffff805`07c53132 ??              ???

STACK_TEXT: 
ffffd300`b94f55c8 fffff802`30c5143b     : 00000000`00000050 fffff805`07c53132 00000000`00000010 ffffd300`b94f5870 : nt!KeBugCheckEx
ffffd300`b94f55d0 fffff802`30a0df40     : ffff8407`00000000 00000000`00000010 ffffd300`b94f58f0 00000000`00000000 : nt!MiSystemFault+0x19273b
ffffd300`b94f56d0 fffff802`30c0e06d     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : nt!MmAccessFault+0x400
ffffd300`b94f5870 fffff805`07c53132     : fffff802`30b22fe0 fffff802`bb5e0000 ffffd482`445fc000 ffffd482`445fc000 : nt!KiPageFault+0x36d
ffffd300`b94f5a00 fffff802`30b22fdf     : fffff802`bb5e0000 ffffd482`445fc000 ffffd482`445fc000 00000000`8bec2f0e : 0xfffff805`07c53132
ffffd300`b94f5a08 fffff802`bb5e0000     : ffffd482`445fc000 ffffd482`445fc000 00000000`8bec2f0e 00000000`0000000b : nt!SepMatchCapability+0x63
ffffd300`b94f5a10 ffffd482`445fc000     : ffffd482`445fc000 00000000`8bec2f0e 00000000`0000000b 00000000`00040283 : kbdhid!WPP_RECORDER_SF_ <PERF> (kbdhid+0x0)
ffffd300`b94f5a18 ffffd482`445fc000     : 00000000`8bec2f0e 00000000`0000000b 00000000`00040283 ffffd300`b94f5db0 : 0xffffd482`445fc000
ffffd300`b94f5a20 00000000`8bec2f0e     : 00000000`0000000b 00000000`00040283 ffffd300`b94f5db0 fffff802`30800000 : 0xffffd482`445fc000
ffffd300`b94f5a28 00000000`0000000b     : 00000000`00040283 ffffd300`b94f5db0 fffff802`30800000 00000000`00000001 : 0x8bec2f0e
ffffd300`b94f5a30 00000000`00040283     : ffffd300`b94f5db0 fffff802`30800000 00000000`00000001 00000000`00000000 : 0xb
ffffd300`b94f5a38 ffffd300`b94f5db0     : fffff802`30800000 00000000`00000001 00000000`00000000 0000b082`445fcc70 : 0x40283
ffffd300`b94f5a40 fffff802`30800000     : 00000000`00000001 00000000`00000000 0000b082`445fcc70 00000000`00000000 : 0xffffd300`b94f5db0
ffffd300`b94f5a48 00000000`00000001     : 00000000`00000000 0000b082`445fcc70 00000000`00000000 fffff780`000003b0 : nt!VrpRegistryString <PERF> (nt+0x0)
ffffd300`b94f5a50 00000000`00000000     : 0000b082`445fcc70 00000000`00000000 fffff780`000003b0 ffff8408`2f2939b0 : 0x1


SYMBOL_NAME:  nt!MiSystemFault+19273b

MODULE_NAME: nt

IMAGE_VERSION:  10.0.19041.5965

STACK_COMMAND: .process /r /p 0xffff8407cb0de080; .thread 0xffff8407d0a170c0 ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  19273b

FAILURE_BUCKET_ID:  AV_X_(null)_BAD_IP_nt!MiSystemFault

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {519102ae-339f-c953-2278-3f0bfcf5aa85}

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: fffff8077f09ff2f, memory referenced.
Arg2: 0000000000000010, 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: fffff8077f09ff2f, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, (reserved)

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


KEY_VALUES_STRING: 1

    Key  : AV.Type
    Value: Execute

    Key  : Analysis.CPU.mSec
    Value: 687

    Key  : Analysis.Elapsed.mSec
    Value: 2276

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 375

    Key  : Analysis.Init.Elapsed.mSec
    Value: 4056

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27829.1001

    Key  : Analysis.Version.Description
    Value: 10.2503.24.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2503.24.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x50

    Key  : Bugcheck.Code.TargetModel
    Value: 0x50

    Key  : Dump.Attributes.AsUlong
    Value: 0x8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: AV_X_(null)_BAD_IP_nt!MiSystemFault

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff8077f09ff2f

    Key  : Failure.Hash
    Value: {519102ae-339f-c953-2278-3f0bfcf5aa85}


BUGCHECK_CODE:  50

BUGCHECK_P1: fffff8077f09ff2f

BUGCHECK_P2: 10

BUGCHECK_P3: fffff8077f09ff2f

BUGCHECK_P4: 0

FILE_IN_CAB:  062425-10609-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffff8904715cb080

READ_ADDRESS: fffff80463efb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 fffff8077f09ff2f

MM_INTERNAL_CODE:  0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  TslGame.exe

FAILED_INSTRUCTION_ADDRESS:
+0
fffff807`7f09ff2f ??              ???

STACK_TEXT: 
fffffe8e`651ceee8 fffff804`6365143b     : 00000000`00000050 fffff807`7f09ff2f 00000000`00000010 fffffe8e`651cf190 : nt!KeBugCheckEx
fffffe8e`651ceef0 fffff804`6340df40     : 00000000`00000861 00000000`00000010 fffffe8e`651cf210 00000000`00000000 : nt!MiSystemFault+0x19273b
fffffe8e`651ceff0 fffff804`6360e06d     : fffffe8e`00000000 00000000`00000000 00000000`00000000 00000000`00000003 : nt!MmAccessFault+0x400
fffffe8e`651cf190 fffff807`7f09ff2f     : ffff8904`715cb080 00000000`000000d8 92fd30c8`b7df3521 fffffe8e`651cf6d0 : nt!KiPageFault+0x36d
fffffe8e`651cf320 ffff8904`715cb080     : 00000000`000000d8 92fd30c8`b7df3521 fffffe8e`651cf6d0 00000000`00013938 : 0xfffff807`7f09ff2f
fffffe8e`651cf328 00000000`000000d8     : 92fd30c8`b7df3521 fffffe8e`651cf6d0 00000000`00013938 eba36be5`b5f50000 : 0xffff8904`715cb080
fffffe8e`651cf330 92fd30c8`b7df3521     : fffffe8e`651cf6d0 00000000`00013938 eba36be5`b5f50000 00000000`00000000 : 0xd8
fffffe8e`651cf338 fffffe8e`651cf6d0     : 00000000`00013938 eba36be5`b5f50000 00000000`00000000 fffffe8e`651cf6d0 : 0x92fd30c8`b7df3521
fffffe8e`651cf340 00000000`00013938     : eba36be5`b5f50000 00000000`00000000 fffffe8e`651cf6d0 eba36be5`b5f50000 : 0xfffffe8e`651cf6d0
fffffe8e`651cf348 eba36be5`b5f50000     : 00000000`00000000 fffffe8e`651cf6d0 eba36be5`b5f50000 00000000`00000001 : 0x13938
fffffe8e`651cf350 00000000`00000000     : fffffe8e`651cf6d0 eba36be5`b5f50000 00000000`00000001 00000000`ffffffff : 0xeba36be5`b5f50000


SYMBOL_NAME:  nt!MiSystemFault+19273b

MODULE_NAME: nt

IMAGE_VERSION:  10.0.19041.5965

STACK_COMMAND: .process /r /p 0xffff8904652dc080; .thread 0xffff8904715cb080 ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  19273b

FAILURE_BUCKET_ID:  AV_X_(null)_BAD_IP_nt!MiSystemFault

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {519102ae-339f-c953-2278-3f0bfcf5aa85}

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: fffff802ce94a131, memory referenced.
Arg2: 0000000000000010, 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: fffff802ce94a131, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, (reserved)

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


KEY_VALUES_STRING: 1

    Key  : AV.Type
    Value: Execute

    Key  : Analysis.CPU.mSec
    Value: 781

    Key  : Analysis.Elapsed.mSec
    Value: 2808

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 375

    Key  : Analysis.Init.Elapsed.mSec
    Value: 4044

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27829.1001

    Key  : Analysis.Version.Description
    Value: 10.2503.24.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2503.24.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x50

    Key  : Bugcheck.Code.TargetModel
    Value: 0x50

    Key  : Dump.Attributes.AsUlong
    Value: 0x8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: AV_X_(null)_BAD_IP_nt!MiSystemFault

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff802ce94a131

    Key  : Failure.Hash
    Value: {519102ae-339f-c953-2278-3f0bfcf5aa85}


BUGCHECK_CODE:  50

BUGCHECK_P1: fffff802ce94a131

BUGCHECK_P2: 10

BUGCHECK_P3: fffff802ce94a131

BUGCHECK_P4: 0

FILE_IN_CAB:  061525-13546-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffde0c3b9ba040

READ_ADDRESS: fffff80210cfb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 fffff802ce94a131

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  TslGame.exe

FAILED_INSTRUCTION_ADDRESS:
+0
fffff802`ce94a131 ??              ???

STACK_TEXT: 
ffff8289`0acf6ee8 fffff802`1045143b     : 00000000`00000050 fffff802`ce94a131 00000000`00000010 ffff8289`0acf7190 : nt!KeBugCheckEx
ffff8289`0acf6ef0 fffff802`1020df40     : 00000000`00000861 00000000`00000010 ffff8289`0acf7210 00000000`00000000 : nt!MiSystemFault+0x19273b
ffff8289`0acf6ff0 fffff802`1040e06d     : ffff8289`00000000 00000000`00000000 00000000`00000000 00000000`00000003 : nt!MmAccessFault+0x400
ffff8289`0acf7190 fffff802`ce94a131     : 00000000`00000000 00000000`00000101 00000000`00000001 00000000`00000000 : nt!KiPageFault+0x36d
ffff8289`0acf7320 00000000`00000000     : 00000000`00000101 00000000`00000001 00000000`00000000 00000001`4022b4f2 : 0xfffff802`ce94a131


SYMBOL_NAME:  nt!MiSystemFault+19273b

MODULE_NAME: nt

IMAGE_VERSION:  10.0.19041.5965

STACK_COMMAND: .process /r /p 0xffffde0c28f02080; .thread 0xffffde0c3b9ba040 ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  19273b

FAILURE_BUCKET_ID:  AV_X_(null)_BAD_IP_nt!MiSystemFault

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {519102ae-339f-c953-2278-3f0bfcf5aa85}

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

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: fffff8065a49ff2f, memory referenced.
Arg2: 0000000000000010, 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: fffff8065a49ff2f, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

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


KEY_VALUES_STRING: 1

    Key  : AV.Type
    Value: Execute

    Key  : Analysis.CPU.mSec
    Value: 718

    Key  : Analysis.Elapsed.mSec
    Value: 4011

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 343

    Key  : Analysis.Init.Elapsed.mSec
    Value: 3988

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27829.1001

    Key  : Analysis.Version.Description
    Value: 10.2503.24.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2503.24.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x50

    Key  : Bugcheck.Code.TargetModel
    Value: 0x50

    Key  : Dump.Attributes.AsUlong
    Value: 0x8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: AV_X_(null)_BAD_IP_nt!MiSystemFault

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff8065a49ff2f

    Key  : Failure.Hash
    Value: {519102ae-339f-c953-2278-3f0bfcf5aa85}


BUGCHECK_CODE:  50

BUGCHECK_P1: fffff8065a49ff2f

BUGCHECK_P2: 10

BUGCHECK_P3: fffff8065a49ff2f

BUGCHECK_P4: 2

FILE_IN_CAB:  062725-10265-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffe68af27fb040

READ_ADDRESS: fffff8022e4fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 fffff8065a49ff2f

MM_INTERNAL_CODE:  2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  TslGame.exe

FAILED_INSTRUCTION_ADDRESS:
+0
fffff806`5a49ff2f ??              ???

STACK_TEXT: 
fffffd05`e9b84ee8 fffff802`2dc5118b     : 00000000`00000050 fffff806`5a49ff2f 00000000`00000010 fffffd05`e9b85190 : nt!KeBugCheckEx
fffffd05`e9b84ef0 fffff802`2da0df40     : 00000000`00000861 00000000`00000010 fffffd05`e9b85210 00000000`00000000 : nt!MiSystemFault+0x19248b
fffffd05`e9b84ff0 fffff802`2dc0e06d     : fffffd05`00000000 00000000`00000000 00000000`00000000 00000000`00000003 : nt!MmAccessFault+0x400
fffffd05`e9b85190 fffff806`5a49ff2f     : ffffe68a`f27fb040 00000000`000000d6 ac71908e`7dfeb93b fffffd05`e9b856d0 : nt!KiPageFault+0x36d
fffffd05`e9b85320 ffffe68a`f27fb040     : 00000000`000000d6 ac71908e`7dfeb93b fffffd05`e9b856d0 00000000`00007948 : 0xfffff806`5a49ff2f
fffffd05`e9b85328 00000000`000000d6     : ac71908e`7dfeb93b fffffd05`e9b856d0 00000000`00007948 9bf2ffb6`f26a0000 : 0xffffe68a`f27fb040
fffffd05`e9b85330 ac71908e`7dfeb93b     : fffffd05`e9b856d0 00000000`00007948 9bf2ffb6`f26a0000 00000000`00000000 : 0xd6
fffffd05`e9b85338 fffffd05`e9b856d0     : 00000000`00007948 9bf2ffb6`f26a0000 00000000`00000000 fffffd05`e9b856d0 : 0xac71908e`7dfeb93b
fffffd05`e9b85340 00000000`00007948     : 9bf2ffb6`f26a0000 00000000`00000000 fffffd05`e9b856d0 9bf2ffb6`f26a0000 : 0xfffffd05`e9b856d0
fffffd05`e9b85348 9bf2ffb6`f26a0000     : 00000000`00000000 fffffd05`e9b856d0 9bf2ffb6`f26a0000 00000000`00000001 : 0x7948
fffffd05`e9b85350 00000000`00000000     : fffffd05`e9b856d0 9bf2ffb6`f26a0000 00000000`00000001 00000000`ffffffff : 0x9bf2ffb6`f26a0000


SYMBOL_NAME:  nt!MiSystemFault+19248b

MODULE_NAME: nt

IMAGE_VERSION:  10.0.19041.5965

STACK_COMMAND: .process /r /p 0xffffe68adfade080; .thread 0xffffe68af27fb040 ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  19248b

FAILURE_BUCKET_ID:  AV_X_(null)_BAD_IP_nt!MiSystemFault

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {519102ae-339f-c953-2278-3f0bfcf5aa85}
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: fffff8031296ff14, memory referenced.
Arg2: 0000000000000010, 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: fffff8031296ff14, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

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


KEY_VALUES_STRING: 1

    Key  : AV.Type
    Value: Execute

    Key  : Analysis.CPU.mSec
    Value: 734

    Key  : Analysis.Elapsed.mSec
    Value: 1978

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 281

    Key  : Analysis.Init.Elapsed.mSec
    Value: 3976

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27829.1001

    Key  : Analysis.Version.Description
    Value: 10.2503.24.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2503.24.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x50

    Key  : Bugcheck.Code.TargetModel
    Value: 0x50

    Key  : Dump.Attributes.AsUlong
    Value: 0x8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: AV_X_(null)_BAD_IP_nt!MiSystemFault

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff8031296ff14

    Key  : Failure.Hash
    Value: {519102ae-339f-c953-2278-3f0bfcf5aa85}


BUGCHECK_CODE:  50

BUGCHECK_P1: fffff8031296ff14

BUGCHECK_P2: 10

BUGCHECK_P3: fffff8031296ff14

BUGCHECK_P4: 2

FILE_IN_CAB:  061925-14937-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffd50205633040

READ_ADDRESS: fffff8032a2fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 fffff8031296ff14

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  TslGame.exe

FAILED_INSTRUCTION_ADDRESS:
+0
fffff803`1296ff14 ??              ???

STACK_TEXT: 
ffff9089`da386ee8 fffff803`29a5118b     : 00000000`00000050 fffff803`1296ff14 00000000`00000010 ffff9089`da387190 : nt!KeBugCheckEx
ffff9089`da386ef0 fffff803`2980df40     : 00000000`00000861 00000000`00000010 ffff9089`da387210 00000000`00000000 : nt!MiSystemFault+0x19248b
ffff9089`da386ff0 fffff803`29a0e06d     : ffff9089`00000000 00000000`00000000 00000000`00000000 00000000`00000003 : nt!MmAccessFault+0x400
ffff9089`da387190 fffff803`1296ff14     : 000001c4`ff9f5180 0000008f`9769f598 00000000`00000000 00000000`00000101 : nt!KiPageFault+0x36d
ffff9089`da387320 000001c4`ff9f5180     : 0000008f`9769f598 00000000`00000000 00000000`00000101 00000001`4022b401 : 0xfffff803`1296ff14
ffff9089`da387328 0000008f`9769f598     : 00000000`00000000 00000000`00000101 00000001`4022b401 fffff802`36c50000 : 0x000001c4`ff9f5180
ffff9089`da387330 00000000`00000000     : 00000000`00000101 00000001`4022b401 fffff802`36c50000 0000008f`9769f598 : 0x0000008f`9769f598


SYMBOL_NAME:  nt!MiSystemFault+19248b

MODULE_NAME: nt

IMAGE_VERSION:  10.0.19041.5965

STACK_COMMAND: .process /r /p 0xffffd501efcdf080; .thread 0xffffd50205633040 ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  19248b

FAILURE_BUCKET_ID:  AV_X_(null)_BAD_IP_nt!MiSystemFault

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {519102ae-339f-c953-2278-3f0bfcf5aa85}

Followup:     MachineOwner
---------
 
Artı 0 Eksi

Hocam yardımcı olduğunuz için teşekkür ederim. Benden Memtest yapmamı istediniz fakat sistemi ilk topladığım aylarda performans konusunda yaşadığım tatminsizliklerden dolayı sizin videonuzdaki talimatları izleyerek 4 saat kadar süren bir test yapmıştım ve sonuç Pass olarak çıkmıştı. Şimdi tekrardan test yapmama gerek var mı?
 
Son düzenleyen: Moderatör:
Artı 0 Eksi
Mesaj yazmak için giriş yapmalı ya da kaydolmalısınız.

Benzer konular

N
  • Soru Soru
R7 9800X3D & RTX 5070 Ti sistemde PUBG oynarken mavi ekran hatası
Mesaj
4
Görüntüleme
75
n3t4
N
  • Soru Soru
GTA V oynarken mavi ekran hatası ve sistemin kapanması sorunu
Mesaj
1
Görüntüleme
57
nnomad
  • Soru Soru
GTA 5 indirken mavi ekran hatası
Mesaj
5
Görüntüleme
168
Astro.PR
E
  • Soru Soru
Monster Tulpar T7'de VIDEO_DXGKRNL_FATAL_ERROR 0x113 mavi ekran hatası
Mesaj
2
Görüntüleme
87
Emir Çip
E
Menü
Giriş yap
Kaydol
Bu siteyi kullanmak için çerezler gereklidir. Siteyi kullanmaya devam etmek için çerezleri kabul etmelisiniz. Daha Fazlasını Öğren.…