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.

Similar Messages

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/

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.

Installing ram boot loop

I got recently 16 gb of ram and I installed 12 gb fine in DIMM 2,3,4 but when I put ram in DIMM slot 1 then no display comes on and pc is in boot loop And if i remove from DIMM 2 ram and put in DIMM 1 then the pc boots fine with only 3 sticks of ram. All rams are good and all slots are fine aswell No issiues in ram slots nor the ram. So how do I get the bios to recognize and boot my pc with 4 sticks of ram ? EDIT: Basically what im saying is i cant use 4 ram sticks but only 3 if i put fourth one in then the pc will go in boot loop with no display
My motherboard is B75A-G41 and yes all pins on cpu part are straight. Ram model is ASint DDR3 4gb-1333 SLA302G08-EDJ1C 1233

Board: MSI B75A-G41
BIOS: Newest Available
VGA: ati radeon hd 7750 1gb gddr5 OC
PSU: generic one with 80+ bronze cant remember company name
CPU: Intel pentium G850 2.9ghz dual core oc 3.1 ghz
MEM: 4x ASint ddr3 4gb-1333
HDD: 500 gb samsung 7500rpm hdd
OS: Windows 8.1 64bit and windows 7 64bit
CASE: old early 2000 case for nostalgia :3
EDIT: also tried the cmos reset 2 times already and trying all rams individually was the first thing i did. I remember when i modified the timmings in bios then the pc started fine but didnt recognize 1 and 2 slots and when i changed the mhz to 1066 then again all started fine but didnt just recgonize the 4th stick in dimm 1
2nd EDIT: If it turns out i cant get them 4 rams running so is it okay to have only 3 sticks in pc?

Boot Loop Issues - MSI Z77A-GD65 - Solved

Picked myself up an MSI Z77A-GD65 as well as some Kingston 2x 4GB RAM sticks with a i5 2500k.
After getting everything installed, it just boot-loops on me showing me no boot menu, with a debug code of 55.
If I take out one of the RAM sticks and just use the #2 slot, it boots fine (but after starting windows, it flashes some blue screen and it boots again. I'm thinking that's only because I haven't installed any drivers and still have the old drivers from my motherboard. Yes/No?).
But as soon as I put the second stick in, it will not boot (swapped sticks and it boots fine with one stick). I've tried 1/3 and 2/4 and the only slot that seems to work is #2 (#4 slot won't boot with one stick in it). Tried each stick in each slot. 1/2 work, but 3/4 will not
I'm guessing this isn't a RAM issue but a MOBO issue? I sense an RMA in my future....

Quote from: XFM on 24-December-12, 08:29:56
Can you take a good quality, in focus hi-rez picture of the socket and post it so we can see what you are talking about?
I would if I could. Best way I can describe it is that the pins are all kind of bent at an angle (imagine an L shape, but upside down). Now take the bottom of the L (where it's small and turns) and kind of bend that facing the ceiling. It's kind of like that...
Quote from: Froggy Gremlin on 24-December-12, 08:30:08
Why is this thread in the Intel duo/quad section?
What are the amps on the PSU +12V rail(s)? And how old is it? Suggest to keep just the one RAM stick in the primary DIMM slot and do a fresh OS install with the Mode set to AHCI. BTW, what is the OS? 32 or 64 bit?
Good question. I think I was very tired/annoyed when I made this, and I guess I didn't look properly. If any mods can move it, or need me to take it down, I can.
PSU - http://www.newegg.com/Product/Product.aspx?Item=N82E16817703005
I don't have a problem doing a fresh install, but would like to make sure it's nothing else before hand. If I do a fresh install, and I still have to RMA the board, I would have to do another one to put all my old stuff back in, and I wouldn't really have a PC until the new board came (I mean I could still use it, but would have to re-install stuff and it seems like a bit of a pain if I don't *have to).
64-bit OS

R4870-T2D512 - installing the driver causes vista to stop booting

Hi,
I have a gigabyte ep45-ds4p motherboard with R4870-T2D512 video card and 4 GB ram and raid mirror 500GB HDD
I have tried the CD driver, the driver from MSI and the driver from ATI.
after installing, the PC will not boot except for safe mode.
argH!
what to do???
thanks
b

Read >>Posting Guide<<

Boot loop when installing os x 10.10.2 from os x 10.6.8

