ntkrnlmp.exe related BSOD

funlovin · 17 Dec 2010

Hello,

thanks for this great platform!
I had several problems with bsod.
The last problem was related with the firewire driver, but now I have no idea.
Almost no idea...maybe it's the psu?

The Installation of the retail windows 7 x64 is 3 month old, same as the hardware. Except the psu, which is 3 years old.

It's a MSI Mainboard H55M-ED33 with an Intel Core i5 and 6GB Ram.
IBM SSD, 2TB Western Digital Caviar Black and 2TB Western Digital Green.
Firewire Card

Thanks a lot!

richc46 · 17 Dec 2010

STOP 0x0000001A: MEMORY_MANAGEMENT Usual causes: Device driver, memory, kernel

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64

Code:

Copyright (c) Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp9_Windows_NT6_BSOD_jcgriff2[1].zip\121710-66316-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
 
Symbol search path is: SRV*c:\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
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c03000 PsLoadedModuleList = 0xfffff800`02e40e50
Debug session time: Thu Dec 16 19:41:21.962 2010 (GMT-5)
System Uptime: 1 days 13:27:34.554
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
......................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 1A, {41790, fffffa80045679e0, ffff, 0}
 
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 )
 
Followup: MachineOwner
---------
 
0: 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: fffffa80045679e0
Arg3: 000000000000ffff
Arg4: 0000000000000000
 
Debugging Details:
------------------
 
 
BUGCHECK_STR:  0x1a_41790
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
 
PROCESS_NAME:  winvnc.exe
 
CURRENT_IRQL:  0
 
LAST_CONTROL_TRANSFER:  from fffff80002ce6f9e to fffff80002c73740
 
STACK_TEXT:  
fffff880`06d24968 fffff800`02ce6f9e : 00000000`0000001a 00000000`00041790 fffffa80`045679e0 00000000`0000ffff : nt!KeBugCheckEx
fffff880`06d24970 fffff800`02cb50da : 00000000`00000000 00000000`03920fff fffffa80`00000000 fffffa80`09294600 : nt! ?? ::FNODOBFM::`string'+0x33906
fffff880`06d24b30 fffff800`02c72993 : ffffffff`ffffffff 00000000`00365da8 00000000`00365db8 00000000`00008000 : nt!NtFreeVirtualMemory+0x5ca
fffff880`06d24c20 00000000`77c5ff3a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0108f228 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c5ff3a
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+33906
fffff800`02ce6f9e cc              int     3
 
SYMBOL_STACK_INDEX:  1
 
SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+33906
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: nt
 
IMAGE_NAME:  ntkrnlmp.exe
 
DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9
 
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33906
 
BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33906
 
Followup: MachineOwner

Its probably memory or driver. It not ntkrnimp. That is just a default driver when the problem cant be found.
We will start with a memory test.
Download memtest86 and test RAM
www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
Run for 8 passes
If passes try a good stick in each slot for 3 passes
If fails do the same for 8 passes.

If you pass, post back for the driver verifier.

funlovin · 19 Dec 2010

You are right, it is a memory problem.
I have several errors during memtest.
Now i will test every module in every slot, to be sure what the problem is.

Next time I will test directly the memory!

Thank you very much.

richc46 · 19 Dec 2010

With a memory problem. Take a known good stick and test it in each slot for at least 6 passes. Good luck