BSOD Help. hal.dll + ntoskrnl.exe

[A2597]

I'm remotely troubleshooting my dads new laptop, an Alienware 17 R5.
I set it up for him at Christmas for VR gaming, and had no issues. As soon as he got it home and hooked it up, he got a very consistent "DRIVER_VERIFIER_DMA_VIOLATION" BSOD after about 15 minutes gaming. Seems stable otherwise.

I have updated the Nvidia drivers, along with the audio, chipset, wireless, bluetooth, and everything else I could think of. I also updated BIOS to the latest update, and ran the funky "full dell system scan" which is how I identified the BIOS update previously mentioned. No change in the BSOD.

Blue Screen View identified hal.dll and ntoskrnl.exe as the causes.
==================================================
Dump File : 013119-12312-01.dmp
Crash Time : 1/31/2019 12:59:29 PM
Bug Check String : DRIVER_VERIFIER_DMA_VIOLATION
Bug Check Code : 0x000000e6
Parameter 1 : 00000000`00000026
Parameter 2 : ffff800f`0e5ba060
Parameter 3 : 00000000`00000200
Parameter 4 : 00000000`00000006
Caused By Driver : hal.dll
Caused By Address : hal.dll+3c4bb
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+1aa0c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\013119-12312-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 17134
Dump File Size : 2,901,876
Dump File Time : 1/31/2019 1:00:35 PM
==================================================

And here is a link to a zip with the dmp files. (I included the last five, but they are all very similar).
https://www.dropbox.com/s/7ucgi8x6tx...idump.zip?dl=0

All help is greatly appreciated. This is about the time I would usually wipe and reinstall, but I'm about 500 miles away right now. Thanks guys!

[Munkus]

Have you tried a Windows startup repair?
https://www.lifewire.com/advanced-st...ptions-2625805

What about Memtest?
Scan the hard drive for errors?
Are you OCing? If so, reset to standard.

Next step would be to begin removing hardware and drivers one by one until you isolate the culprit.

Good luck. Remote troubleshooting is a PITA.

[A2597]

the Alienware tools did a memtest and hard drive scan (was actually surprised) and no errors.
No overclock.

Haven't done windows startup repair, dunno how I'd run that remotely.

Only thing I can think of is if Dad installed the joystick/throttle/rudder pedals into different USB ports. Dunno why that would make this happen though.

I don't know how to read the dmp files to any effect, hoping someone can so better track it down.

[Munkus]

Originally Posted by A2597

the Alienware tools did a memtest and hard drive scan (was actually surprised) and no errors.
No overclock.

Haven't done windows startup repair, dunno how I'd run that remotely.

Only thing I can think of is if Dad installed the joystick/throttle/rudder pedals into different USB ports. Dunno why that would make this happen though.

I don't know how to read the dmp files to any effect, hoping someone can so better track it down.

Does it BSOD when the joystick isn't plugged in? Or just in a particular USB? The point is to eliminate all the variables one by one.

[Mahjik]

Originally Posted by A2597

Only thing I can think of is if Dad installed the joystick/throttle/rudder pedals into different USB ports. Dunno why that would make this happen though.

What flight gear is he using?

Does the BSOD only happen with the flight gear plugged in (i.e. I know it would be boring but for science sake, could he load up a flight sim and just let it go on autopilot for 15-20 minutes for a test)?

[A2597]

We can give it a go. Dunno if we can get him flying without the gear plugged in, but maybe.
He's using the Saitek Yoke and throttle, with Thrustmaster TFRP rudder pedals.

[VW_Factor]

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_VERIFIER_DMA_VIOLATION (e6)
An illegal DMA operation was attempted by a driver being verified.
Arguments:
Arg1: 0000000000000026, Violation code.
Arg2: ffffae8a04226060
Arg3: 0000000000000200
Arg4: 0000000000000006

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0xE6

PROCESS_NAME: X-Plane.exe

CURRENT_IRQL: c

[VW_Factor]

Have we verified that the XPlane install is proper? Repaired or reinstalled perhaps?

Other external variables such as cooling, like is it sitting on a blanket and can't get airflow to the intakes?

If XPlane is causing some issue with HAL.dll, make sure the game is proper.

Also make sure some Alienware bloat didn't auto update something or prevent an update from taking.

[A2597]

Xplane install is good. Also happens with DCS.
Reinstalled x-plane (to a different hard drive even) with same issue.

[Mahjik]

IMO, I think it's something with the flight gear drivers.

[VW_Factor]

Originally Posted by Mahjik

IMO, I think it's something with the flight gear drivers.

That certainly would be the next round of elimination, however. Those drivers or at least the USB driver should show up in the mem dump at least once. I didn't see it in those 5 provided.

Next easy things to check out are overheating/airflow. Otherwise you may likely end up having to take a road trip.

[Mahjik]

Originally Posted by VW_Factor

That certainly would be the next round of elimination, however. Those drivers or at least the USB driver should show up in the mem dump at least once. I didn't see it in those 5 provided.

Dump files, unfortunately don't always show the cause. They do show the result.

I will say, many many years ago, I used to have all sorts of headaches with Saitek drivers. I no longer use any of their devices so I don't know the current state of their QA.

[VW_Factor]

I'm not going to discount the possibility, because reasons..

I've not seen a driver/device such as a USB cause a HAL crash without being included in the dump.

Again certainly doesn't mean that its not possible as the reports aren't always complete, but I have seen things show up as USB Root hub and such in the report. While not specifically showing the device, at least was able to start USB troubleshooting like removing devices or upgrading/downgrading USB drivers/chipset drivers and the like.

[Mahjik]

Originally Posted by Mahjik

Does the BSOD only happen with the flight gear plugged in (i.e. I know it would be boring but for science sake, could he load up a flight sim and just let it go on autopilot for 15-20 minutes for a test)?

Originally Posted by VW_Factor

While not specifically showing the device, at least was able to start USB troubleshooting like removing devices or upgrading/downgrading USB drivers/chipset drivers and the like.

That is basically my suggestion.. First step of troubleshooting, eliminate what is not the problem.

However, given the same problem happens with two different flight sims; there are only two main things in common. The OS and the controllers which is why I suggested removing the controller for the test to eliminate one of the two variables.

[A2597]

I'm now making a trip down Sunday, so I'll be there in person to troubleshoot.
One issue with the laptop is number of USB ports. The Oculus demands 3 (Headset and two sensors) then you need more for all the periferals.

I had a single USB-C to USB3 adapter, but that left an entire USB-C port unused on the PC, and a lot of items plugged into a hub. So I'm bringing two USB-C to USB3 adapters to try an off load some of that.

I'll also try to fully remove the Saitek (Now Logitech, as they bought Saitek) and Thrustmaster drivers and re-install. See if that helps.

Will keep you updated, thanks!