Sound Blaster Recon3Di Defect Discussion Thread - Questions/Solutions Here [M18x R2, M17x R4 Audio]

Install the original package available from Dell Support Drivers & Downloads. This will include the Sound Blaster Recon3Di control panel. You can install the downloaded updates and use the "have file" option device Properties tab from within Device Manager and browse to the newer drivers manually. Or, you can run the setup.exe file in the updated package. If you do not see a setup.exe, look in one of the cab files. I know one of the updates I had to manually extract one of the .cab files and found the setup.exe file there. If you run the setup.exe version of the updated driver, choose the option for custom installation and de-select everything except for drivers. The Creative Updater often does not work well for me. Choose the "Automatic" update from Device Manager almost never works for me. That's why I download them and use the "Have Disk" option from Device Manager.

 

You see Mr Fox, that's what I did.. I must be getting the wrong file.. Would you be able to point me in the right direction?

Thanks

 

Here is how to get the Creative Sound Blaster Recon3Di Control Panel working again for the M14xR2, M17xR4 and M18xR2:

• Download: Audio_Creative_W84_X03_A00_Setup-W39M6_ZPE.exe [10-26-2012, v6.0.100.2039 - works for Windows 7/8/8.1]
  or Audio_Creative_W814_X01_Setup-4T7P8_ZPE.exe [10-09-2013, A00 v1.00.19 - released for Windows 8.1, does not install on Windows 7]
• Download: Phyxion Driver Sweeper v3.2.0
• Uninstall your Creative Audio Stuff in Add/Remove Programs, Reboot into Safe Mode
• Launch Driver Sweeper in Safe Mode and check the box for Creative, scan and remove everything Creative, Reboot
• Install the Dell Sound Blaster Recon3Di linked above, choosing the custom option and be sure everything is selected
• At this point you should have a fully functional Sound Blaster Recon3Di Control Panel and the Microphone Array will be available as a recording device.

The reason the latest Windows Update drivers do not work 100% correctly is they are not designed for our systems. Look at the INF files. You will see that our Alienware hardware ID is not present, and there are significant structural differences in the software, so modding the INF is not enough. There are actually extra features in our Alienware systems and files for those features are missing from most of the drivers. For example, there is no reference to our Microphone Array and that is why this device disappears when using the drivers from Windows Update. If you install the generic driver the audio works, but the built in microphone does not work. In fact, it disappears from the Windows Sound control application.

Spoiler

Creative Sound Blaster Recon3Di [6.0.101.1023, Released 04/08/2014] Source: Microsoft Update Catalog (the hardware IDs noted in red text are not for Alienware)

Creative Sound Blaster Recon3Di [6.0.100.2033, Released 04/30/2012] Source: Alienware / Dell Support (our hardware IDs are noted in blue text)

; ; ; Copyright (C) Creative Technology Ltd. All rights reserved. ; ; Module Name: ; CTHDA.INF ; [Version] Signature="$Windows NT$" Class=MEDIA ClassGuid={4d36e96c-e325-11ce-bfc1-08002be10318} Provider=%CREAF% CatalogFile.NTX86=cthda.cat CatalogFile.NTAMD64=cthda64.cat DriverVer=04/08/2014, 6.0.101.1023 [SignatureAttributes] cthda.sys=SignatureAttributes.DRM CTHRFX32.dll=SignatureAttributes.PETrust CTHRFX64.dll=SignatureAttributes.PETrust [SignatureAttributes.DRM] DRMLevel=1300 [SignatureAttributes.PETrust] PETrust=true [Manufacturer] %MfgName% = Creative, NTAMD64 [ControlFlags] ExcludeFromSelect = * [Creative] %Creative.Device1Desc% = CTDev1, HDAUDIO\FUNC_01&VEN_1102&DEV_0011&SUBSYS_1458A016 %Creative.Device1Desc% = CTDev1, HDAUDIO\FUNC_01&VEN_1102&DEV_0011&SUBSYS_1458A026 %Creative.Device1Desc% = CTDev1, HDAUDIO\FUNC_01&VEN_1102&DEV_0011&SUBSYS_38421035 %Creative.Device1Desc% = CTDev1, HDAUDIO\FUNC_01&VEN_1102&DEV_0011&SUBSYS_38421037 %Creative.Device1Desc% = CTDev1, HDAUDIO\FUNC_01&VEN_1102&DEV_0011&SUBSYS_10197DB5 %Creative.Device1Desc% = CTDev1, HDAUDIO\FUNC_01&VEN_1102&DEV_0011&SUBSYS_1028064C %Creative.Device1Desc% = CTDev1, HDAUDIO\FUNC_01&VEN_1102&DEV_0011&SUBSYS_1462D882 [Creative.NTAMD64] %Creative.Device1Desc% = CTDev1, HDAUDIO\FUNC_01&VEN_1102&DEV_0011&SUBSYS_1458A016 %Creative.Device1Desc% = CTDev1, HDAUDIO\FUNC_01&VEN_1102&DEV_0011&SUBSYS_1458A026 %Creative.Device1Desc% = CTDev1, HDAUDIO\FUNC_01&VEN_1102&DEV_0011&SUBSYS_38421035 %Creative.Device1Desc% = CTDev1, HDAUDIO\FUNC_01&VEN_1102&DEV_0011&SUBSYS_38421037 %Creative.Device1Desc% = CTDev1, HDAUDIO\FUNC_01&VEN_1102&DEV_0011&SUBSYS_10197DB5 %Creative.Device1Desc% = CTDev1, HDAUDIO\FUNC_01&VEN_1102&DEV_0011&SUBSYS_1028064C %Creative.Device1Desc% = CTDev1, HDAUDIO\FUNC_01&VEN_1102&DEV_0011&SUBSYS_1462D882 CT_GUID = "{AC6D33B1-0629-4d06-A0D6-73D896269347}"

