Windows 10: IRQL_NOT_LESS_OR_EQUAL BSOD, Along with some more.

I regular intervals of time i keep getting this BSOD, it sometimes doesn't show for a week or 2, but it has started again 3 days ago with its constant crashing, along with CRITICAL_PROCESS_DIED, PFN_LIST_CORRUPT, SYSTEM_SERVICE_EXCEPTION,BAD_POOL_HEADER. All in the span of a week and some of them appearing since then. So i decided to go and run Driver Verifier as suggested in another thread, but when i enable it and try to boot i get DRIVER_VERIFIER_IOMANAGER_VIOLATION, as such i had to turn it off. Is there a way to resolve these problems? I have attached the driver verifier BSOD and the IRQL one. Attachment 89159

:)

 

Windows 10 PAGE_FAULT_IN_NONPAGE_AREA (win32Kfull.sys)

In the last two days I have had 3 crashes. They are:

SYSTEM_THREAD_NOT_HANDLED (dxgmms1.sys), 7/2/2016

IRQL_NOT_LESS_OR_EQUAL,
7/2/2016

PAGE_FAULT_IN_NONPAGE_AREA (win32Kfull.sys), 7/3/2016

I have uploaded the 3 compressed mini dump files along with a compressed systems info file to this site:

http://altairseven.com/BSOD/

Along with your assistance in determining what has caused these faults, I would like to learn how to read the dump files so I might be able to debug some of these myself.

Thanks...

 

Help with occurring BSOD

Hi Christian,

I am currently on Windows 10, Version 1607 (OS Build 14393.321). The error I get when I encounter the BSOD is a screen stating: IRQL_NOT_LESS_OR_EQUAL tagged along with Qcamain10x64.sys. The error message seems to be consistent every time it occurs.

I hope that helps.

-Janneus

 

Driver verifier is pointing to your DualShock3 driver.
Seh in Scarlet Crush (or if your device is from any other manufacturer; I cannot check because you havent uploaded the adequate data) for any update to the Xinput Wrapper driver. If available, apply it.

But, at the same time, test your RAM modules for possible errors.MemTest86+ - Test RAM Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.
Take a camera snap of the memtest86+ window before closing the program. Let us see it.
Screenshots and Files - Upload and Post in Ten Forums - Windows 10 Forums
___________________________________________________________________________________________
Code: BugCheck A, {38, 2, 0, fffff8037c57ca52} Probably caused by : memory_corruption ( nt!MiResolvePageFileFault+6ca ) Followup: MachineOwner ---------[/quote]

 

[/quote] Just uninstalled a DS3 Tool i had from motionjoy or w/e, wasnt using it, but had it installed apparently... Lets hope this works a bit.

 

Please dont forget to perform a RAM test using Memtest86+. It will be needed to arrive at a concrete decision.