Hi Tw1st,
The culprit is faulty memory. You can run memtest to stress the ram. If memtest reports the ram is faulty, ram is bad. However Memtest is not a perfect tool to test the memory as some faulty ram can pass memtest.
Suggestion
1. Check the temperature of the CPU and make sure that it is not overheat (ie temperature < 60C)
Make sure that the CPU fan works properly
2. Reseat the memory stick to another memory slot
3. Downclock the ram
4. Clean the dust inside the computer case
5. Make sure that the ram is compatible to the motherboard
6. Check the bios setting about memory timing and make sure that it is on
If it still crashes, diagnostic which memory stick is faulty
1. Take out one memory stick. If windows does not crash, the removed memory stick is faulty.
2. If you have only one memory stick, replace the ram
Summary of your debug report
Mini102905-01.dmp BugCheck 1000000A, {9d086240, 2, 0, 80522c18}
Mini102905-01.dmp Probably caused by : memory_corruption ( nt!MiDeletePte+198 )
Mini102905-02.dmp BugCheck 1000000A, {9d086240, 2, 0, 80522c18}
Mini102905-02.dmp Probably caused by : memory_corruption ( nt!MiDeletePte+198 )
Mini110505-01.dmp BugCheck 19, {20, 859ac708, 859ac870, a2d0013}
Mini110505-01.dmp Probably caused by : cmudax.sys ( cmudax+b4b3c )
Mini110605-01.dmp BugCheck 1A, {41284, dd10001, 0, c0883000}
Mini110605-01.dmp Probably caused by : memory_corruption ( nt!MiLocateWsle+c1 )
Mini110605-02.dmp BugCheck 1000000A, {456ee104, 1c, 1, 80502000}
Mini110605-02.dmp Probably caused by : ntkrpamp.exe ( nt!KiUnlinkThread+c )
Mini110605-03.dmp BugCheck 19, {20, 85ee33d0, 85ee3538, a2d0004}
Mini110605-03.dmp Probably caused by : cmudax.sys ( cmudax+b4b3c )