You are totally right, I fixed it myself. What I was sayin is not to jump to conclusion that it is faulty RAM all the time. The problem here was physical. The new master HD Maxtor didn't like to have a slave HD with a jumper in slave position. To work efficiently, it had to be setted on cable select. Since then I absolutely had no crash.
Furthermore, To make sure it wasn't my RAM I had to remove one by one to test them. I tested them separately with MemTest86 and then together. Then again no error on my RAM. Afterwards, knowing the RAM was alright, I had to test the clockage that is why I downgraded it to manual clockage instead of 2.4GHz. Then again it wasn't solving the problem.
I know you guys do all this on spare time and everything, but still, you chose to be tech in this forum, just beware of what you say, people might spend a fortune to fix their problems when the problem could be solved by other means.
I hope this will help other to fix similar problem, and don't take me wrong cause I know what it is to solve problems, that's what I do all day being a tech myself. In most of the cases you have done a tremendous job, so it's not cause you failed one time that you are a bad tech.
I was mad cause I had posted the info you required and you asked it again, that's why I reacted that way. So no arm, I will still continue to visit and promote your forums cause they provide a lot of pertinent information and solutions to miscellaneous subjects. So far everyone I refered to this site has been amazed so please take all benefit.
All the best,