Windows 10: BSOD DRIVER_IRQL_NOT_LESS_OR_EQUAL (ks.sys)

Got this BSOD while playing The Walking Dead.

Attached the dumpfile below.

:)

 

BSOD loop with ks.sys error after creators' update

Hi

I'm on a Windows 10 Pro machine. Everything was working fine and then it prompted me to Update. I went with it and there was trouble updating, it would end up in BSOD and then roll back the update. The last time before I tried to update I quit my antivirus
(avast premier) and then restarted. This time the update worked but now when windows boots up I just see the desktop for a few seconds and then I get another BSOD with a ks.sys error. I've uninstalled my antivirus for now and still the BSOD keeps coming up.
I've read that ks.sys errors are related to driver issues but except for my in-built monitor webcam driver rest everything is fine. Please find latest 3 minidump files in the ondrive link below. Hope to get some help soon.

Minidump.zip

 

VIA Chrome9 HC IGP WDDM Driver Problem Win 10

BSOD report is:

stop code:

system thread exeption not handled, also and

DRIVER_IRQL_NOT_LESS_OR_EQUAL

what failed: VTGKModeDX32.sys

After installing driver on Troubleshoot mode same situation with BSOD.

Please help.

 

I'm also posting a memtest result i did this month, 10 passes 0 errors so it's definitly not a RAM error

Also the report from whocrashed

Code: Crash dump directory: C:\WINDOWS\Minidump Crash dumps are enabled on your computer. On Mon 25/09/2017 01:39:13 your computer crashed crash dump file: C:\WINDOWS\Minidump\092517-3437-01.dmp This was probably caused by the following module: ks.sys (0xFFFFF80197F41BF1) Bugcheck code: 0xD1 (0x58, 0x2, 0x0, 0xFFFFF80197F41BF1) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL file path: C:\WINDOWS\system32\drivers\ks.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Kernel CSA Library Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. On Mon 25/09/2017 01:39:13 your computer crashed crash dump file: C:\WINDOWS\memory.dmp This was probably caused by the following module: ks.sys (ks!KsPinAttemptProcessing+0x601) Bugcheck code: 0xD1 (0x58, 0x2, 0x0, 0xFFFFF80197F41BF1) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL file path: C:\WINDOWS\system32\drivers\ks.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Kernel CSA Library Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. [/quote]

 

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 to run driver verifier.

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.

 

But is there something relevant on the Dumpfiles ?

I'll get Driver Verifier running from today

 

The single dump file doesn't show a lot, which is why I suggest driver verifier.

 

So after 2 days no BSOD was produced, i've already disabled the verifier

 

Hi Shirubidu,

I have looked at your event log and the information WhoCrashed provided, both in regards to the amount of crashes.
Since it appears only 1 crash occured, there is most likely no reason to continue troubleshooting as one-timers are due to small corruptions in the memory which are resolved after rebooting the system and do not come back.

 

I got another BSOD now only with the code IRQL_NOT_LESS_OR_EQUAL 1h after my computer wakes up from suspension and while watching a youtube video, attaching it below

 

Upload the kernel dump, C:\Windows\memory.dmp, to onedrive, dropbox or google drive and post a share link.

 

Here's the dump file: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

 

Got another one with the same code as the last one, this time while playing Gigantic, here comes the attachment

 

So i started searching until i found this out:





Looks like the older versions of razer drivers are more recent than the newest ones, can this trigger bsods ?
If yes, i'll consider uninstalling Razer Synapse 2.0 and get back my old headset and my Realtek Audio Driver that comes together with the mobo

 

Update the drivers of your Razer mouse or reinstall them.