The infamous "c0000005" again.

I tried without virtualization. Same results.

According to hwinfo logs there is always thermal throttling and critical temperature when the apps crash. Sometimes origin crashes and bf4 exits automatically, sometimes bf4 crashes with c0+5. I thought that this thermal throttling is the sign of higher Tjmax, 100°C instead of 85°C. The T case is 67°C by this CPU and usually around 50°C it started to throttle. But one or two days before I set the CPU fan to 200RPM just to try out and the core temp reached 60°C without any issue. Now according to hwinfo it throttled around 45°C. So something is still not okay with the system, not to mention that throttling should not cause app crashes in theory. I'll try out with a different heatsink if I manage to get one. The current one might not lie properly on the CPU, it has a broken fastener which I managed to wire together. Maybe that's the problem, but I somehow doubt it.

Ok. I found the cause of this throttling sign. The headers are at the end of the generated CSV file too. So the plot.ly plot viewer converts them to a true value and shows it as true on the graph. So in reality it wasn't any throttling according to the logs. Then this is not a temperature issue, this is most probably a RAM issue. I'll try it with the high density rams, maybe the new bios made the mobo compatible with them.

Hey... @ET-inf3rno

Try this : https://www.youtube.com/watch?v=oJ0hz9JkLgM

May will work..

__________________________________________________________________________

If is answer working pls give me XP.....
If is answer good for you accept * sulution.....
Have a NICE day.....
Do not copy my post.....
__________________________________________________________________________

Thanks, but I have already done all of these. :-) I had problems with my USB HUB. Maybe removing that will affect the problem. Another idea that I put back my wifi card and check whether the ethernet connection is faulty. I'll check the heatsinks of the north and south bridges too, maybe the mobo overheats. The mobo temp sensor shows at most 45°C though.

ok @ET-inf3rno 

I downloaded bluescreen viewer and windbg and checked some old BSOD dump I had before the BIOS update. They are caused by chrome while watching a flash movie. The origin of the error was nvlddmkm.sys and the code is 0x50. https://msdn.microsoft.com/en-us/library/windows/hardware/ff559023(v=vs.85).aspx PAGE_FAULT_IN_NONPAGED_AREA It is just the same as with origin and bf4. It tried to read a memory address which did not belong to it. According to ms this can be driver, hardware or ram problem. I tested L2 cache, video memory and system memory many times, but they always pass the tests. So this can be a motherboard hardware issue or an nvidia driver issue. I vote on the nvidia driver and I'll try out older versions again. Maybe they will work better with this new BIOS. I'll try out the driver verifier too, maybe I find out more.

I am using a different sata power cable and a different sata data cable now. I haven't had TDR or c0000005 for a day, so maybe this is the solution. I'll wait a week and let's see what happens. my PSU tester arrives 2 weeks from now, after I will be able to test the sata power cables and other power cables as well. If the system is still stable and the problem is not with the sata power cables, then I'll buy a sata data cable tester as well and end this story. I hope this will be the solution.

We have finger crossed for u 👿

Thanks, but did not work. :-( At least I have a new record, 6 hours bf4 without errors. I increased the fan speed from 800 to 1300, so that can be the cause as well, I don't know. Maybe the motherboard overheats or this has something to do with themal expansion. I just bought a new SSD, I'll install win10 enterprise on that and check with that operating system too.

I removed the nvidia driver with DDU and installed a latter one. People claimed that this 347.52 is stable and does not have TDR. I did not have a TDR and a c0000005 error since then, but I guess it takes only more time to get the message. I installed the system with the BIOS having the old CPU microcodes and with a possible faulty SATA data cable, so there is a chance it is corrupted.

At last I found a test which indicates the problem with the nvidia and the usb drivers. So I don't have to play 24/7 to test the system, which was getting burdensome as I made the system more and more stable. Now it takes 6+ hours of gaming to produce a c0000005 error or several days browsing to get a TDR. I'll get my thermal paste, PSU tester, SATA cables, etc. this week. After that I start to try out possible solutions again.