*OFFICIAL* Alienware Area-51M R1 Owner's Lounge

Which specs did you order?
I know the feeling.

 

Anyone switching to the new MSI GT76?

 

Appreciate thoughts on how the MSI GT76 compares to the 51m. I have a few days left to do a full refund on my 51m (9900/2080, currently being replaced due to burning up). From the few days I had with the 51m, performance and screen were great (though I’d prefer 18”), but I didn’t love the keyboard (indistinct feel between keys, so hard to do WASD precisely without touching surrounding keys).

 

I'm going way lighter than most guys here: 9700k/2070, but I'm coming from a 5yo asus so it's christmas no matter what

 

For 1080p gaming, I doubt you'll miss the 2080 over the 2070. And I'm coming from a 8 year old 680M from my signature, I'm ready to experience PC Master Race all over again after lagging behind for soooooo long.

My system was supposed to be delivered today but the FedEx guys decided to come at the only time I wasn't available to receive it. I waited 2 months for this system to reach me so I guess another night won't be that bad. He said he'll do the job first thing tomorrow. I'll post my initial impressions here.



Sent from a Galaxy S9+

 

New design with 11 pipes and none know if it will go up in smoke as your Area-51m. I would wait for users reviews. Amount pipes doesn't tell the whole story. What componets used on the MB is equal important.

 

I am sure with a such a well known fault, they would repair laptops even after warranty expiry. For example Apple MacBook Pros had a serious screen defect which manifested after some years. Apple replaced screens no questions asked, well after warranty expiry. The only naughty thing they did was NOT to inform users (eg email on their iCloud/other account) that their screens would most likely need replacing. My wife thought it was the screen protector I had fitted ages ago, because it did really look like a worn out screen protector. Only I had never fitted a screen protector on her mac.

 

I installed my Intel 9260 today and it seem to work really good. Too soon to draw any conclusions, but it seem way better than killer.

 

This means the buyers don't need more than the minimum *1 years premium* Waranty. Thats good But I'm not good in Rushian roulette. Tested it once before but never more! Never ever.

I'm just an old fashion guy Not this type.

 

the Placebo is working its magic! The Intel 9260 is 100% the same as the Killer 1550. Same exact chip, they use the same drivers, you can use the Intel drivers even.

 

Hello everyone again,

I need a bit of an opinion.

I've undervolted CPU, GPU, and soft-capped FPS to 73 from the global nVidia profile. The monitor supports 144 but I am too old for that refresh rate anyway, I can't really tell the difference between 70 and 100.

Now what gets me worried is that the GPU rarely gets past 60 deg celsius. I've restore the default voltage to see if it's related and I didn't get much of a difference. The CPU gets to 80~ degrees quite fast but the GPU seems to only touch the value above. I'm not running too intensive stuff (2560x1440@73hz) COD-BO4, Metro Exodus, Rage2 right now at the stable FPS cap.
MSI Overlay is showing GPU usage to usually max 80%.

All that and I keep the fans on the performance profile, and the laptop sits on a havit cooler and, yea, though it's summer, it's damn cold here, 21 deg celsius room temp.

I've read around here that low temps usually are signs of the impending doom and the arrival of one of the horsemen. Are these normal temps? What are you guys usually getting? I can try to recreate some tests if someone shares some high value temps for a specific game setup. The past laptop I had with SLI 1080 used to go to 90 with no consent from my side, so either Dell made such an awesome cooling in this machine that I became paranoid, or I'm not paranoid.

Anyone can reassure a scared chicken?
Thanks

 

I benefited from that screen program , still using my 2012 Mac , looks pristine

 

This is fine. Mine runs idle in the low 30s and in the 60s at load.

Sent from my SM-N960U using Tapatalk

 

thanks, heart eased was.
Just for more info, I did some serious benchmarks and they also proved I was paranoid. With 98-99% load it went to 80 deg with balanced fans in no time 3-4 minutes.
After that I did the same tests with performance fans and the max temp was 72 deg, which is actually impressive, these fans are worth their price.

This was all done with the stock voltage so I'm quite happy.

 

A larger percentage of issues with killer came from their add-on software. Take that out of the equation and they have been ok.

 

Placebo for the win! ;-)

