overclocking and a blue screen

Well, not specifically. :-)

For digital circuits there is only three things that matter : timing, timing and timing ... :-)

I mean that one has within the circuitry things called 'registers' that hold values and the machine's behaviour depends on those values. The registers must be able to change value which means that for a short time, during the changes, the value is neither one thing nor the other. They ought only be read when in a valid/meaningful state. Overclocking can ruin the usual co-ordination b/w components ie. regulating who should be looking at what registers for a value and when. Not all components can/will respond in some like manner when sped up.

A BSOD indicates some inconsistency has occurred which is not recoverable. For your machine in it's current setup E@H work has hammered some particular pathway beyond it's design criteria - which is what overclocking really means - aka driving at some speed in a car which wasn't originally considered as safe for said speed. Failure to overclock isn't a failure so much as ambition denied.

Consider un-over-clocking.

Cheers, Mike.