Not long ago I installed Windows 10 on the new SSD and I'm dual booting Windows 7 and a copy of Windows 10 Preview (although the Preview no longer says preview and acts like a real full version).
A few weeks ago I added another memory module just to fill up an empty slot and everything went fine with no hitches in any OS until recently when 10 gave me the oops message and 7 kept going to a black screen. I didn't suspect the memory at first and ended up with a constant loop of disk checking and corruption messages until finally 10 just wouldn't load at all.
Removed the offending memory and then went on to recovery.
Since MS have made booting outside normal mode a pain in the ass now, I managed to fire up 10 preview and create a USB recovery drive.
Disconnected all drives except the SSD, booted from the USB and tried to repair, which it couldn't.
Restore wouldn't work saying I hadn't selected an OS.
Both reset options wouldn't work either as the disk is locked.
DOS cmd using bootrec told me no devices were found.
The disk is functioning correctly as far as I can see and is recognised in the preview and 7.
I'm now downloading 10 again using the media creation tool and will have a go at a clean install later unless anyone knows of a way to unlock the SSD in spite of my Googling.
April 29, 2013
I am sort of having the same boot issues with W10. I am triple booting with XP,W7,&W10. W10 is in the boot menu and I can boot into W10 just fine but if I shut down the PC from within W10 and do a cold boot then I get a "A bootable device has not been detected" issue. If I do a Ctrl>Alt>Del then I can get back into my boot options. I have now set W7 as my default OS. I really think this has to do with UEFI and the only way I can see to fix it is with a W10 reinstall, which at this point I am not going to do. I am thinking of installing W10 in a VM in W7 and use it that way, I am kinda of tired of this UEFI and what it has and is doing for PC users.
I really can't be doing with any more mucking around so I'm doing a clean install tomorrow.
I can't use a VM because of the gaming and I want to take advantage of the SSD speed.
Pretty annoying really and I can barely count on one hand the amount of times this has happened to me and thankfully not much to back up.
Guys, take it from one who has experienced all these issues - the problem is caused by dual booting Windows 7 and Windows 10.
I had similar issues when dual booting Win7 and Win8, Win7 just does not play nice with Win8 and/or 10 in a dual boot scenario.
Most of these issues occur when booting from Win7 to the newer operating system. Booting from a newer operating system to Win7 seems fine, as does booting from Win7 to Win7 (restart).
On my older machine I am still triple booting (Win7+Win8+Win10) and every time I run Win7 and then restart and boot into one of the newer operating systems there are issues - restore points deleted, chkdsk wants to run, no boot device found error messages, and so on. I've got used to it by now.
My newer machine is dual booting Win8+Win10 with no problems whatsoever. It's only when Win7 is thrown into the mix that issues seem to arise.
Marc - I'll almost wager that if you test the memory module it will be okay.
April 29, 2013
Are you using EasyBcd Jim?
I intentionally don't run it from Windows 10 because i've had problems with it causing boot problems, so I use the BIOS instead, although a little more long winded, it achieves the same without altering the boot sectors, at least that's the theory.
I also always disconnect all other drives when installing a new OS and only reconnect them later.
On that basis, I really don't understand why both 10 and 7 should have borked.
I'll be testing the memory module in the next couple of days and I hope you're right. although part of me hopes you're not.
April 29, 2013
I use Easy BCD to set my boot loader entries but that is because all my OS's are all on one drive. I have used the same method you are using when I had the OS's on three different drives. You can use Easy BCD to create your boot menu but Easy BCD would need to be installed on either the W7 or W10 drive. One thing I have noticed when I installed XP and W7, and W10 is that the W10 will write it's own boot menu regardless of the boot menu set up with Easy BCD. I wish I knew how to take screenshots of the two different bootloaders. If you have those's OS's on two different drives then you should be able to at least run bcdedit and use bootrec /fixboot and /fixmbr do a repair on the W7 OS if you have a W7 repair disc or a W7 install disc.
Most Users Ever Online: 271
Currently Browsing this Page:
Guest Posters: 10
Administrators: Jim Hillier, Richard Pedersen, David Hartsock, Marc Thomas
Moderators: Carol Bratt, dandl, Jason Shuffield, Jim Canfield, Terry Hollett, Dick Evans, Sergey Grankin