Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: ntkrnlmp.exe related BSOD

17 Dec 2010   #1

Windows 7 Ultimate x64
ntkrnlmp.exe related BSOD


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!

My System SpecsSystem Spec
17 Dec 2010   #2

Microsoft Community Contributor Award Recipient

Windows 10, Home Clean Install

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

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
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*
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                                    *
*                                                                             *
  # Any other values for parameter 1 must be individually examined.
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa80045679e0
Arg3: 000000000000ffff
Arg4: 0000000000000000
Debugging Details:
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  winvnc.exe
LAST_CONTROL_TRANSFER:  from fffff80002ce6f9e to fffff80002c73740
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
nt! ?? ::FNODOBFM::`string'+33906
fffff800`02ce6f9e cc              int     3
SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+33906
FOLLOWUP_NAME:  MachineOwner
IMAGE_NAME:  ntkrnlmp.exe
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
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.
My System SpecsSystem Spec
19 Dec 2010   #3

Windows 7 Ultimate x64

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.
My System SpecsSystem Spec

19 Dec 2010   #4

Microsoft Community Contributor Award Recipient

Windows 10, Home Clean Install

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

 ntkrnlmp.exe related BSOD

Thread Tools

Similar help and support threads
Thread Forum
"ntkrnlmp.exe" related BSOD
I bought recently this PC and it had this problem from the beginning. I tested the hardware (except power supply) and everything is working, yet i'm still getting BSOD from time to time. If you have any idea what's happening please tell me! sorry for my english
BSOD Help and Support
BSOD Possibly LoL Related; ntkrnlmp.exe
Hey All, My brother recently talked me into downloading League of Legends, and ever since then my computer has been giving me BSODs like crazy. The first few were only while the LoL download was running, then more came when the installer was going. I decided to give up on it, but he talked me...
BSOD Help and Support
BSOD browser related/vssc.exe related
Been getting fairly regular BSOD's that only seem to happen when using a web browser. Chrome BSOD fairly regularly. Firefox less so (Only once). I've also had a vssc.exe BSOD when the pc was idle. Windows fully up to date. All drivers up to date. No conflicts. I've run a sfc scan with no errors or...
BSOD Help and Support
ntkrnlmp.exe related BSOD
Hi. I've been having trouble with my PC for some time now. Windows 7 x64 crashes with random BSOD messages. Windows Vista x86 did the same thing before I switched. Seven is installed onto a formated separate partition. With two sticks of RAM in dual or single channel the system crashes...
BSOD Help and Support
BSOD Apparent related to IPOD Touch and/or related services
My PC has recently started erratic BSOD crashes after a year of bliss. I installed UBUNTU as second boot option and it seems to work normally. Would rather not just give up on Windows 7 - particularly as this is x64 version and UBUNTU is only x86 version; I also have some windows-only software...
BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 22:14.
Twitter Facebook Google+