I've been trying to install OS X Yosemite (v10.10.2) on my 17 " Mid 2009 Mac Book Pro with OS X Snow Leopard (v10.6.8) for the last four days. The upgrade downloads from the App Store without issue but gets caught in a continuous "boot loop" (i.e. restarts continuously) during the last stage of the installation process (i.e. grey screen with an apple logo and loading bar below it). My macbook pro is clean, virus free and meets all of the software upgrade requirements (4GBs RAM, more than 8GBs of HD space available, verified Apple ID/I Cloud Account,10.6.8 or later OS X Software, etc.). I have contacted chat support and made the corrections that were suggested but the installation boot loop continues to stall the installation process. What can I do to solve the challenges I've experienced with the installation process?

Eric,
Many thanks for responding to my query. About this Mac contains, OS X Utilities 1.0 (216). Reinstalling Yosemite 10.10.2 does not help so I just end up restoring 10.6.8 from my time machine back up. I have tried reinstalling 10.10.2 and Repairing my Mac HD from Disk Utilities a number of times only to end up back at the same gray apple screen with the loading bar getting half way before macbook pro just restarts itself over and over again. Ughh... frustrating!

Installed and used SL but now in a boot loop

After installing SL last night and using it all evening, and having it on this morning I've just come to turn my MacBookPro back on and it's in a boot loop not getting to the point where I can enter my password to login. The colour profile kicks in by changing the blue on screen but then it seems to reset back a point with the spinning dots and repeats forever.
Have mounted via my iMac and all seems ok with the HD, running in single mode hasn't made any difference.
Any ideas/solutions for this?

Yes, tried all the usual things but nothing seems to resolve it. To add to the description, the boot gets past the apple logo and you can see the colour blue screen change as the colour profile is loaded but then after a second the circle dots comes up for a few seconds and then the screen resets the colour profile to the original first boot light blue and starts the cycle again, changing the colour profile to a different blue (so two shades of blue, first load blue, then colour adjusted blue) then a pause with the circle dots then change the colour profile again, repeat until bored.

MSI Z68A-GD65 (G3) Boot Loop

Hello all,
I purchased a MSI Z68A-GD65 (G3) and when I started up it goes into a boot loop. I can't see anything on the screen.
Setup
- Motherboard MSI Z68A-GD65 (G3)
- Intel Core i3 Ivy Bridge 3220 3.30GHz 3MB Cache LGA 1155 55W Dual-Core Processor
- Kingston ValueRAM RAM Module - (2 x 8 GB) - DDR3 SDRAM - 1600 MHz DDR3-1600/PC3-12800 - Non-ECC - Unbuffered - CL11 - 240-pin DIMM
- COOLER MASTER Elite Power 400W OEM 20+4 pin & 4+4 pin ATX 12V V2.31 12cm fan Eco-friendly Reliability Quiet Noise Filter 70% efficiency
BIOS stated in the green labels below the "MSI" Heatsink is: E7681 IMSN10.
I tried another PSU and had the same issue.
Anybody can help me? Thank you very much for your time!

Your mainboard does not support an Ivy Bridge processor with the current bios that's why it doesn't come up. It needs a P series bios (7681vP1 and above).
There is no other way than to use any Sandy Bridge cpu to flash bios to the latest to make your cpu work: http://www.msi.com/product/mb/Z68A-GD65--G3-.html#/?div=BIOS
For flashing >>Use the MSI HQ Forum USB flasher<<
If you can't get a hand at a Sandy you need to let any PC shop or MSI do it for you (that's not for free of course). >>How to contact MSI.<<

MSI X79A-GD45 (8D) Boot loop

Setup
MSI X79A-GD45 (8D), Socket-2011
Intel® Core i7-3820 Processor
Corsair Vengeance DDR3 1600MHz 16GB CL9
Kit w/4x 4GB XMS3 modules, CL9-9-9-24, 1.5V
AMD Radeon HD 7970
Cooler Master GX 750W psu
Bios: 7760vA6
If i leave computer off for a few hours it goes into boot loop.
Fans disc etc spins up then it shuts down, goes on like this for a while and if i'm lucky it boots after a while.
Quick fix is to pull a memory stick and it goes directly to the hardware change message (F1/F2 to Setup)
Turn off computer plug memory back inn and it all works as normal.
Putting ram in a triple/quad channel setup also produces the same boot loop, never gotten to bios with that setup.

Here are some things you can try:
I suggest doing a full cmos clear then load optimized defaults.
1.) Run memtest make sure all of you ram is working properly. >>Memtest86<< Try 1 sticks at a time and checking each stick this way may be nessesary to find if you have a bad stick. Also, try each dimm with a known working stick of ram.
2.) Disable / enable XMP test each way and see if the problem goes away either way.
3.) Raise the dramv to 1.55-1.65 volts
4.) Set the command rate from 1t to 2t.
5.) Inspect the cpu socket and the cpu for damage. You will need a magnifying glass and stong light to notice any bent pins in the socket.
6.) Try different ram

