GRUB after POST screen

[cf8000dzl]

I swapped ram from my machine, which is running vista, and has Ubuntu, into another machine running Windows 7.

After swapping, the Windows 7 machine will post, but right after, goes to a black screen with "GRUB" displayed.

Even after swapping the original ram back, it still displays GRUB, and wont boot.

What could have caused this and how can I fix it?

Thanks

 

[computersplus]

Weird

hey that's pretty weird....put your Windows 7 disc back in and do a start up repair

 

[cf8000dzl]

Unfortunately i don't have the CD.

Any other possible fixes?

Thanks

 

[computersplus]

help

this may help

http://www.sevenforums.com/tutorials/2676-bcdedit-how-use.html?ltr=B

 

[computersplus]

Ubuntu

you could load Ubuntu on that drive as well

 

[cf8000dzl]

I cant even get the machine to boot, so I believe the BCDEDIT is out of question.

Why did this GRUB start showing up after swapping the ram?

Thanks.

 

[computersplus]

Weird

Don't know that is weird as it resides on the MBR not in ram very very weird

 

[computersplus]

try this

try this

Download EasyBCD 1.7.2 - NeoSmart Technologies

 

[cf8000dzl]

Managed to find a windows 7 Install cd. Ran the repair, went to console, did bootsect /nt60 c: /mbr, and it still shows GRUB, and wont load.

This is way beyond FUBAR.

Thanks

EDIT: Also ran the integrated repair, and said it cannot save the repair to the boot sector.

 

[patio]

Don't see how this is even possible with just swappinf RAM as it is volatile memory and is erased when power is removed...

Something else is going on here.

You didn;t happen to swap that Vista HDD in there...even for an instakt at any time did you ?

 

[cf8000dzl]

Nothing else has been swapped, only the ram, as i was testing to see if BF2 would run without crashing due to only having 2 gigs in my machine, and swapped for the 4 gigs in the other. My machine works, and the other is kaput.

The only thing that was done before the swap, was running Registry Mechanic. It found 236 errors that it could not fix, + a bunch more that it did fix. Unfortunately, the machine was never restarted after Reg Mech run, before the ram swap, so there is no way to tell if Reg Mech messed it up.

 

[computersplus]

well registry mechanic did not install grub lol.....like i said this is very very weird did you try a full format reinstall

 

[seekermeister]

In the event that you find it necessary to reinstall the OSs, I would strongly recommend that you install each OS on a separate drive, with all other drives disconnected...if you have multiple drives. This would eliminate Grub entirely, as well as any other boot loader, except the BBS Popup menu that appears when you hit F8 during boot, which displays a menu of drives to boot, rather than OSs. I have tried a lot of different bootloaders, and as far as I'm concerned, they aren't worth anything.

 

[patio]

None of what you say happened would have caused these symptoms...including any registry tools.

 

[vswee]

Windows 7 boot FAIL

hi, i have windows 7 and ubuntu and windows 7 installed on my notebook. since i've updated to dual boot of karmic koala and windows 7, i've noticed something strange. when i try to boot up into windows 7, grub allows me to choose it as normal but right after the splash screen the computer just suddenly restarts and dos loads again and then grub.

i can choose to boot into windows 7 again but usually it ends in the same sudden restart about three times then it'll boot up as normal. the computer shows no error message of having been shut down incorrectly or anything, it just fails to boot past the splash screen on the first attempt.

please help me!

 

[seekermeister]

Have you tried booting to the "Last Known Good" option?

 

[Tews]

This is a result of using the WUBI install method... if you do a straight dual boot installation, it will use GRUB straight away...

 

[vswee]

um, there is no "use last knows config that worked" option. it restarts as though nothing's wrong and um dude, i do have them dual booted, no wubi involved. both operating systems exist on two separate disk partitions and are booted into by grub 1.9 beta 4

 

[seekermeister]

If you can boot into Safe Mode, do a selective startup by disabling everything on the Startup tab and see if it cures the problem. If so, reenable the startup items one at a time, until the problem returns. If and when it does, the last item reenabled is the one causing the problem. If disabling these items has no effect, then the problem must be a driver. Go to the Device Manager and check the driver details for each device, making sure that there are no ! or ? items listed. When possible, update all driver to one directly from the device manufactacturer. Sometimes, Windows will balk, claiming that it already has the best driver when attempting to update, unless this is done is Safe Mode.