My computer is very poorly (freezing, BSODs, disk read errors)

[Gustafa]

SO yeah, my computer is freezing a lot, particularly while playing BF4, sometimes while not. After a freeze I will sometimes get a disk read error upon booting. This is usually solved by either rebooting again, clearing the CMOS, or re-seating the RAM. Today I started getting blue screens. One for NTFS.sys and one literally after getting on to the desktop after booting saying "STOP: c0000135 The program can't start because %hs is missing from your computer"

Crystaldisk does not report any errors on my drives, and I've done a Memtest overnight which didn't pull up any errors. I've also tried swapping SATA cables, but definitely isn't that. The fucks going on?

Specs:

W7 Pro 64bit
Asus P8P67 (1.02rev) Motherboard
Intel i5-2500k (default clocks)
R9 280X
850w PSU.

OS is on a WD: Velociraptor drive.

[editline]15th December 2013[/editline]

Just tried to do a check disk, scheduled through Windows. Restarted, came back with a Windows Boot Manager error.

Windows failed to start, a recent hardware or software change might be the problem.

File: Boot / BCD
Status: 0xc000000e

I then rebooted again, the little line blinked for ages detecting the drive, then the disk check started and immediately said that the disk was clean without even scanning it. So it basically skipped the check. Booted into Windows after that without issue.

[djjkxbox360]

Sounds like the hard drive, but it might not be. Check temperatures as this can be a problem when crashes happen during games or intensive tasks. And try opening command prompt and type sfc /scannow to check for broken windows files

[Gustafa]

Temps are all around 30c when in-game, so not that. Ruled out the RAM with my old sticks, definitely not that. sfc /scannow caused the "program can't start because %hs is missing" bsod. Just gonna try again to make sure it wasn't a fluke.

[editline]15th December 2013[/editline]

Turned out to be a fluke, system scan finished fine but did turn up some corrupt files, it also said it couldn't fix some of them >.<. I'd post the log, but it's fucking gigantic and I can't really tell where the scan started in it.

[editline]15th December 2013[/editline]

Running Chkdsk successfully now, has come up with 5 unreadable file record segments so far in the first 3%. The hard drive is also making a squeeking noise when it reads the data. :(

[editline]16th December 2013[/editline]

Chkdsk hung with an unspecified error, rebooted to find bootmgr missing. Oh joy. Also it's weird my bios sometimes won't detect any drives at all.