Tons of BSODs at seemingly random intervals

It is recommended to not remove any dump while troubleshooting, or clearing the events.
The dumps could point to a patern making it easier for troubleshooting.
If you are using a program like Ccleaner please stop using it while troubleshooting.
This because programs like Ccleaner remove dump files that are needed to troubleshoot.
Or configure Ccleaner to not remove dump files:


ESET could take several hours depending on what you have chosen to scan and how many there is present to scan.

Please make sure the cable(s) of the monitor is/are properly connected and not damaged in any way (connection and cable)

All marked drivers are Windows drivers, some or all from the Windows File system.
In any way, I would recommend to run System File Check and to test the hard drives.
Further there is a 0x1A(MEMORY_MANAGEMENT) errors indicating memory problems. If the test is clean, it is suggested to run driver verifier to find the offensive driver.

Code:

0: kd> k
Child-SP          RetAddr           Call Site
ffffd000`2519c218 fffff803`0d971ea9 nt!KeBugCheckEx
ffffd000`2519c220 fffff803`0d9721d0 nt!KiBugCheckDispatch+0x69
ffffd000`2519c360 fffff803`0d9713f4 nt!KiFastFailDispatch+0xd0
ffffd000`2519c540 fffff803`0d936231 nt!KiRaiseSecurityCheckFailure+0xf4
ffffd000`2519c6d0 fffff803`0e08c65c nt!KeRemoveDeviceQueue+0xfd
ffffd000`2519c720 fffff803`0e08ab87 hal!IoFreeAdapterChannelV2+0x60
ffffd000`2519c760 fffff803`0e084ba2 hal!HalAllocateAdapterChannelV2+0x14f
ffffd000`2519c7b0 fffff801`6fb710d1 hal!HalBuildScatterGatherListV2+0x18682
ffffd000`2519c850 fffff801`6fbcc685 PCIIDEX!BmSetup+0x71
ffffd000`2519c8c0 fffff801`6fbcb388 ataport!IdeDispatchChannelRequest+0x115
ffffd000`2519c8f0 fffff801`6fbcb2c5 ataport!IdeStartChannelRequest+0x48
ffffd000`2519c920 fffff801`6fbcc4ff ataport!IdeStartDeviceRequest+0x349
ffffd000`2519ca10 fffff801`6f871367 ataport!IdePortPdoDispatch+0xbf
ffffd000`2519ca40 fffff801`6f8710be ACPI!ACPIIrpDispatchDeviceControl+0x97
ffffd000`2519ca80 fffff801`703640bd ACPI!ACPIDispatchIrp+0xbe
ffffd000`2519caf0 fffff801`70363a2c CLASSPNP!ServiceTransferRequest+0x29d
ffffd000`2519cba0 fffff801`6fa311ed CLASSPNP!ClassReadWrite+0x15c
ffffd000`2519cc50 fffff801`6fae1126 partmgr!PartitionIo+0x1bd
ffffd000`2519cd00 fffff801`701c1408 volmgr!VmReadWrite+0x126
ffffd000`2519cd40 fffff801`702b34e6 fvevol!FveFilterRundownReadWrite+0x2e8
ffffd000`2519ce20 fffff801`702b3348 rdyboost!SmdProcessReadWrite+0x146
ffffd000`2519cef0 fffff801`70253983 rdyboost!SmdDispatchReadWrite+0x98
ffffd000`2519cf20 fffff801`70abdcf6 volsnap! ?? ::FNODOBFM::`string'+0x1b3
ffffd000`2519cf50 fffff803`0d96a037 NTFS!NtfsStorageDriverCallout+0x16
ffffd000`2519cf80 fffff803`0d969ffd nt!KxSwitchKernelStackCallout+0x27
ffffd000`250d4000 00000000`00000000 nt!KiSwitchKernelStackContinue

Diagnostics Test

 System File Check

Please try following:

• Open an admin command prompt
• Copy/paste "sfc/scannow" (without quotes) and press enter
• When it finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

Diagnostics Test

 HDD TEST

Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums

   Note

Do not run SeaTools on an SSD as the results will be invalid.

Run chkdsk
Disk Check - Windows 7 Help Forums

Run HDTune to

• scan for errors, no quick scan but full scan
• check the health,
• benchmark.

It may take some time, but please take the time you need to perform it properly.
Let me know what the results are

• of the error scan,
• make a screenshot of the health of every hard drive and post the screenshots,
• post screenshots with the benchmark of the
  
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

Diagnostic Test

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

   Note

MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Diagnostic Test

 DRIVER VERIFIER

   Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

   Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

Please fill in your system specs

Please follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely including PSU, cooling system and other used stuff.

How to fill in your system specs:

Please try following command in admin command prompt

Code:

DISM /Online /Cleanup-Image /RestoreHealth

If there are problems with RestoreHealth, please follow step 6 or 7 (depending on the file you have from the download) from the tutorial DISM - Repair Windows 10 Image - Tutorial.

With SeaTools, have you only done the 'Fix All long' test?
If you have, open SeaTools again and run the short generic and long generic tests too.
The short generic test is the test that usually always passes, in that case the long generic test is the one that must determine the health of the hard drive.
If however the short generic test fails, the long generic test isn't needed anymore as the hard drive is failing/faulty.

The beeping is from the BIOS, the BIOS has the POST (Power On Self Test) in its software that tests the system at boot.
If something is wrong, you hear beeps, the beeps indicate what is wrong. However you need the motherboard manual to understand what those beeps mean to find out what is wrong.

I'm not someone who gives up until everything has been tried :)

I hope you can get a SSD soon for a clean install, we might just be in an endless troubleshooting process due to the upgrade.