Boot loop after dual booting ubuntu 14.04 LTS

I had an original version of windows 8 which worked properly.But after i dual booting with ubuntu windows takes about 10 to 15 mins to start and sometimes it gets stuck at the boot logo with nowhere to go
even ubuntu also shows there is a system problem.
Please help..

Anything plugged into the ports like an external hard drive? What AV program are you using? How about opening task manager and look at the processes once it boots up and see if anything looks strange in there, like a process running heavy.
Sorry for the late reply.
Regard,
Dave
T430u, x301, x200T, x61T, x61, x32, x41T, x40, U160, ThinkPad Tablet 1838-22R, Z500 touch, Yoga Tab 2 Windows 8.1, Yoga Tablet 3 Pro
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"!
If someone helped you today, pay it forward. Help Someone Else!
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество

Similar Messages

Z68a-gd65 boot loop after bios update using USB

Hi there,
My z68a-gd65 (G3) went into a boot loop after I did a bios update from a USB key that I installed using the latest BIOS version on the MSI site 7681vP8.zip
After the system restarted, it keeps booting up for 5 seconds and then shutting down, I removed all external devices and the Geforce GTX 550 Ti card and used the onboard card, but still no change...
Is there a way to set the board to factory defaults again???
Marcel

Hi there,
Maybe for others to solve the same problem, I found out what was the cause of this problem, I had a USB/Firewire card installed in the PC, after removing it the BIOS update could proceed from the USB stick as planned.
After the update though, my USB/firewire card can still not be installed back into the slot, because doing so will make the boot loop appear again, very odd!
Does anyone know why this new BIOS will not work with the card that has been inside my PC for 2 years???
Marcel

4404 WLC stuck in boot loop after upgrade

In prepping for the upgrade to 4.1.185.0 I've got two controllers at different sites stuck in a boot loop after applying 4.0.219.0. Units will not even get to the <ESC> option menu.
ANy ideas?

Did you clear the configuration on the controller by using Option 5 in the boot menu? This will corrupt the boot image. You should not choose the clear config (option 5) from the boot menu on controllers running 3.2.78.0, 3.2.116.21, 3.2.150.6 or 3.2.150.10, 3.2.171.5 or 3.2.171.6, 4.0.155.5 or 4.0.179.8 and 4.0.179.11.

My ipod is stuck in a boot loop after restoring

My iPod touch 4g is in a boot loop after restoring
It will boot up but 10 seconds later after the unlock screen it goes into the apple boot screen please help!!!

Try:
- iOS: Not responding or does not turn on
- Also try DFU mode after try recovery mode
How to put iPod touch / iPhone into DFU mode « Karthik's scribblings
- If not successful and you can't fully turn the iOS device fully off, let the battery fully drain. After charging for an least an hour try the above again.
- Try on another computer
- If still not successful that usually indicates a hardware problem and an appointment at the Genius Bar of an Apple store is in order.
Apple Retail Store - Genius Bar

P780 boot loop after factory reset

From couple of days ago I started to get popups saying "android ____ .com" or something and every time I clicked OK the message would pop up again not letting me press anything but the OK button continuesly.. so I powered off the phone I powered back up again and my phone wouldn't boot anymore. The screen said "Encryption Unsuccessful" and then there was a "Factory Reset" button right below - nothing happens when I clicked it So I went on and performed a factory reset by entering recovery mode (power button + volume up + volume down) and after it didn't work I went back to recovery mode and tried "clear cache" which didn't work so I then went to factory mode (power button + volume up) and cleared data by selecting MMC or something (it was in chinese) What happens next is, the phone enters a boot loop. It boots, shows the Lenovo logo, then turns off, then boots again, Lenovo logo, turns off, and so on. I wasn't even able to turn off the phone so I clicked that red reset button at the back I didn't try removing the battery or SD card How do I go from here?

I would like to add, whilst I was using the pin clips on the pins near the bios chip, I let the system run until it would beep. During this time, the CPU fan ran really really hard. Have I damaged the CPU somehow?

SYSTEM RECOVERY (F11) is inaccessible after dual-booting Windows 7 and Windows 8.

