IRQL_NOT_LESS_OR_EQUAL mavi ekran hatası

İşletim sistemi
Windows 10

Lata

Femtopat
Katılım
11 Ocak 2021
Mesajlar
55
Genelde masaüstündeyken ya da video izliyorken yahut bilgisayar başından kalktığımda ben daha göremeden mavi ekran yiyip bilgisayar resetleniyor. İşlemci RAM ve yeni SSD taktırdım 2 gün önce ve o günden beri arada bir mavi ekran yiyorum durup dururken.

Bilgisayar özelliklerim:
  • Windows 10,
  • Ryzen 5 3500X,
  • GTX 1050 Ti,
  • 2 adet Kingston HyperX 8 GB 3200 MHz,
  • 1 TB wdblue HDD,
  • 500 GB SanDisk Ultra SSD.
  • ASUS Prime A320M-K anakart.
Minidumplarım da bunlar:


Umarım yeterince bilgi vermişimdir. Gerekirse daha çok bilgi paylaşabilirim. Yardımlarınızı bekliyorum, saygılar.
 

claus

Terapat
Katılım
1 Aralık 2014
Mesajlar
17.965
Makaleler
47
Çözümler
153
Farklı bir PSU ile test et ilk olarak sonrada farklı bir anakart ile. Yeni almana gerek yok, bir bilgisayarcıdan alıp test edebilirsin ücretsiz olarak.
 
KS
Lata

Lata

Femtopat
Katılım
11 Ocak 2021
Mesajlar
55
Farklı bir PSU ile test et ilk olarak sonrada farklı bir anakart ile. Yeni almana gerek yok, bir bilgisayarcıdan alıp test edebilirsin ücretsiz olarak.

1 aydır bilgisayarcıda bakımdaydı, sordum ve işlemci dışında bütün parçaların testleri ayrı ayrı yapıldığını söyledi. AMD ürüne sahip olmadığı için Ryzen işlemcimi değiştirip kontrol edemedi anakart ile PSU'nun test edildiğini söyleyebilirim yani.
Yine saatlerce almamama rağmen bilgisayarı masaüstünde boş bırakıp geldiğimde mavi ekran yedim. Sanırım bu sefer bambaşka sebepten dolayı yedim.

 
Son düzenleme:

claus

Terapat
Katılım
1 Aralık 2014
Mesajlar
17.965
Makaleler
47
Çözümler
153
O halde anakart değiş. Bana sorarsan sistemi elden çıkar ve bir daha AMD almak gibi bir hata yapma.
 

xTayfun

Centipat
Katılım
1 Kasım 2020
Mesajlar
2.102
Makaleler
8
Çözümler
5
Yer
Legendary Eagle Master
O halde anakart değiş. Bana sorarsan sistemi elden çıkar ve bir daha AMD almak gibi bir hata yapma.

Evet. Intel ile oluyorsa artık buna da çüş derim. Bende incelemek isterim.
İlk mavi ekran hatası gene bellekte. Sorun belleklerden.

Hata:
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: ffff828400000000, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000012, 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: fffff8057a328b57, address which referenced memory

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

*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 5233

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

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 44226

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

Key : Analysis.System
Value: CreateObject

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1

ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: a

BUGCHECK_P1: ffff828400000000

BUGCHECK_P2: ff

BUGCHECK_P3: 12

BUGCHECK_P4: fffff8057a328b57

