R5 1600 AF RX 580 IRQL_NOT_LESS_OR_EQUAL mavi ekran hatası

Takumi_Dk · 21 Haziran 2023

WhatsApp Image 2023-06-21 at 18.33.34.jpeg

Minidump.rar

Sürekli bu hatayı alıyorum. İnternette biraz baktım ama hiçbir şey anlamadım. Anakartla alakalı diyor bazıları, bazıları RAM vs. kafam çok bulandı. Yeni format attım. Bundan önce de mavi ekran veriyordu ama hata koduna bakmamıştım, sanırım gene buydu. Genelde Valorant oynarken yiyorum bu hatayı.

Sistem özelliklerim;

Ryzen 5 1600 AF.
ASUS Prime A320M-F
2x8 G.Skill Ripjaws 3000 MHz
Gigabyte Aorus RX 580 4G.
500W Cooler Master (eski model)
120 GB Kingston SSD.
500GB WD Blue HDD.
Windows 10 64X

Format atmadan önceki ekran kartım GTX 1050 onda da mavi ekran veriyordu ama hataya dediğim gibi bakmamıştım, sonra hem format attım hem ekran kartını değiştirdim. 2. el RX 580 aldım. 30 dk FurMark testi yaptım herhangi bir sorun çıkmadı. 75 dereceye çıktı. Satan adam mining yapılmadı dedi ama yüksek ihtimal yapılmıştır. Ekran kartından dolayı olabilir mi veya işlemci?

Remzi53 · 21 Haziran 2023

Hocam, Defender harici virüs programiniz var ise, Revo ile temiz bir sekilde silin, bu hata başka secenekler de dahil bu yuzdende oluyor, Ayrica CMD yonetici olarak calistirin winget upgrade --all komutu uygulayin Sonra Y yes için, güncel olmayan Driverleri gunceller, bu hata Driver sorunu olarak da geciyor

Takumi_Dk · 21 Haziran 2023

Tamamdır çok teşekkür ederim sonuç için tekrar yazacağım.

EgeN7 · 21 Haziran 2023

Evet sürücü hatası, ancak tam olarak neyden kaynaklandığı belli değil.

Genelde bozuk/güncel olmayan sürücüler, RAM veya depolama biriminden kaynaklanıyor.

* Öncelikle Windows sürümü eski görünüyor ancak minidump dosyaları yanıltıcı olabiliyor. Windows Update aracılığıyla güncellemeleriniz varsa hepsini yapın.

* BIOS sürümünüz çok eski kalmış. 2201 kullanıyorsunuz.

Rich (BB code):

BiosVersion = 2201
BiosReleaseDate = 07/10/2020
SystemProductName = PC-HOCASI-GG1-V2
SystemVersion = System Version
SystemSKU = SKU
BaseBoardManufacturer = ASUSTeK COMPUTER INC.
BaseBoardProduct = PRIME A320M-F
BaseBoardVersion = Rev X.0x

6062 sürümüne güncelleyin.

PRIME A320M-F｜Anakart｜ASUS Türkiye

ASUS Prime serisi, AMD ve Intel iÅlemcilerin tÃ¼m potansiyelini ortaya Ã§Ä±karmak iÃ§in Ã¶zenle geliÅtirildi. SaÄlam gÃ¼Ã§ tasarÄ±mÄ±na, kapsamlÄ± soÄutma Ã§Ã¶zÃ¼mlerine ve akÄ±llÄ± ayar seÃ§eneklerine sahip olan Prime serisi anakartlar, kendi PCâlerini toplayan kiÅilere kullanÄ±ÅlÄ±...

www.asus.com

* BIOS güncelleme rehber videosu: Asus Anakartlarda BIOS Güncelleme | 2023

* BIOS'u güncelledikten sonra BIOS'a girin, F5 tuşuna basın ve gelen "Load optimized defaults?" sorusuna "Yes" deyip BIOS'tan çıkın. BIOS'a tekrar girin ve ayarlarınızı yapın (RAM XMP profili, fan ayarları vs.).

