BSOD windows 7 64-bit

[medoomi]

I've recently completed a system build & had two seemingly random BSOD's. I've checked the RAM with Memtest86+, but that seemed to come out fine.

If anyone could give me a reading of the two minidumps, I'd be immensely grateful.

Thanks

 

[zigzag3143]

I've recently completed a system build & had two seemingly random BSOD's. I've checked the RAM with Memtest86+, but that seemed to come out fine.

If anyone could give me a reading of the two minidumps, I'd be immensely grateful.

Thanks

Hi and welcome. both dumps were similar, both had a core OS system failing because of memory management. You mentioned running memtestx86 how long did you run it for?

Second problem, many, many old drivers. obviously need to update the ones listed below

secdrv.SYS        fffff880`08bdf000    fffff880`08bea000    0x0000b000    0x4508052e    9/13/2006 8:18:38 AM                        
DRVECDB.SYS        fffff880`010ce000    fffff880`010ea920    0x0001c920    0x453f8122    10/25/2006 10:22:10 AM                        
DLAIFS_E.SYS        fffff880`0104c000    fffff880`0106d080    0x00021080    0x4548d19c    11/1/2006 11:55:56 AM                        
DLAPoolE.SYS        fffff880`04bf9000    fffff880`04bfbb80    0x00002b80    0x4548d1b5    11/1/2006 11:56:21 AM                        
DLAUDF_E.SYS        fffff880`03c7d000    fffff880`03c9e680    0x00021680    0x4548d1c8    11/1/2006 11:56:40 AM                        
DLAUDFAE.SYS        fffff880`00c6a000    fffff880`00c89c80    0x0001fc80    0x4548d1d8    11/1/2006 11:56:56 AM                        
DLABOIOE.SYS        fffff880`02df0000    fffff880`02df8900    0x00008900    0x4548d1da    11/1/2006 11:56:58 AM                        
DLABMFSE.SYS        fffff880`04077000    fffff880`04080180    0x00009180    0x4548d1df    11/1/2006 11:57:03 AM                        
DLAOPIOE.SYS        fffff880`04abb000    fffff880`04ac1c00    0x00006c00    0x4548d201    11/1/2006 11:57:37 AM                        
DLADResE.SYS        fffff880`04aba000    fffff880`04abad80    0x00000d80    0x4548d21e    11/1/2006 11:58:06 AM                        
PdiPorts.sys        fffff880`0fe9f000    fffff880`0fea7000    0x00008000    0x455d02d4    11/16/2006 7:31:16 PM                        
DLARTL_E.SYS        fffff880`01954000    fffff880`0195be00    0x00007e00    0x45cbf2d4    2/8/2007 11:04:36 PM                        
DLACDBHE.SYS        fffff880`01941000    fffff880`01943300    0x00002300    0x45cbf2f6    2/8/2007 11:05:10 PM                        
DRVEDDM.SYS        fffff880`04aac000    fffff880`04ab9d80    0x0000dd80    0x45ccdabb    2/9/2007 3:34:03 PM                        
PxHlpa64.sys        fffff880`010eb000    fffff880`010f6700    0x0000b700    0x4679a9bc    6/20/2007 5:27:08 PM                        
adfs.SYS        fffff880`08b21000    fffff880`08b39000    0x00018000    0x48640195    6/26/2008 3:52:37 PM

I would do the following.
Since they still say the probable cause of the crashes is memory management you are going to have to run memtest long enough (OVERNIGHT) to find out why.

You should run a system file check to verify and repair your system files
type cmd in search>right click and run as admin>sfc /scannow

If you are overclocking STOP
If you are running a raid update its driver too
you might also want to dl cpu-z, and gpu-z both free utilites to keep an eye on your temps.

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\121709-20326-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a14000 PsLoadedModuleList = 0xfffff800`02c51e50
Debug session time: Thu Dec 17 01:18:38.892 2009 (GMT-5)
System Uptime: 0 days 16:56:31.001
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa80057f0d50, ffff, 0}

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

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa80057f0d50
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  SearchFilterHo

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002af826e to fffff80002a85f00

STACK_TEXT:  
fffff880`0ad0f798 fffff800`02af826e : 00000000`0000001a 00000000`00041790 fffffa80`057f0d50 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0ad0f7a0 fffff800`02ab95d9 : fffffa80`00000000 000007fe`ff228fff 00000000`00000000 fffff800`02c13888 : nt! ?? ::FNODOBFM::`string'+0x339d6
fffff880`0ad0f960 fffff800`02a59080 : ffffffff`ffffffff 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`0ad0fa80 fffff800`02d687af : fffff8a0`02db5970 00000000`00000001 00000000`00000000 fffffa80`08fb4b60 : nt!MmCleanProcessAddressSpace+0x228
fffff880`0ad0fad0 fffff800`02d41cb8 : 00000000`00000000 00000000`00000001 000007ff`fffde000 00000000`00000000 : nt!PspExitThread+0x47f
fffff880`0ad0fba0 fffff800`02a85153 : fffffa80`0c946370 00000000`00000000 fffffa80`08fb4b60 fffffa80`0cdd96b0 : nt!NtTerminateProcess+0x138
fffff880`0ad0fc20 00000000`7749017a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0026f6e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7749017a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+339d6
fffff800`02af826e cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+339d6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+339d6

BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+339d6

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

 

[medoomi]

Thanks so much for your reply

Memtest86+ ran for 8 hours, so I'll try it again. Unfortunately, I'm with family for the next two weeks, so will have to wait till about Jan 4 before I can do it again.

About the old drivers, that was a surprise--I knew the SATA driver was out of date ('06), but I'll check into the other ones too when I get back. What's the best method to keep them up to date (short of doing through all the devices & checking drivers)?

 

[zigzag3143]

Thanks so much for your reply

Memtest86+ ran for 8 hours, so I'll try it again. Unfortunately, I'm with family for the next two weeks, so will have to wait till about Jan 4 before I can do it again.

About the old drivers, that was a surprise--I knew the SATA driver was out of date ('06), but I'll check into the other ones too when I get back. What's the best method to keep them up to date (short of doing through all the devices & checking drivers)?

just took a look at the list of drivers. most of them seem related dlaud***.sys, etc. that may just be one device that is old an needing upgrade. google the names and it will point you to both whose drivers they are and where to get an updated one.

Ken J+

 

[medoomi]

Cool, thanks!