Been Experiencing BSOD since upgrading my Motherboard, CPU, and Power Supply

I just restarted last night, another BSOD.
Managed to take a pic,

KMODE_EXCEPTION_NOT_HANDLED
FLTMGR.SYS

Included the screenshot and the zip file
zbook said:
There was no thread activity after 11/2 until today 11/28.

Recent BSOD were seen (11/22) that did not create dump files.

When available post Memtest86 results from post #4 step #16.

2 tests: 4 passes each = 8 passes

Images with text reports

If there are no errors then read this link on Windows Driver Verifier (WDV):

Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 + Vista | Sysnative Forums
Click to expand...

I'll post Memtest when I have the time.

In the meantime, I've ran Seatools, turned off fast startup, and checked the device manager.

SeaTools: all passed
Device Manager: The only errors I could find is under the USB controllers
 

Attachments

  • 20201208_053616.jpg
    20201208_053616.jpg
    35.1 KB · Views: 6
  • SysnativeFileCollectionApp.zip
    SysnativeFileCollectionApp.zip
    677 KB · Views: 2
  • Seagate.png
    Seagate.png
    61.6 KB · Views: 5
  • Device Manager pt1.png
    Device Manager pt1.png
    173 KB · Views: 4
  • Device Manager pt2.png
    Device Manager pt2.png
    199.2 KB · Views: 4
  • Device Manager pt3.png
    Device Manager pt3.png
    30.6 KB · Views: 6
Hi!

No dumps nor minidumps.
Logs seem the same you sent previous time (28-29 Nov 2020).
To get the new logs (with the minidumps in it, if present), re-use the bsodcollectionapp: SysnativeBSODCollectionApp

You get a persistent error with virtualbox in event viewer - system:
Code: 
  Log Name: System
  Source: VBoxNetLwf
  Event ID: 12
  Description: 
The driver detected an internal driver error on \Device\VBoxNetLwf.
It seems you can solve it deleting .Virtualbox folder from your profile folder: VirtualBox will not start

It seems a memory.dmp is present in c:\windows (seeing your logs).
If yes, you could zip and upload it to a file sharing service, then send the link here.


