Asrock z170 gaming k6 Dr debug errors

Last night I got a blue screen on my asrock z170 gaming k6 (not the first one, but I think the other ones had different reasons, and they stopped anyway) on win 8.1 while doing some average work, with something like IRQL NOT LESS OR EQUAL, I restarted, and got two other bluescreens before windows could finish loading: thread expection not handled. So I went into the uefi bios and disabled every c state and cpu slight overclock, I restarted, and before the pc could output any video, it started giving Dr debug codes, I'm getting a few different one (apparently randomly) : d0, 5d, 62, 79, 00, 19, 04, 40. I tried removing the mobo battery and resetting the cmos hundred times, removing the ram and moving it in every possible combination, removing the vga and switching to the second bios... Nothing fixed it, I'm still getting the same errors. It looks like the mobo is broken to me, but I don't want to rma it for nothing.
Do you have any ideas?
Thanks.

Edited by Filoppi - 21 Jan 2016 at 7:32am

I unplugged everything from the mobo (step by step, testing every time) It's just the ram, the cpu, the heatsink and the hdmi monitor. Not even a video card or hard drivers or any usb are connected, so that is not the problem. And the bios is I think 1.90, or anyway, the last stable one, I checked it two days ago, and it was still up to date.
The psu is a new evga 750 g2, which does not seem to be the problem. It's one moth old, just like the mobo.

Edited by Filoppi - 21 Jan 2016 at 7:25am

Samsung ssd 870 evo. Logitech mouse and keyboard. Zotac 980ti amp extreme. That is all.

You are right, I'm sorry, the ram is 2x corsair CMK16GX4M2B3000C15. It was running at 3000hz like it's supposed to, but the cmos reset should have reset it to its default value. I just don't think these things matter, as the pc has been running fine for a month and it just got a me blue screen two days ago, also I removed all of them and it doesn't start anyway.
Buy yeah, it could be the ram, that is not supported by default (it was when I got the pc), I don't think that both modules could have broken at the same time. And I don't think it's the cpu, as I wasn't doing anything special while the pc broke, at least, it's not likely to be the cpu.
Also please notice that the mobo is giving me tons of different error, depending on whether I just reset it or not, and where the ram is, and that sounds very strange to me.

But I'm pretty sure something is broken. tonight I'm going to test another psu.

So. I tried another working psu and it gives the exact same error. I'm pretty sure it's the mobo but there is a small chance it could be the ram or the cpu.
The ram could be unsupported by default. When you switch the bios selection, do you also have to flash a new fw for that or do they share the same?
Because I'm sure that the ram default timings use to work on a previous bios version, the I used an xmp and upgraded the bios.
Also, how and why could a cpu break?
I just think it's the mobo. Any ideas?