Windows 10: How to fix random ongoing BSOD issues?

Hey, I've been having random ongoing BSOD issues for over a week now and I've tried everything out there to fix the issues. I recently stumbled on 'BlueScreenView' which displays my Dump Files with attached Bug Check Strings.I was hoping someone out there could assist in finding the issue.Bug Check String Codes: 1 MEMORY_MANAGEMENT 0x0000001a -> Caused by driver ntoskrnl.exe 2 PFN_LIST_CORRUPT 0x0000004e -> Caused by driver ntoskrnl.exe 3 IRQL_NOT_LESS_OR_EQUAL 0x000000a -> Caused by driver ntoskrnl.exe

:)

 

Random BSOD while browsing internet


BitDefender is nothing special. mwac.sys causes BSODs anywhere.
A tiny documentation can be found here: Solved Random BSODs - Windows 10 Forums
In that very thread, the suggested action apparently worked.

The storage and network filters of any third party antivirus can cause BSODs. Neither MBAM nor BitDefender is any special. For a regular antivirus, it may be shifted to an alternative; but MBAM has no alternative. So a clean install of the said program is the most feasible first step.
As far as the first step is not failing, it is better to not think for the second step. Because the BSODs are not universal, failure at the first step is not universal; and success at the second step is also not universal.
That is why I posted that my suggestion may work, or may not. Let us see where it goes.

 

Random and Ongoing BSOD's

Unfortunately, they are both examples of a driver that is doing something not recommended (specifying non-paged pool instead of the recommended non-paged pool, non-executable). It's a possible security vulnerability but it's not causing corruption. Also, that is the latest version of MBfilt64.sys from Creative and it's a filter driver for software audio effects - I have the same version on my Haswell system.




Driver Verifier results are almost certainly going to be a red herring in this instance. This is most likely a subtle hardware issue - driver corruption isn't likely to cause single bit corruption.

 

BSOD issue after fixing another BSOD error

Hi Williams,

There are several reasons why BSOD occur, which has different resolution. To check for any corruption or the integrity of your computer's Windows, we suggest that you perform a
Check Disk by following these steps:

• Type cmd in the search bar.
• Right-click on the Command Prompt, then Run as administrator.
  
• Type chkdsk x: /r, the /r command will fix errors found on the disk.

Let us know if you need further assistance.