I hear you. Now there's no Killer software on my laptop anymore, so everything is good!

 

Your Ethernet is Killer(TM)

 

Calibration profile: LG Philips 173WFG.icm using Spyder5Elite+ Colormeter

 

Oh poo... you're right! :-(

 

The 1650x chip is able to actually sustain my wireless download speeds from quite a distance away from my ac router without disconnecting. Quite an improvement over the 1550 in terms of range.

Now to work on calibrating display...

 

Did you install the 200w vbios？
That temps surely sound weird to me.

My dead 51m also got low temps (72c) at max load and could easily pass stress test at performance fan profile according to my recall.

But My replaced one hit 86 c even at performance profile and got throttled. （no UV）
FYI 2080 desktop with some serious coolings can only achieve that 72 Celsius temp at max.

 

@S.K What do you think on this one

 

I really can't wait to see when we might get XMP profile selection and or any type of memory control. Got a really good deal on a 3000mhz CL16 ram kit and would love to take advantage of it. If not I would love to do at least the 2666mhz CL14 profile. Also with my delays continuing I should have the most revised one with a delivery date currently of June 6th. Got my whole work table organised for re padding and pasting and installing other goodies. Also grabbed a Intel 9560 for wifi because it works so well. Can't wait for AX201.

 

Spoke to him. 200w vBIOS, no undervolt, no OC, everything stock. Same configuration as mine, 9900k and 2080 RTX.
He was playing for some time, quit the game and after some time the computer shut down and burned up in smoke. He recorded this video:
https://mobile.twitter.com/AzorFrank/status/1131954343261814784

It seems the vast majority of burned laptops were running the 200w vBIOS with no undervolt, maybe it's just a mere coincidence, but there could be a connection as @Prema already advised.
I think we should push Dell for a recall, I can't use my computer as intended, I don't dare to leave it working while I'm not at home because I'm afraid of burning my home. I know it's just a very remote possibility because all computers that died burned only internally, but there is still the possibility of creating a serious incident.

 

Is there a "release date" vor xmp profile selection / memory control?

 

Today starting up a game my gpu clock speeds getting stuck. it wont go any higher as 480-500 did my gpu die ? fps in games are horrible.

 

Hey guys- need some help with dual booting. I managed to do it before and can't remember how now. So first thing in the BIOS I disable Secure Boot... then I go to the "Add boot option" and all I get are some weird file paths that don't seem to correspond to my SSD...

Before IT reset the BIOS, I had my boot options as:

#1 - Windows Boot Manager
#2 - XPG Gammix S11 Pro 512GB
#3 - Onboard NIC blah blah

Where #2 is my personal SSD where I can do whatever I want when I'm at home.

How do I get back to this? IT Director stated that he'll give me admin access on the windows drive but no way he'll give me the BIOS password, so I only have a couple of times to fix the boot order before they lock the system down again...

 

Try doing a full shut down and cold boot it. This usually fixes stuck clocks for me. It rarely happens at startup.


Sent from my iPhone using Tapatalk

 

yeah, it used to work like that for me either, but now it doesnt, it stays like that.

 

Right click on your desktop then choose nVIDIA Control Panel. Go to Manage 3D Settings from the left pane, then scroll down a bit until you see power management. If you see it's set to OPTIMAL which is the default setting when you install a driver. That's your issue.

Optimal Power means when there is no draw on the screen, the GPU clock speeds is set 0 MHz to save power and then ramps up once it needs to. Sounds great on paper, works like crap. This is the number one reason why anyone might experience crappy performance from their nVIDIA GPU. What's worse, is that's the default setting in the nVIDIA Control Panel after you install a new driver often leading people to blame the driver for bad performance when it's just the fault of nVIDIA's clowns.

Set the power management to Adaptive which puts the GPU at lower clock speeds when no GPU intensive apps are in use and it would ramp the clocks up when needed. That actually works. It's the best balance between getting lower heat from the GPU and good performance in games.

When benchmarking, for the optimal results, it's best to set the power management to High Performance.

Mind you, after you change the power management to whatever you set it to, a reboot is mandatory for the new clocks to take effect.

Classical nVIDIA Swiss Cheese

 

