Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


BSOD ntkrnlmp.exe windows 2003 64 bit VM

  • Please log in to reply
No replies to this topic

#1 jai72k


  • Members
  • 1 posts
  • Local time:05:04 PM

Posted 16 April 2010 - 05:38 PM

I have a Windows 2003 64 bit VM running SQL 2005. For last few weeks, the server has rebooted unexpectedly few times. Below is the memory dump of the latest reboot. Please help find the cause.

Microsoft ® Windows Debugger Version 6.12.0002.633 X86
Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Mini416.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:
*** WARNING: Unable to verify checksum for ntkrnlmp.exe
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (4 procs) Free x64
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Built by: 3790.srv03_sp2_gdr.080813-1204
Machine Name:
Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d4140
Debug session time: Fri Apr 16 09:19:10.337 2010 (UTC - 7:00)
System Uptime: 13 days 15:38:05.301
*** WARNING: Unable to verify checksum for ntkrnlmp.exe
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* *
* Bugcheck Analysis *
* *

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc000001d, fffffadf39b64c56, 2, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiDispatchException+128 )

Followup: MachineOwner

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

This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffffadf39b64c56, The address that the exception occurred at
Arg3: 0000000000000002, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:

EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

fffffadf`39b64c56 62 ???

EXCEPTION_PARAMETER1: 0000000000000002

EXCEPTION_PARAMETER2: 0000000000000000

ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

BUGCHECK_STR: 0x1E_c000001d




EXCEPTION_RECORD: fffff80000386610 -- (.exr 0xfffff80000386610)
ExceptionAddress: fffffadf39b64c56
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0

TRAP_FRAME: fffff800003866a0 -- (.trap 0xfffff800003866a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000202
rdx=000000000000082f rsi=0000000000000000 rdi=0000000000000000
rip=fffffadf39b64c56 rsp=fffff80000386830 rbp=fffff80000386880
r8=000000000000082f r9=fffffadf3b8087a0 r10=000000000000000f
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
fffffadf`39b64c56 62 ???
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80001080e86 to fffff8000102e890

fffffadf`39b64c56 62 ???

fffff800`00385f18 fffff800`01080e86 : 00000000`0000001e ffffffff`c000001d fffffadf`39b64c56 00000000`00000002 : nt!KeBugCheckEx
fffff800`00385f20 fffff800`0102e6af : fffff800`00386610 00000000`00000000 fffff800`003866a0 00001f80`00050240 : nt!KiDispatchException+0x128
fffff800`00386520 fffff800`0102cc43 : fffff800`003866a0 00000000`00000002 fffffadf`39b63000 00000000`00000000 : nt!KiExceptionExit
fffff800`003866a0 fffffadf`39b64c56 : fffffadf`39b6306b 00000000`00000000 00000000`00000022 00000000`00000000 : nt!KiInvalidOpcodeFault+0xc3
fffff800`00386830 fffffadf`39b6306b : 00000000`00000000 00000000`00000022 00000000`00000000 00000000`00000000 : 0xfffffadf`39b64c56
fffff800`00386838 00000000`00000000 : 00000000`00000022 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffadf`39b6306b


fffff800`01080e86 cc int 3


SYMBOL_NAME: nt!KiDispatchException+128



IMAGE_NAME: ntkrnlmp.exe


FAILURE_BUCKET_ID: X64_0x1E_c000001d_BAD_IP_nt!KiDispatchException+128

BUCKET_ID: X64_0x1E_c000001d_BAD_IP_nt!KiDispatchException+128

Followup: MachineOwner

BC AdBot (Login to Remove)


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users