Mint 18 crash to blank screen and won't restart
 

On a Lenovo desktop, Mint 18 suddenly crashed while I was listening to music on youtube, to a black screen with the flashing underline cursor. I manually restarted the computer. I chose Mint 18 from my OS list. It would not start. Instead it read, error attempt to read hd0

I manually restarted and used another OS from the list which works.

Memory test seemed okay. I didn't observe carefully at first, then looked over the results and it was okay.

Updater had it up to date. Including Linux Kernel.

Is there any way to fix it?

It could well be a filesystem problem. I would manually run fsck on the filesystem(s) in question to see if there are any errors.

Can we have the output url from
please?

If a fsck doesn't help, that is. ;)

when you're ready.
and boot the current kernel ("Older versions" on the mint boot menu, I think. I only have the one.)

Can I run this from Mint the OS alongside the faulty Mint install? Because it will not start up but only gives the reading I typed. Or need I go into the safety mode?

You can run it from any of the other Linuxes that you dual boot on your system. You just have to be aware of which filesystem(s) the aberrant Mint install is using (if it is only using one filesystem, i.e. partition, for / (root filesystem) then all the easier).

If you don't have any other Linuxes you can boot up into, you can do it from a Linux installer disk/boot media or any of a variety of repair media.

gparted has a "Check" option on right-click of an unmounted partition.
This is functionally the same as a "manual fsck", IMO.

Could you take another look at the error message. Could it be

Yes and it has just happened again with the alongside OS Mint.
I am now in a live trial version about to use gparted.

Might consider smart results while you are looking at it.

Be sure ram shows as correct amount before you test.

Can see what /var logs might show.

Look at any bios logs if they exist.

Yes, Gparted check function fixed the problem.
What caused the problem, and twice? a hacker?

What does Menu > Log Viewer indicate?
Dozens of possible reasons. None of them have the string [Hh]acker in them, IMO.