only 'Windows Error Recovery' screen during clean install to SSD

whs said:

I assume you changed the BIOS boot order to boot from the CD/DVD reader. Maybe you missed the short message: "Press any key ...". It then reverts trying to boot from the designated disk.

This has occasionally nagged at me, though the sounds from the DVD drive make me think it's GOT to be the boot device. Anyway, no, I've actually not seen the "press any key" message for a LONG time. Audible DVD sounds of spinning up and down and other circumstances tended to make me think this wasn't really a concern. But there's nothing I've found in (F2) BIOS per se to control the boot device. There is the (F10) boot device selector that comes up along with F2 as startup options, and I can move the arrow-controlled selected device to highlight the one I want, but there's no obvious way to latch that selection. F10 doesn't do anything at that point. "Enter" would appear to be the "save and exit" option, but...no, that's not really certain. But if that F10 selection worked, why would it ask me to "press any key...", right? I already told it I wanted to boot from the DVD, didn't I?

Another angle: is it really still possible, after booting with only the DVD (Win7 upgrade) and an "Unknown," "not initialized" and "Unallocated" SSD connected, that it's trying to boot from the SSD, while spinning the DVD up and down crazily... as what, an evil diversion?

It should prompt to Press Any key regardless if DVD drive is set first to boot in BIOS or using the one-time BIOS Boot Menu key. If not burn another DVD using latest official ISO and try booting again: Clean Reinstall - Factory OEM Windows 7

If this fails try writing ISO to flash stick using tool given in tutorial.

There are other steps which have been suggested which need to be caught up and then there will be more - normally this depends upon reply to each step which helps us help you advance.

I must say that I suspect it is your BIOS, needs to be updated, or the SSD is bad, it can happen, or that particular SSD, which you still haven't stated (That I have read) what make and model it is, is just not compatible with your system. That too can happen.

I have a Kingston SSDNow V200 drive that functions perfectly in a fairly new, late 2011 model, Macbook Pro. But when I removed it from the Mac and tried to install it in my new Dell E6420 notebook I could not get the image from an Intel 320 series SSD to install on it or do a clean install of 7 on it. This was after using the Mac to erase and format the drive back to MSDOS Master Boot Record partition table and then doing the same, formatting it, on a Win 7 desktop. That drive is a SATA 3 drive and I'm pretty sure the Dell is SATA 2. The Intel 320 series drive works without any problems in the Dell. I reinstalled it in the Mac and Cloned the Mac OS to it, just to check the drive, and again it works without problems in the Mac.
That drive just is not compatible with the Dell notebook, at least not that particular drive and my Dell notebook.

Installing Win 7 isn't this hard. There has to be some incompatibility between the drive and the system.

gregrocker said:

Check if your model computer or mobo has a newer BIOS version. If so reset the BIOS to defaults: Clear CMOS - 3 Ways to Clear the CMOS - Reset BIOS

While in BIOS setup set SATA controller (if any) to AHCI mode to try install first. If this continues to hang, then try IDE Mode.

Sometimes when the install hangs during driver-loading, you can enter the Device Manager to uninstall any erroring Devices, usually the Display adapter. This allows the install to complete when you can update driver from desktop: Device Manager - Access During Windows 7 Installation

Make sure all peripherals are unplugged[Dave's emphasis added]. Do you have a video card which if necessary you can unplug to default to onboard video chip to try install if it comes to that?

Greg - I'm writing this from the new OS in the ol' HP, so you know this has a happy ending - for now, at least. I haven't rebooted again, despite Windows Updates' persistence, so this could all go up in smoke later today.

"Make sure all peripherals are unplugged..." Given the relative simplicity of trying to reboot again without my HDMI connector (runs to external TV monitor) and a USB cable (goes to a hub w/printer) installed, I figured before I go flashing BIOS or to other terrifying extremes of time-suction, I'd try pulling those innocent cables, too (all other devices were gone by then). Did that make the difference? I dunno. But whatever...it works...for now.

I'm not forgetting that the same SSD let me do what I think I am doing now (loading up my most-needed software) while in IDE mode a couple of weeks back, and was only good for one or two reboots before it surrendered to The Blackening...

Shoots, cuz.
--Dave

So you are saying that SAME SSD, the one you are now having all these problems with, FAILED to load the OS properly a few weeks back after a clean install and a couple RE-Boots?

Not sure this will go over well but the last time I checked 2+2 still = 4. But what you want to happen is to make 2+2 = 5.

It's the DRIVE. Send it back.

We'll see. I've rebooted successfully once so far. And as I mentioned before, all other things were NOT really equal - SATA was set to IDE when it did install and reboot before.

In the world of PC diagnostics, it seems to me widely accepted that the old insanity indicator (expecting a different outcome from the same input) is indeed considered normal and sane. We reboot not once, not twice, but three times before we conclude there's really a problem. Remember the "if MS made cars" comparison? The engine fell out on the freeway? Meh. We call AAA and get it reinstalled, and accept it as normal. 2+2 might equal 4 most of the time, then it gets all wonky and goes to 7, but as everyone knows, when you reboot, it's 4 again. Me, I like a room where I can walk in and turn the light switch on and bathe in the glow of that CFL; maybe the fan turns on, too. Yes, it bothers me when I flip that switch and the room turns inside out, but I have learned to accept, if not enjoy this behavior in the world of PCs.

If it's solved it was clearly the HDMI cable, likely a driver issue which may need resolving or a Dual Monitor setup which is canceling out each other somehow. We have this in another thread right now.

Have you run the HDMI monitor on Win7 before without the problems? If so what is different about the way it's configured now, or its driver, or anything about it?

Greg,

Yeah, still running, and an impressive four reboots under the belt. I think it took this time.

The HDMI/monitor isn't new or anything - I think I changed to the HDMI cable when I put this mobo in the old HP case a year ago, but was still running XP maybe then...or was I? Anyway, it's got lots of hours of use with this same setup, except of course for the new SSD-based OS.

One thing about this that answered a COUPLE of my mysteries from the last few weeks, though - on those two occasions when it looked to me like I had a black screen (no display whatsoever, but power clearly on) and then gave up rebooting and instead went back to try to reinstall etc, well, it's almost certain that in reality, the HDMI was being treated as the primary display - with no signal at all to the desktop monitor. Naturally, I didn't have the "TV" on when I was fighting with the PC, so I never discovered this until today...when it began to bother me that during the black-screen thing, I'd see keyboard lights respond to things like Numlock, or the display would slightly brighten when I moved the mouse - then I discovered the mouse-arrow-cursor could be brought into view on the otherwise-black screen. At that point, merely disconnecting the HDMI swapped the display over to where I'd thought it would have been by default, on my desktop monitor, via the DVI connector. My exposure isn't cutting edge by any means, but since I've not yet run across a PC monitor that even has an HDMI jack, I'd have assumed my mobo would default the video signal to DVI or VGA jacks...apparently not - it's the HDMI first. So it's likely that when the black-screen thing happened a couple of weeks back, it was really this yet-undiscovered stupid problem.

That still doesn't address the fifty or so times I got the "Windows Error Recovery" screen while trying to clean-install between those times, though, but I'm happy to let that recede into the compost-pile of fermenting annoyances in my life.

Thanks again for the pointers.

Mahalo nui - Dave