Aurora R10, new, random reboots

Question

Ok, so just got a brand new (5 days old) Aurora R10 5900 with a RTX 3080 and initially 16GB of the Kingston 3200 memory. First night out of the box I had no problems to speak of as I started loading it up and installing software. Day 2 I went and did the Alienware update installing the newest bios and a couple of other drivers (I don't remember now what they were) and that's when my problems started. Basically the situation is that I can use it for a random amount of time, sometimes light usage (web browsing, email, etc.), sometimes heavily loaded (MSFS) and it will work fine but then after day 2 I would occasionally get a BSOD with a critical hardware failure message (sorry don't have the exact message now). That has since changed now after I have been trying to solve this to just random reboots clear out of the blue. At one point I thought maybe it was heat related since the fans don't run heavy on the machine but the temp monitors I have kept on it don't tend to go above about 75 or so except for random spikes but then quickly go back down, so it seems to be staying cool. I ran the dell diagnostic multiple times, both the quick and the hour long one and everything passed. I ran the memtest86 and it passed as well. (I did add 16gb more crucial ram to the system. The only oddity I have seen there is that in CPU-Z it shows the Crucial as 1600MHz but the Factory supplied Kingston as 1468MHz). Do I need to change out the factory sticks for another 2 of Crucial to get them all the same or would this be my culprit? Event viewer has been showing critical Kernel-Power events at the time of the reboot : (The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.) which is pretty much what I would expect for a system just restarting out of the blue. Occasionally I am getting the WHEA-Logger at the time of the reboot (doesn't seem to happen every time) of both the following errors : A fatal hardware error has occurred. Component: MemoryError Source: Machine Check Exception The details view of this entry contains further information. A fatal hardware error has occurred. Reported by component: Processor CoreError Source: Machine Check ExceptionError Type: Bus/Interconnect ErrorProcessor APIC ID: 0 The details view of this entry contains further information. I've tried all the mentioned diagnostics. I've rolled back the bios to a couple different versions (since it started then) with no change and now am back up to current. I've gone back and made sure bios was set to optimized default options and I'm starting to run out of ideas to try short of calling dell and looking at returning it. I don't want to do that, because when it does stay on (and I've had times it does for a few hours. Really gets annoying though when I am 3.75 hours into a 4 hour flight and then restart) then it runs like a beast that I'm happy with. Help!

speedstep · Answer

'Ok, so just got a brand new (5 days old) Aurora R10 5900 with a RTX 3080 ' New to you but the R13 and 14 are the 'new' models. There are 2 boards. Aurora R10 motherboard NWN7M pegatron 69M10HT00B01 released on December 9, 2019 is supported by Dell with these OEM CPU =* HXPR2 AMD R5-3500, 6C, 65WV7JDD AMD R5-3600, 6C, 65W2HCV8 AMD R5-3600X, 6C, 95WVF3FD AMD R5-3600XT, 6C, 95WXNKFV AMD R7-3700X, 8C, 65W4GX0G AMD R7-3800X, 8C, 105WVJ84G AMD R7-3800XT, 8C, 105WCHMWG AMD R9-3900, 12C, 65W6KJC4 AMD R9-3900X, 12C, 105W2F53D AMD R9-3900XT, 12C, 105W1MHH5 AMD R9-3950X, 16C, 105W Aurora R10 motherboard TYR0X pegatron 69M10HT20A01 released on January 11, 2021 is supported by Dell with these OEM CPU =* HXPR2 AMD R5-3500, 6C, 65WVVDNW AMD R5-5600X, 6C, 65WNTMXC AMD R7-5800, 8C, 65WP0M7X AMD R7-5800X, 8C, 105WMCW0T AMD R9-5900, 12C, 65WKGKW8 AMD R9-5900X, 12C, 105WMMX5C AMD R9-5950X, 16C, 105W I am starting a long term project to improve the R10 by taking the motherboard and putting it into a new standard ATX case that can breathe.  This requires harvesting the front panel so that I can get the Audio and the 2 USB connections, power button, etc for testing on the bench.  The 8930 project is almost exactly the same.  Exception being the 12 pin LED power button 'White' connection. And there is no card reader connector.  There are Reddit posts that say pins 4 and 5 of the 12 pin connector are the ON button.  Won't know until I get my complete front panel that I ordered from Ebay.  Also got a bare board with the VRM heatsinks which are NOT optional IMHO.     Power cables are standard but the USB, Audio, Power LED button, are not.

