Windows 10: Constant BSODs caused by ntoskrnl.exe

Nice progress.
RAM testing has passed. Approximately how long did it take for each 16GB? Was it 1 -2 hours / GB ?
The Nvidia driver was the misbehaving driver and has been replaced.
Now you can use the computer in typical use or even stress it and monitor for the rest of the week.
If there are no more bsod that will complete the troubleshooting.

 

Welp... I just got a new blue screen *Sad... here is the dump file.

 

The bsod mini dump when debugged displayed the Nvidia graphics driver as the misbehaving driver again.

Please report into the thread each step that you had made for the un-installation and re-installation of the driver.

Please post an updated zip log:
BSOD - Posting Instructions - Windows 10 Forums

Code: ffffb300`0ffd3078 fffff803`619695e4Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_24ddebfb518b5a55\nvlddmkm.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for nvlddmkm.sys*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys nvlddmkm+0x1c95e4[/quote] nvlddmkm.sys nVidia Video drivers Download Drivers | NVIDIA
Get from OEM for laptops

 

Well, just got another one.
The steps that I followed to uninstall the NVidia drivers are: 1. I downloaded DDU from Official Display Driver Uninstaller DDU Download (v17.0.7.2). 2. I restarted the PC in safe mode. 3. I opened DDU, and clicked on "Clean and restart". For the installation, I went to Gigabyte's website (my graphics card is Gigabyte), went to my graphic's card page, clicked on support, selected windows 10 64 bits, and downloaded the drivers. When installing, I clicked on "Clean Install", as you said.
The blue screen that I just got happened when I was in safe mode for re-uninstalling the drivers, just before opening DDU.
The dm log collector thing to post here was done after installing the new drivers.

 

There was no definitive misbehaving driver identified in the latest bsod mini dump file.

The Nvidia driver was updated on 8/8/2017
Driver c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_24ddebfb518b5a55\nvlddmkm.sys (22.21.13.8494, 14.94 MB (15,668,664 bytes), 8/8/2017 3:38 PM)

1) create a brand new restore point
2) backup files
3) create a backup image with Macrium and place the backup image on another drive
4) in the first link view the method to modify system failure so that automatic restart is unchecked so that you will have time to view the bsod windows
5) in the second link view the methods to turn on and off windows driver verifier and the custom settings for testing
6) in the third link view the additional 2 methods to turn off windows driver verifier
7) open administrative command prompt and type or copy and paste: shutdown /r /o /f /t 00
When the computer reboots it will open to the Windows advanced troubleshooting menu. Practice navigating to startup options (not startup repair) > select #6 safe mode with command prompt; command prompt with Administrator X: \Windows\system32\cmd.exe; and restore
8) download each bluescreenview and whocrashed:
Blue screen of death (STOP error) information in dump files.
Resplendence Software - WhoCrashed, automatic crash dump analyzer
9) During each bsod you will see a stop code typically driver verifier detected violation and sometimes you may see the misbehaving driver in the form *.sys. If you see the driver please record it an post it into the thread.
10) After each bsod you will need to turn off windows driver verifier and then return to the desktop. On the desktop you will run each bluescreenview and whocrashed to identify the misbehaving driver. Then you will uninstall and reinstall the driver.
11) Whenever there is a bsod please post a new zip so that we can help you troubleshoot the bsod:
BSOD - Posting Instructions - Windows 10 Forums
12) Windows driver verifier is designed to repetitively produce bsod until misbehaving drivers are fixed or until it is turned off. Once there are no more bsod you will run windows driver verifier for 36 hours of typical computer use. If there are no more bsod you will turn off windows driver verifer and the troubleshooting will be completed.

BSOD Finding and fixing them - Microsoft Community

Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

Enable and Disable Driver Verifier in Windows 10 Windows 10 Performance Maintenance Tutorials

 

Ok so I did the Driver verifier thing, and it crashed and everything, etc. I disabled it and got into Windows, but when I opened WhoCrashed and BlueScreenView, neither showed the dumpfile info... turns out that windows didn't created the file (I checked the mindump folder). Should I activate the verifier again and wait for another bluescreen?
Also, the bluescreen didn't showed the xxx.sys file that failed so I got nothing *Sad

 

Open whocrashed > click on analyze > post results into the thread.
Then above analyze click on tools > crash dump test > type: ACCEPT > post results into the thread
Once you have confirmed that the mini dump creation is not continuously failing you can restart windows driver verifier.
For any new bsod please post an updated zip: BSOD - Posting Instructions - Windows 10 Forums

 

This is the latest crash that WhoCrashed gets (it was probably in the last zip I uploaded). I will make the crash dump test just after I post this.


Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 8/9/2017 6:53:41 PM your computer crashed
crash dump file: C:\Windows\Minidump\080917-15281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C560)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801BF4C7C6F, 0xFFFFBF00E5A36F00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

Here is the zip file after the dump test

 

There were startup repairs........what happened?
Restart windows driver verifier.

 

