Manual img ok, multicast causes XP boot loop?

Weird,
our it-support reported that on two sites imaging using ZDM7 manual
multicast (from one machine to other machines) doesn't work anymore,
actual img sessions goes ok, no errors, but cloned machines goes into
Win XP boot loop.
When doing manual unicast img from server to same machines it works ok.
How can it be? Same data going, just a bit different way.
ZDM configs have been the same for a long time. Changes are just on the
image side, new software, size grown.
-sk

Sami,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

Similar Messages

MSI Install - Service Startup Causing a Boot Loop?

Windows 7
I created a service executable in C++ and made an MSI with InstallShield 2014. I added the needed runtimes for the service and go through the MSI install process. Service starts fine, works great, everything is behaving as expected.
I initiate a reboot to ensure the service behaves as normal.
After the reboot a dialog pops up (Presumed from MSI?) that a reboot is required again. Strange it didn't ask before the reboot, but clicking yes to this dialog shuts down the system.
On THIS boot up the system goes through the windows start up and is about to login to the user with the login screen appearing, but then suddenly the system reboots, and it will continuously do this.
Loading last known good configuration allows you to login again, but the same "Reboot REquired" dialog appears, and clicking yes restarts the boot loop failure.
How can I tell what is happening that is requiring the reboot? How can I debug what is causing windows to suddenly shutdown and reboot?
If I install everything and never tell the MSI to start the service, everything is fine.
As for the service itself, it literally just connects up to SCM and does little else. It's basically a framework to actually fill in the functionality.
Hoody Hoo!

Hello RevenantCoder,
For issues regarding InstallShield 2014, it is beyond the scope of our support, you could post it to:
https://community.flexerasoftware.com/forumdisplay.php?133-InstallShield
Thanks for your understading.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

10.9.1 Update Sent My MacBook Pro Into Boot Loop