READ_ADDRESS: fffff8057ab13390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8057aa27330: Unable to get Flags value from nt!KdVersionBlock
fffff8057aa27330: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
ffff828400000000

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: ffffe9013a4294a0 -- (.trap 0xffffe9013a4294a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00001bfa5c4b8efb rbx=0000000000000000 rcx=0000000000000000
rdx=00000013e66828a0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8057a328b57 rsp=ffffe9013a429630 rbp=0000000000000000
r8=0000000000000000 r9=ffff8284dc145701 r10=0000fffff8057a17
r11=ffff847b7dc00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl zr na po nc
nt!KiAcquireSpinLockInstrumented+0x7b:
fffff805`7a328b57 f0480fba2f00 lock bts qword ptr [rdi],0 ds:00000000`00000000=????????????????
Resetting default scope

STACK_TEXT:
ffffe901`3a429358 fffff805`7a21fa69 : 00000000`0000000a ffff8284`00000000 00000000`000000ff 00000000`00000012 : nt!KeBugCheckEx
ffffe901`3a429360 fffff805`7a21bd69 : fffff805`7a24387b ffff8284`f1516f68 fffff805`7a209b70 fffff805`7a1045ca : nt!KiBugCheckDispatch+0x69
ffffe901`3a4294a0 fffff805`7a328b57 : 00000000`00000200 fffff805`7a089fcc ffff8284`d58a66c0 00000000`00000000 : nt!KiPageFault+0x469
ffffe901`3a429630 fffff805`7a08f403 : ffff8284`00000000 00000000`00000001 00000013`e66828a0 00000032`ded6a000 : nt!KiAcquireSpinLockInstrumented+0x7b
ffffe901`3a429680 fffff805`7a379275 : 00000000`00000000 fffff803`a09618e3 00000000`00000000 00001bfa`5c4b7bdb : nt!KeAcquireSpinLockAtDpcLevel+0x63
ffffe901`3a4296b0 fffff805`7a08990e : 00001bfa`5c4b8efb 00000000`00000000 00000013`e66828a0 00000000`00000000 : nt!PpmIdleUpdateConcurrency+0x35
ffffe901`3a4296f0 fffff805`7a088154 : 00000000`00000000 00001f80`0014023b 00000000`00000003 00000000`00000002 : nt!PpmIdleExecuteTransition+0x163e
ffffe901`3a429af0 fffff805`7a2115a4 : ffffffff`00000000 ffff9481`ddb151c0 ffff8284`f824d340 00000000`00000678 : nt!PoIdle+0x374
ffffe901`3a429c60 00000000`00000000 : ffffe901`3a42a000 ffffe901`3a424000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54

SYMBOL_NAME: nt!KiAcquireSpinLockInstrumented+7b

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.804

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 7b

FAILURE_BUCKET_ID: AV_VRF_CODE_AV_nt!KiAcquireSpinLockInstrumented

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {0a0bc53f-93aa-fb8a-757f-42cc8ac17385}

Followup: MachineOwner
X. M. P Kapalı deneyin testi.
2. Hata 1. Hata Aynı. Sorunun kaynağı yavaşça düzeliyor.

1614232277104.png

@Caine 3. Hata System ile başlıyor ama gene ntkrnlmp.exe. RAM kaynaklı.
Hata 3:
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffff80000003, The exception code that was not handled
Arg2: fffff8076161a968, The address that the exception occurred at
Arg3: ffffc90d92c51588, Exception Record Address
Arg4: ffffc90d92c50dc0, Context Record Address

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

*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5546

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 35216

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  7e

BUGCHECK_P1: ffffffff80000003

BUGCHECK_P2: fffff8076161a968

BUGCHECK_P3: ffffc90d92c51588

BUGCHECK_P4: ffffc90d92c50dc0

EXCEPTION_RECORD:  ffffc90d92c51588 -- (.exr 0xffffc90d92c51588)
ExceptionAddress: fffff8076161a968 (nt!DebugPrompt+0x0000000000000018)
   ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 1
   Parameter[0]: 0000000000000002

CONTEXT:  ffffc90d92c50dc0 -- (.cxr 0xffffc90d92c50dc0)
rax=0000000000000002 rbx=000000000000005a rcx=fffff80760fa2d18
rdx=ffffc90d92c5001f rsi=fffff80760faafc0 rdi=000000000000002f
rip=fffff8076161a967 rsp=ffffc90d92c517c8 rbp=ffffc90d92c51920
 r8=ffffc90d92c51850  r9=0000000000000002 r10=fffff8076179c720
r11=0000000000000010 r12=0000000000000408 r13=000000000000012c
r14=000000000000012c r15=ffffc90d92bd47d0
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00040246
nt!DebugPrompt+0x17:
fffff807`6161a967 cc              int     3
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

ERROR_CODE: (NTSTATUS) 0x80000003 - { ZEL DURUM}  Kesme Noktas   Bir kesme noktas na ula  ld .

EXCEPTION_CODE_STR:  80000003

EXCEPTION_PARAMETER1:  0000000000000002

EXCEPTION_STR:  0x80000003

STACK_TEXT: 
ffffc90d`92c517c8 fffff807`6179c764     : 00000000`0000005a fffff807`60faafc0 00000000`0000002f fffff807`60f9a8a7 : nt!DebugPrompt+0x17
ffffc90d`92c517d0 fffff807`60fdc9b1     : 00000000`0000005a fffff807`60faafc0 fffff807`60fa2d14 00000000`00000007 : nt!DbgPrompt+0x44
ffffc90d`92c51820 fffff807`60fdc36f     : 00000000`0000002d ffff9b82`1ada24a0 ffff9b82`1a8f5670 00000000`00000000 : FLTMGR!FltNotifyFilterChangeDirectory+0x1901
ffffc90d`92c51aa0 fffff807`61442975     : ffff9b82`0a6fa280 ffff9b82`0a6fa280 ffff9b82`03ea5cc0 ffffc90d`92bd47e0 : FLTMGR!FltNotifyFilterChangeDirectory+0x12bf
ffffc90d`92c51b70 fffff807`61534e25     : ffff9b82`0a6fa280 00000000`00000080 ffff9b82`03edc080 00000000`00000080 : nt!ExpWorkerThread+0x105
ffffc90d`92c51c10 fffff807`6161a0d8     : ffffb881`9cd40180 ffff9b82`0a6fa280 fffff807`61534dd0 00000000`00740078 : nt!PspSystemThreadStartup+0x55
ffffc90d`92c51c60 00000000`00000000     : ffffc90d`92c52000 ffffc90d`92c4c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  nt!DebugPrompt+18

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.804

STACK_COMMAND:  .cxr 0xffffc90d92c50dc0 ; kb

BUCKET_ID_FUNC_OFFSET:  18

FAILURE_BUCKET_ID:  AV_VRF_nt!DebugPrompt

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f47fc276-52c8-da5f-1a32-8baabfc97af2}

Followup:     MachineOwner
---------
Gene aynı hata. Gene aynı sorun.


Hata 4:
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffff80000003, The exception code that was not handled
Arg2: fffff80056a0f968, The address that the exception occurred at
Arg3: ffffa505f2907588, Exception Record Address
Arg4: ffffa505f2906dc0, Context Record Address

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

*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5577

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 41285

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  7e

BUGCHECK_P1: ffffffff80000003

BUGCHECK_P2: fffff80056a0f968

BUGCHECK_P3: ffffa505f2907588

BUGCHECK_P4: ffffa505f2906dc0

EXCEPTION_RECORD:  ffffa505f2907588 -- (.exr 0xffffa505f2907588)
ExceptionAddress: fffff80056a0f968 (nt!DebugPrompt+0x0000000000000018)
   ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 1
   Parameter[0]: 0000000000000002

CONTEXT:  ffffa505f2906dc0 -- (.cxr 0xffffa505f2906dc0)
rax=0000000000000002 rbx=000000000000005a rcx=fffff80056292d18
rdx=ffffa505f290001f rsi=fffff8005629afc0 rdi=000000000000002f
rip=fffff80056a0f967 rsp=ffffa505f29077c8 rbp=ffffa505f2907920
 r8=ffffa505f2907850  r9=0000000000000002 r10=fffff80056b91720
r11=0000000000000010 r12=0000000000000408 r13=000000000000012c
r14=000000000000012c r15=ffffa505f021b7d0
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00040246
nt!DebugPrompt+0x17:
fffff800`56a0f967 cc              int     3
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

ERROR_CODE: (NTSTATUS) 0x80000003 - { ZEL DURUM}  Kesme Noktas   Bir kesme noktas na ula  ld .

EXCEPTION_CODE_STR:  80000003

EXCEPTION_PARAMETER1:  0000000000000002

EXCEPTION_STR:  0x80000003

STACK_TEXT: 
ffffa505`f29077c8 fffff800`56b91764     : 00000000`0000005a fffff800`5629afc0 00000000`0000002f fffff800`5628a8a7 : nt!DebugPrompt+0x17
ffffa505`f29077d0 fffff800`562cc9b1     : 00000000`0000005a fffff800`5629afc0 fffff800`56292d14 00000000`00000007 : nt!DbgPrompt+0x44
ffffa505`f2907820 fffff800`562cc36f     : 00000000`0000002d ffffcf8f`08ead420 ffffcf8f`0aefe4b0 00000000`00000000 : FLTMGR!FltNotifyFilterChangeDirectory+0x1901
ffffa505`f2907aa0 fffff800`56837975     : ffffcf8f`1a57c040 ffffcf8f`1a57c040 ffffcf8e`f56c2c40 ffffa505`f021b7e0 : FLTMGR!FltNotifyFilterChangeDirectory+0x12bf
ffffa505`f2907b70 fffff800`56929e25     : ffffcf8f`1a57c040 00000000`00000080 ffffcf8e`f56db080 00000000`00000000 : nt!ExpWorkerThread+0x105
ffffa505`f2907c10 fffff800`56a0f0d8     : ffffba81`e7d0a180 ffffcf8f`1a57c040 fffff800`56929dd0 00000000`003e8800 : nt!PspSystemThreadStartup+0x55
ffffa505`f2907c60 00000000`00000000     : ffffa505`f2908000 ffffa505`f2902000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  nt!DebugPrompt+18

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.804

STACK_COMMAND:  .cxr 0xffffa505f2906dc0 ; kb

BUCKET_ID_FUNC_OFFSET:  18

FAILURE_BUCKET_ID:  AV_VRF_nt!DebugPrompt

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f47fc276-52c8-da5f-1a32-8baabfc97af2}

