Unsolved

This post is more than 5 years old

3 Posts

1211

May 2nd, 2017 08:00

AW13-R2 and Graphics Amp

Okay, so here is my twisted tale.

I bought an AW13-R2 and graphics amplifier soon after they were introduced.

I then got a really nice Nvidia GX970, or something like that ( and have since updated to a 1060). Everything worked as it should. Unit booted up no problem in any configuration I had it in. With GA attached, or without. Perfect. 

so as time goes on, the OS became bloated and slow, as it is known to do. Windows 10.

I then got an AW13-R3 , but that's another story.

I decided to reset the OS back to factory, and start over again, in an effort to regain it's former performance.

Now, after I had reset the OS, and downloaded all the stuff I needed (Office/Blizzard/drivers/etc) when I plug it into the GA, the boot up says I need to repair the OS.

So I let this go for awhile, and all it ever did was reboot, and display the same message...a loop of reboot hell..

Frustrated, I disconnected the GA, and it boots fine.

Reconnect the GA and back into repair OS loop HELL.

So, I decided to try just putting it to sleep, THEN connect the GA.

A message appears, saying GA was installed correctly, and to reboot.

Reboot THEN works great. GA and laptop function as before.

But, after any reboot after it has been connected  it goes back into Repair Loop Hell....

Remove the GA, reboot, sleep, reconnect, message appears, reboot, it works.

Reboot any other time, back to Repair loop Hell......

Any suggestions??

I have been pretty diligent to make sure to use the current drivers, and such, and BIOS is all updated as far as I can tell.

I have a system information report if that might help.

Thanks.

1 Attachment

3 Posts

May 2nd, 2017 09:00

Yes, that is what has appeared to fix it, even though It was already installed (:) but re-installing it seems to have fixed the reboot loop. The really strange thing is, a I mentioned in the OP that after a sleep and reconnect/reboot it DID work, just after a complete system reboot is when it failed. So I guess it is good to know LOL

9 Technologist

 • 

4.4K Posts

May 2nd, 2017 09:00

Hi, 

Is your system running the latest Bios? When you reinstalled Windows, did you use a recovery media tool?

28 Posts

May 2nd, 2017 09:00

Update: Just saw your reply to Rodrigo, my suggestion was same: install the GA software, hope it's fixed.

3 Posts

May 2nd, 2017 09:00

I did. I have also verified that the BIOS is current.

However, I have just had a successful boot, after I re-installed the GA software. I hope this fixes it.

I will keep you informed.

Thanks

28 Posts

May 2nd, 2017 09:00

Hi Gshadoan,

When you  re imaged the system, did you update all drivers? (obvious questions perhaps, but like to double check)

Not sure if you installed this one:

http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=NX9DF&fileId=3561423476&osCode=WT64A&productCode=alienware-13-r2&languageCode=en&categoryId=AP 

As well, install the Graphics driver for the laptop video card only, without the GA connected, then reboot and install the driver above. There is no need for separate drivers for the GA Video card.

Lastly I would run Windows updates, since it's a fresh install, in case you haven't yet.

Hope it helps.

28 Posts

May 2nd, 2017 09:00

Computers have mysterious ways? hahaha well not sure, maybe because the sleep state did not completely interrupt the current on the port as it would from a re boot? But yeah, good to know  

No Events found!

Top