IRQL_NOT_LESS_OR_EQUAL (a) mavi ekran hatası

  • Konuyu başlatan 231981
  • Başlangıç Tarihi
  • Mesaj 29
  • Görüntüleme 2.120

231981

Kilopat
Katılım
11 Ekim 2018
Mesajlar
4.814
Makaleler
1
Çözümler
10
Herkese iyi forumlar arkadaşlar. Son 1 haftadır mavi ekran sorunu yaşıyorum fakat 3-4 gündür daha da sıklaştı bu durum. Mutfağa gidip su içip geliyorum sistem reset atmış masaüstü beni karşılar vaziyette oluyor açık bıraktığım programlardan anlıyorum reset attığını. Dün Steam üzerinden biraz oyun oynayayım dedim Left 4 Dead 2 oyununa girdim 10 dakika sonra oyun esnasında mavi ekran verdi daha sonra YouTube üzerinden video izlerken de bir kere mavi ekran verdi. Ben de sanırım Windows ile alakalı sorun vardır dedim Microsoft'un sitesinden en güncel olan 2004 versiyonunu indirdim format attım Pro lisansım vardı onunla lisansladım buraya kadar sorun yok ama ben formatı atalı 3-4 saat oldu bu aralıkta 4 kere mavi ekran verdi şu an ne yapacağımı bilmiyorum. Blue Screen View ile baktım pek bir şey anlamadım. Yardımcı olabilir misiniz? Formattan sonra hiçbir işlem yapmadım sürücüleri resmi sitelerinden indirip kurdum internet tarayıcımı kurdum bir de bütün Windows Update'leri yaptım başka da bir işlem yapmadım masaüstüm tertemiz. Yardımcı olursanız sevinirim.
Windows 10 2004 Pro kurulu sistemde.

Ek Açıklama 2020-10-07 091251.jpg
 
Son düzenleyen: Moderatör:
 
 

Bora dere yazacaktım hızlısınız hocam :D.
 


Buyurun;
 
DDU ile ekran kartı sürücüsünü kaldırıp güncelini yükleyiniz.
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: ffff9b8f471d7158, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff802182404aa, address which referenced memory

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


OVERLAPPED_MODULE: Address regions for 'cldflt' and 'dump_storpor' overlap

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 ffff9b8f471d7158

CURRENT_IRQL:  2

FAULTING_IP:
nt!KiTryUnwaitThread+1ba
fffff802`182404aa 483901          cmp     qword ptr [rcx],rax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  AV

PROCESS_NAME:  msedge.exe

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

TRAP_FRAME:  ffff8901bbe0c810 -- (.trap 0xffff8901bbe0c810)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff9b8f48731158 rbx=0000000000000000 rcx=ffff9b8f471d7158
rdx=ffff9b8f47a7a118 rsi=0000000000000000 rdi=0000000000000000
rip=fffff802182404aa rsp=ffff8901bbe0c9a0 rbp=ffffb200b399f180
 r8=0000000000000000  r9=0000000000000000 r10=0000fffff8021800
r11=ffffc383ee8b85c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiTryUnwaitThread+0x1ba:
fffff802`182404aa 483901          cmp     qword ptr [rcx],rax ds:ffff9b8f`471d7158=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff802183efe29 to fffff802183ddf40

STACK_TEXT: 
ffff8901`bbe0c6c8 fffff802`183efe29 : 00000000`0000000a ffff9b8f`471d7158 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffff8901`bbe0c6d0 fffff802`183ec129 : ffff9b8f`00000000 ffff9b8f`00000000 00000000`00000000 00000000`00000001 : nt!KiBugCheckDispatch+0x69
ffff8901`bbe0c810 fffff802`182404aa : 00000000`00000000 fffff802`185f95b1 00000000`00000000 00000000`00000001 : nt!KiPageFault+0x469
ffff8901`bbe0c9a0 fffff802`1823e318 : ffff9b8f`4e9d1ce0 00000000`00000000 ffffb200`b399f180 00000000`00000000 : nt!KiTryUnwaitThread+0x1ba
ffff8901`bbe0ca00 fffff802`1860c7bd : ffff9b8f`00000000 ffff8901`bbe0cb80 ffff8901`bbe0caa8 ffff9b8f`487311c0 : nt!KeSetEvent+0x158
ffff8901`bbe0ca90 fffff802`183ef878 : ffff9b8f`486f4080 00000000`00000000 00000000`00000000 ffff9b8f`00000000 : nt!NtSetEvent+0xbd
ffff8901`bbe0cb00 00007fff`a6bcbf84 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
0000001a`063fe9f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`a6bcbf84


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff8021838516e-fffff80218385171  4 bytes - nt!MiFreeUltraMapping+32
    [ a0 7d fb f6:c0 be 7d fb ]
    fffff802184879d3-fffff802184879d4  2 bytes - nt!MiRaisedIrqlFault+14c14f (+0x102865)
    [ 80 fa:00 ad ]
6 errors : !nt (fffff8021838516e-fffff802184879d4)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_LARGE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:memory_corruption_large

FAILURE_ID_HASH:  {e29154ac-69a4-0eb8-172a-a860f73c0a3c}

Followup: memory_corruption
---------
 
DDU ile ekran kartı sürücüsünü kaldırıp güncelini yükleyiniz.
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: ffff9b8f471d7158, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff802182404aa, address which referenced memory

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


OVERLAPPED_MODULE: Address regions for 'cldflt' and 'dump_storpor' overlap

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
ffff9b8f471d7158

CURRENT_IRQL:  2

FAULTING_IP:
nt!KiTryUnwaitThread+1ba
fffff802`182404aa 483901          cmp     qword ptr [rcx],rax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  AV