Just tried what you said but still nothing, yesterday it was working fine so i dont think this is settings related.

After removing Command center & OC controls to see if that would help, OC controls gives me a error

Spoiler: logs

[0CBC:24B0][2019-05-26T14:53:18]i001: Burn v3.11.0.1701, Windows v10.0 (Build 17763: Service Pack 0), path: C:\Users\Nick\AppData\Local\Temp\{DC4DDDD5-EFDB-45A4-923C-48E88241FEAA}\.cr\AlienwareOCControlsInstaller_v1.2.32.1210.exe
[0CBC:24B0][2019-05-26T14:53:18]i009: Command Line: '-burn.clean.room=C:\ProgramData\Dell\drivers\2e55a5fb-3b8d-4a06-9ab7-4d36ebd38619\AlienwareOCControlsInstaller_v1.2.32.1210.exe -burn.filehandle.attached=736 -burn.filehandle.self=740 /VerboseC:\ProgramData\dell\drivers\2e55a5fb-3b8d-4a06-9ab7-4d36ebd38619\DUPLogDir\DUPC43D.tmp'
[0CBC:24B0][2019-05-26T14:53:18]i000: Setting string variable 'WixBundleOriginalSource' to value 'C:\ProgramData\Dell\drivers\2e55a5fb-3b8d-4a06-9ab7-4d36ebd38619\AlienwareOCControlsInstaller_v1.2.32.1210.exe'
[0CBC:24B0][2019-05-26T14:53:18]i000: Setting string variable 'WixBundleOriginalSourceFolder' to value 'C:\ProgramData\Dell\drivers\2e55a5fb-3b8d-4a06-9ab7-4d36ebd38619\'
[0CBC:24B0][2019-05-26T14:53:18]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\Nick\AppData\Local\Temp\Alienware_OC_Controls_20190526145318.log'
[0CBC:24B0][2019-05-26T14:53:18]i000: Setting string variable 'WixBundleName' to value 'Alienware OC Controls'
[0CBC:24B0][2019-05-26T14:53:18]i000: Setting string variable 'WixBundleManufacturer' to value 'Dell Inc'
[0CBC:1AC0][2019-05-26T14:53:18]i000: Setting numeric variable 'WixStdBALanguageId' to value 1033
[0CBC:1AC0][2019-05-26T14:53:18]i000: Setting version variable 'WixBundleFileVersion' to value '1.2.32.1210'
[0CBC:1AC0][2019-05-26T14:53:18]e000: Failed to load file into license richedit control from path '(null)' manifest value: (null)
[0CBC:24B0][2019-05-26T14:53:18]i100: Detect begin, 12 packages
[0CBC:24B0][2019-05-26T14:53:18]i000: Setting numeric variable 'AlienwareCommandCenterExist' to value 1
[0CBC:24B0][2019-05-26T14:53:18]i000: Setting numeric variable 'SSCERuntimex86ENUv35Exist' to value 1
[0CBC:24B0][2019-05-26T14:53:18]i000: Setting numeric variable 'MSVisCPP2010x86RedistExist' to value 1
[0CBC:24B0][2019-05-26T14:53:18]i000: Setting numeric variable 'MSVisCPP2017x64RedistExist' to value 1
[0CBC:24B0][2019-05-26T14:53:18]i000: Setting string variable 'SystemProductName' to value 'Alienware Area-51m'
[0CBC:24B0][2019-05-26T14:53:18]i000: Setting numeric variable 'SSCERuntimex64ENUv35Exist' to value 1
[0CBC:24B0][2019-05-26T14:53:18]i000: Registry key not found. Key = 'SOFTWARE\Alienware\OC Controls'
[0CBC:24B0][2019-05-26T14:53:18]i000: Setting numeric variable 'AlienwareOCControlsExist' to value 0
[0CBC:24B0][2019-05-26T14:53:18]i000: Setting numeric variable 'MSVisCPP2013x86RedistExist' to value 1
[0CBC:24B0][2019-05-26T14:53:18]i000: Setting numeric variable 'MSVisCPP2012x86RedistExist' to value 1
[0CBC:24B0][2019-05-26T14:53:18]i000: Setting numeric variable 'MSVisCPP2013x64RedistExist' to value 1
[0CBC:24B0][2019-05-26T14:53:18]i000: Setting numeric variable 'SSCERuntimex64ENUv40Exist' to value 1
[0CBC:24B0][2019-05-26T14:53:18]i000: Setting numeric variable 'MSVisCPP2012x64RedistExist' to value 1
[0CBC:24B0][2019-05-26T14:53:18]w120: Detected partially cached package: SSCERuntime_x86_ENU_v3_5.msi, invalid payload: SSCERuntime_x86_ENU_v3_5.msi, reason: 0x80070002
[0CBC:24B0][2019-05-26T14:53:18]w120: Detected partially cached package: SSCERuntime_x64_ENU_v3_5.msi, invalid payload: SSCERuntime_x64_ENU_v3_5.msi, reason: 0x80070002
[0CBC:24B0][2019-05-26T14:53:18]i101: Detected package: SSCERuntime_x86_ENU_v3_5.msi, state: Present, cached: Partial
[0CBC:24B0][2019-05-26T14:53:18]i101: Detected package: SSCERuntime_x64_ENU_v3_5.msi, state: Present, cached: Partial
[0CBC:24B0][2019-05-26T14:53:18]i101: Detected package: SSCERuntimex64ENUv40, state: Absent, cached: None
[0CBC:24B0][2019-05-26T14:53:18]i101: Detected package: MSVisCPP2010x86Redist, state: Absent, cached: None
[0CBC:24B0][2019-05-26T14:53:18]i101: Detected package: MSVisCPP2012x86Redist, state: Absent, cached: None
[0CBC:24B0][2019-05-26T14:53:18]i101: Detected package: MSVisCPP2012x64Redist, state: Absent, cached: None
[0CBC:24B0][2019-05-26T14:53:18]i101: Detected package: MSVisCPP2013x86Redist, state: Absent, cached: None
[0CBC:24B0][2019-05-26T14:53:18]i101: Detected package: MSVisCPP2013x64Redist, state: Absent, cached: None
[0CBC:24B0][2019-05-26T14:53:18]i101: Detected package: MSVisCPP2017x64Redist, state: Absent, cached: None
[0CBC:24B0][2019-05-26T14:53:18]i101: Detected package: Alienware_OC_xtu6.5.0.114.msi, state: Absent, cached: None
[0CBC:24B0][2019-05-26T14:53:18]i101: Detected package: AlienwareArea51R6.msi, state: Absent, cached: None
[0CBC:24B0][2019-05-26T14:53:18]i101: Detected package: Alienware.msi, state: Absent, cached: None
[0CBC:24B0][2019-05-26T14:53:18]i052: Condition '((AlienwareOCControlsExist = "0") OR WixBundleAction=3)' evaluates to true.
[0CBC:24B0][2019-05-26T14:53:18]i052: Condition '(AlienwareCommandCenterExist OR WixBundleAction=3)' evaluates to true.
[0CBC:24B0][2019-05-26T14:53:18]i199: Detect complete, result: 0x0
[0CBC:1AC0][2019-05-26T14:53:19]i000: Setting numeric variable 'EulaAcceptCheckbox' to value 0
[0CBC:24B0][2019-05-26T14:53:19]i200: Plan begin, 12 packages, action: Install
[0CBC:24B0][2019-05-26T14:53:19]i052: Condition 'NOT SSCERuntimex86ENUv35Exist' evaluates to false.
[0CBC:24B0][2019-05-26T14:53:19]i052: Condition 'NOT SSCERuntimex64ENUv35Exist' evaluates to false.
[0CBC:24B0][2019-05-26T14:53:19]i052: Condition 'NOT SSCERuntimex64ENUv40Exist' evaluates to false.
[0CBC:24B0][2019-05-26T14:53:19]w321: Skipping dependency registration on package with no dependency providers: SSCERuntimex64ENUv40
[0CBC:24B0][2019-05-26T14:53:19]i052: Condition 'NOT MSVisCPP2010x86RedistExist' evaluates to false.
[0CBC:24B0][2019-05-26T14:53:19]w321: Skipping dependency registration on package with no dependency providers: MSVisCPP2010x86Redist
[0CBC:24B0][2019-05-26T14:53:19]i052: Condition 'NOT MSVisCPP2012x86RedistExist' evaluates to false.
[0CBC:24B0][2019-05-26T14:53:19]w321: Skipping dependency registration on package with no dependency providers: MSVisCPP2012x86Redist
[0CBC:24B0][2019-05-26T14:53:19]i052: Condition 'NOT MSVisCPP2012x64RedistExist' evaluates to false.
[0CBC:24B0][2019-05-26T14:53:19]w321: Skipping dependency registration on package with no dependency providers: MSVisCPP2012x64Redist
[0CBC:24B0][2019-05-26T14:53:19]i052: Condition 'NOT MSVisCPP2013x86RedistExist' evaluates to false.
[0CBC:24B0][2019-05-26T14:53:19]w321: Skipping dependency registration on package with no dependency providers: MSVisCPP2013x86Redist
[0CBC:24B0][2019-05-26T14:53:19]i052: Condition 'NOT MSVisCPP2013x64RedistExist' evaluates to false.
[0CBC:24B0][2019-05-26T14:53:19]w321: Skipping dependency registration on package with no dependency providers: MSVisCPP2013x64Redist
[0CBC:24B0][2019-05-26T14:53:19]i052: Condition 'NOT MSVisCPP2017x64RedistExist' evaluates to false.
[0CBC:24B0][2019-05-26T14:53:19]w321: Skipping dependency registration on package with no dependency providers: MSVisCPP2017x64Redist
[0CBC:24B0][2019-05-26T14:53:19]i052: Condition '(SystemProductName ~= "Alienware Area-51 R5") OR (SystemProductName ~= "Alienware 15 R4") OR (SystemProductName ~= "Alienware 17 R5") OR (SystemProductName ~= "Alienware m15") OR (SystemProductName ~= "Alienware m17") OR (SystemProductName ~= "Alienware Aurora R8") OR (SystemProductName ~= "Alienware Area-51m") OR (SystemProductName ~= "G5 5590") OR (SystemProductName ~= "G7 7590") OR (SystemProductName ~= "G7 7790") OR (SystemProductName ~= "Alienware m15 R2") OR (SystemProductName ~= "Alienware m17 R2") OR (SystemProductName ~= "G3 3590") OR (SystemProductName ~= "G5-5090") OR (SystemProductName ~= "G7-7090")' evaluates to true.
[0CBC:24B0][2019-05-26T14:53:19]i000: Setting string variable 'WixBundleRollbackLog_Alienware_OC_xtu6.5.0.114.msi' to value 'C:\Users\Nick\AppData\Local\Temp\Alienware_OC_Controls_20190526145318_000_Alienware_OC_xtu6.5.0.114.msi_rollback.log'
[0CBC:24B0][2019-05-26T14:53:19]i000: Setting string variable 'WixBundleLog_Alienware_OC_xtu6.5.0.114.msi' to value 'C:\Users\Nick\AppData\Local\Temp\Alienware_OC_Controls_20190526145318_000_Alienware_OC_xtu6.5.0.114.msi.log'
[0CBC:24B0][2019-05-26T14:53:19]i052: Condition '(SystemProductName ~= "Alienware Area-51 R6") OR (SystemProductName ~= "Alienware Area-51 R7")' evaluates to false.
[0CBC:24B0][2019-05-26T14:53:19]i052: Condition 'NOT( (SystemProductName ~= "Alienware Area-51 R5") OR (SystemProductName ~= "Alienware Area-51 R6") OR (SystemProductName ~= "Alienware 15 R4") OR (SystemProductName ~= "Alienware 17 R5") OR (SystemProductName ~= "Alienware m15") OR (SystemProductName ~= "Alienware m17") OR (SystemProductName ~= "Alienware Aurora R8") OR (SystemProductName ~= "Alienware Area-51 R7") OR (SystemProductName ~= "Alienware Area-51m") OR (SystemProductName ~= "G5 5590") OR (SystemProductName ~= "G7 7590") OR (SystemProductName ~= "G7 7790") OR (SystemProductName ~= "Alienware m15 R2") OR (SystemProductName ~= "Alienware m17 R2") OR (SystemProductName ~= "G3 3590") OR (SystemProductName ~= "G5-5090") OR (SystemProductName ~= "G7-7090") )' evaluates to false.
[0CBC:24B0][2019-05-26T14:53:19]i201: Planned package: SSCERuntime_x86_ENU_v3_5.msi, state: Present, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None
[0CBC:24B0][2019-05-26T14:53:19]i201: Planned package: SSCERuntime_x64_ENU_v3_5.msi, state: Present, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None
[0CBC:24B0][2019-05-26T14:53:19]i201: Planned package: SSCERuntimex64ENUv40, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None
[0CBC:24B0][2019-05-26T14:53:19]i201: Planned package: MSVisCPP2010x86Redist, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None
[0CBC:24B0][2019-05-26T14:53:19]i201: Planned package: MSVisCPP2012x86Redist, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None
[0CBC:24B0][2019-05-26T14:53:19]i201: Planned package: MSVisCPP2012x64Redist, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None
[0CBC:24B0][2019-05-26T14:53:19]i201: Planned package: MSVisCPP2013x86Redist, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None
[0CBC:24B0][2019-05-26T14:53:19]i201: Planned package: MSVisCPP2013x64Redist, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None
[0CBC:24B0][2019-05-26T14:53:19]i201: Planned package: MSVisCPP2017x64Redist, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None
[0CBC:24B0][2019-05-26T14:53:19]i201: Planned package: Alienware_OC_xtu6.5.0.114.msi, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
[0CBC:24B0][2019-05-26T14:53:19]i201: Planned package: AlienwareArea51R6.msi, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None
[0CBC:24B0][2019-05-26T14:53:19]i201: Planned package: Alienware.msi, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None
[0CBC:24B0][2019-05-26T14:53:19]i299: Plan complete, result: 0x0
[0CBC:24B0][2019-05-26T14:53:19]i300: Apply begin
[0CBC:24B0][2019-05-26T14:53:19]i010: Launching elevated engine process.
[0CBC:24B0][2019-05-26T14:53:19]i011: Launched elevated engine process.
[0CBC:24B0][2019-05-26T14:53:20]i012: Connected to elevated engine.
[0BCC:1A2C][2019-05-26T14:53:20]i358: Pausing automatic updates.
[0BCC:1A2C][2019-05-26T14:53:20]i359: Paused automatic updates.
[0BCC:1A2C][2019-05-26T14:53:20]i360: Creating a system restore point.
[0BCC:1A2C][2019-05-26T14:53:20]i361: Created a system restore point.
[0BCC:1A2C][2019-05-26T14:53:20]i370: Session begin, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{970eb1b1-1a83-406e-bcac-873fc8de5530}, options: 0x7, disable resume: No
[0BCC:1A2C][2019-05-26T14:53:20]i000: Caching bundle from: 'C:\Users\Nick\AppData\Local\Temp\{BAE0F906-138B-44D5-BA3A-53EB3A636BC2}\.be\AlienwareOCControlsInstaller.exe' to: 'C:\ProgramData\Package Cache\{970eb1b1-1a83-406e-bcac-873fc8de5530}\AlienwareOCControlsInstaller.exe'
[0BCC:1A2C][2019-05-26T14:53:20]i320: Registering bundle dependency provider: {970eb1b1-1a83-406e-bcac-873fc8de5530}, version: 1.2.32.1210
[0BCC:1A2C][2019-05-26T14:53:20]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{970eb1b1-1a83-406e-bcac-873fc8de5530}, resume: Active, restart initiated: No, disable resume: No
[0BCC:0FD8][2019-05-26T14:53:20]i305: Verified acquired payload: Alienware_OC_xtu6.5.0.114.msi at path: C:\ProgramData\Package Cache\.unverified\Alienware_OC_xtu6.5.0.114.msi, moving to: C:\ProgramData\Package Cache\{8B80ECB7-13FC-46F5-8EA6-DA38D9FE5794}v1.2.32.1210\Alienware_OC_xtu6.5.0.114.msi.
[0BCC:0FD8][2019-05-26T14:53:20]i305: Verified acquired payload: cab4E521639FE74A3E571C85F4C550C0B68 at path: C:\ProgramData\Package Cache\.unverified\cab4E521639FE74A3E571C85F4C550C0B68, moving to: C:\ProgramData\Package Cache\{8B80ECB7-13FC-46F5-8EA6-DA38D9FE5794}v1.2.32.1210\cab1.cab.
[0BCC:1A2C][2019-05-26T14:53:20]i323: Registering package dependency provider: {8B80ECB7-13FC-46F5-8EA6-DA38D9FE5794}, version: 1.2.32.1210, package: Alienware_OC_xtu6.5.0.114.msi
[0BCC:1A2C][2019-05-26T14:53:20]i301: Applying execute package: Alienware_OC_xtu6.5.0.114.msi, action: Install, path: C:\ProgramData\Package Cache\{8B80ECB7-13FC-46F5-8EA6-DA38D9FE5794}v1.2.32.1210\Alienware_OC_xtu6.5.0.114.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
[0BCC:1A2C][2019-05-26T14:53:24]e000: Error 0x80070643: Failed to install MSI package.
[0BCC:1A2C][2019-05-26T14:53:24]e000: Error 0x80070643: Failed to execute MSI package.
[0CBC:24B0][2019-05-26T14:53:24]e000: Error 0x80070643: Failed to configure per-machine MSI package.
[0CBC:24B0][2019-05-26T14:53:24]i319: Applied execute package: Alienware_OC_xtu6.5.0.114.msi, result: 0x80070643, restart: None
[0CBC:24B0][2019-05-26T14:53:24]e000: Error 0x80070643: Failed to execute MSI package.
[0BCC:1A2C][2019-05-26T14:53:24]i318: Skipped rollback of package: Alienware_OC_xtu6.5.0.114.msi, action: Uninstall, already: Absent
[0CBC:24B0][2019-05-26T14:53:24]i319: Applied rollback package: Alienware_OC_xtu6.5.0.114.msi, result: 0x0, restart: None
[0BCC:1A2C][2019-05-26T14:53:24]i329: Removed package dependency provider: {8B80ECB7-13FC-46F5-8EA6-DA38D9FE5794}, package: Alienware_OC_xtu6.5.0.114.msi
[0BCC:1A2C][2019-05-26T14:53:24]i351: Removing cached package: Alienware_OC_xtu6.5.0.114.msi, from path: C:\ProgramData\Package Cache\{8B80ECB7-13FC-46F5-8EA6-DA38D9FE5794}v1.2.32.1210\
[0BCC:1A2C][2019-05-26T14:53:24]i329: Removed package dependency provider: {D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}, package: SSCERuntime_x64_ENU_v3_5.msi
[0BCC:1A2C][2019-05-26T14:53:24]i329: Removed package dependency provider: {3A9FC03D-C685-4831-94CF-4EDFD3749497}, package: SSCERuntime_x86_ENU_v3_5.msi
[0BCC:1A2C][2019-05-26T14:53:24]i372: Session end, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{970eb1b1-1a83-406e-bcac-873fc8de5530}, resume: None, restart: None, disable resume: No
[0BCC:1A2C][2019-05-26T14:53:24]i330: Removed bundle dependency provider: {970eb1b1-1a83-406e-bcac-873fc8de5530}
[0BCC:1A2C][2019-05-26T14:53:24]i352: Removing cached bundle: {970eb1b1-1a83-406e-bcac-873fc8de5530}, from path: C:\ProgramData\Package Cache\{970eb1b1-1a83-406e-bcac-873fc8de5530}\
[0BCC:1A2C][2019-05-26T14:53:24]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{970eb1b1-1a83-406e-bcac-873fc8de5530}, resume: None, restart initiated: No, disable resume: No
[0CBC:24B0][2019-05-26T14:53:25]i399: Apply complete, result: 0x80070643, restart: None, ba requested restart: No

 

