Hardware:
MSI K8N Neo4 Platinum
AMD 64 x2 4200+ CPU
2-6600gt XFX video cards (SLI)
2 gb OCZ dual channel ram
one 160 gb sata hd
one 160 gb ide hd
I followed the instructions from here: http://www.bleepingcomputer.com/forums/t/176011/how-to-receive-help-diagnosing-blue-screens-and-windows-crashes/
My WinDbg report:
Microsoft ® Windows Debugger Version 6.11.0001.402 X86
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini021509-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 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.080814-1236
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sun Feb 15 15:52:23.734 2009 (GMT-6)
System Uptime: 0 days 0:24:18.456
Loading Kernel Symbols
...............................................................
..............................................................
Loading User Symbols
Loading unloaded module list
...........
Unable to load image nvata.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvata.sys
*** ERROR: Module load completed but symbols could not be loaded for nvata.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {60, 2, 0, b9ef178c}
Probably caused by : nvata.sys ( nvata+1378c )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000060, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: b9ef178c, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 00000060
CURRENT_IRQL: 2
FAULTING_IP:
nvata+1378c
b9ef178c 8b4660 mov eax,dword ptr [esi+60h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: Idle
LAST_CONTROL_TRANSFER: from b9ee7c7d to b9ef178c
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
805513d8 b9ee7c7d 8a56d0e8 00000000 8a56d0e8 nvata+0x1378c
805513f8 b9ee069e 8a56d0e8 8a56d864 00000000 nvata+0x9c7d
80551418 b9ee0e60 8a56d0e8 8a56d864 ffdff9c0 nvata+0x269e
80551428 80545e7f 8a56d1d0 8a56d0e8 00000000 nvata+0x2e60
80551450 80545d64 00000000 0000000e 00000000 nt!KiRetireDpcList+0x61
80551454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28
STACK_COMMAND: kb
FOLLOWUP_IP:
nvata+1378c
b9ef178c 8b4660 mov eax,dword ptr [esi+60h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nvata+1378c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvata
IMAGE_NAME: nvata.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 43052d35
FAILURE_BUCKET_ID: 0xD1_nvata+1378c
BUCKET_ID: 0xD1_nvata+1378c
Followup: MachineOwner
---------
Thanks for any help. Looks like driver error, but, not sure for what.
Edited by lynned, 15 February 2009 - 05:56 PM.