Crash/Mavi Ekran Hataları

cany98

Kilopat
Katılım
15 Mayıs 2019
Mesajlar
154
Merhaba, geçen aydan beri çok defa mavi ekran hatası almaktayım. Bir ara sistemi geri yüklemekle sorunu çözdüğümü zannetmiştim ama tekrar nüksetmeye başladı. Chipset güncellemesi yaptığımda çok fazla hata almaya başlamıştım, BIOS güncellemesi sonrası çok fazla almamıştım, ekran kartı güncellemesi sonrası da çok hata ile karşılaştım. Aralık ayında aldığım hataların minidump dosyaları hakkında link aşağıdadır.

MINIDUMP ARALIK.rar

drive.google.com

Sistem özellikleri:
  • AMD Ryzen 5 3600
  • Gigabyte B450M S2H
  • Gigabyte NVIDIA GeForce RTX 2060
  • Adata XPG Gammix D30 2x8GB Ram
  • Toshiba OCZ TR200 240GB SDD
  • Seagate Barracuda 1TB HDD
 
Tarihe göre sırala Puana göre sırala

Kaldırıp tekrar yüklesem problem oluşturur mu? Benim için gerekli programlar çünkü. Ayrıca fotoğrafı yükleyemedim ama hata sayısı sıfırdı.
 
Artı 0 Eksi
Dosya oluşursa AIDA64 raporu ile birlikte gönder.

Rehber: AIDA64 HTML Raporu Oluşturma

AIDA64'ü bulunduğu yerden çalıştırın. Rapor yazana tıklayın. Özel seçim seçip ileri tıklayın. İşaretlenmiş olanların tikini kaldırın. Buradaki işaretlenmiş olanın da kaldırın. HTML seçip Son'a tıklayın. Dosyayı kaydet tıklayın. Masaüstünü seçip Kaydet'e tıklayıp kaydedin...
www.technopat.net
 
Artı 0 Eksi
Temiz kurulum yap, sürücüleri elle yükle.
MSI Afterburner, µTorrent gibi programlar kurma!


HDD kaç yıllık, bana sağlıklı gözükmedi.

Hala bellek hatası görünmekte, bellek testinin sonuna kadar beklediğine emin misin?

Kod: 
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000000, address which referenced memory

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

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

KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

DUMP_TYPE:  2

BUGCHECK_P1: 0

BUGCHECK_P2: 2

BUGCHECK_P3: 8

BUGCHECK_P4: 0

READ_ADDRESS: fffff8002cb733b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
 0000000000000000

CURRENT_IRQL:  2

FAULTING_IP:
+0
00000000`00000000 ??              ???

PROCESS_NAME:  System

CPU_COUNT: c

CPU_MHZ: e09

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 71

CPU_STEPPING: 0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  AV

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  12-21-2019 00:28:57.0280

ANALYSIS_VERSION: 10.0.18362.1 x86fre

TRAP_FRAME:  ffffd1065a7c6060 -- (.trap 0xffffd1065a7c6060)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff960737f5a740 rbx=0000000000000000 rcx=ffff960737f5ac86
rdx=00003f791f75acea rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=ffffd1065a7c61f0 rbp=0000000000000546
 r8=0000000000000000  r9=0000000000000000 r10=fffff8002e9420e0
r11=ffff960737f5a740 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
00000000`00000000 ??              ???
Resetting default scope

IP_IN_FREE_BLOCK: 0

LAST_CONTROL_TRANSFER:  from fffff8002c7d32e9 to fffff8002c7c14e0

FAILED_INSTRUCTION_ADDRESS:
+0
00000000`00000000 ??              ???

STACK_TEXT: 
ffffd106`5a7c5f18 fffff800`2c7d32e9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
ffffd106`5a7c5f20 fffff800`2c7cf62b : 00000000`00000008 00000000`00000000 00000000`00000002 ffff9607`3328b040 : nt!KiBugCheckDispatch+0x69
ffffd106`5a7c6060 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x46b


THREAD_SHA1_HASH_MOD_FUNC:  bf99962f16aee8a6a536cfcc5454c0cd4db15ac9

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  497aaf2f8d4f907c0c9bce6ce025c930b885e2b8

THREAD_SHA1_HASH_MOD:  2a7ca9d3ab5386d53fea7498e1d81b9c4a4c036b

