irql not less or equal BSOD

Hi abccormac,

Welcome to the 10forums.

Please disconnect every USB device, except for mouse and keyboard.
Please uninstall Google Chrome while troubleshooting.
Please remove / disable items from the startup in taskmanager
These programs could interfere with the boot process giving you trouble and increase the boot time.

The 0xA, 0xD1 and some 0x3B are speaking of memory corruption.
This has 2 sides

• A driver tried to access corrupted data from the memory
• A driver tried to access a wrong/invalid address from the memory

Please test your memory using MemTest86+
If MemTest86+ gives a final result of zero errors, run driver verifier

Diagnostic Test

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

   Note

MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

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.

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.

Code:

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff68001301658, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80145e10670, address which referenced memory

Code:

BugCheck 3B, {c0000005, fffff80114090e8d, ffffd000266158a0, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

Processing initial command '!analyze -v; !
2: kd> !analyze -v; !
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80114090e8d, Address of the instruction which caused the bugcheck
Arg3: ffffd000266158a0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Code:

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000002, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff801aeb40e58, address which referenced memory

Use the computer less then normal as the performance could be horrible bad.

Give it another 24h as instructed.