BSOD DRIVER_VERIFIER_DMA_VIOLATION (e6)

phelanka7 · 05 Dec 2018

Memory.dmp DROPBOX Link (1.04GB):

Dropbox - MEMORY.DMP

Also here's this copy/paste from the scans you requested -

Code:

Microsoft Windows [Version 10.0.17134.407]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.407

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32>verifier /querysettings

Verifier Flags: 0x00000000

  Standard Flags:

    [ ] 0x00000001 Special pool.
    [ ] 0x00000002 Force IRQL checking.
    [ ] 0x00000008 Pool tracking.
    [ ] 0x00000010 I/O verification.
    [ ] 0x00000020 Deadlock detection.
    [ ] 0x00000080 DMA checking.
    [ ] 0x00000100 Security checks.
    [ ] 0x00000800 Miscellaneous checks.
    [ ] 0x00020000 DDI compliance checking.

  Additional Flags:

    [ ] 0x00000004 Randomized low resources simulation.
    [ ] 0x00000200 Force pending I/O requests.
    [ ] 0x00000400 IRP logging.
    [ ] 0x00002000 Invariant MDL checking for stack.
    [ ] 0x00004000 Invariant MDL checking for driver.
    [ ] 0x00008000 Power framework delay fuzzing.
    [ ] 0x00010000 Port/miniport interface checking.
    [ ] 0x00040000 Systematic low resources simulation.
    [ ] 0x00080000 DDI compliance checking (additional).
    [ ] 0x00200000 NDIS/WIFI verification.
    [ ] 0x00800000 Kernel synchronization delay fuzzing.
    [ ] 0x01000000 VM switch verification.
    [ ] 0x02000000 Code integrity checks.

    [X] Indicates flag is enabled.

  Boot Mode:

    Persistent

  Rules:

    All rules are using default settings

  Verified Drivers:

    None

C:\WINDOWS\system32>

zbook · 05 Dec 2018

1) For the latest BSOD crash the dump files were corrupt and were not able to be debugged.
2) Create a brand new restore point:
Create System Restore Point in Windows 10 | Tutorials
3) Make a backup image using Macrium:
Macrium Software | Your Image is Everything
4) Once you have a brand new backup image and a brand new restore point Windows driver verifier can be used to find misbehaving drivers.
In order to use the tool you must be comfortable with the methods to turn off and recover from using tool.
The computer's windows advanced troubleshooting menu is used to turn off or recover from using the tool and the commands are in this Ten Forums link.
In the Ten Forums link there are three customized tests while all non-Microsoft drivers are being tested:
Enable and Disable Driver Verifier in Windows 10 | Tutorials
If there is an immediate BSOD it can be troubleshooted.
If there is no BSOD then modifications of the customized tests can be made so that there are more active tests to produce BSOD.
The computer may become sluggish or the boot may become slow during the use of the tool.
Plan to use the tool for 48 hours. And after the last BSOD for an additional 36 hours of typical computer use.

phelanka7 · 05 Dec 2018

zbook said:

1) For the latest BSOD crash the dump files were corrupt and were not able to be debugged.
2) Create a brand new restore point:
Create System Restore Point in Windows 10 | Tutorials
3) Make a backup image using Macrium:
Macrium Software | Your Image is Everything
4) Once you have a brand new backup image and a brand new restore point Windows driver verifier can be used to find misbehaving drivers.
In order to use the tool you must be comfortable with the methods to turn off and recover from using tool.
The computer's windows advanced troubleshooting menu is used to turn off or recover from using the tool and the commands are in this Ten Forums link.
In the Ten Forums link there are three customized tests while all non-Microsoft drivers are being tested:
Enable and Disable Driver Verifier in Windows 10 | Tutorials
If there is an immediate BSOD it can be troubleshooted.
If there is no BSOD then modifications of the customized tests can be made so that there are more active tests to produce BSOD.
The computer may become sluggish or the boot may become slow during the use of the tool.
Plan to use the tool for 48 hours. And after the last BSOD for an additional 36 hours of typical computer use.

Thanks Zbook. Making my backups and restores right now.

I actually tried running the verifier once and it instantly put me into a BSOD loop. I didn't really know what I was doing and failed to see which was the offending driver. After reading the tutorial it looks like it shows the driver file in ellipses after the BSOD description? I'll update the thread once I'm my restore points are ready and I have run verifier as described in the tutorial again.

Thanks for your help.

zbook · 05 Dec 2018