I restarted driver verifier and it instaltly crashed with the "DRIVER_VERIFIER_DETECTED_VIOLATION" message, I let it crash a few times (like 2 or 3) in order to be shure it created the dump files. I will upload the zip again, and here is the WhoCrashed text:

PD: I see it's an amd thing, how do I uninstall and install that?


Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

You have performed a crash dump test. The test succeeded and the crash dump file was properly written out.

On Fri 8/11/2017 6:29:54 PM your computer crashed
crash dump file: C:\Windows\Minidump\081117-10046-01.dmp
This was probably caused by the following module: amdpsp.sys (amdpsp+0x1702B)
Bugcheck code: 0xC4 (0x2000, 0xFFFFF80753F7702B, 0x0, 0x544545)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\amdpsp.sys
product: Advanced Micro Devices, Inc. amdpsp sys
company: Advanced Micro Devices, Inc.
description: amdpsp sys
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: amdpsp.sys (amdpsp sys, Advanced Micro Devices, Inc. ).
Google query: Advanced Micro Devices, Inc. DRIVER_VERIFIER_DETECTED_VIOLATION



On Fri 8/11/2017 6:29:54 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: amdpsp.sys (amdpsp+0x1702B)
Bugcheck code: 0xC4 (0x2000, 0xFFFFF80753F7702B, 0x0, 0x544545)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\amdpsp.sys
product: Advanced Micro Devices, Inc. amdpsp sys
company: Advanced Micro Devices, Inc.
description: amdpsp sys
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: amdpsp.sys (amdpsp sys, Advanced Micro Devices, Inc. ).
Google query: Advanced Micro Devices, Inc. DRIVER_VERIFIER_DETECTED_VIOLATION

 

There was 1 bsod mini dump file debugged and it displayed amdpsp.sys as the misbehaving driver..
This driver is related to AMD PSP Service.
This is a security component.
A link with video is below.
This driver is not yet in our database.
1) Open the Asus website and enter the computer's serial or product number and the operating system to view available drivers.
2) Search for AMD PSP service or driver amdpsp.sys
3) Download and install an Asus approved new copy of this driver.

Please report into the thread information that you find about this application/driver from the Asus website into the thread.



Code: BugCheck C4, {2000, fffff80753f7702b, 0, 544545}*** WARNING: Unable to verify timestamp for amdpsp.sys*** ERROR: Module load completed but symbols could not be loaded for amdpsp.sysProbably caused by : memory_corruption[/quote] Code: amdpsp AMD PSP Service AMD PSP Service Kernel System Running OK TRUE FALSE 4,096 131,072 0 6/5/2017 3:23:56 PM C:\Windows\system32\DRIVERS\amdpsp.sys 4,096[/quote] Code: Event[362]: Log Name: System Source: Service Control Manager Date: 2017-07-25T22:18:29.655 Event ID: 7045 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-N44VCA9 Description: A service was installed in the system. Service Name: AMD PSP Service Service File Name: system32\DRIVERS\amdpsp.sys Service Type: kernel mode driver Service Start Type: boot start Service Account:[/quote]
Code: Event[363]: Log Name: System Source: Microsoft-Windows-UserPnp Date: 2017-07-25T22:18:29.661 Event ID: 20003 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-N44VCA9 Description: Driver Management has concluded the process to add Service amdpsp for Device Instance ID PCI\VEN_1022&DEV_1456&SUBSYS_14561022&REV_00\4&C93BEE2&0&0239 with the following status: 0.[/quote] Code: Event[6524]: Log Name: System Source: Microsoft-Windows-UserPnp Date: 2017-08-08T15:16:11.077 Event ID: 20001 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-N44VCA9 Description: Driver Management concluded the process to install driver amdpsp.inf_amd64_2c8bb141af1bb3b0\amdpsp.inf for Device Instance ID PCI\VEN_1022&DEV_1456&SUBSYS_14561022&REV_00\4&C93BEE2&0&0239 with the following status: 0x0.[/quote]
AMD Secure Processor (Built-in technology)

 

I checked the Asus website and found nothing about the PSP service, but there was a BIOS update (0806), so i'll install it and see if it changes anything. What I also did was: open device manager, and in security devices, I found "AMD PSP 3.0 Device", I uninstalled it (checking the "delete drivers for this device box), clicked on "check for hardware changes" in device manager, and it installed automatically. I hope this works.

 

Nice.
Restart windows driver verifier to check the stability of the replaced driver.

 

Nope, did not work.

On Fri 8/11/2017 8:21:09 PM your computer crashed
crash dump file: C:\Windows\Minidump\081117-10031-01.dmp
This was probably caused by the following module: amdpsp.sys (amdpsp+0x1702B)
Bugcheck code: 0xC4 (0x2000, 0xFFFFF80E4D49702B, 0x0, 0x544545)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\amdpsp.sys
product: Advanced Micro Devices, Inc. amdpsp sys
company: Advanced Micro Devices, Inc.
description: amdpsp sys
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: amdpsp.sys (amdpsp sys, Advanced Micro Devices, Inc. ).
Google query: Advanced Micro Devices, Inc. DRIVER_VERIFIER_DETECTED_VIOLATION