Vanadiel · Answer

Remove the aftermarket memory sticks and ensure the OEM memory sticks are in the correct slots and try again. These systems are very picky with memory support.

DELL-Chris M · Answer

Vanadiel is correct. The mixing of our OEM memory and retail memory is not advised.

You need to remove the Crucial memory and test the Aurora R10 using only the Dell supplied memory sticks =
Two W21KG Kingston 8GB, XMP DDR4, 3200MHz, 1Gx64, Unbuffered, 288 pin, Single Rank, 1.25V, Non-ECC

speedstep · Answer

@qald

The OEM Ram is very specific.

XW21KG XW21KG

Validated OEM (original equipment manufacturer) memory =

0N6VG 16GB, HyperX Fury XMP DDR4, 3400MHz, 1GBx8, Unbuffered, 288 pin, Dual Rank, 1.35V, Non-ECC, Kingston X0N6VG-HYD2
JV223 16GB, XMP DDR4, 3400MHz, 2Gx64, Unbuffered, 288 pin, Single Rank, 1.35V, Non-ECC, Kingston XJV223-HYA, XJV223-MIE

VTW4H 32GB, XMP DDR4, 3200MHz, 288 pin, Dual Rank, 1.25V, Non-ECC, Kingston XVTW4H-MIE
N205T 16GB, HyperX Fury XMP DDR4, 3200MHz, 2GX64, Unbuffered, 288 pin, Dual Rank, 1.25V, Non-ECC, Kingston XN205T-MIE/XN205T-MIE2
W21KG 8GB, XMP DDR4, 3200MHz, 1Gx64, Unbuffered, 288 pin, Single Rank, 1.25V, Non-ECC

RMWRN 16GB, HyperX Fury XMP DDR4, 2933MHz, 2Gx64, Unbuffered, 288 pin, Dual Rank, 1.35V, Non-ECC, Kingston XRMWRN-HYA/XRMWRN-MIE/XRMWRN-MIE2
J69DF 8GB, HyperX Fury XMP DDR4, 2933MHz, 1Gx64, Unbuffered, 288 pin, Single Rank, 1.35V, Non-ECC, Kingston XJ69DF-HYA/XJ69DF-MIE/XJ69DF-MIE2

RGM6C 16GB, HyperX Fury XMP DDR4, 2666MHz, 2Gx64, Unbuffered, 288 pin, Dual Rank, 1.25V, Non-ECC, Kingston XRGM6C-MIB/XRGM6C-MIE/XRGM6C-MIE2
TP9W1 16GB, HyperX Fury XMP DDR4, 2666MHz, 1Gx72, Unbuffered, 288 pin, Dual Rank, 1.25V, Non-ECC,
5H5PW 8GB, HyperX Fury XMP DDR4, 2666MHz, 1Gx64, Unbuffered, 288 pin, Dual Rank, 1.25V, Non-ECC, Kingston X5H5PW-MIB/X5H5PW-MIE/X5H5PW-MIE2
Y7N41 8GB, DDR4, 2666MHz, 1Gx64, Unbuffered, 288 pin, Single Rank, 1.25V, Non-ECC

TP9W1 16GB DDR4, 2666MHz, 1Gx72, Unbuffered, 288 pin, Dual Rank, 1.25V, Non-ECC
Adata AO2P26KCST2-BZJSHC
Hynix HMA82GU6CJR8N-VK, HMA82GU6DJR8N-VK, HMA82GU6JJR8N-VK
Kingston KTP9W1-HYJ, KTP9W1-MID, KTP9W1-MIE
Micron MTA16ATF2G64AZ-2G6E1, MTA16ATF2G64AZ-2G6H1, MTA16ATF2G64AZ-2G6J1
Samsung M378A2K43CB1-CTD, M378A2K43DB1-CTD

