Share via

BSOD Troubleshooting

Anonymous
2020-11-27T16:42:23+00:00

Hi all, wondering if someone can maybe help me troubleshoot this BSOD that I am getting every few days. 

First, here is a link to my Event Viewer Crash logs: 

https://drive.google.com/drive/folders/1h8dFoXnU\_qA3iEnH-7rfwPglq0AOQOmh?usp=sharing

For some reason, I do not have a c/windows/minidump file, even though I have the option selected to write dumps to a file. 

Ive run: chkdsk with no errors, cfg scannow with no errors, memtest86 overnight, no errors.

My system is:

Msi b450 Tomahawk newest bios

G.skills Trident Z 2x8gb 3200mhz Cl16 running XMP 3200mhz

Ryzen 5 3600 with PBO turned on

Crucial mx500 500gb SSD Windows install

XPG 6000 pro 1tb NVME for games

Crucial mx500 1tb SSD for games

Temperatures are all normal

Running windows 10 Education Insider Preview

Build 20226.rs_prerelease.200925-1415

These BSOD are very random, sometimes the computer will just be idle when I experience it. As of late its "System_thread NetadapterCx.sys' thats causing the BSOD. 

I appreciate any help, thanks!

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

10 answers

Sort by: Most helpful
  1. Anonymous
    2020-12-12T07:02:11+00:00

    The mini-dump file is usually sufficient and this will be found in C:\Windows\Minidump

    The full memory.dmp captures what was in your memory at the time of the crash so it can get to be very large.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2020-11-27T19:55:59+00:00

    Okay, I've made sure that my settings match what you posted directly. Do I do anything else, or do I have to wait for a BSOD to occur again?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2020-11-27T19:45:29+00:00

    Unfortunately it looks as if you are not creating the dump files:

    Event[62]

      Log Name: System

      Source: volmgr

      Date: 2020-11-27T10:56:39.0820000Z

      Event ID: 161

      Task: N/A

      Level: Error ?  Opcode: N/A

      Keyword: Classic  ?  User: N/A

      User Name: N/A

      Computer: Mathew

      Description: 

    Dump file creation failed due to error during dump creation.

    Make sure your settings are exactly as shown below.  Type View advanced system in search window to find the System properties and select Start-up settings. 

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2020-11-27T17:21:34+00:00

    Yea I really wish I could revert back to a 'stable' 2004 build. If I cannot diagnose the BSOD issue, I am debating doing a clean install of windows so that I can choose to opt out of the insider previews. Ive since opted out of it, but have not yet had a windows update available to me.

    As for the memory.dmp there are no files in c/windows with that file handle. 

    Here are the files from the sysnative BSOD program:

    https://drive.google.com/drive/folders/1lxEHrx-e9aAXgu98MwYesg9tOX7nbIHb?usp=sharing

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2020-11-27T16:51:25+00:00

    Hello D3lap,

    There is always a risk when running Insider preview builds that you could experience BSODs - you should provide Feedback to Microsoft via the Feedback hub.

    If you have a memory.dmp file in the C:\Windows directory you could copy that to Google Drive and share it.

    Another option is to share the files from the Sysnative BSOD Log collector:

    Blue Screen of Death (BSOD) Posting Instructions - Windows 10, 8.1, 8, 7 + Vista | Sysnative Forums

    Was this answer helpful?

    0 comments No comments