Yardım Mavi Ekran Hata! Minidump

ilkeryuksel

Klavye Delikanlısı
Klavye Delikanlısı
Katılım
14 Ara 2021
Mesajlar
208
Tepki
46
Selamlar bir kaç haftadır mavi ekran yiyorum.

RAM'lerden kaynaklımı emin değilim minidump incelemesini bilen varsa ekteki dump dosyasını inceleyebilir mi?

Rich (BB code):
For analysis of this file, run !analyze -v
nt!wil_details_FeatureReporting_ReportUsageToService+0x10e:
fffff804`4b653ede e8adf91700      call    nt!_security_check_cookie (fffff804`4b7d3890)
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
BugCheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: fffff8044f11ce70
Arg3: ffffab0c29cb6fc0
Arg4: fffff8044b653ede

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


KEY_VALUES_STRING: 1

    Key  : Analysis.Elapsed.mSec
    Value: 5057

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1000007f

    Key  : Dump.Attributes.AsUlong
    Value: 1808

    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: 0x7f_8_STACKPTR_ERROR_nt!wil_details_FeatureReporting_ReportUsageToService

    Key  : Failure.Hash
    Value: {5faa085e-3a68-f58c-9299-7d9567158962}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1497cf94

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

BUGCHECK_P1: 8

BUGCHECK_P2: fffff8044f11ce70

BUGCHECK_P3: ffffab0c29cb6fc0

BUGCHECK_P4: fffff8044b653ede

FILE_IN_CAB:  111323-8781-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

