R5 3600 RX 6600 sistemde mavi ekran hatası

yay0661 · 8 Temmuz 2023

Minidump dosyama bakıp yardımcı olabilecek var mı?

070723-5718-01.dmp

drive.google.com

16 GB 3200 MHz CL 16
MLD 500 GB M.2 SSD
Gigabyte B450M K
RX 6600
Ryzen 5 3600

EgeN7 · 8 Temmuz 2023

* Kesin olarak neyden kaynaklandığı belli değil.

* Hata Discord'da alınmış gibi görünüyor.

Kod:

PROCESS_NAME:  Discord.exe

* Ayrıca sırıtan bazı detaylar var.

* Sistemde 2 farklı RAM görüyorum.

TEAMGROUP-UD4-3000 ve A-DATA Technology

* Bu bile tek başına soruna sebebiyet verebilecek durumlardan biri.

* Ne zamandır bu şekilde 2 farklı RAM ile kullanıyorsunuz sistemi?
* Daha önce bir sorun yaşadınız mı buna benzer?

* Bunun dışında, BIOS'unuz eski. Hem de beta bir sürüm kullanıyorsunuz.
* Mutlaka F2 sürümüne güncelleyin.

Rich (BB code):

BiosVersion = F2d
BiosReleaseDate = 06/01/2023
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = B450M K
BaseBoardProduct = B450M K-CF

B450M K (Rev. 1.0) - Destek | Anakart GIGABYTE

Lasting Quality from GIGABYTE GIGABYTE Ultra Durable™ motherboards bring together a unique blend of features and technologies that offer users the absolute ultimate platform for their next PC build.

www.gigabyte.com.tr

* Videolu Rehber: Gigabyte B450 BIOS Güncelleme

* BIOS güncelledikten sonra BIOS'a girip Load Optimized Defaults yapın. Kaydedin ve çıkın. Tekrar BIOS'a girin, yapılacak ayarlarınız varsa yapın.

* Chipset sürücülerini de güncelleyin.

Denetim masası > Program ekle / kaldırdan "AMD Chipset Software" silin.
Aşağıdan güncel olanı indirin ama kurmayın.
- https://www.amd.com/en/support/chipsets/amd-socket-am4/b450
İndirdikten sonra interneti kesin ve PC'yi yeniden başlatın.
PC açılınca yeni chipset sürücülerini kurun.
İnterneti bağlayabilirsiniz.

* Yeni güncellemeleriniz varsa Windows Update aracılığıyla yapın.

* Tüm bunların sonucunda hala mavi ekran alıyorsanız yeni dökümü paylaşın. Ona göre bir aksiyon listesi daha hazırlayalım. RAM ve depolama testi yapmak gerekebilir.

Döküm:

Kod:

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

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: ffff89845fd2a0c0, memory referenced.
Arg2: 0000000000000002, 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: fffff80339812e57, 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: Write

    Key  : Analysis.CPU.mSec
    Value: 1453

    Key  : Analysis.Elapsed.mSec
    Value: 1524

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x50

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: AV_W_(null)_nt!RtlpHpLfhSlotAllocate

    Key  : Failure.Hash
    Value: {6e341f15-43df-145e-afc9-8c72a4a25ef6}


BUGCHECK_CODE:  50

BUGCHECK_P1: ffff89845fd2a0c0

BUGCHECK_P2: 2

BUGCHECK_P3: fffff80339812e57

BUGCHECK_P4: 2

FILE_IN_CAB:  070723-5718-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

READ_ADDRESS: fffff8033a2fb390: 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
 ffff89845fd2a0c0

MM_INTERNAL_CODE:  2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Discord.exe

