New
#21
I had a power failure just yesterday. Crashed the computer with everything open.. mail, webpages, everything... Upon turning it back on, same thing as the OP.. Booted to the login, put in the password, and got the cute spinning water loop, I decided to walk away and let it spin. Came back some 1 hour later, and it was back at the login screen so I thought maybe it went into windows desktop and popped back out at the screen saver / blank screen / login prompt... well, put the password in and just the spinning water loop. Decided to do the power off and power on a few times, and same thing, hanging after the password... So, I happen to have beta 7100 still loaded on another drive, so I switch the drives and boot off the beta 7100 with the primary now slave 7127 ... well, it booted fine and I got the 7172 drive open, copied all my files I needed to the 7100 in case of a salvage operation of reinstall completely to the 7127 drive.. after about 20 gigs of copying data, I powered off, switched the drives again, and boom, the primary 7127 worked just fine.
Dont know what fixed with booting it as slave, but fixed the issue without having to reinstall at least, and I have my data backed up on a W7 7100 drive just in case.
I agree with that also but people are people...terms such as Pre-Release or BETA or RC are often "loss in translation" and when problems due arise they often question why it doesn't work as they are thinking they are using the complete new Microsoft OS. Now the case for this OP is that he has a problem but would rather diagnose it without jumping through the hoops of a Format...and I don't blame him. If I can make a suggestion for this thread...lets try and fix this issue without going that far...reinstalls often fix everything but that should be a last resort.
So you would re-install every single driver etc. instead of looking in one place to see what died? Seems a long way around method of doing things IMO.
Beta testing isn't just testing Win7 itself, it's making sure other things work with it too. Formatting or just doing a system repair doesn't tell you what went iffy and you would be back to square one after doing so.
You were trolling and therefore I ignored you.
We'll see when velcrohead confirms it's his nVidia drivers through it when he's @ home.
I'd put money on it if I was a gambler. :)
Let's just say my system has been 'heavily' stressed tested on the reboots for the past few days and it's been doing the same thing, first place I looked (Event Viewer) had red nVidia flags for each time it bummed out.