Random bsods caused by ntkrnlmp

#1
Hello,
I was experiencing random bsods while doing practically anything (surfing, music)
At first it appeared to be memory problem, but I've replaced sticks and problem didn't go away.
Here are minidumps.. View attachment Minidump.zip

Thank you in advance for any time spent assisting in troubleshooting.
 


#2
Hi and welcome.

Uninstall VMWare as it is causing your bsods.

And you really should update your video card driver:

atikmdag atikmdag.sys Thu Jun 25 19:18:11 2009

Drivers & Support | GAME.AMD.COM

Also update your Diamondback3G driver:

DB3G DB3G.sys Mon Nov 07 01:33:11 2005

http://www.razersupport.com/index.php?_m=downloads&_a=view
 


Last edited:
#3
Thanks a lot, that was really impressive.
How did you find out it was vmware? I didnt see it mentioned anywhere in 'analyze -v' output in windbg.
 


#4
Thanks a lot, that was really impressive.
How did you find out it was vmware? I didnt see it mentioned anywhere in 'analyze -v' output in windbg.
Your latest crash dump (110809-22713-01.dmp) shows that.

Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\a\Minidump\D M P\110809-22713-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a17000 PsLoadedModuleList = 0xfffff800`02c54e50
Debug session time: Sun Nov  8 08:10:09.567 2009 (UTC - 5:00)
System Uptime: 0 days 0:02:18.253
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D9, {1, fffffa8007316a70, fffffa8008b90490, 40}

Unable to load image \??\C:\Windows\system32\drivers\vmx86.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for vmx86.sys
*** ERROR: Module load completed but symbols could not be loaded for vmx86.sys
Probably caused by : vmx86.sys ( vmx86+5b76 )

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

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

LOCKED_PAGES_TRACKER_CORRUPTION (d9)
Arguments:
Arg1: 0000000000000001, The MDL is being inserted twice on the same process list.
Arg2: fffffa8007316a70, Address of internal lock tracking structure.
Arg3: fffffa8008b90490, Address of memory descriptor list.
Arg4: 0000000000000040, Number of pages locked for the current process.

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xD9

PROCESS_NAME:  vmware-vmx.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002b5b4ed to fffff80002a88f00

STACK_TEXT:  
fffff880`06810608 fffff800`02b5b4ed : 00000000`000000d9 00000000`00000001 fffffa80`07316a70 fffffa80`08b90490 : nt!KeBugCheckEx
fffff880`06810610 fffff800`02b02713 : fffffa80`07316a70 ffffffff`ffffffff fffff8a0`047ba100 fffffa80`081b6440 : nt!MiAddMdlTracker+0xed
fffff880`06810680 fffff880`04491b76 : fffffa80`08b90490 fffff8a0`047ba101 00000000`00000002 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x3bf1c
fffff880`06810790 fffffa80`08b90490 : fffff8a0`047ba101 00000000`00000002 00000000`00000002 fffffa80`00001000 : vmx86+0x5b76
fffff880`06810798 fffff8a0`047ba101 : 00000000`00000002 00000000`00000002 fffffa80`00001000 00000000`00000004 : 0xfffffa80`08b90490
fffff880`068107a0 00000000`00000002 : 00000000`00000002 fffffa80`00001000 00000000`00000004 00000000`02c30000 : 0xfffff8a0`047ba101
fffff880`068107a8 00000000`00000002 : fffffa80`00001000 00000000`00000004 00000000`02c30000 fffff8a0`04799000 : 0x2
fffff880`068107b0 fffffa80`00001000 : 00000000`00000004 00000000`02c30000 fffff8a0`04799000 fffffa80`08b90490 : 0x2
fffff880`068107b8 00000000`00000004 : 00000000`02c30000 fffff8a0`04799000 fffffa80`08b90490 fffff880`04490f10 : 0xfffffa80`00001000
fffff880`068107c0 00000000`02c30000 : fffff8a0`04799000 fffffa80`08b90490 fffff880`04490f10 00000000`00000000 : 0x4
fffff880`068107c8 fffff8a0`04799000 : fffffa80`08b90490 fffff880`04490f10 00000000`00000000 00000000`00000040 : 0x2c30000
fffff880`068107d0 fffffa80`08b90490 : fffff880`04490f10 00000000`00000000 00000000`00000040 fffff8a0`047ba000 : 0xfffff8a0`04799000
fffff880`068107d8 fffff880`04490f10 : 00000000`00000000 00000000`00000040 fffff8a0`047ba000 00000000`00000001 : 0xfffffa80`08b90490
fffff880`068107e0 00000000`00000000 : 00000000`00000040 fffff8a0`047ba000 00000000`00000001 00000000`00000001 : vmx86+0x4f10


STACK_COMMAND:  kb

FOLLOWUP_IP: 
vmx86+5b76
fffff880`04491b76 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  vmx86+5b76

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: vmx86

IMAGE_NAME:  vmx86.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a85fa8c

FAILURE_BUCKET_ID:  X64_0xD9_VRF_vmx86+5b76

BUCKET_ID:  X64_0xD9_VRF_vmx86+5b76

Followup: MachineOwner
 


Last edited:
#5
Thanks a lot, that was really impressive.
How did you find out it was vmware? I didnt see it mentioned anywhere in 'analyze -v' output in windbg.
Yes, as Cybercore shows. But even if it had no mention at all, I would have known. VMWare is flaky at best. I don't use it at all, but I suppose it's all in how it is configured by the end user that will bring or destroy the stability.
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.