Windows driver verifier is designed to stress the drivers and cause BSOD.
When there is a BSOD there should be dump files.
The dump files are then debugged to find the misbehaving driver(s).
The tool, windows driver verifier will continue to produce BSOD until the tool is turned off.
In order to turn off the tool the Windows advanced recovery menu is opened on the computer and there are generally 3 main methods to turn off the tool:
a) startup settings > restart > safe mode with command prompt > type: verifier /reset
b) command prompt > opens a black box with title bar: Administrator: X:\Windows\system32\cmd.exe and prompt: X:\Sources> type: verifier /bootmode resetonbootfail
c) system restore
The methods to turn off the tool should be done in the above order. Using system restore often leads to a loss of the dump file and then little progress is made in the troubleshooting.

One of the risks of using Windows driver verifier is a boot loop. When in the boot loop the system restore cannot be accessed. The only option is the image recovery. So both the new system restore point and the backup imageare done before using the tool.

If using 3 test settings causes BSOD and then there are no BSOD it can indicate that all misbehaving drivers are fixed. Alternatively it may indicate that the three tests have stress the drivers and are no longer causing BSOD. The the additional approximately 15 tests can be added to produce BSOD.

phelanka7 · 05 Dec 2018

Ran computer for about 2 hours and got BSOD while running the verifier settings.

memory.dmp link: Dropbox - MEMORY.DMP

and beta logs:

zbook · 06 Dec 2018

The memory dump again displayed corruption:

Wed Dec 5 21:18:09.857 2018 (UTC - 6:00)

Code:

BugCheck E6, {26, ffffe60ebf4ce6a0, 0, 6}

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

If there are more corrupt dump files it may be useful to tray an in place upgrade repair as a trial and error step.
Repair Install Windows 10 with an In-place Upgrade | Tutorials

The next two crashes will be debugged and if the corruption persists then plan an in place upgrade repair.

The operating system on the computer is: Version 10.0.17134 Build 17134

The repair can be performed with a same version iso upgrading to 1809 or with an 1803 iso.

This is the iso for 1809:
Download Windows 10
Download Windows 10 ISO File | Tutorials

These are options for older iso:
Windows Download - #1 Windows ISO Download Source
Microsoft Windows and Office ISO Download Tool
TechBench by WZT (v4.1.1)

phelanka7 · 06 Dec 2018

Ran an in place upgrade repair last night. System just crashed under similar behavior (odd, glitchy sounds in game and "stuttering" behavior) followed by a hard crash after a few minutes of this. Strangely enough no BSOD and therefore no Memory.dmp was created. I made a betalog but I don't know if it contains any pertinent info to the crash.

ps - Do you have any opinions on whether this is looking like a hardware or driver issue? The glitchy stuff makes me wonder but its always audio glitching. I'm not seeing any weird graphical artifacts in game like you would expect with a failing GPU, nor am I dropping frames.

phelanka7 · 06 Dec 2018

Another crash. This time no Minidump but got a Dropbox - MEMORY.DMP

zbook · 06 Dec 2018

The dump file was corrupt:

Code:

**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
Unable to read PsLoadedModuleList
**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
KdDebuggerData.KernBase < SystemRangeStart
Loading Kernel Symbols
Unable to read PsLoadedModuleList
GetContextState failed, 0xD0000147
CS descriptor lookup failed
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get program counter
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck E6, {26, ffffb308e9481560, 0, 6}

GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147

In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread.
b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

With you already using Macrium one option is to:
a) clean install Windows 10 1803
b) Install drivers from the computer or motherboard manufacturer
c) Evaluate for computer stability or instability

Another option is to use the computer in safe mode with networking (low resolution) and evaluate for stability or instability.

Not having the ability to debug bugchecks is a handicap. If there are any misbehaving drivers or hardware they may be substantially harder to detect or make progress with the troubleshooting.

phelanka7 · 07 Dec 2018

zbook said:

The dump file was corrupt:

Code:

**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
Unable to read PsLoadedModuleList
**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
KdDebuggerData.KernBase < SystemRangeStart
Loading Kernel Symbols
Unable to read PsLoadedModuleList
GetContextState failed, 0xD0000147
CS descriptor lookup failed
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get program counter
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck E6, {26, ffffb308e9481560, 0, 6}

GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147

In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread.
b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

With you already using Macrium one option is to:
a) clean install Windows 10 1803
b) Install drivers from the computer or motherboard manufacturer
c) Evaluate for computer stability or instability

Another option is to use the computer in safe mode with networking (low resolution) and evaluate for stability or instability.

Not having the ability to debug bugchecks is a handicap. If there are any misbehaving drivers or hardware they may be substantially harder to detect or make progress with the troubleshooting.

Attachment 216471 Attachment 216472

For the record, I have used the drivers from the manufacturer's website before with no luck. Same result.