Valorant IRQL_NOT_LESS_OR_EQUAL mavi ekran

D

DarkstarDF

Kilopat
Katılım
14 Ocak 2017
Mesajlar
72
Çözümler
1
Daha fazla  
Cinsiyet
Erkek
Merhabalar, günlerdir Valorant mavi ekran hatasına çözüm bulmaya çalışıyorum fakat hiçbir gelişme kaydedemedim.
Sorun tam olarak şöyle;
Valorant'ı indirdikten sonra girmeye çalışınca ilk 5-10 saniye siyah ekranda kalıyor ondan sonra mavi ekran hatası veriyor. DDU ile ekran kartımı silip tekrar en güncelini yükledim ve farklı platformlardan izlediğim videolardan yola çıkarak bazı çözümler(uyumluluk modu değiştirme) denedim ve yine sonuç elde edemedim.

Daha fazla yazmadan, size minidump dosyamı paylaşmak istiyorum, mavi ekran hatası konularına hakim olan kişiler konuya el atarsa çok sevinirim.

tttt - Google Drive
 
Son düzenleme:
Tarihe göre sırala Puana göre sırala
Vanguard'ı kaldırıp tekrar deneyin sorunun devam etmesi üzerine Windows 7 SP3 ya da Windows 10'a geçin. Tavsiyem Windows 10 üzerinedir.

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: ffffd80003a19818, memory referenced
Arg2: 000000000000000d, 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: fffff80002a96f40, address which referenced memory

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 968

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

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 962

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

Key : Analysis.System
Value: CreateObject

Key : WER.OS.Branch
Value: win7sp1_ldr_escrow

Key : WER.OS.Timestamp
Value: 2020-01-02T17:07:00Z

Key : WER.OS.Version
Value: 7.1.7601.24545


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: a

BUGCHECK_P1: ffffd80003a19818

BUGCHECK_P2: d

BUGCHECK_P3: 1

BUGCHECK_P4: fffff80002a96f40

WRITE_ADDRESS: Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff80002cb82f0
GetUlongPtrFromAddress: unable to read from fffff80002cb84a8
ffffd80003a19818

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: fffff80000b9e900 -- (.trap 0xfffff80000b9e900)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000001273936c rbx=0000000000000000 rcx=fffff80000b9ead0
rdx=0000000000002711 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a96f40 rsp=fffff80000b9ea98 rbp=fffff80000b9eb50
r8=fffff80002c0f100 r9=00000001acf1ac2f r10=000000000005115a
r11=fffff80002bff180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KeUpdateSystemTime:
fffff800`02a96f40 48895c2408 mov qword ptr [rsp+8],rbx ss:0018:fffff800`00b9eaa0=fffff80003027360
Resetting default scope

DPC_STACK_BASE: FFFFF80000BA4FB0

STACK_OVERFLOW: Stack Limit: fffff80000b9efb0. Use (kF) and (!stackusage) to investigate stack usage.

STACK_TEXT:
fffff800`00b9e7b8 fffff800`02abd2e9 : 00000000`0000000a ffffd800`03a19818 00000000`0000000d 00000000`00000001 : nt!KeBugCheckEx
fffff800`00b9e7c0 fffff800`02abb0ce : 00000000`00000001 ffffd800`03a19818 00000000`00000000 fffff800`03027360 : nt!KiBugCheckDispatch+0x69
fffff800`00b9e900 fffff800`02a96f40 : fffff800`030028e9 fffff800`03027360 fffff800`00b9eb50 fffff800`03027360 : nt!KiPageFault+0x44e
fffff800`00b9ea98 fffff800`030028e9 : fffff800`03027360 fffff800`00b9eb50 fffff800`03027360 fffffa80`00000000 : nt!KeUpdateSystemTime
fffff800`00b9eaa0 fffff800`02aafdef : fffff800`02bff180 fffff800`00b9eb50 00000000`00000000 fffff800`02bff180 : hal!HalReturnToFirmware+0xb25
fffff800`00b9ead0 fffff880`04399912 : fffff880`04398874 00000002`1ac191b5 00000282`00000282 00000771`00000784 : nt!KiInterruptDispatchNoLock+0xaf
fffff800`00b9ec68 fffff880`04398874 : 00000002`1ac191b5 00000282`00000282 00000771`00000784 fffff800`00b95000 : amdppm+0x3912
fffff800`00b9ec70 00000002`1ac191b5 : 00000282`00000282 00000771`00000784 fffff800`00b95000 00000000`00000000 : amdppm+0x2874
fffff800`00b9ec78 00000282`00000282 : 00000771`00000784 fffff800`00b95000 00000000`00000000 fffff800`02b655c4 : 0x00000002`1ac191b5
fffff800`00b9ec80 00000771`00000784 : fffff800`00b95000 00000000`00000000 fffff800`02b655c4 00000000`ffffffed : 0x00000282`00000282
fffff800`00b9ec88 fffff800`00b95000 : 00000000`00000000 fffff800`02b655c4 00000000`ffffffed fffffa80`059db2f8 : 0x00000771`00000784
fffff800`00b9ec90 00000000`00000000 : fffff800`02b655c4 00000000`ffffffed fffffa80`059db2f8 fffff800`02c0f1c0 : 0xfffff800`00b95000


