BSOD running system backup.

I must have forgotten to hit the upload button the first time. Attached for real now. My apologies.

Update. It seems to happen at random now. More at idle now, when I'm NOT actually using it.

On Tue 1/8/2013 11:04:47 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010813-25771-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x40CDB)
Bugcheck code: 0xA (0xB8C53C, 0x2, 0x0, 0xFFFFFFFF82F328AC)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


Is there more information I could provide to help solve this?

Update. I ran full memory scans, checked the hard drive. I have AVG that can't find any root kits or a virus. Double checked with tdskiller. All clean.

Is anyone able to figure out the problem from my memory dump?

Okay, tdsskiller didn't find anything. Does Microsoft Defender Offline reboot on its own when its done?

It looked like it was almost done and nothing was found, but I saw a blue screen (not a bsod) and it flashed so fast I couldn't read what it said. This was on a full scan btw.

I have the boot up USB ready for a memory test and I'm going to do that tonight.

Okay, the overnight mem test did show errors. I removed one stick this morning and got 4 clean passes. I'll run it tonight all night and then spend the weekend changing the memory and the slots.

I also reran the microsoft defender offline one more time and it made it through the whole scan and went back to the main menu without rebooting, so I am hoping that is it.

If I go a few days without a BCOD or reboot, I'll mark this solved.

Thanks for your help.

Okay, I might have a two part problem. I did have one bad memory stick, but the other passed 22 sweeps. Currently only using the good one.

I did turn on the driver verifier and got a crash and uploaded the latest dump file.

Please let me know what you find.

Thanks

Dsprague said:

I took a look at your dump files and two things come to mind while looking at them, first most of them are pointing to memory corruption, and second most of them can be caused by drivers doing things they are not supposed to. So with that said there are two things I would recommend you try:

Firstly since its a lot faster than the second try turning Driver Verifier on by following this tutorial let it run until you get another BSOD then post your new dump files, or if you can not boot and only get the BSOD then boot into safe mode and disable Driver Verifier from there. If however you run Driver Verifier for 24 hours or so without BSOD or the new dump files fail to pin point the cause I would like you to run Memtest86+ for at least 8 passes if not more. Here is a tutorial on how to do that:

Test ram with Memtest86+

If the Memtest comes back with errors it becomes process of elimination, removing ram modules to isolate the bad ram or testing to make sure that the ram slots on the mother board are still working properly.