BSODs - various STOP codes

Funwith4kids said:

Been researching forum with the mounds of helpful info. However, we keep getting BSODs with various stop codes. Need help with figuring out root cause.

At one point it was so bad, the PC would not boot and we refreshed from factory image which helped for awhile. A couple months later getting more and more random BSODs. Ran windows repair, chkdsk, memtest with 7 passes...nothing found.

Attached is DT GRAB ALL file. Can someone with more brains review and provide feedback? TIA.

REFERENCE_BY_POINTER (18)
BAD POOL HEADER (19) several times
PAGE FAULT IN NON PAGED AREA (50) several times

see if this link will help ya out any:

Bad pool header BSOD

Code:

Debugging Details:
------------------


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x18

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from fffff80002c78e14 to fffff80002cd2bc0

STACK_TEXT:  
fffff880`02c063e8 fffff800`02c78e14 : 00000000`00000018 00000000`00000000 fffffa80`09080290 00000000`00000002 : nt!KeBugCheckEx
fffff880`02c063f0 fffff800`02fc8fa9 : fffff880`02c06c60 fffff880`02c06798 00000000`00000017 00000000`00000006 : nt! ?? ::FNODOBFM::`string'+0x48de1
fffff880`02c06450 fffff800`02fc92de : 00000000`00000001 00000000`00000000 00000000`00000001 00000000`00000001 : nt!ObpWaitForMultipleObjects+0x2d3
fffff880`02c06920 fffff800`02cd1e53 : fffffa80`09080400 00000000`00ddf898 fffff880`02c06b88 fffff880`02c06b00 : nt!NtWaitForMultipleObjects+0xe5
fffff880`02c06b70 00000000`7747186a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00ddf878 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7747186a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+48de1
fffff800`02c78e14 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+48de1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035

IMAGE_VERSION:  6.1.7601.18247

FAILURE_BUCKET_ID:  X64_0x18_OVER_DEREFERENCE_nt!_??_::FNODOBFM::_string_+48de1

BUCKET_ID:  X64_0x18_OVER_DEREFERENCE_nt!_??_::FNODOBFM::_string_+48de1

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x18_over_dereference_nt!_??_::fnodobfm::_string_+48de1

FAILURE_ID_HASH:  {5ba4307c-2f62-b1e1-5172-be3b6254fbd1}

Followup: MachineOwner
---------

I've checked the latest dmp file. BugCheck 0x18's are quite rare.

I know you said you ran MemTest, but please start with a thorough test of RAM using MemTest86+. Run a minimum of 8 passes, or until errors occur:
RAM - Test with Memtest86+

Well...

4 RAM sticks....ran 4 memtest+ tests for at least 10 passes each time with each one individually in their own slot and NO ERRORS.

Any advice on why memory errors, but can not narrow down to which RAM stick/slot?

next steps?

That is odd. Are the RAM sticks all exactly the same make/type and speed? Not overclocked in any way?

It might be worth running Prime95 to see if it provides more clues:
Hardware - Stress Test With Prime95