FOLLOWUP_IP:
nt!KiPageFault+46b
fffff800`2c7cf62b 33c0            xor     eax,eax

FAULT_INSTR_CODE:  ffb0c033

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiPageFault+46b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  12dcb470

IMAGE_VERSION:  10.0.18362.535

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  46b

FAILURE_BUCKET_ID:  AV_CODE_AV_NULL_IP_nt!KiPageFault

BUCKET_ID:  AV_CODE_AV_NULL_IP_nt!KiPageFault

PRIMARY_PROBLEM_CLASS:  AV_CODE_AV_NULL_IP_nt!KiPageFault

TARGET_TIME:  2019-12-20T21:13:07.000Z

OSBUILD:  18362

OSSERVICEPACK:  535

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:  1980-01-11 18:53:20

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  5f83

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_code_av_null_ip_nt!kipagefault

FAILURE_ID_HASH:  {4ce35ff9-c5cf-d66d-0323-0f05e33f6692}

Followup:     MachineOwner
---------
 
Artı 0 Eksi

İyi de her şeyi kaldır dedin ya Sürücüleri zaten elle güncelliyorum. Bilgisayar 5-6 aylık HDD sıfır yani. Bellek testini sonuna kadar bekledim.
Çıldırmak üzereyim ya. Bildiğin Google Chrome'da dolaşırken mavi ekran yedim.

122119-9171-01.rar

drive.google.com
 
Artı 0 Eksi
Hala bellek hatası olduğunu düşünüyorum, belki konuya cevap veren diğer kişiler farklı çözüm yolları söylerler.
Kod: 
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
    component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff8026ef73358, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding this single DPC timeout

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

*** WARNING: Unable to verify timestamp for usbfilter.sys
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER:  Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME:  B450M S2H

SYSTEM_SKU:  Default string

SYSTEM_VERSION:  Default string

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  F50a

BIOS_DATE:  11/08/2019

BASEBOARD_MANUFACTURER:  Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT:  B450M S2H

BASEBOARD_VERSION:  x.x

DUMP_TYPE:  2

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff8026ef73358

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

CPU_COUNT: c

CPU_MHZ: e09

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 71

CPU_STEPPING: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x133

PROCESS_NAME:  System

CURRENT_IRQL:  d

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  12-21-2019 13:17:26.0612

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff8026ebeea3d to fffff8026ebc14e0

STACK_TEXT: 
fffff802`75075b08 fffff802`6ebeea3d : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff802`75075b10 fffff802`6ea1f61c : 00000801`69af3251 fffff802`6d116180 00000000`000265fe 00000000`000265fe : nt!KeAccumulateTicks+0x1cbfdd
fffff802`75075b70 fffff802`6e95e4b7 : ffff8e8e`77acbde0 fffff802`75067080 fffff802`75067100 00000000`00000002 : nt!KeClockInterruptNotify+0x98c
fffff802`75075f30 fffff802`6ea02a25 : 00000005`b900ee2c fffff802`6e9cc0e0 fffff802`6e9cc190 fffff802`73b72330 : hal!HalpTimerClockInterrupt+0xf7
fffff802`75075f60 fffff802`6ebc2f7a : fffff802`75067100 fffff802`6e9cc0e0 00000000`00220003 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff802`75075fb0 fffff802`6ebc34e7 : ffff8e8e`779cca30 fffff802`739ab080 00000000`75067100 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff802`75067080 fffff802`6eaa2740 : 00000000`00000000 ffffffff`ffffffff fffff802`75067330 fffff802`6ea33294 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff802`75067210 fffff802`6eaa2327 : fffff802`73b72330 fffff802`6d116180 00000000`00000000 00000000`00000000 : nt!KxWaitForSpinLockAndAcquire+0x30
fffff802`75067240 fffff802`73af1061 : ffff8e8e`77acbde0 00000000`00000000 ffff8e8e`00000d4e 00000000`00000030 : nt!KeAcquireSpinLockRaiseToDpc+0x87
fffff802`75067270 fffff802`6ea31f79 : 00000000`00000007 00000000`00000000 fffff802`75067399 ffff8e8e`772a9b20 : ACPI!ACPIDispatchIrp+0x51
fffff802`750672f0 fffff802`80547314 : 00000000`000000e0 00000000`00000000 00000000`00000001 ffff8e8e`77aa11f8 : nt!IofCallDriver+0x59
fffff802`75067330 fffff802`739aacad : ffff8e8e`77acb920 ffff8e8e`77acb920 ffff8e8e`77acb920 ffff8e8e`778cfbf0 : UsbHub3!HUBPDO_EvtDeviceWdmIrpPreprocess+0x11c4
fffff802`75067400 fffff802`6ea31f79 : ffff8e8e`77acb920 ffff8e8e`77935e10 ffff8e8e`73cec4b8 ffff8e8e`77935e10 : Wdf01000!FxDevice::DispatchWithLock+0x1ed [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1430]
fffff802`75067460 fffff802`73af14ad : ffff8e8e`77935e10 ffff8e8e`77acb920 fffff802`6ea00000 fffff802`6ea33966 : nt!IofCallDriver+0x59
fffff802`750674a0 fffff802`73af10d7 : ffff8e8e`73ae57d0 00000000`00000007 ffff8e8e`77acbe28 ffff8e8e`00000000 : ACPI!ACPIIrpDispatchDeviceControl+0xad
fffff802`750674e0 fffff802`6ea31f79 : 00000000`00000007 ffff8e8e`77a3f890 fffff802`750676d9 00000000`00000001 : ACPI!ACPIDispatchIrp+0xc7
fffff802`75067560 fffff802`803715b8 : ffff8e8e`00000000 ffff8e8e`77a3f890 fffff802`750676d9 00000000`00000001 : nt!IofCallDriver+0x59
fffff802`750675a0 ffff8e8e`00000000 : ffff8e8e`77a3f890 fffff802`750676d9 00000000`00000001 00000000`00000000 : usbfilter+0x15b8
fffff802`750675a8 ffff8e8e`77a3f890 : fffff802`750676d9 00000000`00000001 00000000`00000000 fffff802`6ea31f79 : 0xffff8e8e`00000000
fffff802`750675b0 fffff802`750676d9 : 00000000`00000001 00000000`00000000 fffff802`6ea31f79 ffff8e8e`77acb920 : 0xffff8e8e`77a3f890
fffff802`750675b8 00000000`00000001 : 00000000`00000000 fffff802`6ea31f79 ffff8e8e`77acb920 00000000`00000028 : 0xfffff802`750676d9
fffff802`750675c0 00000000`00000000 : fffff802`6ea31f79 ffff8e8e`77acb920 00000000`00000028 00000000`00000000 : 0x1


