nv4_mini.sys bluescreen

servus,

hab in letzter zeit viele bluescreens. treiberkonflikte kann ich soweit ausschließen, da ich 1stens komplett neu installiert hab, und 2tens nur die neuesten treiber drauf sind!
anfangs dachte ich, es wäre die grafikkarte, da ich zu 95% beim spielen die screens hatte. mittlerweile hab ich keine ahnung was es sein könnte. arbeitsspeicher und hdd sind ausgeschlossen, habe ich getestet...

hier noch die minidump


Microsoft (R) Windows Debugger  Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini012007-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path.           *
* Use .symfix to have the debugger choose a symbol path.                   *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Sat Jan 20 12:22:27.828 2007 (GMT+1)
System Uptime: 0 days 2:33:43.490
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
..................................................................... ..............................................
Loading User Symbols
Loading unloaded module list
...........
Unable to load image nv4_mini.sys, Win32 error 2
*** 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, {8, 9, 0, ba58bae6}

ANALYSIS: Kernel with unknown size. Will force reload symbols with known size.
ANALYSIS: Force reload command: .reload /f ntoskrnl.exe=FFFFFFFF804D7000,213F80,42250FF9
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Probably caused by : nv4_mini.sys ( nv4_mini+3fae6 )

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



ich hoffe man kann mir helfen. oder zumindest den fehler mal eingrenzen, vielleicht doch auf einen treiber, oder usb oder sonst was... vielen dank im vorraus


mfg

wastl


ps: ich werde jetzt mal die omega treiber für die graka installieren. evtl laufen die stabiler... scheinbar ist der nv4.... ein nvidia treiber... son shiiit!!!

naja, ich halt euch auf dem laufenden, falls jmd das gleiche problem haben sollte