Microsoft temel görüntü bağdaştırıcısı başlatılamıyor

MSHD

Hectopat
Katılım
4 Ocak 2021
Mesajlar
158
Daha fazla  
Sistem Özellikleri
İşlemci: AMD Ryzen 5 8400F Ekran Kartı: RTX 5070 Anakart: Asus Prime H610M-K
Cinsiyet
Erkek
Oyun oynarken bir anda mavi ekran verip kapandı ve sonra aygıt yöneticsine girdiğimde ünlem gözüküyor ve aygıt durumunda; bu aygıt başlatılamıyor. (kod 10) hatası gözüküyor. Ayrıca oyunlara da giremiyorum 5dk çalışıyor sonra oyun crash veriyor yardımcı olursanız sevinirm
 
Son düzenleyen: Moderatör:
Eve geçince stacağım eski forum da sttım adam tam arızası dedi RAM testi yaptım 2 saat temiz çıktı ekran kartı çöküyor onunla ilgisi olma ihtimali var mı?

Detaylıca sistemini belirt. C:Windows:minidump içindeki dosyaları yolla.

Atıyorum hemen. @claus

************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToChakraJsProvider : false

-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.031 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 42

Microsoft (R) Windows Debugger Version 10.0.27725.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\musta\OneDrive\Desktop\022225-13671-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 26100 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff807`84200000 PsLoadedModuleList = 0xfffff807`850f4770
Debug session time: Sat Feb 22 21:59:12.892 2025 (UTC + 3:00)
System Uptime: 0 days 0:15:44.526
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.....................
Loading User Symbols

Loading unloaded module list
.........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`846b8460 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9804`1d7de430=000000000000001e

Analiz halini atıyorum hemen.

*******************************************************************************
  • *
  • Bugcheck Analysis *
  • *
*******************************************************************************

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 *
* *
*************************************************************************

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1375

Key : Analysis.Elapsed.mSec
Value: 1678

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: 312

Key : Analysis.Init.Elapsed.mSec
Value: 81344

Key : Analysis.Memory.CommitPeak.Mb
Value: 87

Key : Analysis.Version.DbgEng
Value: 10.0.27725.1000

Key : Analysis.Version.Description
Value: 10.2408.27.01 amd64fre

Key : Analysis.Version.Ext
Value: 1.2408.27.1

Key : Bugcheck.Code.LegacyAPI
Value: 0x1e

Key : Bugcheck.Code.TargetModel
Value: 0x1e

Key : Dump.Attributes.AsUlong
Value: 21008

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 0

Key : Failure.Bucket
Value: AV_nt!KiDispatchException

Key : Failure.Hash
Value: {00781d15-b897-afab-75cd-f83221cbf387}


BUGCHECK_CODE: 1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: 0

BUGCHECK_P3: 8

BUGCHECK_P4: 0

FILE_IN_CAB: 022225-13671-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21008
Kernel Generated Triage Dump

FAULTING_THREAD: ffff830d91702080

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff9804`1d7de428 fffff807`84591086 : 00000000`0000001e ffffffff`c0000005 00000000`00000000 00000000`00000008 : nt!KeBugCheckEx
ffff9804`1d7de430 fffff807`8488d045 : 00000000`c0000005 00000000`00000000 07e1fe0d`57d7c4f8 ffff9804`1d7deff0 : nt!KiDispatchException+0xb16
ffff9804`1d7deb40 fffff807`84888182 : 84e6da97`e4c248ab ffff9804`1d7def80 ffffffff`ffffffff 442fbc68`6b11b0ff : nt!KiExceptionDispatch+0x145
ffff9804`1d7ded20 00000000`00000000 : fffff807`55e80998 00000000`00040286 fbffecb5`d156eaed bfe2f857`1553e54f : nt!KiPageFault+0x442


SYMBOL_NAME: nt!KiDispatchException+b16

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.26100.3194

STACK_COMMAND: .process /r /p 0xffff830d8d743040; .thread 0xffff830d91702080 ; kb

BUCKET_ID_FUNC_OFFSET: b16

FAILURE_BUCKET_ID: AV_nt!KiDispatchException

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {00781d15-b897-afab-75cd-f83221cbf387}

Followup: MachineOwner
---------

Makine windows 11 bu arada.

Sorun nedir? Hala anlayamadım.

@claus

Amd ryzen 5 8400f GTX1060 6gb 16gb ram 2 adet sata ssd

@claus dahili grafiği kapattım işe yaramıyor oyundan atıyor 5dk sonra zaten aktif olmayacağım sen gene bir şeyler yazarsın bakarım denerim.
 
Son düzenleme:

Dosya Ekleri

  • IMG_2923.jpeg
    IMG_2923.jpeg
    503,3 KB · Görüntüleme: 17
  • IMG_2921.jpeg
    IMG_2921.jpeg
    181,6 KB · Görüntüleme: 20
  • IMG_2920.jpeg
    IMG_2920.jpeg
    129 KB · Görüntüleme: 18
  • IMG_2918.jpeg
    IMG_2918.jpeg
    150,9 KB · Görüntüleme: 18
Son düzenleme:
Israr ile dosyaları yollamadığın için problemlerini kendin çözmen zorundasın artık.

Çözdüm zaten format atarak onda problem yok dump dosyasını silmişim bulamadım atamadım. Israr etmediğimi de hatırlatayım neyse önemli değil iyi geceler.
 

Technopat Haberler

Yeni konular

Geri
Yukarı