SYMBOL_NAME: nt!KiPageFault+44e

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 6.1.7601.24545

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0xA_nt!KiPageFault+44e

OS_VERSION: 7.1.7601.24545

BUILDLAB_STR: win7sp1_ldr_escrow

OSPLATFORM_TYPE: x64

OSNAME: Windows 7

FAILURE_ID_HASH: {085d8b05-949f-a350-094c-3209116d6434}

Followup: MachineOwner
---------
 
Artı 0 Eksi
akiyorm dedi:
Vanguard'ı kaldırıp tekrar deneyin sorunun devam etmesi üzerine Windows 7 SP3 ya da Windows 10'a geçin. Tavsiyem Windows 10 üzerinedir?

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to Access'a pageable (or completely invalid) address at an
İnterrupt 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: FFFFD80003A19818, Memory referenced
Arg2: 000000000000000D, 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: FFFFF80002A96F40, address which referenced Memory

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

KEY_VALUES_STRING: 1

Key: Analysis. CPU. MSec
Value: 968

Key: Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007E on DESKTOP-JO5OOR3

Key: Analysis. DebugData
Value: CreateObject

Key: Analysis. DebugModel
Value: CreateObject

Key: Analysis. Elapsed. MSec
Value: 962

Key: Analysis. Memory. CommitPeak. MB
Value: 67

Key: Analysis. System
Value: CreateObject

Key: WER. OS. Branch
Value: WIN7SP1_LDR_ESCROW

Key: WER. OS. Timestamp
Value: 2020-01-02T17:07:00Z

Key: WER. OS. Version
Value: 7.1.7601.24545

ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: A

BUGCHECK_P1: FFFFD80003A19818

BUGCHECK_P2: D

BUGCHECK_P3: 1

BUGCHECK_P4: FFFFF80002A96F40

WRITE_ADDRESS: Unable to GET MmSystemRangeStart
GetUlongPtrFromAddress: Unable to read from FFFFF80002CB82F0
GetUlongPtrFromAddress: Unable to read from FFFFF80002CB84A8
FFFFD80003A19818

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: FFFFF80000B9E900 -- (.Trap 0xfffff80000b9e900)
Note: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
Rax=000000001273936C rbx=0000000000000000 rcx=FFFFF80000B9EAD0
Rdx=0000000000002711 rsi=0000000000000000 rdi=0000000000000000
Rip=FFFFF80002A96F40 rsp=FFFFF80000B9EA98 rbp=FFFFF80000B9EB50
R8=FFFFF80002C0F100 R9=00000001ACF1AC2F R10=000000000005115A
R11=FFFFF80002BFF180 R12=0000000000000000 R13=0000000000000000
R14=0000000000000000 R15=0000000000000000
İopl=0 NV up ei PL zr na po NC
Nt! KeUpdateSystemTime:
Fffff800'02A96F40 48895C2408 mov qword PTR [rsp+8],rbx SS:0018:fffff800'00B9EAA0=FFFFF80003027360
Resetting default scope

DPC_STACK_BASE: FFFFF80000BA4FB0

STACK_OVERFLOW: Stack Limit: FFFFF80000B9EFB0. Use (kF) and (!Stackusage) to investigate stack usage.

