Windows 10: BSOD with this error almost brand new machine

Discus and support BSOD with this error almost brand new machine in Windows 10 BSOD Crashes and Debugging to solve the problem; ********************************************************************************... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by YanZhang_390, Apr 12, 2021.

  1. BSOD with this error almost brand new machine


    [COLOR=rgba30, 30, 30, 1]******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************DPC_WATCHDOG_VIOLATION 133The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVELor above.Arguments:Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending component can usually be identified with a stack trace.Arg2: 0000000000000501, The DPC time count in ticks.Arg3: 0000000000000500, The DPC time allotment in ticks.Arg4: fffff8034b6fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains additional information regarding this single DPC timeoutDebugging 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: 3436 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 4794 Key : Analysis.Init.CPU.mSec Value: 656 Key : Analysis.Init.Elapsed.mSec Value: 35061 Key : Analysis.Memory.CommitPeak.Mb Value: 86 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.1BUGCHECK_CODE: 133BUGCHECK_P1: 0BUGCHECK_P2: 501BUGCHECK_P3: 500BUGCHECK_P4: fffff8034b6fb320DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDEDTRAP_FRAME: ffffed89c08bf540 -- [/COLOR][COLOR=rgba0, 0, 255, 1].trap 0xffffed89c08bf540[/COLOR][COLOR=rgba30, 30, 30, 1]NOTE: The trap frame does not contain all registers.[/COLOR][COLOR=rgba0, 0, 255, 1]Some register values may be zeroed or incorrect.[/COLOR][COLOR=rgba30, 30, 30, 1]rax=000000001ceb36f3 rbx=0000000000000000 rcx=ffffed89c08bf778rdx=ffffed89c97b7450 rsi=0000000000000000 rdi=0000000000000000rip=fffff8034ac44567 rsp=ffffed89c08bf6d0 rbp=ffffed89c97b7260 r8=ffffed89c97b7260 r9=ffffed89c97b7270 r10=fffff8034af0c620r11=0000000000000000 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei pl nz na po ncnt!KeYieldProcessorEx+0x17:fffff803`4ac44567 4883c420 add rsp,20hResetting default scopeBLACKBOXBSD: 1 [/COLOR][COLOR=rgba0, 0, 255, 1]!blackboxbsd[/COLOR][COLOR=rgba30, 30, 30, 1]BLACKBOXNTFS: 1 [/COLOR][COLOR=rgba0, 0, 255, 1]!blackboxntfs[/COLOR][COLOR=rgba30, 30, 30, 1]BLACKBOXPNP: 1 [/COLOR][COLOR=rgba0, 0, 255, 1]!blackboxpnp[/COLOR][COLOR=rgba30, 30, 30, 1]BLACKBOXWINLOGON: 1PROCESS_NAME: SystemSTACK_TEXT: ffff9880`3231fc88 fffff803`4ae3adce : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckExffff9880`3231fc90 fffff803`4ac7541d : 0000174f`7a36ab33 ffff9880`32306180 00000000`00000246 00000000`0041149a : nt!KeAccumulateTicks+0x1c8bceffff9880`3231fcf0 fffff803`4ac759c1 : 00000000`00410f00 00000000`0026ca7e ffff9880`32306180 00000000`00000001 : nt!KiUpdateRunTime+0x5dffff9880`3231fd40 fffff803`4ac6f833 : ffff9880`32306180 00000000`00000000 fffff803`4b631a80 00000000`00000000 : nt!KiUpdateTime+0x4a1ffff9880`3231fe80 fffff803`4ac781f2 : ffffed89`c08bf540 ffffed89`c08bf5c0 ffffed89`c08bf500 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3ffff9880`3231ff30 fffff803`4ad27f55 : 0000009b`2ad20145 ffffa985`708ea500 ffffa985`708ea5b0 ffff1d1a`e1ff0733 : nt!HalpTimerClockInterrupt+0xe2ffff9880`3231ff60 fffff803`4adf785a : ffffed89`c08bf5c0 ffffa985`708ea500 00000000`80000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5ffff9880`3231ffb0 fffff803`4adf7dc7 : 00000000`00000000 ffff9880`3230e1c8 ffffed89`c97b7450 fffff803`4adf7dd4 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfaffffed89`c08bf540 fffff803`4ac44567 : ffffffff`ffffffd1 fffff803`4af0c6e9 00000000`00000010 00000000`00000286 : nt!KiInterruptDispatchNoLockNoEtw+0x37ffffed89`c08bf6d0 fffff803`4af0c6fc : 00000000`00000001 ffffed89`c08bf710 00000000`00010001 00000000`00000000 : nt!KeYieldProcessorEx+0x17ffffed89`c08bf700 fffff803`4ac0781e : ffff9880`32309240 ffffed89`c08bf860 00000000`00000000 ffffa985`1ceb36f3 : nt!KiConfigureHeteroProcessorsTarget+0xdcffffed89`c08bf760 fffff803`4ac06b04 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30effffed89`c08bf8d0 fffff803`4adf991e : ffffffff`00000000 ffff9880`32306180 ffff9880`32311440 ffffa985`a4d66080 : nt!KiRetireDpcList+0x1f4ffffed89`c08bfb60 00000000`00000000 : ffffed89`c08c0000 ffffed89`c08b9000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9eSYMBOL_NAME: nt!KeAccumulateTicks+1c8bceMODULE_NAME: [/COLOR][COLOR=rgba0, 0, 255, 1]nt[/COLOR][COLOR=rgba30, 30, 30, 1]IMAGE_NAME: ntkrnlmp.exeSTACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 1c8bceFAILURE_BUCKET_ID: 0x133_DPC_nt!KeAccumulateTicksOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {88dc98ce-f842-4daa-98d0-858621db6b0f}Followup: MachineOwner[/COLOR]



    [COLOR=rgba30, 30, 30, 1]I have the Minidump file and system info here at this link as well if someone is able to help[/COLOR]

    https://1drv.ms/u/s!ArVFoijfLVY87S3BtaWh5QBV3vt-?e=aCmmcj

    :)
     
    YanZhang_390, Apr 12, 2021
    #1

  2. Brand new PC BSoD

    Hi,

    Corrupted drivers and system files are one of the possible reasons why this issue is happening. We'd like to get additional information to help resolve the issue. Kindly answer the following questions below:

    • What is the stop error code showing on the screen whenever you experience BSoD? (e.g.: 0x0000000A, 0x0000003B, and 0x000000EF)
    • Did you installed any third-party applications on your new computer before the issue started?
    • Is there a specific action you're doing on the computer that triggers BSoD?
    In the meantime, we suggest performing the possible solutions in this
    article
    to help resolve blue screen errors.

    We'll keep an eye out for your response.
     
    Martin Bar, Apr 12, 2021
    #2
  3. Kursah Win User
    BSOD - Registry Error

    Your BSOD code is 0X000000051

    Here's the Google search I did for it: https://www.google.com/search?q=0x0...j5.399j0j7&sourceid=chrome&es_sm=122&ie=UTF-8

    There is a hotfix available that might help, https://support.microsoft.com/en-us/kb/810558

    This thread makes a few good suggestions too: http://www.sevenforums.com/bsod-hel...dows-7-pro-sp1-registry-error-0x00000051.html

    +1 to listing your full system specs, OS version, etc. I did only look at your BSOD log file.

    Run a Diskchk /R (I know you already ran one, so you can skip this)

    Run SFC /SCANNOW

    Report back.
     
    Kursah, Apr 12, 2021
    #3
  4. BSOD with this error almost brand new machine

    HELP ! BSOD with brand new computer.

    Hi,

    I just bought a brand new computer running with Windows 10.

    When I first turned it on, I had a BSOD within 1min. I had to do a "hard" restart because it crashed again when it restarted.

    While I was doing the initial configuration, it may have crashed 3 times more. Then, I started to install the usual software (Office, Adobe, Anti-virus...) and it crashed again at least twice.

    I did all the steps that are listed here.

    Below is the OneDrive link to the zipped folder:

    Files_dmp.zip

    There should be the last three .dmp file, the system info and the computer specification.

    If you need any other information, please let me know.

    Thank you for your help !
     
    Alix Lachaud, Apr 12, 2021
    #4
Thema:

BSOD with this error almost brand new machine

Loading...
  1. BSOD with this error almost brand new machine - Similar Threads - BSOD error almost

  2. BSoD New Machine

    in Windows 10 Software and Apps
    BSoD New Machine: I have an HP ENVY Laptop 17 with 64GB of RAM and an Intel 12th Gen i7-1206p with a 2TB SSD, and since I received the machine, I have been having issues with it freezing and then restarting. I have had a few BSoD, but usually, this happens by the screen just freezing, and then...
  3. BSOD errors W11 brand new PC

    in Windows 10 Gaming
    BSOD errors W11 brand new PC: I got my new pc up and running yesterday 8 March 23 and since then i have gotten over a dozen different blue screen error codes, for basically everything. this is a brand new, fresh install of Windows 11 on a freshly assembled windows 11 compatible pc.Errors...
  4. BSOD errors W11 brand new PC

    in Windows 10 Software and Apps
    BSOD errors W11 brand new PC: I got my new pc up and running yesterday 8 March 23 and since then i have gotten over a dozen different blue screen error codes, for basically everything. this is a brand new, fresh install of Windows 11 on a freshly assembled windows 11 compatible pc.Errors...
  5. BSOD Brand new pc.

    in Windows 10 BSOD Crashes and Debugging
    BSOD Brand new pc.: Hi everyone. So i built a new pc with the following parts: Ryzen 3 2200g Patriot Viper 4 3000mhz 8gb Gigabyte b450m s2h Corsair cx450m An i have been having problems from the very start. I had blue screen errors a lot at the begging but they suddenly stopped. Well they...
  6. BSOD in a Brand New Desktop

    in Windows 10 BSOD Crashes and Debugging
    BSOD in a Brand New Desktop: HI I have been having BSOD on my Dell All in One since the the beginning. I am still in the warranty but before I contact Dell, I want a Microsoft technician to have a look on the Minidump file analysis. I have updated all drivers and reinstalled Windows couple of times...
  7. BSOD 'Machine Check Exception' Error (Almost Everyday)

    in Windows 10 BSOD Crashes and Debugging
    BSOD 'Machine Check Exception' Error (Almost Everyday): Can you help me please almost everyday i get machine check exception, can be 2 times in day and if sound open disturbing repeats. 59891
  8. BSOD on brand-new laptop

    in Windows 10 BSOD Crashes and Debugging
    BSOD on brand-new laptop: Hi all, I have recently bought new laptop (Dell Vostro 5468). I did clean install of Windows 10 and installed additional harddrive. Today I have experienced a BSOD. I had many programs running when a blue screen appeared. I had a look at logs and what is bugging me is this...
  9. Kernel security check error on brand new machine

    in Windows 10 BSOD Crashes and Debugging
    Kernel security check error on brand new machine: Greetings and Merry Christmas. I have a 3 day out of the box, Asus Zenbook pro that is giving me fits. I am getting the BSOD fairly regularly. I have scoured the internet trying to find a solution. From the suggestions I have found so far, I have updated both display...
  10. 100% CPU - Brand New Machine

    in Windows 10 Performance & Maintenance
    100% CPU - Brand New Machine: Hi, I am trying to upgrade a number of machines to Windows 10 Pro. Latest one is a new laptop - fresh install and after it has been running a while it comes up at 100 CPU and it is something to do with Service host local system. This is not the only machine to be affected...