I've also got this message also, in my case I'll used the newest nForce driver, but now I've got other BSOD.
I've debugged one of your .dmp:
==============================================
Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [c:\windows\minidump\a\Mini092705-06.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: c:\windows\symbols
Executable search path is: c:\windows\i386
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Tue Sep 27 21:02:47.640 2005 (GMT+3)
System Uptime: 0 days 0:02:41.140
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
........................................................................................................................................
Loading User Symbols
Unable to load image RT2500.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for RT2500.sys
*** ERROR: Module load completed but symbols could not be loaded for RT2500.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {257e, 2, 0, f8fcdac2}
Probably caused by : RT2500.sys ( RT2500+bac2 )
Followup: MachineOwner
---------
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: 0000257e, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f8fcdac2, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 0000257e
CURRENT_IRQL: 2
FAULTING_IP:
RT2500+bac2
f8fcdac2 0fb608 movzx ecx,byte ptr [eax]
CUSTOMER_CRASH_COUNT: 6
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: Idle
LAST_CONTROL_TRANSFER: from f8fe2c94 to f8fcdac2
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
8054ff48 f8fe2c94 80550070 0000257e 00000006 RT2500+0xbac2
805500a8 f2500000 00000102 0002f250 80550000 RT2500+0x20c94
805500ac 00000000 0002f250 80550000 f8fd5f4b 0xf2500000
STACK_COMMAND: kb
FOLLOWUP_IP:
RT2500+bac2
f8fcdac2 0fb608 movzx ecx,byte ptr [eax]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: RT2500+bac2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: RT2500
IMAGE_NAME: RT2500.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 42675c99
FAILURE_BUCKET_ID: 0xD1_RT2500+bac2
BUCKET_ID: 0xD1_RT2500+bac2
Followup: MachineOwner
---------
=======================================
This caused your BSOD: Sample Driver for Ralink 802.11g Wireless PCI Adapters - Ralink 802.11g Wireless PCI Adapters - Ralink Technology Inc.