STACK_TEXT:
Fffff800'00B9E7B8 fffff800'02ABD2E9: 00000000'0000000A ffffd800'03A19818 00000000'0000000D 00000000'00000001: Nt! KeBugCheckEx
Fffff800'00B9E7C0 fffff800'02ABB0CE: 00000000'00000001 ffffd800'03A19818 00000000'00000000 fffff800'03027360: Nt! KiBugCheckDispatch+0x69
Fffff800'00B9E900 fffff800'02A96F40: Fffff800'030028E9 fffff800'03027360 fffff800'00B9EB50 fffff800'03027360: Nt! KiPageFault+0x44E
Fffff800'00B9EA98 fffff800'030028E9: Fffff800'03027360 fffff800'00B9EB50 fffff800'03027360 fffffa80'00000000: Nt! KeUpdateSystemTime
Fffff800'00B9EAA0 fffff800'02aafdef: Fffff800'02BFF180 fffff800'00B9EB50 00000000'00000000 fffff800'02BFF180: Hal! HalReturnToFirmware+0xB25
Fffff800'00B9EAD0 fffff880'04399912: Fffff880'04398874 00000002'1AC191B5 00000282'00000282 00000771'00000784: Nt! KiInterruptDispatchNoLock+0xaf
Fffff800'00B9EC68 fffff880'04398874: 00000002'1AC191B5 00000282'00000282 00000771'00000784 fffff800'00B95000: Amdppm+0x3912
Fffff800'00B9EC70 00000002'1AC191B5: 00000282'00000282 00000771'00000784 fffff800'00B95000 00000000'00000000: Amdppm+0x2874
Fffff800'00B9EC78 00000282'00000282: 00000771'00000784 fffff800'00B95000 00000000'00000000 fffff800'02B655C4 : 0x00000002`1ac191b5
Fffff800'00B9EC80 00000771'00000784: Fffff800'00B95000 00000000'00000000 fffff800'02B655C4 00000000'ffffffed : 0x00000282`00000282
Fffff800'00B9EC88 fffff800'00B95000: 00000000'00000000 fffff800'02B655C4 00000000'ffffffed fffffa80'059DB2F8 : 0x00000771`00000784
Fffff800'00B9EC90 00000000'00000000: Fffff800'02B655C4 00000000'ffffffed fffffa80'059DB2F8 fffff800'02C0F1C0 : 0xfffff800`00b95000

SYMBOL_NAME: Nt! KiPageFault+44E

MODULE_NAME: NT

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 6.1.7601.24545

STACK_COMMAND:. Thread;. Cxr; KB

FAILURE_BUCKET_ID: 0xA_nt!KiPageFault+44e

OS_VERSION: 7.1.7601.24545

BUILDLAB_STR: WIN7SP1_LDR_ESCROW

OSPLATFORM_TYPE: X64

OSNAME: Windows 7

FAILURE_ID_HASH: {085D8B05-949F-A350-094C-3209116D6434}

Followup: MachineOwner
---------
Genişletmek için tıkla...

İşletim sistemim zaten ilk başta Windows 10'du ve yine aynı hatayı alıyordum Windows 7'ye geçtim bir şey fark etmedi, yani işletim sistemiyle ilgisi olmadığını düşünüyorum.
 
Artı 0 Eksi
Son düzenleyen: Moderatör:
Artı 0 Eksi
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.

Benzer konular

F
  • Soru
Valorant IRQL_NOT_LESS_OR_EQUAL mavi ekran hatası
Mesaj
6
Görüntüleme
926
fatihozdemirel
F
jeend
  • Soru
Valorant oynarken IRQL_NOT_LESS_OR_EQUAL mavi ekran hatası
Mesaj
0
Görüntüleme
340
jeend
jeend
oggomam
  • Soru
Valorant oynarken IRQL_NOT_LESS_OR_EQUAL mavi ekran hatası
Mesaj
1
Görüntüleme
298
EgeN7
EgeN7
Netzwerke
  • Soru
IRQL_NOT_LESS_OR_EQUAL mavi ekran hatası
Mesaj
3
Görüntüleme
964
283156
2
BerkeLucky
  • Soru
Valorant oynarken IRQL_NOT_LESS_OR_EQUAL
Mesaj
2
Görüntüleme
348
KojiroHyuga04
KojiroHyuga04

Technopat Haberler

Yeni konular

Yeni mesajlar

Geri
Yukarı