Big Ga Posted November 26, 2010 Share Posted November 26, 2010 Hi Folks, Have a machine I built a few months ago - Asus M4A89GTDProUSB3 with a 6 core Phenom. Used a F60 SSD as the main boot drive. Everything has been pretty much flawless. Very fast read and writes. Never once seen a BSOD. Even seems to wake up MOST of the time from whatever power down modes it goes into (I think I have had two occasions when it pulled a wobbly after going into hibernate, but turning the PSU switch off and trying again sorted it out). However in the last week, I did get the situation when some things like image ingesting seemed to be taking longer than normal to perform. So I cleared out some temp files (I only had about 9GB free - now its about 20), all seemed ok, however, while this might or might not be a coincidence, the machine often now can't seem to boot up into windows. It just hangs at random points. Anywhere between the BIOS screen and the actual windows icons. If I try it 20 times, I might eventually get into windows - but the strange thing is, if I do, the computer is fine, no probs, and if I do something like a scandisk - no issues. It seems to remain ok as long as I just stay in W7 and don't try and reboot. Sometimes during the boot, it knows it failed last time, and asks if I want to run diagnostics etc, but whatever I select doesn't find anything wrong, and nothing I do makes any difference to the hanging boot issue. I've disconnected the SSD and reinstalled windows on a normal drive, and all seems perfect (I was worried it was a MB issue - doesn't look that way). I am downloading the latest MB drivers and BIOS as we speak, however what's confusing me is that the system in the exact same hardware config has worked so well for a couple of months. I'm tempted to rule out a windows software issue, as I've seen the machine hang on the BIOS boot section a couple of times (rare - but it has happened) before it even gets to the OS load part. This doesn't seem to fit the error reports I've seen while searching the forum - but maybe I've just missed them - anyone got any comments? has this sort of thing happened before (with zero BSOD etc), and thus, any opinions on whether the V2 firmware might sort it? TIA Ga. Link to comment Share on other sites More sharing options...
This topic is now archived and is closed to further replies.