Windows 10: Driver Verifier violation loop - after turning it off - "X64_MEMORY_CO

Good Morning,
Intel Core i7-4770
16GB Ram
64x Windows 10

A few weeks ago my computer started freezing sometimes and then dying, I reinstalled Windows 10 and the problem seems to have gone.

It started once more and I followed a guide to enable Driver Verifier. After it crashed once more I got a BSOD. "Driver Verifier Violation Detected", in a loop over and over, which was good, I got the Minidump log.

However, even after getting to the CMD prompt with the automatic repair and turning OFF Driver Verifier and deleting all the settings and making triple sure no drivers to check were selected, I kept getting the same BSOD.

I had to resort to rolling back Windows 10 to an earlier safepoint, and now I am afraid to turn off my computer in case it won't start up again.

I have the Minidump log here:
Dropbox - 010718-5296-01.rar

The result was "X64_MEMORY_CORRUPTION_LARGE", any help would be appreciated.

:)

 

Been having BSOD on Windows 10 machine since today

Hi,

I enabled the Driver Verifier , then got into a BSOD loop with driver verifier violation. Managed to turn it off in safe mode.

Uploaded the dump.

 

Problem with offline windows defender and windows driver verifier,,, possible incompatibility problem? need windows defender and recovery help

The incompatibility of windows driver verifier and windows defender offline is displayed in this video shot with my samsung smart phone.

There are many computers that displayed blue screens with windows driver verifier. To exit windows driver verifer advanced troubleshooting to safe mode with command prompt was followed by entering verifier /reset.

Then windows defender in full mode was run.

Then windows defender in offline mode was run.

Then windows driver verifier was run again.

Every computer, now 2, went into a blue screen loop. There was no longer an option to go into advanced troubleshooting. There was no administrative command prompt to turn off windows driver verifier. And windows defender offline should not have been running
as it was a one time click and there was no setting to have repetitive runs.

There may or may not be incompatibility in a computer that does not display a blue screen with windows driver verifier. All of the computers that I tested immediately blue screened with stopcodes.

These are some of the stop codes on the multiple computers:

driver verifier detected violation

driver verifier detected violation: hpdskflt.sys

driver verifier detected violation: sddtoki.sys

driver verifier detected violation: soluto.sys

This is a one drive video of the blue screen loop and incompatibility problem with windows driver verifier and windows defender offline: windows defender OFFLINE incompatibility with windows driver verifier.zip

The windows defender should not be running with each boot. There should be an option to progress to advanced troubleshooting without triggering a windows defender offline scan.

 

Hi alexbuer.

Please post in the BSOD section, they know how to read dumps. Follow posting instructions.

BSOD Crashes and Debugging - Windows 10 Forums

As to turning on machine, you are not avoiding anything by keeping it shut off. At some point you have to turn it on.

At worst you could re-install Windows. If you need to get your data off we can help. If you re-install I would suggest you tell Windows not to update your drivers. Sounds like you are good on the install and then one gets updated to point of not working.

Option four of this tutorial.

Enable or Disable Driver Updates in Windows Update in Windows 10


Ken

 

1) In the left lower corner search type or copy and paste:
verifier
2) In the pop up: driver verifier manager > click delete existing settings > click finish > click yes
This should turn windows driver verifier off.
3) run this log collector and post a zip into the thread:
log collector v2-beta06.zip

 

The verifier is, and was, off I got into the cmd and turned it off, deleted all the settings and made sure everything was unchecked. That did not stop it from displaying a BSOD with Driver Verifier Violation.
The log is in the attachments

 

Please update the system specs in the "My Computer" section:

How To Fill Out Your System Specs
System Specs - Fill in at Ten Forums:
System Specs - Fill in at Ten Forums Site Use Tutorials
In the left corner below in your post you find 'My System Specs'.
After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
System Info - See Your System Specs - Windows 7 Help Forums

Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, etc.)


For all tests /steps please post images into the thread.
If there are any problems posting images please use one drive or drop box share links.
Share OneDrive files and folders - Office Support
Upload photos and files to OneDrive - OneDrive


1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan
5) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

6) Make sure that there is no over clocking while troubleshooting.

7) Sometimes there are problems in the bios that produce bsod.
The BIOS: Version/Date American Megatrends Inc. M7848W08.108, 16/07/2013 SMBIOS Version 2.7
8) Please check to see if this is the most up to date version.
9) Open the website for the computer or motherboard manufacturer to view the drivers and post a URL or hyperlink into the thread.

10) To ensure that there are no improper bios settings please reset the bios.
11) Sometimes there can be failure to boot after resetting the bios.
12) Backup the computer files to another drive or to the cloud.
13) Make a backup image usig Macrium:
Macrium Software | Macrium Reflect Free:
Macrium Software | Macrium Reflect Free
14) And please create a brand new restore point.

How to Clear Your Computers CMOS to Reset BIOS Settings:
How to Clear Your Computers CMOS to Reset BIOS Settings
3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow

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

16) Update: hecix64.sys
Intel Management Engine Interface
Drivers & Software

17) Run memtest86+ version 5.01 for at least 8 passes. Memtest86+ - Advanced Memory Diagnostic Tool
This may take hours so plan to run it overnight.
Please make sure you use the Memtest86+ version 5.01 with the link below.
Memtest86+ - Advanced Memory Diagnostic Tool
The testing is done not by time but by passes.
The more passes the better.
There are a significant number of false negatives if fewer than 8 passes are made.
A false negative is a test pass when there is malfunctioning RAM.
There is 16 GB of RAM on the computer.
Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
Just 1 error is a fail and you can abort testing.
Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.
When Memtest86+ has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
Memory problems. - Microsoft Community
MemTest86+ - Test RAM BSOD Tutorials



Code: Event[1333]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2018-01-04T20:14:01.325 Event ID: 1005 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-TTF5NE4 Description: Unable to produce a minidump file from the full dump file.[/quote]
Code: Event[259]: Log Name: System Source: Volsnap Date: 2017-12-25T00:39:00.828 Event ID: 33 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-TTF5NE4 Description: The oldest shadow copy of volume C: was deleted to keep disk space usage for shadow copies of volume C: below the user defined limit.[/quote]
Code: Event[1907]: Log Name: System Source: Display Date: 2018-01-08T15:55:21.161 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-TTF5NE4 Description: Display driver nvlddmkm stopped responding and has successfully recovered.[/quote]
HECIx64.sys
Intel Management Engine Interface
Drivers & Software



Code: meix64 Intel(R) Management Engine Interface c:\windows\system32\drivers\hecix64.sys Kernel Driver Yes Manual Running OK Normal No Yes[/quote]