* 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/a320
İ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.

* Realtek ethernet sürücünüz de 24 Mayıs 2019'dan kalma.

Rich (BB code):

    Image path: \SystemRoot\System32\drivers\rt640x64.sys
    Image name: rt640x64.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri May 24 11:47:02 2019 (5CE7AF86)

* Anakartınızda Realtek® 8111H ethernet kontrolcü var.

* Aşağıda paylaştığım Realtek linkinden "Win10 Auto Installation Program (NDIS)" olanı indirin, tarihi 23/05/2023. Ama kurmayın.

* Daha sonra denetim masası > program ekle/kaldırdan eski sürücüleri silin.
* PC'yi yeniden başlatın.
* İndirdiğiniz güncel sürücüyü kurun.

Realtek PCIe FE / GBE / 2.5G / 5G Ethernet Family Controller Software - REALTEK

www.realtek.com

* Tüm bu işlemlerden sonra mavi ekranlar devam ederse yeni dökümleri paylaşın.

* Duruma göre Memtest86 ile RAM testi gerekecek.

Dökümler:

Kod:

*******************************************************************************
*                                                                             *
*                        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: ffffffff870f06f8, memory referenced
Arg2: 000000000000000e, IRQL
Arg3: 0000000000000001, 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: fffff806108f64c1, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1390

    Key  : Analysis.Elapsed.mSec
    Value: 6713

    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: 187

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xa

    Key  : Failure.Bucket
    Value: AV_nt!KiIpiProcessRequests

    Key  : Failure.Hash
    Value: {76557470-7e84-49e6-bd40-325d9290f3d0}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  a

BUGCHECK_P1: ffffffff870f06f8

BUGCHECK_P2: e

BUGCHECK_P3: 1

BUGCHECK_P4: fffff806108f64c1

FILE_IN_CAB:  062123-27890-01.dmp

WRITE_ADDRESS: fffff806112fb390: 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
 ffffffff870f06f8

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  ffff9e011d9f1d40 -- (.trap 0xffff9e011d9f1d40)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000005 rbx=0000000000000000 rcx=0000000000000000
rdx=ffcc0257a3b05805 rsi=0000000000000000 rdi=0000000000000000
rip=fffff806108f64c1 rsp=ffff9e011d9f1ed0 rbp=ffff9e011d9e30c0
 r8=0000000000000000  r9=0000000000000000 r10=ffff9e011d740180
r11=fffff80610600000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!KiIpiProcessRequests+0xd1:
fffff806`108f64c1 ff83f8060f87    inc     dword ptr [rbx-78F0F908h] ds:ffffffff`870f06f8=????????
Resetting default scope

STACK_TEXT:
ffff9e01`1d9f1bf8 fffff806`10a10029     : 00000000`0000000a ffffffff`870f06f8 00000000`0000000e 00000000`00000001 : nt!KeBugCheckEx
ffff9e01`1d9f1c00 fffff806`10a0bbe3     : 00000000`00000000 0000ffff`f8061088 ffff8dfb`8fe00000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffff9e01`1d9f1d40 fffff806`108f64c1     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x463
ffff9e01`1d9f1ed0 fffff806`10a041d0     : 00000000`00000000 ffff9804`aac6f570 00000000`00000000 00000000`00000000 : nt!KiIpiProcessRequests+0xd1
ffff9e01`1d9f1fb0 fffff806`10a03db1     : 00000000`00000000 fffff806`10a03dff 00000000`00000000 00000000`00000001 : nt!KiIpiInterruptSubDispatch+0x90
ffff9804`aac6f4f0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIpiInterrupt+0x301


SYMBOL_NAME:  nt!KiIpiProcessRequests+d1

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.3086

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  d1

FAILURE_BUCKET_ID:  AV_nt!KiIpiProcessRequests

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {76557470-7e84-49e6-bd40-325d9290f3d0}

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


