Intel Core 2 Duo Sistem Mavi Ekran Hatası

Bilgisayar mavi ekran hatası veriyordu, format attım belki düzelir diye hala oyun oynarken mavi ekran hatası alıyorum. Sadece Zula var, Zula'da oynarken oluyor. Driver'lerımı yükledim.

Intel Core 2 Duo 2.66-2.67 GHz.
AMD Radeon HD 5570.
ASUSTEK Computer P5Q-PRO ( anakart modeli)

Minidump dosyaları:

.
 
Bu bilgisayara en son donanımsal bakım ne zaman yapıldı? Memtest ile RAM testi yapın.

Kod:
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: fffff8017d2e2243, The address that the exception occurred at
Arg3: fffff20bd43e0628, Exception Record Address
Arg4: fffff20bd43dfe70, Context Record Address

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

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

DUMP_TYPE:  2

BUGCHECK_P1: ffffffff80000003

BUGCHECK_P2: fffff8017d2e2243

BUGCHECK_P3: fffff20bd43e0628

BUGCHECK_P4: fffff20bd43dfe70

EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - Bir veya daha fazla ba  ms z de i ken ge ersiz

FAULTING_IP: 
+0
fffff801`7d2e2243 ??              ???

EXCEPTION_RECORD:  fffff20bd43e0628 -- (.exr 0xfffff20bd43e0628)
ExceptionAddress: fffff8017d2e2243
   ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 1
   Parameter[0]: 0000000000000000

CONTEXT:  fffff20bd43dfe70 -- (.cxr 0xfffff20bd43dfe70)
rax=0000000000000088 rbx=ffffa0858d7f2420 rcx=0000000000000017
rdx=0000000000000000 rsi=ffffa08594f83c10 rdi=ffffa08592486000
rip=fffff8017d2e2243 rsp=fffff20bd43e0860 rbp=fffff20bd43e0951
 r8=0000000000000000  r9=0000000000000000 r10=ffffa08592486c48
r11=ffffd8808a8972f0 r12=0000000000000000 r13=0000000000000000
r14=ffffa085923f4000 r15=ffffa085923ea000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00000246
fffff801`7d2e2243 ??              ???
Resetting default scope

CPU_COUNT: 4

CPU_MHZ: a6a

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 17

CPU_STEPPING: a

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CORRUPT_MODULELIST_AV

BUGCHECK_STR:  AV

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-GULEPCP

ANALYSIS_SESSION_TIME:  05-15-2020 15:29:57.0228

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

LAST_CONTROL_TRANSFER:  from ffffd8808a618530 to fffff8017d2e2243

STACK_TEXT:  
fffff20b`d43df608 fffff804`073db416 : 00000000`0000007e ffffffff`80000003 fffff801`7d2e2243 fffff20b`d43e0628 : 0xfffff804`073c2390
fffff20b`d43df610 00000000`0000007e : ffffffff`80000003 fffff801`7d2e2243 fffff20b`d43e0628 fffff20b`d43dfe70 : 0xfffff804`073db416
fffff20b`d43df618 ffffffff`80000003 : fffff801`7d2e2243 fffff20b`d43e0628 fffff20b`d43dfe70 00000000`00000000 : 0x7e
fffff20b`d43df620 fffff801`7d2e2243 : fffff20b`d43e0628 fffff20b`d43dfe70 00000000`00000000 00000000`0006bcd5 : 0xffffffff`80000003
fffff20b`d43df628 fffff20b`d43e0628 : fffff20b`d43dfe70 00000000`00000000 00000000`0006bcd5 fffff804`0739d379 : 0xfffff801`7d2e2243
fffff20b`d43df630 fffff20b`d43dfe70 : 00000000`00000000 00000000`0006bcd5 fffff804`0739d379 00000000`00000003 : 0xfffff20b`d43e0628
fffff20b`d43df638 00000000`00000000 : 00000000`0006bcd5 fffff804`0739d379 00000000`00000003 fffff20b`d43e0d10 : 0xfffff20b`d43dfe70


SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID:  CORRUPT_MODULELIST_AV

PRIMARY_PROBLEM_CLASS:  CORRUPT_MODULELIST_AV

FAILURE_BUCKET_ID:  CORRUPT_MODULELIST_AV

TARGET_TIME:  2020-05-12T17:48:51.000Z

OSBUILD:  18362

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  unknown_date

ANALYSIS_SESSION_ELAPSED_TIME:  64

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:corrupt_modulelist_av

FAILURE_ID_HASH:  {fc259191-ef0c-6215-476f-d32e5dcaf1b7}

Followup:     MachineOwner
 
Bilgisayar mavi ekran hatası veriyordu, format attım belki düzelir diye hala oyun oynarken mavi ekran hatası alıyorum. Sadece Zula var, Zula'da oynarken oluyor. Driver'leri yükledim ama Driver pack ile yükledim. Tekrar mı format atmak gerekiyor.
Aldığım mavi ekran hataları:
1- Driver IRQL_NOT_LESS_OR_EQUAL.
2- IRQL_NOT_LESS_OR_EQUAL.
3- SYSTEM_THREAD_EXCEPTION_NOT_HANDLED.
4-PAGE_FAULT_IN_NONPAGED_AREA.
5-SYSTEM_SERVICE_EXCEPTION.

Intel Core 2 Duo 2.66-2.67 GHz.
AMD Radeon HD 5570.
ASUSTEK Computer P5Q-PRO ( anakart modeli)
 

Dosya Ekleri

  • Ekran Görüntüsü (1).png
    Ekran Görüntüsü (1).png
    49,7 KB · Görüntüleme: 50
  • Ekran Görüntüsü (2).png
    Ekran Görüntüsü (2).png
    50,6 KB · Görüntüleme: 50
  • Ekran Görüntüsü (3).png
    Ekran Görüntüsü (3).png
    48,7 KB · Görüntüleme: 50
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.

Technopat Haberler

Yeni konular

Geri
Yukarı