Şimdi Ara

Mavi Ekran Hatası

Daha Fazla
Bu Konudaki Kullanıcılar: Daha Az
2 Misafir - 2 Masaüstü
5 sn
10
Cevap
0
Favori
129
Tıklama
Daha Fazla
İstatistik
  • Konu İstatistikleri Yükleniyor
0 oy
Öne Çıkar
Sayfa: 1
Giriş
Mesaj
  • Herkese merhaba

    genellikle oyun oynarken mavi ekran hatası alıyorum. sürücülerden kaynaklı olduğunu düşünüp format atıp herşeyi tekrar kurdum ama düzelmedi maalesef. yardımcı olabilirseniz sevinirim.



    Kod

    Yığını:
    ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Kernel base = 0xfffff802`12200000 PsLoadedModuleList = 0xfffff802`12e2a2c0 Debug session time: Wed Mar 12 02:36:10.797 2025 (UTC + 3:00) System Uptime: 0 days 14:21:58.430 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ............................... Loading User Symbols PEB is paged out (Peb.Ldr = 00000000`0034c018). Type ".hh dbgerr001" for details Loading unloaded module list ..................... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff802`125fe570 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffe86`ee89d990=000000000000003b 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the BugCheck Arg2: fffff8022bad7262, Address of the instruction which caused the BugCheck Arg3: fffffe86ee89e290, Address of the context record for the exception that caused the BugCheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1140 Key : Analysis.Elapsed.mSec Value: 3769 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 0 Key : Analysis.Init.CPU.mSec Value: 296 Key : Analysis.Init.Elapsed.mSec Value: 1631 Key : Analysis.Memory.CommitPeak.Mb Value: 101 Key : Analysis.Version.DbgEng Value: 10.0.27793.1000 Key : Analysis.Version.Description Value: 10.2410.02.02 amd64fre Key : Analysis.Version.Ext Value: 1.2410.2.2 Key : Bugcheck.Code.LegacyAPI Value: 0x3b Key : Bugcheck.Code.TargetModel Value: 0x3b Key : Failure.Bucket Value: AV_dxgkrnl!COREACCESS::COREACCESS Key : Failure.Exception.IP.Address Value: 0xfffff8022bad7262 Key : Failure.Exception.IP.Module Value: dxgkrnl Key : Failure.Exception.IP.Offset Value: 0x7262 Key : Failure.Hash Value: {f82e4cf2-218e-44a6-95e1-aaf7440e4d03} Key : WER.OS.Branch Value: vb_release Key : WER.OS.Version Value: 10.0.19041.1 BUGCHECK_CODE: 3b BUGCHECK_P1: c0000005 BUGCHECK_P2: fffff8022bad7262 BUGCHECK_P3: fffffe86ee89e290 BUGCHECK_P4: 0 FILE_IN_CAB: 031225-7687-01.dmp FAULTING_THREAD: ffffa18f5d651080 CONTEXT: fffffe86ee89e290 -- (.cxr 0xfffffe86ee89e290) rax=ffffe928665ed1a0 rbx=ffffa18f4e028000 rcx=fffffe86ee89ecc0 rdx=006500630069006c rsi=0000000000040000 rdi=ffffb40b93ab4de0 rip=fffff8022bad7262 rsp=fffffe86ee89ec98 rbp=ffffb40b93ab4de0 r8=fffffe86ee89ed40 r9=00000000ffffffff r10=fffff8021245a590 r11=0000000000000001 r12=0000000000000000 r13=0000000000000000 r14=ffffb40b93ab4ed0 r15=ffffb40b93ab4ef8 iopl=0 nv up ei pl nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050206 dxgkrnl!COREACCESS::COREACCESS+0x12: fffff802`2bad7262 f048ff4218 lock inc qword ptr [rdx+18h] ds:002b:00650063`00690084=???????????????? Resetting default scope BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: fm.exe STACK_TEXT: fffffe86`ee89ec98 fffff802`2bbb5ac3 : ffffa18f`5d651080 ffffb40b`93ab4eb0 ffffffff`00000000 ffffa18f`5aa54740 : dxgkrnl!COREACCESS::COREACCESS+0x12 fffffe86`ee89eca0 fffff802`2bbb3fe1 : ffffa18f`4e028000 fffff802`00000001 ffffa18f`4e028000 fffffe86`ee89ee80 : dxgkrnl!DXGPROCESS::CloseAdapter+0x2f fffffe86`ee89ed30 fffff802`2bbe53e1 : ffffb40b`93ab4f10 fffffe86`ee89ee80 00000000`00038ef7 ffffb40b`93ab4de0 : dxgkrnl!DXGADAPTER::DestroyHandle+0x11d fffffe86`ee89ed80 fffff802`2bbe6369 : ffffb40b`93ab4de0 fffffe86`00000000 ffffb40b`93ab4de0 ffffa18f`5adb80c0 : dxgkrnl!DXGPROCESS::Destroy+0x341 fffffe86`ee89eff0 fffff802`2bad6a41 : 00000000`00000000 ffffa18f`5b202130 00000000`00000000 fffff802`15a7f508 : dxgkrnl!DXGPROCESS::DestroyDxgProcess+0x105 fffffe86`ee89f140 fffff802`1284fbcf : 00000000`00000000 ffffa18f`46ca1ed0 ffffa18f`5adb80c0 ffffa18f`5d2fc7c0 : dxgkrnl!DxgkProcessNotify+0x1a1 fffffe86`ee89f190 fffff802`127e6eb0 : ffffa18f`5adb8000 ffffa18f`5adb80c0 00000000`00000000 00000000`00000000 : nt!PspCallProcessNotifyRoutines+0x213 fffffe86`ee89f260 fffff802`128499be : ffffa18f`5d6514b8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PspExitProcess+0x70 fffffe86`ee89f290 fffff802`128eb33e : ffffa18f`00000000 00000000`00000001 00000000`00000000 00000000`0034d000 : nt!PspExitThread+0x5b2 fffffe86`ee89f390 fffff802`12612505 : ffffa18f`5adb80c0 ffffa18f`5d651080 fffffe86`ee89f480 ffffa18f`00000000 : nt!NtTerminateProcess+0xde fffffe86`ee89f400 00007ffb`4786da74 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25 00000000`0014fe08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`4786da74 SYMBOL_NAME: dxgkrnl!COREACCESS::COREACCESS+12 MODULE_NAME: dxgkrnl IMAGE_NAME: dxgkrnl.sys IMAGE_VERSION: 10.0.19041.5553 STACK_COMMAND: .cxr 0xfffffe86ee89e290 ; kb BUCKET_ID_FUNC_OFFSET: 12 FAILURE_BUCKET_ID: AV_dxgkrnl!COREACCESS::COREACCESS OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {f82e4cf2-218e-44a6-95e1-aaf7440e4d03} Followup: MachineOwner ---------







  • Yönetici olarak bir komut istemi açın.

    Bunun için Arama kutusuna cmd yazın.

    Arama sonuçlarında Komut İstemi'ne sağ tıklayın ve yönetici olarak çalıştır'ı seçin.

    Onay veya yönetici parolası istenirse, parolayı yazın veya İzin Ver'e tıklayın.

    Komut İstemi penceresinde aşağıdaki komutu yazın ve Enter tuşuna basın.  Komut işleminin tamamlanması birkaç dakika sürebilir.

    DISM.exe /Online /Cleanup-image /Restorehealth 

    sfc /scannow

    winget upgrade --all

    < Bu ileti Android uygulamasından atıldı >
  • franklinda F kullanıcısına yanıt

    Merhaba. Söylediklerinizi yaptım fakat bu sefer farklı bir hata verdi.


    Kod

    Yığını:
    VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e) The video memory manager encountered a condition that it can't recover from. By crashing, the video memory manager is attempting to get enough information into the minidump such that somebody can pinpoint what lead to this condition. Arguments: Arg1: 0000000000000033, The subtype of the BugCheck: Arg2: ffffb9025b3f0d40 Arg3: 0000000000007000 Arg4: 0000000000000000 Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1359 Key : Analysis.Elapsed.mSec Value: 2129 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 0 Key : Analysis.Init.CPU.mSec Value: 296 Key : Analysis.Init.Elapsed.mSec Value: 2293 Key : Analysis.Memory.CommitPeak.Mb Value: 96 Key : Analysis.Version.DbgEng Value: 10.0.27793.1000 Key : Analysis.Version.Description Value: 10.2410.02.02 amd64fre Key : Analysis.Version.Ext Value: 1.2410.2.2 Key : Bugcheck.Code.LegacyAPI Value: 0x10e Key : Bugcheck.Code.TargetModel Value: 0x10e Key : Failure.Bucket Value: 0x10e_33_dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::_VIDMM_PROCESS_ADAPTER_INFO Key : Failure.Hash Value: {590e82e4-fa32-3e14-0943-e6b01c6637c4} Key : WER.OS.Branch Value: vb_release Key : WER.OS.Version Value: 10.0.19041.1 BUGCHECK_CODE: 10e BUGCHECK_P1: 33 BUGCHECK_P2: ffffb9025b3f0d40 BUGCHECK_P3: 7000 BUGCHECK_P4: 0 FILE_IN_CAB: $R1T80YK.dmp FAULTING_THREAD: ffffe0865cf93080 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 PROCESS_NAME: fm.exe STACK_TEXT: fffffd06`e5b56c38 fffff802`8b9b3ad0 : 00000000`0000010e 00000000`00000033 ffffb902`5b3f0d40 00000000`00007000 : nt!KeBugCheckEx fffffd06`e5b56c40 fffff802`c1795fb5 : 00000000`00007000 ffffb902`5b3f0e40 ffffe086`4e003000 ffffb902`5b3f0d40 : watchdog!WdLogEvent5_WdCriticalError+0xe0 fffffd06`e5b56c80 fffff802`c170241a : ffffb902`5b3f0d40 00000000`00000000 00000000`00000001 ffffb902`5b3f0d40 : dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::~VIDMM_PROCESS_ADAPTER_INFO+0x2348d fffffd06`e5b56cc0 fffff802`c1791381 : ffffb902`485e53e0 00000000`00000000 00000000`00000001 01000000`00100000 : dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::`scalar deleting destructor'+0xe fffffd06`e5b56cf0 fffff802`c16f2372 : ffffb902`485e53e0 ffffb902`4e8deb30 ffffe086`46efd950 00000000`000000e0 : dxgmms2!VIDMM_PROCESS::~VIDMM_PROCESS+0x29281 fffffd06`e5b56d20 fffff802`8b715a7e : 00000000`00000001 ffffb902`4e8dec00 00000000`00000000 00000000`00040282 : dxgmms2!VidMmTerminateProcess+0x12 fffffd06`e5b56d50 fffff802`8b71525f : ffffb902`4e8dec60 fffffd06`e5b56e80 00000000`00489c00 ffffb902`4e8deb30 : dxgkrnl!VidMmTerminateProcessX+0x66 fffffd06`e5b56d80 fffff802`8b716369 : ffffb902`4e8deb30 fffffd06`00000000 ffffb902`4e8deb30 ffffe086`5c3f9080 : dxgkrnl!DXGPROCESS::Destroy+0x1bf fffffd06`e5b56ff0 fffff802`8b606a41 : 00000000`00000000 ffffe086`63af7290 00000000`00000000 fffff802`7567f508 : dxgkrnl!DXGPROCESS::DestroyDxgProcess+0x105 fffffd06`e5b57140 fffff802`7164facf : 00000000`00000000 ffffe086`40e31a30 ffffe086`5c3f9080 ffffe086`51cf6f50 : dxgkrnl!DxgkProcessNotify+0x1a1 fffffd06`e5b57190 fffff802`715e6db0 : ffffe086`5c3f9000 ffffe086`5c3f9080 00000000`00000000 00000000`00000000 : nt!PspCallProcessNotifyRoutines+0x213 fffffd06`e5b57260 fffff802`716498be : ffffe086`5cf934b8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PspExitProcess+0x70 fffffd06`e5b57290 fffff802`716eb23e : ffffe086`00000000 00000000`00000001 00000000`00000000 00000000`00207000 : nt!PspExitThread+0x5b2 fffffd06`e5b57390 fffff802`71411e05 : ffffe086`5c3f9080 ffffe086`5cf93080 fffffd06`e5b57480 ffffe086`00000000 : nt!NtTerminateProcess+0xde fffffd06`e5b57400 00007ffe`d4e2da74 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25 00000000`0014fe08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`d4e2da74 SYMBOL_NAME: dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::~VIDMM_PROCESS_ADAPTER_INFO+2348d MODULE_NAME: dxgmms2 IMAGE_NAME: dxgmms2.sys IMAGE_VERSION: 10.0.19041.5607 STACK_COMMAND: .process /r /p 0xffffe0865c3f9080; .thread 0xffffe0865cf93080 ; kb BUCKET_ID_FUNC_OFFSET: 2348d FAILURE_BUCKET_ID: 0x10e_33_dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::_VIDMM_PROCESS_ADAPTER_INFO OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {590e82e4-fa32-3e14-0943-e6b01c6637c4} Followup: MachineOwner




  • ekran kartı tam marka modeli nedir

    laptopsa marka modeli nedir

  • laptop : msi gp66 leopard 11ug

    ekran kartı : rtx 3070m

  • [KaLoNa] kullanıcısına yanıt

    öncellikle driveri laptopun sitesinden indir ama kurma (nvdia indir)


    MSI Global - The Leading Brand in High-end Gaming & Professional Creation | MSI Global - The Leading Brand in High-end Gaming & Professional Creation



    sonra güvenli moda geçip ddu ile nvdia sil

    Rehber: DDU ile Sürücü Kaldırma Rehberi | Technopat Sosyal


    tekrar başlatmadan önce internetini kapat ve yeniden başşlat sonra indirdiğin driveri kur. yeniden başlat interneti tak.


    en son bunu kur update yap

    Download DirectX End-User Runtime Web Installer from Official Microsoft Download Center




    < Bu mesaj bu kişi tarafından değiştirildi potti34 -- 13 Mart 2025; 10:53:37 >




  • Ne olduktan sonra bu hatayı almaya başladınız?

  • Yapay Zeka’dan İlgili Konular
    mavi ekran hatası
    7 yıl önce açıldı
    mavi ekran hatası
    5 ay önce açıldı
    Daha Fazla Göster
  • @potti34 Söylediklerinizi uyguladım şimdilik bir sorun yok ama genellikle gece oluyor. Yarın daha net bir şey söylerim teşekkürler.



    @Venomstr İlk başta ara ara oluyordu sebepsiz yere birden kapanıyordu. Format attıktan sonra düzeldi diye düşündüm ama gece oyundan çıkarken alt f4 yaptığımda yapmaya başladı.




    < Bu mesaj bu kişi tarafından değiştirildi [KaLoNa] -- 13 Mart 2025; 23:41:16 >
  • @potti34 2-3 gündür deniyorum sorun düzeldi gibi hata vermiyor şuan. Teşekkürler.




    < Bu mesaj bu kişi tarafından değiştirildi [KaLoNa] -- 17 Mart 2025; 13:23:45 >
  • 
Sayfa: 1
- x
Bildirim
mesajınız kopyalandı (ctrl+v) yapıştırmak istediğiniz yere yapıştırabilirsiniz.