New
#11
Code:BugCheck A, {fffff0800ad189c0, 2, 0, fffff80002a98ef2} Probably caused by : memory_corruptionmemory_corruption doesn't necessary mean that a RAM module is faulty, it can also point to a object which corrupted the RAM at the time of the crash, for instance a corrupted driver or program. Paging files and the CPU caches can also be causes.Code:Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
Follow these steps -
Test for any corrupted drivers, by running Driver Verifier for least 24 hours, stop the test if a BSOD occurs before this time frame. Driver Verifier will place stress on the drivers within your system, which will cause corrupted drivers to crash and hopefully be pinpointed.
Memory:
Run Memtest86+ for least 7-8 passes, and preferrly overnight as it can take a while to fully complete.
Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.
Test each RAM stick and every motherboard DIMM slot available.
Remove the graphics card too, just to make sure the Video RAM of the card is not causing any problems; only follow this step if your motherboard has a onboard graphics chip or you have an alternative card.