Different BSODs in ntoskrnl.exe, (Codes: 0x3b - 0xc5 - 0x124)

I apologize, i actually did the Memory testing with Memtest86+ - i wasn't aware that there were different ones.

The Power supply calculator says i need a minimum of 338 Watts and recommends a 388 Watt PSU. I am currently using a 750W bequite PSU (because it was on sale and cost just as much as a 500W PSU, so i bought it. Heard good things about bequite and i am using it for a couple of years now, not sure how long exactly.

I ran Furmark for 15 Minutes and it pushed the GPU quite a bit harder than the Valley Benchmark. Temperature rose up to 68°C after a couple of minutes and stayed there for the duration of the test (again, i googled and people said that 15 min are fine for a stability test) If you think a longer test could yield better results, let me know and i will torture the GPU a little more.

When i took the Screenshot (i ran it in FullScreen), Closed Furmark and pasted the Screen into Paint, it actually showed Chrome beneath the actual Test. Not sure what that is about.

I am running Prime95 right now (can you hear the CPU screaming in the background?) and the Temperature just passed 40°C and is climbing rather slow from there on. I will let it run for the 2 hours stated in the Tutorial and then I'll try FurMark again. Maybe in windowed mode, so i can get the Screenshot.

Edit: Here is the Speccy Snapshot ( http://speccy.piriform.com/results/d...ON7enZUsKuRAnR )

Keep in Mind that the Snapshot was taken while Prime95 was running, the idle Temperature of the CPU is pretty much at room temperature. Never really paid attention to it when it wasn't being stressed, but i think it usually hovers around 15-20°C.

Edit2: I just ran Prime 95 for about 2 hours and it failed to produce the requested log file because i'm an Idiot and ran it straight out of the archive without extracting it first.

It's past midnight and i am tired, i will run it again tomorrow. In those 2 Hours, the CPU performed perfectly and the Temp never rose above 43°C.

Could it be that it is somehow the Game itself that causes the Error? (EU4 causes the Crash way more often than other games, i just assumed it's because it's a lot heavier on the CPU than other games.)

If you havent got any error/crash/BSOD etc during all those tests, then tests are all ok.

About the game, yes, it is possible that a poorly coded game can cause a stop 0x124 BSOD.

Slyve said:

One last question, is there any kind of tool that i could use while the game is running to figure out if it actually is the game itself? Some sort of real time logging tool or something similar?

I am not aware of, but I will see if anybody else can tell anything about it.

What I have noticed.

Looking at Speccy.
It shows very low 12V (9.864V) and very low vbat at 1.6V

Check the voltages in Bios.
Check your motherboaed bios battery. I should be 3.0V or very close. (Cmos battery)

Voltage
CPU CORE:
1,188 V

DRAM:
1,500 V

+5V:
5,010 V

+12V:
9,864 V

+3.3V:
3,288 V

CMOS BATTERY:
1,608 V

According to your bios your 12V & 3.3V are good.

Check and see if speccy program is up to date.
Their is a chance it's not working properly with your motherboard.

A motherboard battery can be bad when it new or last for years.

If was me I would just use a DVOM and measure the volts.

If you are getting more BSOD please post new logs so Archie can have a look.