TRAP_FRAME:  ffff89845ed29ea0 -- (.trap 0xffff89845ed29ea0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=000000000000000c
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80339812e57 rsp=ffff89845ed2a030 rbp=ffff89845fd2a130
 r8=1555155555555115  r9=0000000000000000 r10=0000000000000036
r11=0000000000099b43 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!RtlpHpLfhSlotAllocate+0x1a7:
fffff803`39812e57 894590          mov     dword ptr [rbp-70h],eax ss:0018:ffff8984`5fd2a0c0=????????
Resetting default scope

STACK_TEXT:
ffff8984`5ed29bf8 fffff803`39a4af53     : 00000000`00000050 ffff8984`5fd2a0c0 00000000`00000002 ffff8984`5ed29ea0 : nt!KeBugCheckEx
ffff8984`5ed29c00 fffff803`3986e7b0     : ffff8984`5ed29d80 00000000`00000002 ffff8984`5ed29f20 00000000`00000000 : nt!MiSystemFault+0x1b2563
ffff8984`5ed29d00 fffff803`39a0bad8     : ffffc680`00e97180 fffff803`398dae80 55515555`00000000 00001f80`00e90280 : nt!MmAccessFault+0x400
ffff8984`5ed29ea0 fffff803`39812e57     : ffffffff`ffffffff ffff8984`00000038 ffff8984`5ed2a130 00000000`00000200 : nt!KiPageFault+0x358
ffff8984`5ed2a030 fffff803`39812331     : ffffb288`86010340 ffffb288`86014a00 ffffb288`86014c40 02000100`00000100 : nt!RtlpHpLfhSlotAllocate+0x1a7
ffff8984`5ed2a180 fffff803`39fb7074     : 00000000`00000000 00000000`1ec3fda0 ffff8984`6d57624f fffff803`39fb70b9 : nt!ExAllocateHeapPool+0x2b1
ffff8984`5ed2a2c0 fffff803`39c88ac9     : 00000000`000000f0 ffff8984`5ed2a350 00000000`00000000 ffff8984`00000000 : nt!ExAllocatePoolWithTag+0x64
ffff8984`5ed2a310 fffff803`39cbaa9b     : 00000000`00000005 fffff803`3981a106 00000000`00000005 fffffff6`0000000d : nt!ObWaitForMultipleObjects+0x399
ffff8984`5ed2a810 fffff803`39a0f7f5     : 00000000`00000000 ffffb288`91532080 00000000`1ec3f328 ffff8984`5ed2aaa8 : nt!NtWaitForMultipleObjects32+0x11b
ffff8984`5ed2aa90 00000000`77c51cfc     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000000`1ec3f308 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c51cfc


SYMBOL_NAME:  nt!RtlpHpLfhSlotAllocate+1a7

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.3086

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1a7

FAILURE_BUCKET_ID:  AV_W_(null)_nt!RtlpHpLfhSlotAllocate

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {6e341f15-43df-145e-afc9-8c72a4a25ef6}

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

yay0661 · 8 Temmuz 2023

EgeN7 dedi:

* Kesin olarak neyden kaynaklandığı belli değil.

* Hata Discord'da alınmış gibi görünüyor.

Kod:

PROCESS_NAME:  Discord.exe

* Ayrıca sırıtan bazı detaylar var.

* Sistemde 2 farklı RAM görüyorum.

TEAMGROUP-UD4-3000 ve A-DATA Technology

* Bu bile tek başına soruna sebebiyet verebilecek durumlardan biri.

* Ne zamandır bu şekilde 2 farklı RAM ile kullanıyorsunuz sistemi?
* Daha önce bir sorun yaşadınız mı buna benzer?

* Bunun dışında, BIOS'unuz eski. Hem de beta bir sürüm kullanıyorsunuz.
* Mutlaka F2 sürümüne güncelleyin.

Rich (BB code):

BiosVersion = F2d
BiosReleaseDate = 06/01/2023
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = B450M K
BaseBoardProduct = B450M K-CF

B450M K (Rev. 1.0) - Destek | Anakart GIGABYTE

Lasting Quality from GIGABYTE GIGABYTE Ultra Durable™ motherboards bring together a unique blend of features and technologies that offer users the absolute ultimate platform for their next PC build.

www.gigabyte.com.tr

* Videolu Rehber: Gigabyte B450 BIOS Güncelleme

* BIOS güncelledikten sonra BIOS'a girip Load Optimized Defaults yapın. Kaydedin ve çıkın. Tekrar BIOS'a girin, yapılacak ayarlarınız varsa yapın.

* Chipset sürücülerini de güncelleyin.

Denetim masası > Program ekle / kaldırdan "AMD Chipset Software" silin.
Aşağıdan güncel olanı indirin ama kurmayın.
- https://www.amd.com/en/support/chipsets/amd-socket-am4/b450
İndirdikten sonra interneti kesin ve PC'yi yeniden başlatın.
PC açılınca yeni chipset sürücülerini kurun.
İnterneti bağlayabilirsiniz.

* Yeni güncellemeleriniz varsa Windows Update aracılığıyla yapın.

* Tüm bunların sonucunda hala mavi ekran alıyorsanız yeni dökümü paylaşın. Ona göre bir aksiyon listesi daha hazırlayalım. RAM ve depolama testi yapmak gerekebilir.

Döküm:

Kod:

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

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: ffff89845fd2a0c0, memory referenced.
Arg2: 0000000000000002, 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: fffff80339812e57, 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: Write

    Key  : Analysis.CPU.mSec
    Value: 1453

    Key  : Analysis.Elapsed.mSec
    Value: 1524

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x50

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: AV_W_(null)_nt!RtlpHpLfhSlotAllocate

    Key  : Failure.Hash
    Value: {6e341f15-43df-145e-afc9-8c72a4a25ef6}


BUGCHECK_CODE:  50

BUGCHECK_P1: ffff89845fd2a0c0

BUGCHECK_P2: 2

BUGCHECK_P3: fffff80339812e57

BUGCHECK_P4: 2

FILE_IN_CAB:  070723-5718-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

READ_ADDRESS: fffff8033a2fb390: 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
 ffff89845fd2a0c0

MM_INTERNAL_CODE:  2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Discord.exe

TRAP_FRAME:  ffff89845ed29ea0 -- (.trap 0xffff89845ed29ea0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=000000000000000c
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80339812e57 rsp=ffff89845ed2a030 rbp=ffff89845fd2a130
 r8=1555155555555115  r9=0000000000000000 r10=0000000000000036
r11=0000000000099b43 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!RtlpHpLfhSlotAllocate+0x1a7:
fffff803`39812e57 894590          mov     dword ptr [rbp-70h],eax ss:0018:ffff8984`5fd2a0c0=????????
Resetting default scope

STACK_TEXT:
ffff8984`5ed29bf8 fffff803`39a4af53     : 00000000`00000050 ffff8984`5fd2a0c0 00000000`00000002 ffff8984`5ed29ea0 : nt!KeBugCheckEx
ffff8984`5ed29c00 fffff803`3986e7b0     : ffff8984`5ed29d80 00000000`00000002 ffff8984`5ed29f20 00000000`00000000 : nt!MiSystemFault+0x1b2563
ffff8984`5ed29d00 fffff803`39a0bad8     : ffffc680`00e97180 fffff803`398dae80 55515555`00000000 00001f80`00e90280 : nt!MmAccessFault+0x400
ffff8984`5ed29ea0 fffff803`39812e57     : ffffffff`ffffffff ffff8984`00000038 ffff8984`5ed2a130 00000000`00000200 : nt!KiPageFault+0x358
ffff8984`5ed2a030 fffff803`39812331     : ffffb288`86010340 ffffb288`86014a00 ffffb288`86014c40 02000100`00000100 : nt!RtlpHpLfhSlotAllocate+0x1a7
ffff8984`5ed2a180 fffff803`39fb7074     : 00000000`00000000 00000000`1ec3fda0 ffff8984`6d57624f fffff803`39fb70b9 : nt!ExAllocateHeapPool+0x2b1
ffff8984`5ed2a2c0 fffff803`39c88ac9     : 00000000`000000f0 ffff8984`5ed2a350 00000000`00000000 ffff8984`00000000 : nt!ExAllocatePoolWithTag+0x64
ffff8984`5ed2a310 fffff803`39cbaa9b     : 00000000`00000005 fffff803`3981a106 00000000`00000005 fffffff6`0000000d : nt!ObWaitForMultipleObjects+0x399
ffff8984`5ed2a810 fffff803`39a0f7f5     : 00000000`00000000 ffffb288`91532080 00000000`1ec3f328 ffff8984`5ed2aaa8 : nt!NtWaitForMultipleObjects32+0x11b
ffff8984`5ed2aa90 00000000`77c51cfc     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000000`1ec3f308 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c51cfc


SYMBOL_NAME:  nt!RtlpHpLfhSlotAllocate+1a7

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.3086

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1a7

FAILURE_BUCKET_ID:  AV_W_(null)_nt!RtlpHpLfhSlotAllocate

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {6e341f15-43df-145e-afc9-8c72a4a25ef6}

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

Bu RAM'leri uzun zamandır kullanıyorum hata almadım. Dediğiniz şeyleri uyguladım bir daha herhangi bir hata alırsam minidump dosyamı buradan paylaşırım.

EgeN7 dedi:

* Kesin olarak neyden kaynaklandığı belli değil.

* Hata Discord'da alınmış gibi görünüyor.

Kod:

PROCESS_NAME:  Discord.exe

* Ayrıca sırıtan bazı detaylar var.

* Sistemde 2 farklı RAM görüyorum.

TEAMGROUP-UD4-3000 ve A-DATA Technology

* Bu bile tek başına soruna sebebiyet verebilecek durumlardan biri.

* Ne zamandır bu şekilde 2 farklı RAM ile kullanıyorsunuz sistemi?
* Daha önce bir sorun yaşadınız mı buna benzer?

* Bunun dışında, BIOS'unuz eski. Hem de beta bir sürüm kullanıyorsunuz.
* Mutlaka F2 sürümüne güncelleyin.

Rich (BB code):

BiosVersion = F2d
BiosReleaseDate = 06/01/2023
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = B450M K
BaseBoardProduct = B450M K-CF

B450M K (Rev. 1.0) - Destek | Anakart GIGABYTE

Lasting Quality from GIGABYTE GIGABYTE Ultra Durable™ motherboards bring together a unique blend of features and technologies that offer users the absolute ultimate platform for their next PC build.

www.gigabyte.com.tr

* Videolu Rehber: Gigabyte B450 BIOS Güncelleme

* BIOS güncelledikten sonra BIOS'a girip Load Optimized Defaults yapın. Kaydedin ve çıkın. Tekrar BIOS'a girin, yapılacak ayarlarınız varsa yapın.

* Chipset sürücülerini de güncelleyin.

Denetim masası > Program ekle / kaldırdan "AMD Chipset Software" silin.
Aşağıdan güncel olanı indirin ama kurmayın.
- https://www.amd.com/en/support/chipsets/amd-socket-am4/b450
İndirdikten sonra interneti kesin ve PC'yi yeniden başlatın.
PC açılınca yeni chipset sürücülerini kurun.
İnterneti bağlayabilirsiniz.

* Yeni güncellemeleriniz varsa Windows Update aracılığıyla yapın.

* Tüm bunların sonucunda hala mavi ekran alıyorsanız yeni dökümü paylaşın. Ona göre bir aksiyon listesi daha hazırlayalım. RAM ve depolama testi yapmak gerekebilir.

Döküm:

Kod:

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

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: ffff89845fd2a0c0, memory referenced.
Arg2: 0000000000000002, 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: fffff80339812e57, 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: Write

    Key  : Analysis.CPU.mSec
    Value: 1453

    Key  : Analysis.Elapsed.mSec
    Value: 1524

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x50

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: AV_W_(null)_nt!RtlpHpLfhSlotAllocate

    Key  : Failure.Hash
    Value: {6e341f15-43df-145e-afc9-8c72a4a25ef6}


BUGCHECK_CODE:  50

BUGCHECK_P1: ffff89845fd2a0c0

BUGCHECK_P2: 2

BUGCHECK_P3: fffff80339812e57

BUGCHECK_P4: 2

FILE_IN_CAB:  070723-5718-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

READ_ADDRESS: fffff8033a2fb390: 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
 ffff89845fd2a0c0

MM_INTERNAL_CODE:  2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Discord.exe

TRAP_FRAME:  ffff89845ed29ea0 -- (.trap 0xffff89845ed29ea0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=000000000000000c
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80339812e57 rsp=ffff89845ed2a030 rbp=ffff89845fd2a130
 r8=1555155555555115  r9=0000000000000000 r10=0000000000000036
r11=0000000000099b43 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!RtlpHpLfhSlotAllocate+0x1a7:
fffff803`39812e57 894590          mov     dword ptr [rbp-70h],eax ss:0018:ffff8984`5fd2a0c0=????????
Resetting default scope

STACK_TEXT:
ffff8984`5ed29bf8 fffff803`39a4af53     : 00000000`00000050 ffff8984`5fd2a0c0 00000000`00000002 ffff8984`5ed29ea0 : nt!KeBugCheckEx
ffff8984`5ed29c00 fffff803`3986e7b0     : ffff8984`5ed29d80 00000000`00000002 ffff8984`5ed29f20 00000000`00000000 : nt!MiSystemFault+0x1b2563
ffff8984`5ed29d00 fffff803`39a0bad8     : ffffc680`00e97180 fffff803`398dae80 55515555`00000000 00001f80`00e90280 : nt!MmAccessFault+0x400
ffff8984`5ed29ea0 fffff803`39812e57     : ffffffff`ffffffff ffff8984`00000038 ffff8984`5ed2a130 00000000`00000200 : nt!KiPageFault+0x358
ffff8984`5ed2a030 fffff803`39812331     : ffffb288`86010340 ffffb288`86014a00 ffffb288`86014c40 02000100`00000100 : nt!RtlpHpLfhSlotAllocate+0x1a7
ffff8984`5ed2a180 fffff803`39fb7074     : 00000000`00000000 00000000`1ec3fda0 ffff8984`6d57624f fffff803`39fb70b9 : nt!ExAllocateHeapPool+0x2b1
ffff8984`5ed2a2c0 fffff803`39c88ac9     : 00000000`000000f0 ffff8984`5ed2a350 00000000`00000000 ffff8984`00000000 : nt!ExAllocatePoolWithTag+0x64
ffff8984`5ed2a310 fffff803`39cbaa9b     : 00000000`00000005 fffff803`3981a106 00000000`00000005 fffffff6`0000000d : nt!ObWaitForMultipleObjects+0x399
ffff8984`5ed2a810 fffff803`39a0f7f5     : 00000000`00000000 ffffb288`91532080 00000000`1ec3f328 ffff8984`5ed2aaa8 : nt!NtWaitForMultipleObjects32+0x11b
ffff8984`5ed2aa90 00000000`77c51cfc     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000000`1ec3f308 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c51cfc


SYMBOL_NAME:  nt!RtlpHpLfhSlotAllocate+1a7

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.3086

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1a7

FAILURE_BUCKET_ID:  AV_W_(null)_nt!RtlpHpLfhSlotAllocate

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {6e341f15-43df-145e-afc9-8c72a4a25ef6}

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

Önceden de mavi ekran hatası yemiştim ama bir arkadaş işlemci undervolt yapmışsınız vesaire demişti. Bu minidump da öyle bir şey var mı? İşlemciye hiçbir işlem yapmamıştım.

EgeN7 · 8 Temmuz 2023

yay0661 dedi:
İşlemci undervolt yapmışsınız vs. demişti.

Undervolt "yapmışsan" demiş.

lazye dedi:
İşlemciye undervolt yapmışsan, geri al.

Yani herhangi bir undervolt yaptıysanız bu işlemi geri alın demek istemiş.
Kesinlik yok.

lazye · 8 Temmuz 2023

Evet yapmışsan al dedim. Çünkü; yanlış hatırlamıyorsam voltaj değerleri 1.1V gibi görünüyordu. AMD Ryzen Master'a sistemde yüklüydü diye yapmışsan geri al dedim herhangi bir işlem yapmadıysan bir şey yapmana gerek yok.

yay0661 · 8 Temmuz 2023

lazye dedi:
Evet yapmışsan al dedim. Çünkü; yanlış hatırlamıyorsam voltaj değerleri 1.1V gibi görünüyordu. AMD Ryzen Master'a sistemde yüklüydü diye yapmışsan geri al dedim herhangi bir işlem yapmadıysan bir şey yapmana gerek yok.

Kusura bakma yanlış hatırlamışım.

R5 3600 RX 6600 sistemde mavi ekran hatası

Ayrıntılı düzenleme

yay0661

Hectopat

070723-5718-01.dmp

EgeN7

Gigapat

B450M K (Rev. 1.0) - Destek | Anakart GIGABYTE

yay0661

Hectopat

B450M K (Rev. 1.0) - Destek | Anakart GIGABYTE

B450M K (Rev. 1.0) - Destek | Anakart GIGABYTE

EgeN7

Gigapat

lazye

Megapat

yay0661

Hectopat

Benzer konular

Technopat Haberler

Yeni konular

Yeni mesajlar

Gizliliğinize önem veriyoruz