This error indicates that some driver at the kernel level attempted to write to paged virtual memory (that means slow virtual memory that is baked by a hard disk's paged file) during interrupt request that was meant to be processed really fast. This is most likely a software fault.
Windows has several interrupt request levels (more info here and here). Some IRQLa are designed to handle system critical stuff like power mode changes, CPU clock ticks etc. The higher the level - the less stuff a driver can do. For example during a power failure a driver cannot access any memory - it's too slow for that.
If you want to troubleshoot this and pin-point a faulty driver you'll need to open memory dump that was collected right after the crash. You can double check the location of the dump in System Properties > Advanced > Startup and Recovery > Settings > Dump file
. See the picture

You can then open dump file with tools, such as WinDbg (download the right version for your Windows) and in WinDbg you can run analyze -v
on the dump. This should tell you which driver is likely to be at fault.
0xFFFFF800030E518F
attempted towrite
to memory address0x0000000000000080
while at IRQL2
. This could occur because of a bit-flip in memory, but smells to me more like a driver bug. The one time this occurred to me involved a bad Wifi driver, which I downgraded. Whoever supplied the instruction at the0xFFFFF8...
address is the guilty party and should be disabled.