New Windows 11 BSOD

N

NolanKnight1021

Member
Joined
Nov 26, 2021
Posts
9
Hi Guys,

Going crazy for the last two days, have a new PC build and I have been plagued with a pesky BSOD. Here is what I have tried maybe you all will have better luck than me.
  1. Windows Memory Diagnostic (passed_
  2. Memtest 8 Passes No errors detected
  3. Removed and reinstalled RAM modules.
  4. Uninstalled and Reinstalled NVidia Audio and Video Drivers
After all this I still get the DRIVER_VERIFIER_DMA_VIOLATION on caused by the following module: ntoskrnl.exe (nt+0x4159E0)
At this point I have ran out of ideas and help would be much appreciated.

Google Drive Link to Mini Dump Files
Dump Files.zip
 
  • A brief description of your problem (but you can also include the steps you tried)
    • Here is what I have tried maybe you all will have better luck than me.
      1. Windows Memory Diagnostic (passed_
      2. Memtest 8 Passes No errors detected
      3. Removed and reinstalled RAM modules.
      4. Uninstalled and Reinstalled NVidia Audio and Video Drivers
  • System Manufacturer?
    • I put it together, I can give a part list if needed.
  • Laptop or Desktop?
    • Desktop
  • Exact model number (if laptop, check label on bottom)
  • OS ? (Windows 10, 8.1, 8, 7, Vista)
    • Windows 11
  • x86 (32bit) or x64 (64bit)?
    • x64
  • (Only for Vista, Windows 7) Service pack?
  • What was original installed OS on system?
    • Windows 10 upgraded to 11
  • Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)?
    • Full Retail PRO
  • Age of system? (hardware)
    • 3 days
  • Age of OS installation?
    • 3 dyas
  • Have you re-installed the OS?
    • No
  • CPU
    • Intel i9 12900K
  • RAM (brand, EXACT model, what slots are you using?)
    • Corsair Vengeance LPX 4 x 16GB 3600Mhz
  • Video Card
    • EVGA FTW 3080Ti
  • MotherBoard - (if NOT a laptop)
    • MSI PRO z690-A DDR4
  • Power Supply - brand & wattage (if laptop, skip this one)
    • EVGA 1000W
  • Is driver verifierenabled or disabled?
    • Enabled
  • What security software are you using? (Firewall, antivirus, antimalware, antispyware, and so forth)
    • MalwareBytes Suite
  • Are you using proxy, vpn, ipfilters or similar software?
    • N/A
  • Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software)
    • N/A
  • Are you currently under/overclocking? Are there overclocking software installed on your system?
    • N/A
http://speccy.piriform.com/results/FdaDnffuA1Re638aeKGNUAL

Sorry I missed all this before followed the guide this time around. Please let me know if I need anything else.

Thanks
 

Attachments

Could you please disable Driver Verifier and then enable it again with the DMA Verification option, as well as, the settings recommended by this tutorial.

Rich (BB code): 
0: kd> !verifier

