Computer not responding when doing a threat scan.

Computer starts up fine and runs as good as ever, but whenever i run a threatscan in malwarebytes it hangs at "C:windows\system32\NlsLexicons004.dll" and my computer slows to a crawl. Any application that i was on will stop responding and Task Manager will show my HDD activity at 99-100% (yet processes show 0%). After 5-10 minutes or so the scan will complete and my computer will be back to normal.

I checked the system logs in event viewer after one of these slow downs and it shows many warnings "The IO operation at logical block address 0x108cf00 for Disk 0 (PDO name: \Device\0000002c) was retried Event ID 153"

From that event ID i realise it is something to do with my HDD.

Running sfc /scannow and in the verification phase it stopped at 42% saying "windows resource protection could not perform the requested operation."

I ran a CHKDSK at startup and it came back with this:
___________________________________________________________________________________________
Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
Cleaning up instance tags for file 0x2ceff.
365312 file records processed. File verification completed.
4516 large file records processed. 0 bad file records processed.
Stage 2: Examining file name linkage ...
463816 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered.
Stage 3: Examining security descriptors ...
Cleaning up 2094 unused index entries from index $SII of file 0x9.
Cleaning up 2094 unused index entries from index $SDH of file 0x9.
Cleaning up 2094 unused security descriptors.
CHKDSK is compacting the security descriptor stream
Security descriptor verification completed.
49253 data files processed. CHKDSK is verifying Usn Journal...
Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
Read failure with status 0xc0000185 at offset 0x1f08e0000 for 0x10000 bytes.
A disk read error occurredc0000185
The disk does not have enough space to replace bad clusters
detected in file 181752 of name \Windows\WinSxS\AM9085~1.163\NLSLEX~1.DLL.
Read failure with status 0xc0000185 at offset 0x1f05c7000 for 0x10000 bytes.
A disk read error occurredc0000185
The disk does not have enough space to replace bad clusters
detected in file 190176 of name \Windows\WinSxS\AMAE68~1.163\Amd64\CNBJ3030.DPB.
365296 files processed. File data verification completed.

Stage 5: Looking for bad, free clusters ...
175981431 free clusters processed. Free space verification is complete.
CHKDSK discovered free space marked as allocated in the volume bitmap.

Windows has made corrections to the file system.
No further action is required.

976220159 KB total disk space.
271666828 KB in 294898 files.
165288 KB in 49256 indexes.
0 KB in bad sectors.
462315 KB in use by the system.
65536 KB occupied by the log file.
703925728 KB available on disk.

4096 bytes in each allocation unit.
244055039 total allocation units on disk.
175981432 allocation units available on disk.

Internal Info:
00 93 05 00 64 40 05 00 55 d3 09 00 00 00 00 00 ....d@..U.......
dc 00 00 00 24 00 00 00 00 00 00 00 00 00 00 00 ....$...........

Windows has finished checking your disk.
Please wait while your computer restarts.
____________________________________________________________________________________________

Not entirely sure how to fix this.

hello and welcome to eight forums .,if it were mine I would start with a hard drive scan using the utility from the makers of the hard drive ,so start with getting the name off the hdd and go to there website and get the utility for dos, create the cd/dvd and reboot to the dis and run the quick scan and then full scan

caperjack said:

hello and welcome to eight forums .,if it were mine I would start with a hard drive scan using the utility from the makers of the hard drive ,so start with getting the name off the hdd and go to there website and get the utility for dos, create the cd/dvd and reboot to the dis and run the quick scan and then full scan

Click to expand...

Using western digitals data lifeguard tool i failed to use the one for dos, so instead i used the one for windows. Is there an important reason for using one over the other?

You have tried sfc /scannow.

How about trying ---

Dism /Online /Cleanup-Image /RestoreHealth

in admin cmd prompt & THEN sfc /scannow ?

FireJellopy said:

caperjack said:

hello and welcome to eight forums .,if it were mine I would start with a hard drive scan using the utility from the makers of the hard drive ,so start with getting the name off the hdd and go to there website and get the utility for dos, create the cd/dvd and reboot to the dis and run the quick scan and then full scan

Click to expand...

Using western digitals data lifeguard tool i failed to use the one for dos, so instead i used the one for windows. Is there an important reason for using one over the other?

Click to expand...

no ,should show same results

Run extended test on Data Lifeguard. Right click on drive, diagnostics, extended test. May take a while.