I've seen this on two 5591's, a 5491, and a 7285. The Thunderbolt driver will blue screen the box when it connects to a TB16 dock. In trying to track it down, it appears to happen when the software tries to enumerate the devices on the dock (it will BSOD just a few seconds after I authorize the device via the driver). Also, I've tried this against our corporate build as well as a vanilla build off of media.
Anybody else seeing this? Or better yet, have any ideas?
After some more digging it looks like the real culprit is the 'ASMedia USB Extended Host Controller Driver', it simply looked like the thunderbolt driver because every time you utilized the thunderbolt driver you also enabled the ASMedia driver (i.e. I plugged in the TB-16 dock and authorized it to connect), which throws the BSOD.
And the specific error is:
After some more digging it looks like it a very specific device driver that causes the BSOD. I can have the dock connected and have the 'ASMedia USB3.0 eXtensible Host Controller' driver installed, but when I try to install the driver for this device:
I get the BSOD. I've tried taking drivers from the following ASMedia driver versions:
All three cause a BSOD. Here's a copy of the bugcheck info from the last crash:
* Bugcheck Analysis *
An illegal DMA operation was attempted by a driver being verified.
Arg1: 0000000000000026, IOMMU detected DMA violation.
Arg2: ffffa601c4d6b060, Device Object of faulting device.
Arg3: 000000000000001c, Faulting information (usually faulting physical address).
Arg4: 0000000000000006, Fault type (hardware specific).
The problem seems to be with all Asmedia drivers for Asmedia chipsets. I have a pcie esata card with a JBOD box attached, in a Dell XPS 8930. This card uses the Asmedia 106x SATA Controller driver. As soon as I updated to Windows 10 Version 1809 from Version 1803 I received the BSOD with the message INTERNAL_POWER_ERROR. If I disconnect everything from the card, the computer turns on fine. As soon as I plug something back in, within 2 seconds of windows recognizing the attached drives, I get the BSOD.
I have phoned both Dell and Microsoft tech support. They could not figure it out.
I also contacted the card manufacturer and they replied on 1/2/2019 with the following "We are still doing test and trying to find a solution. Asmedia does not seems to have new drivers."
Since then I have done many searches online and as of today, 1/18/2019, there are no new Asmedia drivers. I have switched to another pcie esata card with a Marvell chipset and everything is well. I will continue looking for a newer Asmedia driver.
If I find new Asmedia drivers I will come back here and post it and I will check to see if anyone else has solved the problem.
i have the same problem with a Precision 7530 and aTB18DC Dock. So it is not a Latitude specific problem but a general ASMedia driver problem.
I tried to update firmware, BIOS and drivers of Laptop and Dock, but nothing helped. My ASMedia driver version is 220.127.116.11.
Irregular i get a BSOD with the following message:
DRIVER_VERIFIER_DMA_VIOLATION (e6) An illegal DMA operation was attempted by a driver being verified. Arguments: Arg1: 0000000000000026, IOMMU detected DMA violation. Arg2: ffffaf8f65d82060, Device Object of faulting device. Arg3: 000000000000002f, Faulting information (usually faulting physical address). Arg4: 0000000000000006, Fault type (hardware specific).
I try to speed up the process by triggering our company internal Dell Support.
For what it's worth, I've found a 'sometimes it works' workaround. In my environment I find that if I flash the firmware on the TB16 to the latest, it works most of the time. I do have two docks that still throw a blue screen if you plug in the Ethernet cable, but if they leave the Ethernet cable unplugged and work off of wireless the system seems to be stable. For the record the firmware version of the ASM USB 3.0 Cntlr that works for me is 10.11.A9.
I'm having this same problem, except I don't have a Dell. I just have a media server that specified using a 6Gbps PCI-E eSata Card with the Asmedia chipset. Any chance you can shed some light on what I may need to do to fix this conflict so I can update? Thanks very much, I haven't been able to find many other people discussing this issue.
This has been happening to a lot of our 9360s/9370s for about a month now. We narrowed it down to the same ASMedia USB A11 update from Dell Command Update. It usually happens in combonation with our Dell WD15 docking stations. The result is a BSOD and it crashes all USB and Bluetooth devices until reboot. We have found about half the time installing the older A10 update will fix it, but it does come back most of the time.
I opened a ticket with Dell about this and it was escalated, I'll let you know if I hear anything.
Wondering if you've heard back from Dell about this one? I am experiencing the same issue on an XPS 9370. I've tried reverting the ASmedia driver to 18.104.22.168 Microsoft driver, and the issue appeared to disappear for a few days, but I have since experienced another BSOD. Using a TB16 docking station.
Couple of points regarding the TB16+Skype BSOD concern:
-The fix from dc288 is not a Dell-Support-approved work around but is one that can be tried if you’re comfortable with doing so. Make sure you backup all data and gather all recovery media before ever touching the registry.
-Even though the fix from dc288 is not yet a Dell supported work around, it has been tested by Dell under best effort and has stopped the BSOD from occurring
-Dell engineering is working on a new driver in order to resolve the BSOD. I will be back in the future with updates on that
Thank you for your feedback on this issue.
Justin C Dell Technical Support | Project Sputnik
Dell Support is also on Twitter! https://twitter.com/DellCaresPRO
Remove the following entry at registry key (make a backup copy first):
That is the only difference that 22.214.171.124 has and rolling back the driver does not remove that registry key.
More information on what DMAremapping does:
This policy is intended to provide additional security against external DMA capable devices. It allows for more control over the enumeration of external DMA capable devices incompatible with DMA Remapping/device memory isolation and sandboxing.
Device memory sandboxing allows the OS to leverage the I/O Memory Management Unit (IOMMU) of a device to block unallowed I/O, or memory access, by the peripheral. In other words, the OS assigns a certain memory range to the peripheral. If the peripheral attempts to read/write to memory outside of the assigned range, the OS blocks it.
This is what the Dell tech sent us as well, but those keys don't exist on effected systems that we have, which is a couple hundred 9360s/70s. Not sure where to go from here, we've brainstormed workarounds but nothing helps. We reported this severe issue to Dell almost 2 months ago with no resolution in sight.
Cautiously optimistic that the regedit dc288 recommended has resolved my issue on my Precision 3530 with the TB16 dock. If it does work - we will probably roll out the edit for our entire department (we all have the exact same hardware, and subsequent problems).
Unrelated, but just to highlight the issues with these BUSINESS class machines, we've also had problems with the fan spinning unnecessarily fast, see here: https://www.dell.com/community/Precision-Mobile-Workstations/Precision-3530-fan-control/m-p/6120409/....
This just happened on my Latitude 7490 with driver version 126.96.36.199 through support assist.
Oh just noticed it pulled the BSOD log.
I get the same exact error. using the older dell command update tool on a Dell Laptop Precision 7520
Tried to update from this: ASMedia-USB-Extended-Host-Controller-Driver_XHJRN_WIN_188.8.131.52_A13_01
Version 184.108.40.206, A16
Got the blue screen during the install. Device Manager now says I have version 220.127.116.11, but Command Update doesn't think it installed it, because when it re-scans it says that I still need to update the ASMedia-USB-Extended-Host-Controller-Driver A16 (18.104.22.168)
Here is the dump. Sorry it is unformatted. It got deleted from C:\Windows\Minidump and this is all I had saved.
111319-13281-01.dmp 11/13/2019 2:20:09 PM 0x00000144 00000000`00000001 00000000`00000000 ffffdd8f`9db56d70 ffffdd8f`9da8c050 ucx01000.sys ucx01000.sys+19c70 x64 ntoskrnl.exe+1aaaf0 C:\windows\Minidump\111319-13281-01.dmp 8 15 17134 2,345,644