BSOD DRIVER_VERIFIER_DMA_VIOLATION (e6)

Page 4 of 4 FirstFirst ... 234

  1. Posts : 22,735
    windows 10 professional version 1607 build 14393.969 64 bit
       07 Dec 2018 #31

    In the left lower corner type verifier > move the dot to delete existing settings > click finish > click yes.
    Display the result or confirm that it displayed no settings were changed.

    The memory dump was partially corrupt.

    Open the virtual memory window: (eliminate the paging file and then allow the creation of a new file)
    a) move the dot to no paging file
    b) reboot
    c) reopen the virtual memory window
    d) move the dot back to system managed file
    e) this should delete and recreate the paging file
      My ComputerSystem Spec

  2.    09 Dec 2018 #32

    Might have figured it out. Played video games nearly all weekend with no issues. What I did was drop my audio quality down one notch from 48000Hz to 44100Hz. I played stuff on Ultra quality. Even ran some VR with no problems.

    Click image for larger version. 

Name:	advanced format.png 
Views:	0 
Size:	17.2 KB 
ID:	216812

    Then tonight while watching an NFL stream on my laptop monitor while I was playing a game on my HDMI monitor and crashed again. After rebooting and coming back I found that something had set my bitrate had been set back to 48000Hz from 44100Hz.

    Also, this time it looks like the BSOD gave the paging file time to cooperate so I feel like this memory.dmp won't be corrupt. I think that procedure you suggested in the previous did the trick. I'm hoping anyway.

    100% sure that the issue is something audio related. Whether its hardware or software issue I don't know. I'm hoping this dmp file will suggest some sort of fix.

    Dropbox - MEMORY.DMP
      My ComputerSystem Spec


  3. Posts : 22,735
    windows 10 professional version 1607 build 14393.969 64 bit
       09 Dec 2018 #33

    Please post a new BETA zip.
      My ComputerSystem Spec

  4.    09 Dec 2018 #34

    zbook said: View Post
    Please post a new BETA zip.
    Here you go.
    BSOD DRIVER_VERIFIER_DMA_VIOLATION (e6) Attached Files
      My ComputerSystem Spec


  5. Posts : 22,735
    windows 10 professional version 1607 build 14393.969 64 bit
       10 Dec 2018 #35

    1) Open a support ticket with Kaspersky.
    Report to them you had used the uninstall tool and ask them how to fix:

    Code:
    Kaspersky Security Data Escort Adapter	ROOT\NET\0000	Failure using the VxD loader.

    2) Uninstall MSI afterburner

    3) The mini and memory dumps displayed: BucketId=CORRUPT_MODULELIST_0xE6

    4) Uninstall (reinstall only if needed at this time)
    a) scdemu.sys
    b) ckldrv.sys

    Code:
    scdemu	SCDEmu	c:\windows\system32\drivers\scdemu.sys
    Code:
    SCDEmu.SYS
    PowerISO Virtual Drive driver
    http://www.poweriso.com/download.htm
    Code:
    networkx	NetworkX	c:\windows\system32\ckldrv.sys
    Code:
    ckldrv.sys
    CrypKey software
    http://www.crypkey.com/support/downloads.php


    5) Run Memtest86 version 8.0 for 8 or more passes
    MemTest86 - Official Site of the x86 Memory Testing Tool
    Testing is not done by time but by passes.
    The more passes the better the testing conditions.
    The computer has two 8 GB RAM DDR4 RAM modules.
    Testing time is approximately 1 -2 hours /GB RAM
    Testing needs to be continuous.
    Just one error is a fail and testing can be aborted.
    Then remove both RAM modules and re-seat one module at a time in the same DIMM for 8 or more passes to differentiate good from malfunctioning RAM.
    For all tests use a camera or smartphone camera to take pictures and post images into the thread
      My ComputerSystem Spec

  6.    10 Dec 2018 #36

    Memory checks out.

    Still crashing. Now instead of audiodg.exe I have werfault.exe.

    Click image for larger version. 