Followup:     MachineOwner
---------
Bu sefer Kernel ile ilgili. RAM ilgili bir şey yok 5. Hatada.


Hata 5 KERNEL_SECURITY_CHECK_FAILURE:
KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure.  The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: fffff30b6d9a9f90, Address of the trap frame for the exception that caused the bugcheck
Arg3: fffff30b6d9a9ee8, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

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

*** WARNING: Unable to verify timestamp for win32kfull.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 6327

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 46831

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  139

BUGCHECK_P1: 3

BUGCHECK_P2: fffff30b6d9a9f90

BUGCHECK_P3: fffff30b6d9a9ee8

BUGCHECK_P4: 0

TRAP_FRAME:  fffff30b6d9a9f90 -- (.trap 0xfffff30b6d9a9f90)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffbd0a23242788 rbx=0000000000000000 rcx=0000000000000003
rdx=ffffbd0a2578b7f0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff802804fbc4e rsp=fffff30b6d9aa120 rbp=ffffbd0a2578b7c0
 r8=ffffbd0a2578b7e8  r9=0000000000000001 r10=0000fffff802808b
r11=ffffbf7e25600000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po cy
nt!KeRundownQueueCommon+0x252:
fffff802`804fbc4e cd29            int     29h
Resetting default scope

EXCEPTION_RECORD:  fffff30b6d9a9ee8 -- (.exr 0xfffff30b6d9a9ee8)
ExceptionAddress: fffff802804fbc4e (nt!KeRundownQueueCommon+0x0000000000000252)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000003
Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Discord.exe

ERROR_CODE: (NTSTATUS) 0xc0000409 - Sistem, bu uygulamada y   n tabanl  bir arabelle in ta t   n  alg lad . Bu ta ma, k t  niyetli bir kullan c n n bu uygulaman n denetimini ele ge irmesine olanak verebilir.

EXCEPTION_CODE_STR:  c0000409

EXCEPTION_PARAMETER1:  0000000000000003

EXCEPTION_STR:  0xc0000409

STACK_TEXT: 
fffff30b`6d9a9c68 fffff802`80607a69     : 00000000`00000139 00000000`00000003 fffff30b`6d9a9f90 fffff30b`6d9a9ee8 : nt!KeBugCheckEx
fffff30b`6d9a9c70 fffff802`80607e90     : ffffbd0a`152b2a60 fffff30b`6d9aa430 ffffbd0a`1f9ee080 fffff30b`6d9aa4d0 : nt!KiBugCheckDispatch+0x69
fffff30b`6d9a9db0 fffff802`80606223     : 00000000`00000000 00000000`00000000 00000000`00000103 00000000`00000000 : nt!KiFastFailDispatch+0xd0
fffff30b`6d9a9f90 fffff802`804fbc4e     : 00000000`00000000 fffff802`80828ccc ffffbd0a`152a5220 00000000`00000001 : nt!KiRaiseSecurityCheckFailure+0x323
fffff30b`6d9aa120 fffff802`804fb97e     : ffffbd0a`2578b7c0 ffffbd0a`2578b7c0 fffff30b`6d9aa201 00000000`00000000 : nt!KeRundownQueueCommon+0x252
fffff30b`6d9aa170 fffff802`804fb7f8     : ffffbd0a`2578b790 fffff30b`6d9aa200 00000000`00000000 00000000`00000000 : nt!KeRundownQueueEx+0x66
fffff30b`6d9aa1b0 fffff802`808bedbb     : ffffbd0a`2578b790 00000000`00000000 ffffbd0a`152a5220 00000000`00000000 : nt!IopDeleteIoCompletionInternal+0x50
fffff30b`6d9aa210 fffff802`807fb250     : ffff8395`2be82500 00000000`000030ec ffffbd0a`1f9ee080 ffff8b0e`e404b080 : nt!IopDeleteIoCompletion+0xb
fffff30b`6d9aa240 fffff802`80461277     : 00000000`00000000 00000000`00000000 fffff30b`6d9aa5d0 ffffbd0a`2578b7c0 : nt!ObpRemoveObjectRoutine+0x80
fffff30b`6d9aa2a0 fffff802`8046119e     : ffff83b5`4459b010 ffff83b5`4459b010 00000000`00000000 fffff30b`6d9aa128 : nt!ObfDereferenceObjectWithTag+0xc7
fffff30b`6d9aa2e0 ffff8395`2bca0201     : ffff83b5`4459b010 fffff30b`00000000 ffff83b5`4459b010 ffffbf7e`25600000 : nt!HalPutDmaAdapter+0xe
fffff30b`6d9aa310 ffff8395`2bc9f5f2     : 00000000`00000000 ffff83b5`4459b010 fffff30b`6d9aa5d0 ffff83b5`4459b010 : win32kbase!zzzDestroyQueue+0x451
fffff30b`6d9aa340 ffff8395`2bcc3053     : ffff83b5`4459b010 00000000`00000000 ffffbd0a`23242580 ffff8395`2bec42a0 : win32kbase!HMPkheFromPheWorker+0x1402
fffff30b`6d9aa4d0 ffff8395`2b228c0b     : 00000000`00000001 00000000`00000001 ffffbd0a`23242580 00000000`00000000 : win32kbase!UserThreadCallout+0x553
fffff30b`6d9aa6c0 00000000`00000001     : 00000000`00000001 ffffbd0a`23242580 00000000`00000000 fffff30b`6d9aaa08 : win32kfull+0x28c0b
fffff30b`6d9aa6c8 00000000`00000001     : ffffbd0a`23242580 00000000`00000000 fffff30b`6d9aaa08 ffff8395`2bc92d0c : 0x1
fffff30b`6d9aa6d0 ffffbd0a`23242580     : 00000000`00000000 fffff30b`6d9aaa08 ffff8395`2bc92d0c 00000000`00000001 : 0x1
fffff30b`6d9aa6d8 00000000`00000000     : fffff30b`6d9aaa08 ffff8395`2bc92d0c 00000000`00000001 fffff30b`6d9aa7f0 : 0xffffbd0a`23242580