Y7N41 8GB DDR4, 2666MHz, 1Gx64, Unbuffered, 288 pin, Single Rank, 1.25V, Non-ECC
Adata AO2P26KC8T1-BXGSHC
Hynix HMA81GU6CJR8N-VK, HMA81GU6DJR8N-VK, HMA81GU6JJR8N-VK
Kingston KY7N41-HYJ, KY7N41-MID, KY7N41-MIE
Micron MTA8ATF1G64AZ-2G6E1, MTA8ATF1G64AZ-2G6H1, MTA8ATF1G64AZ-2G6J1
Samsung M378A1K43CB2-CTD, M378A1K43DB2-CTD

qald · Answer

Tested and on the OEM only memory it locked up the system but didn't restart. No error messages in event viewer other than the one because I was forced to do a hard shut down. I believe this was the behavior I remember when I first opened up the box and was why I was looking at getting the Crucial memory because I know I was using most of the 16gb of Memory.

qald · Answer

So testing once again with just the 2x8gb OEM Kingston XW21KG Memory. I will post in a few hours the results since it tends to crash within about 2-3 hours of usage. If it is down to the memory is this an issue of just this particular memory not being compatible with anything other than it's own model? Or is it a issue with the MB? At this point since looking to keep the 32gb one way or another if the memory turns out to be incompatible with each other does it matter if I just get another 2 of the Crucial to have all 4 match with crucial or does it have to be Kingston xw21kg sticks due to the MB?

Also a side note I have seen a number of places mention that some of the errors I have seen could be heat related. I pulled the side panel and left it open and had it sitting in an ac cooled room. The temps did drop a bit but it still rebooted so best I can tell it isn't a thermal event. At one point I was able to get a crash dump and this was what came from the analysis :

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffa305d27e2028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000bc000800, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000001010135, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1952

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 8169

    Key  : Analysis.Init.CPU.mSec
    Value: 1046

    Key  : Analysis.Init.Elapsed.mSec
    Value: 29908

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 105

    Key  : Bugcheck.DumpVsMemoryMatch
    Value: True

    Key  : Dump.Attributes.AsUlong
    Value: 1000

    Key  : WER.OS.Branch
    Value: co_release

    Key  : WER.OS.Timestamp
    Value: 2021-06-04T16:28:00Z

    Key  : WER.OS.Version
    Value: 10.0.22000.1


FILE_IN_CAB:  MEMORY.DMP

DUMP_FILE_ATTRIBUTES: 0x1000

BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffa305d27e2028

BUGCHECK_P3: bc000800

BUGCHECK_P4: 1010135

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  FlightSimulator.exe

