BSOD hal.dll code 0xc000185

[Phoenix221]

My computer froze after being away from it for half an hour and when I restarted I got a message saying there was an error with File:\Windows\system32\hal.dll

It attempts automatic repair on startup and fails then I get the following message.

RECOVERY

Your PC needs to be repaired

a required device isn't connected or can't be accessed

Error code: 0x0000185

You'll need to sue the recovery tools on your installation media. If you don't have any installation media (like a disc or USB device), contact your system administrator or PC manufactuere

Press Enter to try again

Press F8 for Startup Settings

Press Esc for UEFI Firmware Settings

System diagnostics

I ran a system quick test which said

Hard Drive Short DST Test Failed

In Test Logs (All) I got the following messages

Type Hard Drive, Passed, Failure ID NA, NA

Type System [Q] Failed, Failture ID UC063Q-6A18SM-XD7X1F-60RE03, Hard Drive 1

I attempted restarting with the first system recovery disk in and it didn't do anything.

What do I need to do to fix this?

[pritam2015 · Accepted solution]

Hi,

                 I decoded your error code and I got 303 error code for your hard drive. The hard drive of your notebook is crashed and you need to replace it.

                 You are getting this error message from UEFI memory and windows is not loading at all, because of your hard drive is completely damaged.

[Phoenix221]

Thanks for the help. Is there any way to recover my data or is it lost?

[Skylarking]

---

@Phoenix221 wrote:
:

I ran a system quick test which said

Hard Drive Short DST Test Failed

:

What do I need to do to fix this?

---

HDD's use magnetic platters which is divided into sectors where the actual data is stored. The HDD firmware is clever enough to determine that these sectors are working correctly. When some issue is found, it can be either a hard fault or a soft fault, the sector is marked as a bad sector and is no longer used. This bad sector is mapped to another good loaction on the HDD platter by the firmware. which only has a limited memory for handling these bad sectors mappings. And at some point the firmware can't handle any more bad sectors...

In any case, when a sector that is used to store some file becomes bad, it means that the portion of data stored on that sector can no longer be trusted. It may be OK, it may be corrupted, but it can't be trusted. And if the file using this now bad sector was an important windows executable, it could be indeed corrupted and the OS may crash or behave oddly... 

Too many bad sectors means too many files you can't trust...

Sometimes, sometimes, "chkdisk" will find and repair the damage file (or identify it) so it could be worth a go. Also the command "sfc /scannow" could be used to scan and fix protected system files. Doing these two things may give you a bit of a window to better handle the suspect HDD and its data.

It's worth a go

But if you can't even boot into the OS, then your options become limited 

So i'd get a new HDD and reinstall the OS.If you have a recent backup you can use (before these sector issues started to occur) try it as restoring an image is quicker than a full reinstall.

In any case, most of your files should still be OK if the disk still spins up...

Anyway after you reinstall/reimage to a new HDD, you could reconnect the suspet HDD to your machine. Then try "chkdisk" and after that move your important files to your shinny new HDD.

If that doesn't work, as the files seem corrupt, then a more intensive data recovery process may be needed but cost and complexity goes up and your options become less and less the more the suspect HDD is used.

[pritam2015]

Unfortunately, there is no way to recover your data as @skylarking said the data is stored in magnetic plates and reader strip read the data from these disks whenever any of disks or reader gets contact with each other(physically), data stored on the disk is gets damaged.