I dual booted Windows 8 with Windows 7 and now the RECOVERY partition (F is not loading upon pressing F11. It gives me the boot configuration data error. I have it marked as Healthy (Primary Partition) and I am able to access the files via. My Computer in both OS, but not through F11 System Recovery.
The bcdedit log is here: http://pastebin.com/b0Y5Hd1F
My partition letters:
C: Windows 7
D: Windows 8
F: RECOVERY
H: SYSTEM
In Visual BCD, One WRE is set to D: and the other is set to F:. Should i set both to F, which is the actual RECOVERY partition?
[2] The UEFI boot setup is unable to create HP_TOOLS parition because 4 partitions already exist. I don't remember having the SYSTEM partition earlier so maybe that repalced HP_TOOLS?
[3] When I try to create a recovey media, the orange circle filter keeps of going even after I have inserted the an external USB hard drive for it to detect. Does it usually take this long? I am guessing once the recovery media is made I could do system repair from there and get RECOVERY to work?

What is the p/n? Remove the battery and look for it. Post all alphanumeric characters.
CTO means configure to order. That means only you and HP know the notebook's configuration.
The problem you are going to run into is that there is a maximum of four primary partitions allowed by Windows. That is by design. It appears that you removed the HP_TOOLS partition, which was a requisite for the UEFI diagnostics.
Frankly it looks like what you will have to do is put the UEFI environment on a USB stick.
I would create the recovery media on a high quality 16GB USB drive.
The partition schema must be as follows:
1) C: (NTFS)
2) HP_Tools F: (must be FAT32)
3) RECOVERY D: (NTFS)
4) SYSTEM (NTFS) created by the Windows install process
I am not aware of a dual-boot or more schema that allows a UEFI environment with the Recovery Manager accessible from F11. I wish I had better news for you. Perhaps our forum Provost DavidPK knows how it can be done.
I do recommend that you copy the RECOVERY partition to an external disk for safety sake.
If you are able to boot into the recovery manager I strongly suggest that you create your recovery media. If you do not do that you will not have a copy of your operating system and drivers for a plan B. I did not go with the option you used and did not create problems to deal with later.
When I play around with my loaner notebook and configure it to dual/triple boot, I always install a different hard disk and put the original one aside. You can still return your system to its original configuration and then take the hard disk out and use another one to play with. I believe that would be the wisest path to follow.
****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
2015 Microsoft MVP - Windows Experience Consumer

Changing Boot Order on Dual Boot Windows 8 and Ubuntu

