HP G70-250US BIOS Manufacturer and version

Hi,
I have a HP G70-50US Laptop that won't boot and need to know the BIOS maker (i.e. AMI Award etc.) and version so I can lookup the codes for a Power On System Test Card.
Thank you.

Hi hp_edm, welcome to the HP Forums. If your computer is very slow after the BIOS upgrade, are you still able to boot into Windows? You could first try to restore the BIOS using this method: HP Notebook PCs - Restoring the BIOS
If that doesn't help, try a hard reset using this method:  Performing a Hard Reset or Forced Reset
If it is still slow, test your hard drive using this method:  Testing a Hard Disk from the BIOS
Let me know how that turns out.
TwoPointOh
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom to say “Thanks” for helping!

Similar Messages

  • Include OS and DB manufacturer and version as well as MDM version

    Hi all,
    I am sure you will all agree that it will be easier to respond to messages if we all could include the following:
    1) Server OS manufacturer and version
    2) DB manufacturer and version
    3) Client (GUI or Web)
    4) MDM Version (this is in the format 5.5.xx.xx)
    Do you agree?  If so please do so when you next post.
    Thanks all

    Hi Charles,
    I like this proposal. Especially the MDM Version is very helpful if anyone wants to recreate the problem on a local PC. Additionally it makes sense to add this info because of the release of MDM 7.1. MDM 7.1 has a lot of changed as well as additional functionality compared to MDM 5.5. It's easier to answer a question if it's clear, what the question is about.
    Cheers
    Michael

  • Satellite A660 - BIOS links and version history

    Just for your knowledge please find below the complete *A660 BIOS version history*:
    _[Version 1.80 - 2010-10-01|http://cdgenp01.csd.toshiba.com/content/support/downloads/saw0v180.exe]_
    - Limited the DDR3-1333Mhz DRAM speed to 1066Mhz. on Clarksfield CPU platforms.
    - Updated: The SM_SENSE# status is kept during deep sleep mode for the Sleep & Music function.
    _[Version 1.70 - 2010-09-22|http://cdgenp01.csd.toshiba.com/content/support/downloads/saw0v170.exe]_
    - Fixed: Background turns blank, and the wrong password won't clear automatically when setting or deleting a User or Supervisor Password.
    - Fixed: System will hang when setting a 512 byte owner string.
    - Fixed: When Fast Boot was enabled, DMI Type12 had no data.
    - Fixed: When Fast Boot was enabled, the system did not ask for the HDD and system passwords.
    - Fixed: When PCI LAN was disabled, the boot menu reported a network issue.
    - Fixed: When a RAM module's serial number is all zeros, the system will hang.
    _[Version 1.60 - 2010-08-03|http://cdgenp01.csd.toshiba.com/content/support/downloads/saw0v160.exe]_
    - Updated the Intel OSB logo.
    - Fixed: Shared memory allocation issue on UMA SKUs.
    - Fixed: Blurred Toshiba logo.
    - EC-1.60: Reduced the sensor button debounce time to 50ms.
    _[Version 1.50 - 2010-07-08|http://cdgenp01.csd.toshiba.com/content/support/downloads/saw0v150.exe]_
    - Updated the Intel MRC to 1.3-1 for Warm boot shutdown issue.
    _[Version 1.40 - 2010-06-28|http://cdgenp01.csd.toshiba.com/content/support/downloads/saw0v140.exe]_
    - Updated the N11M and N11P NVIDIA VBIOS code base.
    - Updated the Clarksfield CPU Microcode to M13106E5_04.
    - Fixed: The computer may hang if certain RAM modules are used in Computrace platforms.
    _[Version 1.30 - 2010-06-09|http://cdgenp01.csd.toshiba.com/content/support/downloads/saw0v130.exe]_
    - Updated the N11E Nvidia VBIOS for 3D SKUs.
    - EC-1.30: Added a workaround to fix an ALS function issue after resuming from S4/S5 and restarting.
    _[Version 1.20 - 2010-06-03|http://cdgenp01.csd.toshiba.com/content/support/downloads/saw0v120.exe]_
    - Added: N11E Nvidia VBIOS for 3D SKU.
    - Updated the Computrace option ROM to fix a problem installing and running SysMark/MobileMark.
    _[Version 1.10 - 2010-05-10|http://cdgenp01.csd.toshiba.com/content/support/downloads/saw0v110.exe]_
    Initial production BIOS for these models.

    Hey,
    Thats interesting list but as PauPau wrote, the same you can find on Toshiba US page.
    I dont have additional information about version history but I can confirm that newest version 1.80 works properly. I use it since 2 months now and dont have any problems.
    Especially Satellite A660 is a great computer and it was a very good decision to buy it. :)

  • G70-250US notebook synaptics mouse pad will not work & keyboard will only work until I log onto pc

    I have a G70-250US model notebook with Vista 32. I decided to reload OS due to issues with mouse pad and keyboard. I still have the same problem whereby the mouse pad will not work and keyboard will only work until I log in and then it will not work.  External mouse and keyboard will work fine.  I tried uninistalling drivers for both and rebooting and letting OS find new hardware and install the drivers and this still did not correct.  I even pulled down the synaptics driver from HP site and still not working.  I checked the BIOS and it is the most recent. I am at a loss. Any ideas on these issues. 

    Ok I tested a bunch of different Firefoxes on my pos linux box.
    '''''Worked with xmodmap:'''''
    Vanilla 16.0.2,
    Vanilla 16.0B6,
    Ubuntu Firefox 16.0.2 (16.0.2+build1-0ubuntu0.10.04.1)
    '''''Did Not Work with xmodmap:'''''
    Vanilla 17.0.1,
    Ubuntu Firefox 17.0.1 (17.0+build2-0ubuntu0.10.04.1)
    I have an old Dell Dimension 2400 I plan to use as a replacement for the Sony Vaio when it pops. I've held out as long as possible because it lacks a pci or usb wifi and I really didn't want to run 50 feet of cat5 up a flight of stairs to it. [as i type this i think i remember where a linksys stick for it might be]. Yes I guess it's about time I just do that.
    Don't laugh but the reason I held off adding a simple usb keyboard was just lack of space in my tiny bedroom. My setup is on two tray tables side-by-side. Sony Vaio is on left one, my lcd monitor and mouse are on the other. I barely have room to put a cup of coffee on the one with monitor and mouse let alone a full size usb keyboard lol.
    Anyway thank you again for all your help.

  • Bios Flashing and Recovery

    BIOS FLASHING
    We do not recommend using the MSI LiveUpdate tool to update your BIOS! It may be okay for updating your drivers, but please do not use it to flash the BIOS in Windows!
    Windows-based flashing - If you REALLY insist on flashing the BIOS under Windows, if you encounter any error during flashing, whatever you do, DON'T restart your PC! Try again until the flash is successful, otherwise your board will not start! Disable any anti-virus program (along with any other programs) prior to flashing.
    Boards with built-in M-Flash function - While M-Flash work's properly most of the time, it has still proved to be less reliable than the forum tool / manual flash.
    Before flashing your BIOS, you must ensure your system is fully stable! Any instabilities can cause a bad flash and create an expensive paper weight. Included with the forum flash tool is MEMTEST, we recommend running this for 2 or more passes prior to a flash.
    If you do not understand what your BIOS is, or what it does, please read: >> BIOS. What it is, and all you need to know <<
    Our first choice we recommend you use is our own USB flashing tool, developed by Svet.
    It is important to note, that the only way to flash the ME extension of the BIOS of modern Intel boards is through the use special processes. The bios versions posted by moderators here: >>BIOSes<< include the additional files to accomplish this. These bios are all official and are directly from MSI.
    >>>MSI Forum HQ USB Flashing Tool<<<
    If you are unable to use the MSI HQ USB BIOS Flashing Tool
    >>How to create a dos bootable USB stick>>
    It is important to note that if any BIOS, EC FIRMWARE or any other type of FIRMWARE downloaded from MSI for a manual flash contains an BAT file it must be used. Not doing so will cause the flash to fail and require RMA.
    For Intel Users, flash via FPT
         Socket LGA 1150           : >>ME 9 FPT files & Instruction>>
    Many of the bios versions posted here: >>BIOSes<< Contain a .bat file. All you need to do is extract all of the contents of the archive into the root directory of a DOS bootable USB stick and run the bat file from pure DOS.
         Socket LGA 1155 & 2011: >>ME 7&8 FPT Files and instruction<<
    Linux users
    See this topic: >>Flash your BIOS, the Linux way! [beware the dangers!!]<<
    Modified and BETA BIOSes
    Use only at your own risk! All BETA BIOS versions posted by the moderators of this forum are directly from MSI and will not effect your warranty.The use of user modified BIOS versions may damage the board and may void your warranty. Exercise extreme caution in regards to user posted BIOS versions. Please also be aware that MSI and this forum can not be held responsible if you trash your mobo by using a modded, beta or otherwise incorrect BIOS.
    WHEN IT ALL GOES WRONG...
    BIOS RECOVERY
    In many cases, provided the 'bootblock' of your BIOS is not corrupted during a bad flash, the BIOS can often be recovered by following the recovery procedures detailed below. NOTE: this recovery method should not be followed for normal practice of updating your BIOS!
    For Modern MSI Systems, refer to:
    <<Multi-Bios Equipped Mainboards>>
    <<Single-Bios Equipped Mainboards>>
    Legacy Systems:
     For Award BIOS
    Make a bootable floppy disk*
    Copy the Award flash utility & BIOS file to the said floppy disk
    Create an autoexec.bat with "Award_Flash_Utility BiosFilename" in the content (e.g. awdfl823K w6378vms.130)
    Sample on how to create an autoexec:
    a. On Windows, open the notepad
    b. On the notepad, write "awdfl823K w6378vms.130" (without the " ")**
    c. Save the file as autoexec.bat
    Boot up system with the said floppy (it will take less than 2 minutes before screen comes out)
    Re-flash the BIOS & reboot.
    *Need a bootable floppy disk? Look here: http://www.bootdisk.com
    **Make sure you enter the correct filenames for your flasher program and BIOS ROM file!
     For AMI BIOS
    Rename the desired AMI BIOS file to AMIBOOT.ROM and save it on a floppy disk. e.g. Rename A569MS23.ROM to AMIBOOT.ROM
    Insert this floppy disk in the floppy drive. Turn On the system and press and hold Ctrl-Home to force update. It will read the AMIBOOT.ROM file and recover the BIOS from the A drive.
    When 4 beeps are heard you may remove the floppy disk and restart the computer.
     For new boards with AMI BIOS core 8 (4MB)
    Discovered by Jack The Newbie:
    Of course, the steps are similar to the standard AMI BIOS Recovery Procedure for internal floppy drives (rename corresponding BIOS File to AMIBOOT.ROM, hit CTRL + HOME after starting the system).
    What has to be done (tested on P45 Platinum):
    1. An optical SATA Drive needs to be connected to one of the Intel ICH10R SATA ports. {After a lot of testing, I found that it does not work with the same optical drive connected to the SATA Ports hosted by the secondary JMicron Controller.  Also, using an optical drive on the JMicron IDE/PATA port does not help either.}
    2. A proper BIOS File has to be renamed to AMIBOOT.ROM and burned on an empty CD.
    3. CMOS-Clear with main A/C power cable removed from PSU has to be performed. {If this step is not done, the system will reboot after pressing CTRL + Home and will not proceed with recovery procedure.}
    4. Press CTRL + Home to trigger BIOS Recovery.  -> The system should enter BIOS Recovery Routine. {Will basically work with both USB & PS/2 keyboard.  However, a PS/2 Keyboard is recommended as the system will respond earlier to PS/2 Keyboard than to USB Devices.}
    What should happen now:
    1. After pressing CTRL + HOME the LED Status should change to "Intializing Hard Disk Controller" and there should be access to the optical drive connected to the Intel ICH10R SATA ports.
    2. It can take up to 30+ seconds until the BIOS File that was renamed to AMIBOOT.ROM is found. {Drive Bay can be opened to try a different CD without turning off or restarting the system.}
    3. When the system finds the BIOS File, LED Status will change to "Testing RTC" and there should be a message on the screen indicating that the Flash Recovery Procedure has started.
    4.  Since the BIOS File is 4MB in size, it will take a while until the BIOS is actually reflashed.
    Its also possible that BIOS recovery on boards with AMIBIOS8 can be done using a FAT-formatted USB stick, containing the renamed BIOS file. Be warned, in some circumstances it may take several moments before recovery procedure actually begins. See Bas' reply below for further information.
    BIOS recovery on Wind netbooks
    See this post here:
    https://forum-en.msi.com/index.php?topic=130509.msg982711#msg982711
    BIOS recovery on non-UEFI notebooks
    In order to recovery this type of system you will need an FAT32 formatted USB stick.
    Download the applicable bios from MSI's website and rename this bios.
    It must be re-named to either AMIBOOT.ROM or xxxxIMS.ROM / xxxxAMS.ROM  You may need to try each way to determine which one is necessary.
    Then place the renamed bios onto the root directory of the FAT32 formatted USB stick.
    Now you are ready to cover the Notebook.
    To do this, remove the AC power cord and battery. Once that has been completed, install the USB stick you prepared earlier.
    Now, apply AC power (leaving the battery disconnected) and turn on the notebook. Recovery should begin after 5 minutes.
    IF ALL ELSE FAILS...
    Locate the BIOS chip on your mainboard. If it is soldered directly to the PCB like...
    ...then you have no choice but to return the board to your supplier, or to MSI, for replacement.
    To request an RMA from MSI, open a support ticket at https://register.msi.com/ocss/
    If your BIOS chip is in a socket, like...
    ...then you may be able to source a replacement BIOS chip, either from MSI, or from a website such as www.badflash.com
    Updated 11/21/2013, original post by Stu

         A.) Download >>this<< bios archive and place it on your desktop. Do not decompress.
         B.) Download and install the >>MSI HQ Forum USB flasher<< .
         C.) Insert your FAT32 formatted usb stick.
         D.) Make sure that all win 8 options are disabled. (Fast Boot etc) Also make sure the legacy USB is enabled.
         E.) Start the forum flash tool and select option 1. Then point the tool at the compressed archive we downloaded earlier. Then to your USB Flash Drive.
         F.) Boot to the USB from working bios B.
         G.) Once it booted successfully switch to bios A without powering down or rebooting
         H.) Now follow the directions and let the tool flash bios A with desired version

  • G70-250US Notebook - sleep issues in Win7?

    I just bought the G70-250US... my first notebook ever after 15 years of computing.  The very first thing I did (after creating recovery discs of course) was format the drive and put Win7 RC1 (x64) on it.  It runs great now and I have no HP bloatware.  I got all the latest drivers from HP and Intel.
    99% of the time the sleep and wakeup work fine.  However, I have noticed if I close the lid and let it sleep for a long time (8+ hours, while I myself and ALSO sleeping), that when I open the lid to wake it in the morning, it will appear to wake up, but the display will remain blank, and I will need to force it asleep a 2nd time (through power button or lid) and then wake it a second time, and then it will function fine, display and all.
    Is this a known issue, or is it perhaps just a compatibility issue with Win7?  Does it happen in Vista?  I can't really check since I wiped Vista off so fast. :-)
    Thanks!
    Message Edited by The111 on 09-25-2009 12:06 AM
    Message Edited by The111 on 09-25-2009 12:17 AM

    One more thing I noticed... when waking up after a long sleep, it briefly displays the HP logo and then the Windows resume screen... and THEN the screen goes black and will not come back unless I sleep it a second time.  So it almost seems to be a display driver issue, maybe?
    EDIT: Incidentally, Windows update just found a display driver update released yesterday.  We'll see if that fixes it...
    Message Edited by The111 on 09-25-2009 06:15 PM

  • H97M-G42 stuck at boot with BIOS 7925v25 and 7924v26

    I am in a loophole with the MSI H97M-G43 Motherboard.
    I would not recommend this motherboard to anyone planning to play with ESXi
    Bios v21 v22 v23 v24 would not recognize quadport lan adapters such as Intel PRO/1000 VT or Intel PRO/1000 PT.
    In Bios they will appear us "Unrecognized Manufacturer" and there is no option to enable hardware from unrecognized manufacturers
    Bios v25 v26 would recognize PRO/1000 VT hardware but would refuse to but OS.
    Very very confusing and unstable situation.

    Update:
    Bios v25 & v26 are unable to initialize 32GB of RAM, thus creating boot issues.
    16GB RAM work just fine.
    Bios v21,v22,v23,v24 would handle 32GB of ram without any problems.
    Wow..... MSI

  • Bios updated and now K8N Neo won't boot? FIXED!

    Successfully restored from backup (after some hassles!), but thanks to everyone who helped.
    Having messed with the bios some more, I *think* I now know what the problem was.  And *blush*, I think it was my fault all along *blush*.
    I think I had one of the drives selected at the top in Hard Disk Boot sequence, instead of the SCSI - Raid Array.
    That would mean it was only reading half the MBR at boot time which would kindof explain the problems I was having.
    Still, we live and learn.  Thank God for backups!
    Cheers all
    Chippy
    I hope someone can please help me?
    I just upgraded my K8N Neo2 bios from 1.4b to Easybios 1.3c (or whatever its called).
    I took all the proper precautions and the bios update itself has worked just fine. My system is "working" OK.
    However, I can't boot. The system POSTs fine, detects the raid0 array just fine and then falls over with an MBR 1 error and an MBR 3 error.
    I booted from the XP install CD and loaded up recovery console, and I can log on to the array. The array and all data is fine.
    So it looks like its just the MBR record that is screwed. Is this because of some incompatibiliy between my old and new bios?
    And anyway, please does anyone know how to fix it? I suppose I can try to rebuild the MBR somehow, but I don't know how. And I really DO NOT want to risk losing all of the data on the array. Yes, I have a full back up, but I don't want to end up having to rely on it!
    Has anyone seen this problem before when doing a bios update? And any ideas how to fix it?
    (I guess I could flash back to 1.4b, but I really would like a later bios version to go with my new - as yet untested - Opty 146).
    Thanks

    Thanks for the tip, Doc.  But I have entered the bios settings from scratch.
    I can try it again, but why do you think that might work?  There really aren't two many sata and raid settings to make - all you have to do is enable the two channels (sata3 and sata3) and then enable them also in the raid menu.  That's it.  And the board "sees" the raid array just fine, its just it won't boot anymore.  I can read and write to the array no problem from Windows Recovery Console, so I conclude that the hardware is all working properly.  I think its an MBR incompatibility issue between the two bios versions... or maybe MBR corruption.
    I seem to remember some people having problems with this a year or so ago when upgrade this bios from 1.4 to 1.5.  Some people were having to do complete Windows reinstalls to fix it.  That was why I didn't update my bios sooner.
    But I asked around this time and it seemed those problems had been resolved.
    Seems I was mistaken!
    Any other thoughts / suggestions?
    Thanks
    Chip

  • MSO PRO-E 7522 BIOS confusion and persistent BSoD

    Hi there
    A few months ago I switched from 775 to 1366.
    Components changed:
    CPU (from Q9550 to i7 950)
    MOBO (from Asus P5QL PRO to MSI PRO-E
    RAM (From 8gb 800Mhz DDR2 to 12GB 1333Mhz DDR3 ADATA)
    PSU (from Antec 550W to Cooler Master Ultimate 900W
    +1 GFX card (Another ATI XfX 5870 Black Ed.)
    I did not overclock the old system and I haven't overclocked my current system.
    Now the thing is, I've been having bluescreens ever since I got that MSI PRO-E.
    I've tried: switching RAM (since it said 1 was faulty), switched harddrives, reinstalled windows +/-6 times and looking for driver updates.
    Now finaly I went looking at the BIOS.
    Since I got a new PRO-E I remembered that I had no idea what version of the BIOS was running.
    It seems that currently version 8.C0 is running.
    Now I need to know if it matters that I've got the 8.xx BIOS version while running a crossfire setup.
    Because I've read this:
    Version 7.xx (7.3 is supposed to be the latest) supports Crossfire
    Version 8.xx (8.E is supposed to be the latest) supports SLI.
    Now I understand that 7.3 won't support SLI, only crossfire.
    But does version 8.xx support both SLI AND Crossfire? Or am I simple messing up my computer because I've got a wrong BIOS version?
    BSoD info:
    problem continues to be caused by: ntkrnlmp.exe I think.
    Well the first blue screen does not:
    Loading Dump File [C:\Windows\Minidump\010711-24296-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02a54000 PsLoadedModuleList = 0xfffff800`02c91e50
    Debug session time: Fri Jan  7 08:06:29.587 2011 (UTC + 1:00)
    System Uptime: 0 days 0:29:44.806
    Loading Kernel Symbols
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    Loading User Symbols
    Loading unloaded module list
    *                        Bugcheck Analysis                                    *
    Use !analyze -v to get detailed debugging information.
    BugCheck 3B, {c0000005, fffff880048e3817, fffff88006ffd8e0, 0}
    Probably caused by : atikmdag.sys ( atikmdag+90817 )
    Followup: MachineOwner
    Second blue screen:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Windows\Minidump\010711-22531-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02a0d000 PsLoadedModuleList = 0xfffff800`02c4ae50
    Debug session time: Fri Jan  7 08:36:18.533 2011 (UTC + 1:00)
    System Uptime: 0 days 0:28:46.626
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    *                        Bugcheck Analysis                                    *
    Use !analyze -v to get detailed debugging information.
    BugCheck 1A, {41790, fffffa8000496e00, ffff, 0}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
    Followup: MachineOwner
    I have also tried: registry cleaner countless times. though it sometimes did find stuff I don't think anything could relate to some shortcut which the program thought to be useless but was actualy referring to the windows debugging program. And even without regsitry faults (being detected) it crashed.
    So I just need to knowL could it be my BIOS version + Crossfire = blue screen
    If not.. any idea's?
    Details system info:
    OS:  Microsoft Windows 7 Ultimate x64 (Tried with and without updates and service pak, these bluescreens are from this morning while I was @ school.
    CPU: i7 950
    Mobo: MSI PRO-E 7522
    RAM: 12 GB ADATA 1333 DDR3 (listed as supported)
    Graphics Cards:
    ATI XfX 5870 Black Ed. 1GB.
    ATI XfX 5870 6 Eyefinity Black Ed. 2 GB (as main card)
    (I know, not an ideal combination but the 1gb card will be replaced)
    2x 1TB Samsung Hard drives
    PSU: Cooler Master 900-1080W
    Casing: Cooler Master HAF922
    System @ stock speed, I do not overclock!

    Quote
    Ah, ok so its already running at 1066?
    Yes.
    Quote
    CPU-Z showed 530.5
    CPU-Z always shows the real frequency.  Because of the DDR architecture (Double Data Rate) there are two transactions per clock cycle.  That means 530.5 MHz effectively translates to 530.5 x 2 = DDR3-1061 [~DDR3-1066].  The small difference (DDR3-1061 vs. DDR3-1066) can have two causes:  The Base Clock Speed is either not set to 133 MHz in BIOS Setup and/or Spread Spectrum in Enabled and causes small clock speed deviations.
    Quote
    Then what would you have me do now?
    Leave the memory frequency setting @DDR3-1066.  It is better for testing anyway.  You can worry about that later.  The only thing you may want to check is the Base Clock speed (make sure it is set to 133 MHz in BIOS) and the Spread Spectrum setting (disable it).

  • G470 BIOS shutdown and restart problem 40cn33ww_64 2.19

    Hi there, please kindly help me. I have Lenovo G470 Notebook. with Core I3, 8GB RAM, 500GB HDD, Bios Version 2.19 (Updated)actually, after i updated to 2.19 bios version i got these problem. when i click shutdown. the Disk stops but the the power still running.when i click restart (on battery) my notebook goes to shutdown completelywhen i click shutdown (on adaptor) my notebook goes to restart. first i think this is about OS, i try all OS but it remain the same problem.please give me a solution. thanks.

    samidt wrote:
    Hi CB, i'm very appreciating your effort to solve my problem
    I tried your way to press OKR key when my laptop is Off.
    What i got is, i go to my win10 logo. Not to bios one
    And when i'm on my desktop, there's no other thing than my ordinary desktop.
    FYI, before i get the win10 logo, i got the black screen with F2 to bios and F12 to select boot order. But i prefer not to press it.
    Its just like the same with pressing power button to power on my laptop.
    Any idea how to solve it CB ?
    I'm familiar with laptop stuff. So maybe you can show me how i fix it myself.
    Big thanks CB
    Just a couple of questions to clear up my understanding of the situation - bear with me.
    Before you installed Windows 10, did the power button respond normally and were you able to see your BIOS pages?
    Also - when you installed / upgraded to Windows 10 was it a "clean install" or did you follow the upgrade path?
    If you were able to operate the notebook with the power button prior to installing / upgrading to Windows 10 I would try booting from a "live DVD" for Linux (Mint / Ubuntu / Fedora) to see if it works in that situation.  If it works as expected in Linux then we have a Windows OS issue to deal with.
    If you performed a "clean install" of Windows 10 it may have wiped out the factory partition (hidden) on your hard drive and going back to factory settings may not be an option.
    Cheers.

  • HP G70-250US Vista Audio problem

    HP G70-250us, Vista Audio Problem

    Hello ricinfl,
    Welcome to the HP Forums!
    I understand you are experiencing the computer audio not working. I created a troubleshooting guide on how to resolve the issue: Audio does not Work after a Certain Period of Time
    Please provide your results and feedback. If the issue is not resolved, please clarify it. Thanks!
    Mario
    I worked on behalf of HP.

  • Bios upgrade and spontaneous shutting down

    Hi, I have an s10e, and recently upgraded my bios to 96 version. Right after the upgrade, the computer started shutting itself off without any notification. The shutdown is basically sudden, seems to happen just randomly, but usually takes less than 10min after starting up. Any suggestions/help would be much appreciated. It is a very annoying problem and my computer is practically not usable. I suspect it is the low treshold CPU temperature settting, but the bios does not have an option to manually change this. The fan control programs I got from this website did not help either. Help! Please!

    Hi and welcome..
    to extract is there a hardware issue or software issue... the answer isnt  easy
    in normal case... there isnt a dependency of updating BIOS or not... But when u use a program that tried to manipulate hardware special or something.. that could be run into failure...
    Starting in BIOS ... press F2 to to get in BIOS press F9 to load setup defaults... change some values you want/or not .. for example Config site ... Quickstart on/off Beep AC On/off ... BOOT settings
    Fn-F7 to activate numlock via +/- arrange USB CD to first USB HDD to second HDD to third.. then leave BIOS with F10 save and exit...
    Starting windows ... and reduce start up programs to prevent that a program could do the unattended shutdown...
    How to do that   XP Startup
    after this procedure...look is there a wrong setting in  Lenovo Energymanagement  ...
    ...still shutdown ... temperature ? getting warm ?
    download coretemp to watch temperature ... >over 65 C there is something wrong...
    then you can call your local service ....
    if temp is not so warm .. and still shutdown ...could be other problem...
    sincerely KalvinKlein
    Want more ? For further information to get the most of your S-Class machine
    Lenovo Energymanagement 
    Backup
    Windows 7  
    Clean XP Install
    XP Startup
    Small WebCam Guide
    Lenovo Easy Capture
    Resolution > 1024 x 576 / 600 
    Thinkies 2x X200s/X301 8GB 256GB SSD @ Win 7 64
    Ideas Centre A520 ,Yoga 2 256GB SSD,Yoga 2 tablet @ Win 8.1

  • Does the BIOS 68MSU ROM Version F.0A support Penryn?

    Hello,
    I would like to know if the BIOS 68MSU ROM version F.0A (release date: Nov 05, 2008) will support the Intel Penryn processor. I know for sure this BIOS will supports Merom but does this version also supports the newer Penryn. The Service Manual is of limited used as it was released in mid 2007 which is before the release of Penryn (release date early 2008). Any assistance would be greatly appreciated. Thanks.
    Regards,
    Tze

    I tried to install windows 7driver while in Windows 8  which it didn't like and locked in error loop, long story short I had to do factory Windows 7 restore install my needed programs then upgrade to Windows 8. I took screen shots of device manager in Windows 7 because there was unknown device that was listed in General Tab Microsoft ACPI-Compliant System that with previous install could not figure what device it was other than ACPI power management and Windows 8 took the Generic Microsoft ACPI-Compliant System driver. This time I compared to the screenshot still could figure out what was missing so I looked at the unknown device driver Details Tab and saw several references to ACPI\HPQ6001. I did a Google search and found that referenced: ACPI\HPQ6001="HP Wireless Button Driver" but the checked the HP website and there is no Windows 8 driver. My apologies if in haste about the Bios update. I can't confirm or prove it is the bios up to this point until HP completes the job because it's still half done. The bios update may as stated by HP "Provides support for the Microsoft Windows 8 wireless button controls" but without the Windows 8 drivers to work in conjunction with the bios fix the bios update is still useless and half complete because the intended problem was not fixed. I'm figured out the problem now it's left to HP to complete and I hope it does not take too long for them to create drivers to fix the problem.

  • MSI H81M-E33 BIOS Issues and Post Flash Issues

    Hello,
    My situation is as follows: (TL:DR at bottom)
    Built a new computer and decided to use the new LGA 1150 refreshed CPUs. Bought the MSI H81M-E33 Motherboard and installed windows. Noticed a problem with the rebooting even when installing windows. Thought it was just because of the windows installation, but problem persisted in which the computer seems to shut down but doesn't power down and i have to manually hold power button to power down and then push it again to start up. No real issues it seems since the computer does close processes and shut down but this was irritating me. I read online that BIOS updates seem to fix this problem. Did some research and decided to update with M-Flash to bios v6.6.
    As I used M-flash to update to BIOS (selected "Select one file to update BIOS and ME") v6.6 the update stops at 47% and then the computer attempts to restart. BUT it still has the same problem and does not power down. So I manually powered down and started it back up. I then got "no signal" even as I waited. Now I'm freaking out and I power it down again and try again. This time I wait and it get to BIOS (MSI Screen) and then no signal again (not booting windows). Again I hold power down and power back on. Long wait again and I get back to bios. Still freaked out at this point but relieved I didn't brick motherboard.
    Decide to flash v6.5 in case 6.6 was too new and might some problems. However v6.5 has the same problems; bios update stops at 47%, computer attempts to reboot, can't reboot, I power off, power on, no signal, power off, power on, wait a while and it gets to BIOS (MSI Screen), then boots to windows.
    Right now the bios does read the bios version as v6.5 but I still have the issues in restarting where that doesn't really work. In addition, I now have this wait from pushing the power button to when I see BIOS (MSI Screen).
    TL:DR
    Had reboot problems decided to update BIOS
    Used M-flash ("Select one file to update BIOS and ME") to update to v6.6
    Update stopped at 47%, computer attempted to reboot, got no signal (reboot problem), powered off, powered on, waited a long time nothing, freaked out, powered off, powered on, waited a while got to bios (Whew), checked for new version (it is).
    Decided v6.6 might be too new decided to try v6.5 used M-Flash again
    Again stopped at 47%, computer attempted to reboot, got no signal (reboot problem), powered off, powered on, waited a long time, nothing, powered off powered on, waited a while got to bios, checked bios for new version (it is), save and exit, no signal, power off, power on, waited a while got to bios, then booted into windows
    My concerns are;
    I seem to still have reboot issue.
    I have to wait for BIOS now, no longer pretty quick start.
    My questions are;
    Did I mess up the flashing somewhere?
    Was stopping at 47% normal?
    Should I try to update the BIOS another method to fix my current problems?
    Am I missing a step somewhere?
    Any help is appreciated, I just got really freaked out by the whole process but I'm just glad the computer still works (kinda).
    Thanks in advance for any help, and apologies on the long essay just wanted to be as specific as possible.
    -J
    Specs:
    MSI H81M-E33
    Intel i5-4590
    Corsair CX-430
    Crucial Ballistix Sport 8GB
    PNY Optima Series 240GB
    Seagate Barracuda 1TB
    LG 12x BD-Rom
    Microsoft Wireless Desktop 2000

    MFlash reboots in the process. To be sure reupdate using the below instructions and archive for a proper fpt flash. If you used Win8 feature (fastboot) before the first update be aware taht you need to set anything again after an update (e.g. enabling safeboot) as everything is set to default.
    >>Use the MSI HQ Forum USB flasher<<
         A.) Download the attached archive (E7817IMS_660.rar.rar) and place it on your desktop. Do not decompress.
         B.) Download and install the Forum flash tool.
         C.) Insert your FAT32 formatted usb stick.
         D.) Make sure that all win 8 options are disabled. (Fast Boot etc) Also make sure the legacy USB is enabled.
         E.) Start the forum flash tool and select option 1. Then point the tool at the compressed archive we downloaded earlier. Then to your USB Flash Drive.
         F.) Boot to the USB 
         G.) Now follow the directions and let the tool flash
         H.) After flashing reinstall ME drivers in Windows:  http://download.msi.com/dvr_exe/intel_amt90_mb.zip

  • Satellite L840 - BIOS update and blue screen

    Hello,
    I recently bought a Toshiba L840-04E (PSK8LA- O4E007) and installed Windows 7 64bit.
    Issue: BlueScreen
    Question: I assume this is the dreaded "blue screen of death" and I need to do something to prevent servious problems in the future (I've used the laptop lightly for a couple of days with no issues).
    How do I analyze the dump information to find out what caused the blue screen?
    Or is it best to go back to the last restore point before the blue screen event? A restore point was made before I updated the BIOS from v 1.80 to 6.20. Also, Toshiba shows that there is a new BIOS 6.30 version.
    Before the blue screen event I had changed the setting for the on/off button to "shut down" and made a few minor other changes to settings and then just before the blue screen error I plugged in a Seagate External Hard Drive.
    Are there any suggestions about what steps I should take?
    Thanks so much.
    April

    Hi
    Generally the BSOD appears due to serious software problem or hardware problem.
    You said you connected an external USB HDD to the notebook right before the BSOD appeared so probably the BSOD was caused by the attached HDD who knows
    If this happened for the first time, dont be afraid it could be just a temporal problem
    But if it would appear often, you should investigate a little bit and should try to replicate the issue and the reason for that

Maybe you are looking for