Windows 10: all these BSODs are driving me nuts

Hello,

I'm getting very frequent BSOD's, and up to now have not been able to get to the root of the problem. The software I'm using to analyse the dumps says it's not a hardware problem. My impression is that usually the BSOD occurs on waking up from hibernation. The usual advice is to "remove all third party software, etc. etc."; however, this is not practicable for me since I have so much software installed. One thing that seems puzzling is that the Event Viewer shows a message "Dump file creation failed due to error during dump creation"; however, a dump eventually was created. Any advice to solve this problem would be appreciated. I am providing links to data on some of my latest BSODs.

Regards,

BostjanVi


https://1drv.ms/f/s!AnO7wUiRDtNHhymf74m-dM0CIsx8


https://1drv.ms/f/s!AnO7wUiRDtNHhyh_cA9F0QBBunGm


https://1drv.ms/f/s!AnO7wUiRDtNHhz50j7HBA4pgl3Fb

:)

 

Hard drive/ OS issue

a guy suggested :

• shutdown
• unhooked HDD
• restarted
• yay !!
• reconnected HDD
• restarted
• yay !!

also , try method 3
How do I unlock the drive where Windows 10 is installed?

 

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.

 

Installing XP : IRQ_NOT_LESS_OR_EQUAL

Boot in step-by-step confirmation mode, and see what service or drive is causing the bsod.