Hi and welcome to TSF please follow the instructions here http://www.techsupportforum.com/f217/blue-screen-of-death-bsod-posting-instructions-452654.html
Here is the details of the 3 BSOD.Download the Avast Removal Tool (ART) from here -> save to desktop.
Boot into SAFEMODE - NO Networking. Then go to desktop, RIGHT-click on the ART icon and select Run as Administrator.
When complete - re-boot.
Install MS Security Essentials --> http://www.microsoft.com/Security_Essentials/
Then reset the Windows Firewall to its default settings -
START -> type cmd.exe -> right-click -> run as administrator -> type netsh advfirewall reset press enter
[font=lucida console]
BugCheck 109, {a3a039d895dfa524, b3b7465ee85dcde6, fffff88000d07058, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 109, {a3a039d895a698ad, b3b7465ee824c16f, fffff88000c6d058, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 109, {a3a039d895f9f586, b3b7465ee8781e48, fffff88000d40058, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]
1. Avast has been known to do this, hence the request for removalCause
There are generally three different causes for this bug check:
1. A driver has inadvertently, or deliberately, modified critical kernel code or data. Microsoft Windows Server 2003 with Service Pack 1 (SP1) and later versions of Windows for x64-based computers do not allow the kernel to be patched except through authorized Microsoft-originated hot patches. For more information, see Patching Policy for x64-based Systems.
2. A developer attempted to set a normal kernel breakpoint using a kernel debugger that was not attached when the system was started. Normal breakpoints (bp) can only be set if the debugger is attached at start time. Processor breakpoints (ba) can be set at any time.
3. A hardware corruption occurred. For example, the kernel code or data could have been stored in memory that failed.
Regards,Memtest - Instructions:
Download the ISO (or the .exe for USB drives) from here http://www.memtest.org/#downiso
Then (if you have chosen the ISO) burn the ISO using IsoRecorder: http://isorecorder.alexfeinman.com/W7.htm
Boot from the CD/USB and run the test (at least 7 passes per test) with only one stick of RAM in place at a time.
It is a time consuming process but it is the only way to be sure it isn't a RAM fault.
For your final test, run the test with all the RAM in place.
[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jun 14 12:52:58.945 2010 (GMT+12)
System Uptime: 0 days 2:07:30.959
BugCheck 109, {a3a039d895dfa524, b3b7465ee85dcde6, fffff88000d07058, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR: 0x109
PROCESS_NAME: System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jun 14 10:44:02.855 2010 (GMT+12)
System Uptime: 0 days 0:37:52.870
BugCheck 109, {a3a039d895a698ad, b3b7465ee824c16f, fffff88000c6d058, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR: 0x109
PROCESS_NAME: System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jun 14 10:04:45.507 2010 (GMT+12)
System Uptime: 0 days 4:03:08.912
BugCheck 109, {a3a039d895f9f586, b3b7465ee8781e48, fffff88000d40058, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR: 0x109
PROCESS_NAME: System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]
Another restart. This time Windows asks if I want to repair the start up, which I would very much like, but it randomly restarts soon after I accept. And now I am trying again, and it seems to be stuck at "Attempting repairs" after I said it could try rolling back to a restore point.stop: c0000221 Unknown Hard Error
\SystemRoot\System32\ntdll.dll
That would explain a fair bit. On the basis of that return your RAM.EDIT: Update - running Memtest86 after a second blue screen and I am getting loads of errors. Nice!