ntkrnlmp.exe related BSOD

[funlovin]

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]

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

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64

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

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]

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]

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