THREAD_SHA1_HASH_MOD_FUNC:  80c9f0ccc0f965fe46e926fd9b82b1aa459f68fa

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  6df733522fb7c17391fdcb32142cbce7716a49fc

THREAD_SHA1_HASH_MOD:  72634a6b3264b1fd9a86be9f6e4ea9c4d9c0beb1

FOLLOWUP_IP:
usbfilter+15b8
fffff802`803715b8 488b5c2430      mov     rbx,qword ptr [rsp+30h]

FAULT_INSTR_CODE:  245c8b48

SYMBOL_STACK_INDEX:  11

SYMBOL_NAME:  usbfilter+15b8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbfilter

IMAGE_NAME:  usbfilter.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5657b129

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  15b8

FAILURE_BUCKET_ID:  0x133_DPC_usbfilter!unknown_function

BUCKET_ID:  0x133_DPC_usbfilter!unknown_function

PRIMARY_PROBLEM_CLASS:  0x133_DPC_usbfilter!unknown_function

TARGET_TIME:  2019-12-20T22:28:31.000Z

OSBUILD:  18362

OSSERVICEPACK:  476

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:  2011-12-30 02:28:41

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  47be

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x133_dpc_usbfilter!unknown_function

FAILURE_ID_HASH:  {2500a8d6-f4f0-c5a0-6330-a17f98ce7154}

Followup:     MachineOwner
---------
 
Artı 0 Eksi
Mesaj yazmak için giriş yapmalı ya da kaydolmalısınız.

Benzer konular

  • Soru
Oyunlarda crash ve mavi ekran hataları
Mesaj
3
Görüntüleme
624
crixus1940
  • Soru
Rainbow 6 Siege Crash ve Mavi Ekran Hataları
2
Mesaj
16
Görüntüleme
2.713
MayCrasH
  • Çözüldü
Çözüldü  Windows 10 Mavi Ekran ve Crash Hataları
2
Mesaj
10
Görüntüleme
1.964
MustafaSargin
  • Soru
i9 13900KF RTX 4090 mavi ekran ve crash hataları
2
Mesaj
16
Görüntüleme
1.202
NESTER34
  • Soru
i5 12400F sistemde mavi ekran hataları
Mesaj
4
Görüntüleme
228
KindOfEmre
Menü
Giriş yap
Kaydol
Bu siteyi kullanmak için çerezler gereklidir. Siteyi kullanmaya devam etmek için çerezleri kabul etmelisiniz. Daha Fazlasını Öğren.…