Minidump dosya analizi

musallat.exe · 5 Temmuz 2023

Linki paylaştım. Yardımcı olursanız sevinirim.

070523-18640-01.rar

drive.google.com

armas · 5 Temmuz 2023

Ekran kartı sürücünü kaldırıp tekrar kurar mısın?

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

Display Driver Uninstaller (DDU), zamanla bilgisayara takılan farklı monitörler, üst üste güncellenen sürücüler ve Windows güncellemeleri sonrası biriken kayıt defteri ve sürücü dosyalarını silerek temiz bir sürücü kurulumunun yolunu açan kullanışlı bir araçtır. Adım adım sürücü temizliği...

www.technopat.net

musallat.exe · 5 Temmuz 2023

armas dedi:
Ekran kartı sürücünü kaldırıp tekrar kurar mısın?

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

Display Driver Uninstaller (DDU), zamanla bilgisayara takılan farklı monitörler, üst üste güncellenen sürücüler ve Windows güncellemeleri sonrası biriken kayıt defteri ve sürücü dosyalarını silerek temiz bir sürücü kurulumunun yolunu açan kullanışlı bir araçtır. Adım adım sürücü temizliği...

www.technopat.net

Sürücü açısından bilgisayarım temiz, NVIDIA ve AMD için ayrı ayrı DDU yapıp AMD driverını kurmuştum en son.

armas · 5 Temmuz 2023

AMD son sürücüsü WHQL mi? Değilse önceki sürümlerden WHQL bir tane kurun.

musallat.exe · 5 Temmuz 2023

armas dedi:
AMD son sürücüsü WHQL mi?

Evet WHQL. Minidump dosyamı okuyabildiniz mi, ne çıktı acaba?

armas · 5 Temmuz 2023

Evet okudum, ekran kartı sürücün hatalı çıktı. Başka bakacak arkadaşlar için de atayım buraya. Hata adını internette araştırırsan AMD'nin kendi forumunda da çözümünün sürücü ile alakalı olduğunu görebilirsin.

Kod:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff807516fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding the cumulative timeout
Arg4: 0000000000000000

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

*** WARNING: Unable to verify timestamp for amdkmdag.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                                   ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2265

    Key  : Analysis.Elapsed.mSec
    Value: 3601

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 389

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: 0x133_ISR_amdkmdag!unknown_function

    Key  : Failure.Hash
    Value: {ce335412-b260-6bc1-3af9-ea5584f041c4}

    Key  : Hypervisor.Enlightenments.Value
    Value: 68669340

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 417cf9c

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 1

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 4853999

    Key  : Hypervisor.Flags.ValueHex
    Value: 4a10ef

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7


BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff807516fb320

BUGCHECK_P4: 0

