Windows 10: Bsod, irql_not_less_or_equal

I want to ask you for help to find the cause of bsod.
Windows 10, random bsod after a few hours of use

Attachment 35301

:)

 

DRIVER_OVERRAN_STACK_BUFFER Windows 10

The other BSODs i get are

PAGE_FAULT_IN_NONPAGED_AREA (win32kfull.sys)

And

IRQL_NOT_LESS_OR_EQUAL

 

BSOD - IRQL_NOT_LESS_OR_EQUAL

Hi,

I have been experiencing BSODs in the last 4 days.

The last BSOD showed me "IRQL_NOT_LESS_OR_EQUAL" and I don't know what happened.

(I forgot what the previous BSODs error, I believe it was not "IRQL_NOT_LESS_OR_EQUAL").

Here is the link for my last 3 minidumps file and MSinfo32.

Minidump_and_MSinfo32.zip

Please, I need your help.

Thanks.

 

Hi krustybbr,

Welcome to the 10forums.
Please read BSOD Posting Instructions

 

can you help me? *Biggrin

First post edited, thank you

 

The thing with editing a post is, is that there is no notification, so we don't know if anything has changed.
My point, next time please make a new post with the uploaded zip file *Smile

I'll take a look and see what I can find

 

I uploaded, now I'm waiting for an answer

Attachment 35320

Minidump
Attachment 35321

Attachment 35323

 

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

A windows driver is blamed in the crash, 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.

 

Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please read and run driver verifier.

A windows driver is blamed in the crash, 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 having selected verifier, I just got a new blue screen

New minidump
New bluescreenview image

 

Try to boot into safe mode and enable driver verifier, how to boot into safe mode

 

It is for me to do vefier driver in safe mode or regular Windows?

 

Activate driver verifier in safe mode and perform it in regular windows.

 

just select these three or any more?
I/O Verification
Force pending I/O requests
IRP logging

 

That is correct, only those 3.

 

I did what you asked, began to give blue screen at logon Windows

Minidump