Windows 10: Tarkov BSOD, memory management error

The last 2 attempts at trying to download tarkov as resulted in an error downloading it aswell as a memory management bsod errorThis was one of the minidump files 071924-6125-01.dmpI have had stability issues with the pc, so far i have hard reinstalled windows, clean install of drivers, for the most part it has become stable exept for this instanceThis is my first time building a pc, i stil dont know much but is it possible that since im downloading a large file to my drive, and i only have 1 drive in the system that it causes instabilty aswell as errors in the download, i always have to repai

:)

 

BSOD- memory management

Upon checking the dump file, the issue is being caused by ntoskrnl.exe. Ntoskrnl.exe is the one responsible for memory management that is why you're having the Memory Management error. We suggest that you follow the steps found in the link that we provided
in our last reply to resolve the issue. Please take note that if you're overclocking your processor or video card, kindly reset their settings to default.

Let us know the outcome after performing the provided steps.

 

IRQ memory BSODS, device manager, memory range?

The only time I've seen that type of BSOD for myself is when I fried the PCI-e slots on my Striker 2 board... There wasn't anything that I could do, try and rma and go on.. I would suggest the steps that MilkyWay has said.. But, if you really don't know much about Bios's... I wouldn't play with Irq's... That can mess up everything on your board. USB, ethernet, ram, chip... But, that's just me on playing with irq's... To much of a hassle IMHO..

 

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.