i7 3770 sistemde mavi ekran hatası

İşletim sistemi
Windows 10

Skyrise

Decapat
Katılım
3 Nisan 2020
Mesajlar
58
Merhabalar;
Sistemimde kullandığım i3 2100 işlemci yetersiz kaldığı için i7 3770'e geçiş yaptım. Eski işlemcimde de hatalar alıyordum ve çoğunlukla bellek ile ilgili oluyordu. Sistem boştayken sorun yok ancak oyun oynarken "IRQL_NOT_LESS_OR_EQUAL" hata kodlu mavi ekran hatasını alıyorum sorun nedir? Yeni bir Windows kursam sorunum çözülür mü?
Windows 10.
i7 3770.
GTX 650 Ti Boost.
8 GB RAM.

[CODE title="minidump"]Microsoft (R) Windows Debugger Version 10.0.22415.1002 AMD64.
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\mirac\Desktop\minidump\082821-10843-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available.

************* Path validation summary **************
Response Time (ms) Location.
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64.
Product: WinNt, suite: TerminalServer SingleUserTS.
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff807`0d200000 PsLoadedModuleList = 0xfffff807`0de2a3b0
Debug session time: Sat Aug 28 21:27:19.363 2021 (UTC + 3:00)
System Uptime: 0 days 4:20:58.045
Loading Kernel Symbols.
...............................................................
................................................................
................................................
Loading User Symbols.
Loading unloaded module list.
............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`0d5f5210 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffc8e`d2a29420=000000000000000a
1: kd> !analyze -v
*******************************************************************************
* *
* 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: ffffde0183e80020, memory referenced.
Arg2: 00000000000000ff, IRQL.
Arg3: 00000000000000b5, 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: fffff8070d5282d4, address which referenced memory.

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3609.

Key : Analysis.DebugAnalysisManager
Value: Create.

Key : Analysis.Elapsed.mSec
Value: 22796.

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

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

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

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

BUGCHECK_CODE: a

BUGCHECK_P1: ffffde0183e80020.

BUGCHECK_P2: ff.

BUGCHECK_P3: b5.

BUGCHECK_P4: fffff8070d5282d4.

WRITE_ADDRESS: fffff8070defb390: 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
ffffde0183e80020.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System.

TRAP_FRAME: fffffc8ed2a29560 -- (.trap 0xfffffc8ed2a29560)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000006
rdx=fffff807084d0180 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8070d5282d4 rsp=fffffc8ed2a296f0 rbp=0000000000000000
r8=ffff85090969f5a8 r9=0000000000000000 r10=0000000000000001
r11=ffffcdf829c00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl nz na pe nc.
nt!PpmIdleExecuteTransition+0x1154:
fffff807`0d5282d4 65488b042520000000 mov rax,qword ptr gs:[20h] gs:00000000`00000020=????????????????
Resetting default scope.

STACK_TEXT:
fffffc8e`d2a29418 fffff807`0d607169 : 00000000`0000000a ffffde01`83e80020 00000000`000000ff 00000000`000000b5 : nt!KeBugCheckEx
fffffc8e`d2a29420 fffff807`0d603469 : ffff8509`156f4a3c 00000000`00000000 ffff8509`0bd3a7fc 00000000`000000e8 : nt!KiBugCheckDispatch+0x69
fffffc8e`d2a29560 fffff807`0d5282d4 : 00000000`0000d56f 00000000`0000006f 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x469
fffffc8e`d2a296f0 fffff807`0d527004 : 00000000`00000000 00001fa0`00000008 00000000`00000003 00000000`00000002 : nt!PpmIdleExecuteTransition+0x1154
fffffc8e`d2a29af0 fffff807`0d5f8d34 : ffffffff`00000000 ffffde01`83a8b240 ffff8509`1afd2080 00000000`000003de : nt!PoIdle+0x374
fffffc8e`d2a29c60 00000000`00000000 : fffffc8e`d2a2a000 fffffc8e`d2a24000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54

SYMBOL_NAME: nt!PpmIdleExecuteTransition+1154

MODULE_NAME: nt.

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.631

STACK_COMMAND: .thread ; .cxr ; kb.

BUCKET_ID_FUNC_OFFSET: 1154.

FAILURE_BUCKET_ID: AV_nt!PpmIdleExecuteTransition

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release.

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {0ced0187-972d-f83e-de87-663d75806c32}

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

[/CODE]
 
Ben bir sürücü hatası olduğundan şüpheleniyorum, bellekler ile alakalıdır belki. Şu konuya bir göz atmanız yardımcı olabilir.

 
Son düzenleme:

Yeni konular

Geri
Yukarı