Blue Screen help needed with debug

[loum]

I am getting the BSOD about to or three times a day. I have downloaded WinDBG but am having trouble analyzing it. Could someone please help. It looks like it is a vista driver causing this but i am not sure which device. I have unistalled some drivers but no luck. PLEASE HELP!!! I like Win 7 but can't live with BSOD.

Lou

 

[zigzag3143]

I am getting the BSOD about to or three times a day. I have downloaded WinDBG but am having trouble analizing it. Could someone please help. It looks like it is a vista driver causing this but i am not sure which device. I have unistalled some drivers but no luck. PLEASE HELP!!! I like Win 7 but can't live with BSOD.

Lou

Hi and welcome three of the dmps were similar. Pretty obvious memory mangement. I would
download memtestx86 and run it overnight

run a system file check to berify and re[air your system file
type cmd in search>right click and run as admin>sfc /scannow

If you are overclocking stop
if you are rjnning a raid update the driver

Ken J+

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


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

Symbol search path is: SRV*d:\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
[B]Built by: 7600.16385.amd64fre.win7_rtm.090713-1255[/B]
Machine Name:
Kernel base = 0xfffff800`02e01000 PsLoadedModuleList = 0xfffff800`0303ee50
Debug session time: Fri Dec 18 10:14:02.760 2009 (GMT-5)
System Uptime: 0 days 0:19:55.430
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41284, 4c7001, 0, fffff70001080000}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ac3 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: 00000000004c7001
Arg3: 0000000000000000
Arg4: fffff70001080000

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


BUGCHECK_STR:  0x1a_41284

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

[B]PROCESS_NAME:  msnmsgr.exe[/B]

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ec9a63 to fffff80002e72f00

STACK_TEXT:  
fffff880`084f5ed8 fffff800`02ec9a63 : 00000000`0000001a 00000000`00041284 00000000`004c7001 00000000`00000000 : nt!KeBugCheckEx
fffff880`084f5ee0 fffff800`02ea5b49 : fffffa80`06cadec8 ffffffff`ffffffff fffffa80`06c1bb60 ffffffff`ffffffff : nt! ?? ::FNODOBFM::`string'+0x4ac3
fffff880`084f5f20 fffff800`02eb966b : df600000`3d7cc847 fffff680`00002638 ffffffff`ffffffff 000fffff`ffffffff : nt!MiTerminateWsle+0x29
fffff880`084f5f60 fffff800`02eb495e : fffff8a0`02c4a8d0 fffff800`00000000 fffffa80`06cadb30 fffffa80`06cadec8 : nt!MiDecommitPages+0x20b
fffff880`084f67f0 fffff800`02e72153 : ffffffff`ffffffff 00000000`0010a0a0 00000000`0010a098 fffffa80`00000001 : nt!NtFreeVirtualMemory+0x2de
fffff880`084f68e0 00000000`7701009a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0010a068 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7701009a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4ac3
fffff800`02ec9a63 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4ac3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3

BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3

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

 

[loum]

Thanks Ken J+. I will do memtest tonight. I have tried to do a system scan but it gets to 6% and gives me a message "Windows Resource Protection could not perform the requested operation." I did start the cmd prompt as administrator. Not sure why it will not scan?

 

[loum]

I have done the Memtest over night and there were no errors found. Does this mean the memory is fine? I am not doing any overclocking. I am letting the MOBO automatically detect most settings? Any other advice?