Debug minidump

Code:

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*http://msdl.microsoft.com/download/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                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
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.

FAULTING_IP: 
+0
fffffa80`07e5bb60 06              ???

EXCEPTION_PARAMETER1:  0000000000000002

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  SearchProtocol

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002ab6a17 to fffff80002a76f00

FAILED_INSTRUCTION_ADDRESS: 
+0
fffffa80`07e5bb60 06              ???

STACK_TEXT:  
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


STACK_COMMAND:  kb

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

SYMBOL_STACK_INDEX:  1

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

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

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.