That dmp does not help much.

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-24953-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02849000 PsLoadedModuleList = 0xfffff800`02a86e50
Debug session time: Wed Mar 10 16:40:24.417 2010 (GMT-5)
System Uptime: 0 days 0:35:42.074
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {60, 0, fffff880009e8180, 1}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000060, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009e8180, The PRCB address of the hung processor.
Arg4: 0000000000000001, 0.

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


OVERLAPPED_MODULE: Address regions for 'nvlddmkm' and 'nvlddmkm.sys' overlap

BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`076c26f8 fffff800`02867443 : 00000000`00000101 00000000`00000060 00000000`00000000 fffff880`009e8180 : nt!KeBugCheckEx
fffff880`076c2700 fffff800`028c35f7 : ffff0800`00000000 fffff800`00000001 00000000`0002625a 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4e3e
fffff880`076c2790 fffff800`02814090 : 00000000`00000000 fffff880`076c2940 fffff800`0282f460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`076c2890 fffff800`028b73f3 : 00000000`6e74a774 fffff800`0282f460 00000065`00000000 00000075`0000027b : hal!HalpRtcClockInterrupt+0x130
fffff880`076c28c0 fffff800`028c8e00 : fffff900`00000000 00000000`00000001 00000000`00000000 fffff960`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`076c2a50 fffff800`028d3061 : fffff900`c1c42001 00000000`00000003 00000000`00000001 fffff900`c23ad770 : nt!KeFlushMultipleRangeTb+0x260
fffff880`076c2b20 fffff800`028e60fb : 00000000`00000003 fffff880`076c2c80 fffff900`c1c42000 fffff960`001f653f : nt!MiFlushTbAsNeeded+0x1d1
fffff880`076c2c30 fffff800`029eaceb : 00000000`000027e0 00000000`000027e0 00000000`00000021 fffffa80`024c95b0 : nt!MiAllocatePagedPoolPages+0x4bb
fffff880`076c2d50 fffff800`028cd860 : 00000000`000027e0 fffff880`030b4cc0 00000000`00000021 00000000`00000000 : nt!MiAllocatePoolPages+0x8e2
fffff880`076c2ea0 fffff800`029edbfe : 00000000`00000000 fffff960`001340d1 00000000`00000020 fffff880`030b4cc0 : nt!ExpAllocateBigPool+0xb0
fffff880`076c2f90 fffff960`001228ed : fffff900`c2acc410 00000000`00000000 fffff960`00266fb4 fffff960`001340d1 : nt!ExAllocatePoolWithTag+0x82e
fffff880`076c3080 fffff960`00123e0f : 00000000`00000000 fffff880`076c3220 00000000`00000001 fffff960`001214ee : win32k!AllocateObject+0xdd
fffff880`076c30c0 fffff960`000fb48c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!SURFMEM::bCreateDIB+0x1fb
fffff880`076c31b0 fffff960`000fb006 : 00000021`00000049 00000000`00000021 ffffffff`fb08111e 00000000`00000049 : win32k!hsurfCreateCompatibleSurface+0x3bc
fffff880`076c3280 fffff800`028ba153 : fffffa80`06446a10 fffff880`076c33e0 00000000`00000000 fffff900`c00c0010 : win32k!GreCreateCompatibleBitmap+0x26e
fffff880`076c3360 00000000`755b2dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`001fceb8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x755b2dd9


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE

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