*******************************************************************************
*                                                                             *
*                        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: 00000000cd9db260, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff8004a116233, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1859

    Key  : Analysis.Elapsed.mSec
    Value: 3484

    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: 202

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xa

    Key  : Failure.Bucket
    Value: AV_nt!KeInitializeQueue

    Key  : Failure.Hash
    Value: {4c4e0875-b45d-3201-3572-551e16abf47c}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  a

BUGCHECK_P1: cd9db260

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff8004a116233

FILE_IN_CAB:  062123-27921-01.dmp

WRITE_ADDRESS: fffff8004aafb390: 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
 00000000cd9db260

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  VALORANT-Win64-Shipping.exe

DPC_STACK_BASE:  FFFFDE8F84276FB0

TRAP_FRAME:  ffffde8f842769a0 -- (.trap 0xffffde8f842769a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000cd9db258 rbx=0000000000000000 rcx=0000000000000017
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8004a116233 rsp=ffffde8f84276b38 rbp=ffffde8f84276cb0
 r8=fffff8004a116230  r9=ffffdf8942cffc10 r10=0000fffff8004a11
r11=ffff85fda7400000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac po cy
nt!KeInitializeQueue+0x23:
fffff800`4a116233 48894008        mov     qword ptr [rax+8],rax ds:00000000`cd9db260=????????????????
Resetting default scope

STACK_TEXT:
ffffde8f`84276858 fffff800`4a210029     : 00000000`0000000a 00000000`cd9db260 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffffde8f`84276860 fffff800`4a20bbe3     : 00000000`00140001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffde8f`842769a0 fffff800`4a116233     : fffff800`4a088810 ffffde8f`84276e80 ffff9600`cd9d8180 00000748`e4bf7a7f : nt!KiPageFault+0x463
ffffde8f`84276b38 ffffdf89`422ea710     : 00000000`000008c8 00000000`00000f44 00000000`00400a02 00000000`00000000 : nt!KeInitializeQueue+0x23
ffffde8f`84276b68 00000000`000008c8     : 00000000`00000f44 00000000`00400a02 00000000`00000000 00000748`e4bf5e1f : 0xffffdf89`422ea710
ffffde8f`84276b70 00000000`00000f44     : 00000000`00400a02 00000000`00000000 00000748`e4bf5e1f ffff7705`657af533 : 0x8c8
ffffde8f`84276b78 00000000`00400a02     : 00000000`00000000 00000748`e4bf5e1f ffff7705`657af533 00000000`00000000 : 0xf44
ffffde8f`84276b80 00000000`00000000     : 00000748`e4bf5e1f ffff7705`657af533 00000000`00000000 fffff800`4a0887d0 : 0x400a02


SYMBOL_NAME:  nt!KeInitializeQueue+23

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.3086

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  23

FAILURE_BUCKET_ID:  AV_nt!KeInitializeQueue

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {4c4e0875-b45d-3201-3572-551e16abf47c}

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

Takumi_Dk · 21 Haziran 2023

EgeN7 dedi:

Evet sürücü hatası, ancak tam olarak neden kaynaklandığı belli değil.

Genelde bozuk/güncel olmayan sürücüler, RAM veya depolama biriminden kaynaklanıyor.

* Öncelikle Windows sürümü eski görünüyor ancak minidump dosyaları yanıltıcı olabiliyor. Windows Update aracılığıyla güncellemeleriniz varsa hepsini yapın.

* BIOS sürümünüz çok eski kalmış. 2201 kullanıyorsunuz.

Rich (BB code):

BiosVersion = 2201
BiosReleaseDate = 07/10/2020
SystemProductName = PC-HOCASI-GG1-V2
SystemVersion = System Version.
SystemSKU = SKU.
BaseBoardManufacturer = ASUSTeK COMPUTER INC.
BaseBoardProduct = PRIME A320M-F
BaseBoardVersion = Rev X.0x

6062 sürümüne güncelleyin.

PRIME A320M-F｜Anakart｜ASUS Türkiye

ASUS Prime serisi, AMD ve Intel iÅlemcilerin tÃ¼m potansiyelini ortaya Ã§Ä±karmak iÃ§in Ã¶zenle geliÅtirildi. SaÄlam gÃ¼Ã§ tasarÄ±mÄ±na, kapsamlÄ± soÄutma Ã§Ã¶zÃ¼mlerine ve akÄ±llÄ± ayar seÃ§eneklerine sahip olan Prime serisi anakartlar, kendi PCâlerini toplayan kiÅilere kullanÄ±ÅlÄ±...

www.asus.com

* BIOS güncelleme rehber videosu: Asus Anakartlarda BIOS Güncelleme | 2023

* BIOS'u güncelledikten sonra BIOS'a girin, F5 tuşuna basın ve gelen "load optimized defaults?" sorusuna "yes" deyip BIOS'tan çıkın. BIOS'a tekrar girin ve ayarlarınızı yapın (RAM XMP profili, fan ayarları vs.).

* 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/a320
İ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.

* Realtek Ethernet sürücünüz de 24 Mayıs 2019'dan kalma.

Rich (BB code):

 Image path: \SystemRoot\System32\drivers\rt640x64.sys
 Image name: rt640x64.sys
 Browse all global symbols functions data.
 Timestamp: Fri May 24 11:47:02 2019 (5CE7AF86)

* Anakartınızda realtek® 8111h Ethernet kontrolcü var.

* Aşağıda paylaştığım Realtek linkinden "Windows 10 Auto ınstallation program (NDIS)" olanı indirin, tarihi 23/05/2023. ama kurmayın.

* Daha sonra Denetim Masası > program ekle/kaldırdan eski sürücüleri silin.
* PC'yi yeniden başlatın.
* İndirdiğiniz güncel sürücüyü kurun.

Realtek PCIe FE / GBE / 2.5G / 5G Ethernet Family Controller Software - REALTEK

www.realtek.com

* Tüm bu işlemlerden sonra mavi ekranlar devam ederse yeni dökümleri paylaşın.

* Duruma göre Memtest86 ile RAM testi gerekecek.

Dökümler:

Kod:

*******************************************************************************
* *
* 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: ffffffff870f06f8, memory referenced.
Arg2: 000000000000000e, IRQL.
Arg3: 0000000000000001, 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: fffff806108f64c1, address which referenced memory.

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

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 1390.

 Key : Analysis.Elapsed.mSec
 Value: 6713.

 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: 187.

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

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

 Key : Bugcheck.Code.LegacyAPI
 Value: 0xa.

 Key : Failure.Bucket
 Value: AV_nt!KiIpiProcessRequests

 Key : Failure.Hash
 Value: {76557470-7e84-49e6-bd40-325d9290f3d0}

 Key : WER.OS.Branch
 Value: vb_release.

 Key : WER.OS.Version
 Value: 10.0.19041.1

BUGCHECK_CODE: a

BUGCHECK_P1: ffffffff870f06f8.

BUGCHECK_P2: e

BUGCHECK_P3: 1

BUGCHECK_P4: fffff806108f64c1.

FILE_IN_CAB: 062123-27890-01.dmp

WRITE_ADDRESS: fffff806112fb390: 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
 ffffffff870f06f8.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System.

TRAP_FRAME: ffff9e011d9f1d40 -- (.trap 0xffff9e011d9f1d40)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000005 rbx=0000000000000000 rcx=0000000000000000
rdx=ffcc0257a3b05805 rsi=0000000000000000 rdi=0000000000000000
rip=fffff806108f64c1 rsp=ffff9e011d9f1ed0 rbp=ffff9e011d9e30c0
 r8=0000000000000000 r9=0000000000000000 r10=ffff9e011d740180
r11=fffff80610600000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc.
nt!KiIpiProcessRequests+0xd1:
fffff806`108f64c1 ff83f8060f87 inc dword ptr [rbx-78F0F908h] ds:ffffffff`870f06f8=????????
Resetting default scope.

STACK_TEXT:
ffff9e01`1d9f1bf8 fffff806`10a10029 : 00000000`0000000a ffffffff`870f06f8 00000000`0000000e 00000000`00000001 : nt!KeBugCheckEx
ffff9e01`1d9f1c00 fffff806`10a0bbe3 : 00000000`00000000 0000ffff`f8061088 ffff8dfb`8fe00000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffff9e01`1d9f1d40 fffff806`108f64c1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x463
ffff9e01`1d9f1ed0 fffff806`10a041d0 : 00000000`00000000 ffff9804`aac6f570 00000000`00000000 00000000`00000000 : nt!KiIpiProcessRequests+0xd1
ffff9e01`1d9f1fb0 fffff806`10a03db1 : 00000000`00000000 fffff806`10a03dff 00000000`00000000 00000000`00000001 : nt!KiIpiInterruptSubDispatch+0x90
ffff9804`aac6f4f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIpiInterrupt+0x301

SYMBOL_NAME: nt!KiIpiProcessRequests+d1

MODULE_NAME: nt.

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.3086

STACK_COMMAND: .cxr; .ecxr ; kb.

BUCKET_ID_FUNC_OFFSET: d1.

FAILURE_BUCKET_ID: AV_nt!KiIpiProcessRequests

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release.

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {76557470-7e84-49e6-bd40-325d9290f3d0}

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

*******************************************************************************
* *
* 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: 00000000cd9db260, memory referenced.
Arg2: 0000000000000002, IRQL.
Arg3: 0000000000000001, 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: fffff8004a116233, address which referenced memory.

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

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 1859.

 Key : Analysis.Elapsed.mSec
 Value: 3484.

 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: 202.

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

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

 Key : Bugcheck.Code.LegacyAPI
 Value: 0xa.

 Key : Failure.Bucket
 Value: AV_nt!KeInitializeQueue

 Key : Failure.Hash
 Value: {4c4e0875-b45d-3201-3572-551e16abf47c}

 Key : WER.OS.Branch
 Value: vb_release.

 Key : WER.OS.Version
 Value: 10.0.19041.1

BUGCHECK_CODE: a

BUGCHECK_P1: cd9db260.

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff8004a116233.

FILE_IN_CAB: 062123-27921-01.dmp

WRITE_ADDRESS: fffff8004aafb390: 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
 00000000cd9db260.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: VALORANT-Win64-Shipping.exe

DPC_STACK_BASE: FFFFDE8F84276FB0.

TRAP_FRAME: ffffde8f842769a0 -- (.trap 0xffffde8f842769a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000cd9db258 rbx=0000000000000000 rcx=0000000000000017
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8004a116233 rsp=ffffde8f84276b38 rbp=ffffde8f84276cb0
 r8=fffff8004a116230 r9=ffffdf8942cffc10 r10=0000fffff8004a11
r11=ffff85fda7400000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac po cy.
nt!KeInitializeQueue+0x23:
fffff800`4a116233 48894008 mov qword ptr [rax+8],rax ds:00000000`cd9db260=????????????????
Resetting default scope.

STACK_TEXT:
ffffde8f`84276858 fffff800`4a210029 : 00000000`0000000a 00000000`cd9db260 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffffde8f`84276860 fffff800`4a20bbe3 : 00000000`00140001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffde8f`842769a0 fffff800`4a116233 : fffff800`4a088810 ffffde8f`84276e80 ffff9600`cd9d8180 00000748`e4bf7a7f : nt!KiPageFault+0x463
ffffde8f`84276b38 ffffdf89`422ea710 : 00000000`000008c8 00000000`00000f44 00000000`00400a02 00000000`00000000 : nt!KeInitializeQueue+0x23
ffffde8f`84276b68 00000000`000008c8 : 00000000`00000f44 00000000`00400a02 00000000`00000000 00000748`e4bf5e1f : 0xffffdf89`422ea710
ffffde8f`84276b70 00000000`00000f44 : 00000000`00400a02 00000000`00000000 00000748`e4bf5e1f ffff7705`657af533 : 0x8c8.
ffffde8f`84276b78 00000000`00400a02 : 00000000`00000000 00000748`e4bf5e1f ffff7705`657af533 00000000`00000000 : 0xf44.
ffffde8f`84276b80 00000000`00000000 : 00000748`e4bf5e1f ffff7705`657af533 00000000`00000000 fffff800`4a0887d0 : 0x400a02.

SYMBOL_NAME: nt!KeInitializeQueue+23

MODULE_NAME: nt.

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.3086

STACK_COMMAND: .cxr; .ecxr ; kb.

BUCKET_ID_FUNC_OFFSET: 23.

FAILURE_BUCKET_ID: AV_nt!KeInitializeQueue

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release.

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {4c4e0875-b45d-3201-3572-551e16abf47c}

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

Çok teşekkür ederim, hepsini denedikten sonra tekrar sonuç için yazacağım.

biosu güncelledim,chipseti güncelledim ama realthek in eski driverları hangisi onları bulamadım bunlardan hangisi acaba ?

EgeN7 · 22 Haziran 2023

Installer ile kurulmamış belli ki. O yüzden de denetim masasında görünmüyor olabilir.

Üstüne kurmayı deneyebilirsiniz.

Takumi_Dk · 22 Haziran 2023

Realtek driverı kurdum, birazdan Memtest86'yı başlatacağım, denedikten sonra tekrar sonuç için yazacağım. Tekrardan çok teşekkür ederim.

WhatsApp Image 2023-06-23 at 09.04.03.jpeg

WhatsApp Image 2023-06-23 at 09.04.01.jpeg

WhatsApp Image 2023-06-23 at 09.03.58 (1).jpeg

WhatsApp Image 2023-06-23 at 09.03.58.jpeg

Memtest86 da hata verdi 1 tane

sistemimdeki tek sıfır şeylerin RAM olması dışında bir sorun yok

, acaba hangi RAM sıkıntılı?

Takumi_Dk dedi:
Realtek driverı kurdum, birazdan Memtest86'yı başlatacağım, denedikten sonra tekrar sonuç için yazacağım. Tekrardan çok teşekkür ederim.

Memtest86 da hata verdi 1 tane sistemimdeki tek sıfır şeylerin RAM olması dışında bir sorun yok , acaba hangi RAM sıkıntılı?

Ve XMP profili nedir acaba? Önemli bir şey ise nasıl yapılıyor?

WhatsApp Image 2023-06-23 at 09.35.16.jpeg

İkisinde de maximum bandwidth 2133 MHz olarak görünüyor ama RAM'ler 3000 MHz bende 3000 MHz de kullanıyorum sorun bu olabilir mi?

MiniDump 2.rar = minidump 2
Sanırım "IRQL not less or equeal" hatası bitti ve bu sefer de kernel Security chechk failure
Şeklinde mavi ekran verdi.

R5 1600 AF RX 580 IRQL_NOT_LESS_OR_EQUAL mavi ekran hatası

Ayrıntılı düzenleme

Takumi_Dk

Decapat

Remzi53

Hectopat

Takumi_Dk

Decapat

EgeN7

Megapat

PRIME A320M-F｜Anakart｜ASUS Türkiye

Realtek PCIe FE / GBE / 2.5G / 5G Ethernet Family Controller Software - REALTEK

Takumi_Dk

Decapat

PRIME A320M-F｜Anakart｜ASUS Türkiye

Realtek PCIe FE / GBE / 2.5G / 5G Ethernet Family Controller Software - REALTEK

EgeN7

Megapat

Takumi_Dk

Decapat

Benzer konular

Yeni konular

Yeni mesajlar

Gizliliğinize önem veriyoruz