First of all, you shouldn't use Driver Cleaner or any other automatic 3rd part driver installers as they can install wrong or problematic driver versions.
Code:
BugCheck A, {fffffa81f4c95131, [COLOR=#ff0000]2[/COLOR], 1, fffff80002b67a6b}
This bugcheck means that pageable memory was referenced at an IRQL too high. More specifically it was referenced at IRQL 2 (Disptach Level), 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.
Code:
3: kd> [COLOR=#008000]kv[/COLOR]Child-SP RetAddr : Args to Child : Call Site
fffff880`009b0b08 fffff800`02acaae9 : 00000000`0000000a fffffa81`f4c95131 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx <-- The BSOD.
fffff880`009b0b10 fffff800`02ac9760 : fffffa80`08492000 fffff880`1390a9e1 fffffa80`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009b0c50 fffff800`02b67a6b : 00000000`002fe6b9 00000000`00000000 00000000`00000000 00000000`00000000 : [COLOR=#ff0000]nt!KiPageFault+0x260[/COLOR] (TrapFrame @ fffff880`009b0c50)
fffff880`009b0de0 fffff800`02b6f324 : fffffa80`0848f000 fffff880`1395019e fffffa80`08492000 fffffa80`07b4c040 : [COLOR=#0000ff]nt!PpmQueryTime+0x4b[/COLOR] <-- some Processor Power Management routines.
fffff880`009b0e10 fffff800`02bc34bb : 00000007`852a3de0 fffff880`037d5180 fffffa80`07ca0530 fffffa80`07ca0678 : nt!PpmSnapIdleAccumulation+0x94
fffff880`009b0e60 fffff800`02bee122 : 00000000`ffffffed 00000971`bae9060b fffffa80`0c921b50 00000000`00000001 : nt!PpmPerfRecordUtility+0x4b
fffff880`009b0ed0 fffff800`02ad5d0c : fffff880`037d5180 fffffa80`000328c2 fffffa80`06b2d128 00000000`000000c2 : nt!PpmPerfAction+0x22
fffff880`009b0f00 fffff800`02ace715 : 00000000`00000000 fffffa80`0af51060 00000000`00000000 fffff800`02bee100 : [COLOR=#0000ff]nt!KiRetireDpcList+0x1bc[/COLOR] <-- Deferred Procedure Call list being finished
fffff880`009b0fb0 fffff800`02ace52c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5 (TrapFrame @ fffff880`009b0e70)
fffff880`0a867bf0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
The Processor Power Management routines probably raised the IRQL to perform some tasks but something tried to access pageable memory which we cannot find, especially seen as this is a minidump.
Lets move onto the other .dmp file you had originally.
Code:
BugCheck 1E, {[COLOR=#ff0000]ffffffffc0000005[/COLOR], fffff80002d7fbfd, 0, 2f9}
This bugcheck indicates a Kernel Mode exception has occurred that it couldn't handle.
More specifically an Access Violation occurred which indicates the CPU tried to access memory that it couldn't address.
Code:
fffff880`07179908 fffff800`02ade488 : 00000000`0000001e ffffffff`c0000005 fffff800`02d7fbfd 00000000`00000000 : nt!KeBugCheckExfffff880`07179910 fffff800`02a92bc2 : fffff880`0717a0e8 fffffa80`08984f20 fffff880`0717a190 00000000`00000100 : nt! ?? ::FNODOBFM::`string'+0x482fd
fffff880`07179fb0 fffff800`02a9173a : 00000000`00000000 00000000`000002f9 00000000`00000200 fffffa80`08984f20 : [COLOR=#ff0000]nt!KiExceptionDispatch+0xc2 [/COLOR]<-- The exception being dispatched.
fffff880`0717a190 fffff800`02d7fbfd : fffffa80`00000001 fffffa80`06b1b660 fffff880`04b51900 fffffa80`746c6644 : [COLOR=#ff0000]nt!KiPageFault+0x23a[/COLOR] (TrapFrame @ fffff880`0717a190)
fffff880`0717a328 00000000`00000000 : 00000000`00000000 fffff960`000f9d6c fffff900`c01fdc60 fffff900`c01fdca8 : [COLOR=#0000ff]nt!NtReadFile+0x52b[/COLOR]
With this .dmp file I had to dump the raw stack as nothing else gave off a clear signal as to what was the cause.
Code:
Unable to load image \SystemRoot\system32\DRIVERS\klif.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
[COLOR=#ff0000]klif+0x631f0[/COLOR]
This particular driver is part of Kaspersky Anti Virus.
I would remove Kaspersky at least as a test to see if this is part of the problem.
Use this removal tool
For the time being I would replace it with Microsoft Security Essentials.
Microsoft Security Essentials - Microsoft Windows
Code:
Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
[COLOR=#ff0000]atikmpag+0x46c12[/COLOR]
AMD display driver...
Code:
0: kd> [COLOR=#008000]lmvm atikmdag[/COLOR]start end module name
fffff880`13668000 fffff880`14578000 atikmdag T (no symbols)
Loaded symbol image file: atikmdag.sys
Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
Image name: atikmdag.sys
Timestamp: [COLOR=#ff0000]Fri Apr 18 03:13:16 2014[/COLOR] (53508A3C)
CheckSum: 00EAEEE6
ImageSize: 00F10000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
It's a new version which I have seen a few issues with, have you installed the correct version, given that you have been using programs like Driver Cleaner have you removed the previous version properly?
Try rolling back to a version late 2013.
Code:
Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
[COLOR=#ff0000]Rt64win7+0x7ccb[/COLOR]
Lastly I see your Realtek Network Ethernet controller Driver causing issues.
Code:
0: kd> [COLOR=#008000]lmvm rt64win7[/COLOR]start end module name
fffff880`0503b000 fffff880`05122000 Rt64win7 T (no symbols)
Loaded symbol image file: Rt64win7.sys
Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
Image name: Rt64win7.sys
Timestamp: [COLOR=#ff0000]Thu May 08 10:27:02 2014[/COLOR] (536B4DE6)
CheckSum: 000E7862
ImageSize: 000E7000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
It's a new version, is it the correct version?
Try re-installing it or installing an older version.
Post back the results :)
