[Mellosun]

Moin Bordies,

Also gestern erfolgreich den RC1 von Win 7 install!

Doch heute Vormittag hatte ich 4 Bluescreens hintereinander.
Zuerst gingen die Minianwendungen nicht mehr....kurz danach der Bluescreen.

Nach einem Neustart kam dann das Fenster das Windows nach einen unerwartenden runterfahren wieder ausgeführt wird und Bluscreen die zweite!
Das gleiche passierte beim nächsten Neustart....
Beim vierten Neustart ging der explorer nicht mehr.....ich habe dann den taskmanager geöffnet und nen neuen Task (explorer.exe) gestartet! Da kamm die Meldung: Taskmanager funktioniert nicht mehr....nochmaliges aufrufen ging aber! Ich habe dann wieder ein neustart gemacht und mir das Debugger tool von MS geladen. Hier mal der inhalt:

CODE

Loading Dump File [C:\Users\Chef\Desktop\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is 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+ *
**************************************************
*******************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Windows 7 Kernel Version 7100 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Machine Name:
Kernel base = 0xfffff800`02859000 PsLoadedModuleList = 0xfffff800`02a92e90
Debug session time: Thu May 7 10:51:52.688 2009 (GMT+2)
System Uptime: 0 days 0:01:38.467
**************************************************
*******************
* 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+ *
**************************************************
*******************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
..................................................
.............
..................................................
..............
..........
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffdf018). Type ".hh dbgerr001" for details
Loading unloaded module list
....
**************************************************
*****************************
* *
* Bugcheck Analysis *
* *
**************************************************
*****************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {5003, fffff70001080000, 3a75, 3a77000074e8}

***** 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. ***
*** ***
*** 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 ***
*** ***
**************************************************
***********************
**************************************************
***********************
*** ***
*** ***
*** 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 ***
*** ***
**************************************************
***********************
**************************************************
***********************
*** ***
*** ***
*** 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 ***
*** ***
**************************************************
***********************
**************************************************
***********************
*** ***
*** ***
*** 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 : ntkrnlmp.exe ( nt!wcsncat_s+246a4 )

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

Dannach ist ja die ntkrnlmp.exe für die Bluescreen´s verantwortlich.....nur wo liegt da das Problem? Wie kann ich selbiges identifizieren und beseitigen?

Hoffe, ihr habt Tips für mich.....


Gruß Mello

[caracas]

Hast du mal den erweiterten Start mittels F8 Taste aufgerufen?

Mach das Mal und starte a) im abgesicherten Modus oder b) letzte funktioniende Version (Wiederherstellungspunkt)

[Mellosun]

Also momentan funktioniert Win 7 ja wieder....also ich bin weder in den Abgesicherten Modus, noch habe ich die Letzte Funktionierende Version benutzt!

[caracas]

Wenn es jetzt wieder funktioniert, dann setz dir einen Wiederherstellungspunkt

[Mellosun]

Zitat (MagicAndre1981: 07.05.2009, 13:19)

Bug Check 0x1A: MEMORY_MANAGEMENT

Trage mal im Debugger unter "Symbol File Path" das hier ein:
srv*C:\Windows\symbols*http://msdl.microsoft.com/download/symbols

und starte die Analyze nochmals.

Erstmal Danke für die Hilfe.....

Ich habe das nun gemacht, folgendes kommt nun dabei raus:

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


Loading Dump File [C:\Users\Chef\Desktop\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

WARNING: Whitespace at end of path element
Symbol search path is: srv*C:\Windows\symbols*http://msdl.microsoft.com/download/symbols 
Executable search path is: 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
Windows 7 Kernel Version 7100 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Machine Name:
Kernel base = 0xfffff800`02859000 PsLoadedModuleList = 0xfffff800`02a92e90
Debug session time: Thu May  7 10:51:52.688 2009 (GMT+2)
System Uptime: 0 days 0:01:38.467
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
Loading Kernel Symbols
..................................................
.............
..................................................
..............
..........
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffdf018).  Type ".hh dbgerr001" for details
Loading unloaded module list
....
**************************************************
*****************************
*                                                                                                                                                        *
*                                               Bugcheck Analysis                                                                       *
*                                                                                                                                                        *
**************************************************
*****************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {5003, fffff70001080000, 3a75, 3a77000074e8}