SYMBOL_NAME:  win32kbase!zzzDestroyQueue+451

MODULE_NAME: win32kbase

IMAGE_NAME:  win32kbase.sys

IMAGE_VERSION:  10.0.19041.746

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  451

FAILURE_BUCKET_ID:  0x139_3_CORRUPT_LIST_ENTRY_win32kbase!zzzDestroyQueue

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {90dbe9f4-12f8-df4e-56b5-3dcaabb1ba95}

Followup:     MachineOwner
---------
@Caine @claus Bu 5 hatanın 4'ü RAM. 5. Hata ise Windows sebep oluyor.
 
Son düzenleme:

GadordaeR

Hectopat
Katılım
9 Aralık 2015
Mesajlar
47
Çözümler
1
Yani bir aydır sürekli sürücü güncelleyip duruyorum bir işe yaramıyor açıkçası, teknik servise göre de sürücü hatası değil diyor. Deneme yanılma yapıp bulmaya çalışıyor fakat hala bir sonuç çıkmadı haftalardır anakart sıkıntılı demişlerdi yükseltip B450-MK yaptım farklı RAM takıp denendi fakat hala çalışmıyor, en son işlemci ile ekran kartı olabilir dedi. Bilemiyorum artık sıkıntı ne neden sürekli hata alıyorum boşuna anakart değiştirmiş gibi hissediyorum. Ethernet adaptörü değil direkt olarak kablosunu kullanıyorum bu arada.



