Çözüldü Sık sık mavi ekran alıyorum

Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.
Durum
Mesaj gönderimine kapalı.

Kadri Fidan

Kilopat
Katılım
17 Aralık 2014
Mesajlar
20
Daha fazla  
Cinsiyet
Erkek
Arkadaşlar merhaba, yaklaşık 2-3 aydır kullandığım sistemimde son 1, 5 haftadır hepsi farklı nedenlerden olmak üzere sık sık mavi ekran hatalarıyla karşılaşmaktayım. İlk hata BAD_SYSTEM_CONFIG_INFO idi. Ne yazık ki ne yaptıysam masaüstü ekranıma dönemedim ve format atmak zorunda kaldım. Format attıktan sonraki çıkan mavi ekranlara ait minidump dosyalarını da paylaşıyorum.


Bilgisayarı yeni topladım sayılır, yeni nesil oyunlarda bir tık zorlanan ama takır takır çalışan Intel sistemimi satıp Ryzen'e geçtim ama bu mavi ekran hataları cidden beni bilgisayardan soğuttu. Hepsinin açıklaması farklı ve internetten çözümlerine baktığımda hepsine sürücülerini güncelleştirin, Windows Update'inizi kontrol edin vs. diyor, hepsini yapıyorum. Anakart sitesinden chipset, Realtek vs. sürücülerini güncelleştirdim, BIOS'umu güncelleştirdim, ekran kartımı güncelleştirdim ama mavi ekranlar devam ediyor. Oyun oynama sırasında hiç olmadı, genelde Opera'da dolanırken ya da bilgisayar boştayken yaşandı hepsi de.

Sistem özellikleri:
Ryzen 5 3600.
MSI GTX 1070.
MSI B450M Bazooka v2.
XPG D60G 16 GB 3200 MHz.
James Donkey 480 GB SSD.
1 TB WD purple 5400 RPM.

Cidden alakası var mıdır bilmiyorum ama wallpaper engine kullanmaya başladıktan sonra oldu. Benim sistemimden daha düşük sistemlere sahip arkadaşlarımda bir sıkıntı çıkar mıyor ama sorunun gerçek sebebini bulamadığım için dipnot olarak ekleyeyim dedim.
 
Son düzenleyen: Moderatör:
Çözüm
MSI yazılımları hala sistemde yüklüler kaldır demiştim ama.

Chipset, Ses ve Ağ sürücüsünü güvenli mod ile kaldır tekrar kur.

Kod:
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: 000000000000031c, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000047, 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: fffff8060d822097, 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: 31c

BUGCHECK_P2: ff

BUGCHECK_P3: 47

BUGCHECK_P4: fffff8060d822097

WRITE_ADDRESS: fffff8060dd733b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
000000000000031c

CURRENT_IRQL:  0

FAULTING_IP:
nt!PpmIdleExecuteTransition+927
fffff806`0d822097 899d1c030000    mov     dword ptr [rbp+31Ch],ebx

CPU_COUNT: c

CPU_MHZ: e10

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

PROCESS_NAME:  System

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  02-13-2020 19:12:29.0537

ANALYSIS_VERSION: 10.0.18362.1 x86fre

TRAP_FRAME:  fffffe811a6b5650 -- (.trap 0xfffffe811a6b5650)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8060d975280 rbx=0000000000000000 rcx=33c5ed4faa2e0001
rdx=00000000002cbf16 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8060d822097 rsp=fffffe811a6b57e0 rbp=0000000000000000
r8=00000000004b1201  r9=0000000000000000 r10=00000000ffffffff
r11=ffffce7f6fc00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl zr na po nc
nt!PpmIdleExecuteTransition+0x927:
fffff806`0d822097 899d1c030000    mov     dword ptr [rbp+31Ch],ebx ss:0018:00000000`0000031c=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8060d9d33e9 to fffff8060d9c1510

STACK_TEXT:
fffffe81`1a6b5508 fffff806`0d9d33e9 : 00000000`0000000a 00000000`0000031c 00000000`000000ff 00000000`00000047 : nt!KeBugCheckEx
fffffe81`1a6b5510 fffff806`0d9cf72b : fffffe81`1a6b5620 00000000`00000002 ffffde81`d5e80251 00000000`00000001 : nt!KiBugCheckDispatch+0x69
fffffe81`1a6b5650 fffff806`0d822097 : 00006446`17e64a57 00006446`17e64a57 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x46b
fffffe81`1a6b57e0 fffff806`0d8215ce : 00000000`00000003 00000000`00000002 ffffa60b`a7d35100 00000000`00000008 : nt!PpmIdleExecuteTransition+0x927
fffffe81`1a6b5b00 fffff806`0d9c5018 : ffffffff`00000000 ffffde81`d5e80180 ffffa60b`ae6af080 00000000`00000360 : nt!PoIdle+0x36e
fffffe81`1a6b5c60 00000000`00000000 : fffffe81`1a6b6000 fffffe81`1a6b0000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x48


THREAD_SHA1_HASH_MOD_FUNC:  fbc86847fe4eb6c3c1fac4537ef130091fd9343a

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  6efa8337f1f83fb6c761e7f449f6066ab3a91f1e

THREAD_SHA1_HASH_MOD:  ee8fcf1fb60cb6e3e2f60ddbed2ec02b5748a693

FOLLOWUP_IP:
nt!PpmIdleExecuteTransition+927
fffff806`0d822097 899d1c030000    mov     dword ptr [rbp+31Ch],ebx

FAULT_INSTR_CODE:  31c9d89

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!PpmIdleExecuteTransition+927

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4269a790

IMAGE_VERSION:  10.0.18362.657

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  927

FAILURE_BUCKET_ID:  AV_CODE_AV_nt!PpmIdleExecuteTransition

