BSOD Win7: bios in this system not fully ACPI compliant


Recommended Posts

I have a Gateway GT5694 (Details: http://support.gateway.com/us/en/s/PC/R/1015569R/1015569Rnv.shtml )

I have been running it with 4gb ram using Win7 for a few years, and it was time for an upgrade. So I checked the specs to get the correct memory and ordered a SSD drive(Waited SO long for one of these) I shut the system down, grounded myself and added the two new 2gb chips. Booted up, checked BIOS and now 8gb ram. Save BIOS settings, reboot and then a BSOD: "The bios in this system is not fully ACPI compliant" WTH? <sigh> Okay, shut down, remove the new two chips, reboot, check bios, 4gb, reboot and.... BSOD. I have tried running the setup from the original Win7 disc and with "safe mode" from disc (F7) but no luck. I ran the F7 test memory function (with the original 4gb) and it shows no issues. but no matter what I try I get this BSOD.

The BIOS update from Gateway does not contain the file necessary for a boot disc... and the instructions say to run the process from withn Windows (although there is a batch file...)

Thoughts?

I created a bootable dvd with Nero 9 and yet... I cannot access the files from the dvd. WTH?! The dvd boots up (DR DOS, wow that's a blast from the past!!!!) and gives me an a: prompt (this really is a blast from the past) I cannot access the dvd from which the computer boots up from. This is becoming amazininly stupid. There must be some way to fix this issue.

Anyone?

What you are getting is not a BSOD, you are not even making it into Windows, as it sounds.

Might be having RAM voltage problems. Can you verify that all chips are 1.5V or 1.6V?

Also, has this happened since you put the RAM in, or after you put the SSD in? Did you try removing the SSD and just trying the RAM or vice versa?

Try this from MS:

http://support.microsoft.com/kb/831691


  1. Insert your Windows XP CD-ROM into the computer's CD-ROM drive or DVD-ROM drive, and then restart your computer from the CD-ROM.
    Note Some computers may require that you modify the basic input/output system (BIOS) settings before you can start the computer from a CD-ROM. For information about how to modify BIOS, see your computer documentation.
  2. When the "Welcome to Setup" screen appears, press R to start Recovery Console.
  3. If your computer is configured for dual booting or multiple booting, select the relevant Windows XP installation.
  4. When you are prompted to do so, type the administrator password, and then press ENTER.
    Note By default, the administrator password is blank in Windows XP Home Edition.
  5. By default, Hiberfil.sys is typically located in the root directory (C:\). At the command prompt, type del hiberfil.sys, and then press ENTER.
  6. Restart the computer

What you are getting is not a BSOD, you are not even making it into Windows, as it sounds.

Might be having RAM voltage problems. Can you verify that all chips are 1.5V or 1.6V?

Also, has this happened since you put the RAM in, or after you put the SSD in? Did you try removing the SSD and just trying the RAM or vice versa?

Actually I am getting a BSOD, I did mention it above, but I tend to talk to much. Currently I have the older hard drive and only the 2 original RAM chips. So everything is as it was before I installed the new RAM, which is why I am so frustrated

Davo,

I have tried using the Win8 and Win7 discs to get to recovery console (I saw that article too, thank you though) I will dig up an XP disc this morning and see if that will work. What happens is that Windows copies files and when it gets to the point where the "Welcome to Setup" is going to start... I get the BSOD. ARG!

Thanks to both of you for the feedback.

Ok so this is doing this even though you have removed the two new bits of ram?

Also is it a Legit copy of windows?

is it this screen your getting?

4dfd642c60aa1.jpg

have a look at this link

http://airtechproductions.blogspot.co.uk/2011/10/bios-in-this-system-is-not-fully-acpi.html

Haggis,

Yea my discs are all legit (no harm in asking) but what the article you linked to mention is that the disc needs to have SP2 or 3, so I found another disc that had that service pack and the F7 key works. The first round I tried to use recovery console, but it's not taking my admin password. NBD. I will install XP, update the BIOS and then see if I can add the new RAM back, then the SSD drive and then install Win8. What a fun day ahead. I will update this as to the result in case anyone else needs this info someday.

Well, I was able to install XP but the BIOS update available from Gateway gives an error, a vague worthless error: "problem freeing mapping bios" I think it's time to get a new machine.

At least the XP via F7 to bypass the ACPI issue was successful *IF* using a disc with Service pack 2 or greater.

The sad thing is, I gave up and purchased a new Gateway and then had to spend 7+ hours talking with their tech support in order to boot from dvd so I could replace the hd with a SSD, which I was told I could not upgrade the machine. Because the app included with the system could not create a backup/restore drive (it would pause at 99%) I was told to buy restore media from them. That's right, I should purchase Restore Media because THEIR software didn't work. <sigh> I was able to escalate the issue and get the discs for free.... except that they were out of the discs... for a brand new model.

The new Gateway system would have been a decent system for the price so long as I didn't want to upgrade it. I just gave up on the process since simple tasks took SO long.

Details:

* The Gateway site for my new model stated that F2 was the key for getting into the BIOS... it's the DEL key.

* Setting DVD/CD drive as the boot will not boot to that device until several other settings are set.

* The Windows 8 Key is now within the firmware for OEM machines (so says MS and Gateway via a converence call) so I could not use the ISO that I purchased from MS of Win8 to install to a blank drive.

* Gateway tech support do not read what the user enters into the chat session. eg: I said I was using their software and it does not complete and was given a URL on how to use the software. Um.... I'm doing that!

* When the issue is escalated to a Level 2 tech, the tech does not bother to read what is already typed forcing the user to restate/retype what is already been said.

I have ordered a ASUS motherboard and a new CPU and memory and I am back building my own system. Thanks for the feedback and my bitchiness about Gateway... I will state again that my older Gateway worked fine for 3 years and the new one SEEMED good. As long as you don't plan to upgrade these systems could be fine.

  • Eric locked this topic
This topic is now closed to further replies.
  • Posts

    • Mp3tag 3.35 by Razvan Serea Mp3tag is a powerful and yet easy-to-use tool to edit metadata (ID3, Vorbis Comments and APE) of common audio formats. It can rename files based on the tag information, replace characters or words from tags and filenames, import/export tag information, create playlists and more. The program supports online freedb database lookups for selected files, allowing you to automatically gather proper tag information for select files or CDs. Mp3tag supports the following audio formats: Advanced Audio Coding (aac) Free Lossless Audio Codec (flac) Monkeys Audio (ape) Mpeg Layer 3 (mp3) MPEG-4 (mp4 / m4a / m4b / iTunes compatible) Musepack (mpc) Ogg Vorbis (ogg) OptimFROG (ofr) OptimFROG DualStream (ofs) Speex (spx) Toms Audio Kompressor (tak) True Audio (tta) Windows Media Audio (wma) WavPack (wv) Mp3tag 3.35 changelog: This version introduces a new Files options page, enhanced toolbar customization, support for RF64 WAV files, improved Discogs and MusicBrainz tag sources, and many other improvements and fixes. See the Release Notes for more details. Download: Mp3tag 64-bit | 5.7 MB (Freeware) Download: Mp3tag 32-bit | 5.2 MB Link: Mp3tag Homepage | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • The FIFA World Cup is not US centric.
    • It’s amusing how Microsoft is pushing IT admins as if this was a major, game-changing update. In reality, it’s just an enablement package that bumps the build number, which is disappointing compared to the more substantial 22H2 and 24H2 releases. Technically, 25H2, 26H1, and the upcoming 26H2 are essentially the same, differing only in support schedules. They could have included the Windows K2 improvements here, but chose not to. The era of Windows being in the backburner continues, and this 26H2 release feels like an afterthought. Shame, Nadella, shame.
    • Microsoft, totally not confusing /s 25H2 - Current for non-Arm based Windows 26H1 - Current for Arm based Windows 26H2 - Only for non Arm Windows
    • After I installed those, my older but capable Win 11 laptop (16GB RAM) reported it as 26H2 26300.8697. Then I installed it on my big laptop (128GB RAM! Hehe sorry), it reported it as 25H2 26220.8690. Ugh. Do I have to switch Insiders channels from Release to Beta?
  • Recent Achievements

    • Week One Done
      AMV earned a badge
      Week One Done
    • One Month Later
      AMV earned a badge
      One Month Later
    • Collaborator
      ryansurfer98 went up a rank
      Collaborator
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      523
    2. 2
      +Edouard
      174
    3. 3
      PsYcHoKiLLa
      78
    4. 4
      Steven P.
      72
    5. 5
      Michael Scrip
      71
  • Tell a friend

    Love Neowin? Tell a friend!