STACK_TEXT:  
ffffe380`33b98948 fffff801`49701a7b     : 00000000`00000124 00000000`00000000 ffffa305`d27e2028 00000000`bc000800 : nt!KeBugCheckEx
ffffe380`33b98950 fffff801`4c2710c0     : 00000000`00000000 ffffe380`33b98a29 ffffa305`d27e2028 ffffa305`d27e2028 : nt!HalBugCheckSystem+0xeb
ffffe380`33b98990 fffff801`4983fd33     : 00000000`00000000 ffffe380`33b98a29 ffffa305`d27e2028 ffffa305`ca3fe330 : PSHED!PshedBugCheckSystem+0x10
ffffe380`33b989c0 fffff801`4970346d     : ffffa305`ca3c8b00 ffffa305`ca3c8b00 ffffa305`ca3fe380 178bfbff`7ed8320b : nt!WheaReportHwError+0x393
ffffe380`33b98a90 fffff801`497038b8     : 00000000`00000015 ffffa305`00000003 ffffb30b`21901000 00000000`00000015 : nt!HalpMcaReportError+0xb1
ffffe380`33b98bf0 fffff801`4970374c     : ffffa305`ca2f8fc0 00000000`00000000 ffffe380`33b98e00 00000000`00000000 : nt!HalpMceHandlerCore+0x138
ffffe380`33b98c50 fffff801`49702beb     : ffffa305`ca2f8fc0 ffffe380`33b98ef0 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0
ffffe380`33b98c90 fffff801`4970556b     : ffffa305`ca2f8fc0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0x97
ffffe380`33b98cc0 fffff801`49765a29     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x3b
ffffe380`33b98cf0 fffff801`496274fe     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9
ffffe380`33b98d20 fffff801`49627128     : 00000000`00000010 00000000`00000000 ffffe380`33b10180 00000000`00000000 : nt!KxMcheckAbort+0x7e
ffffe380`33b98e60 fffff801`49770e0a     : fffff801`49ef8bc0 00000000`00ffffff ffffa305`df6443c0 00000000`00000000 : nt!KiMcheckAbort+0x2a8
ffffb30b`21907760 fffff801`4963fbba     : ffffe380`ffffffff 00000000`00000000 ffffa305`e33d6dc0 00000000`00000002 : nt!KiSendHeteroRescheduleIntRequest+0x3e
ffffb30b`21907790 fffff801`49486179     : ffffa305`00000015 ffffa305`00000008 ffffb30b`21907970 fffff801`00000000 : nt!KiSwapThread+0x1bbc9a
ffffb30b`21907870 fffff801`49480094     : 00000000`00000000 fffff801`00000000 ffffa305`00000076 00000009`f5dbc8fc : nt!KiCommitThreadWait+0x159
ffffb30b`21907910 fffff801`4987b88b     : ffffa305`e1072460 0000002b`00000006 00000000`00000001 00000158`fd2c1000 : nt!KeWaitForSingleObject+0x234
ffffb30b`21907a00 fffff801`4987b7ba     : ffffa305`df6443c0 0000002b`5b77fd38 00000000`00000000 00000000`00000020 : nt!ObWaitForSingleObject+0xbb
ffffb30b`21907a60 fffff801`49629e78     : 00000158`d9e29110 ffffb30b`21907b20 ffffb30b`21907ab8 ffffffff`fff99760 : nt!NtWaitForSingleObject+0x6a
ffffb30b`21907aa0 00007ffc`98003f34     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
0000002b`5b77fd08 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`98003f34


MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x124_0_AuthenticAMD_MEMORY__UNKNOWN_FATAL_IMAGE_AuthenticAMD.sys

OS_VERSION:  10.0.22000.1

BUILDLAB_STR:  co_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b0905187-9dbc-d607-4dc5-8630b9eddb7f}

Followup:     MachineOwner
---------

21: kd> !errrec ffffa305d27e2028
===============================================================================
Common Platform Error Record @ ffffa305d27e2028
-------------------------------------------------------------------------------
Record Id     : 01d873c01cdbb698
Severity      : Fatal (1)
Length        : 1019
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 5/30/2022 2:07:53 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Memory
-------------------------------------------------------------------------------
Descriptor    @ ffffa305d27e20a8
Section       @ ffffa305d27e21c8
Offset        : 416
Length        : 80
Flags         : 0x00000001 Primary
Severity      : Fatal

Physical Addr.: 0x0000000100ef8c80

===============================================================================
Section 1     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffa305d27e20f0
Section       @ ffffa305d27e2218
Offset        : 496
Length        : 192
Flags         : 0x00000000
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Data Read
Flags         : 0x00
Level         : 1
CPU Version   : 0x0000000000a20f10
Processor ID  : 0x0000000000000019
Instr Pointer : 0x0xfffff80149770e0a

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffffa305d27e2138
Section       @ ffffa305d27e22d8
Offset        : 688
Length        : 292
Flags         : 0x00000000
Severity      : Fatal

Error         : DCACHEL1_DRD_ERR (Proc 21 Bank 0)
  Status      : 0xbc00080001010135
  Address     : 0x0000000100ef8c80
  Misc.       : 0xd01a0ffe00000000

===============================================================================
Section 3     : {c34832a1-02c3-4c52-a9f1-9f1d5d7723fc}
-------------------------------------------------------------------------------
Descriptor    @ ffffa305d27e2180
Section       @ ffffa305d27e23fc
Offset        : 980
Length        : 39
Flags         : 0x00000000
Severity      : Informational

*** Unknown section format ***

Vanadiel · Answer

Does it lock up with any other application, or just flight simulator?

qald · Answer

So far predominately Flight Simulator since I got the machine for that, but I have had it lock up and restart when just sitting on the desktop with nothing else much open other than the normal background tasks. I just tend to notice it more in Flight Simulator, my guess because it pushes the machine harder.

Side question on the Ram if I do want to expand it again to the 32gb does it have to be the kingston model or if I buy two more 8gb Crucial (keeping the sticks the same brand and model) would it be as finicky?

qald · Answer

That was why I wanted to add the 16gb more of ram, but still trying to determine if I need to just buy 16gb more of cruical for all cruical or see if I can find somewhere the kingston memory. As to the heat I have been watching it and with the case closed it hits in the 70s typically when maxed out but not much above that. When I opened the side case and left it open in the room it was doing in the high 60s so it isn't a heat issue as best I can tell. Now the Processor itself will max out at about 80c but it is liquid cooled and when it does this tends to quickly come back down. I already have the awcc running in performance profile but haven't noticed much of a difference in the fan speeds overall.

RodsterB · Answer

I'm a MS Flight Sim nut and at minimum, MSFS 2020 needs 16GB of RAM. If running MSFS in 4K I would suggest 32GB of RAM. Also MSFS is very CPU intensive, has always been since MSFS 4.0

You might want to check your temps and see if they are pushing CPU temps higher in the 80-90c range. If they are I would open AWCC and run the Performance Fan Profile.

Your Kernel Power event entries can also be caused by a faulty PSU that can't handle the loads of the CPU and GPU.

RodsterB · Answer

I would run Dell hardware diagnostics just to make sure everything in your system is a OK.

qald · Answer

Have run it countless times and it almost always passed. One time it did force restart during the diagnostic but didn’t report a fail of course sigh.  However I may have an update. I finally pulled the oem memory and am just running on the 16gb aftermarket crucial memory and flight simulator has actually stayed up for over 6 hours which is the longest it has done so on this machine.  there may have been an issue with the Kingston ram that only comes out when really heavily used. Since the diagnostic is not pounding it as hard. The odd part is that the Kingston ram passed memest86 so not sure why msfs would kill it with that ram in the system. Planning on continuing to leave msfs running overnight and see if I come back to it or your system restarted to truly tell if there oem memory is my focal point like it is currently looking. Of course if it is not sure how I can explain that to Dell to get it addressed other than buying my own memory since the Oem one doesn’t work right…..

Vanadiel · Answer

Since this is a new machine it should be covered under warranty. Contact @DELL-Cares and they can assist you with further troubleshooting and warranty repairs if required.

JohnnyRamone · Answer

If you want 32GB Ram you have to buy the Kingston OEM directly from Dell. Its the only memory that is guaranteed to work in these systems. OEM-memory is not the fastest and it is very expensive but Dell offers very limited aftermarket ram-support. Mixing OEM and aftermarket is a nogo. Even only using Crucial can lead to failures. The fastest OEM-Memory for your system is 3466Mhz. If the aurora keeps crashing with OEM-parts you should return it.

qald · Answer

So as to the test with the crucial 16gb flight sim managed to stay running 16 hours and the system did not reboot (longest it has ever gone without a force reboot). It did get an error message about not being able to find a referenced memory spot but I did some research and this is a bug that was recent in MSFS that has not been fixed yet so I can't fault the hardware for it. So at this point it would appear my suspicions are confirmed that it is the kingston ram causing issues.

I can understand the mixing issues since they would be running different timings, different voltage, etc but something is wrong when you can't even use Ram that is made third party and is guaranteed to work in the board by the third party company.

Alienware Desktops

Was this post helpful?