FILE_IN_CAB:  070523-18640-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
ffffa000`9b29ae18 fffff807`50e43b14     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff807`516fb320 : nt!KeBugCheckEx
ffffa000`9b29ae20 fffff807`50c813c3     : 000b933a`5549d530 ffffa000`9b281180 00000000`00000000 ffffa000`9b281180 : nt!KeAccumulateTicks+0x1bfef4
ffffa000`9b29ae80 fffff807`50c80eaa     : ffffe10f`96730480 ffffd58e`d617e8b0 00000000`001cfb00 00000000`00000000 : nt!KeClockInterruptNotify+0x453
ffffa000`9b29af30 fffff807`50d3ec65     : ffffe10f`96730480 fffff807`50d232b7 00000000`00000000 00000000`00000000 : nt!HalpTimerClockIpiRoutine+0x1a
ffffa000`9b29af60 fffff807`50dfdfca     : ffffd58e`d617e8b0 ffffe10f`96730480 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffa000`9b29afb0 fffff807`50dfe797     : ffffd58e`d617ea20 ffffd58e`d617ea78 ffffe10f`96730480 ffffd58e`d617ea78 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffd58e`d617e830 fffff807`50cde607     : ffffffff`ffffffd2 fffff807`50c950de 00000000`00000010 00000000`00040282 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffd58e`d617e9c0 fffff807`50c950da     : 00000000`00000000 ffffd0dc`4d18043d ffffd58e`d617f501 ffffe10f`bdf98020 : nt!KeYieldProcessorEx+0x17
ffffd58e`d617e9f0 fffff807`50c96de3     : 00000000`d2e55d0d 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxWaitForLockOwnerShip+0x2a
ffffd58e`d617ea20 fffff807`84626a94     : ffffe10f`bd3f5cb0 ffffe10f`bf233860 00000000`001cfa80 ffffe10f`bf233860 : nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x73
ffffd58e`d617ea50 ffffe10f`bd3f5cb0     : ffffe10f`bf233860 00000000`001cfa80 ffffe10f`bf233860 fffff807`84c44000 : amdkmdag+0xc6a94
ffffd58e`d617ea58 ffffe10f`bf233860     : 00000000`001cfa80 ffffe10f`bf233860 fffff807`84c44000 00000000`00000000 : 0xffffe10f`bd3f5cb0
ffffd58e`d617ea60 00000000`001cfa80     : ffffe10f`bf233860 fffff807`84c44000 00000000`00000000 ffffe10f`bd3f5cb9 : 0xffffe10f`bf233860
ffffd58e`d617ea68 ffffe10f`bf233860     : fffff807`84c44000 00000000`00000000 ffffe10f`bd3f5cb9 00000000`00000000 : 0x1cfa80
ffffd58e`d617ea70 fffff807`84c44000     : 00000000`00000000 ffffe10f`bd3f5cb9 00000000`00000000 ffffe10f`bd3f5c01 : 0xffffe10f`bf233860
ffffd58e`d617ea78 00000000`00000000     : ffffe10f`bd3f5cb9 00000000`00000000 ffffe10f`bd3f5c01 00000000`00000000 : amdkmdag+0x6e4000


SYMBOL_NAME:  amdkmdag+c6a94

MODULE_NAME: amdkmdag

IMAGE_NAME:  amdkmdag.sys

Malwarebytes, ve başka programlarda da sorun çıkmış fakat asıl sebep ekran kartın. BIOS güncellersin ardından.

musallat.exe · 5 Temmuz 2023

armas dedi:

Evet okudum, ekran kartı sürücün hatalı çıktı. Başka bakacak arkadaşlar için de atayım buraya. Hata adını internette araştırırsan AMD'nin kendi forumunda da çözümünün sürücü ile alakalı olduğunu görebilirsin.

Kod:

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL.
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at.
 DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff807516fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains.
 additional information regarding the cumulative timeout.
Arg4: 0000000000000000.

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

*** WARNING: Unable to verify timestamp for amdkmdag.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 ***
*** ***
*************************************************************************

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 2265.

 Key : Analysis.Elapsed.mSec
 Value: 3601.

 Key : Analysis.IO.Other.Mb
 Value: 0

 Key : Analysis.IO.Read.Mb
 Value: 0

 Key : Analysis.IO.Write.Mb
 Value: 0

 Key : Analysis.Init.CPU.mSec
 Value: 389.

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

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

 Key : Bugcheck.Code.LegacyAPI
 Value: 0x133.

 Key : Dump.Attributes.AsUlong
 Value: 8

 Key : Dump.Attributes.KernelGeneratedTriageDump
 Value: 1

 Key : Failure.Bucket
 Value: 0x133_ISR_amdkmdag!unknown_function

 Key : Failure.Hash
 Value: {ce335412-b260-6bc1-3af9-ea5584f041c4}

 Key : Hypervisor.Enlightenments.Value
 Value: 68669340.

 Key : Hypervisor.Enlightenments.ValueHex
 Value: 417cf9c.

 Key : Hypervisor.Flags.AnyHypervisorPresent
 Value: 1

 Key : Hypervisor.Flags.ApicEnlightened
 Value: 1

 Key : Hypervisor.Flags.ApicVirtualizationAvailable
 Value: 0

 Key : Hypervisor.Flags.AsyncMemoryHint
 Value: 0

 Key : Hypervisor.Flags.CoreSchedulerRequested
 Value: 0

 Key : Hypervisor.Flags.CpuManager
 Value: 1

 Key : Hypervisor.Flags.DeprecateAutoEoi
 Value: 0

 Key : Hypervisor.Flags.DynamicCpuDisabled
 Value: 1

 Key : Hypervisor.Flags.Epf
 Value: 0

 Key : Hypervisor.Flags.ExtendedProcessorMasks
 Value: 1

 Key : Hypervisor.Flags.HardwareMbecAvailable
 Value: 1

 Key : Hypervisor.Flags.MaxBankNumber
 Value: 0

 Key : Hypervisor.Flags.MemoryZeroingControl
 Value: 0

 Key : Hypervisor.Flags.NoExtendedRangeFlush
 Value: 0

 Key : Hypervisor.Flags.NoNonArchCoreSharing
 Value: 1

 Key : Hypervisor.Flags.Phase0InitDone
 Value: 1

 Key : Hypervisor.Flags.PowerSchedulerQos
 Value: 0

 Key : Hypervisor.Flags.RootScheduler
 Value: 0

 Key : Hypervisor.Flags.SynicAvailable
 Value: 1

 Key : Hypervisor.Flags.UseQpcBias
 Value: 0

 Key : Hypervisor.Flags.Value
 Value: 4853999.

 Key : Hypervisor.Flags.ValueHex
 Value: 4a10ef.

 Key : Hypervisor.Flags.VpAssistPage
 Value: 1

 Key : Hypervisor.Flags.VsmAvailable
 Value: 1

 Key : Hypervisor.RootFlags.AccessStats
 Value: 1

 Key : Hypervisor.RootFlags.CrashdumpEnlightened
 Value: 1

 Key : Hypervisor.RootFlags.CreateVirtualProcessor
 Value: 1

 Key : Hypervisor.RootFlags.DisableHyperthreading
 Value: 0

 Key : Hypervisor.RootFlags.HostTimelineSync
 Value: 1

 Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
 Value: 0

 Key : Hypervisor.RootFlags.IsHyperV
 Value: 1

 Key : Hypervisor.RootFlags.LivedumpEnlightened
 Value: 1

 Key : Hypervisor.RootFlags.MapDeviceInterrupt
 Value: 1

 Key : Hypervisor.RootFlags.MceEnlightened
 Value: 1

 Key : Hypervisor.RootFlags.Nested
 Value: 0

 Key : Hypervisor.RootFlags.StartLogicalProcessor
 Value: 1

 Key : Hypervisor.RootFlags.Value
 Value: 1015.

 Key : Hypervisor.RootFlags.ValueHex
 Value: 3f7.

BUGCHECK_CODE: 133.

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00.

BUGCHECK_P3: fffff807516fb320.

BUGCHECK_P4: 0

FILE_IN_CAB: 070523-18640-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8.
 Kernel Generated Triage Dump.

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System.

STACK_TEXT:
ffffa000`9b29ae18 fffff807`50e43b14 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff807`516fb320 : nt!KeBugCheckEx
ffffa000`9b29ae20 fffff807`50c813c3 : 000b933a`5549d530 ffffa000`9b281180 00000000`00000000 ffffa000`9b281180 : nt!KeAccumulateTicks+0x1bfef4
ffffa000`9b29ae80 fffff807`50c80eaa : ffffe10f`96730480 ffffd58e`d617e8b0 00000000`001cfb00 00000000`00000000 : nt!KeClockInterruptNotify+0x453
ffffa000`9b29af30 fffff807`50d3ec65 : ffffe10f`96730480 fffff807`50d232b7 00000000`00000000 00000000`00000000 : nt!HalpTimerClockIpiRoutine+0x1a
ffffa000`9b29af60 fffff807`50dfdfca : ffffd58e`d617e8b0 ffffe10f`96730480 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffa000`9b29afb0 fffff807`50dfe797 : ffffd58e`d617ea20 ffffd58e`d617ea78 ffffe10f`96730480 ffffd58e`d617ea78 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffd58e`d617e830 fffff807`50cde607 : ffffffff`ffffffd2 fffff807`50c950de 00000000`00000010 00000000`00040282 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffd58e`d617e9c0 fffff807`50c950da : 00000000`00000000 ffffd0dc`4d18043d ffffd58e`d617f501 ffffe10f`bdf98020 : nt!KeYieldProcessorEx+0x17
ffffd58e`d617e9f0 fffff807`50c96de3 : 00000000`d2e55d0d 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxWaitForLockOwnerShip+0x2a
ffffd58e`d617ea20 fffff807`84626a94 : ffffe10f`bd3f5cb0 ffffe10f`bf233860 00000000`001cfa80 ffffe10f`bf233860 : nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x73
ffffd58e`d617ea50 ffffe10f`bd3f5cb0 : ffffe10f`bf233860 00000000`001cfa80 ffffe10f`bf233860 fffff807`84c44000 : amdkmdag+0xc6a94
ffffd58e`d617ea58 ffffe10f`bf233860 : 00000000`001cfa80 ffffe10f`bf233860 fffff807`84c44000 00000000`00000000 : 0xffffe10f`bd3f5cb0
ffffd58e`d617ea60 00000000`001cfa80 : ffffe10f`bf233860 fffff807`84c44000 00000000`00000000 ffffe10f`bd3f5cb9 : 0xffffe10f`bf233860
ffffd58e`d617ea68 ffffe10f`bf233860 : fffff807`84c44000 00000000`00000000 ffffe10f`bd3f5cb9 00000000`00000000 : 0x1cfa80.
ffffd58e`d617ea70 fffff807`84c44000 : 00000000`00000000 ffffe10f`bd3f5cb9 00000000`00000000 ffffe10f`bd3f5c01 : 0xffffe10f`bf233860
ffffd58e`d617ea78 00000000`00000000 : ffffe10f`bd3f5cb9 00000000`00000000 ffffe10f`bd3f5c01 00000000`00000000 : amdkmdag+0x6e4000

