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: Debug minidump

11 Mar 2010   #1

Windows 7 Ultimate 64
Debug minidump

Hi gus I have no idea how to do this. Could someone please attemp to debug this dmp. I will be very greatful.

My System SpecsSystem Spec
11 Mar 2010   #2

Windows 7 Professional x64

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\Jonathan\Desktop\031010-17846-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a05000 PsLoadedModuleList = 0xfffff800`02c42e50
Debug session time: Wed Mar 10 15:19:31.254 2010 (GMT-5)
System Uptime: 0 days 0:02:34.144
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

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

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+460da )

Followup: MachineOwner

7: 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: fffffa8007e5bb60, 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.

fffffa80`07e5bb60 06              ???

EXCEPTION_PARAMETER1:  0000000000000002

EXCEPTION_PARAMETER2:  0000000000000000




PROCESS_NAME:  SearchProtocol


LAST_CONTROL_TRANSFER:  from fffff80002ab6a17 to fffff80002a76f00

fffffa80`07e5bb60 06              ???

fffff880`0846f6c8 fffff800`02ab6a17 : 00000000`0000001e ffffffff`c000001d fffffa80`07e5bb60 00000000`00000002 : nt!KeBugCheckEx
fffff880`0846f6d0 fffff800`02a76542 : fffff880`0846fea8 00000000`00000000 fffff880`0846ff50 fffffa80`07e5bc20 : nt! ?? ::FNODOBFM::`string'+0x460da
fffff880`0846fd70 fffff800`02a7469f : fffff880`0846ff50 fffff880`01088102 00000000`00000000 fffffa80`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`0846ff50 fffffa80`07e5bb60 : fffffa80`07bf05b0 00000000`00000000 00000000`00000000 fffff800`02a801af : nt!KiInvalidOpcodeFault+0x11f
fffff880`084700e0 fffffa80`07bf05b0 : 00000000`00000000 00000000`00000000 fffff800`02a801af fffffa80`06af3010 : 0xfffffa80`07e5bb60
fffff880`084700e8 00000000`00000000 : 00000000`00000000 fffff800`02a801af fffffa80`06af3010 fffffa80`05756c10 : 0xfffffa80`07bf05b0


nt! ?? ::FNODOBFM::`string'+460da
fffff800`02ab6a17 cc              int     3


SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+460da

FOLLOWUP_NAME:  MachineOwner


IMAGE_NAME:  ntkrnlmp.exe


FAILURE_BUCKET_ID:  X64_0x1E_BAD_IP_nt!_??_::FNODOBFM::_string_+460da

BUCKET_ID:  X64_0x1E_BAD_IP_nt!_??_::FNODOBFM::_string_+460da

Followup: MachineOwner
There is the debugging.

There's not much we can determine from that one dmp, but my best advice is try a memory test, update your video card drivers, and run a system files check.

Download a copy of Memtest86 and burn the ISO to a CD using ImgBurn. Boot from the CD, and run at least 5 passes.

Open an elevated command prompt and enter sfc /scannow.
My System SpecsSystem Spec
11 Mar 2010   #3

Windows 7 Ultimate 64

Thank you very much. I had already run memtest all drivers are the latest on a fresh os install. and sfc did not find any problems.
My System SpecsSystem Spec


 Debug minidump

Thread Tools

Similar help and support threads
Thread Forum
BSOD - Minidump debug
Would someone please debug these minidump files? This has been occurring a min. of 2x per day. Thanks for any help in resolving this crisis.
BSOD Help and Support
Hi Can anyone tell me what I need to do to read the .DMP files in the minidump directory. Windows 7 32 bit. Thanx
BSOD Help and Support
Debug please!
thanks guys
BSOD Help and Support
How do I debug a minidump?
Hey there folks :) I'm basically new to the turf and I have a couple of questions (You can skip the rest of this paragraph to get to the good stuff). First let me introduce my self: I work a lot with installing windows and maintaining computers for friends and associates and I just installed...
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 13:48.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App