BSOD ntoskrnl.exe

1) To ensure that there are no improper bios settings please reset the bios.
2) Sometimes there can be failure to boot after resetting the bios.
3) Backup any important files to another drive or to the cloud.
4) Make a backup image or update the image using Macrium:
Macrium Software | Macrium Reflect Free:
Macrium Software | Macrium Reflect Free
5) 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

6) Please run
CPU-Z | Softwares | CPUID
CPU-Z | Softwares | CPUID
open it and make screenshots of the following tabs
CPU
Mainboard
Memory
SPD*
Graphics

*SPD shows the details of each stick, you can show the details by choosing different slots in the left upper corner.
Please make screenshots of each stick.

7) Please post each screenshot in your next reply/replies.

Changed the Verifier settings to all but DDI compliance checking and randomized low resource simulation. Got the DRIVER_VERIFIED_DETECTED_VIOLATION BSOD. It did not list the driver on the blue screen. Same as before where I cannot disable Driver Verifier and system restore fails on all restore points I created. But I will pull my SSD and get the log and the dump files. I just need to know where to look for them.

The dump files:

1) mini dump files: %SystemRoot%\Minidump or c:\windows\minidump

2) memory dump file: %SystemRoot%\MEMORY.DMP or C:\Windows\MEMORY.DMP

There were no dump files on the OS drive. I did a full search. I know debug information was set to Complete Memory Dump.

When using Windows driver verifier the customized settings can be modified.
Start out with the settings in the second link.
All non-windows drivers will be tested simultaneously.
The tests in use will vary.
For example: start out with the customized settings in the second link. Then add two to three tests. There are approximately 20 + tests. So over time all the tests can be performed but only using approximately a maximum of 10 may allow you to use the tool without the current problems.
You could add two to three tests and then when you are near ten tests remove three and add three. Again this way all drivers are exposed to all the tests over time.

cwsink said:

According to the dump files your CPU's integrated memory controller is overclocked at DDR4-2400. The highest setting officially supported by Intel for your CPU is DDR4-2133. Does your motherboard's BIOS allow you to set the memory to run at DDR4-2133? If so, I'd recommend doing so and testing the system to see if the problems continue.

Also, in my experience, there is no reliable software diagnostic for testing DDR4 memory. The most reliable method has been to use the system as you normally would but with only 1 DIMM installed (for each DIMM) to try and separate the bad from the good DIMMs. I've lost count of how many times I've seen memtest86 and Windows Memory Diagnostic say DDR4 memory is good only to find out in the end the system had a bad DIMM.

I was able to get a pair of standard 4GB DDR4-2133 dimms of RAM to use for testing. Assuming neither of the testing dimms was bad, it is not the RAM because I still got a memory management BSOD.

zbook said:

When using Windows driver verifier the customized settings can be modified.
Start out with the settings in the second link.
All non-windows drivers will be tested simultaneously.
The tests in use will vary.
For example: start out with the customized settings in the second link. Then add two to three tests. There are approximately 20 + tests. So over time all the tests can be performed but only using approximately a maximum of 10 may allow you to use the tool without the current problems.
You could add two to three tests and then when you are near ten tests remove three and add three. Again this way all drivers are exposed to all the tests over time.

Tried enabling 2 extra tests at a time apart from the original 3 I know would run OK. No other tests other than those three would run correctly. They would all result in a Driver Verifier Violation Detected BSOD, but would not give me the name of the driver on the BSOD nor a dump file. I did try Macrum backup image. But it would always fail to restore the image same as system restore would fail to roll back to the restore point. After clean installing 10 more times, I started diagnosing the old fashioned way. Disabling certain devices (and their software if applicable) to see if the system will run without crashing when certain devices are disabled.

Whenever there is a BSOD please post:
a) beta log collector zip
b) memory.dmp

The windows verifier tool works in producing BSOD.
The problems that you had reported in the thread was turning off or recovery from using the tool.
If you can use the tool it should be able to produce BSOD if there are misbehaving drivers.
Once there are no longer any misbehaving drivers the tool should no longer produce BSOD.
For the turning off and recovery you are limiting the number of test in use at any one time.
See if you can use just the three customized tests in this thread:
Enable and Disable Driver Verifier in Windows 10 | Windows 10 Tutorials
Then add one customized test and remove one customized test.
Keep using this method so that all tests are performed on non-Microsoft drivers.
Then see if you can increase the number of tests to four or five at a time.
At some point in time all tests should be performed on all of the drivers.

zbook said:

Whenever there is a BSOD please post:
a) beta log collector zip
b) memory.dmp

The windows verifier tool works in producing BSOD.
The problems that you had reported in the thread was turning off or recovery from using the tool.
If you can use the tool it should be able to produce BSOD if there are misbehaving drivers.
Once there are no longer any misbehaving drivers the tool should no longer produce BSOD.
For the turning off and recovery you are limiting the number of test in use at any one time.
See if you can use just the three customized tests in this thread:
Enable and Disable Driver Verifier in Windows 10 | Windows 10 Tutorials
Then add one customized test and remove one customized test.
Keep using this method so that all tests are performed on non-Microsoft drivers.
Then see if you can increase the number of tests to four or five at a time.
At some point in time all tests should be performed on all of the drivers.

Here are the logs for the last 2 BSODs. I am uploading the dump files.

I was able to use the 3 customized test (I/O verification, force I/O requests, IRP logging) on all the non-Microsoft drivers. System ran with no stability issues or crashes for 3 days. Once I added any 4th test (I started with Special Pool and got down to Power framework) I would get the Driver Verifier BSOD, no specific driver stated, no dump file, system restore and Macrum would always fail, and all the methods to disable Driver Verifier would fail resulting in the need to clean install.

When verifier /reset was used what did you see?
See if you can customize using three tests first by removing IRP logging and adding any of the other tests.
Then see if you can remove I/o requests ad add any of the other tests.
Then see if you can remove I/o verification and add any of the other tests.

The memory dumps were not posted.
Were you able to find them?

Crash dump found at C:\Windows\MEMORY.DMP
Creation date: 08/05/2018 00:49:16
Size on disk: 741 MB

Crash dump found at C:\Windows\MEMORY.DMP
Creation date: 08/04/2018 02:01:40
Size on disk: 1128 MB


After each dump you should find then zip then upload the memory dump.
The next dump will delete the prior memory dump.
So it will be unavailable for troubleshooting unless you save it or zip it and up load it.

I do have both the memory dumps. Just lost internet for a while this morning so I could not upload them. They are uploading right now.

I will play with the 3 tests to see if I can select different ones and check it's behavior.

When I tried to command prompt reset verifier with verifier/reset, it would come back with a "no settings changed" message. I would then try the resetonbootfail, but that would not take either. It seems that once the Driver Verifier violation detected blue screen is initiated, the verifier is disabled, or at least that's what the verifier thinks when I query its settings. All flags come back as cleared and no drivers being verified.