Çözüldü GTX 1660 Ti sistemde mavi ekran

Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.
İşletim sistemi
Windows 10

Vctx

Centipat
Katılım
24 Mayıs 2023
Mesajlar
4
Daha fazla  
Cinsiyet
Erkek
Bu gece oyun indirirken birden mavi ekran yedim hatta 2 kere yedim ama diğer minidump dosyası yoktu.
Windows'u güncelledim.
GPU sürücülerini de güncelledim.

Sistemim.
Ryzen 5 3500.
GTX 1660 Ti.
B450M-H
Ballistix 8 GB.
 
Çözüm
Windows 10 sürümünüz eski kalmış. Minidump dosyaları yanıltıcı olabiliyor ama yüksek ihtimalle eski. O yüzden Windows Update aracılığıyla tüm güncellemeleri yapın.


BIOS eski kalmış. Anakartınızın aşağıdaki model olduğunu doğruladıktan sonra BIOS güncelleyin, 15/07/2020 sürümünü kullanıyorsunuz.


B45CS421.BSS'ye yani son sürüme güncelleyebilirsiniz.

Güncelledikten sonra tekrar BIOS'a girin, F3'e basın ve Load Defaults sorusuna Yes deyip BIOS'tan çıkın, tekrar BIOS'a girip ayarlarınızı yapın (RAM XMP, fan ayarları vs.).


NVIDIA ekran kartı sürücülerine bugün yeni bir güncelleme geldi, son sürüme güncelleyin.



Denetim masası > program ekle/kaldırdan eski chipset sürücülerinizi (AMD Chipset Software) kaldırın. Aşağıdakini indirin ve kurun.



Realtek ethernet sürücünüz eski kalmış.
Anakartınızda RTL8111H ethernet kontrolcü var.
İlk başka aşağıdaki linkten yeni sürücüleri indirin.
İndirdikten sonra eskilerini program ekle/kaldırdan silin.
Daha sonra PC'yi yeniden başlatın ve yeni indirdiğiniz sürücüyü kurun.

Bu linkten "Win10 Auto Installation Program (NDIS)" olanı indirebilirsiniz. Tarihi 23/05/2023.



Kaspersky'ı şimdilik kaldırın, mavi ekranlara sebebiyet verebiliyor.

Riot Vanguard'ı sağ alttan kapatın, denetim masasından uygulamayı silin, PC'yi yeniden başlatın ve oyuna girmeden önce oyun dosyalarının bütünlüğünü doğrulatın.

Tüm bu işlemler sonucunda tekrar mavi ekran alırsanız güncel dosyaları paylaşın.


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: fffff806234fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding the cumulative timeout
Arg4: 0000000000000000

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1656

    Key  : Analysis.Elapsed.mSec
    Value: 4318

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Failure.Bucket
    Value: 0x133_ISR_nt!KeAccumulateTicks

    Key  : Failure.Hash
    Value: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff806234fb320

BUGCHECK_P4: 0

