BSOD with possibly faulty hardware


  1. Posts : 1
    Win 10
       #1

    BSOD with possibly faulty hardware


    It crash infrequently and 3rd party bluescreen reader suggest thermal issue but I know that it is not the case.

    Here is the V2 log>

    DESKTOP-OMMEESP-(2023-04-14_15-20-22).zip - Google Drive


    Here is the mini dump>

    041123-56250-01.dmp - Google Drive


    Here is the tuneup-plus log>

    Tuneup_log 2023-04-14 at 14-53-22.zip - Google Drive


    Windows version is 22H2
      My Computer


  2. Posts : 890
    10 Pro/11 Pro Dual Boot
       #2

    krisskross said:
    It crash infrequently and 3rd party bluescreen reader suggest thermal issue but I know that it is not the case.

    Here is the V2 log>

    DESKTOP-OMMEESP-(2023-04-14_15-20-22).zip - Google Drive


    Here is the mini dump>

    041123-56250-01.dmp - Google Drive


    Here is the tuneup-plus log>

    Tuneup_log 2023-04-14 at 14-53-22.zip - Google Drive


    Windows version is 22H2
    All dumps are 100% the same.

    Intel(R) Turbo Boost Max Technology 3.0 Driver

    your drivers for it are from 10/27/2016 and need updating

    0: kd> !analyze -v
    *******************************************************************************
    * *
    * 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. The offending component can usually be
    identified with a stack trace.
    Arg2: 0000000000001e00, The watchdog period.
    Arg3: fffff802240fb320, 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 IntelNit.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 ***
    *** ***
    *************************************************************************
    *** WARNING: Unable to verify timestamp for win32k.sys

    KEY_VALUES_STRING: 1

    Key : Analysis.CPU.mSec
    Value: 1968

    Key : Analysis.DebugAnalysisManager
    Value: Create

    Key : Analysis.Elapsed.mSec
    Value: 3460

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

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

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

    Key : WER.OS.Branch
    Value: vb_release

    Key : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key : WER.OS.Version
    Value: 10.0.19041.1


    BUGCHECK_CODE: 133

    BUGCHECK_P1: 1

    BUGCHECK_P2: 1e00

    BUGCHECK_P3: fffff802240fb320

    BUGCHECK_P4: 0

    DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

    TRAP_FRAME: fffff90efedd7500 -- (.trap 0xfffff90efedd7500)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=000000002cf1c404 rbx=0000000000000000 rcx=fffff90efedd76d0
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8022361c04c rsp=fffff90efedd7698 rbp=0000000000000000
    r8=0000000000000008 r9=0000000000000000 r10=fffff80223400000
    r11=ffffa3fd28800000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei ng nz na po nc
    nt!KeYieldProcessorEx+0x1c:
    fffff802`2361c04c c3 ret
    Resetting default scope

    BLACKBOXBSD: 1 (!blackboxbsd)


    BLACKBOXNTFS: 1 (!blackboxntfs)


    BLACKBOXPNP: 1 (!blackboxpnp)


    BLACKBOXWINLOGON: 1

    CUSTOMER_CRASH_COUNT: 1

    PROCESS_NAME: System

    STACK_TEXT:
    fffff802`29c80c88 fffff802`2385be7a : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff802`240fb320 : nt!KeBugCheckEx
    fffff802`29c80c90 fffff802`236d844d : 0001ba26`aa053975 fffff802`2186b180 00000000`00000246 00000000`08423c94 : nt!KeAccumulateTicks+0x186c4a
    fffff802`29c80cf0 fffff802`236d89f1 : 00000000`00000000 00000000`04ec2ee8 fffff802`2186b180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
    fffff802`29c80d40 fffff802`236d2863 : fffff802`2186b180 00000000`00000000 fffff802`240318a0 00000000`00000000 : nt!KiUpdateTime+0x4a1
    fffff802`29c80e80 fffff802`236db222 : fffff90e`fedd7500 fffff90e`fedd7580 fffff90e`fedd7500 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
    fffff802`29c80f30 fffff802`23608aa5 : 000013b0`c5514715 fffff802`240f3a20 fffff802`240f3ad0 00000000`00000000 : nt!HalpTimerClockInterrupt+0xe2
    fffff802`29c80f60 fffff802`237fb23a : fffff90e`fedd7580 fffff802`240f3a20 00000000`000001bf 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
    fffff802`29c80fb0 fffff802`237fba07 : fffff90e`00000000 00001f80`007f0294 00000000`2cf124a4 fffff90e`fedd76d0 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
    fffff90e`fedd7500 fffff802`2361c04c : fffff802`23823368 00000000`00000200 00000000`000001bf 00000000`00000090 : nt!KiInterruptDispatchNoLockNoEtw+0x37
    fffff90e`fedd7698 fffff802`23823368 : 00000000`00000200 00000000`000001bf 00000000`00000090 00000000`00000000 : nt!KeYieldProcessorEx+0x1c
    fffff90e`fedd76a0 fffff802`3d7b660a : 00000000`02000103 00000000`00000000 ffffa406`dda4f580 00000000`00000000 : nt!KeQueryTotalCycleTimeThread+0x20a248
    fffff90e`fedd77e0 00000000`02000103 : 00000000`00000000 ffffa406`dda4f580 00000000`00000000 00000000`00000000 : IntelNit+0x660a
    fffff90e`fedd77e8 00000000`00000000 : ffffa406`dda4f580 00000000`00000000 00000000`00000000 00000000`00000000 : 0x2000103


    SYMBOL_NAME: IntelNit+660a

    MODULE_NAME: IntelNit

    IMAGE_NAME: IntelNit.sys

    STACK_COMMAND: .thread ; .cxr ; kb

    BUCKET_ID_FUNC_OFFSET: 660a

    FAILURE_BUCKET_ID: 0x133_ISR_IntelNit!unknown_function

    OS_VERSION: 10.0.19041.1

    BUILDLAB_STR: vb_release

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {7067e6dd-c390-c75f-f6b3-0bb8664966be}

    Followup: MachineOwner
    ---------
      My Computers


  3. Posts : 41,460
    windows 10 professional version 1607 build 14393.969 64 bit
       #3

    How come there are entries in the hosts file?
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 11:04.
Find Us




Windows 10 Forums