A2597
Well-known member
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/7ucgi8x6txqoynj/minidump.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!
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/7ucgi8x6txqoynj/minidump.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!