Startup Problem - Please help

Hello everyone, it's my first post in the forums and I'm in desperate need for your help. It's my first time dealing with a problem like this one so here it is.

Three years ago I bought a decent desktop for that time and I guess the main parts that are worth a mention here are:

MB:Asus Striker II Extreme
CPU:Intel Core 2 Quad Q9650 3.00GHZ
RAM:2GB DDR3 1600MHZ
GPU:nVidia GeForce GTX260
HD:WD Velociraptor 300GB 10k RPM

Truthfully, apart from minor issues, I never had a serious problem until now. My problem started to appear on September after I returned from my annual summer vacation. The PC wasn't used for about a month.

So when I booted my PC, logged into Windows 7 Pro 32-bit and everything was working fine, the system gave me a BSOD. I thought it was no big deal but then Windows 7 refused to start. To be precise, the system was stuck in the loading bar that had stopped moving. I wasn't sure what to do. Tried many reboots or to fix it with the Windows CD via system restore or repair but all of them had the same outcome. At a moment of improvisation, I disconnected the hard drive and reconnected it. That was it, on the next boot Windows successfully started and no BSOD was shown again. I dismissed it as an one-time thing and didn't care much.

The PC continued to work fine for about 2 weeks. This time a message was shown before loading Windows: 'DISK BOOT FAILURE' and was stuck right there. I disconnected and reconnected the hard drive again and once again the problem vanished.

After about a week this time I had a combination of those two. I logged on my windows, got a BSOD and the loading bar was stuck again. I did the hard drive trick, rebooted and this time I got the DISK BOOT FAILURE message. Did it a second time in a row and then it was finally fixed.

I had began to worry so I performed an OS format and installed Windows 8 which I got early via Dreamspark. Nothing changed (except for the BSOD that now is windows 8 style).

Weeks passed with the problem gradually reappearing more often and with me always trying to fix it with the same routine.

Right now, as I'm typing this, I'm praying I won't get another BSOD for today.The problem now appears every day and more specifically every morning. I get 4-5 BSODs a day and throw 1-2 DISK BOOT FAILURE messages if you like in there. I disconnect and reconnect the hard drive 3 or 4 times now so I can finally get it to work.

What's interesting enough though is the fact that after I can finally get it to load Windows, the system runs perfect for the rest of the day. I can't explain it. I can even perform 5 restarts and still not crash or anything but first thing tomorrow morning, I'll either get a BSOD or get stuck in the loading screen or get a DISK BOOT FAILURE message. OR maybe all three like today.

My guess is my hard drive's days are numbered. But I still can't get it how is it possible for it to run perfectly after I can finally log into the OS.

Any ideas? Anyone with a similar problem in the past and how he solved it?

If you need any more hardware information I'll be glad to provide it. I'd like to keep my PC away from service if there's another solution.

Have you tried checking the HDD data and power cables (and possibly using a different one?
Also try plugging the HDD lead into a different connector on the motherboard.
If none of those help try running some s.m.a.r.t diagnostics software on your HDD to see if it is failing (it will know). There are some free utilities that you can download form the manufacturers but they are usually HDD brand dependent.

If you are working with your laptop computer, it can be annoying when the computer rush into confrontation and will not start or boot up. There are a few troubleshooting odd jobs that you can oppose to get the computer started again. This will not get hold of any software to do and can be ended without allocation an apparent. Decent the difficulty may take a few mechanism and preserve parts.
gold coast it support

This question was for a desktop as given in the specifications and your reply makes no sense.

@Noct90 - how did you go, if you got if fixed what was the problem (may help others in the future).