When you are in the cmd prompt in that mode you have to direct the chkdsk to the volume.
While it is normally C: - Windows may see it as being in D: so you would first need to enter this cmd -
bcdedit |find "osdevice"
That is a Pipe symbol before find which is the uppercase of \
Assuming that it is C: you would enter chkdsk c: /r
From whatever you get when you have the machine switched on, does CTRL+ALT+DEL get you the option to choose Task Manager ?
If it does, then click on File/Run new task and enter eventvwr - check the box to run the task as an admin - OK
When the Event Viewer opens, ensure Event Viewer (Local) is highlighted in the left pane and when the sections come up, check to see if Critical gives you anything other than an Event ID 41 - that just tells you what you already know and is useless.
If that's all it gives then see what events Errors gives you.
Using Task Manager you can also use it to open a cmd prompt admin by typing cmd.exe in the Run new task box and also checking the box to run new task as an admin.
I don't know if you would be able to enter this cmd from the recovery cmd prompt, but see if you can boot it up into Safe Mode with Networking with these cmds.
At the cmd prompt enter bcdedit
You are looking for the Identifier which can either be {default} or {current}
Then enter bcdedit /set {your identifier} safeboot network
Enter exit to close the cmd window then restart.
Hopefully that will boot you to Safe Mode with Networking but you will need to wire up to get Internet connectivity.
If you can get that far then I want you to download BlueScreenView which will analyze your Memory Dump files to see if it can ID what caused the shutdown.
http://www.nirsoft.net/utils/blue_screen_view.htmlIf you can get into that mode and a simple Restart doesn't get you back to normal mode, then from a cmd prompt admin enter -
bcdedit /deletevalue {your identifier} safeboot
exit
Then restart, but if the machine will only work in Safe Mode for the moment then, you will need to work in that mode.
If the HDD has further deteriorated then it could have damaged drivers, which BlueScreenView should highlight.
BTW - What are you using to post on ?