Diagnosing a BSoD

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?
From: Manthorp23 Nov 2013 10:33
To: CHYRON (DSMITHHFX) 21 of 44
Ozzgur (as in Oscar Kokoshka, natch): parental right to bestow embarrassing pet names.
EDITED: 23 Nov 2013 10:33 by MANTHORP
From: CHYRON (DSMITHHFX)24 Nov 2013 13:17
To: Manthorp 22 of 44
We saw some awesome OK pics at the royal academy ~20 years ago.
From: koswix24 Nov 2013 21:19
To: CHYRON (DSMITHHFX) 23 of 44
Make your mind up, we're they awesome or just Ok?
From: Manthorp24 Nov 2013 22:03
To: CHYRON (DSMITHHFX) 24 of 44
Fine painter, fine son.
From: CHYRON (DSMITHHFX)24 Nov 2013 22:23
To: koswix 25 of 44
They we're awesome.
From: Ken (SHIELDSIT)25 Nov 2013 05:23
To: koswix 26 of 44
Should we jump all over you're shit for that?
From: Oscarvarium (OZGUR) 4 Jan 2014 21:46
To: ALL27 of 44
Bloody thing did it again. Running memtest now, but apparently I'm meant to only have one stick in at a time to test them properly? Is there any point in letting it run with both sticks in or should I cancel it and restart?
From: CHYRON (DSMITHHFX) 5 Jan 2014 00:42
To: Oscarvarium (OZGUR) 28 of 44
If the test fails, then you'll know at least one is bad and should test them separately. Otherwise, they are both fine. IIRC correctly, if it is a memory issue it will likely transpire during a quick test anyway, and there's no real benefit to running the long test.
From: Oscarvarium (OZGUR) 5 Jan 2014 01:23
To: CHYRON (DSMITHHFX) 29 of 44
It's still not done after 5+ hours, but it seems to have flagged errors (65535+ apparently) already. Should I therefore assume at least one of the sticks is faulty and quit the test, then restart it with just one stick plugged in and run the (quick?) test?
From: CHYRON (DSMITHHFX) 5 Jan 2014 02:07
To: Oscarvarium (OZGUR) 30 of 44
Yeah, that sounds plausible. I don't really know much about memtest. I've never had memory fail the tests the very few times I've run it, I've had plenty of other problems to deal with, mostly drives and blown caps on the mb but (so far) not bad memory.