Windows 10: Getting several BSODs daily

Hello, I have a samsung notebook 7 (740u5l-y0us). since last month, I am struggling with several bsods. most of them are system service exception and thread exception not handled. i downloaded the bluescreenview app to see what really causes the problem, but everytime it says microsoft windows operating system. I thought this is a hard drive issue, so I bought a new one still didin't work. I updated the graphic card drivers,network drivers. I used sfc/scannow, DISM, still didn't work. could somebody help me figure out what is really causing the bsod.



here are my minidump files location

https://1drv.ms/u/s!AjPeKbFNB759g0-bbF9hESjXp-k_?e=JDrbi6

:)

 

daily BSOD during normal windows use (not gameplay)

Here you go:
step16a, 16b and 17:









and I used Everything to find WFP-20190203-1043.dmp (430 MB):
WFP-20190203-1043.dmp - Google Drive

 

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.

 

BSOD DPC_Watchdog_Violation daily

Those steps are not relevant to me. In those steps it asks to check the IDE ATA/ATAPI controllers for iastore.sys in the listed drivers.

I do not have iastore as a driver nor is that the files causing the BSOD.

The driver that is causing it (I got this from BlueScreenView) is nvstore.sys which is listed as the driver for three identical items in 'storage controllers' There are 4 items there. 3 of them are called NVIDIA nForce Serial ATA Controller. Those three
all list this nvstore.sys as their driver.

I suspect that if I could replace or fix that driver it would solve the issue based on the advice given by Annanya. Does that sound right? If so, how would I go about it?

Dan