windows 7 blue screen, possibly related to ntoskrnl

Hello all, I am not too great with stuff like this so bear with me. I am running windows 7 64 bit professional version and have been getting a few blue screens seemingly randomly the past few days. I used blue screen view to look and they all seem to involve ntoskrnl.exe and one with that and ntfs.sys. I also ran sfc /scannow that said i had some corrupted files it couldnt fix. I have just been trying to do these things based on what others have said in forums and such, but i do not know how to decipher them and create a solution. I attached the mini dump files, if anyone can help me that would be fantastic.

its crashed twice more in the past like 15 minutes...

added new dump files

i have run bios memory and hard drive tests that passed. however, the windows memory diagnostic reports hardware problems when i run the test with 2 ram sticks inserted. Each ram slot in the first slot by itself passes fine. only when the second slot is also in use does it report hardware issues and to contact the manufacturer. i contacted hp, and they had me run the bios test and since it passed they dont see a need to do anything about it. i sent this into repair about a month ago and all they did was re-image the drive and send it back, but its still having the same problems.

i could really use some help here

shaneo8709 said:

its crashed twice more in the past like 15 minutes...

added new dump files

i have run bios memory and hard drive tests that passed. however, the windows memory diagnostic reports hardware problems when i run the test with 2 ram sticks inserted. Each ram slot in the first slot by itself passes fine. only when the second slot is also in use does it report hardware issues and to contact the manufacturer. i contacted hp, and they had me run the bios test and since it passed they dont see a need to do anything about it. i sent this into repair about a month ago and all they did was re-image the drive and send it back, but its still having the same problems.

i could really use some help here

Well these 5 still point to multiple problems including memory, system files, etc. To deal with this you should start with memory diags. You cant use the built in as it does not stress the memory enough. You should use memtestx86, download and burn to cd, run it for at least 7 passes.

Let us know the results

Ken

Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jun  8 08:48:59.127 2010 (GMT-4)
System Uptime: 1 days 0:25:48.000
BugCheck C4, {91, 2, fffffa8003d1b040, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4904 )
BUGCHECK_STR:  0xc4_91
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jun  7 08:16:47.388 2010 (GMT-4)
System Uptime: 0 days 0:07:34.370
BugCheck A, {fffffa8012582010, 2, 1, fffff80002b8f9f7}
Probably caused by : memory_corruption ( nt!MiReleaseConfirmedPageFileSpace+87 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  sppsvc.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jun  7 06:53:06.147 2010 (GMT-4)
System Uptime: 0 days 1:16:06.129
BugCheck 3B, {c0000005, fffff80002a7c805, fffff880039903f0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  explorer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jun  6 07:52:01.528 2010 (GMT-4)
System Uptime: 0 days 0:40:02.112
BugCheck 3B, {c0000005, fffff80002bbc90d, fffff88007b5b9f0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+53d )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jun  6 00:58:47.233 2010 (GMT-4)
System Uptime: 0 days 0:17:39.215
BugCheck 24, {1904fb, fffff88002fc43d8, fffff88002fc3c40, fffff80002f1503a}
Probably caused by : fileinfo.sys ( fileinfo!FIStreamLog+89 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x24

well i ran it for one full pass and part of another, almost 8000 errors showed in the list i think? i really dont know what any of this stuff means, here is a screenshot of the memtest

could it be software related? or more likely a hardware issue?

With that memtest result it is definitely hardware.