945p neo3 Problem after live update bios

Hi,
After I made the update trought live update, my computer doesn't start, I don't know what to do?
When I restarted it only shows the logo, if I hit DEL or TAB keys it shows to the start of the boot but it freezes.
I already clear the cmos, did anything that i had found on this forum, but nothing works.
I don't have the chance of doing anything because it won't gets the part to enter in bios.
It only appears in the screen thre lines:
AMIBIOS 2005.....
MSI 945PL Neo A7236IMS V1.9 Date: 08/07/06 08:05:52
Intel(R) Core(TM)2 CPU               6400 @ 2.13 GHz , Speed:
and nothing else appears.
One of the things that is very strange is if my board is a 945p neo3 why it happears 945 pl neo, did the live update flash my motherboard with a wrong bios version????
is what it looks.
Any ideas to fix this, if there is a fix?
I don't see anything, because the motherboard don't even reaches the process of boot, so I can't try to flash a other version of bios because the process never reaches the time to boot from floppy, usb, disk..
HELP PLEASE,
Thanks in advance,
Nuno

"Thanks for the ISO File, everything is now correct, the problem with the memory was related with checksum, now happears the 4096 MB."
Nope they was 2 separate problems, solved with one hit.
"About I couln't start your application, whith the historial of your application and antivirus that I saw on the post about it, i got suspecious right away of my antivirus solution.
So to help, I uninstall and after that i could run it, I use Symantec Endpoint Proctection, is the corporate solution from symantec that is replacing the old one known as SAV - Symantec Antivirus Corporate Edition. I didn't find any  message in the logs of it, but the fact is that if I have this solution installed I could not run USB tool, if I Uninstall I could run it."
Probably same resource conflict with your AV (some kind of system restriction) which cause Tool unable to proceed properly and terminating itself.
Can't duplicate your issue. I was using SAV - Symantec Antivirus Corporate Edition(Up to date) till now and Tool perform well,
Just installed and updated Symantec Endpoint Protection (Updated to latest definition with all protection activated) and the Tool perform well as expected too.
"now happears the 4096 MB"
Nice