You could impose the creation of another minidump with ms windows driver verifier, if you prefer to investigate the cause of your BSODs.
Please read CAREFULLY the following instructions:
  • Create a restore point
  • Create a system image.
    You can follow this tutorial, if you shouldn't know how to do: Using Macrium Free to Backup or Image your drives
  • Backup your important files (the files you don't want to lose)
  • Read the guide about Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 & Vista (click).
  • Read some other tutorials/guides and WARNINGS on internet.
  • Unzip on your desktop the file I attached Verifier.zip and then:
    1. Open an elevated command prompt (right-click on windows start button, click command prompt (admin)
    2. Type (copy/paste) in it:
      Code: 
      bcdedit /export c:\DEFAULT-BCDedit-SystemStoreContent
powershell -executionpolicy unrestricted "%userprofile%\desktop\EnableVerifier.ps1"
    3. Press enter
    4. The previous commands will modify your bcdedit settings, will set the necessary driver verifier settings, will reboot your PC in three minutes (but you can reboot it before).
      It will (more precisely):
      Read More:
  • After the reboot, open a command prompt and check if verifier settings are enabled with this command
    Code: 
    verifier /querysettings
    Press enter.
    If they are enabled, let verifier run from 24 to 72 hours.
    If they are not enabled, inform me.
    If you'll get a very fast BSOD after you logged into windows, or after some dozens of minutes, the option ResetOnUnusualShutdown (rous) should reset driver verifier settings (and should allow you to boot your machine in a normal state).
    But if this won't happen, you'll need to go to safe mode to reset verifier settings.
    Once safe mode is available, from an elevated command prompt you'll type:
    Code: 
    verifier /reset
    Press enter.
    Sometimes it is necessary to use a system restore point (or a system image).
  • If you get a verifier BSOD in next 24-72 hours, post here the new verifier dump; from an elevated command prompt, launch this command:
    Code: 
    md "%userprofile%\desktop\minidump" && copy c:\windows\minidump "%userprofile%\desktop\minidump"
If you won't get BSODs at all, we'll wait the next BSOD in next days/weeks.



When we have finished and hopefully solved the BSOD, to restore the previous bcdedit settings you'll type (copy/paste) in an elevated command prompt:
Code: 
bcdedit /import "c:\DEFAULT-BCDedit-SystemStoreContent"
Press enter.
 
Last edited:
xilolee said:
No dumps nor minidumps.
Logs seem the same you sent previous time (28-29 Nov 2020).
To get the new logs (with the minidumps in it, if present), re-use the bsodcollectionapp: SysnativeBSODCollectionApp
Click to expand...
I sent the wrong file, sorry.
Here's the correct one.

xilolee said:
It seems you can solve it deleting .Virtualbox folder from your profile folder: VirtualBox will not start
Click to expand...
I have deleted the .VirtualBox folder, thanks for that

xilolee said:
It seems a memory.dmp is present in c:\windows (seeing your logs).
If yes, you could zip and upload it to a file sharing service, then send the link here.
Click to expand...
Here's the link, MEMORY.zip

xilolee said:
You could impose the creation of another minidump with ms windows driver verifier, if you prefer to investigate the cause of your BSODs.
Please read CAREFULLY the following instructions:
  • Create a restore point
  • Create a system image.
    You can follow this tutorial, if you shouldn't know how to do: Using Macrium Free to Backup or Image your drives
  • Backup your important files (the files you don't want to lose)
  • Read the guide about Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 & Vista (click).
  • Read some other tutorials/guides and WARNINGS on internet.
  • Unzip on your desktop the file I attached Verifier.zip and then:
    1. Open an elevated command prompt (right-click on windows start button, click command prompt (admin)
    2. Type (copy/paste) in it:
      Code: 
      bcdedit /export c:\DEFAULT-BCDedit-SystemStoreContent
powershell -executionpolicy unrestricted "%userprofile%\desktop\EnableVerifier.ps1"
    3. Press enter
    4. The previous commands will modify your bcdedit settings, will set the necessary driver verifier settings, will reboot your PC in three minutes (but you can reboot it before).
      It will (more precisely):
      Read More:
  • After the reboot, open a command prompt and check if verifier settings are enabled with this command
    Code: 
    verifier /querysettings
    Press enter.
    If they are enabled, let verifier run from 24 to 72 hours.
    If they are not enabled, inform me.
    If you'll get a very fast BSOD after you logged into windows, or after some dozens of minutes, the option ResetOnUnusualShutdown (rous) should reset driver verifier settings (and should allow you to boot your machine in a normal state).
    But if this won't happen, you'll need to go to safe mode to reset verifier settings.
    Once safe mode is available, from an elevated command prompt you'll type:
    Code: 
    verifier /reset
    Press enter.
    Sometimes it is necessary to use a system restore point (or a system image).
  • If you get a verifier BSOD in next 24-72 hours, post here the new verifier dump; from an elevated command prompt, launch this command:
    Code: 
    md "%userprofile%\desktop\minidump" && copy c:\windows\minidump "%userprofile%\desktop\minidump"
If you won't get BSODs at all, we'll wait the next BSOD in next days/weeks.



When we have finished and hopefully solved the BSOD, to restore the previous bcdedit settings you'll type (copy/paste) in an elevated command prompt:
Code: 
bcdedit /import "c:\DEFAULT-BCDedit-SystemStoreContent"
Press enter.
Click to expand...
I don't think I'm willing to carry out the driver verifier, at least not at the moment. Apologies.
 

Attachments

Attachments

  • memtest86 test2 pt1.jpeg
    memtest86 test2 pt1.jpeg
    72.4 KB · Views: 6
  • memtest86 test2 pt2.jpeg
    memtest86 test2 pt2.jpeg
    44.6 KB · Views: 5
  • memtest86 test2 pt3.jpeg
    memtest86 test2 pt3.jpeg
    25.3 KB · Views: 4
  • memtest86 test1 pt3 (all 0s).jpeg
    memtest86 test1 pt3 (all 0s).jpeg
    34.5 KB · Views: 4
  • memtest86 test1 pt2.jpeg
    memtest86 test1 pt2.jpeg
    50.1 KB · Views: 5
  • memtest86 test1 pt1.jpeg
    memtest86 test1 pt1.jpeg
    72.8 KB · Views: 5
zbook said:
For the unknown USB device use the hardware ID:

How to Find Drivers for Unknown Devices in the Device Manager
How to easily find drivers for Unknown Devices in Windows
Click to expand...
Of the 5 unknown USB,
3 gave me USB\DEVICE_DESCRIPTOR_FAILURE
1 gave me USB\RESET_FAILURE
and the last gave me USB\SET_ADDRESS_FAILURE

All of them are not currently connected to the PC.
I think this could be related to my sort-of faulty USB cable I use to charge my phone.
So I don't think it's a big issue.
 
Honestly, I didn't find anything useful in the dump:
Read More:
It looks like you got errors from chrome and opera, got bored and rebooted.
Uplay was intercepted by the event log:
Read More:
There's an error in a USB device, maybe the one you showed at 24th post:
Read More:
 
The recent dumps seem to indicate problems with the file system. I would still be suspicious of VirtualBox - drivers are still present. Also there is another driver YSDrv and some unloaded modules (YSR0 & YSDDR0) associated with the same program (BigNoxVM?)

Unable to load image \SystemRoot\system32\DRIVERS\VBoxDrv.sys, Win32 error 0n2
Unable to load image \SystemRoot\system32\DRIVERS\VBoxNetAdp6.sys, Win32 error 0n2
Unable to load image \??\C:\Program Files (x86)\Bignox\BigNoxVM\RT\YSDrv.sys, Win32 error 0n2

I can't say with any certainty that these are the problem but maybe worth investigating further.
 
xilolee said:
Honestly, I didn't find anything useful in the dump:
Read More:
It looks like you got errors from chrome and opera, got bored and rebooted.
Uplay was intercepted by the event log:
Read More:
There's an error in a USB device, maybe the one you showed at 24th post:
Read More:
Click to expand...
Oh yeah, due to having multiple windows and tabs open, I usually terminate my browsers through the task manager if I ever need to reboot or free up ram.

I have no clue what happened with Uplay.

Thanks for your help all this time.
 
I guess I am a little puzzled here. Poster is using a brand new motherboard with some old and new hardware, getting memory error messages and you have been asked to do Memtest86 quite a few times and post logs and that appears to be the only thing you haven't done yet it is the single most important thing you were asked. Specific messages aside 90% of all error messages are caused by bad or mismatched memory and your memory is a brand new category of memory being Ddr4, low end memory at that used on Ryzen 3rd Gen hardware that in my experience requires daily tweaking to begin with.
(I must explain as I am sitting on a Ryzen 3600 Gen 3 cpu with an AS Rock B550M Pro4 board which is my second motherboard after a Gigabyte Aorus board failure being driven crazy by freezes and "failures to execute" as I wait for endlessly slow shipping of an Intel i7 9700K cpu so I can throw this junk in the trash where I believe it belongs. I have never had so many issues with a cpu and boards in my life and I don't think any of this is "ready for prime time".)
 
Rich-M said:
I guess I am a little puzzled here. Poster is using a brand new motherboard with some old and new hardware, getting memory error messages and you have been asked to do Memtest86 quite a few times and post logs and that appears to be the only thing you haven't done yet it is the single most important thing you were asked. Specific messages aside 90% of all error messages are caused by bad or mismatched memory and your memory is a brand new category of memory being Ddr4, low end memory at that used on Ryzen 3rd Gen hardware that in my experience requires daily tweaking to begin with.
(I must explain as I am sitting on a Ryzen 3600 Gen 3 cpu with an AS Rock B550M Pro4 board which is my second motherboard after a Gigabyte Aorus board failure being driven crazy by freezes and "failures to execute" as I wait for endlessly slow shipping of an Intel i7 9700K cpu so I can throw this junk in the trash where I believe it belongs. I have never had so many issues with a cpu and boards in my life and I don't think any of this is "ready for prime time".)
Click to expand...

He did it: 28th post.
 
Oops my bad the attachments didn't show on the pc I was on for some reason.
 
Last edited:

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top