PROCESS_NAME:  msedge.exe

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

TRAP_FRAME:  ffff8901bbe0c810 -- (.trap 0xffff8901bbe0c810)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff9b8f48731158 rbx=0000000000000000 rcx=ffff9b8f471d7158
rdx=ffff9b8f47a7a118 rsi=0000000000000000 rdi=0000000000000000
rip=fffff802182404aa rsp=ffff8901bbe0c9a0 rbp=ffffb200b399f180
r8=0000000000000000  r9=0000000000000000 r10=0000fffff8021800
r11=ffffc383ee8b85c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiTryUnwaitThread+0x1ba:
fffff802`182404aa 483901          cmp     qword ptr [rcx],rax ds:ffff9b8f`471d7158=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff802183efe29 to fffff802183ddf40

STACK_TEXT:
ffff8901`bbe0c6c8 fffff802`183efe29 : 00000000`0000000a ffff9b8f`471d7158 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffff8901`bbe0c6d0 fffff802`183ec129 : ffff9b8f`00000000 ffff9b8f`00000000 00000000`00000000 00000000`00000001 : nt!KiBugCheckDispatch+0x69
ffff8901`bbe0c810 fffff802`182404aa : 00000000`00000000 fffff802`185f95b1 00000000`00000000 00000000`00000001 : nt!KiPageFault+0x469
ffff8901`bbe0c9a0 fffff802`1823e318 : ffff9b8f`4e9d1ce0 00000000`00000000 ffffb200`b399f180 00000000`00000000 : nt!KiTryUnwaitThread+0x1ba
ffff8901`bbe0ca00 fffff802`1860c7bd : ffff9b8f`00000000 ffff8901`bbe0cb80 ffff8901`bbe0caa8 ffff9b8f`487311c0 : nt!KeSetEvent+0x158
ffff8901`bbe0ca90 fffff802`183ef878 : ffff9b8f`486f4080 00000000`00000000 00000000`00000000 ffff9b8f`00000000 : nt!NtSetEvent+0xbd
ffff8901`bbe0cb00 00007fff`a6bcbf84 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
0000001a`063fe9f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`a6bcbf84


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff8021838516e-fffff80218385171  4 bytes - nt!MiFreeUltraMapping+32
    [ a0 7d fb f6:c0 be 7d fb ]
    fffff802184879d3-fffff802184879d4  2 bytes - nt!MiRaisedIrqlFault+14c14f (+0x102865)
    [ 80 fa:00 ad ]
6 errors : !nt (fffff8021838516e-fffff802184879d4)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_LARGE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:memory_corruption_large

FAILURE_ID_HASH:  {e29154ac-69a4-0eb8-172a-a860f73c0a3c}

Followup: memory_corruption
---------

Güncel sürümü kurulu zaten.
 
Uyarı! Bu konu 5 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.

Technopat Haberler

Yeni konular

Geri
Yukarı