Similar Messages

  • Z77A-G43 login loop after Live update BIOS to V25.1

    Hi,
    Z77A-G43 windows login loop after Live update BIOS to V25.1
    I'm able to see the BIOS menu. But when i continue to login to windows, it loops.
    i would like to know on how to proceed on this. I tried safemode and i was able to login.
    I cannot find the clear cmos jumper on this board.
    Appreciate your response on this one. Thanks!
    edit: I just tried removing the board battery. But still encountering the same issue.
    -Paul

    There is no such BIOS version for this board.
    The last BIOS is v2.11  see here http://www.msi.com/product/mb/Z77A-G43.html#/?div=BIOS
    As for the CMOS jumper. This must be the most stupid saving that MSI has ever done. They leave out the jumper, obviously in an effort to save costs. 
    Check your manual to find the location of the clear CMOS pins. Then you need to short these with a jumper from somewhere else  or use a metal object to connect the pins.

  • BIG PROBLEM after Live Update installed

    I installed the live update and now my system has crashed!
    During my initial set up of this system I was having overheating issues. I stopped this by selecting the Advanced preset setting in the BIOS.
    Well after installing the Live update the system restarted and installed the recommended updates for the mobo. I once again restarted the system only to have it shut doen within 30 - 40 seconds (never even got Windows to completely boot). I tried several times with the same outcome. I then remembered the over heating issue I had during the build. I looked back here to see how I solved the problem. I tried to preform the same steps I took earlier (going into BIOS and setting the advanced preset) each time being shut down before being able to accomplish the task. I am now left with a stone cold quiet system! I get the power switch to light up on the case and 2 of the LED's on the board turm blue. I have tried the mobo power button and the reset button with no luck!
    Thoughts?

    Quote from: Svet on 11-June-10, 22:01:34
    Why you didn't tell this until now?
    You tell that you've installed Live Update, not mention that you've proceed with BIOS update too...
    Repeat again >>Clear CMOS Guide<< with power cord removed,
    and leave 1 memory stick in 1st dimm, then try to boot
    My apologies, you are correct. In the Live updates, BIOS was among the items to be updated.
    I already tried the clear CMOS excatly as indicated in the link/video.

  • 870A-G54 Black screen after Live Update bios

    Hi everybody,
    My computeur works fine since 3years, I change nothing inside, I just want to upgrade all drivers and bios because sometimes the computeur was freezing without any reason....
    So...I installed live update...Live update processed to the flash of the bios to the latest version, everything was ok, auto-reboot and.... black screen !!!!
    Visually all is fine : led on, fan ok, fan of the video card too, hard drive is launching but nothing in the screen.
    I already read all the post about the same problem, I try to reset the bios by unplugging the cord of the psu and move the jumper : nothing...
    I change the video card : nothing more...
    When I unplugged all the ram I heard 3 bips, and when 1 or more dimm present there is no bip.
    I know there is a problem with this fu***** bios update but can you have an idea for my problem and help me ???!!!
    Thanks.

    Quote from: Svet on 26-October-13, 22:51:04
    try again clear cmos, >>Clear CMOS Guide<<
    ...I follow multiple times this guide...again and again the same problem...an onother idea boss ? 

  • Multiple Samsung Stratosphere problems after FF1 update

    There have been multiple posts on various issues users have found after the recent Stratopshere FF1 update.  Some were replys to older posts and some only touched on a single issue.  I wanted to consolodate into one thread, and hopefully get teh attention of Verizon to maybe reply here.
    For reference, a lot has been discuss here --> https://community.verizonwireless.com/message/874446
    Summary:  Verizon and Samsung have finally updated the Stratosphere almost 1 year after release.  This updated the phone from Android 2.3.5 to Android 2.3.6.  Going by filename, this is known as the FF1 update.   This update went live at the end of August 2012, and most users were upgraded before mid September 2012.
    There were some noticable changes in this update:
    -Lock screen has changed.  The puzzle piece and glass lock options have been removed.  New options have been added, such as facial recognition unlock.
    -Call answering screen has changed, introducing the option to ignore call with a message.
    -Camera now has digital zoom ability.
    -Ability to uninstall the 2 games the phone comes with (Need for Speed and Lets Golf)
    -Phone icon has changed ever so slightly
    -Wifi icon now included up and down arrows to indicate data is being sent or recieved
    -Wallpaper no longer "stretches" over multiple screens - ie, it no longer scrolls as you move from screen to screen
    -The visual voicemail app has been improved (I have personally not used this feature)
    -Callback number is now supported in text / picture messages
    -Android core OS updated from 2.3.5 to 2.3.6 (both versions are still Gingerbread)
    -Update to how the device deals with the end of scrolling.  It used to rubber-band bounce back, now it will just give a green bar and expand the bar as you scroll.  (I cannot fault Samsung for this change as this was at teh core of an Apple lawsuit and has been changed in newer versions of Android.)
    -(I am sure there are more.  please list any others you may have noticed)
    I have found some problems, and others have confirmed that this is (at least) somewhat widespread:
    -The biggest problem is with wifi connectivity.  Upon an initial connection to wifi, everything works great.  After somewhere between 15minutes and 2 hours, problems start happening.  Its as if the wifi keeps hanging or reconnecting.  Download speeds (tested with the SpeedTest.com app) slow to about one third of normal.  Apps like Facebook that require a constant connection will just time out.
    -It appears the signal strength for 3g and 4g connections is lower.  There are places where I used to get a 4g connection, and now I only get 3g.  Some palces I fall back to just 2g digital.
    Another minor issue i found was with text messages.  When you reply to a message, it no longer automatically focuses the text in the input box.  You have to first click into the box to start typing.  Not a huge deal, but one more step to take over and over.  Minor annoyence.
    At my house, I struggle to get a 3g or 4g signal.  I depend on wifi for my data connection.  So with the wifi connection problem introduced by teh FF1 update, my phone is somewhat useless to me now while at home.  Here are teh troubleshooting steps I have been through so far to attempt to fix the wifi problem:
    -Complete factory reset on my phone.  (did not help)
    -Pull battery and SIM card out of phone for 15 minutes.  (did not help)
    -Went to a Verizon store.  The guy at the store was helpful, and said he also had a Stratosphere and was getting the same wifi problems after the update.  He said all he could do was to send me out a replacement phone. I got the replacement phone, and it had the same problems.
    -I read in multiple palces that Android 2.3.6 has a bug within wifi and DHCP.  Apparently if you have a DHCP lease set to "forever", the phone will keep requesting a new address.  Setting the DHCP server on the router to something like 2 weeks, or using a static IP is supposed to solve this.  I have a NetGear N900 router, and I can not change teh DHCP lease time.  It appears, however, that my router is not sending out "forever" leases.  But just to make sure, I gave my phone a static IP.  (None of these steps made any difference).
    The only thing that temporarily fixes the problem is a reboot of the phone.  This will again give you anywhere from 15min to 2 hours of good wifi use before problems start happening.
    I have now had this update for over a week, and on 2 phones.  I still can't maintain a wifi connection for much longer than 15 minutes without problems starting up.
    I am asking Verizon or Samsung to at least confirm this issue if possible.  Maybe there are newer revs of the Stratopshere hardware that don't have this problem.  Or there is something unique about my (and apparently others) situation.  But it seems like Verizon's current stance is to offer a repalcement phone (as currently all Stratospheres are within their 1 year manufacture warranty as the phone has not been ouy for quite 1 year yet).
    I am asking for a workaround for this problem, or a true fix adressed by a new software update, or at least allow us to roll back to the original Andorid 2.3.5 software.
    I have had my original Stratosphere for almost a year with no wifi problems - then get the FF1 update and have had nothing but problems on 2 different phones.
    Thank you for your time.

    Thanks for starting a comprehensive thread on problems with this update. I want to add one more.
    I have Bluetooth in my car (a 2004 model), and previously the phone has connected to it practically instantly when I start the car. Since the update, I have never been able to connect the phone to the car by Bluetooth. Several times the phone has made a standard notification sound at the moment it should be connecting to Bluetooth, though no notification appears. I have no idea what that could mean.The car's Bluetooth shows up as paired in the list of devices in Settings > Wireless & networks > Bluetooth settings. I haven't seen this widely reported as an update issue, but perhaps some others have experienced it too.
    UPDATE: I finally did some testing, and found that the notification was to signal the extremely brief appearance of a dialog indicating that the car's Bluetooth was requesting a connection. Accepting that request let the phone connect with the car, and calls went to the car's sound system as they should. When I turned the car off and back on (just the electrical system; not wasting any gas on this!), the connection was established immediately, so apparently the acceptance only had to be done once. Nevertheless, it did have to be done, and the dialog notification disappears within seconds. I believe it would have been possible to go into Bluetooth settings and accept the connection request there if I missed the notification; but not seeing the notification, I might not know to do this.
    One further observation: When I turned the phone's Bluetooth off and back on after a connection had been established, leaving the car on the whole time, the two did not reconnect. I believe that may be different from before the update, but I'm not really sure.
    Message was updated by David Rensberger

  • Still the same problem with Live update 2

    I still have the same problem with Live update 2.
    I've downloaded newer Bios update but it's 13 MB... it's obvious that I can not have
    in floppy disk and I'm a little bit  uncomfortable of updating bios from CD-rom .
    But what else can I do, besides updating Bios to get out of this Live update from start-up.
    Should I clear CMOS?

    13mb are you really sure ?
    go here instead.
    http://www.msi.com.tw/program/support/bios/bos/spt_bos_detail.php?UID=436&kind=1
    the download file is around 300kb.
    make sure you get the right file.
    you did not specify if you got L or ILRS.
    also dont use live update.
    get drivers from http://www.nvidia.com instead.

  • EFI Problems after last update anyway to downgrade ??

    Hello
    EFI Problems after last update anyway to downgrade ??
    i have updated my MacBook 2010 EFI to MB71.0039.B0E which is 2.1 version
    after updating to this version the Boot time become much slower when i want to change boot partition
    and shutdown become very much slower and startup too
    i tried to install Mac OS X Lion again but it doesnt help
    can i downgrade to this version 2.0 ???
    or when Apple will release the new version ?
    or where can i send a feedback regarding this issues !!!!
    Thanks

    These are user to user forums. If anyone knows the answer, they will give it.
    You can always call Apple support which may charge a fee or you can patiently wait for an answer here, which is free.

  • Share and save problem after latest update

    hello,
    i have share and save problem after latest update - i have installed ps touch on nexus 5 about 2 months ago and until yesterday everything was good but after latest update i can't save and share images in ps touch ( i do reinstall this app  but problem is still  and app doesn't work properly   ) how  can i downgrade to the old version ? Could you fix this problem quickly ?

    i use app which called "aLogcat"
    --------- beginning of /dev/log/main
    I/dalvikvm(24476): Enabling JNI app bug workarounds for target SDK version 11...
    D/dalvikvm(24476): GC_CONCURRENT freed 174K, 2% free 17054K/17264K, paused 2ms+2ms, total 15ms
    W/InputEventReceiver(24476): Attempted to finish an input event but the input event receiver has already been disposed.
    W/InputEventReceiver(24476): Attempted to finish an input event but the input event receiver has already been disposed.
    W/InputEventReceiver(24476): Attempted to finish an input event but the input event receiver has already been disposed.
    --------- beginning of /dev/log/system
    W/ViewRootImpl(24476): Dropping event due to root view being removed: MotionEvent { action=ACTION_MOVE, id[0]=0, x[0]=38.0, y[0]=-115.0, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=2, eventTime=27743080, downTime=27743066, deviceId=4, source=0x1002 }
    W/ViewRootImpl(24476): Dropping event due to root view being removed: MotionEvent { action=ACTION_UP, id[0]=0, x[0]=38.0, y[0]=-115.0, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=0, eventTime=27743086, downTime=27743066, deviceId=4, source=0x1002 }
    D/dalvikvm(24476): GC_FOR_ALLOC freed 122K, 1% free 17271K/17428K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 10K, 1% free 17434K/17604K, paused 7ms, total 7ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 65K, 2% free 17690K/17928K, paused 8ms, total 8ms
    I/dalvikvm-heap(24476): Grow heap (frag case) to 17.615MB for 328336-byte allocation
    D/dalvikvm(24476): GC_FOR_ALLOC freed 0K, 2% free 18010K/18252K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 18011K/18252K, paused 9ms, total 9ms
    I/dalvikvm-heap(24476): Grow heap (frag case) to 18.073MB for 479536-byte allocation
    D/dalvikvm(24476): GC_FOR_ALLOC freed 0K, 2% free 18479K/18724K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_CONCURRENT freed <1K, 2% free 18481K/18724K, paused 2ms+1ms, total 10ms
    D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 6ms
    I/dalvikvm-heap(24476): Grow heap (frag case) to 18.532MB for 479536-byte allocation
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 18949K/19196K, paused 9ms, total 9ms
    D/dalvikvm(24476): GC_CONCURRENT freed <1K, 2% free 19418K/19668K, paused 1ms+1ms, total 10ms
    D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 7ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 19592K/19844K, paused 8ms, total 8ms
    I/dalvikvm-heap(24476): Grow heap (frag case) to 20.049MB for 933136-byte allocation
    D/dalvikvm(24476): GC_FOR_ALLOC freed 0K, 2% free 20503K/20756K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_CONCURRENT freed <1K, 2% free 21416K/21668K, paused 1ms+1ms, total 12ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 50K, 2% free 22351K/22580K, paused 7ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 5K, 1% free 23900K/24140K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 1% free 25824K/26084K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 3411K, 14% free 24528K/28204K, paused 12ms, total 13ms
    D/dalvikvm(24476): GC_CONCURRENT freed 2814K, 14% free 24256K/28204K, paused 2ms+1ms, total 11ms
    D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 4ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 9266K, 1% free 17270K/17424K, paused 10ms, total 10ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 15K, 1% free 17575K/17748K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 22K, 2% free 17875K/18072K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 1K, 2% free 18195K/18396K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 18517K/18720K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 18838K/19044K, paused 11ms, total 11ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 19159K/19368K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 19480K/19692K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 19974K/20192K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 20616K/20840K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 21431K/21664K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 22714K/22960K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 182K, 2% free 24004K/24432K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 8478K, 33% free 17593K/26228K, paused 14ms, total 14ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 18K, 32% free 17895K/26228K, paused 12ms, total 12ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 18K, 31% free 18198K/26228K, paused 11ms, total 11ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 1K, 30% free 18519K/26228K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 29% free 18840K/26228K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_CONCURRENT freed <1K, 26% free 19482K/26228K, paused 2ms+1ms, total 14ms
    D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 10ms
    D/dalvikvm(24476): GC_CONCURRENT freed <1K, 23% free 20297K/26228K, paused 2ms+1ms, total 15ms
    D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 11ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 19% free 21260K/26228K, paused 10ms, total 10ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 15% free 22543K/26228K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 182K, 9% free 23979K/26228K, paused 21ms, total 22ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 8485K, 33% free 17598K/26132K, paused 13ms, total 14ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 25K, 32% free 17894K/26132K, paused 12ms, total 12ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 12K, 31% free 18204K/26132K, paused 12ms, total 12ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 1K, 30% free 18524K/26132K, paused 12ms, total 12ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 28% free 18845K/26132K, paused 8ms, total 9ms
    D/dalvikvm(24476): GC_CONCURRENT freed <1K, 26% free 19487K/26132K, paused 1ms+0ms, total 9ms
    D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 7ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 23% free 20129K/26132K, paused 9ms, total 9ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 20% free 21091K/26132K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 15% free 22375K/26132K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 9K, 9% free 24011K/26132K, paused 14ms, total 14ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 2147K, 10% free 23855K/26456K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_CONCURRENT freed 8776K, 35% free 17337K/26304K, paused 3ms+2ms, total 20ms
    W/InputEventReceiver(24476): Attempted to finish an input event but the input event receiver has already been disposed.
    W/InputEventReceiver(24476): Attempted to finish an input event but the input event receiver has already been disposed.
    W/ViewRootImpl(24476): Dropping event due to root view being removed: MotionEvent { action=ACTION_UP, id[0]=0, x[0]=564.0, y[0]=-50.0, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=0, eventTime=28190972, downTime=28190972, deviceId=4, source=0x1002 }
    D/dalvikvm(24476): GC_CONCURRENT freed 186K, 31% free 17626K/25476K, paused 2ms+1ms, total 12ms
    D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 4ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 63K, 30% free 17884K/25476K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 3K, 29% free 18201K/25476K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_CONCURRENT freed <1K, 27% free 18696K/25476K, paused 2ms+1ms, total 12ms
    D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 9ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 25% free 19190K/25476K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 23% free 19831K/25476K, paused 9ms, total 9ms
    D/dalvikvm(24476): GC_CONCURRENT freed <1K, 19% free 20794K/25476K, paused 2ms+0ms, total 12ms
    D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 8ms
    D/dalvikvm(24476): GC_CONCURRENT freed <1K, 14% free 22078K/25476K, paused 1ms+2ms, total 14ms
    D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 12ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 7% free 23855K/25476K, paused 10ms, total 10ms
    D/dalvikvm(24476): GC_CONCURRENT freed <1K, 6% free 24176K/25476K, paused 2ms+1ms, total 14ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 6440K, 26% free 19562K/26216K, paused 9ms, total 10ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 93K, 23% free 20207K/26216K, paused 10ms, total 10ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed 11K, 21% free 20935K/26216K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 18% free 21673K/26216K, paused 9ms, total 9ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 15% free 22499K/26216K, paused 8ms, total 8ms
    D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 10% free 23695K/26216K, paused 9ms, total 9ms

  • IPhone 4s got problem after I update to 7.1.1. Battery drain so fast

    iPhone 4s got problem after I update to 7.1.1. Battery drain so fast

    The Ultimate Guide to Solving iOS Battery Drain
    <http://www.overthought.org/blog/2014/the-ultimate-guide-to-solving-ios-battery-d rain>

  • Had a problem after download updated itune, error 7 (window error 126) cant open itune at all

    Had a problem after download updated itune, it failed as Error code MSVCR80 and then next message is error 7 (window error 126), cant open itune at all

    Had a problem after download updated itune, it failed as Error code MSVCR80 and then next message is error 7 (window error 126), cant open itune at all

  • Please Read This To Reduce or Eliminate Problems after Software Update

    Hi all, I have been reading quite a handful of Mac users here reporting problems ranging from minor ones like slow downs to major ones like application crashes, and many of them blame the new OS and/or Security Updates.
    Without learning more from the details of how did they perform their Software Updates and Install, I am making a huge assumption that it maybe something they did or didn't do, one of the key things they did not do is Repair Disk Permission
    Below is what I called, the "ritual procedure" needed to perform before and after a Software Update, and also any other major software installation - to help reduce or eliminate "hiccups" afterwards, I cannot gaurantee that all macs all over the world will not suffer any problems after an update, but by doing so, you may help reduce it; I have 4 macs all together and so far I have not encounter any major problems after many versions updates.
    Anyway, I didn't come out with this series of procedures, I read it off somewhere in this Discussion quite a while ago, and thought I share it again with all of you:
    1.Before starting Software Update, unplug all external devices, FireWire, USB, hubs etc etc, not just turning them off but unplug the cables off your Mac, leave only your keyboard, mouse and internet connection on (unless you are using a wireless keyboard and/or mouse or on wireless internet)
    2.Repair Disk Permission
    3.Restart the Mac, then start your SU, do not run any other apps.
    4.After finishing SU, restart your mac; If you are updating OS or Security Updates, Restart is required.
    5.Repair Disk Permission again
    6.Shutdown and re-plug in everything and start up your mac as normal.
    I know the procedure is pretty long and "troublesome", especially the unplugging and restarting part, but so far it really has done my macs good, so I am going to "swear" by it... my FireWire, USB devices etc still work as normal.
    This is really contrary to that "Macs are easy to use", yes, no doubt about it, but the software updates etc is just well, put it this way: The Mac OS when it comes to updates, is very very delicate... so handle with it great care, it will just turn out okay.
    Cheers

    Thank you for posting that. I posted a similar set of suggestions here:
    http://www.macmaps.com/backup.html
    Disclaimer: Reference to links I make to my Macmaps.com website are a for your information only type reference. I do not get any profit from this page, and it is open to the public.

  • K8T Neo Fir won't post after live update to 2.0 bios

    After running the Live Update which updated the bios to 2.0, I can't boot into XP (SP 1).  I can boot in safe mode.  Not sure how to get this running again.  I've tried everything I can think of, any ideas on what I might try?
    Setup was running fine prior to bios update.
    XP SP 1
    K8T Neo Fir
    1 GB
    Promise Sata Raid 1 - 2 80GB Sata drives
    Radeon 9600

    I tried executing "fixboot" from the recovery console but this may have made things worse.  After running this successfully, the console reported that it had written a new boot vloc on teh C partition in FAT32.  The SATA drives are not formatted in FAT32!  Now I don't get the Windows initial screen at all, it just goes back to the bios and restarts.  I can still startup in safe mode though.
    Maybe the Recovery Console can't see the drives properly because the Promise drivers are not loaded?  Any ideas?  I'm in deep now!

  • Live Update (Bios 1.x to 1.6). Boot problems

    I have my setup running with Win XP Pro SP-1 for the last month or so. I just decided to do a live update run. It said that I should  update my bios to 1.6.
    After going through the process (Windows based non-Dos). The system was rebooted. Now, it just refuses to load Windows.
    Infact, it refuses to do anything after initial post.
    I get past the initial test (post) and get to the part where you can press TAB to get to RAID setup (I think). I can hit Delete to get to the BIOS features.
    BUT, it does not load Windows.
    The system just goes to a blank screen.
    I tried to use Win XP to install XP again.... nothing
    I tried to use a bootable floppy to check if it worked... nothing
    I used Linux CDs to see if they work... nothing.
    Nothing to do with my CD-RW drive, my HD and my floppy works.
    CTRL-HOME method does nothing...
    I am clueless as to what happened. This makes no sense.

    Slight error in my system specs.
    It is a Maxtor Diamond Max 9 (120gigs and 2mb cache).
    I tried different settings. If I set the drive on a differen cable (either primary or secondary) and set it as Master. The CD ROM does not work.
    However, if I set the drive as Cable select or slave... the CD rom works. It tries to install XP..
    It says
    Press any key to start....... blah blah
    Checking your system configuration....
    Then blank screen.
    So here is what happens.
    1. If NO HD... the Windows CD will load and attempt to install. Going through the section asking for pressing F6 for ASR etc.
    2. If HD as Master (on either cable). CDROM does not kick in at all. Despite it being set as first boot device.
    3. If HD set as Slave or Cable select. CD ROM kicks in, But does not go into the blue install screen for XP. Just blank screen after it checks for system configuration.

  • Cannot Post After Live Update of BIOS

    System: MSI K8NGM2-FID, 4 gig Corsair, AMD 4400 X2, EVGA 7800GT, 4 Seagate 160 SATA II drives in RAID 0, HP 740vi, Sony floppy, CoolerMaster 810 Stacker case, PS Power & Cooling Turbo 510/SLI.
    I just assembled the system. It POSTed fine. I installed Windows XP (SP 2), NAV 2006, Linksys USB network card, MSI LiveUpdate. I updated the BIOS 3.0 to 3.1 using Windows through the Live Update and making a rescue disk. Nothing remarkable about the update. System will not POST i.e. nothing shows up on the screen although the lights on the Corsair memory go through the appropriate cycle and the keyboard lights shine as usual. Attempted to restore from rescue—can get the disk read using control home: still no POST. Same result after using the BIOS reset switch on the board.
    I get no automated to my message to MSI online tech support.
    What can I do?

    try shutting off, disconnecting the power cord, removing the CMOS battery, tap the power button a few times to discharge any residual power, then leave the battery out for a couple of minutes, before refitting it, then reconnect the power cable, power back on, enter BIOS setup and re-enter BIOS settings

  • MSI GT70 0NC-070NE problems with KLM and S-Bar after Live Update

    Hey there.
    Last night i decided to update my laptop with the newest drivers, so i launched Live Update and got startet.
    When it was done with all of the updates, and had rebooted, both S-Bar and KLM wouldn't start. I clicked the button to have windows try and fix it online, but it didn't help.
    After that i tried to update them to the newest version, and that didn't help either.
    Is this a know issue, or am i just unlucky? Can it maby be solved with installing Win8, as im doing that in a few days from now?

    Quote from: MicHead on 26-January-13, 18:25:53
    Hey there.
    Last night i decided to update my laptop with the newest drivers, so i launched Live Update and got startet.
    When it was done with all of the updates, and had rebooted, both S-Bar and KLM wouldn't start. I clicked the button to have windows try and fix it online, but it didn't help.
    After that i tried to update them to the newest version, and that didn't help either.
    Is this a know issue, or am i just unlucky? Can it maby be solved with installing Win8, as im doing that in a few days from now?
    Make sure you have installed also NET Framework before you use KLM and S-Bar and I really don't recommend to use Live Update, if you want to update your drivers to the latest just go to the manufacurer's website in download section. Don't forget to choose your version of windows before downloading!
    http://www.msi.com/product/nb/GT70-0NC.html

Maybe you are looking for