BSOD 0xFFFFF801330CD3E1) Error: IRQL_NOT_LESS_OR_EQUAL after reboot

Dump is not much help. Looking at the WER data in msinfo32.nfo, you had 3 Bluescreens in 3 minutes. All were 0x00000a.

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.

Can also be caused by memory problems. You have DIMMs in slots A2, B2 and C2. The manual recommends A1, B1 and C1 for Triple Channel. I'm sure you've been running this way for a long time but it might be worth moving them to see if it makes any difference.

Attachment 218014

If that doesn't make any difference then I suggest running Driver Verifier to see if this is driver induced.
===================================================
Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes. Machines exposed to Driver Verifier may run very sluggishly due to the stress being applied to the drivers.

Driver Verifier - Enable and Disable in Windows 10

Pay close attention to PART TWO and make sure the correct boxes are checked.

   Warning

It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

Always create a Restore Point prior to enabling Driver Verifier so you have a way to recover if it goes haywire. Seldom does but it can happen.

What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the Beta log collector and upload the resulting zip file.

May also want to run memtest86 to test your ram. A minimum of 8 passes with 0 errors is required for a good test.
Please take a picture with your phone or a digital camera an post it here when complete. Any failure means you have defective ram and it needs to be replaced.

You can follow these directions here but use memtest86 instead of memtest86+:
===================================================
Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

• RAM will accept and keep random patterns of data sent to it
• There are no errors when different parts of memory try to interact
• There are no conflicts between memory addresses

Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

   Warning

MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.

If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

   Note

MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.

Take a picture when done and post in the forum please.

The Driver Verifier BSOD points to a problem with a Brother driver:

Code:

BugCheck C9, {24c, fffff80143470ba0, ffffac8ff6406980, 103}
*** WARNING: Unable to verify timestamp for BrSerIb.sys
*** ERROR: Module load completed but symbols could not be loaded for BrSerIb.sys
Unable to load image \SystemRoot\system32\DRIVERS\BrUsbSIb.sys, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for BrUsbSIb.sys
Probably caused by : BrSerIb.sys

Code:

Driver Description:  Brother Serial Interface Driver
Driver Update Site: http://www.brother.com/html/download/index.htm

Code:

Driver Description:  Brother Serial USB Driver
Driver Update Site: http://www.brother.com/html/download/index.htm

Do you have a Brother printer installed? If so, download and install the latest driver for it, see if that makes a difference.

Run Memtest for 12 hours. No problems.
Have updated Brother drivers.
Now a case of wait and see.

Thanks to everyone for all the help.

ow many passes did memtest complete?