Code:
BugCheck A, {fffff68000109008, 0, 0, fffff80002da83b6}
This bugcheck means that pageable memory was referenced at an IRQL too high. This is an illegal operation as pageable memory can only be referenced at IRQL 1 (APC Level) or IRQL 0 (Passive Level).
So why doesn't the IRQL lower to access the memory address?
Windows doesn't work that way for good reason.
An Interrupt request (IRQ) has been initiated it is serviced in an order of priorities, for example an IRQ has been sent to service an I/O and an IRQ has been sent to draw a Window for an application, the disk I/O is more important so it is put at an IRQL higher than the application request. Right, so the I/O IRQ has to be completed before the IRQL can lower to service the IRQs below it.
Now, when something tries to access pageable memory at an IRQL higher than APC level it generates a page fault because the memory has been paged out to disk, now this page fault cannot be resolved by the trap handler because the IRQL is too high but the page fault needs servicing.
It then becomes a stalemate, you can't complete the page fault because the IRQL is too high but you cannot lower the IRQL because it needs servicing so the system bugchecks.
However, the strange thing I've noticed is this:
Code:
[COLOR="red"]0000000000000000[/COLOR], IRQL
This IRQL wasn't too high,
Use Kaspersky's TDSSKiller Anti Rootkit utility
Anti-rootkit utility TDSSKiller
Uninstall these programs.
Code:
Start Menu\Programs\[COLOR="Red"]MotioninJoy[/COLOR] Public:Start Menu\Programs\MotioninJoy Public
Code:
Start Menu\Programs\[COLOR="red"]DAEMON Tools Lite[/COLOR] Public:Start Menu\Programs\DAEMON Tools Lite Public
Find alternatives as they're caused quite a lot of issues.