MSI z77 mpower boot loop-cold start

Just got this PC put together a few days ago and I havent had luck keeping it at 4.5ghz @ 1.360v.
System Specs:
i5 2500k
z77 mpower @ latest bios version
16gb Corsair Vengeance 1866mhz
msi GTX 670 power edition oc
750w Corsair psu
256gb samsung SSD
Corsair H80
I can get it overclocked to 4.5ghz @ 1.360v and while running prime95 for 24hrs it was 100% stable, temps never went over 70C. I have set the I/O voltage to 1.2500v, the System Agent voltage to 1.105, the RAM memory voltage to 1.60v. XMP enabled @ 1866 9-10-9-27.
The problem is that it runs fine until I shut it down for 15 minutes then try to boot it back up, it boot loops 5-6 times then resets everything in the BIOS. The motherboard shows a code 60 as soon as it powers up, then it shuts down again, then powers back up then it gets stuck on A2, then again shuts down and starts back up and shows 60 again, and then A2 again, does this 5-6 times until it decides to reset everything and it allows me into BIOS again. It's driving me INSANE. Does anyone know what the heck is going on? I want to be able to shut it down when I go to sleep and be able to turn it back on without overclocking it again in the morning, ya know?
It works perfectly fine when I restart the computer, only happens when it sits turned off for more than 5 minutes.
Appreciate the help in advance.

We have similar boards and I cannot view your screen shots: https://forum-en.msi.com/index.php?topic=162043.0
Try an overclock based off mine and see if it is better.
If you want to do an muliplier change oc, post better screen shots so I can see what you have set.
**PS: Don't mimic my ram settings, just enable xmp. Also, you won't be able to get this stable at 1866 w/ 4 sticks unless you are lucky. Esp with a Sandy cpu.
Do your testing with just 2 sticks in dual channel, then put the 4 in and if you are lucky you may be able to set it to 1600 9-9-924 / 2t.

MSI Z77A G45 boot loop

Hi everyone!
I just tried to flash my MSI Z77A G45 today from the bios version 2.1 to 2.A.
I had blackscreens all the time when i tried to flash it with the M-FLASH utility from my bios.
Then everything just started normaly (after each blackscreen), but there wasn't any update, i tried to force the update with LiveUpdate.
And now when i try to start the computer, i just get a blackscreen (no signal for the monitor) and a boot loop.
It just stops and reboot after 10s.
My hardware is working perfectly, i think this is from a corrupted bios issue.
Which things i tried:
- Doing a clear CMOS (nothing happens)
- Removing the CMOS battery for 10 minutes (the reboot loop stopped, but there was not any display, i restarted the PC then and the reboot loop started again)
- Cleaning my PC (from dust and things like that), it was not efficient at all
- Booting from a USB key with the bios in, and formated as FAT32, nothing happens too. It doesn't recognize the USB key and anything else (keypad etc.) so the blackscreen was there again.
My Hardware:
CPU: Intel Core i5 3570 3.4 Ghz
Motherboard: MSI Z77A G45
GPU: None (Intel graphics 4000)
RAM: 2x4Gb Corsair Vengeance
HDD: Crucial M4 SSD 64Gb
Power supply: Corsair 850W
Do you think that i need to send my mother board back to the RMA?
I hope you will be able to help me, or find a solution
Thanks in advance

You can try the steps found here https://forum-en.msi.com/index.php?topic=119375.0
Otherwise, it is RMA time.
Next time use the forum flash tool and archives found on the forums.

MSI Z77A-G45 Boot Loop problem

Hi,
I recently built my computer 2-3 months ago. It worked fine until a couple days ago it started boot looping. It doesn't even get to BIOS. I think it's my motherboard gone bad. I switched CPU and memory with another computer and it works fine but when i put it in my computer it boot loops again. before i go through this whole warranty ordeal does anyone have any ideas i could try? Thanks!

>>Posting Guide<< please list all the components in your system!
Motherboard?
CPU?
RAM?
GPU (if you have a dedicated graphics card)?
PSU (Power Supply Unit - please list the +12v rail/s amperage rating/s on its data sheet)?
what you have described is usually either a Bad Motherboard or a Inadequate/overstressed PSU! so the components list of what you used to build the system is Very important to determine what exactly has gone wrong.

MSI Install - Service Startup Causing a Boot Loop?

Similar Messages

Maybe you are looking for