Bsod; please help find problem

Please help with my BSOD crashes!

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 50
BCP1: FFFFF6FC58056A58
BCP2: 0000000000000000
BCP3: FFFFF80002CD20B8
BCP4: 0000000000000002
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\121210-21075-01.dmp
C:\Users\Adam\AppData\Local\Temp\WER-37627-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

BSOD REPORTS:
Windows_NT6_BSOD_jcgriff2 AND PERFRMON.zip - Windows Live

magicadam123 said:

Please help with my BSOD crashes!

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 50
BCP1: FFFFF6FC58056A58
BCP2: 0000000000000000
BCP3: FFFFF80002CD20B8
BCP4: 0000000000000002
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\121210-21075-01.dmp
C:\Users\Adam\AppData\Local\Temp\WER-37627-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

BSOD REPORTS:
Windows_NT6_BSOD_jcgriff2 AND PERFRMON.zip - Windows Live

There are a few problems

1-memory corruption run memtest to check yours.

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.


Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\121210-21075-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c50000 PsLoadedModuleList = 0xfffff800`02e8de50
Debug session time: Sun Dec 12 22:35:32.611 2010 (GMT-5)
System Uptime: 0 days 6:26:00.425
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff6fc58056a58, 0, fffff80002cd20b8, 2}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiLockProtoPoolPage+38 )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff6fc58056a58, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002cd20b8, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ef80e0
 fffff6fc58056a58 

FAULTING_IP: 
nt!MiLockProtoPoolPage+38
fffff800`02cd20b8 4a8b3c36        mov     rdi,qword ptr [rsi+r14]

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880031fc930 -- (.trap 0xfffff880031fc930)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000007ffffffff8 rbx=0000000000000000 rcx=fffff8b00ad4bb20
rdx=fffff880031fcbc8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002cd20b8 rsp=fffff880031fcac0 rbp=fa80042fd3700420
 r8=0000000000000000  r9=fffff88002f63180 r10=0000000000000000
r11=fffff880031fcb20 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!MiLockProtoPoolPage+0x38:
fffff800`02cd20b8 4a8b3c36        mov     rdi,qword ptr [rsi+r14] ds:0001:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002d3f8f2 to fffff80002cc0740

STACK_TEXT:  
fffff880`031fc7c8 fffff800`02d3f8f2 : 00000000`00000050 fffff6fc`58056a58 00000000`00000000 fffff880`031fc930 : nt!KeBugCheckEx
fffff880`031fc7d0 fffff800`02cbe82e : 00000000`00000000 fffffa80`042fd3a8 fffffa80`051bc200 fffffa80`04c1f180 : nt! ?? ::FNODOBFM::`string'+0x40ec0
fffff880`031fc930 fffff800`02cd20b8 : fffffa80`051f0810 fffff800`02fd6837 fffffa80`04c1f030 fffffa80`04627830 : nt!KiPageFault+0x16e
fffff880`031fcac0 fffff800`02caa777 : fffffa80`042fd370 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiLockProtoPoolPage+0x38
fffff880`031fcb10 fffff800`02fb160f : fffffa80`042fd210 00000000`00000011 00000000`000840a1 fffffa80`000840a1 : nt!MiDeleteSegmentPages+0xad
fffff880`031fcbc0 fffff800`02de808b : fffffa80`042fd218 00000000`00000001 00000000`00000000 00000000`00000631 : nt!MiSegmentDelete+0x7b
fffff880`031fcc00 fffff800`02de86fd : 00000000`00000000 00000000`00000080 fffffa80`0366d890 00000000`00000012 : nt!MiProcessDereferenceList+0x23b
fffff880`031fccc0 fffff800`02f64c06 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDereferenceSegmentThread+0x10d
fffff880`031fcd40 fffff800`02c9ec26 : fffff880`02f63180 fffffa80`036f0b60 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031fcd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiLockProtoPoolPage+38
fffff800`02cd20b8 4a8b3c36        mov     rdi,qword ptr [rsi+r14]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiLockProtoPoolPage+38

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x50_nt!MiLockProtoPoolPage+38

BUCKET_ID:  X64_0x50_nt!MiLockProtoPoolPage+38

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

2-Old drivers from back to 2005 need updating.

Code:

MarvinBus64.sys    9/23/2005 16:17:03    fffff880`05054000    0x433470cf    fffff880`05098000            0x00044000                    
speedfan.sys    9/24/2006 08:26:48    fffff880`01493000    0x45168798    fffff880`0149a000            0x00007000                    
pcouffin.sys    12/5/2006 09:39:30    fffff880`03e85000    0x457584a2    fffff880`03e99380            0x00014380                    
Rt64win7.sys    2/26/2009 04:04:13    fffff880`03f0d000    0x49a65b0d    fffff880`03f3f000            0x00032000

3-luafv.sys-part of the OS
Run a system file check

SFC /SCANNOW Command - System File Checker

Ken J

1. Memtest86
Okay, I ran Memtest86 and on the second pass it found an error.

0011f4d3b4 in Chan 1 - 4596.9 MB

Good: 66dde7cc

Bad:66dde7dc

2. Drivers
I was only able to find a couple of the drivers. I will keep searching though.

3. System File check
I ran the test and it found no problems

So what do I do now? Open up my tower and start removing RAM? Is there a systematical way of doing it that will yield the best results? Thanks.

Tews said:

No... if memtest found errors, you need to replace the module.. you will need to test each module in order to isolate the bad stick. When you find one that passes, test each slot to eliminate a problem with the motherboard..

Okay, So remove all but once stick of my ram, then Memtest it. If it passes then move it to another slot? I have two 2GB of DDR3. Will it work with just one?