Backup critical data by any means possible.
Can indicate that the SYSTEM hive loaded by the osloader/NTLDR
was corrupt. This is unlikely, since the osloader will check
a hive to make sure it isn't corrupt after loading it.
It can also indicate that some critical registry keys and values
are not present. (i.e. somebody used regedt32 to delete something
that they shouldn't have) Booting from LastKnownGood may fix
the problem, but if someone is persistent enough in mucking with
the registry they will need to reinstall or use the Emergency Repair Disk.
Arg4: c000014d, usually the NT status code ("C000014D" STATUS_REGISTRY_IO_FAILED)
You can of course try "Last Known Good" option from the advanced boot menu (F8) if you are having trouble booting your machine, and see if that helps.
Looks like it may be a hard disk issue so use the native Check Disk utility to see if it produces anything useful.
Open an elevated command prompt and type
chkdsk C: /R
answer in the affirmative "Y" when prompted
let it finish all five stages and check the results in event viewer when complete.
EDIT: I would also recommend checking with your system board manufacturer to determine if there is a BIOS update available that might help improve system stability.