BAD_STACK_POINTER:  ffffab0c29cb6fc0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
ffffab0c`29cb6fc0 fffff804`4b620b1f     : 00200020`00200020 00200020`00200020 00000000`0000ffff fffff804`4b859887 : nt!wil_details_FeatureReporting_ReportUsageToService+0x10e
ffffab0c`29cb7090 fffff804`4b8592be     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeIsMultiCoreClassesEnabled+0x3f
ffffab0c`29cb70e0 fffff804`4b8595ab     : ffffe002`42b715c0 ffffab0c`29cb7180 ffffab0c`29cb7288 00000000`00000000 : nt!KiGenerateHeteroSets+0x26
ffffab0c`29cb7110 fffff804`4b6c5f62     : 00000000`00000000 00000000`00000000 00000000`0000ffff ffffe002`42b715c0 : nt!KiHeteroChooseTargetProcessor+0x9d
ffffab0c`29cb71c0 fffff804`4b6465bc     : ffffe002`42b715c0 fffff804`4b6d3a4a 00000000`00000020 00000000`00000000 : nt!KiDeferredReadySingleThread+0x742
ffffab0c`29cb7590 fffff804`4b6bfda1     : 00000000`00000000 00000000`00000000 00000000`00000000 fffff804`480a4180 : nt!KiDeferredReadyThread+0x3c
ffffab0c`29cb75c0 fffff804`4b6bf0fa     : 00000000`00000000 00000000`00000000 00000000`00000000 fffff804`480a4180 : nt!KiQueueReadyThread+0x391
ffffab0c`29cb7630 fffff804`4b6bf441     : 00007fff`fffeffff 00000000`00000000 ffffab0c`29cb7929 fffff804`480a4180 : nt!KiQuantumEnd+0xe6a
ffffab0c`29cb78a0 fffff804`4b81f55b     : 00000000`00000000 00000000`00000000 00007fff`ffff0000 fffff804`4fe6e2dc : nt!KiDispatchInterrupt+0x121
ffffab0c`29cb7990 fffff804`4b818b91     : ffffab0c`29cb7a40 ffffab0c`29cb8540 fffff804`4fdf2233 00000000`00000003 : nt!KiDpcInterruptBypass+0x1b
ffffab0c`29cb79c0 fffff804`4b627841     : 00000000`00000000 fffff804`4b62783f 00000000`00000000 fffff804`4b62783f : nt!KiInterruptDispatch+0xb1
ffffab0c`29cb7b50 fffff804`4b627088     : fffff804`4fde0000 fffff804`4fdf2233 ffffab0c`29cb97f0 fffff804`4fe8f684 : nt!RtlpUnwindPrologue+0x3f1
ffffab0c`29cb7c20 fffff804`4b626437     : 00000000`00000000 ffffab0c`29cb9a70 fffff804`4fdf2233 fffff804`4fe8f684 : nt!RtlpxVirtualUnwind+0x108
ffffab0c`29cb7ce0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlUnwindEx+0x1f7


SYMBOL_NAME:  nt!wil_details_FeatureReporting_ReportUsageToService+10e

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.2506

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  10e

FAILURE_BUCKET_ID:  0x7f_8_STACKPTR_ERROR_nt!wil_details_FeatureReporting_ReportUsageToService

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {5faa085e-3a68-f58c-9299-7d9567158962}

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

Rediron

Sözü Geçen
Sözü Geçen
Katılım
7 Ocak 2022
Mesajlar
2,374
Tepki
600
Konum
İstanbul /Anadolu
Selamlar bir kaç haftadır mavi ekran yiyorum.

RAM'lerden kaynaklımı emin değilim minidump incelemesini bilen varsa ekteki dump dosyasını inceleyebilir mi?

Rich (BB code):
For analysis of this file, run !analyze -v
nt!wil_details_FeatureReporting_ReportUsageToService+0x10e:
fffff804`4b653ede e8adf91700      call    nt!_security_check_cookie (fffff804`4b7d3890)
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
BugCheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: fffff8044f11ce70
Arg3: ffffab0c29cb6fc0
Arg4: fffff8044b653ede

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


KEY_VALUES_STRING: 1

    Key  : Analysis.Elapsed.mSec
    Value: 5057

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1000007f

    Key  : Dump.Attributes.AsUlong
    Value: 1808

    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: 0x7f_8_STACKPTR_ERROR_nt!wil_details_FeatureReporting_ReportUsageToService

    Key  : Failure.Hash
    Value: {5faa085e-3a68-f58c-9299-7d9567158962}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1497cf94

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

BUGCHECK_P1: 8

BUGCHECK_P2: fffff8044f11ce70

BUGCHECK_P3: ffffab0c29cb6fc0

BUGCHECK_P4: fffff8044b653ede

FILE_IN_CAB:  111323-8781-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

BAD_STACK_POINTER:  ffffab0c29cb6fc0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffffab0c`29cb6fc0 fffff804`4b620b1f     : 00200020`00200020 00200020`00200020 00000000`0000ffff fffff804`4b859887 : nt!wil_details_FeatureReporting_ReportUsageToService+0x10e
ffffab0c`29cb7090 fffff804`4b8592be     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeIsMultiCoreClassesEnabled+0x3f
ffffab0c`29cb70e0 fffff804`4b8595ab     : ffffe002`42b715c0 ffffab0c`29cb7180 ffffab0c`29cb7288 00000000`00000000 : nt!KiGenerateHeteroSets+0x26
ffffab0c`29cb7110 fffff804`4b6c5f62     : 00000000`00000000 00000000`00000000 00000000`0000ffff ffffe002`42b715c0 : nt!KiHeteroChooseTargetProcessor+0x9d
ffffab0c`29cb71c0 fffff804`4b6465bc     : ffffe002`42b715c0 fffff804`4b6d3a4a 00000000`00000020 00000000`00000000 : nt!KiDeferredReadySingleThread+0x742
ffffab0c`29cb7590 fffff804`4b6bfda1     : 00000000`00000000 00000000`00000000 00000000`00000000 fffff804`480a4180 : nt!KiDeferredReadyThread+0x3c
ffffab0c`29cb75c0 fffff804`4b6bf0fa     : 00000000`00000000 00000000`00000000 00000000`00000000 fffff804`480a4180 : nt!KiQueueReadyThread+0x391
ffffab0c`29cb7630 fffff804`4b6bf441     : 00007fff`fffeffff 00000000`00000000 ffffab0c`29cb7929 fffff804`480a4180 : nt!KiQuantumEnd+0xe6a
ffffab0c`29cb78a0 fffff804`4b81f55b     : 00000000`00000000 00000000`00000000 00007fff`ffff0000 fffff804`4fe6e2dc : nt!KiDispatchInterrupt+0x121
ffffab0c`29cb7990 fffff804`4b818b91     : ffffab0c`29cb7a40 ffffab0c`29cb8540 fffff804`4fdf2233 00000000`00000003 : nt!KiDpcInterruptBypass+0x1b
ffffab0c`29cb79c0 fffff804`4b627841     : 00000000`00000000 fffff804`4b62783f 00000000`00000000 fffff804`4b62783f : nt!KiInterruptDispatch+0xb1
ffffab0c`29cb7b50 fffff804`4b627088     : fffff804`4fde0000 fffff804`4fdf2233 ffffab0c`29cb97f0 fffff804`4fe8f684 : nt!RtlpUnwindPrologue+0x3f1
ffffab0c`29cb7c20 fffff804`4b626437     : 00000000`00000000 ffffab0c`29cb9a70 fffff804`4fdf2233 fffff804`4fe8f684 : nt!RtlpxVirtualUnwind+0x108
ffffab0c`29cb7ce0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlUnwindEx+0x1f7


SYMBOL_NAME:  nt!wil_details_FeatureReporting_ReportUsageToService+10e

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.2506

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  10e

FAILURE_BUCKET_ID:  0x7f_8_STACKPTR_ERROR_nt!wil_details_FeatureReporting_ReportUsageToService

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {5faa085e-3a68-f58c-9299-7d9567158962}

Followup:     MachineOwner
---------
Profesonel değilim, kend, işimi halledecek kadar anlayıp araştırabiliyorum. Chipset sürücüsünü kontrol edin bence. Daha çok bellek uyumluluğu gibi. Aşağıdaki makale var faydalanabileceğiniz.
 
KS

ilkeryuksel

Klavye Delikanlısı
Klavye Delikanlısı
Katılım
14 Ara 2021
Mesajlar
208
Tepki
46
Profesonel değilim, kend, işimi halledecek kadar anlayıp araştırabiliyorum. Chipset sürücüsünü kontrol edin bence. Daha çok bellek uyumluluğu gibi. Aşağıdaki makale var faydalanabileceğiniz.
Cevabiniz icin teşekkür ederim ama ramlerim set halinde uyumludur. Sorun farkli bir yerde olabilir mi?
 

Şu anda bu konuyu okuyan kullanıcılar

Son mesajlar

Geri
Üst