Did you get the chipset drivers(Intel, Audio, video, network, wireless etc) from the Aorus site or somewhere else?
X9 | AORUS
X9 | AORUS
[SOLVED] BSOD DRIVER_VERIFIER_DMA_VIOLATION (0xe6)
- Thread starter PhelanKA7
- Start date
I used the Driver Updater utility as suggested by an Aorus/Gigabyte rep.
Did the Aorus rep have any history on the laptop?
Open box items are usually returned for a reason is there still warranty on this unit?
Open box items are usually returned for a reason is there still warranty on this unit?
Not that I know of.
Aorus/Gigabyte will honor the warranty until June of 2020. Honestly that's my last resort if I can't fix it. I just prefer to do everything I possibly can to try and fix it myself. I learn more that way too.
Lets see if jcgriff can get any more out of the dumps have you enabled verifier for non microsoft drivers and received any more minidmps yet?
Turning verifier hasn't revealed anything. I've tried that route twice with no luck.
You have to leave Driver Verifier running for 24 hours minimum.
One thing to try to see if your copy of Windows is the cause here or if it is unknown hardware - Install a version of Windows obtained directly from Microsoft that we know is genuine.
Download the ISO and install Windows Server 2016 onto your system. It is good for 180 days.
Server 2016 directly from Microsoft - Windows Server Free Trial | Microsoft
Server 2016 and Windows 10 are nearly identical OS' except that in Windows 10 the server functions are turned off.
Run Server 2016 for at least several days.
If no 0xc6 BSODs, then we know the problem to be your version of Windows.
If you do get 0xc6 BSODs, then we know the problem is unknown hardware failure.
Regards. . .
jcgriff2
p.s. I do not see any other options here.
One thing to try to see if your copy of Windows is the cause here or if it is unknown hardware - Install a version of Windows obtained directly from Microsoft that we know is genuine.
Download the ISO and install Windows Server 2016 onto your system. It is good for 180 days.
Server 2016 directly from Microsoft - Windows Server Free Trial | Microsoft
Server 2016 and Windows 10 are nearly identical OS' except that in Windows 10 the server functions are turned off.
Run Server 2016 for at least several days.
If no 0xc6 BSODs, then we know the problem to be your version of Windows.
If you do get 0xc6 BSODs, then we know the problem is unknown hardware failure.
Regards. . .
jcgriff2
p.s. I do not see any other options here.
Is there a recovery partition on the HDD? If there is that is what you should be using to reinstall Windows.
If no recovery partition or you don't want or need it anymore, format the HDD before installing Windows Server 2016 -
Format HDD (low level format) - KillDisk
Regards. . .
jcgriff2
If no recovery partition or you don't want or need it anymore, format the HDD before installing Windows Server 2016 -
Format HDD (low level format) - KillDisk
Regards. . .
jcgriff2
Another crash after running a game for about 2 hours tonight. Zip file attached.
Last time I ran driver verifier I ran it for about 48 hours and would still get the same "0xe6 DMA violation" BSOD, not a Driver Verifier BSOD so it didn't really serve a purpose.
I'll try the Windows 2016 Server install when I get a chance.
Thanks for the help.
Last time I ran driver verifier I ran it for about 48 hours and would still get the same "0xe6 DMA violation" BSOD, not a Driver Verifier BSOD so it didn't really serve a purpose.
I'll try the Windows 2016 Server install when I get a chance.
Thanks for the help.
This dump may be one that has the corrupt module list that I described earlier. BSOD error screen died before it reached 100% and loading it up in Windbg revealed some bad juju. In the past I think I have fixed this by going into advanced system settings and resetting all the page file settings (select "No Paging File" > Click back to "Automatically manage paging file size for all drives"). Maybe this will indicate something. No idea.
Thanks.
Thanks.
For elimination purposes run the Intel Processor Diagnostic Utility from Intel here> https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool
So I have the original Windows installation (where the problem began back in October) that resides in a separate partition on another SSD. Is there any possible way that it could be causing this issue on this current Windows image? I wouldn't think so is why I've never mentioned it, but I'm running out of ideas.
The original install should not be causing an issue.
Code:
Bugcheck code 0000001A
Arguments 00000000`00041284 000000c0`fbbdc000 00000000`00000000 fffff300`108043101st param is a working set list, it's corrupt.
Code:
3: kd> !wsle fffff30010804310
Working Set Instance @ fffff30010804170
Working Set Shared @ fffff30010804310
FirstFree [B][COLOR=#006400]2e81 [/COLOR][/B]FirstDynamic 5
LastEntry [B][COLOR=#4b0082]2ea0 [/COLOR][/B]NextSlot 5 LastInitialized 2f91
NonDirect 0 HashTable 0 HashTableSize 0
Code:
3: kd> dd fffff30010804310
fffff300`10804310 [B][COLOR=#006400]00002e81 [/COLOR][/B]00000000 00000005 00000000
fffff300`10804320 [B][COLOR=#4b0082]00002ea0 [/COLOR][/B]00000000 00002f91 00000000
fffff300`10804330 00000008 00000000 00000000 00000000
fffff300`10804340 00000000 00000000 00000000 00000000
fffff300`10804350 80001000 fffff380 a0181390 fffff3c0
fffff300`10804360 10804370 fffff300 00000000 00000000
fffff300`10804370 bc5e2009 fffff178 10804179 fffff300
fffff300`10804380 80084029 fffff179 bcc00429 fffff178Run Memtest 86+ on this rig, it's more than likely bad RAM.
See my first post. I've run a full suite of tests in Memtest 86. 8 passes. Twice.
It's not the RAM.
I'm certain its hardware at this point, but I've put RAM thru its paces and the CPU as well with Prime95.
Let me take that back...You guys are obviously way more knowledgeable than I am.
1. Can Memtest86, how I ran it thoroughly, miss something bad in the RAM?
2. Is there something on board related to the RAM but not the physical RAM itself that could be bad that Memtest86 is missing?
3. I'm wondering if, since this is a laptop there could be a heat related issue that doesn't pop up while testing JUST the RAM or JUST the CPU but really only crops up when the GPU, CPU, and RAM are all being run fairly hard?
1. Can Memtest86, how I ran it thoroughly, miss something bad in the RAM?
2. Is there something on board related to the RAM but not the physical RAM itself that could be bad that Memtest86 is missing?
3. I'm wondering if, since this is a laptop there could be a heat related issue that doesn't pop up while testing JUST the RAM or JUST the CPU but really only crops up when the GPU, CPU, and RAM are all being run fairly hard?
Has Sysnative Forums helped you? Please consider donating to help us support the site!