Random BSOD's, error 0x8000000000000002

Welcome to SF Claus :) .

Although I would like having more than two dump files, the problem appears to be a driver
issue at the moment, I suspect AVG but I'm not pointing any fingers yet.

Please follow these steps to help and cover the culprit:

Arc said:

Your crash dumps are not showing any finite probable cause.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Arc said:

First run it with all the existing/installed RAM modules. If it comes with no error, all is good.

But if it starts showing errors, Stop testing. Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:
No code has to be inserted here. It is a RAM, a bad RAM.

But if you have got a result like that:
No code has to be inserted here. It is a motherboard issue. The particular slot is bad.

If memtest comes free from errors, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

• BTW, the BIOS is extremely old but we will only keep that in mind for now.

Let us know the results.

I'll be here :).

Hmm, well DV (Driver Verifier) didn't find any faulting drivers that usually indicates
a hardware issue, on the other hand a single dump isn't enough let DV crash the machine a few more times
and post the new dumps the same way as before :).

I also recommend, since you populated all DIMM slots, updating your BIOS.

   Warning

Flashing the BIOS is a risky procedure. If you are uncomfortable
performing it yourself have a technician perform it for you.
Regardless, flashing is at your own risk.

Prior to updating the BIOS, reset the BIOS back to default:

• CLR CMOS

   Note

Write down the current value of the SATA Mode!
Its either AHCI or IDE.
After resetting the CMOS go back and verify the value for SATA Mode is what it was
when the OS was installed.

If any component is overclocked reset it back to stock speeds!

Current BIOS:

Code:

BiosVersion = 1103   
BiosReleaseDate = 07/11/2008

Update available:

Code:

Version 2105
P5Q3 Deluxe/WiFi-AP @n BIOS 2105
Enhance the compatibility with certain memory.
                     1,19 MB - update 2009.07.03

• Motherboards - P5Q3 Deluxe/WiFi-AP @n
• Attachment 300344

Any updates :)?