D-Bracket (processor initialization hang up)

Hey guys i need some help,
So i built this comp about 2 months ago or so and it was working fine, then it started weird by turning itself off sometimes. So i brought it home to work on it over my spring break. It keeps hanging with the d-bracket LEDs showing red in the 1 and 4 position and green in the 2 and 3 positions:
Red    - Green
Green - Red
Looking at the led configurations i think that is the processor initialization hang up. I'm hoping that my processor isnt fried, because that would be pretty disappointing.
i put my system specs in my signature, if you need to know anything else let me know.
Thanks in advance guys.

Hello, provide PSU details(can be found into PSU sticker)
that doesn't look good..:
2GB Memory (4x PC 2100 512MB)
4 sticks... unknown brand probably mixed, low rated freq...
remove power cord from the PSU and Clear CMOS Guide
try to boot with one stick only into DIMM slot close to CPU socket.
check CPU cooling system too. (apply new thermal paste, check & clear CPU socket and CPU cooler from any dust, replace CPU cooler if condition is bad.)
best will be to get decent memory 2 sticks at least PC3200.

Similar Messages

  • D-Bracket Processor Initialization on K8N Neo4 Platinum

    Folks,
    I just read through previous posts and want to list what I plan to try first.  See setup in my profile below.  I built the new systems in Aug-Sept, 2005.
    Situation:
    This morning after last night's normal shutdown I get blank screen, no disk drive sounds, but I hear fans and see temperature sensors with abnormally cool readings.  The DVD light flashed.  I checked D-Bracket and have 1&4 red and 2&3 green for processor initialization.  I found no loose cables.  I have not yet opened the case.
    What to try first:
    I gather the D-Bracket is only advisory, not gospel.  So the standard things are
    clear CMOS - I plan to use the button on the 7125 MB
    remove CMOS battery for an hour
    remove and reconnect the power cables from the PSU to the MB
    I welcome any comments.  I still am a hardware novice.

    Thanks to HenryW for his comments and suggestions on Christmas day.
    Simply disconnecting and reconnecting the main cable from the PSU to the MB got my box back in business.  I always welcome easy victories.
    I assume it was some kind of power anomaly that caused a circuit breaker like action in the MB so disconnecting the fully seated and secure cable, waiting a minute, then reconnecting was sufficient.
    I have another issue, though, a NB fan that is not functioning.  I will make a second post about that after getting breakfast.

  • Neo2 won't post -- hangs on "Processor initialization"

    Well after 6 months of my new computer running just fine, it's suddenly starting to crap out on me. Every so often over the past 2 months, my computer would fail to boot up and the DBracket LEDs would hang on the code for Processor initialization. The monitor light would stay orange and never recieve a signal. But I'd simply reboot and it would work.
    However, 3 days ago I went to install a wireless card (DLink Wireless 108G) and the drivers weren't installing properly and it wasn't being recognized. When I rebooted, it started to hang on Processor initialization again. After reconnecting the power and reseating the card many times, it still would not boot. So I took it out and it booted up just fine.
    Eventually I got the card installed properly and it worked for a day and a half (with a few lockups), but then the problem came back. I've since removed the card completely and have been troubleshooting from there.
    It boots about 10% of the time. If I keep trying over and over again, it never will. But if I let it sit for a while then try, sometimes it works. If I take out my GPU, it works every time. One time it wasn't working and i took out a stick of RAM and it decided to work. After browsing this site for a while I decided my PSU was probably going bad (was 400w with 20A on the +12 rail), so I went out and bought a new Antec Truepower 430w. Sadly this fixed nothing.
    I'm pretty confused because I can't narrow it down to the exact cause as sometimes it just happens to work. So nothing is completely broken.
    Some things I've tried:
    Reseting the BIOS with the jumper.
    Reseating the GPU (sometimes this worked)
    Reseating the RAM
    Unplugging all connections and redoing them.
    Also, all fans spin properly on every boot attempt.
    Any help would be greatly appreciated.

    Well I tried using an old graphics card (geforce 2 mx I think) and it worked sometimes, didn't work others. Right now it's tending to not work, so i'm thinking it's the motherboard.
    Maybe I'll try getting a new battery, as it's a lot cheaper than a new motherboard at least. But I'm curious, why do you think it's the battery?

  • K9N2 (MS-7374) Boot Problem - 8 beeps, hangs on processor initialization

    Hello everyone. I've been looking through posts on this forum and attempting to resolve this issue for a while now. Before I go and make potentially expensive purchases, I'd like some thoughts.
    I have a K9N2 (MS-7374) motherboard. I had done some maintenance on the system, primarily adding new HDDs. Everything was running fine. I did notice that, after a while, a white LED had come on (which indicates that the 12v power connection was not properly connected, though I wasn't aware at the time). The case was open during this time. I decided to disconnect the old HDDs and close it up.
    After doing so, I noticed that it wouldn't boot. It'd just hang there, 4 red LEDs. I remembered this happening before, which was due to the video card not receiving enough power. So I checked the connection and the white LED went off. I attempted to boot. The other LEDs flashed briefly (to indicate that the system was on, the 4 LED indicators, PCI, etc), then it immediately shut off and returned to the standby state, as indicated by the orange LED in the lower-right hand corner.
    I removed the 12v connector and noticed that one of the pins on the cable that connected the motherboard to the power supply was staring to come out. I pushed it back into place and plugged it back in. I went to boot the system and found another problem. It would hang on "Processor Initialization", as indicated by RGGR on the LEDs, and beep a total of 8 times (short). The 8 sounds like 2 short beeps, followed by a very short pause, followed by 6 more short beeps.
    So, here's what I tried after reading a number of resources, including these forums:
    Disconnected everything except for the CPU, memory and video card. No change.
    Checked the PCIe video card and its power connections. Replaced it with an old PCI video card. Still had the same issue.
    Removed the RAM. Resulted in 3 long beeps. Re-added a single stick. Same problem as before. Repeated for each of the other three sticks individually. No change.
    Removed the motherboard from the case, in case of a short. Still same issue.
    The only thing I haven't tried is a new power supply, because I don't have any spares. I wanted some input before I go buy one. I'm also concerned by the two beeps, pause, then six additional. Is that indicative of two failures, or can I safely assume it intended to be 8 beeps?
    Thanks for any help

    Quote
    OCZ SLI 4096MB PC6400 DDR2 800MHz (2x1024MB)
    nVidia SLI-Ready PC6400 DDR2 800MHz (2x2048MB)
    You should not mix memory sticks
    Quote
    - Disconnected everything except for the CPU, memory and video card. No change.
    - Checked the PCIe video card and its power connections. Replaced it with an old PCI video card. Still had the same issue.
    - Removed the RAM. Resulted in 3 long beeps. Re-added a single stick. Same problem as before. Repeated for each of the other three sticks individually. No change.
    - Removed the motherboard from the case, in case of a short. Still same issue.
    - The only thing I haven't tried is a new power supply, because I don't have any spares. I wanted some input before I go buy one. I'm also concerned by the two beeps, pause, then six additional. Is that indicative of two failures, or can I safely assume it intended to be 8 beeps?
    Looks like you miss something, double check everything again.
    Reseat VGA and check all power cables

  • MSI k8n Neo2 Platinum processor initialization d-bracket radeon 3850

    Hi guys,
    I just bought (from eBay ) a Powercolor HD Radeon 3850 AGP. When I removed my old GeForce 7600 GT and put it on the system didn't start. No beep, no display signal. The D-Bracket was stuck on Processor Initialization stage (11 RED,12 GREEN,21 GREEN, 22 RED). I tried quite a few stuff, like bios upgrade, bios agp settings but same **it  . Please help. Thanks.

    Hi there, thanks for your help. I dont know if it works in another system. I have to try somewhere else tomorrow..Yes it is in the slot 100%. PSU is a Thermaltake Xaser, I don't remember its Wattage, I bought it back in 2004. Maybe 450W?!..Does the Radeon require more power than the 7600GT?They have the same power connector. Do you think anyway that such a new AGP card like Radeon 3850 would work without any tweaks on my system?? I have been reading about the AGP voltages and I am quite confused..My mobo has 1.5V for the AGP but I think I read somewhere that the latest AGP cards work on 0.8V...

  • CPU initialization hang on bootup after moving computer

    Sorry for the crossposts, but I am unsure where to put this.
    After moving my system across country I have encountered a problem.  When I boot up my K7N2-L with 2200 and MSI GF4 4200, the system hangs on "processor initialization," as indicated by the D-bracket LED display.  Removing *just the VGA card remedies this problem and the system moves to boot up properly.  
    What could be the cause of this problem?  The only way I can see the VGA card affecting the CPU is by insufficient power or a short in the system.  Would this be a mobo problem, a CPU problem, a PSU problem or a VGA problem?  the system had worked fine months before I moved it.  
    Any help is appreciated.
    Nathan

    I have already pulled  everything out and put everything back.  That is how I found out it works without the video card- process of elimination.  So, when I have everything BUT the video card in there, it works.  When I have the video card in there, it doesn't.
    How do I know it is the video card causing the problem and not the video card interface, or the PSU or some power related issue within the system?
    Any other ideas?  I've already cleared the CMOS and I have not been able to test the system with other components.
    Nathan

  • CPU initialization hang on bootup- works w/o VGA card!?

    After moving my system across country I have encountered a problem.  When I boot up my K7N2-L with 2200 and MSI GF4 4200, the system hangs on "processor initialization," as indicated by the D-bracket LED display.  Removing *just the VGA card remedies this problem and the system moves to boot up properly.  
    What could be the cause of this problem?  The only way I can see the VGA card affecting the CPU is by insufficient power or a short in the system.  Would this be a mobo problem, a CPU problem, a PSU problem or a VGA problem?  the system had worked fine months before I moved it.  
    Any help is appreciated.
    Nathan

    Quote
    Originally posted by NovJoe
    Low PSU power possible to affect this... Over-heating of card and CPU could also be the cause... BIOS settings could be another cause too... Trying looking into these areas as there's alot of possibilites on a general problem like this.
    All the Best...  :D !!!
    I have reseated my processor- overheating is not the cause.  It has worked fine before.  I have cleared the CMOS, so BIOS settings are not the cause.  It is not low PSU power either (unless something is wrong with my PSU).  This system has been running fine for months until I moved it.  Thanks for your suggestions though...

  • POST LEDs RGGR Processor Initialization

    What can be deduced from the sudden onset of this failure?
    I Tried (with no effect):
     Reset BIOS jumper,
     unplug all drives
     swap known good ram
     remove all cards including video
    This happened on a shutdown restart after removing HP Officejet 500 software which was acting weird when booting without the printer attached - the mouse would only move in extreme slow motion.
    No bulging or leaking capacitors visible.
    Power Supply works fine on another system.
    BIOS is up-to-date and been working fine for many months.
    Since the POST passes the preliminary tests:
    0: System Power On
    1: Early chipset initialization
    2: Memory Detection
    3: Decompressing BIOS image to RAM
    4: Initializingt Keyboard Controller
    5: Testing VGA BIOS
    and then freezes on:
    6: Processor Initialization
    and since this is the only Socket 370 mobo and cpu I have
    (Can't swap for known good)
    What can be deduced by this failure message?
    (Thanks for your expert opinions in advance)

    MSI-6366 mobo - Apollo Pro266
    PIII-667
    256meg pc133 sdram
    20gig wd 7200 hd
    250w psu
    Geforce2mx200 AGP
    What I am asking for, is help understanding what the explanation given for the red-green-green-red lockup means.
    From that link (and the mobo manual) it sez:
        Red-Green-Green-Red
        Processor Initialization
        - This will slow information regarding the processor
            (like brand name, system bus, etc...)
    It hangs there forever and the Monitor never comes out of powersave mode.
    Seems that the processor has already successfully run some BIOS code to test memory, decompress BIOS, init the keyboard and test the VGA BIOS, so I don't think the processor just went bad.
    Since the same RGGR pattern freeze happens with or without the video card installed, or with a PCI video card installed, then the VGA BIOS test must not be testing the actual video card itself, or else it is skipping this test since this mobo has no "on-board" VGA.
    Any insights?

  • Stuck on Processor Initialization

    Hi all,
    Tonight I decided to upgrade to Windows 7. I preordered almost 2 months ago so I was quite eager to install it :D I also purchased 2 more gigs of ram.
    So after I backed up PC I turned of PC, grounded myself and installed the extra 2 gigs of ram. Cleared CMOS, booted PC and it went into Windows XP  no worries. Shut down PC again, un-plugged my IDE HardDrives and all USB devices. Installed Windows 7 and all went ok, had a play around with W7 after about 30 mins I shut PC down again, grounded myself, plugged in IDE HardDrives. Switched on PC and it made a 3 second beep and repeated every 5 seconds or so. According to D-Bracket it stuck on "Memory Detection Test". So I took out the modules one by until PC started to boot. Replaced modules and it passed the memory test but then nothing else happened ie not posting and gets stuck at "Processor Initialization". I know this because the d-bracket lights are as follows 1-Red, 2-Green, 3 - Green, 4 - Red.
    There was at one point where all 4 lights on the D-Bracket were red and nothing else happened. Discovered there could be an issue with the processor. Any way I Cleared CMOS and again stuck on "Processor Initialization". I'm starting to feel that somehow I fried the processor, what you guys/gals think?
    any help appreciated.
    Cheers
    Darren
    Specs in signature

    Thanks Fredrik for quick reply.
    You reminded me, I forgot to say I did accidently remove the power to the fan for the main board but I did put it back straight away!
    Main Board power cable connected defo.
    This is what I did just now:
    1. Removed all ram.
    2. Rebooted and got the beep.
    3. Tried all memory sticks in slot one and each time D-Bracket reported "Processor Initialization"
    4. Replaced all Ram.
    5. Removed SATA HD, USB PCI Card and Graphics Card turned on PC and still getting "Processor Initialization"
    So as it stands there is nothing connected apart from fans and the system wont get past "Processor Initialization".

  • No Post -Processor Initialization

    K8N neo platinum
    I built my pc in october. its been working fine ever since. then the other night it was running fine. i came back and the screen was blank. so i restarted the system. and ever since its hangin on 1:red 2:green 3:green 4:red "Processor Initialization".
    I havnt changed any settings for a few weeks, and the pc was sat there just fine at the time playing an mp3 before it happened.
    Ive tryed moving RAM around checking all connections, restings BIOS that kind of thing, and its still stuck.
    Any suggestions are welcome. Does it look as thought i'll need to send the Mobo back?
    specs are roughly:
    AMD 64 3200+
    1GB ddr400
    250GB SATA
    radeon 9800 pro

    RollerCam540,
    Quote
    when the CPU is dead that's when you get the "processor initialization"
    Quote
    no, i'm wrong. read this:
     :lol_anim:hope southwalesboy's not gota weak heart
    Hi southwalesboy,
    Quote
    specs are roughly:
    please supply further details re :-
    1) Ram Make & type
    2) Power supply Make + (max output for 3.3v=??A ,5v=??A, & 12 v=??A Usually on side of unit)

  • Wasapi: IAudioClient- Initialize() hanging when opening audio capture device

    I'm trying to open the capture/input audio device. I call ActivateAudioInterfaceAsync() , then when I call IAudioClient->Initialize() on the capture device, the app hangs, supposedly because for some reason it's trying to display the 'Allow app to
    use the mic?' prompt.
    The hang _doesn't_ occur if I manually set the app permission to use the mic (i.e. launch the app without having it open the audio devices, open the permission tile, activate the mic permission).
    Calls to ActivateAudioInterfaceAsync and  IAudioClient->Initialize() are made from the UI thread (the one that receives callbacks for buttons, which on Metro style apps seems to be different from the thread that starts the application, i.e. WinMain).
    What am I doing wrong?
    I've attached the stack that shows the app hung below.
    Thanks,
    Flavio.
    ntdll.dll!_NtAlpcSendWaitReceivePort@32()
    Unknown
    rpcrt4.dll!LRPC_CASSOCIATION::AlpcSendWaitReceivePort(unsigned long,struct _PORT_MESSAGE *,struct _ALPC_MESSAGE_ATTRIBUTES *,struct _PORT_MESSAGE *,unsigned long *,struct _ALPC_MESSAGE_ATTRIBUTES *,union _LARGE_INTEGER *)
    Unknown
    rpcrt4.dll!LRPC_BASE_CCALL::DoSendReceive(void)
    Unknown
    rpcrt4.dll!LRPC_BASE_CCALL::SendReceive(struct _RPC_MESSAGE *)
    Unknown
    rpcrt4.dll!LRPC_CCALL::SendReceive(struct _RPC_MESSAGE *)
    Unknown
    rpcrt4.dll!_I_RpcSendReceive@4()
    Unknown
    rpcrt4.dll!_NdrSendReceive@8()
    Unknown
    rpcrt4.dll!@NdrpSendReceive@4()
    Unknown
    rpcrt4.dll!_NdrClientCall2()
    Unknown
    AudioSes.dll!_AudioServerCreateStream@36()
    Unknown
    AudioSes.dll!CAudioClient::CreateRemoteStream(enum SYSTEM_AUDIO_STREAM_TYPE,__int64,__int64,struct SYSTEM_AUDIO_STREAM *)
    Unknown
    AudioSes.dll!CAudioClient::Initialize(enum _AUDCLNT_SHAREMODE,unsigned long,__int64,__int64,struct tWAVEFORMATEX const *,struct _GUID const *)
    Unknown
    Metro.exe!App1::MainPage::Startup() Line 171
    C++
    Metro.exe!<lambda_f0ad93afb1643234338c56b595dca446>::operator()() Line 48
    C++
    Metro.exe!Platform::Details::__abi_FunctorCapture0<<lambda_f0ad93afb1643234338c56b595dca446>,void>::Invoke() Line 850
    C++
    Metro.exe!Windows::UI::Core::DispatchedHandler::Invoke()
    C++
    Metro.exe!Windows::UI::Core::DispatchedHandler::[Windows::UI::Core::DispatchedHandler::__abi_IDelegate]::__abi_Windows_UI_Core_DispatchedHandler___abi_IDelegate____abi_Invoke()
    C++
    Windows.UI.dll!6283fdff()
    Unknown
    [Frames below may be incorrect and/or missing, no symbols loaded for Windows.UI.dll]
    Windows.UI.dll!628314ae()
    Unknown
    user32.dll!_InternalCallWinProc@20()
    Unknown
    user32.dll!_UserCallWinProcCheckWow@36()
    Unknown
    user32.dll!_CallWindowProcAorW@24()
    Unknown
    user32.dll!_CallWindowProcW@20()
    Unknown
    Windows.UI.Xaml.dll!5e06b434()
    Unknown
    Windows.UI.Xaml.dll!5e06b3af()
    Unknown
    user32.dll!_InternalCallWinProc@20()
    Unknown
    user32.dll!_UserCallWinProcCheckWow@36()
    Unknown
    user32.dll!_DispatchMessageWorker@8()
    Unknown
    user32.dll!_DispatchMessageW@4()
    Unknown
    Windows.UI.dll!628311dc()
    Unknown
    Windows.UI.dll!62831290()
    Unknown
    Windows.UI.Xaml.dll!5e16dee2()
    Unknown
    Windows.UI.Xaml.dll!5e16dea1()
    Unknown
    Windows.UI.Xaml.dll!5e16de65()
    Unknown
    ntdll.dll!_RtlReleaseSRWLockExclusive@4()
    Unknown
    03655668()
    Unknown
    twinapi.dll!67b2c9dd()
    Unknown
    twinapi.dll!67b2cab2()
    Unknown
    twinapi.dll!67b2c9f6()
    Unknown
    SHCore.dll!740c1ffd()
    Unknown
    kernel32.dll!@BaseThreadInitThunk@12()
    Unknown
    ntdll.dll!___RtlUserThreadStart@8()
    Unknown
    ntdll.dll!__RtlUserThreadStart@8()
    Unknown

    When you're in this state, can you take a dump of the svchost.exe process containing the AudioSrv service and send it to me? email to (mateer at microsoft dot com)
    Matthew van Eerde

  • MSI K8T Neo D-Bracket Early Initialization

    Hi,
    I recently put togther my computer
    -msi k8t neo fisr
    -athlon 64 3200
    -thermaltake xaser II case
    -hardcano II
    -thermaltake xaser III 480w power supply
    -thermaltake silent boost k8 fan and heatsink
    -2x 512 corsair xms 3200 v1.1 cl2
    -samsung 16x dvd rom
    -ati radeon 9700 pro /w zalman heatsink
    Im kinda newbie at making computers(only my second time making a comp)
    For some reason my computer hangs at early chipset initialization nothing shows up on screen, when i take out everything my computer beeps 3 times in intervals and still hangs on early initiliaztion.When i just put my memory in, the beeps stop but comp still hangs at early intialization.Anyone got any ideas?Could it be i installed my cpu wrong? bad video card?Or could it be i put in the pins wrong? Well thnx for looking and i appreciate any help.
    Thnx

    We have seen this happen alot in the P4 Forum, As There seems to be numerous Members that are having some compatability issues with the ATI-9700, Pro, and Non Pro VPU's . Someone Contacted ATI Tech. Support Directely and recieved this Response >> Dated Dec 24, 2003 at 01:10 PM reply
    Hi David,
    This video card has a know problem with the some of the MSI manufactured motherboards. It seems that the Boards involved are the VIA series, and the INTEL i865PE series. The only ATI cards that work have to have a serial # with -30 at the end or higher or they will not work. Because this card is discontinued our supplier cannot gaurantee a -30 card as a replacement. We can only exchange for a different item within the first 15 days so the only thing I can suggest is to see if you have a friend that may want to buy the card as there is probably nothing wrong with it and then buy another one. Any of the new 9600 or 9800 series don't have this problem. If you have any other questions let me know. Thanks alot.
    Ryan S.   Senior Tech. ATI Canada
    I hope that this is Not the case with your Board. And now we have also seen that this compatability issue is NOT Just limited to the i865PE's as I have seen Threads involving both the SIS 655 and the INTEL i875P MSI Boards also.
    I have also recieved word that some of the Rev.1-A 9700 Boards were also only 4 Layer PCB's, Not the Normal 5 Layer, and this is Leading to the Graphic Cards NOT Making Good Contact in the AGP Slot. And I have Read that this can be somewhat remedied by trying to (Gently) Making sure that the Card is inserted Completely into the Slot, also try (Again very gently) wiggling the Card back, and forth, to help establish better contact with the cards Gold Fingers, and the slot itself........I dont know, check and see if your Card is one of the -30 Cards, or look in SANDRA, and Under "Information Module", select "PCI, AGP, Card Reader" and Check AGP, and see what the Rev. is for your Card if it has the (A_1) then it may be a Thin one , I know; sounds rediculous, does'nt it? Sorry I could not Be of Any more assistance........Let us know.........SEAN REILLY875

  • Neo2 plat stuck at processor initialization

    help,out of the blue, my k8n neo2 platinum won't boot. the diagnostic bracket is showing red,green,green,red which the book says is processor initilization. i swapped in a known working processor with no luck, swapped known working memory, jumpered the cmos reset, removed the battery, disconected the drives. nothing has worked. any ideas? the motherboard just go bad? it's been bullet proof up 'till now. any help would be appreciated.

    here are the specs
    k8n neo2 platinum w/ whatever the latest  bios is, cant remember exact version
    athlon x2 4200
    2x512 sticks of corsair pc 3200 xms memory
    ati x800xl
    aspirie 520 watt ps  28a,30a,34a,
    maxtor 140 gig hd ide
    windows xp sp2
    couldn't really find anything else in that post that helped, i can't even get in to the bios. this thing has been running flawlessly for 3 years until this situation cropped up out of the blue. i looked through the stickies but to no avail. thanks.

  • D-bracket processor intialization failure

    I have a problem with system I built for a friend about six months ago.  Were he was playing earlier in the day then shut it down and then went back later and got no post except for no video signal on the monitor.  And when he brought to me I had 4 red lights on DB then I reset cmos I got 1 red 2 amber 3amber 4 red. I've checked the psu, ram, changed cpu. I have no way to check the video card or mobo. Any suggestions for what it might be. ???
    Turbo link 430 w 3.3v 28 A, 5v 40 A 12v 18 A
    Msi k8n neo 4
    6600 GT PCI express
    AMD Athlon 64 3200+ Venice 1GHz HT 512KB L2 Cache Socket 939 Processor - Retail
    1 GB cosair value select memory

    Thanks to HenryW for his comments and suggestions on Christmas day.
    Simply disconnecting and reconnecting the main cable from the PSU to the MB got my box back in business.  I always welcome easy victories.
    I assume it was some kind of power anomaly that caused a circuit breaker like action in the MB so disconnecting the fully seated and secure cable, waiting a minute, then reconnecting was sufficient.
    I have another issue, though, a NB fan that is not functioning.  I will make a second post about that after getting breakfast.

  • Amazon App Suite - App Store Initialization Hang

    I thought this may be useful.
    Following device de-registration via the Amazon web-site, I found that I could not log back into the App Store app on my Motorola Droid Razr M. After contacting Amazon and spending some time with them with no resolution, I found that if any of the App Suite apps are disabled the App Store app will hang at "Initializing" in the newest version, or "bad password" in the factory version. Simply re-enable the apps via Manage Apps > Disabled and clear the data on each and all works fine.

    OK got it thanks

Maybe you are looking for

  • Videofunction on iphone 4 is not working after the update to IOS7

    Hi. The videofunction on my iphone 4 is not working after the update to IOS 7: Anyone else experiencing the same problem? Anyone with solutions? Thanks!

  • Macbook Pro Doesn't Recognize Samsung TV

    Hi all, I've seen this question in a few other discussions which are still unresolved, but I'm hoping maybe I can get some answers. I've been hooking up my MBP 15" to my Samsung LCD TV (Model: LN32B460) for almost a year. Last night, I connected the

  • InDesign CS2 'Unlock' greyed out ?

    I am using CS2 (v4.0.5/WinXP SP3) and wish to replace some .AI/.PDF objects with newer versions in an InDesign document that is a couple of years' old. I recall locking the objects, but find that the 'Unlock Position' option on the Object menu is gre

  • How to keep image dpi at 300dpi

    I am trying to print a photo for framing but when I mess around with the colours the quality seems to diminish this is on my iPad quastion is ? Is it possible to drastically change colours and maintain high dpi.  For large printing around 60 cm sq pl

  • Screen lights up

    Hi, since a week ago, my macbooks screen give a white screen or about half a second when I start it up (so before the apple logo comes on) or when I get it out of the hybernate. Is that normal? Thanx!