Windows 10: Frequent Random BSOD, KERNEL_DATA_INPAGE_ERROR and INACCESSIBLE_BOOT..

I am unable to boot with memtest86+, I tried burning the iso to a CD and using the installer on a USB and i'm only getting "operating system not found"
I changed the BIOS setting after the first attempt: boot from external drive -> enable
and set external drive priority the highest
Still the same results.
I think I won't run the memtest86+.

I'll save up for a 1TB+ SSD because I don't want to downgrade in storage space.
A one like this will be fine?
Amazon.com: Intel DC S3500 2.5'' 1.2TB SATA III MLC Internal Solid State Drive (SSD) SSDSC2BB012T401: Computers & Accessories
if so, any similar cheaper ones?
if not, which do you recommend?

Thank you for the help.

 

I would recommend this one Amazon.com: Samsung 850 EVO 1TB 2.5-Inch SATA III Internal SSD (MZ-75E1T0B/AM): Computers & Accessories because it looks overall to be a great SSD (and receives a 9/10 score of the #1 tech site in my country).

 

Thank you for your help guys.

It seems like my HDD fixed itself. I'm not getting any BSODs anymore.
After 2 event entries my BSODs seems to have stopped.2/26/2017 -> The file system structure on volume C: has now been repaired.
RepairDetail 25008: Start repair on 02/26/2017 at 23:42:50:641 25016: Processing repair verb Connect: 0x6000000062152, "$I30", 0x6000000062152, 0x1, 0x6000000062186,,, 0x6000000062186 Flags: 0x34, 0x801 27294: The index entry GoogleCrashHandler.exe in index 0x6000000062152 of file 0x6000000062186 is missing. 26101: Inserting an index entry GoogleCrashHandler.exe into index 0x6000000062152 of file 0x6000000062186. 25009: End repair on 02/26/2017 at 23:42:50:662
RepairData 0F000000FFFFFFFFFFFFFFFFAE102E0006000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000020000000000000000000000000000000000000000000000000000000200000001000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 0000
2/26/2017 -> Volume C: (\Device\HarddiskVolume5) is healthy. No action is needed.

The next day 2/27/2017 I had another event entry where it gave me the error that the Hard disk has a bad block, but I have not been getting any BSODs since 2/26/2017.
I have no other disk related error in my event viewer except from today.
3/4/2017 -> The driver detected a controller error on \Device\Harddisk1\DR2.
Is this critical? What can I do about this.

I'm still saving up for an SSD, but if this "self-repair" is a temporary fix for an HDD maybe it can help others?
Not sure how it did it because I have not run any repairing tools other than chkdsk, but chkdsk didn't help in the past.

Thank you and may this help others with a failing HDD

 

Windows has mechanisms to repair detected corruptions by itself. It, however, cannot do much more than that, so anyone else reading this should get prepared for replacement.