SYMBOL_NAME: amdkmdag+c6a94

MODULE_NAME: amdkmdag.

IMAGE_NAME: amdkmdag.sys

Malwarebytes, ve başka programlarda da sorun çıkmış fakat asıl sebep ekran kartın. BIOS güncellersin ardından.

Driverdan ziyade ekran kartıyla alakalı bir sorun olabilir mi? Kullandığım kartın backplate kısmındaki bir smd si kopuk çünkü.

Ben yine de sondan 2 önceki WHQL driveri bulup kurayım bu durumu çözmek adına.

armas · 5 Temmuz 2023

musallat.exe dedi:
Driverdan ziyade ekran kartıyla alakalı bir sorun olabilir mi? Kullandığım kartın backplate kısmındaki bir smd si kopuk çünkü.

Ben yine de sondan 2 önceki WHQL driveri bulup kurayım bu durumu çözmek adına.

Fiziki bir sorun olabilir mi bilmiyorum fakat kaynak ekran kartı. Durum düzelmezse evet smd kaynaklı olabilir.

@Enes3078 Müsait olursan bakabilir misin?

Minidump dosya analizi

Ayrıntılı düzenleme

musallat.exe

Decapat

070523-18640-01.rar

armas

Megapat

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

musallat.exe

Decapat

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

armas

Megapat

musallat.exe

Decapat

armas

Megapat

musallat.exe

Decapat

armas

Megapat

Benzer konular

Yeni konular

Yeni mesajlar

Gizliliğinize önem veriyoruz