You can Window 8 Tree hug all you want Mystere, just stating a fact that Windows 8 doesn't like me overclocking and I have read the same thing with others having a problem getting the Blue Screen of death. And after i slowed it down they went away so there's a problem and it's not the hardware because it ran perfect under Windows 7. And all I can say is people aren't buying it..I wonder why? It was tailored toward the Tablet World and they made a big mistake thinging PC users would accept it for what it is.
Basically, you're trying to blame the paint on your car because the engine blows up from running it without any water coolant.
That is like blaming the coolant for your paint peeling
overclocking is a mystical beast, you can get 2 computers that run identical hardware and software and get different stability levels at different overclock levels.
if it runs stable at stock then gradually overclock untill it falls over at peak settings, then step back from that and retest for stability again and again, what worked under one set of circumstances may not work under others.
I'm saying that they're two unrelated things. A CPU executes code. Under normal conditions, this is a deterministic process. The CPU will always execute the same instructions the same way.
The problem here is that overclocking causes components to fail, and when they fail, they become non-deterministic. This means they can randomly flip bits in memory, randomly execute a different instruction, etc...
Think of a program executing the same way you would read a book. If two people read a book, and one of them is dyslexic, they will see two different things. Now, imagine the dyslexic person starts to blame the book for "not liking dyslexia". That's basically what you're saying here. A book can't make someone dyslexic, the same way code can't "not like overclocking". All the book can do is expose the dyslexia, much like code can expose a failing component.
If the code executes normally when not overclocking, but doesn't when you overclock. The only possible explanation is that the overclocking is at fault, because nothing has changed with the software.
As for why it works in Windows 7, it's impossible to say, but likely it's still failing.. just in a way that you may not notice (maybe memory that is not being used is failing, or the CPU is jumping to a place that executes valid code, or maybe the new code is using a feature of the CPU that 7 didn't, and that feature is failing while overclocking).
I can't count how many times I've seen people make these kinds of arguments when a new OS comes out. They mistake cause and effect. They think that because something worked previously, it must be the new thing that's faulty. That may be the case, but more often then not the problem is something that was always wrong, but just happened to work in the old environment by luck.
By way of example, when XP came out, people complained that XP was broken, because software they used to use worked fine in Windows 9x. In reality, those programs had bugs that simply did not manifest themselves in 9x (perhaps they assumed a piece of memory would always contain a specific value, even though that was not documented or they assumed that they did not have to initialize a data structure before they sent it to an API, even though the documentation said they had to.. after all, it seemed to work if they didn't initialize it).
The point here is that computers are fickle, and sometimes broken things, for some strange reason, work even though they are broken. When something changes in the environment, the conditions that allowed the broken thing to work are no longer there, and it reverts back to broken behavior.
As for OCing, I do overclock my GPU and have no issues with it under Windows 8. I've been using 8 since developer preview and I honestly have never gotten a single BSOD. To be even more honest, the last time I ever got a BSOD on Windows was during XP.