Still getting this issue and Line 6 have resorted to " Try reinstalling the OS.." which is not an adequate response, im certain there is bad code in the driver but im not clued up enough on these sorts of issues on windows.
The exact cause of the error based on the fault code is
"A driver tried to access an address that is pageable (or that is completely invalid) while the IRQL was too high"
Attached is some info from the last BSOD mini dump using BlueScreenView, it confirms this cause.
Here is some further information I found regarding this error
=================================================================================
If the first parameter has the same value as the fourth parameter, and the third parameter indicates an execute operation, this bug check was likely caused by a driver that was trying to execute code when the code itself was paged out. Possible causes for the page fault include the following:
The function was marked as pageable and was running at an elevated IRQL (which includes obtaining a lock).
The function call was made to a function in another driver, and that driver was unloaded.
The function was called by using a function pointer that was an invalid pointer.
Resolution
To begin debugging, use a kernel debugger to get a stack trace.
If the problem is caused by the driver that you are developing, make sure that the function that was executing at the time of the bug check is not marked as pageable or does not call any other inline functions that could be paged out.
BCCode: d1 0x000000d1 <-- read this link
http://www.faultwire.com/solutions-fatal_error/DRIVER-IRQL-NOT-LESS-OR-EQUAL-0x000000D1-*1210.html?order=votes
