Windows sign in will not open "Bad Hard Disk"

When turning on, the screen will display the windows startup animation and once finished a blank screen. After about 30 seconds to a minute a black screen pops up and asks if i would like to start up normally or run startup recovery. The Normal start up fails and ends up returning to the first black screen. When i run startup repair it says it cannot find a solution. I sent error message and the log said:

All tests performed were successful.
Root cause found: boot status indicates that the OS booted successfully.
Root cause found: bad hard disk: Bugcheck 7a. Parameters = 0xfffff8a000efeb80, 0xffffffffc0000185, 0x1753e08c0, 0xfffff900c0770000.

Each session reported a single root cause which ended up being one of those two.

After that i went under additional options and signed into system recovery using one of the users and selected startup repair again and went under problem details:

Problem signiture:
Problem event name: StartupRepairOffline
Problem Signiture 01: 6.1.7600.16385
Problem Signiture 02: 6.1.7600.16385
Problem Signiture 03: unknown
Problem Signiture 04: 21200110
Problem Signiture 05: AutoFailover
Problem Signiture 06: 6
Problem Signiture 07: BadDisk
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

I tried looking up aolutions online but couldnnt find one that was identicle.

I then tried diskcheck using command prompt, under C: /F and /R.

Sometimes the processes would complete with no errors or solutions and sometimes the processes would get stuck on a certain file and would not move even after 10 to 20 mins alone. Although when the processes do complete at the bottom they would say something along the lines of "log could not be saved : status 50" or something.

The computer runs Windows 7 64-bit and is an Asus A35S series.

Time is of the essense as i need this laptop for school. Thankyou.

Well that doesn't sound good, I'm still investigating other options but as far as the thread you lead me to. Are those directions only for Linux? or will it work both ways?

Ahh.. well with some further studying it actually turned out that the hard disk was loose. It had slid partly out of the socket. All it needed was a little tightening and wa-la it was fixed. Although not 3 hours later we discovered that there really was an error with the disk drive which wouldn't allow the system to boot at all. Something called the boot manager was missing or something. So we decided it would just be easier to get a new hard disk and get it over with, and it now works fine. Thank you for the help though.