Like the title says, I updated to 10.9.1 and it sent my MacBook Pro (13" Early 2011 i5 16GB RAM 1333MHz) into a Kernel Panic and/or Kernel Trap which resulted in my system being stuck in a boot loop!
While I'm already dealing with another issue regarding Mavericks on my laptop this was the last thing I needed to happen! What I ultimately tried was booting into Safe Mode (hold down Shift immediately after you hear the boot chime), and clear out my ~/Library LaunchAgents folder and my /Library LaunchAgents and LaunchDaemons folders. While it knocked my computer out of the boot loop, it didn't solve my other issue.
Anyone have any ideas why 10.9.1 would cause a boot loop?
Just wanted to share this info with anyone in case they're concerned about upgrading to 10.9.1.

Uninstall Trusteer Rapport. Your Mac cannot operate properly with it installed.
Be sure to follow its uninstallation instructions, and do not use any so-called "cleaners" or "zappers" to uninstall it.
Uninstalling Rapport on Mac OS X
You should back up your system prior to making any changes. Is there a reason you are not using Time Machine?
May I suggest that you review the following setting in System Preferences?
Although you may easily override that setting, it will serve to protect you from inadvertently installing garbage.
Update to OS X 10.9.4 using the App Store. Install all Apple updates. Your report indicates you are still using an earlier release.

MSI GX70 and SSD causing boot loop

Hi,
I've bought the MSI GX70 laptop 2 weeks ago which suits my needs pretty well.
It does seem to have some issues with SSD, not sure if they are known issues yet...
Powering up the laptop results in a boot loop 9 out of the 10 times. As soon as it passes the POST it reboots instead of starting Windows.
If I remove the SSD from the second slot (the only one that is available next to the existing HD) it boots from the stock HD fine, no issues.
As soon as I install the SSD again, it's starting to loop again.
So I thought, let's replace the stock HD with the SSD (switch connectors) but it doesn't even recognize the SSD disk as bootable device if I do so.
I'm sure the boot order and settings are fine, played around with them to be sure.
There is a workaround to get the system started.
While the laptop is in the boot loop (starting up, showing the MSI logo and doing that over and over again) you have to keep pressing the DEL button to enter the bios, hit escape to quit the bios once you're in without changing and saving anything and it boots up Windows fine.
The SSD is a PNY XLR8 120gb
I'm sure the HD is fine because it came out of the previous laptop without issues.
Any thought on the above?
Thanks
/Nick

I guess my real question here is are you 100% certain that at this very second, the SSD is in fact 100% ok? I'm only asking as after reading a few reviews, almost 50% of them (granted, they are reviews, and people usually really only review things when they are bad...) were showing that they had to return this very SSD because it went bad.
That's really the only thing that comes to mind. This uses the very common Sandforce chipset that quite a few SSD's have and work perfectly fine with. So I can't really comment more than that.

Boot Loop Grey Screen - Flashed Image File on Startup Disk

My computer is a boot loop thanks to my really stupid error using Terminal. I was trying to flash an OpenElec image on a USB drive but I accidentally flashed it on to my startup disk, disk1, which caused some major issues. here is the link to what I was trying to do: http://wiki.openelec.tv/index.php/HOW-TO:Installing_OpenELEC/Writing_The_Disk_Im age#tab=Mac_OSX
Instead of writing it to disk3, I wrote it to disk1 using this command : sudo dd if=OpenELEC-Generic.x86_64-5.0.0-efi.img of=/dev/rdisk1 bs=4m
Repair Disk does not work, I don't have a backup so I can't just reinstall the OS X without losing all my data? I tried using Target Mode, I able to view the HD on another Mac but all my photos are in a iPhoto library (120GB) which cannot be opened or copied due to Error -36. I tried importing the file into iPhoto on the Target Mac but get an error that iPhoto disk is full. We cleaned the Target Mac iPhoto library completely. The photos are the last 10 years of our life so we cannot lose them.
Is there a way to remove the image that I installed on the HD via Terminal so it will start up again? Can I somehow Target Mode transfer the photos onto to another Mac?
Please help me!
line 1: /dev/disk0: Permission denied
/Volumes/Cruzer/Terminal Saved Output: line 3: 0:: command not found
/Volumes/Cruzer/Terminal Saved Output: line 4: 1:: command not found
/Volumes/Cruzer/Terminal Saved Output: line 5: 2:: command not found
/Volumes/Cruzer/Terminal Saved Output: line 6: 3:: command not found
/Volumes/Cruzer/Terminal Saved Output: line 7: /dev/disk1: Permission denied
/Volumes/Cruzer/Terminal Saved Output: line 9: 0:: command not found
/Volumes/Cruzer/Terminal Saved Output: line 10: 1:: command not found
/Volumes/Cruzer/Terminal Saved Output: line 11: 2:: command not found
/Volumes/Cruzer/Terminal Saved Output: line 12: /dev/disk2: Permission denied
/Volumes/Cruzer/Terminal Saved Output: line 14: 0:: command not found
/Volumes/Cruzer/Terminal Saved Output: line 15: Logical: command not found
/Volumes/Cruzer/Terminal Saved Output: line 16: 5843C88A-1AEE-455B-AA12-1B9017FBE610: command not found
/Volumes/Cruzer/Terminal Saved Output: line 17: Unencrypted: command not found
/Volumes/Cruzer/Terminal Saved Output: line 18: /dev/disk3: No such file or directory
/Volumes/Cruzer/Terminal Saved Output: line 20: 0:: command not found
/Volumes/Cruzer/Terminal Saved Output: line 21: /dev/disk4: No such file or directory
/Volumes/Cruzer/Terminal Saved Output: line 23: 0:: command not found
/Volumes/Cruzer/Terminal Saved Output: line 24: /dev/disk5: No such file or directory
/Volumes/Cruzer/Terminal Saved Output: line 26: 0:: command not found
/Volumes/Cruzer/Terminal Saved Output: line 27: /dev/disk6: No such file or directory
/Volumes/Cruzer/Terminal Saved Output: line 29: 0:: command not found
/Volumes/Cruzer/Terminal Saved Output: line 30: /dev/disk7: No such file or directory
/Volumes/Cruzer/Terminal Saved Output: line 32: 0:: command not found
/Volumes/Cruzer/Terminal Saved Output: line 33: /dev/disk8: No such file or directory
/Volumes/Cruzer/Terminal Saved Output: line 35: 0:: command not found
/Volumes/Cruzer/Terminal Saved Output: line 36: /dev/disk9: No such file or directory
/Volumes/Cruzer/Terminal Saved Output: line 38: 0:: command not found
/Volumes/Cruzer/Terminal Saved Output: line 39: /dev/disk10: No such file or directory
/Volumes/Cruzer/Terminal Saved Output: line 41: 0:: command not found
/Volumes/Cruzer/Terminal Saved Output: line 42: /dev/disk11: No such file or directory
/Volumes/Cruzer/Terminal Saved Output: line 44: 0:: command not found
/Volumes/Cruzer/Terminal Saved Output: line 45: /dev/disk12: No such file or directory
/Volumes/Cruzer/Terminal Saved Output: line 47: 0:: command not found
/Volumes/Cruzer/Terminal Saved Output: line 48: /dev/disk13: No such file or directory
/Volumes/Cruzer/Terminal Saved Output: line 50: 0:: command not found
/Volumes/Cruzer/Terminal Saved Output: line 51: /dev/disk14: No such file or directory
/Volumes/Cruzer/Terminal Saved Output: line 53: 0:: command not found
/Volumes/Cruzer/Terminal Saved Output: line 54: /dev/disk15: No such file or directory
/Volumes/Cruzer/Terminal Saved Output: line 56: 0:: command not found
/Volumes/Cruzer/Terminal Saved Output: line 57: -bash-3.2#: command not found
logout
[Process completed]

Install OS X Using Internet Recovery
Be sure you backup your files to an external drive or second internal drive because the following procedure will remove everything from the hard drive.
Boot to the Internet Recovery HD:
Restart the computer and after the chime press and hold down the COMMAND-OPTION- R keys until a globe appears on the screen. Wait patiently - 15-20 minutes - until the Recovery main menu appears.
Partition and Format the hard drive:
Select Disk Utility from the main menu and click on the Continue button.
After DU loads select your newly installed hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Click on the Partition tab in the DU main window.
Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Click on the Options button, set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the process has completed. Quit DU and return to the main menu.
Reinstall OS X: Select Reinstall OS X and click on the Install button. Be sure to select the correct drive to use if you have more than one.
Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.
This should restore the version of OS X originally pre-installed on the computer.

Z68A-GD80 B3 Boot Loop and Failed BIOS LED Flashing

I've been having "boot loop" issues with my system since it was built in June. Basically, when the system is powered on the lights/fans come on for around 3 seconds then it shuts itself off for another 3 seconds and repeats the loop infinitely. Meanwhile there are no POST code beeps and nothing shows up on screen. I also noticed today that the Dual BIOS control LED is flashing during boot loops indicating that the primary BIOS has failed.
As this was my first build in quite a while I didn't initially worry about it too much, figuring that it was probably just a BIOS setting or improperly seated hardware issue. Shortly there after my son was born and needless to say there wasn't a whole lot of time to trouble shoot a PC for a couple of months. Fast forward four months later to today and the boot looping is driving me nuts. It seems to occur when the system has been powered down overnight and more frequently if the reset button is used. I've read a lot of stuff saying that the Gigabyte boards are prone to this issue, but can't find anyone else with the same issue on a MSI z68 board. I've check/done the following to try and trouble shoot the issue.
1. Flash to BIOS 17.3 (twice)
2. Installed system speaker to hear post codes. Got a whole lot of nothing.
3. Installed one stick of RAM in slot one. Tried all four sticks. Nothing works.
4. Set BIOS values to default.
5. Tried disabling and enabling XMP profiles for the RAM.
6. Upped the voltage on the RAM to 1.5V, since the board reports an under-volt around 1.48 on auto. No effect.
7. Disabled PLL overvolt.
8. Enabled VDroop (still not clear on what this is).
9. Removed both video cards and used the on chip video. No effect.
10. Unplugged all USB devices.
11. Tried XMP enabled and disabled for the memory.
12. Hard drive plugged in and removed makes no difference.
13. Bare system with only one stick of RAM installed, no difference.
11. Lots of other crap that I can't think of right now.
Any help would be great as I'm at a loss here.
System specs are as follows;
Intel 2600K
Corsair H50 Cooler
MSI z68a-gd80 B3 with BIOS v 17.3
PNY Geforce GTX 560 Ti (2x in SLI)
Linksys Wireless G PCI card
Crucial Ballistix Sport RAM (4x2GB at 1600 MHz XMP enabled)
Segate Barracuda 7200 RPM Drive 500GB (2x in RAID0)
OCZ Vertex2 64 GB SSD as system cache
Corsair TX750 Power Supply
Corsair 600t case

More wierd stuff.
I couldn't get the board to boot without looping last night, tried the usual unplugging and clearing the CMOS nothing. Boot loops at every turn.
I wonder if maybe I've got some bad pins or a poor connection on my RAM slots. I removed the RAM and began testing one by one. First stick gave a boot loop. Second stick worked. On restart the BIOS LED wasn't flashing anymore, which is odd since I hadn't yet set the BIOS fix feature to enabled. I powered down again and put my RAM back in, set my BIOS settings as suggested, and then clocked the RAM to 1333MHz. Seemed stable last night through a number of restarts.
As for the backup BIOS reporting v 17.3. Yeah, that is odd. The manual says it can't be flashed either. Maybe BIOS just reports what the primary version number is no matter which chip (primary or secondary) is actually active and being booted from?
I'd like to think this is over, but I'm sure when I go home and power up I'll get another boot loop. I'd rather not be without a PC for a couple weeks, but I may just have to RMA so I don't have to deal with this anymore. It's quite frustrating to have fiddle around for 10+ minutes to get your PC up and running, plus with a RAID0 setup and SSD cache I'm just asking for a system failure with all these power on/off cycles.

Ipod Stuck in "boot Loop" and itunes says I'm not connected to the internet.

Aright well I'm having a huge problem fixing my ipod.    Let's start at the beginning, i wanted to put new music onto my ipod but itunes wasn't detecting my ipod, it said i have to restore my ipod to factory settings, so i manually did it from the ipod it's self.   When it started to boot up again it just froze at the apple logo. and the loading wheel is stuck. after some research i found out that its called "boot loop" and the only way to fix this is to restore it from itunes itself.
sounds simple enough, so i go ahead and connect the ipod to itunes and try to restore it (via DFU mode) The restore wont happen because it says im not connected to the Internet, when clearly i am.      So in a nutshell..   in order to restore my ipod.. i need to get itunes to recognize that I'm connected to the Internet.
I've done everything i can think of,   make sure my firewall isn't interfering and itunes is enabled. The Internet proxy is what it needs to be. Ive uninstalled and reinstalled itunes.   I actually chatted with a apple tech and he couldn't seem to help me out.
If anyone can help me or has been in this situation and know's exactly what to do.   please let me know.. it would be greatly appericated

That was the first thing I tried..what the site told me, but its still telling me I'm not connected to the internet when I am. Should I just delete everything by hand. Like I said I wanted to take it back and upgrade to the 80 gig ipod.

Windows 2008 Server boot loop and unable to log on in Safe mode

The Situation: I used msconfig to reboot Windows 2008 Server r2 into safe mode. On rebooting, boot progresses ok and the log in screen appears very quickly, then disappears and the machine reboots. I've tried typing the password very quickly and whether
I get it wrong or just can't get enough typed in time, I don't know, but the reboot loop continues. So, i can't log on and can't change safe boot back to normal.
I know Server 2008 uses bcdedit and no longer has a boot.ini, so I don't know if it is still possible manually to amend a boot file so it starts in normal mode again. Can anyone help me to break out of this boot loop without having to resort to anything
major, such as reinstallation?
Just to make clear, I haven't updated the system and the only change made was with msconfig to require safe boot on restarting.
Thanks

from the safemode try this syntax
Syntax: bcdedit /deletevalue {default} safeboot
http://technet.microsoft.com/en-us/library/cc721886(WS.10).aspx
http://www.virmansec.com/blogs/skhairuddin
How on earth is that a good answer? Sorry for the necrosis here of bringing up a post 9 months later, but I just ran in to this issue again. The OP said that he was STUCK IN A BOOT LOOP having placed himself in SAFEMODE already.
How is he supposed to type this in if he can't log in?
What worked for me was to keep striking F8 like a cobra during boot and telling it to use the Last Known Good Configuration option, after the 4th autoreboot, it let me log in and let me switch it back out of the safe mode and back to the normal boot. Yes,
I am aware this is quite lucky and now I don't have to rebuild all my server set up, and that your mileage may vary here, but, keep trying, you might be lucky.

Droid Razr M Red Eye Boot Loop--continues for TOO many customers, need help!

Droid Razr M problem with red eye boot loop--with ALL of the many posts that can be found online concerning this problem, why is there not a FIX from Motorola and/or Verizon? All I seem to get are suggestions (I've tried) and "device is now considered out-of -date, you need a new phone". Why should I purchase a new phone when I will have another issue in 2 yrs to cause me to purchase again? Amazing how I am back to the 3G Droid Razr X to make due--It is about 5 yrs out-of-date. Support with phones that are out-of-contract is ...well, pretty much non-existent. Motorola gives the same "run around" after a 1 hr. call. Verizon chat tech were helpful/nice but I was sent to motorola when answers could not be found...useless call transfer/number. Any help for this Verizon faithful customer other than spend more $ for another phone?

Factory data reset is all that you can try really. If that does not repair the issue, then the software or hardware might really be at fault, and a repair would be necessary.

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

Iphone 4 & 3gs on ios5.01 in a boot loop

Having both an iphone 4 and 3GS (neither are jail broken) in the same fault being stuck in a boot loop following nothing in common with either phone in relation to an application causing the issue.
I commenced in removing some application to see if that would make a difference, as the loop cycle was too fast t back the device up but that made no difference.
I then removed some pictures from both devices and well what do you know they have stopped looping and are back up and running correctly.

Hi,
The state of the computer/s memory is irrelevant to this issue even though there is no shortage on either memory or disk capacity.
How-ever the issue was resolved by removing a number of images/photos and videos from the iphone 4 & 3GS.
I do hope that this resolution can help others, and that the possible limitation issue of the devices for the storage of images and videos can be looked into as it clearly did cause an issue for the users, and I am a strong believer in finding the cause rather than re-building devices; as that does not give an answer in removing the issue in the future.
I hope this heps.

MDT 2012 Win7 x64 capture fails - boot loop

Hi everyone,
I'm pretty new to MDT and having a problem capturing a Win7 x64 reference image.
It seems to start out fine doing the Sysprep and so on, but then it has to restart the computer and after that it goes into a boot loop. After this, I have been forced to format and reinstall Win7 on the computer. This picture shows what it loops through
in about 20 seconds - and it shows nothing else than what's on these pictures :)
www.jaded.dk/boot_loop.png
I have been Google'ing alot, but can't find any post with the same issue, since most other get an error msg which I dont.
Here is some info about the setup.
I'm deploying the task sequence locally using these commands:
net use * \\mdtserver\DeploymentShare$ /user:domain\username
cscript \\mdtserver\DeploymentShare$\Scripts\LiteTouch.wsf
Server running MDT 2012 U1 - Win server 2008 R2, 64 bit
The laptop on which i'm trying to capture the ref img is a HP Elitebook 8470p. It is fully patched with windows updates and I have installed a few apps like Office 2010, flash player, reader etc.
The "Rules" on my MDT Workbench is like this:
[Settings]
Priority=Default
Properties=MyCustomProperty
[Default]
OSInstall=Y
SkipCapture=NO
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerBackup=YES
SkipBitLocker=YES
SkipTimeZone=YES
SkipLocaleSelection=YES
InputLocale=0406:00000406
KeyboardLocale=0406:00000406
KeyboardLocalePE=0406:00000406
SystemLocale=0406:00000406
UILanguage=0406
UserLocale=0406:00000406
My task sequence looks like this:
www.jaded.dk/task_seq.png
I don't know where to find a log of the capture, to get a hint of what has gone wrong.
Hope you can help me out here :) And please let me know if you need more info.
Thanks
Morten

Thank you both for answering.
ccatlett_sogeti:
I didn't seem to have Windows Deployment Services installed on my server. I just installed it and added WinPE boot files as bootimage according to this guide: http://blogs.technet.com/b/manojnair/archive/2011/11/23/exploring-mdt-2012-beta-2-part-6-of-10-integrating-mdt-2012-beta-2-with-windows-deployment-services-wds.aspx
Is that correct?
Keep in mind that I don't use PXE at the moment, if that makes any difference :)
David:
I will try to add SLShareDynamicLogging. I set it like this - hope it's correct:
SLShareDynamicLogging =\\MDTSERVER\DeploymentShare$\Logs\%ComputerName%

For Those Experiencing the Infinite Boot Loop on P67A-GD65

My story in a nutshell - bought the original (non B3) P67A-GD65 from Newegg on the first day it was available along with 8 GB (2X4 GB) Corsair Vengeance DDR3-1600 ram and Intel i5 2500k processor. Received the items, hooked them up on a test bench (rubber mb supports so no grounding issues) along with a Corsair VX-550 P/S (both 24 pin and 8 pin leads plugged in), GTX-460 video card (2 PCI-E 6 pin connectors plugged in), the default Intel i5 heatsink and a known good USB KB and mouse. Promptly experienced the infinite loop boot issue others have described - fans on h/s and video card spin up, 1st APS LED lights for a fraction of a second then all 6 light up for 3 to 4 seconds then APS LEDs go out and fans on h/s and video card spin down. No beeps from speaker and no video signal to monitor. After everything has stopped spinning (about 3 to 4 seconds), the power comes back on and the cycle repeats exactly the same way every time until I turn off the power supply. Here is what I tried:
1. Used only 1 stick of ram (tried in all 4 slots)
2. Pulled 1 stick of DDR3-1600 ram from my working X58 system (again tried in all 4 slots)
3. Different power supply (OCZ 520-ADJ)
4. Known good PCI video card instead of GTX-460 (in case there was some problem with power draw)
Under each of these changes, the same infinite boot loop occurred. Called tech support, they walked me through each step I had already tried and finally suggested I RMA both the MB and the CPU to Newegg. Did so and the replacements worked fine from the start.
Then came the B2 stepping issue. Notified both Newegg and MSI that I had one of the B2 boards. Newegg notified me they had the new B3 boards in stock. Arranged for cross shipment where they would ship me the new board and then I would return the old one. Received the new one last Friday. Put it on the same test bench as above and the same infinite boot loop is now happening on the new B3 stepping board. Just to test, put the cpu, ram and GTX-460 video card back into the B2 stepping board and everything works perfectly.
Another test, since some people reported the infinite loop problem when they had failed to plug in the 8 Pin power lead to the mb, I unplugged the 8 pin connector on the working B2 stepping board. The infinite loop problem is entirely different in this case. When you press the power switch, the fans start to spin and the first LED lights for less than a second. Then the LED goes off and the fans start to spin down. After everything has stopped, it repeats until the power supply is turned off.
This is my first MSI motherboard after 15 years of Abit and Asus with the occasional Gigabyte or EVGA thrown in and I am not happy with the QC I have experienced with this board!
So to summarize, 2 of the 3 P67A-GD65 boards I received from Newegg have had this infinite boot loop problem. Apparently, I have to RMA again. Am I lucky or what???!!!
Monte

Quote from: BMSliger on 16-March-11, 00:05:11
If it was the chipset causing this problem, it seems it would be a widespread complaint among all vendors. I have looked at the Asus and Gigabyte boards and do not see this particular problem described and certainly not multiple users reporting the same problem. I am giving up on this and will arrange an RMA and will see if I can talk Newegg into an Asus board for only the price difference. MSI has a very good reputation in the industry, but it has been a disaster for me!!!
Thanks for your replies,
Monte
Frankly, I can understand your frustrations on the problem but it is not fair to judge a brand by looking at the number of complains in a forum. I can guarantee you, there are more RMAs out there from all other manufacturers even before an user even knows that a Forum ever exist for them to post for enquiry and most of them aren't an IT engineer or hardware engineer by self.
If you want to compare, I have also been in this industry for more than 15 years and I have many DOA boards from other manufacturers as well and DOAs after RMAs are common to me. When you handle thousands of PCs, laptops and mainframes, such things are really common.
Back to your problem. Maybe I didn't make it clear on how I want to describe on my previous post for your issue in words. I am referring to having a chance to let the system boot into BIOS or past BIOS after multiple times of rebooting, then you can try to flash the BIOS. This is also not uncommon as I have encountered systems which are problematic but are able to boot into Windows after 15 to 20 times of infinite reboots by itself.
How about processor? Tested it in another system yet? Or is this another unless suggestion to you?

My iPad is in a boot loop. Can't use itunes.

Today my iPad went into a boot loop. I don't know the cause as I wasn't in at the time but it's possible one of the kids tried to update or something, however I just don't know.
The screen blinks from the apple logo to the lockscreen and is totally unresponsive. The only time it is in any way responsive is immediately after a reset after which I can swipe to unlock, enter my pin, and see the home screen for about 1 second, then the boot loop begins and it is unresponsive.
I can't use itunes to restore. When I connect to iTunes it asks if I want to use the computer to manage the iPad (it's never asked me this before). After I click continue I get a message telling me to respond on the iPad. I can't because it's in a boot loop and unresponsive. Even if I try connecting to itunes after a reset I can only get as far as the homescreen, where I can see the option to "trust" my computer but cannot actually press it. Then the boot loop begins.
I've tried connecting to itunes while pressing the home button but that doesn't work either.
What other options do I have?