; ; ; Copyright (C) Creative Technology Ltd. All rights reserved. ; ; Module Name: ; CTHDA.INF ; [Version] Signature="$Windows NT$" Class=MEDIA ClassGuid={4d36e96c-e325-11ce-bfc1-08002be10318} Provider=%CREAF% CatalogFile.NTX86=cthda.cat CatalogFile.NTAMD64=cthda64.cat DriverVer=03/27/2012, 6.0.100.2033 [Manufacturer] %MfgName% = Creative, NTAMD64 [ControlFlags] ExcludeFromSelect = * [Creative] %Creative.Device1Desc% = CTDev1, HDAUDIO\FUNC_01&VEN_1102&DEV_0011&SUBSYS_10280550 %Creative.Device1Desc% = CTDev1, HDAUDIO\FUNC_01&VEN_1102&DEV_0011&SUBSYS_10280551 %Creative.Device1Desc% = CTDev1, HDAUDIO\FUNC_01&VEN_1102&DEV_0011&SUBSYS_10280552 %Creative.Device1Desc% = CTDev1, HDAUDIO\FUNC_01&VEN_1102&DEV_0011&SUBSYS_10280580 %Creative.Device1Desc% = CTDev1, HDAUDIO\FUNC_01&VEN_1102&DEV_0011&SUBSYS_1028057B [Creative.NTAMD64] %Creative.Device1Desc% = CTDev1, HDAUDIO\FUNC_01&VEN_1102&DEV_0011&SUBSYS_10280550 %Creative.Device1Desc% = CTDev1, HDAUDIO\FUNC_01&VEN_1102&DEV_0011&SUBSYS_10280551 %Creative.Device1Desc% = CTDev1, HDAUDIO\FUNC_01&VEN_1102&DEV_0011&SUBSYS_10280552 %Creative.Device1Desc% = CTDev1, HDAUDIO\FUNC_01&VEN_1102&DEV_0011&SUBSYS_10280580 %Creative.Device1Desc% = CTDev1, HDAUDIO\FUNC_01&VEN_1102&DEV_0011&SUBSYS_1028057B CT_GUID = "{AC6D33B1-0629-4d06-A0D6-73D896269347}"

Go to the Microsoft Update Catalog and search for Recon3Di and you will see the following list:

Spoiler

Notice the hyperlinks in the left column. If you click on the hyperlink it will open a new window with information on the driver. See the examples below.

In order for everything to work correctly, you must look at the details on each driver to determine whether or not that driver has matching hardware ID string for your system.

Unless I missed one, the newest version of the Sound Blaster Recon3Di available from the Windows Update Catalog that applies to our Alienware laptops is v6.0.100.2040 (released by Microsoft on 09-07-2012). The Windows 8.1 driver linked at the top of the page (10-09-2013, A00 v1.00.19) may be Alienware's version of the same driver as this one, but the one from the Windows Update Catalog does not have the Sound Blaster Recon3Di Control Panel. You will need to install the Alienware driver package first, then use the "Have Disk" method to install the v6.0.100.2040 available from the Microsoft Update Catalog.

