Condor: Here is an analysis of your minidmp. It appears to be your video card as the culprit.
Microsoft (R) Windows Debugger Version 6.7.0005.1
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\DOWNLOADS\Mini092007-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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805533a0
Debug session time: Thu Sep 20 23:07:54.525 2007 (GMT-7)
System Uptime: 0 days 9:33:03.580
Loading Kernel Symbols
...................................................................................................................................................
Loading User Symbols
Loading unloaded module list
............
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {0, 0, 0, 0}
Unable to load image \SystemRoot\System32\ativvaxx.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ativvaxx.dll
*** ERROR: Module load completed but symbols could not be loaded for ativvaxx.dll
Probably caused by : ativvaxx.dll ( ativvaxx+5c833 )
Followup: MachineOwner
---------
kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000000, EXCEPTION_DIVIDED_BY_ZERO
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
TRAP_FRAME: a76fcb34 -- (.trap 0xffffffffa76fcb34)
ErrCode = 00000000
eax=00000000 ebx=e21d9010 ecx=00000000 edx=00000000 esi=00000000 edi=e2368940
eip=bfd9c833 esp=a76fcba8 ebp=0826dc88 iopl=0 nv up ei pl zr ac pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010257
ativvaxx+0x5c833:
bfd9c833 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from 80596813 to 804f8aca
STACK_TEXT:
a76fcad0 80596813 0000007f bfd9c833 00000000 nt!KeBugCheck+0x14
a76fcb28 8053d60f a76fcb34 0826dc88 bfd9c833 nt!Ki386CheckDivideByZeroTrap+0x41
a76fcb28 bfd9c833 a76fcb34 0826dc88 bfd9c833 nt!KiTrap00+0x83
WARNING: Stack unwind information not available. Following frames may be wrong.
a76fcba4 e2141048 e12b6f58 0826dc88 e239ca04 ativvaxx+0x5c833
a76fcca4 805a504f 805a5fa1 00000078 bfd49ebd 0xe2141048
a76fcd54 8053ca28 01a0002c 0586f958 0586f940 nt!MiSecureVirtualMemory+0x4bb
a76fcd54 7c90eb94 01a0002c 0586f958 0586f940 nt!KiFastCallEntry+0xf8
0586f940 00000000 00000000 00000000 00000000 0x7c90eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
ativvaxx+5c833
bfd9c833 ?? ???
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: ativvaxx+5c833
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ativvaxx
IMAGE_NAME: ativvaxx.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 4584abd1
FAILURE_BUCKET_ID: 0x7f_0_ativvaxx+5c833
BUCKET_ID: 0x7f_0_ativvaxx+5c833
Followup: MachineOwner
---------
