Windows 10: I keep getting random bsod errors can anyone help me

here are the dump fileshttps://drive.google.com/drive/folders/1wJZ89OAjGwlFUX2e3ciyMVEygZwq_qZc?usp=sharing

:)

 

Random BSODs "Bad_Pool_Caller"


This BSOD happens anywhere, irrespective of BitDefender. It takes place even when the antivirus is MSE in case of Windows 7. The most common cause is an expired trial or a cracked installation. Some examples:

• Norton: Windows 7 Random bsod caused by tcpip.sys - Windows 7 Help Forums
• MBAM only: Epic BSOD error appears just after few seconds from boot Solved - Windows 7 Help Forums
• McAfee: BSOD on Internet Related Programs (tcpip.sys) - Windows 7 Help Forums
• Avast: Bad Pool Header 0x00000019 at random times - Windows 7 Help Forums
• Avira: BSOD randomly Crashes my Laptop and freezes at Memory dump 100 - Windows 7 Help Forums
• Crack: BSOD every 6 minutes, also recent freezes - Windows 7 Help Forums

We are on our way of troubleshooting. If the uninstallation and reinstallation does not work, we will take the next step.

I, in general, know what I am doing and what I am suggesting. If I feel that I am unable to control the issue, I will definitely ask for help.

 

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.

 

Getting BSOD 0x124 error

Ignore what everone said here.

0x124 BSOD is usually related to VCCIO (VTT), run Prime95 version 26.6 with custom sizes of 512K to 640K with 50% of your memory for at least 8 hours.

If you get a 0x124 BSOD, increase VCCIO voltage by small steps, run Prime95 again until your stable.

If you pass Prime95 512K to 640K without a BSOD, then its Vcore too low. I'd suggest running IntelBurnTest with 80% of your memory to verify stability (8 to 12 hours).

Oh, and yeah, if this problem appeared all of the sudden, the reason is CPU degradation, you can prevent it by enabling C-States or adjust your overclock to use lower voltages.