BSoD (ntoskrnl.exe)

So, I was playing CSGO and all of a sudden I got a BSOD. This is my first time getting one so I really freaked out. The system just restarted and started working normally. I just got a message

Windows has recovered from an unexpected shutdown.

After doing a bit of research I found out that a driver named ntoskrnl.exe caused the BSoD to appear. As stated earlier, I never had any problems with this. It was completely random.

Here's some more info.

The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000050 (0xfffffa800251443b, 0x0000000000000000, 0xfffff8000307515f, 0x0000000000000002). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 120915-23680-01.

param1 0x00000050 (0xfffffa800251443b, 0x0000000000000000, 0xfffff8000307515f, 0x0000000000000002) 
  param2 C:\Windows\MEMORY.DMP 
  param3 120915-23680-01

What should I do?

(This isn't really an answer, but it won't fit in a comment.)

As far as I can tell, I don't think the memory.dmp file will be helpful. From the minidump, the problem happened in a routine called MiAgeWorkingSet. It had a zero in a register that was supposed to contain the virtual address of some structure in memory, and zero is never a good address. This routine has to do with the "working set list", which keeps track of which pages of RAM are being used by a process, and "aging" the entries.

The thing is, there can't possibly be anything wrong with that routine; it's a standard part of every Windows system and is called far too often; if something was wrong with it Windows systems would be crashing all over the place. The routine was probably operating on the working set list of a process, and that list was probably corrupt. That is, some of the data in the list was invalid.

The trouble is there is not a good way to find out how that happened. Literally any kernel mode driver in the system could have done it. Or, it might have been due to hardware problems, like an actual problem with RAM. A very slightly flaky power supply can cause intermittent memory problems too.

There is no clear indication here of what to do next. You could do the usual hardware stuff: Reseat your RAM, etc. Cleaning dust out of the heat sinks is a good idea (yes, overheating can cause this sort of problem too). On the software side, make sure Windows and all of your drivers, especially video drivers, are up to date.

Oh, and: If you're overclocking anything, STOP.

Sorry I can't be of more help. Maybe magicandre can do better.