A couple months down the line I kept on getting booting error. "Windows has failed to boot please run start-up recovery" or something along the lines of that was displayed. After multiple attempts at unsuccessful recovery I decided to reformat. I noticed a partition on the disk called SYSTEM FILES. I decided I'd find drivers on the internet or what not a clear the entire hard drive of both the SYSTEM FILES partition and the normal Windows 7 partition. After reformatting everything ran smoothly... That is until I put in the driver disk. After reboot the computer wouldn't start. I reinsert my Window's 7 disk, go through the boot menu, and attempt a repair. I notice that the SYSTEM FILES partition is back. I reformatted my computer yet again and started anew.
After doing the same thing without putting the driver disk in windows still fails to boot and prompts me to repair. I see the SYSTEM FILES partition is there again. I decide to just repair the start up function with the disk and all goes well. A few log ins later the log-in takes a good 10-20 minutes and then comes up with an error (which I don't recall, but I believe it had to do with a Kernel Error or perhaps that was the BSoD I encountered later). I do a full Windows 7 repair and then use the window's 7 memory check which doesn't say my memory has any problems.
Currently the computer will occasional BSoD, won't recover from power loss, often has to be repaired, and when using programs (I've noticed it happens in Winamp) it will simply freeze stopping everything including sound.
This is still under warranty, but being in college I can't just ship my laptop off for a couple weeks to get it repaired.
What I believe to be happening is that the SYSTEM FILES partition is somehow effecting the Windows 7 files or something of that nature, but I could be completely wrong given that I have no knowledge of hardware errors.
(Not completely sure what board this goes in)
Edited by Multiverse Labyrinth, 19 January 2011 - 12:03 AM.