Memory_Management BSOD

[jaymac10]

Please help!

Keep getting a memory_managemnt blue screen...

Attached is my DMP File!

Thanks,

Jay

 

[zigzag3143]

Please help!

Keep getting a memory_managemnt blue screen...

Attached is my DMP File!

Thanks,

Jay

hI AND WELCOME
this crash was again caused by memory management.
You also have drivers that are more than 2 years old an should be updated

I would update these

secdrv.SYS        fffff880`0471d000    fffff880`04728000    0x0000b000    0x4508052e    9/13/2006 8:18:38 AM                        
emupia2k.sys        fffff880`04f56000    fffff880`04fa8000    0x00052000    0x461a3aba    4/9/2007 8:08:10 AM                        
ctsfm2k.sys        fffff880`04fa8000    fffff880`04ff2000    0x0004a000    0x461a3abb    4/9/2007 8:08:11 AM                        
ctoss2k.sys        fffff880`04598000    fffff880`045d3000    0x0003b000    0x461a3abe    4/9/2007 8:08:14 AM                        
ha10kx2k.sys        fffff880`06003000    fffff880`061bc000    0x001b9000    0x461a3abf    4/9/2007 8:08:15 AM                        
ctaud2k.sys        fffff880`04425000    fffff880`044f6000    0x000d1000    0x461a3acd    4/9/2007 8:08:29 AM                        
ctprxy2k.sys        fffff880`045d3000    fffff880`045db000    0x00008000    0x461a3ace    4/9/2007 8:08:30 AM                        
COMMONFX.DLL        fffff880`04e5c000    fffff880`04e87000    0x0002b000    0x461a3ad6    4/9/2007 8:08:38 AM                        
CTAUDFX.DLL        fffff880`0644d000    fffff880`064fc000    0x000af000    0x461a3ad7    4/9/2007 8:08:39 AM                        
CTSBLFX.DLL        fffff880`064fc000    fffff880`065a7000    0x000ab000    0x461a3ada    4/9/2007 8:08:42 AM

I wpould also dl memtestx86 and run it for hours (prefer overnight)
run a system file check to verify and repair your system files
type cmd in search>right click and run as admin>sfc /scannow
Hope this helps

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\121609-19687-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a55000 PsLoadedModuleList = 0xfffff800`02c92e50
Debug session time: Thu Dec 17 02:11:13.040 2009 (GMT-5)
System Uptime: 0 days 4:48:14.928
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {31, fffffa8007e25220, fffff8800e083000, fffff8a0072938f6}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+6378 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000031, The subtype of the bugcheck.
Arg2: fffffa8007e25220
Arg3: fffff8800e083000
Arg4: fffff8a0072938f6

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


BUGCHECK_STR:  0x1a_31

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  mcupdate.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002df483d to fffff80002ac6f00

STACK_TEXT:  
fffff880`078ef6f8 fffff800`02df483d : 00000000`0000001a 00000000`00000031 fffffa80`07e25220 fffff880`0e083000 : nt!KeBugCheckEx
fffff880`078ef700 fffff800`02dabc15 : fffff880`0e083000 00000000`00ee0000 00000000`00bc4000 fffffa80`00367770 : nt! ?? ::NNGAKEGL::`string'+0x6378
fffff880`078ef750 fffff800`02d9917c : 00000000`00000000 00000000`00000000 fffff6fc`40054d10 fffff800`00000000 : nt!MiPerformFixups+0x65
fffff880`078ef7a0 fffff800`02aa8eed : 00000000`0001227d 00000000`00000bc4 fffff8a0`07245e68 00000000`00000002 : nt!MiRelocateImagePfn+0x114
fffff880`078ef800 fffff800`02dabb71 : fffffa80`05bf6310 fffff6fc`40054d10 fffff8a0`00000002 00000000`00000000 : nt!MiValidateImagePages+0x2bd
fffff880`078ef8a0 fffff800`02dab280 : ffffffff`ffffffff 00000000`00000001 fffff8a0`07276000 00000000`0000005f : nt!MiSwitchBaseAddress+0x61
fffff880`078ef8d0 fffff800`02dbf0ae : 00000000`00000004 00000000`01000000 00000000`00000000 00000000`00000000 : nt!MiRelocateImageAgain+0x100
fffff880`078ef920 fffff800`02db4893 : fffff880`078efb80 00000000`00000000 00000000`00000000 fffff880`078efb78 : nt!MmCreateSection+0x302
fffff880`078efb30 fffff800`02ac6153 : fffffa80`05ae36f0 00000000`0019dfd8 fffff880`078efbc8 00000000`0019e1a8 : nt!NtCreateSection+0x162
fffff880`078efbb0 00000000`7770035a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0019dfb8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7770035a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::NNGAKEGL::`string'+6378
fffff800`02df483d cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::NNGAKEGL::`string'+6378

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x1a_31_nt!_??_::NNGAKEGL::_string_+6378

BUCKET_ID:  X64_0x1a_31_nt!_??_::NNGAKEGL::_string_+6378

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

 

[jaymac10]

Thank you!

However, what is any easy way to update these drivers automatically? The standard windows update does not seem to catch these...

Thanks,

Jay

 

[chev65]

If you list your system specs we may be able to find you some updated Windows 7 drivers.

 

[TaraSWinTeam]

Hi Jay,

Find more information about checking your drivers here: Update a driver for hardware that isn't working properly. This includes how to find and upload drivers outside of your update.

Cheers,
Tara
Windows Outreach