What you really need to do is get into the recovery console of windows 7 again, open the command prompt, and run 'chkdsk C: /r' (the drive letter of C: may have changed as you're booting outside of windows, but it should be ok as recovery console usually uses X: as its default root directory.

All intellectual property rights, including without limitation to copyright and trademark of this work and its derivative works are the property of, or are licensed to, GIGA-BYTE TECHNOLOGY CO., LTD.

Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers. EDIT 2: This is what it gets stuck at when I try to boot into safe mode: Note the slight graphical corruption at the top of the screen.

Especially if you didn't mess around with hardware or drivers just before the problem occured.

Try running a disk test that reads the disk, byte by byte.

This is undoubtedly a corrupt install of windows caused by a few bad blocks.

This can be windows own fault, not the hardware itself.I happened to see this article just now and saw that the article is quite old so assume that the owner of the post must have rebuilt his machine by now.Still I'd like to add an answer of my own for anyone else that comes across this.It checks the integrity of windows system files and requests to replace as necessary. See 4.5 years desktop and server support experience covering 70 companies running anything from windows 98 to windows 7. You may try booting into your system with a Windows PE disk and renaming those files so the drivers don't load on next boot and see where you get.The only time I've really experienced this issue is when the jumpers on my IDE drives (I put Windows 7 on an old P4 as an experiment) were set to cable select.Before getting into troubleshooting, disconnect as many devices as you can. Forget the motherboard being at fault, it almost certainly isn't.