I re-downloaded the latest video drivers from AMD the other day, and if I remember correctly it said they were already up to date then anyway.

I'm not great at this, but I ran it through the Microsoft Analyser and got the following info:

BUGCHECK_STR:  0x1a_3452

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  FlashPlayerPlu

The "FlashPlayerPlu" bit MAY be a red herring, but when I've looked at things in the past that normally has the name of the driving which is causing the Blue Screen.

I found another tool: http://www.resplendence.com/whocrashed

Which says:

On Wed 20/11/2013 22:35:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112013-20701-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x1A (0x3452, 0xD601000, 0xFFFFF700010BF8A0, 0xE830000202B4F800)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.  

So yeah, unless someone better than me can dig some info up you may have to collate a couple of these before it says anything useful :(

Flash and browser need updating?

See if the NSA has been collecting your crash dumps.

So mebbe the latest ones have a bug? 

Intensive processing = heat, especially if the house is being kept warm atm.  Try cleaning your fans & cooling fins. Costs nothing & at worst eliminates overheating as the cause.

certainly also a possible. Web video seems to bum processing hard so that plus games will do it.

The pool header is bad.

A couple of sources seem to suggest bad ram for that error.

Would a few more of the .dmp and .xml crash info files be useful? The folders had a load in, I just zipped up the most recent of each.

FF is up to date. Pretty sure I updated Flash recently too but I've redownloaded and reinstalled it just in case.

The room is generally very very cold, as you might be able to guess by how often I like to open your windows when I'm there. :P

If it is overheating it would have to be from some malfunctioning component rather than external temperature, but I'll still give it a dust.

I do hope not, my RAM is only six months old. :(

Good test is pull the side off. Could also be psu or gpu are failing, or power dips/spikes.

In general FF builds from about ~6-mos ago seem crashy on both xp, and multiple linux distros for me (though not causing BSDs or anything like that). Seems to correlate to javascripts. I switched to Chrome because of it.

Try running memtest? Although when I had dodgy ram and had lots of BSODs the ram passed the tests.

You speak sooth, old bean. Kokoshky, take note.

Hoo hee?

Ozzgur (as in Oscar Kokoshka, natch): parental right to bestow embarrassing pet names.

We saw some awesome OK pics at the royal academy ~20 years ago.