use gpuz check your pcie status

 

Click on ? and run the render test.

 

I honestly think if you are that worried you should return the system if you're in your return window. Get something else for your own piece of mind. The odds that it will catch your home on fire is slim to non-existent. The videos show this is a fizzle rather than an explosion or raging fire. Personally, I am not that worried about this that much. If it happens I have coverage and if it doesn't even better. I am not worried about my home burning down either. If these were bursting into flames that's a different story, but every video just shows a fizzle.

Sent from my SM-N960U using Tapatalk

 

Always a risk. I don't let my computers run when I'm out. Neither when I sleep. I always turn it of.
Experience similar like this ain't fun. At least if you are outside your home you won't be fried...

 

Clocks wont go higher as that.

 

Lol, this is not helping the guy. I mean it is any risk with ANY system. Not just this one.

Sent from my SM-N960U using Tapatalk

 

Clean out drivers with Display Driver Uninstaller and resinstall drivers from scratch.

Edit. Check also out Reliability Monitor to see if there is installed something new (changes around same time you experienced the problems) on your machine.

HaHa
Always turn it of when you don't work on it

 

I'm outside of my return window. Anyway I love this system (for the moment). The thing is I would be much comfortable and calmer if Dell did a recall and revised all the laptops. Apparently the amount of fried machines is not that low as they claim.

 