***** 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.                                                                                                             ***
***                                                                                                                                ***
***     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                                                                       ***
***                                                                                                                                ***
**************************************************
***********************
**************************************************
***********************
***                                                                                                                                ***
***                                                                                                                                ***
***     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                                                                       ***
***                                                                                                                                ***
**************************************************
***********************
**************************************************
***********************
***                                                                                                                                ***
***                                                                                                                                ***
***     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                                                                       ***
***                                                                                                                                ***
**************************************************
***********************
**************************************************
***********************
***                                                                                                                                ***
***                                                                                                                                ***
***     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                                                                       ***
***                                                                                                                                ***
**************************************************
***********************
PEB is paged out (Peb.Ldr = 000007ff`fffdf018).  Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 000007ff`fffdf018).  Type ".hh dbgerr001" for details
Probably caused by : ntkrnlmp.exe ( nt!wcsncat_s+246a4 )

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

Ist das Hilfreich?

[Mellosun]

OK, aber wie schicke ich das an MS?
Macht das WIn 7 selbst oder muss ich da nachhelfen?

[Mellosun]

Ich muss Dich, und auch mich, leider enttäuschen.....

Ich finde dort keinen solchen Punkt!

Was ich sehe ist: Archivierte Meldungen anzeigen aber wenn ich darauf klicke, sind keine vorhanden!
Das ganze sieht so aus:



Habe zwar noch etwas gesucht aber nichts gefunden.....


Und noch ein zweites Problem habe ich mit Win7:

Nachdem ich einen Neustart des Rechners gemacht habe, sind meine Desktop Einstellungen jedesmal vertauscht.
Ich habe zwei TFTs, der Linke ist das Primäre Gerät also es befindet sich die Taskleiste auf diesem Monitor!
Auf dem Rechten Monitor habe ich die Minianwendungen sowie Rocked Dock! Nach einem Neustart des PCs ist es genau anders rum....auf dem Linken Monitor sind die Minianwendungen und Rocked Dock und auf dem Rechten Monitor ist die Taskleiste! Ich kann dies dann in der Nvidia Systemsteuerung auch nicht ändern....ich muss jedesmal die VGA Stecker an der Grafikkarte tauschen....
Ich habe eine Nvidia 8800 GTX und den Beta Treiber von letzter Woche!
Ich werde jetzt mal den neuen Treiber versuchen aber vielleicht hat ja dennoch schon einer eine Lösung des Problems!


THX, Mellosun

[druidix]

Hi,
bei mir die lief Installation fast vollständig ohne Probleme durch. Nur ein Treiber des Compaq Evo N800C fehlte: die eingbaute WLAN Karte. Nach download der Treiber von HP für XP produziert der Rechner reproduzierbar bluescreens. Wird der Treiber deaktiviert läuft das System ohne Probleme. Gruesse vom druiden

Hier das dump file :

CODE

Loading Dump File [G:\050709-41099-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 \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows Kernel Version 7100 UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7100.0.x86fre.winmain_win7rc.090421-1700
Kernel base = 0x8282f000 PsLoadedModuleList = 0x8296e570
Debug session time: Thu May 7 07:47:48.554 2009 (GMT+2)
System Uptime: 0 days 0:03:24.589
**************************************************
*******************
* 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 \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** 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
....
**************************************************
*****************************
* *
* Bugcheck Analysis *
* *
**************************************************
*****************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {31420200, 2, 0, 828f4393}

*** WARNING: Unable to verify timestamp for ndis.sys
*** ERROR: Module load completed but symbols could not be loaded for ndis.sys
*** WARNING: Unable to verify timestamp for wlcom51b.sys
*** ERROR: Module load completed but symbols could not be loaded for wlcom51b.sys
***** 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. ***
*** ***
*** 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 ***
*** ***
**************************************************
***********************
**************************************************
***********************
*** ***
*** ***
*** 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 ***
*** ***
**************************************************
***********************
**************************************************
***********************
*** ***
*** ***
*** 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 ***
*** ***
**************************************************
***********************
**************************************************
***********************
*** ***
*** ***
*** 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 : wlcom51b.sys ( wlcom51b+6464 )

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

Dieser Beitrag wurde von Urne bearbeitet: 16. Mai 2009 - 09:55
Änderungsgrund: geboxt. Urne

[caracas]

Versuchs mal mit dem alten Treiber, den du mit dem Gerät erhalten hast. Klappt meistens!!