FILE_IN_CAB:  061423-31031-01.dmp

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  ffff8009e3f5ce10 -- (.trap 0xffff8009e3f5ce10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff806234fdcc0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80622a6494d rsp=ffff8009e3f5cfa0 rbp=fffff8061e7e0180
 r8=0000000000000193  r9=ffff8009e3f5d330 r10=0000000000000000
r11=0000000000000014 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KeQueryValuesThread+0x24d:
fffff806`22a6494d 65488b0c2520000000 mov   rcx,qword ptr gs:[20h] gs:00000000`00000020=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Discord.exe

STACK_TEXT:
fffff806`26ae8e18 fffff806`22c43b14     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff806`234fb320 : nt!KeBugCheckEx
fffff806`26ae8e20 fffff806`22a813c3     : 0000330f`43e9d1d0 fffff806`1e7e0180 00000000`00000000 fffff806`1e7e0180 : nt!KeAccumulateTicks+0x1bfef4
fffff806`26ae8e80 fffff806`22a80eaa     : fffff806`234f3980 ffff8009`e3f5ce90 00000000`00000000 fffff806`1e7e0180 : nt!KeClockInterruptNotify+0x453
fffff806`26ae8f30 fffff806`22b3ec65     : fffff806`234f3980 00000000`00000000 00000000`00000000 ffff7d8b`f0b9ce1d : nt!HalpTimerClockIpiRoutine+0x1a
fffff806`26ae8f60 fffff806`22bfdfca     : ffff8009`e3f5ce90 fffff806`234f3980 00000000`000001e3 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff806`26ae8fb0 fffff806`22bfe797     : ffff9d84`43784580 ffff8009`e3f5cfc0 fffff806`234fdcc0 00000000`00000193 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff8009`e3f5ce10 fffff806`22a6494d     : ffff9d84`3d016580 00d00090`00000090 ffff9d84`00000000 fffff806`22a1ef05 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff8009`e3f5cfa0 fffff806`22e66621     : 00000000`00000000 fffff806`00000000 00000000`00000000 00000000`00000000 : nt!KeQueryValuesThread+0x24d
ffff8009`e3f5d020 fffff806`22e662b2     : ffff9d84`53e84920 ffff9d84`53e84ba0 ffff9d84`572e1480 00000000`00000000 : nt!PsQueryStatisticsProcess+0x111
ffff8009`e3f5d0a0 fffff806`22e12c21     : 00000000`00000000 ffff9d84`53e84340 00000000`ffffffff 00000000`00000000 : nt!ExpCopyProcessInfo+0x42
ffff8009`e3f5d120 fffff806`22e09037     : ffff8009`e3f5d7b8 ffff8009`00044400 00000000`00000000 00000000`00000000 : nt!ExpGetProcessInformation+0x9f1
ffff8009`e3f5d780 fffff806`22e081e7     : 00000000`00000001 ffffc5bc`00000000 00000000`572e1480 00000000`00010000 : nt!ExpQuerySystemInformation+0xd07
ffff8009`e3f5dac0 fffff806`22c0f7f8     : ffff9d84`572e0000 00007ffa`90565600 ffff8009`e3f5db80 ffff9d84`559f42c0 : nt!NtQuerySystemInformation+0x37
ffff8009`e3f5db00 00007ffa`917ed774     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`16e7e348 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`917ed774


SYMBOL_NAME:  nt!KeAccumulateTicks+1bfef4

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.3086

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1bfef4

FAILURE_BUCKET_ID:  0x133_ISR_nt!KeAccumulateTicks

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {65350307-c3b9-f4b5-8829-4d27e9ff9b06}

Followup:     MachineOwner
---------
Olan minidump'ı da paylaşmamışsınız.

 
Olan minidumpı da paylaşmamışsınız.


Pardon hocam.
 
Windows 10 sürümünüz eski kalmış. Minidump dosyaları yanıltıcı olabiliyor ama yüksek ihtimalle eski. O yüzden Windows Update aracılığıyla tüm güncellemeleri yapın.


BIOS eski kalmış. Anakartınızın aşağıdaki model olduğunu doğruladıktan sonra BIOS güncelleyin, 15/07/2020 sürümünü kullanıyorsunuz.


B45CS421.BSS'ye yani son sürüme güncelleyebilirsiniz.

Güncelledikten sonra tekrar BIOS'a girin, F3'e basın ve Load Defaults sorusuna Yes deyip BIOS'tan çıkın, tekrar BIOS'a girip ayarlarınızı yapın (RAM XMP, fan ayarları vs.).


NVIDIA ekran kartı sürücülerine bugün yeni bir güncelleme geldi, son sürüme güncelleyin.



Denetim masası > program ekle/kaldırdan eski chipset sürücülerinizi (AMD Chipset Software) kaldırın. Aşağıdakini indirin ve kurun.



Realtek ethernet sürücünüz eski kalmış.
Anakartınızda RTL8111H ethernet kontrolcü var.
İlk başka aşağıdaki linkten yeni sürücüleri indirin.
İndirdikten sonra eskilerini program ekle/kaldırdan silin.
Daha sonra PC'yi yeniden başlatın ve yeni indirdiğiniz sürücüyü kurun.

Bu linkten "Win10 Auto Installation Program (NDIS)" olanı indirebilirsiniz. Tarihi 23/05/2023.



Kaspersky'ı şimdilik kaldırın, mavi ekranlara sebebiyet verebiliyor.

Riot Vanguard'ı sağ alttan kapatın, denetim masasından uygulamayı silin, PC'yi yeniden başlatın ve oyuna girmeden önce oyun dosyalarının bütünlüğünü doğrulatın.

Tüm bu işlemler sonucunda tekrar mavi ekran alırsanız güncel dosyaları paylaşın.


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: fffff806234fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding the cumulative timeout
Arg4: 0000000000000000

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1656

    Key  : Analysis.Elapsed.mSec
    Value: 4318

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Failure.Bucket
    Value: 0x133_ISR_nt!KeAccumulateTicks

    Key  : Failure.Hash
    Value: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff806234fb320

BUGCHECK_P4: 0

FILE_IN_CAB:  061423-31031-01.dmp

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  ffff8009e3f5ce10 -- (.trap 0xffff8009e3f5ce10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff806234fdcc0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80622a6494d rsp=ffff8009e3f5cfa0 rbp=fffff8061e7e0180
 r8=0000000000000193  r9=ffff8009e3f5d330 r10=0000000000000000
r11=0000000000000014 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KeQueryValuesThread+0x24d:
fffff806`22a6494d 65488b0c2520000000 mov   rcx,qword ptr gs:[20h] gs:00000000`00000020=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Discord.exe

STACK_TEXT:
fffff806`26ae8e18 fffff806`22c43b14     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff806`234fb320 : nt!KeBugCheckEx
fffff806`26ae8e20 fffff806`22a813c3     : 0000330f`43e9d1d0 fffff806`1e7e0180 00000000`00000000 fffff806`1e7e0180 : nt!KeAccumulateTicks+0x1bfef4
fffff806`26ae8e80 fffff806`22a80eaa     : fffff806`234f3980 ffff8009`e3f5ce90 00000000`00000000 fffff806`1e7e0180 : nt!KeClockInterruptNotify+0x453
fffff806`26ae8f30 fffff806`22b3ec65     : fffff806`234f3980 00000000`00000000 00000000`00000000 ffff7d8b`f0b9ce1d : nt!HalpTimerClockIpiRoutine+0x1a
fffff806`26ae8f60 fffff806`22bfdfca     : ffff8009`e3f5ce90 fffff806`234f3980 00000000`000001e3 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff806`26ae8fb0 fffff806`22bfe797     : ffff9d84`43784580 ffff8009`e3f5cfc0 fffff806`234fdcc0 00000000`00000193 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff8009`e3f5ce10 fffff806`22a6494d     : ffff9d84`3d016580 00d00090`00000090 ffff9d84`00000000 fffff806`22a1ef05 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff8009`e3f5cfa0 fffff806`22e66621     : 00000000`00000000 fffff806`00000000 00000000`00000000 00000000`00000000 : nt!KeQueryValuesThread+0x24d
ffff8009`e3f5d020 fffff806`22e662b2     : ffff9d84`53e84920 ffff9d84`53e84ba0 ffff9d84`572e1480 00000000`00000000 : nt!PsQueryStatisticsProcess+0x111
ffff8009`e3f5d0a0 fffff806`22e12c21     : 00000000`00000000 ffff9d84`53e84340 00000000`ffffffff 00000000`00000000 : nt!ExpCopyProcessInfo+0x42
ffff8009`e3f5d120 fffff806`22e09037     : ffff8009`e3f5d7b8 ffff8009`00044400 00000000`00000000 00000000`00000000 : nt!ExpGetProcessInformation+0x9f1
ffff8009`e3f5d780 fffff806`22e081e7     : 00000000`00000001 ffffc5bc`00000000 00000000`572e1480 00000000`00010000 : nt!ExpQuerySystemInformation+0xd07
ffff8009`e3f5dac0 fffff806`22c0f7f8     : ffff9d84`572e0000 00007ffa`90565600 ffff8009`e3f5db80 ffff9d84`559f42c0 : nt!NtQuerySystemInformation+0x37
ffff8009`e3f5db00 00007ffa`917ed774     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`16e7e348 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`917ed774


SYMBOL_NAME:  nt!KeAccumulateTicks+1bfef4

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.3086

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1bfef4

FAILURE_BUCKET_ID:  0x133_ISR_nt!KeAccumulateTicks

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {65350307-c3b9-f4b5-8829-4d27e9ff9b06}

Followup:     MachineOwner
---------
 
Çözüm
Hocam sağ olun BIOS'u güncelledim şu ana kadar herhangi bir mavi ekran hatası yaşamadım.
Windows 10 sürümünüz eski kalmış. Minidump dosyaları yanıltıcı olabiliyor ama yüksek ihtimalle eski. O yüzden Windows Update aracılığıyla tüm güncellemeleri yapın.


BIOS eski kalmış. Anakartınızın aşağıdaki model olduğunu doğruladıktan sonra BIOS güncelleyin, 15/07/2020 sürümünü kullanıyorsunuz.


B45CS421.BSS'ye yani son sürüme güncelleyebilirsiniz.

Güncelledikten sonra tekrar BIOS'a girin, F3'e basın ve Load Defaults sorusuna Yes deyip BIOS'tan çıkın, tekrar BIOS'a girip ayarlarınızı yapın (RAM XMP, fan ayarları vs.).


NVIDIA ekran kartı sürücülerine bugün yeni bir güncelleme geldi, son sürüme güncelleyin.



Denetim masası > program ekle/kaldırdan eski chipset sürücülerinizi (AMD Chipset Software) kaldırın. Aşağıdakini indirin ve kurun.



Realtek ethernet sürücünüz eski kalmış.
Anakartınızda RTL8111H ethernet kontrolcü var.
İlk başka aşağıdaki linkten yeni sürücüleri indirin.
İndirdikten sonra eskilerini program ekle/kaldırdan silin.
Daha sonra PC'yi yeniden başlatın ve yeni indirdiğiniz sürücüyü kurun.

Bu linkten "Win10 Auto Installation Program (NDIS)" olanı indirebilirsiniz. Tarihi 23/05/2023.



Kaspersky'ı şimdilik kaldırın, mavi ekranlara sebebiyet verebiliyor.

Riot Vanguard'ı sağ alttan kapatın, denetim masasından uygulamayı silin, PC'yi yeniden başlatın ve oyuna girmeden önce oyun dosyalarının bütünlüğünü doğrulatın.

Tüm bu işlemler sonucunda tekrar mavi ekran alırsanız güncel dosyaları paylaşın.


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: fffff806234fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding the cumulative timeout
Arg4: 0000000000000000

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1656

    Key  : Analysis.Elapsed.mSec
    Value: 4318

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Failure.Bucket
    Value: 0x133_ISR_nt!KeAccumulateTicks

    Key  : Failure.Hash
    Value: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff806234fb320

BUGCHECK_P4: 0

FILE_IN_CAB:  061423-31031-01.dmp

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  ffff8009e3f5ce10 -- (.trap 0xffff8009e3f5ce10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff806234fdcc0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80622a6494d rsp=ffff8009e3f5cfa0 rbp=fffff8061e7e0180
 r8=0000000000000193  r9=ffff8009e3f5d330 r10=0000000000000000
r11=0000000000000014 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KeQueryValuesThread+0x24d:
fffff806`22a6494d 65488b0c2520000000 mov   rcx,qword ptr gs:[20h] gs:00000000`00000020=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Discord.exe

STACK_TEXT:
fffff806`26ae8e18 fffff806`22c43b14     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff806`234fb320 : nt!KeBugCheckEx
fffff806`26ae8e20 fffff806`22a813c3     : 0000330f`43e9d1d0 fffff806`1e7e0180 00000000`00000000 fffff806`1e7e0180 : nt!KeAccumulateTicks+0x1bfef4
fffff806`26ae8e80 fffff806`22a80eaa     : fffff806`234f3980 ffff8009`e3f5ce90 00000000`00000000 fffff806`1e7e0180 : nt!KeClockInterruptNotify+0x453
fffff806`26ae8f30 fffff806`22b3ec65     : fffff806`234f3980 00000000`00000000 00000000`00000000 ffff7d8b`f0b9ce1d : nt!HalpTimerClockIpiRoutine+0x1a
fffff806`26ae8f60 fffff806`22bfdfca     : ffff8009`e3f5ce90 fffff806`234f3980 00000000`000001e3 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff806`26ae8fb0 fffff806`22bfe797     : ffff9d84`43784580 ffff8009`e3f5cfc0 fffff806`234fdcc0 00000000`00000193 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff8009`e3f5ce10 fffff806`22a6494d     : ffff9d84`3d016580 00d00090`00000090 ffff9d84`00000000 fffff806`22a1ef05 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff8009`e3f5cfa0 fffff806`22e66621     : 00000000`00000000 fffff806`00000000 00000000`00000000 00000000`00000000 : nt!KeQueryValuesThread+0x24d
ffff8009`e3f5d020 fffff806`22e662b2     : ffff9d84`53e84920 ffff9d84`53e84ba0 ffff9d84`572e1480 00000000`00000000 : nt!PsQueryStatisticsProcess+0x111
ffff8009`e3f5d0a0 fffff806`22e12c21     : 00000000`00000000 ffff9d84`53e84340 00000000`ffffffff 00000000`00000000 : nt!ExpCopyProcessInfo+0x42
ffff8009`e3f5d120 fffff806`22e09037     : ffff8009`e3f5d7b8 ffff8009`00044400 00000000`00000000 00000000`00000000 : nt!ExpGetProcessInformation+0x9f1
ffff8009`e3f5d780 fffff806`22e081e7     : 00000000`00000001 ffffc5bc`00000000 00000000`572e1480 00000000`00010000 : nt!ExpQuerySystemInformation+0xd07
ffff8009`e3f5dac0 fffff806`22c0f7f8     : ffff9d84`572e0000 00007ffa`90565600 ffff8009`e3f5db80 ffff9d84`559f42c0 : nt!NtQuerySystemInformation+0x37
ffff8009`e3f5db00 00007ffa`917ed774     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`16e7e348 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`917ed774


SYMBOL_NAME:  nt!KeAccumulateTicks+1bfef4

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.3086

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1bfef4

FAILURE_BUCKET_ID:  0x133_ISR_nt!KeAccumulateTicks

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {65350307-c3b9-f4b5-8829-4d27e9ff9b06}

Followup:     MachineOwner
---------[/CODE
[/QUOTE]
 

Technopat Haberler

Geri
Yukarı