I am running both Fedora 14 and Windows 7 Professional on a home-built machine. The two operating systems are installed on different internal hard disks, and boot using Grub v1.99. The motherboard is an Asus M4A87TD/USB3 equipped with an AMD Phenom II 1075T processor and 16GB of RAM (G.Skill running at 1333Mhz).
Since the beginning of December, Fedora 14 and all other distributions of Linux have been unable to boot. During the boot process, the Grub screen appears and allows me to select between the operating systems installed. When I attempt to boot Fedora 14, the Grub screen is replaced with a screen of kernel errors, which run until I shut off the machine. This happens with all other distributions of Linux I've tried, both as Live CDs and bootable USB sticks, regardless of whether the internal hard disks are connected to the motherboard.
All the while, the computer boots Windows 7 Professional without incident. I suspect that I may have allowed Windows 7 to update some kind of Asus motherboard driver or firmware, but I cannot find evidence of that in the "uninstall programs" control panel in Windows 7. Further, the Asus website does not appear to have any firmware update for the motherboard other than a BIOS update, which I have yet to perform.
* Booting from a USB stick with the latest available Linux kernel
* Uninstalling all Windows 7 updates back to October 2011 (long before the problem started)
Solutions I'm thinking about trying:
* Updating the BIOS
* Replacing the motherboard
My questions to the community:
* Have you noticed such behavior in Linux-Windows machines before?
* Under what circumstances have you noticed this similar behavior?
* What do you think might be the cause of my problem?
* What solutions would you recommend I try?
This has happened to me before while trying to run Ubuntu on a separate harddrive and I have the Asus M4A89GTD/ USB 3 pro. I had Ubuntu installed inside Windows and after a few weeks or months of not using Ubuntu, I decided to try and boot it up and I got a black screen feeding much errors.
I think the problem might have to be with something inside windows. I would probably try to look for some stuff on Ubuntu or some other Linux forums.
Thanks for the reply, pacmanandre. I'm sorry to hear you've had the same problem that I have, may I ask what solution you used? If it's too complicated to go into detail here, can you post a link to the procedure you used?
In your case of separate drives, and what I do (Windows 7 x64 Pro, RHEL, Ubuntu, and Mac OS X ; 4 drives) is to use 'BIOS Profiles' as a 'boot selector' as opposed to some other boot loader. Windows 7 doesn't play well with others, and I have separate BIOS environments with my OSes.
This issue has been resolved. It turns out that one of my RAM chips was defective. I became aware of this first by running "memtest," available in the GRUB menu on startup. When memtest revealed errors during RAM testing, I tested each chip individually, determining that one of the four was defective. After its removal, I was able to enter 64-bit Linux on the very next boot.