Aurora R7 corrected hardware error occured

I suggest you shut-down, unplug from wall, and dissipate any flea-power by pressing power button a few times and then let system sit un-powered for 15 minutes.

Remove and Re-seat

- All memory DIMMs

- Video card

- Any other PCIe cards

Check all connectors and plugs (full insertion, etc.)

Re-power and test.

Also, what BIOS version are you running?

Product support for Alienware Aurora R7 

I would not really worry about errant driver update messages. If they are verified as updated (as you did), you are good.

Never underestimate the quality and utility of flea power.    

BIOS: 1.0.2.   

First thing that had to be done was update BIOS,  Chipset, and latest drivers from Killer to fix a very bad known packet loss problem.    Glad the updates where all released 2 days before I received shipment.

I've seen all over that the WHEA corrected errors are largely ignored.      It's the occasional pause where everything halts for 3-5 seconds that I notice maybe once an hour.  Don't know what I don't notice.    There is usually a recent WHEA log when I check.

Also ran general diagnostics, including from bios and everything always comes back passed.

mattww3 wrote:

Never underestimate the quality and utility of flea power.    

 

BIOS: 1.0.2.   

1. First thing that had to be done was update BIOS,

2. latest drivers from Killer to fix a very bad known packet loss problem.    

 

3. I've seen all over that the WHEA corrected errors are largely ignored.      It's the occasional pause where everything halts for 3-5 seconds that I notice maybe once an hour. 

 

4. Also ran general diagnostics, including from bios .

1. Good

2. Hmm. For WiFi or the on-board wired ethernet. Was driver installed from Windows-Update?

3. Not sure why people are ignoring it, AFAIK, it's not normal. Pretty sure it means something is broken.

4. ePSA Diags ... good. It's not all-telling, but it's a good start.

Should probably create and boot a www.MemTest86.com flash drive and see if you can get through 2 full passes with absolutely 0 errors.

2:   The killer drivers had to be installed directly from Killer website.   Both Dell and MS had older drivers at the time.   Had at least 60%+ WiFI packet loss until BIOS/Chipset + killer update.

3.    The specific error is WHEA 17 with the Intel vendor ID.    Lots of stuff for a very long time in searching. I think it would be easier to figure out if I knew what the device was.

Bus:Device:Function: 0x0:0x1C:0x2
Vendor ID:Device ID: 0x8086:0xA292

As of now this post is the only reference to contain 0xA292 on google.    So that's an achievement.

I just created the USB MemTest86 boot.     It's something I will have to get to when I can get to it.   Full dual pass mem test on 32gb is going to make the fleas very bored.

Any ideas on possible device from vendor ID? 

Just to make things even more unusual...

About 2 hours ago I had windows explorer freak out.   I had joined a video conference and was unable to turn up my volume.   Task bar hovering over volume mouse would turn into spinning wait wheel.    Was unable to open start menu,   tried to open command prompt directly through using command bar in browser and it wouldn't launch.    Explorer eventually crashed and didn't bring up task manager...   so I powered off.

Have not had a single WHEA log in past two hours.    Just prior to this happening there where 6  within a minute which is unusual.    

And now it's gone .?      No strange pauses either.   

Only event log from "Administrative events"

The program explorer.exe version 10.0.16299.15 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
 Process ID: 1ba8
 Start Time: 01d358b07f19d56b
 Termination Time: 0
 Application Path: C:\Windows\explorer.exe
 Report Id: 81709293-cbd4-4a3e-93f2-17db83265a56
 Faulting package full name:
 Faulting package-relative application ID:

I guess talking about problems helps to resolve them.    

mattww3 wrote:

2:   The killer drivers had to be installed directly from Killer website.   Both Dell and MS had older drivers at the time.   Had at least 60%+ WiFI packet loss until BIOS/Chipset + killer update.

 

3.    The specific error is WHEA 17 with the Intel vendor ID.    Lots of stuff for a very long time in searching. I think it would be easier to figure out if I knew what the device was.

Bus:Device:Function: 0x0:0x1C:0x2
Vendor ID:Device ID: 0x8086:0xA292

 

As of now this post is the only reference to contain 0xA292 on google.    So that's an achievement.

 