If you're happy now then just continue to enjoy the system rather than worrying about what might or might not happen. Acknowledge it exists, takes steps to mitigate your concerns, but try not to agonize over it.


Sent from my SM-N960U using Tapatalk

 

I feel like bugging Frank about BIOS updates. My system came with 2666MHz RAM and I cant even utilize itat its rated speeds. Also want BIOS OC controls as well since proprietary software is garbage for most part. Things that are needed before even attempting to bench...


Sent from my iPhone using Tapatalk

 

Tell him that A51m is trash and it will be returned within the grace period(don't give the service tag or Express code) and you will buy a MSI GT series with better RAM speed and OC control in BIOS. If Azor says All the best for your venture (i.e. MSI) do note that better OC controls and 2667MHz+ RAM speed will only be dream.

 

I like that strategy of extracting info , makes sense

 

My system came in today, have been playing around with it all day. Clean installed, decrapiffied Windows 10 and realised AWCC and other AW junk does not work without Windows Store. WTF. Everything stopped working properly after that point, couldn't even right click on desktop to go to nvidia CC. I had to reinstall the OS all over again and I feel like we are being forced to use Windows Store at this point which I've never done. Screw Dell,AW and MS and all the other big fat greedy mofos.

Good news though: loved the system. The back color is a dream, the soft touch is so much better than my M17XR3 and feel durable this time, the quality of the chassis is absolutely world class, the screen (AUO) feels better than my wife's 2018 Macbook Pro, the keyboard is unbelievable.

The performance of the chips is more than ample for my needs. Haven't done a lot of testing because of Windoze non sense but initial benchmarks [heaven + aida 64] 10 min loop is pushing the CPU to 80° (~4.7Ghz) and GPU to 72° (~1875 Mhz) and it looks like I've a lot of headroom here. My ambient temps are quite high (live in Dubai and wifey hates AC) but I will try to reach my 5Ghz, 2Ghz daily driver target.

The Division 2 key also seems to be useless for me because of regional lockdown so if anyone is interested in a Division 2 trade with any other game(don't care about value, if I like it I will take it) , feel free to PM and we can take it further.

Also, if someone has AW wallpaper pack, please give me a link guys. I lost all my wallpapers and any advice will be highly appreciated and repped.

Cheers.

Sent from a Galaxy S9+

 

Do you have both chargers connected? I see thermal and power limit there!!!

 

Enjoy in good health

 

Thanks brother. It's getting fine tuned as we speak, will post my findings here soon.

Sent from a Galaxy S9+

 

@Trulyfatal

I had a similar issue, suddenly the fps in games was all over the place, load was rather high, and I also had the ACC error. It all started after an ACC update and after it was unable to update the OC controls.

After stoping MSI AB from startup and clean reinstall of ACC and the OC controls with the ones in an archive I found here some posts back it went back to normal so my money are on some OC profile discordance from the update, not a hardware issue.

I didn't get to do a clean video driver reinstall as it got back to normal after ACC cleanup but I pretty much had to go back to no OC and stock vcc and clocks all around to get it out of that state.

 

This looks like it thinks there is only 1 charger connected. When i play WoW i usually use 1 connector and i have these clocks. Sometimes even when both are plugged in, looks like it's getting bugged or something. What often works for me is to unplug 1 charger from the back and plug it back in.