---

UPDATE: For anyone that wants to test this along with me, I tweaked something in the driver to change the functional power state of the Recon3Di driver. Considering that loss of audio function is frequently restored after putting the machine to sleep and waking it up, my logic is that altering the available power states for the audio chipset might make it behave. I found values in a reference driver for another brand of laptop and modded the INF for our system to see if this change will circumvent the problem we are encountering. Perhaps another OEM discovered this and implemented it as a fix for the audio chipset problem.

I haven't used it long enough to know if it is a cure, but if several of us test it the result would be more conclusive than me doing it on my own. It may affect the M14xR2, M17xR4 and M18xR2 differently, so it would be good if people that have each model can test it. The screen shots in the spoiler below show what I tweaked in the driver INF file.

Here is how to replicate what I have done:

• If you have Windows 7/8 download the first driver linked above (v6.0.100.2039). If you have Windows 8.1, download the second driver linked above (A00 v1.00.19).
• Folllow the cleanup procedure outlined above (using Driver Sweeper) and do a clean install of the appropriate driver.
• Download my modded Windows Update driver using this link, install it through Device Manager using the "Have Disk" method

Everything should be functional, including the Microphone Array... at least it is on my system. Only time will tell if the mod makes any difference. I am crossing my fingers and hoping that it does. As my M18xR2 is a dual-boot setup, I will be testing this tweak on Windows 7 and Windows 8.1 concurrently.

Spoiler

NOTE: If you are running Windows 8/8.1 remember to reboot with Driver Signature Enforcement disabled or the driver installation will fail. This is because I modded the INF file.