Buna bakacağım fakat BIOS'tan fazla anlamıyorum arayıp bulmaya çalışırım fakat sorun bu değilse daha kötü bir hale sokmasın bilgisayarı? Geri dönüşü olur değil mi bunu yaparsam?
Daha kötü bir hale sokmaz. Aksine hata düzelicek. Denemenizi tavsiye ediyorum.
 

claus

Terapat
Katılım
1 Aralık 2014
Mesajlar
17.965
Makaleler
47
Çözümler
153
Ben söyleyeceğimi söyledim.
 
KS
Lata

Lata

Femtopat
Katılım
11 Ocak 2021
Mesajlar
55
Ryzen 5 3500X'imi servise götürdüm ve parasını iade ettiler. Ben de yerine gidip Ryzen 3600 aldım ve bir haftadır hiçbir hata almadım sanırsam sorun çözüldü yardım eden herkese teşekkürler.
 

Caine

Megapat
Katılım
5 Ağustos 2019
Mesajlar
7.794
Makaleler
1
Çözümler
140
Ryzen 5 3500X'imi servise götürdüm ve parasını iade ettiler. Ben de yerine gidip Ryzen 3600 aldım ve bir haftadır hiçbir hata almadım sanırsam sorun çözüldü yardım eden herkese teşekkürler.
R5 3500X işlemcileri büyük ihtimalle kronik sorunlu. R5 3500X işlemcisi ile mavi ekran alanlar genelde işlemci değiştirdiklerinde sorun çözülmüş oluyor. Çok ilginç.
 

Yeni konular

Yukarı