VOGONS


First post, by Socket3

User metadata
Rank Oldbie
Rank
Oldbie

Hello Vogons.

A few months ago I bought an Acer Aspire 9920G. It is a big boy(tm) with a stunning 20" screen and decent specs. My unit came from the same place I get 90% of my retro gear, a recycling center. It came complete sans HDDs, but would not power on. Slight corrosion on some of the screws, it has clearly been sitting outside for a while. I opened it up, gave it a good clean, re-paste, and managed to diagnose several faults.

One of the ram sticks was bad. The other gives errors in memtest. Both have been replaced. The CMOS battery is flat and for some reason shorted. The machine will only post with the CR2016 removed. Easy enough to source a replacement. The video card is MXMII - an 8600GT - and it suffers from Bumbgateitis, as most mobile GPUs of this time period do. It will come alive if I blast it with heat for a few minutes. It seems getting it to 50C causes something to expand and make contacts, causing the machine to post. I was even able to install windows. Unfortunately it is not game or 3dmark stable - it will lock up after the first two 3dmark01 tests requiring a reboot. If I let it go completely cold it refuses to work until I heat it to around 50-60C with my heatgun. So i shelved the machine and started occasionally looking online for a well priced replacement.

Luckily, a week ago I found an individual in Hungary who sells several brand new sealed 9600GT 512MB DDR3 in the same form factor, apparently Acer branded - so I grabbed one for 30 euro shipped. I installed it into the 9920g, and here's where all the issues began.

At first the Laptop would only display on an external monitor, and would show a warning message on POST:

"ERROR MXM Structure not found or Invalid. Reflash MXM ROM or add MXM Structure and associated callbacks to SBIOS! Post will be halted for 30 seconds and performance will be limited to Ballanced mode until this is resolved"

followed by a countdown. After 30 seconds the laptop will post and boot into windows - on external display only. Driver would not install either, and forcing the driver to install caused the PC to lock up at boot.

I looked online and found a modded unlocked BIOS witch removes this message and apparenty allows for the use of any MXMII GPU - but there is a catch:

The attachment Screenshot 2026-06-10 223313.png is no longer available

https://www.bios-mods.com/forum/Thread-Acer-9 … deo-restriction
https://www.bios-mods.com/forum/Thread-Acer-9 … deo-restriction

As user Netroller from bios-mods forum pointed out, the laptop's built in display lacks EDID pins (why ACER? what was the point?) and to make matters worse, the internal LCD uses a 24-bit VESA FPDI protocol instead of a more common OpenLDI link format. This causes the LCD to not be detected in windows (it shuts off as soon as the driver loads) and when it does run (if I don't connect an external display and only until the driver loads - OR if I go to control panel and force-enable the second display) it shows this corruption:

The attachment corruption 2.jpeg is no longer available
The attachment corruption.jpeg is no longer available
The attachment running.jpeg is no longer available

So far I have been fooling around using an external display, but this defeats the whole purpose of the laptop.
The fix would be, as far as I can understand, adding something to the 9600GT's video bios or modifying it to "hardcode the correct 24-bit encoding type" into the new card's video bios so that I can use the laptop with it's built in display.

Does anybody have an Idea how to do that?

I have the original video card and could probably heat it up one more time and dump the video bios, but flashing it onto the 9600GT won't work, and I don't have the technical skill to dissect it's bios or mod the 9600GT bios... '

The attachment 9920g 8600.jpeg is no longer available

Can any of vogons resident BIOS gurus help with that?

Last edited by Socket3 on 2026-06-15, 11:28. Edited 6 times in total.

Reply 1 of 4, by PcBytes

User metadata
Rank l33t
Rank
l33t

For anyone looking - there are some archived modded BIOS files made by .NetRoller from the (now defunct) NotebookReview forum.

Attaching the link here as it covers several other models (including a few which I own, namely 5720G, 5920G and 7720G, all which were previously plagued by the same defective GPU as Socket3)

https://mega.nz/folder/iJ5FwAoR#PqYOcbC_r9dciJ5sut6AfA

As far as I can remember - to flash them, extract WinPhlash (or the Insyde flasher, IIRC they were SFX packages but I have to check) from the main Acer executable, then replace the WPH/ROM file with the modified one. WinPhlash usually doesn't check for the checksum IIRC and thus will flash whatever file it is fed.

