Legit Reviews

Ok,
I have windows 7 SP1 and I had that error(Stop 0x0000003B (c0000094, fffff8800ff22e54, fffff880098897f0, 0) - SYSTEM_SERVICE_EXCEPTION)
so should I download the hotfix?

Only if you have Cyberlink Youcam installed too. Try this, yeah, I'm full of try this kind of info. Download Driver Sweeper and run it for all ATi/AMD drivers.
http://phyxion.net/Driver-Sweeper/Driver-Sweeper/
After the sweep reboot. Then install the latest beta drivers from AMD.
http://support.amd.com/us/kbarticles/Pa ... river.aspx

If you have your GPU overclocked set it back to stock and see if any of that helps.

Ok, I don't have Cyberlink Youcam installed, so I won't install the hotfix.
I already updated my AMD driver yesterday ( after the BSOD) to see if it helped.( and I don't know yet if it helped)

Well... It's been over a day and I don't see a BSOD error message. Is it working fine now?

I don't know, most of the time it happens 2 times a week.

Now I got this error
0x00000124

Try this... Pull out all RAM except 1 stick. Run it for a while and see if you get a BSOD. If you do pull that stick and try the other 1 by itself.

I think I am just going to return to stock speeds or lower my overclock, i am getting sick of all those errors
Maby my CPU isn't a good overclocker.
I want to thank you very very much for helping me to solve this problem and all the time you spend on this problem.

I would try the RAM first. It sounds like you have a piece of bad hardware. Since just about every error is different that leads me to believe it's RAM. I had a similar experience not too long ago and it was in fact RAM.
http://forums.legitreviews.com/about30319.html

Let me know if you do go back to stock and still have problems.

I have the same motherboard as you and a I7 860 @ 3.66. The memory I have is this http://www.newegg.com/Product/Product.a ... 6820145314 Like Major_A said, it's probably the memory. Gook Luck!
Edit: My rig runs 24/7 running F@H which runs my cpu @ 100% all the time on a Corsair H-50 temps are 67C.

Just an update:
I have lowered my overclock to 3.5GHz (160x22) at 1.225V and I havent had a BSOD since.
I also found out that a pc makes a dump-file after a BSOD, so I debugged the latest file with WinDbg and the results were that my processor was the reason for the BSOS's.

Glad to hear it isn't crashing. I knew the crashes created dumps but I wasn't aware there was a program you can use to open them up easily.