Suddenly, my laptop refuses to start Windows. I tried rebooting it multiple times and tried startup repair, but that doesn't start up either. Ubuntu works fine, so I'm pretty sure this is a Windows error and not a hardware error. Any help to getting my laptop to boot Windows or getting startup repair to work?
What happens exactly when you try to boot it up.
It loads fine, until it gets to [url=http://www.erdalozkaya.com/wp-content/uploads/windows-starting1.jpg]this part[/url] which just keeps repeating over and over again. If I try to use startup repair, it gets stuck after [url=http://0.tqn.com/d/pcsupport/1/5/d/4/-/-/windows-7-startup-repair-2.jpg]this screen[/url] is done loading.
Edit: it also shows [url=http://www.lytebyte.com/wp-content/uploads/2007/04/vista-default-boot-screen.jpg]this screen[/url] before going to black screen in startup repair, which is weird because I'm pretty sure that's the Vista loading screen.
Happened to me before. Turns out one of the RAM sticks is dead.
Try removing one of your RAM or replacing it.
Are you sure? Ubuntu runs fine. I'll do that memtest to see if my RAM's OK.
Are you running Ubuntu off a CD? If so, the hard drive might be going.
No, I have it set on dual boot together with Win7
RAM and HDD are working fine, I've tested it. While I was looking this problem up, I noticed most people who have this problem could fix it with a bootsect /nt60 all, so I'll try that. Will doing that screw up my grub boot system?
[QUOTE=Egonny;30025359]RAM and HDD are working fine, I've tested it. While I was looking this problem up, I noticed most people who have this problem could fix it with a bootsect /nt60 all, so I'll try that. Will doing that screw up my grub boot system?[/QUOTE]
bootsect will just create a new boot sector. Depending on your HDD config, it might mess up your bootloader if both operating systems are on 1 drive (why would you do that in the first place if its not a VM?).
Fixed it, there was something up with my Classpnp.sys file (in C:/Windows/windows32/drivers), so I searched it up and turns out all I had to do was set my BIOS back to default and then adjusting the boot order to the previous order.
Sorry, you need to Log In to post a reply to this thread.