Hi Case,
It is great as you can solve your problem by yourself. Over 50% of the problems in this forum are related to faulty RAM and the problem owners keep on asking me how sure it is faulty RAM. I am not Jesus and I cannot guranteer my recommendation are always correct.
I've analysed your minidumps. One minidump had corrupt module list which may be caused by bad RAM or software driver error. Bugcheck code 7F with NT status code 0000000d is usually related to hardware error. It maybe faulty RAM, CPU or motherboard. Two of your minidumps crashed at SwapContext which is windows's context switching and it only crashes unless it is hardware error. The conclusion of your minidump is hardware problem. Which hardware component is faulty and base my pass statisitcs for similart problem. My conclusion is 60% RAM, 20% is motherboard and 10% is CPU or PSU. As you already confirm that it is faulty RAM and your finding will be part of history record and it would help me to resolve similar problem. Thanks for your sharing your experience with us as some people never feed their result.
The debug report of your minidumps are as folllowing. If you encounter similar problem later and most likely it is faulty RAM
Mini073005-01.dmp 0A (0015e3e0, 00000002, 00000001, 804e7aa6) module list might be corrupt
Mini072405-04.dmp 8E (c0000005, bf80f7f4, f86156f8, 00000000) win32k!IsTrayWindow+45
Mini072405-05.dmp 7F (0000000d, 00000000, 00000000, 00000000) nt!SwapContext+95 -> nt!KiSystemFatalException+f
Mini073005-02.dmp EA (8222d618, 820f3650, f8969cb4, 00000001) win32k!xxxMsgWaitForMultipleObjects+b0 -> nt!KiSwapContext+2e
Mini080205-02.dmp 24 (001902fe, f8654234, f8653f30, f838ad7a) Ntfs!NtfsAreHashNamesEqual+b
cpc2004