Alternatively, download a standard copy of WinPhlash (32bit, I do not the slightest recommend doing it under x64.), and once opened, point to the WPH file (or ROM file, depending on model) that corresponds to the laptop. Or the DOS variant of PhoenixBIOS (as 9920G is one of those to use Phoenix as far as I know, and the WPH format further solidifies this) but I have less experience with that one (as most flashing I used to do was done on a low-level Hiren's Boot live WinXP environment.)

WARNING - 6920G and 8920G files are recommended to be flashed via external programmer. I have presonally tried those two and ended up with bricked boards due to the flashers and not the BIOS files themselves. DOS flashers also have the same weird issue and it only happens with these two specific models.

"Enter at your own peril, past the bolted door..."
Main PC: i5 3470, GB B75M-D3H, 16GB RAM, 2x1TB
98SE : P3 650, Soyo SY-6BA+IV, 384MB RAM, 80GB

Reply 2 of 4, by Socket3

User metadata
Rank Oldbie
Rank
Oldbie
PcBytes wrote on 2026-06-10, 20:47:
For anyone looking - there are some archived modded BIOS files made by .NetRoller from the (now defunct) NotebookReview forum. […]
Show full quote

For anyone looking - there are some archived modded BIOS files made by .NetRoller from the (now defunct) NotebookReview forum.

Attaching the link here as it covers several other models (including a few which I own, namely 5720G, 5920G and 7720G, all which were previously plagued by the same defective GPU as Socket3)

https://mega.nz/folder/iJ5FwAoR#PqYOcbC_r9dciJ5sut6AfA

As far as I can remember - to flash them, extract WinPhlash (or the Insyde flasher, IIRC they were SFX packages but I have to check) from the main Acer executable, then replace the WPH/ROM file with the modified one. WinPhlash usually doesn't check for the checksum IIRC and thus will flash whatever file it is fed.

Alternatively, download a standard copy of WinPhlash (32bit, I do not the slightest recommend doing it under x64.), and once opened, point to the WPH file (or ROM file, depending on model) that corresponds to the laptop. Or the DOS variant of PhoenixBIOS (as 9920G is one of those to use Phoenix as far as I know, and the WPH format further solidifies this) but I have less experience with that one (as most flashing I used to do was done on a low-level Hiren's Boot live WinXP environment.)

WARNING - 6920G and 8920G files are recommended to be flashed via external programmer. I have presonally tried those two and ended up with bricked boards due to the flashers and not the BIOS files themselves. DOS flashers also have the same weird issue and it only happens with these two specific models.

wow, thank you for the link!

There's a 9600GT bios file there "9600mgt-ddr3-9920g.rom" that seems, judging by the name, to be made specifically for the 9920g. I'll try flashing it when I get home from work. Thanks loads!!!

Reply 3 of 4, by Socket3

User metadata
Rank Oldbie
Rank
Oldbie

Unfortunately neither of the bios or video bios files made any difference to my machine beyond what I've been able to find myself....

- The 9600mgt-ddr3-9920g.rom file is identical to the BIOS file already flashed to my 9600m GT. I managed to flash it with nvflash 5.56, then rebooted, still no image on the internal display. When forced on, the internal display image is corrupted just like before. Nvflash tells me this file and the video bios on my card are identical.

- The "CV120_MXM_V3_BETA.WPH" made no difference. Pheonix flash complained it's the same version as CV120_MXM_V2.WPH witch I found on bios-mods.com. I force flashed it anyway. No change.

I've managed to get the 9920's original 8600m GT going again just so i can dump it's bios - I've done so both with NVFLASH and with GPU-Z:

The attachment G84_M_9920g_gpu-z.zip is no longer available

- GPU-Z dump

The attachment g84m_9920g_nvflash.zip is no longer available

- NVFLASH dump

I've also dumpled the video bios of my 9600M GT, but since for all intensive purposes it's identical to the one in the link provided by @pcbytes, I'll just link that file for convenience:

The attachment 9600mgt-ddr3-9920g.zip is no longer available

I've read about modders deconstructing BIOS files and editing them - if anyone here has this skill, please help. As far I know, to get my 9920's internal display going, the 9600gt bios needs to be modified so that the 9600m will drive the LCD via 24-bit VESA FPDI protocol instead of OpenLDI. This information should be included in the attached 8600m gt video bios dumped from my laptop's defective GPU.

Here is some extra information @pcbytes managed to uncover from nbreview archive:

NOTE: If you have a 9600M GT or similar card, that works with the Microsoft standard VGA driver, but produces a lockup/BSOD/black screen as soon as you install recent Nvidia drivers, read this. This is a known bug in Nvidia drivers, and a workaround is available in the form of a VBIOS patch. This is not a problem with the BIOSes in this thread.

Greetings!

I think I found the reason behind GeForce 9600M GT's reluctance to work with Acer Aspire 5920G/6920G/8920G laptops. Apparently it all boils down to a corrupt MXM structure in the BIOS.

The 6920G and 8920G <s>share the same BIOS</s> EDIT: They actually use different BIOSes, despite containing the same motherboard (though the MXM structure is the same in both), and indeed, their symptoms are also the same: no display on the internal LCD during POST. However, connecting an external display to the HDMI port allows POST messages to show up on that screen.

So, I looked into the MXM structure embedded in the 6920G's BIOS (armed with the recently leaked specification for the MXM structure), and found the following:
The output device structure for the HDMI port of the 6/8920G is 0x00F9F78A2120, which parses to:
Device type: TMDS (DVI or HDMI)
DDC port: DDC-B (MXM pins 230 & 232)
Connector: HDMI Type A socket
Connector location: External
Link type: Single-link DVI/HDMI connected to TMDS link A
HDMI audio source: No audio
Digital signal drive strength: Normal
Digital reserved field 1 (2 bits, should always be 11): 01 (incorrect, violates the MXM spec!)
Output select GPIO: None
DDC select GPIO: None
Device detection GPIO: #0, active low (logic low on GPIO pin 0 indicates a display plugged into the HDMI port)
System hot plug notification: Disabled

The culprit is apparently Device detection GPIO (marked in red), which is presumably always low/0 on this machine, indicating a device plugged in! Because the boot display order is VGA first, then HDMI, finally internal display; connecting a display to HDMI (or fooling the MXM VGA into thinking one is connected, as it is happening now) suppresses POST display on the internal LCD, and directs it to the HDMI port. When Windows finally boots up, it recognizes the internal display and makes it primary (Windows always considers the internal display primary by default, regardless of the MXM structure), so display in Windows is normal.

So, the MXM VGA basically thinks that an HDMI display is plugged in all the time, and proceeds to make that imaginary display primary.

The 5920G (and its little brother, the 4720G) fares even worse: it flat out refuses to POST with a 9600M GT plugged in! Again, a quick look at the MXM structure (hidden in BIOSCOD02.ROM inside the BIOS image) reveals that something is amiss, even more so than with the 6/8920G:
-The checksum of the MXM structure is wrong.
-On this notebook, the boot display preference order is different: internal first, then analog VGA, then HDMI, and finally TV-Out. So, the problem is not the same as with the 6920G. However:
-The internal display's output device struct claims that the internal display can also produce sound through a SPDIF connection, and that the link between the internal panel and the computer is long-distance, requiring extra signal power. A field identified as "reserved, set to all ones" is set to all zeros.
-According to their respective output device structs in the MXM structure, the VGA, HDMI and TV outputs are all internal connectors.
-The VGA output has a "TV format" field set to NTSC-M, despite not being a TV output. The Digital Connection field is set to "Reserved for future uses, do not use" instead of "Not applicable".
-The HDMI link again has the reserved field zeroed out.
-The TV out is identified as an HDTV YPbPr component output, but the TV format is "legacy 525-line NTSC-M" (should be "480i" for an HD connector). And again, Digital connection is "Reserved for future uses". But here comes the real bummer:
-All outputs (including the internal display!) mark GPIO#0 for device detection, interpreting logic 0 as Connected, and 1 as Disconnected. This is wrong in many ways, e.g. one GPIO line can only be used by one display; the internal display has no device detection (it is always plugged in); the board has no GPIO expander, so GPIO#0 doesn't even exist, and is always read as 0; and finally the HDMI output also marks this GPIO as its Output selection GPIO - which is impossible, as a GPIO can't be in more than one mode at the same time.
-The MXM connector claims to be MXM-HE, capable of delivering 3.2W to regular and 12W to HE cards. I the reality, the connector is MXM-II, so it doesn't support HE cards at all; and I'm pretty sure it can handle more than 3.2W when dealing with regular Type II cards. (I've modded this one to 32W.)
-The final two fields are a vendor-specific field for PCI\VEN_0401 (a nonexistent vendor), and a weird 4-byte field that appears to be completely random junk. Disassembling BIOSCOD02.ROM in IDA revealed that this field is not really junk - it is the beginning of the x86 machine code that responds to MXM interrupts. Apparently when the BIOS was built, the end of the already-wrong MXM structure got overwritten with BIOS code!

I've made an attempt to fix these errors, but I have no Acer 5/6/8920G to test them, <s>so the following modded BIOSes are untested</s> Update: 6920G+9600M GT confirmed working by lizzarddos, 5920G confirmed by multiple users to help 9500M GS, 9600M GS and Quadro cards, 5920G + 9600M GT confirmed by u6b36ef, 9920G personally tested by me, so there is no reason why the 4720G would not work.

(BIOSes last updated 2011-05-29.)
Aspire 4720(Z)G (Phoenix): request download ticket | ifile.it
Aspire 5520G (Phoenix, with unlocked menus): http://ifile.it/bi2qtc6/IC50133_MXM.WPH
Aspire 5720(Z)G, 7720(Z)G (InsydeH2O, with unlocked menus and integrated EFI shell, probably fixes external display issues, updated 2011-11-24): http://ifile.it/3wlxm6j/icl50_1.45_black_edition_40.fd
Aspire 5920G (Phoenix, with unlocked menus, updated 2011-11-06): http://ifile.it/noxplab/5920G_MXM_V3.WPH
Aspire 6920G (Phoenix, with unlocked menus): <!--request download ticket | ifile.it previous: -->request download ticket | ifile.it
Aspire 8920G (Phoenix, with unlocked menus): <!--request download ticket | ifile.it previous: -->request download ticket | ifile.it
NEW! Aspire 9920G (Phoenix, with unlocked menus, updated 2011-11-06, use with driver v275.33 and these VBIOSes): http://ifile.it/ej0c3oi/CV120_MXM_V2.WPH
Extensa 5620G, Travelmate 5720G (Phoenix, with unlocked menus, experimental): request download ticket | ifile.it Link fixed 2012-03-28
<s>iFile.it folder containing all current BIOSes: BIOS Mods | ifile.it</s> This folder contains newer BIOSes than the ones above, and one of them (5920G) has produced a bad flash. Consider these to be beta BIOSes until further notice!
Please test them and report any results here!

Note: <s>The 5520G, 7520G and 9920G are affected, too - however, the BIOSes on these machines don't contain an MXM structure at all, so unless someone figures out how to add an interrupt handler for INT 15h, EAX=0x5F80 to BIOSCOD02.ROM, they cannot be patched. (Note: Even if someone finds the interrupt handler for INT 15h, EAX=0xE820 - memory map, that would be of great help.)</s> 5520G and 9920G are available now. The 5520G BIOS may also work on the 7520G, but this is untested.

The Aspire 5720G (ICL50) BIOS is NOT required for 9600M GT upgrades - it primarily fixes issues with ATI cards refusing to drive external displays. It is also usable on Aspire 5315, 5320, 5715(Z)(G), 5720(Z)(G), 7320, 7720(Z)(G) and eMachines E510 machines, including IGP ones, to unlock extra tweaking menus. It does not, however, enable upgrading IGP ICL50s to MXM cards - that is still physically impossible.

Thanks,
.NetRolller 3D

Help me bring this Chonky boy back!

Reply 4 of 4, by Socket3

User metadata
Rank Oldbie
Rank
Oldbie

[UPDATE]

I'm not making any headroom with this issue whatsoever. Here's what I've done so far:

- I flashed the 9200g with both modified BIOSes, one I've discovered using google, one in the link provided by @PcBytes. These are unlocked bioses witch 1. remove the "MXM Structure missing" warning from the POST siquence and 2. Provide a series of advanced bios options that are usually hidden. Some are very handy. None of these BIOS files actually fixes the problem with the on-board display not working correctly. These files are CV120_MXM_V2.WPH and C120_MXM_V3_BETA.WPH. I couldn't find any difference between the two when it comes to my issue.

- I flashed the "9600mgt-ddr3-9920g.rom" onto my new video card. This has disabled the internal display completely. Before, with my 9600m gt's stock video bios, after updating my 1.10 bios with the CV120_MXM _V2 file, my laptop would post and display on the on-board screen, but the colors would be wrong, corrupted, and as soon as the GPU driver loaded the internal display would shut off. I could use the laptop by connecting an external display to the VGA port. After flashing this video bios the internal display refuses to work at boot. Turning my laptop on with no external monitor would result in no display whatsoever. I do not understand the point of this rom - in my opinion it's a step back.

Where I'm at right now: I kept the CV120_MXM_V3_BETA bios and rolled back to my original video bios, the one that came with my new 9600m gt, since that at least allows me to see something if I turn the laptop on with no external display.

I had an AI inspect the stock 9920g G84m (8600m gt) bios and compare it to the G96m bios to see what was modified by ACER to get an MXM card working with teh 24 bit panel - and the AI said the cards are different generations and contain different display table data. I also tried tu use an AI to help me modify a video bios using a HEX editor, so that it would make the video card use the 24-bit VESA FPDI protocol instead of defaulting to OpenLDI link format witch the on board 20" display does not support. Problem is I can't flash the modded bios - every version of NVFLASH I've tried so far gave me a "please use a newer version of NVFLASH" - a common error when trying to flash a modified bios and one I can't seem to get around.

What I mean to try next: - somebody on some forum back in the day suggested trying to include de video bios from the MXM card into the laptop's main BIOS. I don't think that will fix the display corruption tough, I think that was a fix for the "MXM stucture" error - but I'm thinking it might be worth a shot.