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: Oldest
Most helpful Newest Oldest
  1. SD - IA 179.8K Reputation points Independent Advisor
    2021-02-11T15:56:29+00:00

    Hi,

    I am Sumit, an Independent Advisor.

    We need log files(called dump files) that tell us what lead to crash.

    Please share them with us for a better analysis of the problem. Instructions can be found here:

    https://answers.microsoft.com/en-us/windows/for...

    To share files here, please see:

    How to share diagnostic files/logs on Microsoft community

    https://answers.microsoft.com/en-us/feedback/fo...

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-02-11T18:31:47+00:00

    Was this answer helpful?

    0 comments
  3. SD - IA 179.8K Reputation points Independent Advisor
    2021-02-12T04:50:33+00:00

    Hi,

    I don't see a link. Can you retry please?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2021-02-12T14:23:46+00:00

    I've had a look at all 25 dumps from your link.  Here is the overview of each bugcheck code and the probably caused by reason provided by WinDBG (at best this is a guide but is often wrong).  The sheer variety and the mention of memory corruption makes me think this is a hardware problem and most likely to be memory.

    BugCheck A, {250, 2, 0, fffff80543dcabf8}

    Probably caused by: ntkrnlmp.exe ( nt!SwapContext+b8 )

    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

    BugCheck 133, {1, 1e00, fffff80338171358, 0}

    Probably caused by: ntkrnlmp.exe ( nt!KeAccumulateTicks+1c18bb )

    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

    BugCheck A, {40066, ff, 0, fffff8023ba313be}

    Probably caused by: ntkrnlmp.exe ( nt!PoIdle+39e )

    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

    BugCheck A, {0, ff, 58, fffff80319abd0cf}

    Probably caused by: ntkrnlmp.exe ( nt!KiGetNextTimerExpirationDueTime+11f )

    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

    BugCheck A, {0, ff, 0, fffff80647189eb8}

    Probably caused by: ntkrnlmp.exe ( nt!PpmIdleSelectStates+288 )

    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

    BugCheck A, {0, ff, 46, fffff8051c78a17f}

    Probably caused by: ntkrnlmp.exe ( nt!PpmEstimateIdleDuration+153 )

    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

    BugCheck 1A, {61941, 222deefe300, f, ffff9b03452bcb00}

    Probably caused by: Unknown_Image ( ANALYSIS_INCONCLUSIVE )

    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

    BugCheck D1, {fffff802407d0088, ff, 0, fffff802407d0088}

    Probably caused by: amdppm.sys ( amdppm!AcpiCStateIdleExecute+23 )

    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

    BugCheck 133, {0, 501, 500, fffff80444571358}

    Probably caused by: ntkrnlmp.exe ( nt!KeAccumulateTicks+1c1837 )

    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

    BugCheck 139, {3, ffff918642c6f520, ffff918642c6f478, 0}

    Probably caused by: ntkrnlmp.exe ( nt!KiInsertTimerTable+1b6fac )

    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

    BugCheck 1CE, {ffffb70412ca5080, ffffc700a2851340, 0, 0}

    Probably caused by: ntkrnlmp.exe ( nt!SwapContext+528 )

    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

    BugCheck 1, {7ff82eabc7d4, 0, ffff, ffffc90dd092cb80}

    Probably caused by: ntkrnlmp.exe ( nt!KiSystemServiceExitPico+1fe )

    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

    BugCheck 50, {fffff8020000002b, 10, fffff8020000002b, 2}

    Probably caused by: win32kbase.sys ( win32kbase!HmgInsertObjectInternal+6f )

    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

    BugCheck 1, {7ffdf72dfa44, 0, ffff, fffff009a5941b80}

    Probably caused by: ntkrnlmp.exe ( nt!KiSystemServiceExitPico+1fe )

    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

    BugCheck 1, {7ffecae3d4c4, 0, ffff0000, ffffce84bc018b80}

    Probably caused by: ntkrnlmp.exe ( nt!KiSystemServiceExitPico+1fe )

    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

    BugCheck 192, {ffff9d09211a9080, ffffbd0dead56330, 0, 0}

    Probably caused by: Npfs.SYS ( Npfs!NpFsdRead+bd )

    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

    BugCheck A, {3028c8, ff, 4, fffff8033718bd82}

    Probably caused by: ntkrnlmp.exe ( nt!PpmIdleSelectStates+152 )

    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

    BugCheck BE, {fffff80614e06000, 900000001cc6121, ffffab01f44d8dd0, a}

    Probably caused by: memory_corruption ( nt!MiRaisedIrqlFault+127d23 )

    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

    BugCheck 3B, {c0000005, fffff8078c06161c, fffff282e3659db0, 0}

    Probably caused by: WdNisDrv.sys ( WdNisDrv+161c )

    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

    BugCheck D1, {10, ff, 3b, fffff80641e71306}

    Probably caused by: amdppm.sys ( amdppm!SnapEnergyCounters+26 )

    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

    BugCheck 4E, {7, 1b2f27, 200000000422fc9, 0}

    Probably caused by: memory_corruption ( nt!MiPfnReferenceCountIsZero+1c8ded )

    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

    BugCheck 50, {ffffc07de1c00000, 0, ffffac9cc4843446, 2}

    Probably caused by: win32kbase.sys ( win32kbase!GreReleaseSemaphoreInternal+15 )

    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

    BugCheck A, {253087cfe, ff, c0, fffff8053bc316b0}

    Probably caused by: ntkrnlmp.exe ( nt!PpmIdleExecuteTransition+180 )

    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

    BugCheck 1E, {ffffffffc0000005, 0, 8, 0}

    Probably caused by: ntkrnlmp.exe ( nt!KiDispatchException+1d33f9 )

    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

    BugCheck 133, {1, 1e00, fffff80630173358, 0}

    Probably caused by: win32kbase.sys ( win32kbase!UserSessionSwitchLeaveCrit+62 )

    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

    Run a memory test such as memtest86 for 4 passes but if this does not show any errors I think you are the victim of the AMD CPU/motherboard problem that many people have been facing in recent weeks.  I think you will need to keep updating and hope that W10 updates might eventually fix it.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2021-02-12T17:28:00+00:00

    I'll repost the link just in case you can't see it for somewhat reason.

    https://1drv.ms/u/s!Aq6wDqYiClWbhEgyN5aN5KjPpup_?e=S7n8AY

    Was this answer helpful?

    0 comments