Hi there,
Recently got a HP Pavilion g6 2213sa which came with Windows 8 (spit!) and this disgusting UEFI BIOS replacement (double spit!).
Anyway, I need to dual boot Ubuntu on my system, so I installed Ubuntu. Normally, on a non UEFI system, a "Grub" bootloader installed by Linux would take over the startup process, and allow you to choose between either Windows 8 or Ubuntu on startup.
However, on this computer, startup is just booting straight to Windows 8 despite the fact that Ubuntu and Grub IS installed.
Now, upon startup, if I press F9, then I get to change the boot-device on a one-time basis. I can either select "OS Boot Manager", which loads Windows 8, or "Ubuntu" which loads the Grub bootloader which allows me to select Windows 8 or Ubuntu.
However, when I press F10 to enter the Bios Setup with the intention of changing the boot order permanently, the Ubuntu option isn't there. Instead it has OS Manager, USB Disk, CD Rom, USB CD Rom and Network Card.
Thanks, HP for, the crappily designed BIOS.
Anyway, can anyone PLEASE provide me a way of changing the boot order so that GRUB is loaded first and NOT this crap Windows 8 rubbish (that I would happily bin if I didn't need it for work).

There is the same problem in HP 2000 laptops (in my case specifically, HP 2000-2D22DX). I did some investigation using trial and error, and this is what I found out:
There is some sort of a "recovery feature" or so that on every boot sets the very first UEFI load option to point to one of the two locations, in this order:
\EFI\Microsoft\Boot\bootmgfw.efi
\EFI\Boot\bootx64.efi
This option is displayed as "OS boot Manager" (for the first path) and something akin to "UEFI partition" for the second path, completely ignoring the actual name given to it (when you look at the EFI variables through efibootmgr, you can see that what is displayed as "OS boot Manager" actually is set to the name "Windows Boot Manager"; why anyone would do such renaming is beyond me). If you try to change the boot order so that this slot isn't the first, the UEFI will overwrite the BootOrder variable on next boot and reset it to point to "OS boot Manager" anyway.
By default, both of the paths above contain the same Microsoft bootloader (if you check the md5sum of both, you'll see they match).
So, until HP releases an updated UEFI that allows turning this "feature" off or rearranging boot options through the F10 UEFI setup, this is what you can do to get dual boot with the least amount of hackiness:
In Windows, mount the UEFI partition (mountvol S: /S mounts it as the S: drive) and copy the file \EFI\Microsoft\Boot\bootmgfw.efi to use some other name (for example, I copied it to "\EFI\Microsoft\Boot\bootmgfw.efi~", but you can change the name to anything else).
In the Windows command prompt, update the Windows UEFI entry to point to the new name: bcdedit /set {bootmgr} path \EFI\Microsoft\Boot\bootmgfw.efi~ (adapt to your set name accordingly).
Optionally, change the name of the Windows boot loader so that you would be certain that it points to the new file location: bcdedit /set {bootmgr} description "Fixed Windows path"
Install the other OS. In my case the bootloader was installed into \EFI\opensuse\grubx64.efi.
Delete the two files, \EFI\Microsoft\Boot\bootmgfw.efi and \EFI\Boot\bootx64.efi.
Use efibootmgr to delete the "OS boot Manager" entry: sudo efibootmgr -b 0000 -B
Set the new OS bootloader to be the default bootloader by using efibootmgr with the -o option. In my case, I had an entry called "opensuse" in slot Boot0001 and the updated path Windows entry in slot Boot0002, so I had to do sudo efibootmgr -o 0001,0002
Update GRUB to point the Windows entry to your renamed file (you'll have to create a new file in /etc/grub.d and rerun grub-mkconfig).
And that's it, now the UEFI will boot GRUB by default (it won't regenerate the "OS boot Manager" entry since it won't be able to find either of the two hardcoded paths and will "fall back" to properly reading the BootOrder variable), and the F9 menu will still allow choosing to boot Windows directly.

Mac partition becomes laggy after dual boot windows 7

Hi all,
Last week I dual boot my Windows 7 again to make larger memory space for Windows partition. However after the dual boot, everytime when I first log in my Mac partition, it hangs and I need to restart to get it back to normal, Even though is back to normal, I still notice it takes longer time to open my documents compared to last time. I have roughly 10Gb for my Mac storage, I wonder is it because of the low memory space that makes this happens. Please advice!

Lack of harddisk space can indeed be the cause for the problems you have.
Have a read here http://www.thexlab.com/faqs/lackofram.html
Stefan

Windows 10 Upgrade infinite boot loop after reset

I did a Windows 10 upgrade on an old computer with these specs:-Windows 7 Pro- 64 bit-Dell Optiplex 755-4 GB RAM-Intel Core2 Duo processor Everything ran fine after the upgrade. However I wanted to do a clean install. So I did so and chose the option to not keep any files or programs. It went through the process and was stalled at 99% for some time. I let it run over night. I came back and looked at it about 16 hours later and the 99% was gone, but the "hourglass" was still going. I pressed Escape and then CTRL+ALT+Delete to try to get it to respond. Now it is stuck in an infinite boot loop. It will reboot and then after several minutes it brings up an error message of "Your PC ran into a problem and needs to restart...- Inaccessible boot device." Then it restarts and the loop starts over.I've tried booting into safe mode using F8, but...

These days, there are many ways to combine electronics. Custom gaming PC? No problem. Raspberry Pi arcade? Easy. GoPro on the hood of your RC car? Awesome!I thought up this combo, a tiny portable computer with a huge screenhttp://www.newegg.com/Product/Product.aspx?Item=0FC-001H-00017&cm_re=pico_projector-_-0FC-001H-0...http://www.newegg.com/Product/Product.aspx?Item=N82E16883400001&cm_re=compute_stick-_-83-400-001...What are some of your cool tech combos?

DROID in boot loop after OTA update

Just accepted the update today. After phone updated and attempted to reboot...its in a continuous boot loop. How can I stop it?

Try taking the battery out. If it still loops when you try to power it on, then the only other thing to try besides a factory reset is to take it to a verizon store and see if they can do anything.

KB300061 - Boot loop after isntalling

We are in an enterprise running Win 7 x64 on all of our workstations. Our updates are managed by WSUS, and we have an auto approval setup to allow critical and security updates to be installed. This morning, several of our workstations requested a reboot
to finish applying updates. Upon rebooting, many of them were stuck in a boot loop. Windows would attempt to load, it would then blue screen for a fraction of a second, then brought up the recovery menu. Here's what we've tried:
- Startup repair
- MBR repair
- SFC /scannow
- DISM (tried removing packages individually and rolling back)
- System restore (no restore points)
- wusa to uninstall packages by KB (catastrophic failure)
- Safe mode doesn't boot
None of what we knew to try worked. The one thing the computers stuck in the boot loop have in common is the model number. They are all HP Probooks, sharing the same model number. None of my other computers in the enterprise had trouble applying the updates.
I'm conflicted. Any advice or help would be appreciated!

Hi,
Please refer to my reply in another thread, follow the steps to troubleshoot your problem for test.
https://social.technet.microsoft.com/Forums/windows/en-US/3d9d948e-eaf9-43e0-92e7-bebb96cb6180/stop-error-0x7b-after-windows-updates-101410152014?forum=w7itproappcompat#73e3402b-c420-48c6-b2e7-b4a6a5be327c
Roger Lu
TechNet Community Support

MSI P67A-GD53 (B3) Boot loop after BIOS update

Hi,
I've just updated my BIOS to 7681v42 from an earlier version (can't remember which one exactly) and after the update I am stuck in a boot loop. The computer turns on for about 5 seconds or so and then switches back off, the CPU fan, motherboard fan & video card fan spin for a few seconds then power is cut.
I've tried booting up with nothing else connected (no vga, memory, hdd, empty USB slots) to no avail. I have tried resetting the CMOS as well but I don't get any further than the reset loop.
Can anyone suggest something? Is there any way to force the MB to use the backup BIOS?
Thanks in advance.

You can try doing this again with a single stick of ram or some different ram, but more than likely you will need to rma the board for re-flashing.

SG300-28 switch in boot loop after firmware upgrade

After performing a firmware upgrade on an SG300-20 switch from ver 1.1.0.73 to 1.2.5.70 the switch now boots up with the following error and resets:
30-Aug-2011 10:47:33 %L1Mngr-F-PARAMTOOLONG: csco-sb parameter %s is too long.
The attached file contains a full output of the console boot process.
I have tried loading different versions from the console, but all produce the same error.
Has any one any idea how to resolve this issue?
Thanks
Des

Hello Tom, Thanks for your reply,
I had done the process before with the 3 firmwares offered in the cisco website. I did it again, and i get a boot loop again, with following error:
%L1Mngr-F-PARAMTOOLONG: csco-sb parameter serialNo is too long.
Any ideas?
Thank you,
Nico
Console
     Startup Menu
[1] Download Software
[2] Erase Flash File
[3] Password Recovery Procedure
[4] Set Terminal Baud-Rate
[5] Stack menu
[6] Back
Enter your choice or press 'ESC' to exit:
Downloading code using XMODEM.
-- Download complete --
Calculating file's checksum...OK
Erasing FLASH ->>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Writing to flash 0x6aa500 records...
Setting checksum: 0x350925f6 , Address: 0x0
OK.
Flash programming success.
Perform WARM BOOT ...
Boot1 Checksum Test...............................PASS
Boot2 Checksum Test...............................PASS
Flash Image Validation Test.......................PASS
BOOT Software Version 1.0.0.4 Built 08-Apr-2010 16:37:57
Networking device with Marvell ARM CPU core. 128 MByte SDRAM.
I-Cache 16 KB. D-Cache 16 KB. L2 Cache 256 KB. Cache Enabled.
MAC Address   : 58:35:d9:96:7f:5d.
Autoboot in 2 seconds - press RETURN or Esc. to abort and enter prom.
Preparing to decompress...
100%
Decompressing SW from image-1
100%
OK
Running from RAM...
Board ID is 22
Device ID 0xdf5111ab
*** Running SW Ver. 1.2.7.76 Date 19-Jul-2012 Time 17:54:43 ***
HW version is V
Base Mac address is: 58:35:d9:96:7f:5d
Dram size is : 128M bytes
Dram first block size is : 101376K bytes
Dram first PTR is : 0x1900000
Dram second block size is : 4096K bytes
Dram second PTR is : 0x7C00000
Flash size is: 16M
19-Jul-2012 17:54:46 %CDB-I-LOADCONFIG: Loading running configuration.
19-Jul-2012 17:54:47 %CDB-I-LOADCONFIG: Loading startup configuration.
Device configuration:
Slot 1 - SF302-08MP
Device 0: GT_98DX1005 (AlleyCat)
-- Unit Standalone                --
Tapi Version: v1.9.5
Core Version: v1.9.5
19-Jul-2012 17:55:02 %L1Mngr-F-PARAMTOOLONG: csco-sb parameter serialNo is too l
ong.
***** FATAL ERROR *****
Reporting Task: ROOT.
Software Version: 1.2.7.76 (date 19-Jul-2012 time 17:54:43)
***** DEBUG *****
DEBUG LOG IS EMPTY
0x16a614
0x167054
0x6bdc18
0x490518
0x4959e4
0x495bac
0x815674
0x816b10
0x817e64
0x1d51e8
0x1cb010
0x121d3c
***************** SYSTEM RESET *****************

P67a-c43 boot loop after bios update

Last night, I attempted to update the bios on my P67A-C43 (B3) board using the version 5.1 bios. After the BIOS installed, it restarted and came up with the "all settings were reset to default values. press f1 to run setup. press f2 to continue" I hit f2 and my system keeps resetting in an infinite boot loop. I was able to reset the BIOS using the reset button on the back of the board to get back to the bios prompt, but pressing either f1 or f2 puts it back into the boot loop. Any help would be appreciated.

Quote from: ScunnyUK on 01-February-11, 16:08:59
Hi,
The blue screens started after a clean Bios flash to the 18b10 bios then eventually it stopped working complety (just doing the start up cycle over and over)
I had tried reseting cmos and it doesnt make a difference, the motherboard will not post , boot , start up at all so default settings cant be set (although reseting cmos would set to default anyway)
Each time the board goes through the start up cycle (i.e. upon pressing start button the board will start up with fans spinning for a second then shut down, start up again with fans spinning for a second then shut down, continuasly repeating until main power is removed) I have used a multimeter to measure the voltage read points on the board and they show that there is no vcore being suplied to the cpu but all other points show the voltage is being supplied to those componants, so imo that is where the problem lies and I would sugest that the other ppl who are having this issue to also try measuring the voltage read points and see if the same thing is happening on thier boards .
If others are getting the same results (no vcore) then the msi techs should be informed of this issue..(imo)
1.8b10 still is a beta bios. I got random bluescreens with that one also at some point a blinking bios led. So I flashed back from secondary bios (using the first option (change disable in enable)in "security" in the EFI shell to allow flashing from secondary bios), blinking bios led now stopped, Then I flashed with 1.7, no issues sofar cpu now running stable at 4.5Ghz (already 2 days).

[SOLVED] Boot loop after upgrade

Hi all,
When i try to boot arch, even in fallback mode, boot fail and go in loop.
loop happen just after the display of nvidia logo, then it try to do something (not showed in screen), it fail, and the nvidia logo is showen again.
I can't access to GDM, i can't turn off computer (have to remove battery from my laptop), i can't access to terminal/console/virtual console.
Last things i've made:
- full update system (pacman -Syu)
- changed /etc/environment adding this line (i was trying to solve tearing problem):
CLUTTER_PAINT=disable-clipped-redraws:disable-culling
CLUTTER_VBLANK=True
nothing seem to work
i've already removed the 2 added lines from another linux distro i've on the same computer, so i don't think /etc/environment is a problem here
don't know what to do and how to solve...
any hints?
thanks
Nico
Last edited by tracuboTL (2012-02-07 14:43:30)

I have exactly the same problem,
Did a full update with pacman.
I haven't updated with yaourt, because I had some problems and rebooted, but now I cannot access the terminal.
If I switch to tty1, I constantly switch back. Ctrl+Alt+Backspace is not enabled and I'm not sure it would work.
I've tried to only boot to runlevel 3, but gdm is in the daemons or I did something wrong because I boot into X again.
Anyone have an idea how to solve this?
Thanks
EDIT: solved it for me
Step 1: on boot let GRUB only boot to init 1
Step 2: change config files so not to start X
Step 3: reboot so you have networking support
Step 4: search in aur if you have a your own cairo package (pacman -Qm)
Step 5: rebuilt that cairo package
Step 6: start X
* step 2 and 3 are maybe not needed if you know how to get networking in init 1. Re;ember to undo the changes in Step 2 so X starts at boot again.
Last edited by tmske (2012-02-06 18:15:15)

Boot loop after dual booting ubuntu 14.04 LTS

Similar Messages

Maybe you are looking for