Back in the late Triassic Period when I was current on hardware and OS, a blue screen was aka a General Protection Fault.
No idea how true that still is.
So what's a GP fault?
Well, you got your storage...hard drives and the like, slow but doesn't forget when you shut down.
And then you got your RAM, fast, but it forgets when you shut down.
So your CPU works mostly out of RAM, but when the RAM is full, a whole "page" of data in RAM, the most ancient usually, meaning the opposite of what your CPU is working on right now, the oldest stuff in RAM, gets written to a temporary file in storage, so new data that is needed right now, can be loaded into the freed up RAM, and the old stuff is available, if needed, in a handy spot where the CPU can call for it's return en block.
This is called paging.
Unix has a couple advantages over it's mostly stolen younger sibling, Windows. One, it pages smooth and well, very few errors. Two, it maintains a certain distance from current activity, imagine a supervisor in a glass window tower overlooking a factory floor. If an engine block drops unexpectedly on a workers hand, Unix can dispassionately raise the block by remote control and call 911 fast and smooth, instead of flipping out over all the gore and screaming.
Windows used to flip out and panic the kernal when there was the slightest hint of trouble. It got a LOT better with Win2K, and recovers from errors a thousand times better than pre W2K code. What kinda errors?
Well, all of them, but significant to this tread, General Protection Faults. A GP fault is when the CPU and OS code try to page swap older RAM data to an address that the...Table of Contents...say is already loaded with data that shouldn't be over written. The new and currently necessary data has no place to be loaded, cuz the ancient data hasn't been page swapped to the hard drive yet, and a whole bunch of processor threads, who are expecting the new data yesterday, find themselves idle and start screaming at the supervisor (CPU), who, unlike in the mature and stable Unix factory, is right there on the assembly line floor, and he panics...his eyes glaze over, his jaw drops, and his lips move, trying to solve 857453242648465342 problems at once, but in reality solving nothing, what comes out of his mouth is gibberish, the screen turns to hash, and then, the reptilian core of deep level programming takes over and displays the "Technical Difficulties, Please Stand By" logo, which you know as the Blue Screen of Death.
Of course, this is all greatly simplified, and technically just plain wrong, in a thousand different ways, but it gets the point across.
So, what's your move?
One...make a note of what you've been doing that day...say 30 to 60 minutes before the BSOD. Not every mouse click...but in general...like...mixing 85846353254356 tracks with another 588463242 effects while running 68458735354 softsynths....or watching videos on Youtube, thru your HDMI connected second monitor. Over the course of several BSODs you will probably notice certain trends.
Two, if you are lucky enough to be able to read the Blue crash dump screen...while it's running a core dump, (writing the contents of every memory register to a core dump file, so a code weenie can detective his way into the core of the problem by reading the crash file, (files) get a pen and paper ready cuz at the end of the core dump, you are going to get a HANDY CLUE.
Somewhere near the end of all the computerese gibberish will be something that looks like a filename...perhaps "atikmpag.sys" for example...can anyone tell I'm working thru some BSOD issues of my own?
Use that file name to search the interwebs....oh I dunno...maybe "BSOD, Windows 7, atikmpag.sys" in yer fav search engine. Figure on half the responses to be way too complicated for you to understand. Figure on half the rest to be written in Burmese Sanskrit slang, you know, those bells and smileys that look like a foreign language. Don't waste a bunch of time on the junk, scan the search results for Little Red Riding Hood...answers that look JUUUUUSSSSSTTT RIGHT.
Make a note or two on what you find there. You MAY actually accumulate enough information to fix your own problem, or you may just get a better idea what's up to where you can contact support at say...your graphic card vendor....ATI km PAG(E) dot SYS(driver), get it?
Good luck.
PCs and achievement with same are not an objective, they are a process.
Good luck.