BSOD 0x7F?

Does anybody know what BSOD 0x7F is? I've looked through a couple of overclocking guides and it wasn't in them.

"BSOD codes for overclocking
0x101 = increase vcore
0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore...have to test to see which one it is
on i7 45nm, usually means too little VVT/QPI for the speed of Uncore
on i7 32nm SB, usually means too little vCore
0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore
0x1A = Memory management error. It usually means a bad stick of Ram. Test with Memtest or whatever you prefer. Try raising your Ram voltage
0x1E = increase vcore
0x3B = increase vcore
0x3D = increase vcore
0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage
0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances
0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x
0x109 = Not enough or too Much memory voltage
0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)
0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r

BSOD Codes for SandyBridge
0x124 = add/remove vcore or QPI/VTT voltage (usually Vcore, once it was QPI/VTT)
0x101 = add more vcore
0x50 = RAM timings/Frequency add DDR3 voltage or add QPI/VTT
0x1E = add more vcore
0x3B = add more vcore
0xD1 = add QPI/VTT voltage
“0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances”
0X109 = add DDR3 voltage
0x0A = add QPI/VTT voltage"

Closest one is 0x7E. I'm 100% sure that the code that I'm getting right now is an 'F' not an 'E.'

Specs:
2500k
ASROCK extreme3
Corsair 2x4gb 1600mhz.

HTPC computer. Mild overclock, 4ghz. Prime95 Blend test.

If its a HTPC, you really don't need to overclock.

I did find a bit of info on the 7f though:

http://msdn.microsoft.com/en-us/li [...] s.85).aspx

Here are some suggested solutions:

STrange that that fixed it considering its not even related to overclocking.

Maybe the BSoD was wrong.

As I said, overclocking is a bit overkill for a HTPC anyways.

Glad to see you got a solution though.