Şimdi Ara

Mavi Ekran hatası

Daha Fazla
Bu Konudaki Kullanıcılar: Daha Az
2 Misafir (1 Mobil) - 1 Masaüstü1 Mobil
5 sn
8
Cevap
0
Favori
265
Tıklama
Daha Fazla
İstatistik
  • Konu İstatistikleri Yükleniyor
0 oy
Öne Çıkar
Sayfa: 1
Giriş
Mesaj
  • Öncelikle iyi günler bu aralar laptobumda mavi ekran hatası çıkmaya başladı İ5 9300H 16GB Ram GTX 1650 ekran kartı Windows 10


    Kod

    Yığını:
    Microsoft (R) Windows Debugger Version 10.0.22415.1002 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\081321-7953-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 = 0xfffff803`0fc00000 PsLoadedModuleList = 0xfffff803`1082a190 Debug session time: Fri Aug 13 19:43:03.862 2021 (UTC + 3:00) System Uptime: 0 days 3:07:32.554 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ .......... Loading User Symbols Loading unloaded module list .................. For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff803`0fff71d0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffda00`d88678f0=0000000000000124 4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the WHEA_ERROR_RECORD structure to get more details. Arguments: Arg1: 0000000000000000, Machine Check Exception Arg2: ffffc205c81e9028, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value. Arg4: 000000000100110a, Low order 32-bits of the MCi_STATUS value. 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: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION *** *** *** ************************************************************************* *** WARNING: Unable to verify checksum for win32k.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 5187 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 14123 Key : Analysis.Init.CPU.mSec Value: 374 Key : Analysis.Init.Elapsed.mSec Value: 10271 Key : Analysis.Memory.CommitPeak.Mb Value: 88 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: 124 BUGCHECK_P1: 0 BUGCHECK_P2: ffffc205c81e9028 BUGCHECK_P3: be000000 BUGCHECK_P4: 100110a BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: ffffda00`d88678e8 fffff803`100b41aa : 00000000`00000124 00000000`00000000 ffffc205`c81e9028 00000000`be000000 : nt!KeBugCheckEx ffffda00`d88678f0 fffff803`0e7c15b0 : 00000000`00000000 ffffc205`c81e9028 ffffc205`c3bf67e0 ffffc205`c81e9028 : nt!HalBugCheckSystem+0xca ffffda00`d8867930 fffff803`101b60ee : 00000000`00000000 ffffda00`d88679d9 ffffc205`c81e9028 ffffc205`c3bf67e0 : PSHED!PshedBugCheckSystem+0x10 ffffda00`d8867960 fffff803`100b5ad1 : ffffc205`c5dc54c0 ffffc205`c5dc54c0 ffffc205`c3bf6830 ffffc205`c3bf67e0 : nt!WheaReportHwError+0x46e ffffda00`d8867a40 fffff803`100b5e43 : 00000000`00000004 ffffc205`c3bf6830 ffffc205`c3bf67e0 00000000`00000004 : nt!HalpMcaReportError+0xb1 ffffda00`d8867bb0 fffff803`100b5d20 : ffffc205`c38f97d0 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandlerCore+0xef ffffda00`d8867c00 fffff803`100b5f71 : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0 ffffda00`d8867c40 fffff803`100b51db : 00000000`00000000 00000000`00000000 ffffda00`d8867ed0 00000000`00000000 : nt!HalpMceHandlerWithRendezvous+0xc9 ffffda00`d8867c70 fffff803`100b7a25 : ffffc205`c38f97d0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0x5f ffffda00`d8867ca0 fffff803`1010d3d9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x35 ffffda00`d8867cd0 fffff803`100062fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9 ffffda00`d8867d00 fffff803`10005fb7 : 0000001a`00000000 fffff803`10005eec ffffda00`d8800180 00000000`00000000 : nt!KxMcheckAbort+0x7a ffffda00`d8867e40 fffff803`0fe1985f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277 ffffbe0e`9f25f500 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiCheckForTimerExpiration+0x15f MODULE_NAME: GenuineIntel IMAGE_NAME: GenuineIntel.sys STACK_COMMAND: .thread ; .cxr ; kb FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {5371cb52-c3d9-558e-47d4-d31c09567ca2} Followup: MachineOwner ---------



    < Bu mesaj bu kişi tarafından değiştirildi seydihan623 -- 13 Ağustos 2021; 22:33:4 >







  • memory test yap dostum, hardware hatasi var, memory testden gecerse, yine de intelin processor diagnostic tool ile cpuya da bak...

  • memory testi nasıl yapıcam bi uygulama öneriniz varmı

  • seydihan623 S kullanıcısına yanıt

    memtes86 diye bi uygulama var, youtubeden bak nasil kullanildigina, memtest86 ile yapabilirisn testi, baya bi suruyor yalniz...

  • Ram kontrolu yapınız kaç tane ram var bilmiyorum.


    Bilginiz varsa Ram ları söküp silgi ile slota giren kısımlarını silin.Tekrar takın hala sorun devam ediyorsa Ram lardan biri yada hepsi arızalı olabilir.


    Hiç bilgini yoksa iyi bir bilgisayarcıya gösterin.

  • memory testimi yaptım ve herhangi bi sorun gözükmedi bende anlamadım şuan yazılımsalmı donanımsalmı kafayı yicem artık

  • seydihan623 S kullanıcısına yanıt

    O zaman bi temiz kurulumla deneyin, bir de hic undervolt uygulamayin cpuya basta...

  • Yapay Zeka’dan İlgili Konular
    MAVİ EKRAN HATASI
    2 yıl önce açıldı
    Daha Fazla Göster
    
Sayfa: 1
- x
Bildirim
mesajınız kopyalandı (ctrl+v) yapıştırmak istediğiniz yere yapıştırabilirsiniz.