Verify Flags Level 0x0012092b

  STANDARD FLAGS:
    [X] (0x00000000) Automatic Checks
    [X] (0x00000001) Special pool
    [X] (0x00000002) Force IRQL checking
    [X] (0x00000008) Pool tracking
    [ ] (0x00000010) I/O verification
    [X] (0x00000020) Deadlock detection
    [ ] (0x00000080) DMA checking
    [X] (0x00000100) Security checks
    [X] (0x00000800) Miscellaneous checks
    [X] (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

  RESERVED FLAGS (use of these flags is unsupported):
    [X] (0x00100000) Unused or reserved flag

    [X] Indicates flag is enabled
 
Only run the collection app when there are new crashes, otherwise there's no use.
 
Did you run the log collection tool again? It seems like the same dump files as before?

Edit: Sorry, they are different.
 
I reran and deleted the old one just to make sure this was the new fresh. I checked in there and I can see the dump for 12:11 please let me know if I did something wrong or need to change something else.

Thanks
 

Attachments

Rich (BB code): 
0: kd> lmvm e2f68
Browse full module list
start             end                 module name
fffff80d`c7ac0000 fffff80d`c7b3f000   e2f68    T (no symbols)           
    Loaded symbol image file: e2f68.sys
    Image path: \SystemRoot\System32\drivers\e2f68.sys
    Image name: e2f68.sys
    Browse all global symbols  functions  data
    Timestamp:        Thu Feb 18 07:44:41 2021 (602E1AE9)
    CheckSum:         0008A3E4
    ImageSize:        0007F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

Could you please check for any updates for your Intel PCI-e network driver? It seems to be causing the DMA violation crashes. I suspected that it may have been the network card.

Support: PRO Z690-A
 
NolanKnight1021 said:
I reran and deleted the old one just to make sure this was the new fresh. I checked in there and I can see the dump for 12:11 please let me know if I did something wrong or need to change something else.
Click to expand...
Thanks, your other upload was okay, it my mistake. I didn't edit my original post fast enough. My apologies!
 
Hmm, they all appear to be the same bugcheck as before. There is a slightly newer BIOS update for your motherboard, unfortunately it doesn't specify any of the changes, however, it may be worthwhile updating the BIOS to the latest version.
 
The logs indicated that the RAM is overclocked at 3600.

The Intel CPU supports DDR4 up to 3200.

Please turn off XMP and make sure that the RAM is not overclocked during the troubleshooting.

Once the computer is stable you're free to modify the hardware to your preferences.
 
Hi There,
So I have gone ahead and updated the BIOS and still it happened. In the process of reinstalling Win 11 and the newest drivers to see if this can fix it, but if this doesn't do it I am leaning towards a bad MOBO.
Thanks
 
The most recent bugchecks were E6.

These were Windows Driver Verifier (WDV) dump files however WDV was not in use.

These types of bugchecks are very likely related to problems with Windows.
However you should first evaluate the drive bad block.
And rule out other hardware problems.


OS Name: Microsoft Windows 11 Pro
OS Version: 10.0.22000 N/A Build 22000


Please report the BSODs to Microsoft using the feedback hub:
Send feedback to Microsoft with the Feedback Hub app


Also seen in the logs was another WHEA error indicating possible hardware problems.

WHEA reports and drive tests were in an earlier post that never made it to this thread.


Code: 
Event[28]
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2021-11-26T16:53:30.0340000Z
  Event ID: 1
  Task: N/A
  Level: Error ?  Opcode: Info  ?  Keyword: WHEA Error Event Logs  ?  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: DESKTOP-R0POSRJ
  Description:
A fatal hardware error has occurred. A record describing the condition is contained in the data section of this event. ?


Please perform these tests in sequence:

1) Run HD Tune (free or trial version)
HD Tune website
Post images for results on these tabs:
a) Health
b) Benchmark
c) Full error scan


2) Run Sea Tools for Windows
long generic test


3) HD Sentinel (free or trial version)
Hard Disk Sentinel - HDD health and temperature monitoring
Post images for results on these tabs:
a) Overview
b) Temperature
c) SMART


4) Download and install of these temperature monitoring software:
Speccy
HD Monitor
SpeedFan


5) Run Prime95
GIMPS - Free Prime95 software downloads - PrimeNet
Monitor for 3 hours and record the highest temperature.
Read the instructions so that you can abort testing as needed.

6) Run OCCT
OCBASE/OCCT : Free, all-in-one stability, stress test, benchmark and monitoring tool for your PC
Post images for results for these tests:
CPU, Linpack, Memory, 3D, Power
 
zbook said:
These were Windows Driver Verifier (WDV) dump files however WDV was not in use.
Click to expand...
Despite the name of the bugcheck, it isn't specific to Driver Verifier. From the documentation for Stop 0xE6:

The E6 major bugcheck code can be observed when Driver Verifier is not enabled.
Click to expand...

Source: Bug Check 0xE6 DRIVER_VERIFIER_DMA_VIOLATION - Windows drivers

Now, I believe the fourth parameter of the bugcheck (fault type) may actually be an enumeration value for the fault information type enumeration.

Rich (BB code): 
0: kd> dt _FAULT_INFORMATION_ARM64_TYPE
nt!_FAULT_INFORMATION_ARM64_TYPE
   UnsupportedUpstreamTransaction = 0n0
   AddressSizeFault = 0n1
   TlbMatchConflict = 0n2
   ExternalFault = 0n3
   PermissionFault = 0n4
   AccessFlagFault = 0n5
   TranslationFault = 0n6
   MaxFaultType = 0n7

If this is the case, then it would seem that the issue is because of a permission fault. I was going to suggest that you disable DMA Protection, however, it seems that you have already done so.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top