Name:	werfault.png 
Views:	0 
Size:	436.6 KB 
ID:	216917

    Code:
    Version=1
    EventType=BlueScreen
    EventTime=131889610286467247
    ReportType=4
    Consent=1
    UploadTime=131889610294442789
    ReportStatus=268435456
    ReportIdentifier=0b3e6799-7d96-4302-987d-95621385973c
    IntegratorReportIdentifier=eceed904-782b-4bb3-b58c-bb6b4a788c0e
    Wow64Host=34404
    NsAppName=BlueScreen
    OriginalFilename=WerFault.exe
    AppSessionGuid=00000000-0000-0000-0000-000000000000
    BootId=22
    IsFatal=4294967295
    EtwNonCollectReason=3
    Response.BucketId=0xE6_nt!KiInterruptSubDispatchNoLock
    Response.type=4
    Response.CabId=8a982460-7ae4-4351-9b41-93eedb0370d4
    Sig[0].Name=Code
    Sig[0].Value=e6
    Sig[1].Name=Parameter 1
    Sig[1].Value=26
    Sig[2].Name=Parameter 2
    Sig[2].Value=ffff91859a0c7060
    Sig[3].Name=Parameter 3
    Sig[3].Value=0
    Sig[4].Name=Parameter 4
    Sig[4].Value=6
    Sig[5].Name=OS version
    Sig[5].Value=10_0_17763
    Sig[6].Name=Service Pack
    Sig[6].Value=0_0
    Sig[7].Name=Product
    Sig[7].Value=768_1
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=10.0.17763.2.0.0.768.101
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=1033
    State[0].Key=Transport.DoneStage1
    State[0].Value=1
    OsInfo[0].Key=vermaj
    OsInfo[0].Value=10
    OsInfo[1].Key=vermin
    OsInfo[1].Value=0
    OsInfo[2].Key=verbld
    OsInfo[2].Value=17763
    OsInfo[3].Key=ubr
    OsInfo[3].Value=168
    OsInfo[4].Key=versp
    OsInfo[4].Value=0
    OsInfo[5].Key=arch
    OsInfo[5].Value=9
    OsInfo[6].Key=lcid
    OsInfo[6].Value=1033
    OsInfo[7].Key=geoid
    OsInfo[7].Value=244
    OsInfo[8].Key=sku
    OsInfo[8].Value=101
    OsInfo[9].Key=domain
    OsInfo[9].Value=0
    OsInfo[10].Key=prodsuite
    OsInfo[10].Value=768
    OsInfo[11].Key=ntprodtype
    OsInfo[11].Value=1
    OsInfo[12].Key=platid
    OsInfo[12].Value=10
    OsInfo[13].Key=sr
    OsInfo[13].Value=0
    OsInfo[14].Key=tmsi
    OsInfo[14].Value=6799
    OsInfo[15].Key=osinsty
    OsInfo[15].Value=1
    OsInfo[16].Key=iever
    OsInfo[16].Value=11.134.17763.0-11.0.95
    OsInfo[17].Key=portos
    OsInfo[17].Value=0
    OsInfo[18].Key=ram
    OsInfo[18].Value=16333
    OsInfo[19].Key=svolsz
    OsInfo[19].Value=915
    OsInfo[20].Key=wimbt
    OsInfo[20].Value=0
    OsInfo[21].Key=blddt
    OsInfo[21].Value=180914
    OsInfo[22].Key=bldtm
    OsInfo[22].Value=1434
    OsInfo[23].Key=bldbrch
    OsInfo[23].Value=rs5_release
    OsInfo[24].Key=bldchk
    OsInfo[24].Value=0
    OsInfo[25].Key=wpvermaj
    OsInfo[25].Value=0
    OsInfo[26].Key=wpvermin
    OsInfo[26].Value=0
    OsInfo[27].Key=wpbuildmaj
    OsInfo[27].Value=0
    OsInfo[28].Key=wpbuildmin
    OsInfo[28].Value=0
    OsInfo[29].Key=osver
    OsInfo[29].Value=10.0.17763.168.amd64fre.rs5_release.180914-1434
    OsInfo[30].Key=buildflightid
    OsInfo[30].Value=d10397e2-e749-4f58-b613-9c7bb1eac55c
    OsInfo[31].Key=edition
    OsInfo[31].Value=Core
    OsInfo[32].Key=ring
    OsInfo[32].Value=Retail
    OsInfo[33].Key=expid
    OsInfo[34].Key=containerid
    OsInfo[35].Key=containertype
    OsInfo[36].Key=edu
    OsInfo[36].Value=0
    File[0].CabName=121018-19437-01.dmp
    File[0].Path=121018-19437-01.dmp
    File[0].Flags=851970
    File[0].Type=2
    File[0].Original.Path=\\?\C:\WINDOWS\Minidump\121018-19437-01.dmp
    File[1].CabName=sysdata.xml
    File[1].Path=WER-23390-0.sysdata.xml
    File[1].Flags=851970
    File[1].Type=5
    File[1].Original.Path=\\?\C:\WINDOWS\TEMP\WER-23390-0.sysdata.xml
    File[2].CabName=WERInternalMetadata.xml
    File[2].Path=WER6A81.tmp.WERInternalMetadata.xml
    File[2].Flags=851970
    File[2].Type=5
    File[2].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6A81.tmp.WERInternalMetadata.xml
    File[3].CabName=WERInternalRequest.xml
    File[3].Path=WER6A92.tmp.xml
    File[3].Flags=851970
    File[3].Type=5
    File[3].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6A92.tmp.xml
    File[4].CabName=memory.csv
    File[4].Path=WER6AB0.tmp.csv
    File[4].Flags=589826
    File[4].Type=5
    File[4].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6AB0.tmp.csv
    File[5].CabName=sysinfo.txt
    File[5].Path=WER6AC1.tmp.txt
    File[5].Flags=589826
    File[5].Type=5
    File[5].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6AC1.tmp.txt
    File[6].CabName=Report.zip
    File[6].Path=Report.zip
    File[6].Flags=65536
    File[6].Type=11
    File[6].Original.Path=\\?\C:\WINDOWS\system32\Report.zip
    Ns[0].Name=stopcode
    Ns[0].Value=000000E6
    Ns[1].Name=p1
    Ns[1].Value=0000000000000026
    Ns[2].Name=p2
    Ns[2].Value=FFFF91859A0C7060
    Ns[3].Name=p3
    Ns[3].Value=0000000000000000
    Ns[4].Name=p4
    Ns[4].Value=0000000000000006
    FriendlyEventName=Shut down unexpectedly
    ConsentKey=BlueScreen
    AppName=Windows
    AppPath=C:\Windows\System32\WerFault.exe
    NsPartner=windows
    NsGroup=windows8
    ApplicationIdentity=00000000000000000000000000000000
    MetadataHash=-310496441
      My ComputerSystem Spec

  7. Ztruker's Avatar
    Posts : 7,040
    Windows 10 Pro X64 1809 17763.134
       10 Dec 2018 #37

    You forgot the part about posting a picture of the results.

    For all tests use a camera or smartphone camera to take pictures and post images into the thread
      My ComputersSystem Spec


 
Page 4 of 4 FirstFirst ... 234

Related Threads
Hello, So first of all, I am not a computer wizard. Some terms I might not understand as i've never had a problem like this before, but i'll try to enlist as much information as possible. Since last friday or so, i've suddenly encountered a...
Hello, so i think i have dealt with this bluescreen 3times now, and it seemed to have gone away after i went from my amd system to intel. But now its there again. The most useful function ever, wake from sleep, is now bluescreening my computer. I...
Hi, i got this computer about 3~ Weeks ago, and have gotten random BSOD's after that. System Information Bellow Intel Core i5-6600K 3.5Ghz @ 3.5 GeForce GTX960 2gb GDDR5, Physx CUDA 1TB Harddisk 7200RPM 8Gb DDR4 2133Mhz Dual Channel, 2x4gb...
I recently upgraded my htpc from 8.1 pro to Win 10 pro. I have had multiple BSOD since then. 4 were for store exception not handled and the last 2 were for kmode exception not handled mv91xx.sys. Please advise.
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 19:52.
Find Us