View Single Post
26 Jan 2013  
x BlueRobot


BugCheck D1, {fffffa800a126004, 2, 0, fffffa800904922f}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
Usual causes:  Device driver
It seems there is most likely a problem with the drivers, a driver has attempted to access a memory address which isn't yet present, the current IRQL level (DISPATCH_LEVEL) means that other threads will need to be scheduled to run, although a driver has tried to interrupt the CPU when it shouldn't have, and this has caused the bugcheck.

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours: Additional Help - Using Driver Verifier to identify issues with Drivers


Start Menu\Programs\Driver Genius
These third-party driver updating programs are not needed and can cause problems, it is best to search for driver updates manually and then install these drivers through the Windows Device Manager.

Scan for any missing, modified or corrupted protected Windows files with:
My System SpecsSystem Spec