Diagnosing a BSoD

From: Oscarvarium (OZGUR)20 Nov 2013 23:59
To: ALL1 of 44
I've been getting sudden bluescreens while playing DotA 2 or Minecraft - generally only while simultaneously watching a YouTube video (or even just having one paused and minimised) or a livestream, but not consistently. I believe it has also been bluescreening while not playing any game and just watching a video or playing music, but most often while a game is running.

Anyone know how to tell what's actually wrong with my system? I get the message "BAD_POOL_HEADER" on the bluescreen, along with the code 0x00000019 which the internet tells me is the significant part of what's displayed. This is the info given in the "Windows has recovered from an unexpected shutdown" dialogue box from my most recent crash, and I've attached the "Files that help describe the problem" in a .zip.

Problem signature:
  Problem Event Name:    BlueScreen
  OS Version:    6.1.7601.2.1.0.768.3
  Locale ID:    2057

Additional information about the problem:
  BCCode:    1a
  BCP1:    0000000000003452
  BCP2:    000000000D601000
  BCP3:    FFFFF700010BF8A0
  BCP4:    E830000202B4F800
  OS Version:    6_1_7601
  Service Pack:    1_0
  Product:    768_1


My instinct tells me I need to replace my main hard drive since it's pretty old at this point. All the rest of my components are relatively new though, and should be detailed in my profile which I will check now to make sure it's up to date.
Attachments:
From: milko21 Nov 2013 00:26
To: Oscarvarium (OZGUR) 2 of 44
video drivers I reckon.
From: Oscarvarium (OZGUR)21 Nov 2013 03:54
To: milko 3 of 44
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.
From: Dan (HERMAND)21 Nov 2013 09:56
To: Oscarvarium (OZGUR) 4 of 44
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.  
From: Dan (HERMAND)21 Nov 2013 09:58
To: ALL5 of 44
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 :(


From: ANT_THOMAS21 Nov 2013 10:00
To: Oscarvarium (OZGUR) 6 of 44
Flash and browser need updating?
From: Ken (SHIELDSIT)21 Nov 2013 11:13
To: ALL7 of 44
See if the NSA has been collecting your crash dumps.
From: milko21 Nov 2013 12:19
To: Oscarvarium (OZGUR) 8 of 44
So mebbe the latest ones have a bug? 
From: Manthorp21 Nov 2013 12:28
To: Oscarvarium (OZGUR) 9 of 44
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.
From: milko21 Nov 2013 13:01
To: Manthorp 10 of 44
certainly also a possible. Web video seems to bum processing hard so that plus games will do it.
From: Chris (CHRISSS)21 Nov 2013 14:35
To: Oscarvarium (OZGUR) 11 of 44
The pool header is bad.

A couple of sources seem to suggest bad ram for that error.
From: Oscarvarium (OZGUR)21 Nov 2013 15:31
To: Dan (HERMAND) 12 of 44
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.
From: Oscarvarium (OZGUR)21 Nov 2013 15:35
To: ANT_THOMAS 13 of 44
FF is up to date. Pretty sure I updated Flash recently too but I've redownloaded and reinstalled it just in case.
EDITED: 21 Nov 2013 15:35 by OZGUR
From: Oscarvarium (OZGUR)21 Nov 2013 15:36
To: Manthorp 14 of 44
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.
From: Oscarvarium (OZGUR)21 Nov 2013 15:37
To: Chris (CHRISSS) 15 of 44
I do hope not, my RAM is only six months old. :(
From: CHYRON (DSMITHHFX)21 Nov 2013 16:43
To: Manthorp 16 of 44
Good test is pull the side off. Could also be psu or gpu are failing, or power dips/spikes.
From: CHYRON (DSMITHHFX)21 Nov 2013 16:46
To: Oscarvarium (OZGUR) 17 of 44
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.
From: Chris (CHRISSS)21 Nov 2013 21:03
To: Oscarvarium (OZGUR) 18 of 44
Try running memtest? Although when I had dodgy ram and had lots of BSODs the ram passed the tests.
From: Manthorp21 Nov 2013 22:07
To: CHYRON (DSMITHHFX) 19 of 44
You speak sooth, old bean. Kokoshky, take note.
From: CHYRON (DSMITHHFX)22 Nov 2013 21:10
To: Manthorp 20 of 44
Hoo hee?