For Windows 8/8.1 install using the "Have Disk" installation process, choose the bottom driver (two are listed and you will want the "unsigned" driver... the top one has a digit signature and you don't want that one.)

 

M17xR4 joining the recon3di rehab program FOX

 

Fox, I will be testing your driver mod as well as soon as my schedule frees up to allow me to nuke the R4 and start from scratch. I will be in the market for a m18x R2 if this solves the issue. fingers crossed!

 

One thing I really miss about the 18xr2 versus my 18 is that the sound on the xr2 did sound much fuller vs slightly tinny on the 18

Sent from my Nexus 5 using Tapatalk

 

The Recon3Di is a wonderful card when it works, especially with the klipsch speakers.

Only thing I'm confused about....wasn't BIOS A05 supposed to address this problem? I want to go back and test on that BIOS but because I'm now on A11 and the blind flash method isn't exactly wonderful/guaranteed to work, I'm scared to go back. I'm sticking to Windows 7 so I could care less about UEFI/Secure boot/Fast boot.

 

Yeah, Secure Boot/Fast Boot blows chunks real bad. UEFI is fine, but those other two cancers and Secure Flash have no place on an enthusiast machine... pure garbage IMHO for a gamer/overclocker machine.

 

Sorry to be the bearer of bad news, but your modded driver did not work for me Fox. Audio died after reboot of installing some windows updates (did not install the creative driver from windows update, used the dell driver + yours), which makes me believe even more this was a low level EEPROM programming bug that cannot be fixed with drivers, or else Dell would have done so. To fix it now would involve a recall, which I do not see happening ever. At this point I would be happy going back to a M18x R1 or M17x R3 to just be rid of this problem

 

Oh well... I guess it was worth trying. Sorry it didn't work.

 

Well now going on for a few weeks, no audio issues from the recon3di chip, but then I haven't tried changing output (headphones to speakers)

 

My two cents based on my experience with my two Alienware M18X R2 laptops that I have owned for almost 2 years. Note that I reinstall my OS about once every six weeks.

One M18X R2 laptop has never had any problems, including any of the audio problems discussed in this thread.

My problem child (also M18X R2) is on its third motherboard. I did not experience the audio problems discussed in this thread with either of its first two motherboards, but with my current motherboard (purchased on eBay) my OS fails to recognize my Sound Blaster Recon3Di sound card upon a fresh installation of Windows 7 Ultimate 64 bit 100% of the time.

This problem is solved by turning off the laptop and then closing the lid. Note that I am always on AC power.

Once my lid has been closed and reopened (with laptop turned off), I install driver 6.0.100.2033 and I am in business.

 

Well, I took the ballsy move to downgrade from A12 to A05 via blind flash to see if it makes any difference. So far so good...time will tell.

 

Update. No further improvement with A05 bios. I noticed something though. I wonder if we have access to the various sleep states in the driver. After repeated sleep cycles within 5 minutes of each other, sound always came back. However, it seems after entering a "deep sleep" or an occasional reboot, sound disappears again.

 

When my Recon3Di disappears, putting my system to sleep and waking it back up works 100% of the time to bring it back. In fact, this is the only reason I have ever used sleep functionality on the M18xR2. Rebooting often does not change anything.

What is really odd is I can go for weeks and not have an issue, then it happens a few times in a week, then the problem goes away again for a good while. I cannot identify a use pattern that might affect it, and I have tried to pay attention to identify what might trigger it. It's just really weird. Thankfully, it's not a massive problem. I would much prefer to deal with this random inconvenience than the far worse nonsense on the newer machines.

 

Ahh some user still got this audio issue, it was so annoying i did try all possible solution but no luck. At end replaced my system MB, from that day till today not a single time this issue pop up. I think it is hardware issue and most of first revision MB (M18x R2 and m17x R4) got this issue. if you want to get rid of this issue permanent, better change MB.

 

I've gotten 2 MB changes in the past, both of them were still faulty.

 

My first was not an early R2 mobo and it was recently replaced under warranty. They are both behaving basically the same... seldom have the bug. When it does, it is briefly frequent (a few times in a row spread out over a few days) then mysterious goes away for a spell. It gets better long enough for you to totally forget about it, but then it rears an ugly head again as a brief reminder of its presence. Must be a digital version of what it is like to have a STD, LOL.

 

May be you got old stock. I remember i've tried all possible software tweak non of worked. It's hardware issue, i think Dell released bios A03 specially to fix this issue but it did nothin.

lol it was more than 2 years ago i've started this thread, audio issue gave me headache most of time you got to put into sleep n wake up to fix it. Then i replaced MB, from that day and till today not a single time i had this problem. Now i dont think Dell will ever release any bios update for R2.

 

i know this is an ongoing issue, but has anyone else updated the recon3di drivers with this *.cab file

Microsoft Update Catalog

 

We need more time to figure out if it fixes anything with the dropped audio, but it seems to function OK while it is working. The Recon3Di driver numbering is all over the board. Notice that the driver from April 2013 would appear to be the newest driver based on version numbering. Based on release date it is not, unless Creative released an older driver to Microsoft for inclusion in the Catalog out of sync with the version. It's really strange. Given that owners of non-Alienware systems with Recon3Di have reported similar problems, my suspicion is that Creative's product is inherently bugged and might not be something drivers can fix. But, I will keep on trying different drivers as they become available in hope that it is a driver issue. Thank you for posting the link for others to test it.

Spoiler

 

Well, that is the price we AW uses have to pay for the tech we like,

The drivers seem to have corrected the stability of the taskbar creative control, and will report any other fixes,

 

Well, my audio quit working twice this morning with the .2052 driver from 9/14. So, basically no change. I think it is just a coincidence and not worse than before. I've had no stability issues with the Creative Control Panel, ever, just randomly disappears like unplugging a USB device and immediately comes back after putting the machine to sleep and waking it up again.

*Edit: sleep, wake, working again - didn't stay broken for long

 

Hello guys, I follow this topic by a few months. I dont have a M18x or a M17x, i have a M14x, but the problem is the same. Sometimes when i turn on my Notebook, it have no sound. One thing that i saw in one of the replies, is that this problem is related with the power. So i tried to turn on the notebook in battery, without the power cable plugged. And every time i did this, the sound works. When i forget to unplug the cable, the sound does not works.

Maybe this information can help, and sorry for my bad english.

 

Hello.

I would also like to offer my expirience if it helps anything. My sound blaster is changing its subsystem id when I boot into windows for the first time. Control panel says that no audio device is connected and I have to select another one. Also device manager says I have an "High Definition Audio Device" and has microsoft drivers. Audio is working though.

Upon reboot sound card is OK. Control panel is working , device manager says Soundblaster Recon 3Di and everything is OK.

Once I force installed drivers to the "High Definition Device" and sound was dissapeared. Device manager said "Soundblaster Recon 3Di".

I made a restart and device was gone completely. I closed the lid, open, and there it was. Sound was OK.

Deleted all the drivers, reboot, installed Dells drivers and ever since (a month ago) sound is as follows.

First boot - Sound is working, SB panel not, Device is "High definition Device" with another subsystem id.

Reboot - Sound is working, SB panel is working with the setings I have chosen, Device is sound blaster recon 3Di with the correct subsystem id.

 

@ Mr. Fox after installing .2052 driver, you need to disable the older version of CTAudSvcService, under services. Creative needs to update the Control Panel, the service compatibility issues delays boot on Win8.1/10, win7 no issues.

 

Thanks for the tip, Brother j95. I almost always boot into Windows 7 for everything. I so very seldom ever boot either of those crappy OSes for anything other than a Fire Strike benchmark or to look at something long enough to give advice to a Windows 8.1 user. If I update them I will follow your guidance on disabling those services. I might not even have Creative drivers installed... have to check, but Windows 8.1 and 10 may be running the native generic Windows HD Audio drivers that are included with the OS. My post above regarding the .2052 driver was with Windows 7.

Edit: The screen shot on Nov 7 was also Windows 7. I run a Windows 8 desktop theme because I like the pointy corners on the windows better than the rounded ones, so that along with the flag Start button instead of the round orb button can be very misleading when looking at my screen shots.

 

Yep, disable only CTAudSvcService. I've reported (9841) this many times together with others probably, got the update build 9860 and it was not yet listed under microsoft catalog. I'm hitting them hard with the performance issues on win8.1/10, just adding more performance options, EU means trouble (first performance option), EE. UU. different trouble...

.2052 Audio service

 

I still don't see how these driver updates help. My sound card still dips out when it goes to sleep, no matter what driver version. Still holding out in case dell decides to issue a recall

 

I had 4 m17x R4, 3 m18x R2s. Ane only one of them (a m18x R2) had this problem. No matter what I do, Sound just disappears.
I decided to buy a new board from taotabo and this problem was wiped.
I think it is some hardware issue and it is fixed after sometime because I only had one that had this problem.

 

The drivers make no difference. It has a mind of its own. I am on my second M18xR2 board. The one I have now is about 6 months old and came with A11 BIOS. In both cases the issue is primarily an inconvenience, not a serious problem. It's similar in nuisance factor to the old "plugged in/not charging" issue the M17xR2 is famous for... slide your hand under the front, unlatch the battery for a second, then slap it shut and it's gone. In this case sleep > wake > done. I'm not happy about it, but it's not bad enough to make a huge stink over it. I'd rather put up with minor annoyance like this than have to live with a weaker pile of crap for a laptop. It's kind of like having an incurable squeak or rattle in the dashboard of a muscle car... really annoying, but excusable when you look at the big picture and consider how horrible a performance downgrade would be.

 

I wonder if its possible to solder the IDT chip from the R1/R3 into R2/R4 boards in place of the creative chip, but I don't even know how many pins are on each chip, let alone the abscence of a pinout diagram.

 

That would be a good idea if the audio subsystem is just one chip that is interchangeable and everything else is identical. Maybe that is possible. I have thought about the same thing, but I would not have the SMD soldering skill or tools to do it.

 

Mr. Fox what happens if your motherboard goes and you have unlocked the bios will Dell still replace the part? or say that as you have unlocked the bios its your own fault. I have warranty till 2017 on my M18X R2

 

Having an unlocked BIOS or other system modification does not void the warranty. Using XTU, ThrottleStop, etc. does not void the warranty. However, user-induced damage is not covered under warranty. If you damage your system by user error doing something like trying to flash an unlocked BIOS and mess it up by not following the correct process that would be user-induced damage that is not covered by warranty.

The best way to avoid problems with overzealous reps looking for a reason to say no is to never make any mention of the unlocked BIOS (or vBIOS mods, or any other special tweaks) for any reason whatsoever. That information is not relevant, most don't have any idea what you are talking about, and bottom line is that it's none of their business what firmware you are using. Just don't be dishonest and try to claim something that is your fault under warranty (like bricking your machine try to flash modded firmware) and everything should be peachy. There are some people out there that lie in order to get things fixed under warranty that are totally their fault, and honesty is the best policy. By the same token, not disclosing irrelevant details is not dishonest, and providing them with irrelevant information that raises unnecessary questions is stupid.

 

Thanks for your in-depth answer as always you give a good answer so thank you. Yeah I make sure to check my mods and I know what I'm doing just that I saw you have had a m/board replacement and was curious.

 

You're welcome.

I have had system exchanges with unlocked BIOS and vBIOS mods, one depot repair with modded BIOS and vBIOS firmware and a motherboard with unlocked BIOS replaced under warranty. Nobody ever said a word about those things to me. I'm sure they either did not notice or did not care. The depot repair was with a custom paint job and they didn't have a problem with that either. None of those in-warranty repairs had a causal relationship to the modifications.

 

Glad that you had no problems well apart from the replacement parts. I've put my cpu at 3.7 instead of 4.2 due to heat problems. I did a cpu stress test on xtu and it caused my laptop to restart that did scare me lol

 

I wonder if we could start a petition or something to get Dell/Alienware to correct the problem or replace machines with this sound issue.

 

Well after pressing Dell further, it seems they've quit replacing motherboards and offered up a replacement Alienware 17 R1. Details on specs later. I'm sad though, that they will never correct the issue. I would happily trade the 17 for a M17x R4 or M18x R2 with a fully operational working sound chip.

 

I agree with you the new look of the r5 is polarising, either you love it or hate, I am in the latter camp. The recon3di post the nov update (win) seems to be fixed in 7 although I am still having some grief in 8

 

s.....they shipped me a unit with a 1600x900 LCD. Unacceptable. Can I reject the unit when I receive it, or should I refuse delivery or what?

Processor: Intel Core 4th Generation i7-4710MQ Processor (6MB Cache, up to 3.5GHz w/ Turbo Boost)
V5G7F Slot-Load Dual Layer Blu-ray Combo (BR-ROM, DVD+/-RW, CD-RW)
H7H2R AMD Radeon R9 M290X with 4GB GDDR5
DMR33 Windows 8.1 (64Bit) English
8-cell Lithium Ion (86 wHr) Battery
16 GB Dual Channel DDR3L 1600MHz (8GBx2) Memory
Office 365 - 1 Month Trial (Internet access required to install & activate)
17.3 inch (439.42 mm) WLED HD+ (1600 x 900) Anti-Glare Display
Intel Dual Band Wireless-AC 7260 + Bluetooth 4.0
Dell Outlet Alienware 17 R1
Windows 8.1 64BIT
2 MP FHD Camera
Office 365 - 1 Month Trial (Internet access required to install & activate)
240W AC Adapter
Windows 8.1 64BIT

 

Yeah, that's totally unacceptable. I would take delivery and use it while they correct the error on their end for downgrading your display resolution. If you refuse delivery it could cause a delay in their processing of your warranty claim. They should build you another system with the correct display or provide new parts to correct their mistake.

 

A quick update. I tried the 2052 drivers and upon install I got a BSOD reporting a cthda..(somthing) has crashed. After a reboot, card and soundblaster panel was ok. Since then I decided to remove the battery and have the laptop only on AC power. Even if I have to transfer it in my bag, battery is not on. For these two days, everytime I boot, sound, soundcard and sbpanel is woriking OK.


well still going without problems.....laptop shuts down and is moved almost 2 times a day.

 

I got the 17 today, and to my dismay, it is 1600x900. The dell rep I was working with has not commented about the issue, nor has he commented about returning the M17x R4 back. Until they fix the display issue, I'm not sending the M17x R4 back. The ONLY thing I like about the 17, is the more solid build quality, and the 100% functional audio chip. FACK the rest of it, complete and total junk. The relocated power jack, the LCD bezel, lack of hardware buttons, hot CPU, LOCKED BIOS, Windows 8. Screw it all. I would happily trade both machines for a 100% functional M18x, I feel like it would have the same build quality of the 17, but without stupid design changes.

 

Yeah, it's hard to get past those downgrades... it's a pretty big list, too.

Not sure what the heck they were thinking by sending you a machine with a 900p display. That's a joke, but not a funny one.

 

So he said these were my two options:
1. Accept the 17 as it is. no modifications possible, because there are no more 1080P Alienware 17s left in stock.
2. Send the 17 back, place repair work order on the M17x R4 to replace motherboard.

Naturally, I went with option 2.

 

Good choice. Option 2 would have been my pick also. The mere fact that the M17xR3/R4 had an option for a 900p screen is a joke.

Interesting news that the Alienware 17 must be going bye-bye just like the Alienware 14. That's certainly what that sounds like to me.

 

Might be where you live, but 1080p still exists as an option for the 17 (in the US). 60Hz and 120Hz.
But whatever, what has been done has been done.

 

I live in the US, he checked outlet inventory twice and couldn't find a 1080P model. They are not giving me a new built model, simply whatever they have in the refurb stock.