Alienware Graphics Amplifier with 40 Series GPU's

[Maxware79]

Someone posted this on Reddit this week so it may be helpful for some of you.

 

 

 

[ssj92]

Just to copy/paste in the event that post ever gets deleted or something:

 

Further reading of experiences around the AGA in this and other forums, made me even try the plug and unplug technique proven to work by some users with the 3000 series (https://www.dell.com/community/Alienware/PCI-e-3-0-x4-for-ampere-3080-3090-question/m-p/7894720#M43691), however I had no luck until I did the following:

• Uninstalled AWCC using Revo uninstaller (advanced scan and deleting found entries is mandatory after uninstalling)

• Restarted system

• Uninstalled Nvidia drivers

• Restarted system

• Installed the Chipset INF utility

• Restarted the system

• Located the following subkey in regedit HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\PnP\Pci

• Generated the HackFlags entry with a value data of 200 as depicted here (https://learn.microsoft.com/en-us/troubleshoot/windows-client/deployment/error-attach-pci-express-expansion-chassis)

• Reinstalled Nvidia drivers using the latest package

• Restarted system

• The card was still being detected as “Microsoft Basic Display Adapter”, so I uninstalled the Nvidia drivers

• Restarted the system

• Generated the HackFlags entry with a value data of 400 as previously described (this value worked for me)

• Reinstalled Nvidia drivers

• Restarted the system

• After restarting, the card was outputting video and recognized as NVIDIA GeForce RTX 4070 Ti

• Reinstalled the latest AWCC

• Restarted the system

• After restarting, the card and AGA were also being recognized in the AWCC

 

Important notes:

1. The HackFlags entry never worked for me until I uninstalled the NVIDIA drivers each time I modified the subkey; for this reason I suggest testing systematically the 200, 400 and 600 values always uninstalling and reinstalling.

2. Apparently AWCC can interfere with process since I tried everything depicted below and it did not work until AWCC was uninstalled.

3. The AGA and card were connected to my laptop the whole time

[aldarxt]

On 1/12/2023 at 4:29 PM, ssj92 said:

Just to copy/paste in the event that post ever gets deleted or something:

 

Further reading of experiences around the AGA in this and other forums, made me even try the plug and unplug technique proven to work by some users with the 3000 series (https://www.dell.com/community/Alienware/PCI-e-3-0-x4-for-ampere-3080-3090-question/m-p/7894720#M43691), however I had no luck until I did the following:

• Uninstalled AWCC using Revo uninstaller (advanced scan and deleting found entries is mandatory after uninstalling)

• Restarted system

• Uninstalled Nvidia drivers

• Restarted system

• Installed the Chipset INF utility

• Restarted the system

• Located the following subkey in regedit HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\PnP\Pci

• Generated the HackFlags entry with a value data of 200 as depicted here (https://learn.microsoft.com/en-us/troubleshoot/windows-client/deployment/error-attach-pci-express-expansion-chassis)

• Reinstalled Nvidia drivers using the latest package

• Restarted system

• The card was still being detected as “Microsoft Basic Display Adapter”, so I uninstalled the Nvidia drivers

• Restarted the system

• Generated the HackFlags entry with a value data of 400 as previously described (this value worked for me)

• Reinstalled Nvidia drivers

• Restarted the system

• After restarting, the card was outputting video and recognized as NVIDIA GeForce RTX 4070 Ti

• Reinstalled the latest AWCC

• Restarted the system

• After restarting, the card and AGA were also being recognized in the AWCC

 

Important notes:

1. The HackFlags entry never worked for me until I uninstalled the NVIDIA drivers each time I modified the subkey; for this reason I suggest testing systematically the 200, 400 and 600 values always uninstalling and reinstalling.

2. Apparently AWCC can interfere with process since I tried everything depicted below and it did not work until AWCC was uninstalled.

3. The AGA and card were connected to my laptop the whole time

Could the AWCC interfere with other mxm cards like the Aetina_MXM_M3N1080 or the A4500 that you had a problem with. I have been having a problem with the Aetina_MXM_M3N1080 not working in the m18x r2 and m17x r4. I am going to try again but remove AWCC and see what happens.

[ssj92]

3 hours ago, aldarxt said:

Could the AWCC interfere with other mxm cards like the Aetina_MXM_M3N1080 or the A4500 that you had a problem with. I have been having a problem with the Aetina_MXM_M3N1080 not working in the m18x r2 and m17x r4. I am going to try again but remove AWCC and see what happens.

No. I ran aetina 1080 perfectly fine in aw18 and awcc is installed. also works in m18xr2. 

[aldarxt]

3 hours ago, ssj92 said:

No. I ran aetina 1080 perfectly fine in aw18 and awcc is installed. also works in m18xr2. 

Thanks anyway but I just tried again in the m17x r4 and the GTX 1080 just won't work. I get code 43 and searched around again and nothing works. Tried uninstalling AWCC and OSD also Intel HD Graphics 4000 just to see what happens. The BIOS sees the 1080, so does GPU-Z but very limited info. The drivers install fine even tried standard drivers but they would not even allow it. This is why it gets scairy buying cards. I just had another goof-up buying a GTX-1070 for the P870DMG-3 and the guy sent me a GTX-1080. Now I have 2 different cards for it and can't run in SLI. I am thinking of asking if I could return the 1080 in exchange for a 1070. But maybe I should just flash the BIOS and get a 2080 or 3080 IDK!