I've problems that have gotten worse from rebooting. My old laptop locked up while going into hibernate mode one time so I turned it off and turned it back on; completely hosed the file allocation table. Had to replace the hard drive.
(It was years ago but I've still got that drive because I heard there was a way one could get to do basic data recovery at home with equipment that one might be able to find at a computer store with a little shopping around. I never got the details of that though. Does anyone know?)
For me it seems like if I hard reboot after Windows froze on me, it just loves to FUBAR sdb.dat and spam the error log, even with a brand new hard drive, and running chkdsk /f doesn't fix it. (Deleting it after rebooting did, though! Apparently it wasn't
important. I couldn't find jack shit about how to fix it or what it even did.)
I even turned off write caching to stop it from happening again, but apparently when I upgraded to windows 10, it helpfully turned it back on, so it FUBAR'd it again a month ago or two ago.
If what you did was "hose the file allocation table" (since it shouldn't normally be possible to damage the drive physically by rebooting) there's a backup table on the drive. If you broke windows, that's different of course but looking at it in another computer could be expected to work if the drive is still OK. Normally chkdsk could fix it. Depending on the size of the drive, it could take a while.
Expensive specialized recovery equipment is for trying to recover stuff directly off the platters if it's been erased or physically damaged, and that's expensive (and you shouldn't need it). You just need to be able to connect the drive to a computer and run chkdsk /f on it and see if it fixes what's wrong.