So, yesterday I blue screen of death crashed 3 times shortly after loading Korengal valley. And was unable to play in the Insurgency World series. My 1st thought was just to reinstall PR and
BF2. This did not work. So in order to open the crash dump files I downloaded debugging tools for windows. Here are the results, it clearly says that nv4_mini.sys is the problem, my question is how do I fix this? This is pretty technical stuff, does anyone have any ideas, it would be appreciated.
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini033009-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 (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.080814-1236
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Mon Mar 30 08:56:22.484 2009 (GMT-4)
System Uptime: 0 days 0:01:48.489
Loading Kernel Symbols
.................................................. .................................................. ...........................................
Loading User Symbols
Loading unloaded module list
...........
Unable to load image nv4_mini.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_mini.sys
*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {7, 2, 0, b8f21657}
Probably caused by : nv4_mini.sys ( nv4_mini+66657 )
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: 00000007, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: b8f21657, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 00000007
CURRENT_IRQL: 2
FAULTING_IP:
nv4_mini+66657
b8f21657 8b4808 mov ecx,dword ptr [eax+8]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: Idle
LAST_CONTROL_TRANSFER: from ac0175f6 to b8f21657
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
8055127c ac0175f6 b8e8bb75 806e6900 00006f5b nv4_mini+0x66657
80551290 00000000 00000000 00006d9e 00000040 rdbss!RxInsertWorkQueueItem+0xb5
STACK_COMMAND: kb
FOLLOWUP_IP:
nv4_mini+66657
b8f21657 8b4808 mov ecx,dword ptr [eax+8]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nv4_mini+66657
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nv4_mini
IMAGE_NAME: nv4_mini.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 499c9be8
FAILURE_BUCKET_ID: 0xD1_nv4_mini+66657
BUCKET_ID: 0xD1_nv4_mini+66657
Followup: MachineOwner
---------