BUCKET_ID:  AV_CODE_AV_nt!PpmIdleExecuteTransition

PRIMARY_PROBLEM_CLASS:  AV_CODE_AV_nt!PpmIdleExecuteTransition

TARGET_TIME:  2020-02-12T21:10:52.000Z

OSBUILD:  18362

OSSERVICEPACK:  657

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:  2005-04-23 04:40:32

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

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

ANALYSIS_SESSION_ELAPSED_TIME:  8c65

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_code_av_nt!ppmidleexecutetransition

FAILURE_ID_HASH:  {3d77750b-80a6-c195-659c-ebcffecd3d05}

Followup:     MachineOwner
---------
021420-7921-01.rar Az önce de bu hatayı verdi, bilgisayarın başında değildim sadece kmode kısmına kadarını okuyabildim sonra yeniden başlattı. Yeğenler youtubedan video izliyordu sadece.
 
XMP kapat yapıyorsan bellek frekansı yükseltme iptal et, bellekler 2133MHz çalışsın.

Hata devam ederse temiz kurulum yap tüm sürücüleri elle yükle.
Kod:
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000008, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: ContextRecord                                 ***
***                                                                   ***
*************************************************************************
*** 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: ffffffffc0000005

BUGCHECK_P2: 0

BUGCHECK_P3: 8

BUGCHECK_P4: 0

CPU_COUNT: c

CPU_MHZ: e10

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 71

CPU_STEPPING: 0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  02-14-2020 18:01:14.0906

ANALYSIS_VERSION: 10.0.18362.1 x86fre

EXCEPTION_RECORD:  ffff8542a150a000 -- (.exr 0xffff8542a150a000)
ExceptionAddress: 0000000000000000
   ExceptionCode: 0282b867
  ExceptionFlags: 8a000004
NumberParameters: 72362087
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000000
   Parameter[2]: 0000000000000000
   Parameter[3]: 0000000000000000
   Parameter[4]: 0000000000000000
   Parameter[5]: 0000000000000000
   Parameter[6]: 0000000000000000
   Parameter[7]: 0000000000000000
   Parameter[8]: 0000000000000000
   Parameter[9]: 0000000000000000
   Parameter[10]: 0000000000000000
   Parameter[11]: 0000000000000000
   Parameter[12]: 0000000000000000
   Parameter[13]: 0000000000000000
   Parameter[14]: 0000000000000000

TRAP_FRAME:  ffff800000000000 -- (.trap 0xffff800000000000)
Unable to read trap frame at ffff8000`00000000

LAST_CONTROL_TRANSFER:  from fffff8022442fea7 to fffff802243c1510

STACK_TEXT: 
ffffc088`de7d1fb8 fffff802`2442fea7 : 00000000`0000001e ffffffff`c0000005 00000000`00000000 00000000`00000008 : nt!KeBugCheckEx
ffffc088`de7d1fc0 fffff802`243d351d : ffff8542`a150a000 ffffc088`de7d2850 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x168b67
ffffc088`de7d2670 fffff802`243cf705 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x11d
ffffc088`de7d2850 00000000`00000000 : ffffc68f`81cfb640 fffff802`00000000 ffffc68f`00000000 00000000`00000000 : nt!KiPageFault+0x445


THREAD_SHA1_HASH_MOD_FUNC:  2e9ab7e93b3f60731b8608f9c5cc37cdb42d594f

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  3135bdb7147924eaa427da45cd7aa1118cae1f02

THREAD_SHA1_HASH_MOD:  d084f7dfa548ce4e51810e4fd5914176ebc66791

FOLLOWUP_IP:
nt!KiDispatchException+168b67
fffff802`2442fea7 cc              int     3

FAULT_INSTR_CODE:  86f741cc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiDispatchException+168b67

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4269a790

IMAGE_VERSION:  10.0.18362.657

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  168b67

FAILURE_BUCKET_ID:  0x1E_nt!KiDispatchException

BUCKET_ID:  0x1E_nt!KiDispatchException

PRIMARY_PROBLEM_CLASS:  0x1E_nt!KiDispatchException

TARGET_TIME:  2020-02-14T14:46:09.000Z

OSBUILD:  18362

OSSERVICEPACK:  657

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:  2005-04-23 04:40:32

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

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

ANALYSIS_SESSION_ELAPSED_TIME:  3a5a

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x1e_nt!kidispatchexception

FAILURE_ID_HASH:  {4c003660-11e1-3fb7-2474-3522eb7ee67b}

Followup:     MachineOwner
---------
 
XMP açık da, ben en temizi yeni bir format atayım ya. Şimdiye kadar atmamanın sebebi Forza Horizon 4'ü yüklemeye üşenmekti hem sildiğim MSI yazılımlarını vs. de kullanıyordum ara ara. Teşekkürler yine de.

PC'yi güvenli mod da başlatınca mavi ekran yemiyorum, güvenli modun performansa bir etkisi var mı ya? Sürekli güvenli moda başlatsam mesela?
 
Son düzenleyen: Moderatör:
AMD'nin sitesinden son Chipset'i indirdim, Windows Update ile güncelleştirmeleri yaptım, yaklaşık 1 haftadır mavi ekran almıyorum. Sorun düzeldi sanırım. Sürücülerde sıkıntı vardı herhalde. Chipset'imi anakartın sitesinden güncellemiştim öncesinde. Yardımcı olan herkese teşekkürler
 
Son düzenleyen: Moderatör:
Durum
Mesaj gönderimine kapalı.
Bu siteyi kullanmak için çerezler gereklidir. Siteyi kullanmaya devam etmek için çerezleri kabul etmelisiniz. Daha Fazlasını Öğren.…