According to the sticky, it's likely to be a driver issue:
0x0000000A: IRQL_NOT_LESS_OR_EQUAL
When people see this error, they see the IRQ part and assume that this must be caused by an IRQ conflict. This is not the case. It is caused when a kernel mode process or, more commonly, a driver attempts to access memory that it shouldn’t. If you receive this error, you should be thinking about the drivers you have installed. Are they certified to work by Microsoft?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.