Hi J_Constantine,
Welcome to the Apple Support Communities!
I understand that your iPad is restarting and not responding sporadically. You have already attempted some great troubleshooting steps and I think you are on the right track. Holding the home button is one step that you take while placing your device in recovery mode to restore. This is the method that I would suggest to restore. For complete information on how to place your device into recovery mode, please reference the attached article.
If you can't update or restore your iPhone, iPad, or iPod touch - Apple Support
Best regards,
Joe

GT780DXR Random Boot Loops

I have a MSI GT780DXR that is randomly going into a boot loop. The laptop will run fine for 2-8 hours most times then it will restart and get to the windows login screen and reboot again and sometimes will only get to the windows loading screen and reboot but this is as far as it gets and just keeps rebooting. The CPU/GPU temps when reboot happens: Idle/Load CPU: 40-60c GPU: 45-70c so I do not believe it is heat related. I have tested the RAM,HDD,CPU and drivers, parts tested by replacing with other working parts and drivers with clean installs and testing with each driver. The problem also occurs in linux so it's not related to Windows. I ran a live linux for 6.5 hours with no reboots and then started a game and within 30 min the reboots began yet during a test the day before I was able to game for 8 full hours before the reboots started yet I have also had them start as early as 10 min after turning the laptop on for the first time that day. So the reboot loops are very random and the only hardware I have not tested is the GPU and motherboard due to cost of the components.
Any advise would be helpful.

Quote from: nicolai.madsen on 22-March-15, 17:17:04
UPDATE: When my laptop had a random reboot last night, I noticed something. I have a cooling-fan-stand that my laptop is hooked up to. This runs on USB power straight from the laptop. (before you ask, the laptop does random reboots whether this stand is hooked up or not. I've also had this cooling-fan-stand for 4 years, so it's not the source of the issue.) BUT I noticed that when the laptop rebooted, the on/off light on this cooling-stand didn't switch off. So there MUST have been power running through the laptop the whole time.
I really don't know what's causing this. Maybe there wasn't enough power to run the laptop, so it restarted, but there was still enough power to run the USB-cooling-stand? That seems odd.
It won't need much power to drive a USB cooling pad. If you shut the system down and still the cooling pad is running, then it only means the system still provides power for the USB port after system is off and by this design, it drains the battery power and what you might lose is the battery life. But I cannot be sure this will be the cause of the reboot problem.

Manual img ok, multicast causes XP boot loop?

Similar Messages

Maybe you are looking for