BSOD 2-10min after Win10 update (nvlddmkm.sys/ntoskrnl/pci.sys)

The cause is the driver of your GPU or your GPU or services from software.

Please do the following:

• Search msconfig and open it
• Go to the tab services
• Check 'Hide Microsoft services'
• See if there is a service called Nvidia Streaming Kernel service or Nvidia Streamer Service
• If there is a service, uncheck it
• Click apply > ok
• Reboot if asked

Please check your manufacturer for driver updates.

Code:

7: kd> lmvm nvlddmkmstart             end                 module name
fffff801`11000000 fffff801`11af2000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Tue Aug 25 15:41:50 2015 (55DC709E)
    CheckSum:         00AB7BF3
    ImageSize:        00AF2000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Diagnostic Test

 GPU TEST

Run Furmark to stress test your GPU. FurMark - GPU Stress Test - Windows 10 Forums

   Note

Run Furmark for around 30 minutes.

   Warning

Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if overheating occurs.

According to the information in the dumps you have a driver from 2015.8.25.
Please update your driver

Artist said:

Won't happen, I crash at most 2min after the GPU kicks in if I enable it again.

You mean the program crashes?

Are there other versions of the drivers available at the manufacturer?

Sorry, I'm busy with a lot of people, sometimes I don't have time to read back.

I'd like to know if there are more drivers involved with this, I don't believe this is only related to the GPU and that these drivers aren't working as they should.

Diagnostic Test

 DRIVER VERIFIER

   Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial run driver verifier.

Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

   Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

Without driver verifier it will be guessing what is causing it, or a lot of luck that the driver is blamed.