New
#1
BSOD DRIVER_IRQL_NOT_LESS_OR_EQUAL (ks.sys)
Got this BSOD while playing The Walking Dead.
Attached the dumpfile below.
Got this BSOD while playing The Walking Dead.
Attached the dumpfile below.
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.
WarningPlease 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.
NoteYour 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
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
Last edited by Shirubidu; 04 Oct 2017 at 08:01.
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.