Various BSOD's occuring randomly

Anonymous
2021-02-11T15:22:43+00:00

Hi, I've bought brand new PC and started having random BSOD's while using PC or just when idling on desktop.

I've tried to use Windows Memory Diagnostic, also ran commands /scannow and such in CMD because I read it in so many other topics regarding BSOD.

I've had trouble uploading my dump files so i'll just post results here that I've got in WinDbgPreview.

I did memtest on both RAM drives and they were without errors after 4hr test each.

My specs: 

CPU: Ryzen 5 3600

GPU: Gigabyte WF2 RTX 2060 

MOBO: Aorus B450 Pro

RAM: XPG 2X8GB 3200MHz 

SSD: Kingston A2000 Nvme m.2

HDD: WD 1TB

PSU: FSP Hyper Pro+ 650W

I managed to upload dump files here: https://1drv.ms/u/s!Aq6wDqYiClWbhEgyN5aN5KjPpup_?e=S7n8AY

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

52 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2021-02-11T15:23:54+00:00

    Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\Users\GOOD LUCK\Desktop\minidump\020721-7390-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 18362 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff802`3ba00000 PsLoadedModuleList = 0xfffff802`3be461b0
Debug session time: Sun Feb  7 09:40:33.739 2021 (UTC + 1:00)
System Uptime: 0 days 1:12:34.399
Loading Kernel Symbols
...............................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
.......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`3bbc3b20 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffba8c`81253830=000000000000000a
4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000040066, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8023ba313be, address which referenced memory

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

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3780

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-KL6MEN5

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 16010

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: 19h1_release

    Key  : WER.OS.Timestamp
    Value: 2019-03-18T12:02:00Z

    Key  : WER.OS.Version
    Value: 10.0.18362.1

ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  a

BUGCHECK_P1: 40066

BUGCHECK_P2: ff

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8023ba313be

READ_ADDRESS: fffff8023bf713b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8023be283b8: Unable to get Flags value from nt!KdVersionBlock
fffff8023be283b8: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
 0000000000040066 

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  ffffba8c81253970 -- (.trap 0xffffba8c81253970)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000003 rbx=0000000000000000 rcx=0000000000040046
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8023ba313be rsp=ffffba8c81253b00 rbp=0000000000040046
 r8=0000000000000008  r9=0000000000000000 r10=0000fffff8024cb9
r11=ffffd37a8fc00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di ng nz na po nc
nt!PoIdle+0x39e:
fffff802`3ba313be 488b4d20        mov     rcx,qword ptr [rbp+20h] ss:0018:00000000`00040066=????????????????
Resetting default scope

STACK_TEXT:  
ffffba8c`81253828 fffff802`3bbd5929     : 00000000`0000000a 00000000`00040066 00000000`000000ff 00000000`00000000 : nt!KeBugCheckEx
ffffba8c`81253830 fffff802`3bbd1c69     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffba8c`81253970 fffff802`3ba313be     : 00000000`00000003 00000000`00000002 00000000`00000000 00000000`00000008 : nt!KiPageFault+0x469
ffffba8c`81253b00 fffff802`3bbc7614     : ffffffff`00000000 ffffe381`ba240180 ffff8506`87c26080 00000000`00001248 : nt!PoIdle+0x39e
ffffba8c`81253c60 00000000`00000000     : ffffba8c`81254000 ffffba8c`8124e000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x44

SYMBOL_NAME:  nt!PoIdle+39e

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.18362.1316

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  39e

FAILURE_BUCKET_ID:  AV_nt!PoIdle

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {0f00f4f4-fc66-441c-10bf-8ccc2952f11b}

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

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-02-11T15:23:02+00:00

    Most recent BSOD

    Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\GOOD LUCK\Desktop\minidump\021121-7421-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 18362 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff803`37c00000 PsLoadedModuleList = 0xfffff803`380461b0
Debug session time: Thu Feb 11 15:55:48.574 2021 (UTC + 1:00)
System Uptime: 0 days 17:43:12.234
Loading Kernel Symbols
...............................................................
................................................................
....................................................
Loading User Symbols
Loading unloaded module list
...........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`37dc3b20 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffb201`309d8b10=0000000000000133
9: 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: fffff80338171358, 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                                   ***
***                                                                   ***
*************************************************************************
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4703

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-KL6MEN5

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 10697

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: 19h1_release

    Key  : WER.OS.Timestamp
    Value: 2019-03-18T12:02:00Z

    Key  : WER.OS.Version
    Value: 10.0.18362.1

ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff80338171358

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  ffffd80bea299780 -- (.trap 0xffffd80bea299780)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000006c6b4494 rbx=0000000000000000 rcx=ffffd80bea299970
rdx=0000000000000005 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80337c2d3eb rsp=ffffd80bea299910 rbp=0000000000000080
 r8=0000000000000102  r9=0000000000000000 r10=fffff8033536f800
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!KeYieldProcessorEx+0x1b:
fffff803`37c2d3eb 4883c420        add     rsp,20h
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffb201`309d8b08 fffff803`37df4c1b     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff803`38171358 : nt!KeBugCheckEx
ffffb201`309d8b10 fffff803`37c34e8c     : 000005f4`5063dfbc ffffb201`30980180 00000000`003e4c0f 00000000`003e4c0f : nt!KeAccumulateTicks+0x1c18bb
ffffb201`309d8b70 fffff803`37b5d567     : ffffd80b`ea299b10 ffffd80b`ea299780 ffffd80b`ea299800 00000000`00000002 : nt!KeClockInterruptNotify+0x98c
ffffb201`309d8f30 fffff803`37cfdaa5     : 00000094`879e66e0 ffff800d`5f8c9d00 ffff800d`5f8c9db0 ffff5954`5dc322df : hal!HalpTimerClockInterrupt+0xf7
ffffb201`309d8f60 fffff803`37dc55aa     : ffffd80b`ea299800 ffff800d`5f8c9d00 00000000`000000ff ffff800d`5f8c9d00 : nt!KiCallInterruptServiceRoutine+0xa5
ffffb201`309d8fb0 fffff803`37dc5b17     : 00000000`00000200 fffff803`37b5d8f8 ffff800d`6a2ed180 fffff803`37dc5b24 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffd80b`ea299780 fffff803`37c2d3eb     : 00000000`00000010 00000000`00000286 ffffd80b`ea299938 00000000`00000018 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffd80b`ea299910 fffff803`37cc370a     : ffff800d`6bd97180 00000094`3f9dffbb 00000001`00000002 ffff800d`66a0b010 : nt!KeYieldProcessorEx+0x1b
ffffd80b`ea299940 fffff803`37cc22b9     : 00000000`0000000c 00000000`00989680 00000000`00250fe7 00000000`000000ff : nt!KiProcessExpiredTimerList+0x31a
ffffd80b`ea299a30 fffff803`37dc764e     : ffffffff`00000000 ffffb201`30980180 ffffb201`30991340 ffff800d`6b61f080 : nt!KiRetireDpcList+0x4e9
ffffd80b`ea299c60 00000000`00000000     : ffffd80b`ea29a000 ffffd80b`ea294000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x7e

SYMBOL_NAME:  nt!KeAccumulateTicks+1c18bb

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.18362.1316

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1c18bb

FAILURE_BUCKET_ID:  0x133_ISR_nt!KeAccumulateTicks

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

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

    Was this answer helpful?

    0 comments