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 No comments

52 answers

Sort by: Oldest
  1. Anonymous
    2021-02-21T12:02:11+00:00

    Thanks for the extra files. I do concur that Firefox is playing a role in all the crashes. Just look how many times it was the process running at the time of the crash. You also have Kaspersky running as your AV program. If you continue to get problems I would try removing this for a while to see if it helps.

    Built by: 19041.1.amd64fre.vb_release.191206-1406

    Debug session time: Sat Feb 20 20:45:01.692 2021 (UTC + 0:00)

    System Uptime: 0 days 0:03:06.316

    BugCheck 139, {3, ffffab0eb5268730, ffffab0eb5268688, 0}

    Probably caused by: ntkrnlmp.exe ( nt!KiFastFailDispatch+d0 )

    BUGCHECK_STR: 0x139

    PROCESS_NAME: firefox.exe

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

    Built by: 19041.1.amd64fre.vb_release.191206-1406

    Debug session time: Sat Feb 20 20:22:04.370 2021 (UTC + 0:00)

    System Uptime: 0 days 0:13:25.994

    BugCheck 13A, {8, ffff800cad010100, ffff800cb75a2c70, 0}

    Probably caused by: dxgmms2.sys ( dxgmms2!VIDMM_RECYCLE_HEAP_MGR::DestroyMultirange+2923e )

    BUGCHECK_STR: 0x13a_8

    PROCESS_NAME: firefox.exe

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

    Built by: 19041.1.amd64fre.vb_release.191206-1406

    Debug session time: Sat Feb 20 14:45:57.404 2021 (UTC + 0:00)

    System Uptime: 0 days 0:03:16.029

    BugCheck 162, {ffffd18b412ac080, ffffe48708ec5b50, ffffffff, 0}

    Probably caused by: ntkrnlmp.exe ( nt!KeAbPostRelease+1af8c7 )

    BUGCHECK_STR: 0x162

    PROCESS_NAME: svchost.exe

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

    Built by: 19041.1.amd64fre.vb_release.191206-1406

    Debug session time: Sat Feb 20 14:42:16.733 2021 (UTC + 0:00)

    System Uptime: 0 days 0:04:32.358

    BugCheck 139, {1e, ffffae066aab4f50, ffffae066aab4ea8, 0}

    Probably caused by: ntkrnlmp.exe ( nt!KiFastFailDispatch+d0 )

    BUGCHECK_STR: 0x139

    PROCESS_NAME: steam.exe

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

    Built by: 19041.1.amd64fre.vb_release.191206-1406

    Debug session time: Sat Feb 20 12:51:37.366 2021 (UTC + 0:00)

    System Uptime: 0 days 0:03:58.990

    BugCheck 3B, {c0000005, fffff80422c60ae8, ffffaf8d32875de0, 0}

    Probably caused by: ntkrnlmp.exe ( nt!ExAcquirePushLockExclusiveEx+108 )

    BUGCHECK_STR: 0x3B_c0000005

    PROCESS_NAME: csrss.exe

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

    Built by: 19041.1.amd64fre.vb_release.191206-1406

    Debug session time: Sat Feb 20 12:47:14.060 2021 (UTC + 0:00)

    System Uptime: 0 days 0:07:21.685

    BugCheck 3B, {c0000005, fffff8052baee8d7, fffffd06556e3b60, 0}

    Probably caused by: dxgkrnl.sys ( dxgkrnl!DXGALLOCATIONREFERENCE::~DXGALLOCATIONREFERENCE+114 )

    BUGCHECK_STR: 0x3B_c0000005

    PROCESS_NAME: firefox.exe

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

    Built by: 19041.1.amd64fre.vb_release.191206-1406

    Debug session time: Sat Feb 20 12:25:26.282 2021 (UTC + 0:00)

    System Uptime: 0 days 0:09:33.907

    BugCheck 192, {ffffd988fc7b5080, ffff860aae0da9c8, 0, 0}

    *** WARNING: Unable to verify timestamp for klif.sys

    Probably caused by: klif.sys ( klif+b4d9d )

    BUGCHECK_STR: 0x192

    PROCESS_NAME: firefox.exe

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

    Built by: 19041.1.amd64fre.vb_release.191206-1406

    Debug session time: Sat Feb 20 11:25:19.879 2021 (UTC + 0:00)

    System Uptime: 0 days 0:03:32.503

    BugCheck 1000007E, {ffffffffc0000005, fffff8025e5bb48b, ffffc885d2d95198, ffffc885d2d949d0}

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

    Probably caused by: Ntfs.sys ( Ntfs!NtfsAcquireFileForModWrite+fb )

    BUGCHECK_STR: AV

    PROCESS_NAME: System

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

    Built by: 19041.1.amd64fre.vb_release.191206-1406

    Debug session time: Sat Feb 20 11:21:23.320 2021 (UTC + 0:00)

    System Uptime: 0 days 0:04:49.945

    BugCheck A, {7ffb24d48efb, 2, 1, fffff80213c0cece}

    Probably caused by: memory_corruption ( nt!MiUserFault+28e )

    BUGCHECK_STR: AV

    PROCESS_NAME: dwm.exe

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

    Built by: 19041.1.amd64fre.vb_release.191206-1406

    Debug session time: Sat Feb 20 11:16:08.170 2021 (UTC + 0:00)

    System Uptime: 0 days 0:03:11.794

    BugCheck D1, {ffffa10f000000c5, 2, 0, fffff807239572e8}

    Probably caused by: afd.sys ( afd!AfdPoll64+544 )

    BUGCHECK_STR: AV

    PROCESS_NAME: firefox.exe

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

    Built by: 19041.1.amd64fre.vb_release.191206-1406

    Debug session time: Sat Feb 20 11:01:18.476 2021 (UTC + 0:00)

    System Uptime: 0 days 2:11:57.096

    BugCheck A, {0, ff, 0, fffff80358b8a967}

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

    Probably caused by: ntkrnlmp.exe ( nt!HvlGetPpmStatsForProcessor+37 )

    BUGCHECK_STR: AV

    PROCESS_NAME: System

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

    Built by: 18362.1.amd64fre.19h1_release.190318-1202

    Debug session time: Sat Feb 20 07:21:12.201 2021 (UTC + 0:00)

    System Uptime: 0 days 0:50:42.168

    BugCheck A, {8, 2, 0, fffff80678a798cd}

    Probably caused by: ntkrnlmp.exe ( nt!KiTryUnwaitThread+17d )

    BUGCHECK_STR: AV

    PROCESS_NAME: EpicWebHelper.exe

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

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2021-02-22T06:43:43+00:00

    I have uninstalled firefox, epic games and kaspersky AV from system but crashes keep coming but only while using any browser. I was using Chrome it was happening now i'm using Edge and it still happens. While i play highly demanding video games nothing happens, only while using browser which is beyond me.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2021-02-22T07:14:01+00:00

    Please keep providing the new crash dumps so we can look for common causes. The fact that it only happens while browsing is a clue and suggests we need to focus on software that runs at these times. Internet filters or scanners, network software etc.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2021-02-22T19:59:19+00:00

    Sure, here are minidump files from today: https://1drv.ms/u/s!Aq6wDqYiClWbhHuvfMgKszr8FsAH?e=ecBCD4

    The thing is i am running driver verifier but the only cause of crash is always the same - ntoskrnl.exe+some random letters and numbers

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2021-02-22T20:16:40+00:00

    If you run Driver Verifier with all those selections it is not surprising that you get crashes. I would advise that you turn off Verifier for now.

    Was this answer helpful?

    0 comments No comments