I just created the USB MemTest86 boot.     It's something I will have to get to when I can get to it.   Full dual pass mem test on 32gb is going to make the fleas very bored.

 

Any ideas on possible device from vendor ID? 

 

2. The other day, my wife was using Edge browser on the Aurora-R6 and asked "is the Internet working for you"? Mine was fine but her's was real slow. Reboot didn't help. I checked ethernet cables, desktop-ethernet-switch, router, etc. Packet-loss is a good description. She started playing World-of-Warcraft again online and it strangely appeared fine. 

So, thanks. I just updated the on-board "Killer Networks e2400 Gigabit Ethernet RJ-45" wired-ethernet driver from Device Manager. Driver changed from older Microsoft to much newer Rivet. Windows update is on common Consumer branch, so it's lame we have to do this. Seems to have fixed it. Generally, I hate Rivet/Killer and stay away from heavy driver suite ... I just run the core driver. Had no choice with this purchase (since it's build-into the motherboard). This is the first problem I've had with it.

3. I will search more later. I think low hits might be related to the very new chipset and processor. However, it could just be a bad motherboard or something installed in it. Could be related to some unique hardware combo or even a specific driver you are running.

Yes, run the MemTest86 some time soon. Turn off LCD while it runs.

mattww3 wrote:

1. About 2 hours ago I had windows explorer freak out.   

 

2. Have not had a single WHEA log in past two hours.    Just prior to this happening there where 6  within a minute which is unusual.    

 

3. I guess talking about problems helps to resolve them.    

1. IE-11 is dead and abandoned. If you want to stick with Microsoft, you should be using Edge. I jumped ship after all these many years and now use Chrome with the popular AdBlock Extension.

Windows is obviously having a problem running on your system, and it knows it.

2. Good.

3. Yeah, I wish. 

Reliability Monitor report provides a nice over-view.

Could be power glitch or brown-out. A nice-new system like that, I would never even power-it-up once unless connected to good UPS (like APC). 

haha,  that was windows Explorer,  not IE :)   There are only some obscure and risky alternatives for replacing shell

It's been over 24 hours and no WHEA events and I just updated Nvidia drivers because they where there.    Things are pretty smooth.    Really,  those WHEA errors have been there since day one and poof,   like magic,  they are not there.   Which pretty much means they will return at some point.

The Chipset update still shows available even though installed but looking at the logs,  it's just a bad Dell assistant unable to cope with an xml file.    It won't go away until someone feels the need to create an update.  Or I can try various versions of Dell utility removals, abandonments, or reinstalls.   

System.Xml.XmlException

at System.Xml.XmlElement..ctor(XmlName name, Boolean empty, XmlDocument doc)

at System.Xml.XmlDocument.CreateElement(String prefix, String localName, String namespaceURI)

at System.Xml.XmlDocument.CreateElement(String name)

at eSupport.Common.Client.Core.LastUpdatedHelper.SetLastUpdatedValue(String type, String value)]]>

That message pops up when I check for updates.    However,  this is not a driver issue it is a Dell Assistant issue.    So,  it's not concerning for performance.    Saw several other posts in various places and reinstall doesn't generally work.    Will probably go away if dell does an update.   Or if I stop using their tools.

Reliability Monitor looks like it's been sitting at 10 until yesterday's incident.    Will keep an eye on it.

mattww3 wrote:

1. haha, that was windows Explorer, not IE There are only some obscure and risky alternatives for replacing shell

2. Really, those WHEA errors have been there since day one and poof, like magic, they are not there. Which pretty much means they will return at some point.

3. The Chipset update ... even though installed

4. It won't go away until someone feels the need to create an update.

5. However, this is not a driver issue it is a Dell Assistant issue.

1. Oops, sorry. No, I mis-read that. I was not suggesting replacing the shell

2. Interesting

3. Good

4. Right

5. Right. No, I don't use it because it can't be trusted. Lenovo has a similar utility. I use it (because it actually works pretty good) but after an upgrade to Windows-10, there is now a file caught-in-it as well.

Sorry to say to anyone in future hoping for an answer on this topic.

6 days later.   Event log has not happened since.   No idea why.

It's magic.

Good to hear it is working better.

Maybe Windows updated some software or a driver that fixed it.