Vollständige Version anzeigen : Bluescreen & G5 Set Point-Problem


Tranceport
23.05.2008, 13:20

Hi Leute!
Habe zwei Probleme mit Vista 64bit bzw. Server 2008 64bit (Ein Freund hat exakt die gleiche Hardware wie ich, PC&G5, Hardwarefehler können also ausgeschlossen werden)
1. Setpoint zeigt mir die DPIeinstellungen und die Tastenbelegung der Maus nicht an (also links die Reiter mit der Maus und dem Schachturm) Hatte ich bei XP auchmal mit dem neusten Treiber, hab dann einfach von meiner LogitechCD die dabei war installiert, aber die ist schon zu alt für Vista. Logitech hab ich schon gemailt, aber keine wirklich gute Antwort bekommen.
2. und zwar bekomm ich nach einer bestimmen Zeit zocken (im letzten Fall war es Kanes Rache) einen schicken Bluescreen. Die Minidump sagt folgendes dazu:

*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****

Use !analyze -v to get detailed debugging information.

BugCheck D1, {10, 2, 1, fffffa6000851c5e}

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

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to -pdb files that have full type information. ***
*** ***
*** Certain -pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to -pdb files that have full type information. ***
*** ***
*** Certain -pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to -pdb files that have full type information. ***
*** ***
*** Certain -pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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+ *
*********************************************************************
Probably caused by : NDIS-SYS ( NDIS+42c5e )

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

Finished dump check


Wie bring ich dem debugger die symbole O_o ?
Trance




raid-rush.ws | Imprint & Contact pr