Top-Themen

Aktuelle Themen (A bis Z)

Administrator.de FeedbackApache ServerAppleAssemblerAudioAusbildungAuslandBackupBasicBatch & ShellBenchmarksBibliotheken & ToolkitsBlogsCloud-DiensteClusterCMSCPU, RAM, MainboardsCSSC und C++DatenbankenDatenschutzDebianDigitiales FernsehenDNSDrucker und ScannerDSL, VDSLE-BooksE-BusinessE-MailEntwicklungErkennung und -AbwehrExchange ServerFestplatten, SSD, RaidFirewallFlatratesGoogle AndroidGrafikGrafikkarten & MonitoreGroupwareHardwareHosting & HousingHTMLHumor (lol)Hyper-VIconsIDE & EditorenInformationsdiensteInstallationInstant MessagingInternetInternet DomäneniOSISDN & AnaloganschlüsseiTunesJavaJavaScriptKiXtartKVMLAN, WAN, WirelessLinuxLinux DesktopLinux NetzwerkLinux ToolsLinux UserverwaltungLizenzierungMac OS XMicrosoftMicrosoft OfficeMikroTik RouterOSMonitoringMultimediaMultimedia & ZubehörNetzwerkeNetzwerkgrundlagenNetzwerkmanagementNetzwerkprotokolleNotebook & ZubehörNovell NetwareOff TopicOpenOffice, LibreOfficeOutlook & MailPapierkorbPascal und DelphiPeripheriegerätePerlPHPPythonRechtliche FragenRedHat, CentOS, FedoraRouter & RoutingSambaSAN, NAS, DASSchriftartenSchulung & TrainingSEOServerServer-HardwareSicherheitSicherheits-ToolsSicherheitsgrundlagenSolarisSonstige SystemeSoziale NetzwerkeSpeicherkartenStudentenjobs & PraktikumSuche ProjektpartnerSuseSwitche und HubsTipps & TricksTK-Netze & GeräteUbuntuUMTS, EDGE & GPRSUtilitiesVB for ApplicationsVerschlüsselung & ZertifikateVideo & StreamingViren und TrojanerVirtualisierungVisual StudioVmwareVoice over IPWebbrowserWebentwicklungWeiterbildungWindows 7Windows 8Windows 10Windows InstallationWindows MobileWindows NetzwerkWindows ServerWindows SystemdateienWindows ToolsWindows UpdateWindows UserverwaltungWindows VistaWindows XPXenserverXMLZusammenarbeit

Problem Prolific USB RS232 Adapter

Frage Hardware Peripheriegeräte

Mitglied: killtec

killtec (Level 3) - Jetzt verbinden

23.10.2014 um 14:21 Uhr, 1553 Aufrufe, 11 Kommentare

Hallo zusammen,
folgendes Problem. An einem Laptop mit Windows 7 Pro 64 Bit hängt ein USB-Adapter von Prolific (bzw. mit einem Prolific Chip) dran.
Der Adapter funktioniert ca. 20-30 Sekunden normal.
Dann passiert es, dass im Putty Fenster alles stehen bleibt. Der Adapter hängt sich auf. Ziehe ich ihn vom PC ab und stecke ihn wieder an, so wird dieser nicht mehr erkannt. Das zeigt sich so, als ob ich nichts anschließen würde.
Nach dem Neustart des PC's funktioniert er weider ein paar Sekunden.

Ich habe auch schon den aktuellsten Treiber geladen.

Es scheint jedoch auch, als ob sich der gesamte USB Bus aufhängt. Schließe ich einen USB-Stick an, passiert auch nichts.

Gruß
Mitglied: keine-ahnung
23.10.2014 um 14:45 Uhr
Moin,
hängt ein USB-Adapter von Prolific
auf Wasserleitung? Telefon? Fernsehantenne?
Es scheint jedoch auch, als ob sich der gesamte USB Bus aufhängt.
You get, what you pay ... hier eine Lösungsmöglichkeit, die hiermit kombiniert werden sollte ...

LG, Thomas
Bitte warten ..
Mitglied: killtec
23.10.2014 um 14:45 Uhr
Hier noch der Chrashdump:
01.
ini Kernel Dump File: Only registers and stack trace are available 
02.
 
03.
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`068cb532? 
04.
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`07537142? 
05.
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`153d37b2? 
06.
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`0862a042? 
07.
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`06cb0c32? 
08.
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`12354542? 
09.
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`11e9ec32? 
10.
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`123736b2? 
11.
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`11b4a042? 
12.
Symbol search path is: *** Invalid *** 
13.
**************************************************************************** 
14.
* Symbol loading may be unreliable without a symbol search path.           * 
15.
* Use .symfix to have the debugger choose a symbol path.                   * 
16.
* After setting your symbol path, use .reload to refresh symbol locations. * 
17.
**************************************************************************** 
18.
Executable search path is:  
19.
********************************************************************* 
20.
* Symbols can not be loaded because symbol path is not initialized. * 
21.
*                                                                   * 
22.
* The Symbol Path can be set by:                                    * 
23.
*   using the _NT_SYMBOL_PATH environment variable.                 * 
24.
*   using the -y <symbol_path> argument when starting the debugger. * 
25.
*   using .sympath and .sympath+                                    * 
26.
********************************************************************* 
27.
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2 
28.
*** WARNING: Unable to verify timestamp for ntoskrnl.exe 
29.
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe 
30.
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 
31.
Product: WinNt, suite: TerminalServer SingleUserTS 
32.
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144 
33.
Machine Name: 
34.
Kernel base = 0xfffff800`03218000 PsLoadedModuleList = 0xfffff800`0345b890 
35.
Debug session time: Thu Oct 23 14:32:37.897 2014 (UTC + 2:00) 
36.
System Uptime: 0 days 0:52:46.233 
37.
********************************************************************* 
38.
* Symbols can not be loaded because symbol path is not initialized. * 
39.
*                                                                   * 
40.
* The Symbol Path can be set by:                                    * 
41.
*   using the _NT_SYMBOL_PATH environment variable.                 * 
42.
*   using the -y <symbol_path> argument when starting the debugger. * 
43.
*   using .sympath and .sympath+                                    * 
44.
********************************************************************* 
45.
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2 
46.
*** WARNING: Unable to verify timestamp for ntoskrnl.exe 
47.
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe 
48.
Loading Kernel Symbols 
49.
............................................................... 
50.
................................................................ 
51.
.............................................................. 
52.
Loading User Symbols 
53.
Loading unloaded module list 
54.
........... 
55.
 
56.
************* Symbol Loading Error Summary ************** 
57.
Module name            Error 
58.
ntoskrnl               The system cannot find the file specified 
59.
 
60.
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded. 
61.
You should also verify that your symbol search path (.sympath) is correct. 
62.
******************************************************************************* 
63.
*                                                                             * 
64.
*                        Bugcheck Analysis                                    * 
65.
*                                                                             * 
66.
******************************************************************************* 
67.
 
68.
Use !analyze -v to get detailed debugging information. 
69.
 
70.
BugCheck 1000009F, {4, 258, fffffa80069e5b50, fffff80000b9c3d0} 
71.
 
72.
***** Kernel symbols are WRONG. Please fix symbols to do analysis. 
73.
 
74.
************************************************************************* 
75.
***                                                                   *** 
76.
***                                                                   *** 
77.
***    Either you specified an unqualified symbol, or your debugger   *** 
78.
***    doesn't have full symbol information.  Unqualified symbol      *** 
79.
***    resolution is turned off by default. Please either specify a   *** 
80.
***    fully qualified symbol module!symbolname, or enable resolution *** 
81.
***    of unqualified symbols by typing ".symopt- 100". Note that   *** 
82.
***    enabling unqualified symbol resolution with network symbol     *** 
83.
***    server shares in the symbol path may cause the debugger to     *** 
84.
***    appear to hang for long periods of time when an incorrect      *** 
85.
***    symbol name is typed or the network symbol server is down.     *** 
86.
***                                                                   *** 
87.
***    For some commands to work properly, your symbol path           *** 
88.
***    must point to .pdb files that have full type information.      *** 
89.
***                                                                   *** 
90.
***    Certain .pdb files (such as the public OS symbols) do not      *** 
91.
***    contain the required information.  Contact the group that      *** 
92.
***    provided you with these symbols if you need this command to    *** 
93.
***    work.                                                          *** 
94.
***                                                                   *** 
95.
***    Type referenced: NT!_ETHREAD                                   *** 
96.
***                                                                   *** 
97.
************************************************************************* 
98.
Implicit thread is now fffffa80`069e5b50 
99.
************************************************************************* 
100.
***                                                                   *** 
101.
***                                                                   *** 
102.
***    Either you specified an unqualified symbol, or your debugger   *** 
103.
***    doesn't have full symbol information.  Unqualified symbol      *** 
104.
***    resolution is turned off by default. Please either specify a   *** 
105.
***    fully qualified symbol module!symbolname, or enable resolution *** 
106.
***    of unqualified symbols by typing ".symopt- 100". Note that   *** 
107.
***    enabling unqualified symbol resolution with network symbol     *** 
108.
***    server shares in the symbol path may cause the debugger to     *** 
109.
***    appear to hang for long periods of time when an incorrect      *** 
110.
***    symbol name is typed or the network symbol server is down.     *** 
111.
***                                                                   *** 
112.
***    For some commands to work properly, your symbol path           *** 
113.
***    must point to .pdb files that have full type information.      *** 
114.
***                                                                   *** 
115.
***    Certain .pdb files (such as the public OS symbols) do not      *** 
116.
***    contain the required information.  Contact the group that      *** 
117.
***    provided you with these symbols if you need this command to    *** 
118.
***    work.                                                          *** 
119.
***                                                                   *** 
120.
***    Type referenced: nt!_ETHREAD                                   *** 
121.
***                                                                   *** 
122.
************************************************************************* 
123.
************************************************************************* 
124.
***                                                                   *** 
125.
***                                                                   *** 
126.
***    Either you specified an unqualified symbol, or your debugger   *** 
127.
***    doesn't have full symbol information.  Unqualified symbol      *** 
128.
***    resolution is turned off by default. Please either specify a   *** 
129.
***    fully qualified symbol module!symbolname, or enable resolution *** 
130.
***    of unqualified symbols by typing ".symopt- 100". Note that   *** 
131.
***    enabling unqualified symbol resolution with network symbol     *** 
132.
***    server shares in the symbol path may cause the debugger to     *** 
133.
***    appear to hang for long periods of time when an incorrect      *** 
134.
***    symbol name is typed or the network symbol server is down.     *** 
135.
***                                                                   *** 
136.
***    For some commands to work properly, your symbol path           *** 
137.
***    must point to .pdb files that have full type information.      *** 
138.
***                                                                   *** 
139.
***    Certain .pdb files (such as the public OS symbols) do not      *** 
140.
***    contain the required information.  Contact the group that      *** 
141.
***    provided you with these symbols if you need this command to    *** 
142.
***    work.                                                          *** 
143.
***                                                                   *** 
144.
***    Type referenced: nt!_TRIAGE_9F_PNP                             *** 
145.
***                                                                   *** 
146.
************************************************************************* 
147.
************************************************************************* 
148.
***                                                                   *** 
149.
***                                                                   *** 
150.
***    Either you specified an unqualified symbol, or your debugger   *** 
151.
***    doesn't have full symbol information.  Unqualified symbol      *** 
152.
***    resolution is turned off by default. Please either specify a   *** 
153.
***    fully qualified symbol module!symbolname, or enable resolution *** 
154.
***    of unqualified symbols by typing ".symopt- 100". Note that   *** 
155.
***    enabling unqualified symbol resolution with network symbol     *** 
156.
***    server shares in the symbol path may cause the debugger to     *** 
157.
***    appear to hang for long periods of time when an incorrect      *** 
158.
***    symbol name is typed or the network symbol server is down.     *** 
159.
***                                                                   *** 
160.
***    For some commands to work properly, your symbol path           *** 
161.
***    must point to .pdb files that have full type information.      *** 
162.
***                                                                   *** 
163.
***    Certain .pdb files (such as the public OS symbols) do not      *** 
164.
***    contain the required information.  Contact the group that      *** 
165.
***    provided you with these symbols if you need this command to    *** 
166.
***    work.                                                          *** 
167.
***                                                                   *** 
168.
***    Type referenced: nt!_KPRCB                                     *** 
169.
***                                                                   *** 
170.
************************************************************************* 
171.
************************************************************************* 
172.
***                                                                   *** 
173.
***                                                                   *** 
174.
***    Either you specified an unqualified symbol, or your debugger   *** 
175.
***    doesn't have full symbol information.  Unqualified symbol      *** 
176.
***    resolution is turned off by default. Please either specify a   *** 
177.
***    fully qualified symbol module!symbolname, or enable resolution *** 
178.
***    of unqualified symbols by typing ".symopt- 100". Note that   *** 
179.
***    enabling unqualified symbol resolution with network symbol     *** 
180.
***    server shares in the symbol path may cause the debugger to     *** 
181.
***    appear to hang for long periods of time when an incorrect      *** 
182.
***    symbol name is typed or the network symbol server is down.     *** 
183.
***                                                                   *** 
184.
***    For some commands to work properly, your symbol path           *** 
185.
***    must point to .pdb files that have full type information.      *** 
186.
***                                                                   *** 
187.
***    Certain .pdb files (such as the public OS symbols) do not      *** 
188.
***    contain the required information.  Contact the group that      *** 
189.
***    provided you with these symbols if you need this command to    *** 
190.
***    work.                                                          *** 
191.
***                                                                   *** 
192.
***    Type referenced: nt!KPRCB                                      *** 
193.
***                                                                   *** 
194.
************************************************************************* 
195.
************************************************************************* 
196.
***                                                                   *** 
197.
***                                                                   *** 
198.
***    Either you specified an unqualified symbol, or your debugger   *** 
199.
***    doesn't have full symbol information.  Unqualified symbol      *** 
200.
***    resolution is turned off by default. Please either specify a   *** 
201.
***    fully qualified symbol module!symbolname, or enable resolution *** 
202.
***    of unqualified symbols by typing ".symopt- 100". Note that   *** 
203.
***    enabling unqualified symbol resolution with network symbol     *** 
204.
***    server shares in the symbol path may cause the debugger to     *** 
205.
***    appear to hang for long periods of time when an incorrect      *** 
206.
***    symbol name is typed or the network symbol server is down.     *** 
207.
***                                                                   *** 
208.
***    For some commands to work properly, your symbol path           *** 
209.
***    must point to .pdb files that have full type information.      *** 
210.
***                                                                   *** 
211.
***    Certain .pdb files (such as the public OS symbols) do not      *** 
212.
***    contain the required information.  Contact the group that      *** 
213.
***    provided you with these symbols if you need this command to    *** 
214.
***    work.                                                          *** 
215.
***                                                                   *** 
216.
***    Type referenced: nt!_KPRCB                                     *** 
217.
***                                                                   *** 
218.
************************************************************************* 
219.
************************************************************************* 
220.
***                                                                   *** 
221.
***                                                                   *** 
222.
***    Either you specified an unqualified symbol, or your debugger   *** 
223.
***    doesn't have full symbol information.  Unqualified symbol      *** 
224.
***    resolution is turned off by default. Please either specify a   *** 
225.
***    fully qualified symbol module!symbolname, or enable resolution *** 
226.
***    of unqualified symbols by typing ".symopt- 100". Note that   *** 
227.
***    enabling unqualified symbol resolution with network symbol     *** 
228.
***    server shares in the symbol path may cause the debugger to     *** 
229.
***    appear to hang for long periods of time when an incorrect      *** 
230.
***    symbol name is typed or the network symbol server is down.     *** 
231.
***                                                                   *** 
232.
***    For some commands to work properly, your symbol path           *** 
233.
***    must point to .pdb files that have full type information.      *** 
234.
***                                                                   *** 
235.
***    Certain .pdb files (such as the public OS symbols) do not      *** 
236.
***    contain the required information.  Contact the group that      *** 
237.
***    provided you with these symbols if you need this command to    *** 
238.
***    work.                                                          *** 
239.
***                                                                   *** 
240.
***    Type referenced: nt!KPRCB                                      *** 
241.
***                                                                   *** 
242.
************************************************************************* 
243.
************************************************************************* 
244.
***                                                                   *** 
245.
***                                                                   *** 
246.
***    Either you specified an unqualified symbol, or your debugger   *** 
247.
***    doesn't have full symbol information.  Unqualified symbol      *** 
248.
***    resolution is turned off by default. Please either specify a   *** 
249.
***    fully qualified symbol module!symbolname, or enable resolution *** 
250.
***    of unqualified symbols by typing ".symopt- 100". Note that   *** 
251.
***    enabling unqualified symbol resolution with network symbol     *** 
252.
***    server shares in the symbol path may cause the debugger to     *** 
253.
***    appear to hang for long periods of time when an incorrect      *** 
254.
***    symbol name is typed or the network symbol server is down.     *** 
255.
***                                                                   *** 
256.
***    For some commands to work properly, your symbol path           *** 
257.
***    must point to .pdb files that have full type information.      *** 
258.
***                                                                   *** 
259.
***    Certain .pdb files (such as the public OS symbols) do not      *** 
260.
***    contain the required information.  Contact the group that      *** 
261.
***    provided you with these symbols if you need this command to    *** 
262.
***    work.                                                          *** 
263.
***                                                                   *** 
264.
***    Type referenced: nt!_KPRCB                                     *** 
265.
***                                                                   *** 
266.
************************************************************************* 
267.
************************************************************************* 
268.
***                                                                   *** 
269.
***                                                                   *** 
270.
***    Either you specified an unqualified symbol, or your debugger   *** 
271.
***    doesn't have full symbol information.  Unqualified symbol      *** 
272.
***    resolution is turned off by default. Please either specify a   *** 
273.
***    fully qualified symbol module!symbolname, or enable resolution *** 
274.
***    of unqualified symbols by typing ".symopt- 100". Note that   *** 
275.
***    enabling unqualified symbol resolution with network symbol     *** 
276.
***    server shares in the symbol path may cause the debugger to     *** 
277.
***    appear to hang for long periods of time when an incorrect      *** 
278.
***    symbol name is typed or the network symbol server is down.     *** 
279.
***                                                                   *** 
280.
***    For some commands to work properly, your symbol path           *** 
281.
***    must point to .pdb files that have full type information.      *** 
282.
***                                                                   *** 
283.
***    Certain .pdb files (such as the public OS symbols) do not      *** 
284.
***    contain the required information.  Contact the group that      *** 
285.
***    provided you with these symbols if you need this command to    *** 
286.
***    work.                                                          *** 
287.
***                                                                   *** 
288.
***    Type referenced: nt!_KPRCB                                     *** 
289.
***                                                                   *** 
290.
************************************************************************* 
291.
************************************************************************* 
292.
***                                                                   *** 
293.
***                                                                   *** 
294.
***    Either you specified an unqualified symbol, or your debugger   *** 
295.
***    doesn't have full symbol information.  Unqualified symbol      *** 
296.
***    resolution is turned off by default. Please either specify a   *** 
297.
***    fully qualified symbol module!symbolname, or enable resolution *** 
298.
***    of unqualified symbols by typing ".symopt- 100". Note that   *** 
299.
***    enabling unqualified symbol resolution with network symbol     *** 
300.
***    server shares in the symbol path may cause the debugger to     *** 
301.
***    appear to hang for long periods of time when an incorrect      *** 
302.
***    symbol name is typed or the network symbol server is down.     *** 
303.
***                                                                   *** 
304.
***    For some commands to work properly, your symbol path           *** 
305.
***    must point to .pdb files that have full type information.      *** 
306.
***                                                                   *** 
307.
***    Certain .pdb files (such as the public OS symbols) do not      *** 
308.
***    contain the required information.  Contact the group that      *** 
309.
***    provided you with these symbols if you need this command to    *** 
310.
***    work.                                                          *** 
311.
***                                                                   *** 
312.
***    Type referenced: nt!_KPRCB                                     *** 
313.
***                                                                   *** 
314.
************************************************************************* 
315.
************************************************************************* 
316.
***                                                                   *** 
317.
***                                                                   *** 
318.
***    Either you specified an unqualified symbol, or your debugger   *** 
319.
***    doesn't have full symbol information.  Unqualified symbol      *** 
320.
***    resolution is turned off by default. Please either specify a   *** 
321.
***    fully qualified symbol module!symbolname, or enable resolution *** 
322.
***    of unqualified symbols by typing ".symopt- 100". Note that   *** 
323.
***    enabling unqualified symbol resolution with network symbol     *** 
324.
***    server shares in the symbol path may cause the debugger to     *** 
325.
***    appear to hang for long periods of time when an incorrect      *** 
326.
***    symbol name is typed or the network symbol server is down.     *** 
327.
***                                                                   *** 
328.
***    For some commands to work properly, your symbol path           *** 
329.
***    must point to .pdb files that have full type information.      *** 
330.
***                                                                   *** 
331.
***    Certain .pdb files (such as the public OS symbols) do not      *** 
332.
***    contain the required information.  Contact the group that      *** 
333.
***    provided you with these symbols if you need this command to    *** 
334.
***    work.                                                          *** 
335.
***                                                                   *** 
336.
***    Type referenced: nt!_KPRCB                                     *** 
337.
***                                                                   *** 
338.
************************************************************************* 
339.
Probably caused by : ntoskrnl.exe ( nt+78a8a ) 
340.
 
341.
Followup: MachineOwner 
342.
--------- 
343.
 
344.
0: kd> !analyze -v 
345.
******************************************************************************* 
346.
*                                                                             * 
347.
*                        Bugcheck Analysis                                    * 
348.
*                                                                             * 
349.
******************************************************************************* 
350.
 
351.
DRIVER_POWER_STATE_FAILURE (9f) 
352.
A driver has failed to complete a power IRP within a specific time. 
353.
Arguments: 
354.
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp 
355.
	subsystem. 
356.
Arg2: 0000000000000258, Timeout in seconds. 
357.
Arg3: fffffa80069e5b50, The thread currently holding on to the Pnp lock. 
358.
Arg4: fffff80000b9c3d0, nt!TRIAGE_9F_PNP on Win7 and higher 
359.
 
360.
Debugging Details: 
361.
------------------ 
362.
 
363.
***** Kernel symbols are WRONG. Please fix symbols to do analysis. 
364.
 
365.
************************************************************************* 
366.
***                                                                   *** 
367.
***                                                                   *** 
368.
***    Either you specified an unqualified symbol, or your debugger   *** 
369.
***    doesn't have full symbol information.  Unqualified symbol      *** 
370.
***    resolution is turned off by default. Please either specify a   *** 
371.
***    fully qualified symbol module!symbolname, or enable resolution *** 
372.
***    of unqualified symbols by typing ".symopt- 100". Note that   *** 
373.
***    enabling unqualified symbol resolution with network symbol     *** 
374.
***    server shares in the symbol path may cause the debugger to     *** 
375.
***    appear to hang for long periods of time when an incorrect      *** 
376.
***    symbol name is typed or the network symbol server is down.     *** 
377.
***                                                                   *** 
378.
***    For some commands to work properly, your symbol path           *** 
379.
***    must point to .pdb files that have full type information.      *** 
380.
***                                                                   *** 
381.
***    Certain .pdb files (such as the public OS symbols) do not      *** 
382.
***    contain the required information.  Contact the group that      *** 
383.
***    provided you with these symbols if you need this command to    *** 
384.
***    work.                                                          *** 
385.
***                                                                   *** 
386.
***    Type referenced: NT!_ETHREAD                                   *** 
387.
***                                                                   *** 
388.
************************************************************************* 
389.
Implicit thread is now fffffa80`069e5b50 
390.
************************************************************************* 
391.
***                                                                   *** 
392.
***                                                                   *** 
393.
***    Either you specified an unqualified symbol, or your debugger   *** 
394.
***    doesn't have full symbol information.  Unqualified symbol      *** 
395.
***    resolution is turned off by default. Please either specify a   *** 
396.
***    fully qualified symbol module!symbolname, or enable resolution *** 
397.
***    of unqualified symbols by typing ".symopt- 100". Note that   *** 
398.
***    enabling unqualified symbol resolution with network symbol     *** 
399.
***    server shares in the symbol path may cause the debugger to     *** 
400.
***    appear to hang for long periods of time when an incorrect      *** 
401.
***    symbol name is typed or the network symbol server is down.     *** 
402.
***                                                                   *** 
403.
***    For some commands to work properly, your symbol path           *** 
404.
***    must point to .pdb files that have full type information.      *** 
405.
***                                                                   *** 
406.
***    Certain .pdb files (such as the public OS symbols) do not      *** 
407.
***    contain the required information.  Contact the group that      *** 
408.
***    provided you with these symbols if you need this command to    *** 
409.
***    work.                                                          *** 
410.
***                                                                   *** 
411.
***    Type referenced: nt!_ETHREAD                                   *** 
412.
***                                                                   *** 
413.
************************************************************************* 
414.
************************************************************************* 
415.
***                                                                   *** 
416.
***                                                                   *** 
417.
***    Either you specified an unqualified symbol, or your debugger   *** 
418.
***    doesn't have full symbol information.  Unqualified symbol      *** 
419.
***    resolution is turned off by default. Please either specify a   *** 
420.
***    fully qualified symbol module!symbolname, or enable resolution *** 
421.
***    of unqualified symbols by typing ".symopt- 100". Note that   *** 
422.
***    enabling unqualified symbol resolution with network symbol     *** 
423.
***    server shares in the symbol path may cause the debugger to     *** 
424.
***    appear to hang for long periods of time when an incorrect      *** 
425.
***    symbol name is typed or the network symbol server is down.     *** 
426.
***                                                                   *** 
427.
***    For some commands to work properly, your symbol path           *** 
428.
***    must point to .pdb files that have full type information.      *** 
429.
***                                                                   *** 
430.
***    Certain .pdb files (such as the public OS symbols) do not      *** 
431.
***    contain the required information.  Contact the group that      *** 
432.
***    provided you with these symbols if you need this command to    *** 
433.
***    work.                                                          *** 
434.
***                                                                   *** 
435.
***    Type referenced: nt!_TRIAGE_9F_PNP                             *** 
436.
***                                                                   *** 
437.
************************************************************************* 
438.
************************************************************************* 
439.
***                                                                   *** 
440.
***                                                                   *** 
441.
***    Either you specified an unqualified symbol, or your debugger   *** 
442.
***    doesn't have full symbol information.  Unqualified symbol      *** 
443.
***    resolution is turned off by default. Please either specify a   *** 
444.
***    fully qualified symbol module!symbolname, or enable resolution *** 
445.
***    of unqualified symbols by typing ".symopt- 100". Note that   *** 
446.
***    enabling unqualified symbol resolution with network symbol     *** 
447.
***    server shares in the symbol path may cause the debugger to     *** 
448.
***    appear to hang for long periods of time when an incorrect      *** 
449.
***    symbol name is typed or the network symbol server is down.     *** 
450.
***                                                                   *** 
451.
***    For some commands to work properly, your symbol path           *** 
452.
***    must point to .pdb files that have full type information.      *** 
453.
***                                                                   *** 
454.
***    Certain .pdb files (such as the public OS symbols) do not      *** 
455.
***    contain the required information.  Contact the group that      *** 
456.
***    provided you with these symbols if you need this command to    *** 
457.
***    work.                                                          *** 
458.
***                                                                   *** 
459.
***    Type referenced: nt!_KPRCB                                     *** 
460.
***                                                                   *** 
461.
************************************************************************* 
462.
************************************************************************* 
463.
***                                                                   *** 
464.
***                                                                   *** 
465.
***    Either you specified an unqualified symbol, or your debugger   *** 
466.
***    doesn't have full symbol information.  Unqualified symbol      *** 
467.
***    resolution is turned off by default. Please either specify a   *** 
468.
***    fully qualified symbol module!symbolname, or enable resolution *** 
469.
***    of unqualified symbols by typing ".symopt- 100". Note that   *** 
470.
***    enabling unqualified symbol resolution with network symbol     *** 
471.
***    server shares in the symbol path may cause the debugger to     *** 
472.
***    appear to hang for long periods of time when an incorrect      *** 
473.
***    symbol name is typed or the network symbol server is down.     *** 
474.
***                                                                   *** 
475.
***    For some commands to work properly, your symbol path           *** 
476.
***    must point to .pdb files that have full type information.      *** 
477.
***                                                                   *** 
478.
***    Certain .pdb files (such as the public OS symbols) do not      *** 
479.
***    contain the required information.  Contact the group that      *** 
480.
***    provided you with these symbols if you need this command to    *** 
481.
***    work.                                                          *** 
482.
***                                                                   *** 
483.
***    Type referenced: nt!KPRCB                                      *** 
484.
***                                                                   *** 
485.
************************************************************************* 
486.
************************************************************************* 
487.
***                                                                   *** 
488.
***                                                                   *** 
489.
***    Either you specified an unqualified symbol, or your debugger   *** 
490.
***    doesn't have full symbol information.  Unqualified symbol      *** 
491.
***    resolution is turned off by default. Please either specify a   *** 
492.
***    fully qualified symbol module!symbolname, or enable resolution *** 
493.
***    of unqualified symbols by typing ".symopt- 100". Note that   *** 
494.
***    enabling unqualified symbol resolution with network symbol     *** 
495.
***    server shares in the symbol path may cause the debugger to     *** 
496.
***    appear to hang for long periods of time when an incorrect      *** 
497.
***    symbol name is typed or the network symbol server is down.     *** 
498.
***                                                                   *** 
499.
***    For some commands to work properly, your symbol path           *** 
500.
***    must point to .pdb files that have full type information.      *** 
501.
***                                                                   *** 
502.
***    Certain .pdb files (such as the public OS symbols) do not      *** 
503.
***    contain the required information.  Contact the group that      *** 
504.
***    provided you with these symbols if you need this command to    *** 
505.
***    work.                                                          *** 
506.
***                                                                   *** 
507.
***    Type referenced: nt!_KPRCB                                     *** 
508.
***                                                                   *** 
509.
************************************************************************* 
510.
************************************************************************* 
511.
***                                                                   *** 
512.
***                                                                   *** 
513.
***    Either you specified an unqualified symbol, or your debugger   *** 
514.
***    doesn't have full symbol information.  Unqualified symbol      *** 
515.
***    resolution is turned off by default. Please either specify a   *** 
516.
***    fully qualified symbol module!symbolname, or enable resolution *** 
517.
***    of unqualified symbols by typing ".symopt- 100". Note that   *** 
518.
***    enabling unqualified symbol resolution with network symbol     *** 
519.
***    server shares in the symbol path may cause the debugger to     *** 
520.
***    appear to hang for long periods of time when an incorrect      *** 
521.
***    symbol name is typed or the network symbol server is down.     *** 
522.
***                                                                   *** 
523.
***    For some commands to work properly, your symbol path           *** 
524.
***    must point to .pdb files that have full type information.      *** 
525.
***                                                                   *** 
526.
***    Certain .pdb files (such as the public OS symbols) do not      *** 
527.
***    contain the required information.  Contact the group that      *** 
528.
***    provided you with these symbols if you need this command to    *** 
529.
***    work.                                                          *** 
530.
***                                                                   *** 
531.
***    Type referenced: nt!KPRCB                                      *** 
532.
***                                                                   *** 
533.
************************************************************************* 
534.
************************************************************************* 
535.
***                                                                   *** 
536.
***                                                                   *** 
537.
***    Either you specified an unqualified symbol, or your debugger   *** 
538.
***    doesn't have full symbol information.  Unqualified symbol      *** 
539.
***    resolution is turned off by default. Please either specify a   *** 
540.
***    fully qualified symbol module!symbolname, or enable resolution *** 
541.
***    of unqualified symbols by typing ".symopt- 100". Note that   *** 
542.
***    enabling unqualified symbol resolution with network symbol     *** 
543.
***    server shares in the symbol path may cause the debugger to     *** 
544.
***    appear to hang for long periods of time when an incorrect      *** 
545.
***    symbol name is typed or the network symbol server is down.     *** 
546.
***                                                                   *** 
547.
***    For some commands to work properly, your symbol path           *** 
548.
***    must point to .pdb files that have full type information.      *** 
549.
***                                                                   *** 
550.
***    Certain .pdb files (such as the public OS symbols) do not      *** 
551.
***    contain the required information.  Contact the group that      *** 
552.
***    provided you with these symbols if you need this command to    *** 
553.
***    work.                                                          *** 
554.
***                                                                   *** 
555.
***    Type referenced: nt!_KPRCB                                     *** 
556.
***                                                                   *** 
557.
************************************************************************* 
558.
************************************************************************* 
559.
***                                                                   *** 
560.
***                                                                   *** 
561.
***    Either you specified an unqualified symbol, or your debugger   *** 
562.
***    doesn't have full symbol information.  Unqualified symbol      *** 
563.
***    resolution is turned off by default. Please either specify a   *** 
564.
***    fully qualified symbol module!symbolname, or enable resolution *** 
565.
***    of unqualified symbols by typing ".symopt- 100". Note that   *** 
566.
***    enabling unqualified symbol resolution with network symbol     *** 
567.
***    server shares in the symbol path may cause the debugger to     *** 
568.
***    appear to hang for long periods of time when an incorrect      *** 
569.
***    symbol name is typed or the network symbol server is down.     *** 
570.
***                                                                   *** 
571.
***    For some commands to work properly, your symbol path           *** 
572.
***    must point to .pdb files that have full type information.      *** 
573.
***                                                                   *** 
574.
***    Certain .pdb files (such as the public OS symbols) do not      *** 
575.
***    contain the required information.  Contact the group that      *** 
576.
***    provided you with these symbols if you need this command to    *** 
577.
***    work.                                                          *** 
578.
***                                                                   *** 
579.
***    Type referenced: nt!_KPRCB                                     *** 
580.
***                                                                   *** 
581.
************************************************************************* 
582.
************************************************************************* 
583.
***                                                                   *** 
584.
***                                                                   *** 
585.
***    Either you specified an unqualified symbol, or your debugger   *** 
586.
***    doesn't have full symbol information.  Unqualified symbol      *** 
587.
***    resolution is turned off by default. Please either specify a   *** 
588.
***    fully qualified symbol module!symbolname, or enable resolution *** 
589.
***    of unqualified symbols by typing ".symopt- 100". Note that   *** 
590.
***    enabling unqualified symbol resolution with network symbol     *** 
591.
***    server shares in the symbol path may cause the debugger to     *** 
592.
***    appear to hang for long periods of time when an incorrect      *** 
593.
***    symbol name is typed or the network symbol server is down.     *** 
594.
***                                                                   *** 
595.
***    For some commands to work properly, your symbol path           *** 
596.
***    must point to .pdb files that have full type information.      *** 
597.
***                                                                   *** 
598.
***    Certain .pdb files (such as the public OS symbols) do not      *** 
599.
***    contain the required information.  Contact the group that      *** 
600.
***    provided you with these symbols if you need this command to    *** 
601.
***    work.                                                          *** 
602.
***                                                                   *** 
603.
***    Type referenced: nt!_KPRCB                                     *** 
604.
***                                                                   *** 
605.
************************************************************************* 
606.
************************************************************************* 
607.
***                                                                   *** 
608.
***                                                                   *** 
609.
***    Either you specified an unqualified symbol, or your debugger   *** 
610.
***    doesn't have full symbol information.  Unqualified symbol      *** 
611.
***    resolution is turned off by default. Please either specify a   *** 
612.
***    fully qualified symbol module!symbolname, or enable resolution *** 
613.
***    of unqualified symbols by typing ".symopt- 100". Note that   *** 
614.
***    enabling unqualified symbol resolution with network symbol     *** 
615.
***    server shares in the symbol path may cause the debugger to     *** 
616.
***    appear to hang for long periods of time when an incorrect      *** 
617.
***    symbol name is typed or the network symbol server is down.     *** 
618.
***                                                                   *** 
619.
***    For some commands to work properly, your symbol path           *** 
620.
***    must point to .pdb files that have full type information.      *** 
621.
***                                                                   *** 
622.
***    Certain .pdb files (such as the public OS symbols) do not      *** 
623.
***    contain the required information.  Contact the group that      *** 
624.
***    provided you with these symbols if you need this command to    *** 
625.
***    work.                                                          *** 
626.
***                                                                   *** 
627.
***    Type referenced: nt!_KPRCB                                     *** 
628.
***                                                                   *** 
629.
************************************************************************* 
630.
 
631.
ADDITIONAL_DEBUG_TEXT:   
632.
You can run '.symfix; .reload' to try to fix the symbol path and load symbols. 
633.
 
634.
MODULE_NAME: nt 
635.
 
636.
FAULTING_MODULE: fffff80003218000 nt 
637.
 
638.
DEBUG_FLR_IMAGE_TIMESTAMP:  531590fb 
639.
 
640.
DRVPOWERSTATE_SUBCODE:  4 
641.
 
642.
FAULTING_THREAD:  fffffa80069e5b50 
643.
 
644.
CUSTOMER_CRASH_COUNT:  1 
645.
 
646.
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT 
647.
 
648.
BUGCHECK_STR:  0x9F 
649.
 
650.
CURRENT_IRQL:  0 
651.
 
652.
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre 
653.
 
654.
LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80003290a8a 
655.
 
656.
STACK_TEXT:   
657.
fffff880`035caac0 00000000`00000000 : 00000000`0000000f 00000000`00000000 ffffe259`6d969c61 00000000`00000000 : nt+0x78a8a 
658.
 
659.
 
660.
STACK_COMMAND:  .thread 0xfffffa80069e5b50 ; kb 
661.
 
662.
FOLLOWUP_IP:  
663.
nt+78a8a 
664.
fffff800`03290a8a 488d8c2400010000 lea     rcx,[rsp+100h] 
665.
 
666.
SYMBOL_STACK_INDEX:  0 
667.
 
668.
SYMBOL_NAME:  nt+78a8a 
669.
 
670.
FOLLOWUP_NAME:  MachineOwner 
671.
 
672.
IMAGE_NAME:  ntoskrnl.exe 
673.
 
674.
BUCKET_ID:  WRONG_SYMBOLS 
675.
 
676.
FAILURE_BUCKET_ID:  WRONG_SYMBOLS 
677.
 
678.
ANALYSIS_SOURCE:  KM 
679.
 
680.
FAILURE_ID_HASH_STRING:  km:wrong_symbols 
681.
 
682.
FAILURE_ID_HASH:  {70b057e8-2462-896f-28e7-ac72d4d365f8} 
683.
 
684.
Followup: MachineOwner 
685.
--------- 
686.
 
687.
0: kd> lmvm nt 
688.
start             end                 module name 
689.
fffff800`03218000 fffff800`037fd000   nt       T (no symbols)            
690.
    Loaded symbol image file: ntoskrnl.exe 
691.
    Image path: \SystemRoot\system32\ntoskrnl.exe 
692.
    Image name: ntoskrnl.exe 
693.
    Timestamp:        Tue Mar 04 09:38:19 2014 (531590FB) 
694.
    CheckSum:         00554C03 
695.
    ImageSize:        005E5000 
696.
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Bitte warten ..
Mitglied: killtec
23.10.2014 um 14:47 Uhr
Ok Thomas,
du meinst also ich sollte einen neuen kaufen? Trotz dass dieser an einem anderem Rechner mit der gleichen Software funktioniert? (OS + Putty)

Gruß
Bitte warten ..
Mitglied: keine-ahnung
23.10.2014 um 15:03 Uhr
du meinst also ich sollte einen neuen kaufen?
Nur, wenn Du den Ärger mit diesem Taiwan-Müll nicht mehr haben willst - mitunter hält so ein mehrtägiges troubleshooting ja auch munter .

LG, Thomas
Bitte warten ..
Mitglied: killtec
23.10.2014 um 15:46 Uhr
Evtl. noch einen anderen Adapter zur Auswahl?

Gruß
Bitte warten ..
Mitglied: killtec
24.10.2014 um 11:38 Uhr
Hi Thomas,
was hälst du von dem?
http://de.rs-online.com/web/p/product/6877806/?grossPrice=Y&cm_mmc= ...

der hat den gleichen FTDI - Chip (FTDI FT232R) den der Adapter von dir hat.

Gruß
Bitte warten ..
Mitglied: keine-ahnung
24.10.2014 um 12:36 Uhr
Moin nochmal,
was hälst du von dem?
kommt das von Hals oder von Halten ? Kenne ich nicht - wenn ich etwas wirklich benötige, kaufe ich bei Herstellern, die für Qualität und - nicht zu vergessen - Support bekannt sind.

LG, Thomas
Bitte warten ..
Mitglied: killtec
24.10.2014 um 13:04 Uhr
Hi,
natürlich meinte ich hältst du von dem
Ich kenne das W&T nicht. Ich weiß auch nicht in wie weit ich da bestellen kann. Bei den Anderen habe ich ein Konto von der Fa. her. Daher dachte ich wenn es der gleiche Chip ist, sollte das doch gehen oder?

Gruß
Bitte warten ..
Mitglied: aqui
24.10.2014 um 21:31 Uhr
Ich habe auch schon den aktuellsten Treiber geladen.
Hast du den Treiber direkt von der Prolific Website ?? Den solltest du auch verwenden...
http://www.prolific.com.tw/us/showproduct.aspx?p_id=225&pcid=41

Ansonsten ggf. mal mit http://www.nirsoft.net/utils/usb_devices_view.html debuggen.
Bitte warten ..
Mitglied: killtec
27.10.2014 um 08:16 Uhr
Hi Aqui,
ja, den habe ich direkt von deren Seite.
Ich schaue mir das Debugging aber auch noch mal an.

Gruß
Bitte warten ..
Mitglied: hildefeuer
28.10.2014 um 19:47 Uhr
Ich habe den gleichen blauen Prolific usb to rs232 Adapter. Meiner lauft unter Win7HP7/64. Habe allerdings damals den Vista64 Treiber installiert. (PL2303_Vista_Installer.exe 1811kb) Der Win7 von der Taiwan webside geht nicht.
Bitte warten ..
Ähnliche Inhalte
Peripheriegeräte
USB zu RS232 Converter
Erfahrungsbericht von KuemmelPeripheriegeräte45 Kommentare

Hallo Kollegen, ich möchte gerne meine Erfahrungen mit den sogenannten USB to RS232 Converter mit euch teilen. Die einen ...

LAN, WAN, Wireless
Gibt es USB zu WLAN Adapter?
Frage von grkaLAN, WAN, Wireless3 Kommentare

Hallo, ich habe ein Gerät das ein USB Kabel hat und im PC als Serieller COM Port in der ...

Peripheriegeräte
Seriell auf USB Adapter
Frage von Coachi81Peripheriegeräte16 Kommentare

Hallo, zum konfigurieren einer Sprechstelle muss ich über die serielle Schnittstelle meines PCs auf die USB Schnittstelle der Sprechstelle ...

Festplatten, SSD, Raid
SAS auf USB-Adapter?
gelöst Frage von anteNopeFestplatten, SSD, Raid17 Kommentare

Hallo zusammen, SATA auf USB-Adapter gibt es ja zu Häuf, aber kennt jemand einen SAS auf USB-Adapter? Bin da ...

Neue Wissensbeiträge
Perl

Perl hat heute Geburtstag: 30 Jahre Perl: Lange Gesichter zum Geburtstag

Information von Penny.Cilin vor 7 StundenPerl2 Kommentare

Hallo, auch wenn es wenige wissen und noch weniger Leute es nutzen. Perl hat heute Geburtstag. 30 Jahre Perl ...

Sicherheit

Blackberry stirbt - Keine Updates für Priv mehr

Tipp von certifiedit.net vor 7 StundenSicherheit1 Kommentar

Blackberry wird zu einer 08/15 Firma und geht wohl mehr und mehr den Weg, den HTC schon ging. Von ...

Windows 10

Autsch: Microsoft bündelt Windows 10 mit unsicherer Passwort-Manager-App

Tipp von kgborn vor 2 TagenWindows 1011 Kommentare

Unter Microsofts Windows 10 haben Endbenutzer keine Kontrolle mehr, was Microsoft an Apps auf dem Betriebssystem installiert (die Windows ...

Sicherheits-Tools

Achtung: Sicherheitslücke im FortiClient VPN-Client

Tipp von kgborn vor 2 TagenSicherheits-Tools

Ich weiß nicht, wie häufig die NextGeneration Endpoint Protection-Lösung von Fortinet in deutschen Unternehmen eingesetzt wird. An dieser Stelle ...

Heiß diskutierte Inhalte
Batch & Shell
Kann man mit einer .txt Datei eine .bat Datei öffnen?
gelöst Frage von HelloWorldBatch & Shell22 Kommentare

Wie schon im Titel beschrieben würde ich gerne durch einfaches klicken auf eine Text oder Word Datei eine Batch ...

Netzwerkgrundlagen
Belibiges Teilnetz einer Subnetzmaske rausfinden?
gelöst Frage von CenuzeNetzwerkgrundlagen18 Kommentare

Wundervollen Gutentag, mittlerweile kann ich Subnetting so einigermaßen, aber ein Problem habe ich noch. Netzwerkadresse und Boradcast errechnen ist ...

LAN, WAN, Wireless
WLAN Reichweite erhöhen mit neuer Antenne
gelöst Frage von gdconsultLAN, WAN, Wireless12 Kommentare

Hallo, ich besitze einen TL-WN722N USB-WLAN Dongle mit einer richtigen Antenne. Ich frage mich jetzt ob man die Reichweite ...

Windows Server
Logging von "gesendeten Nachrichten" auf Terminalservern
gelöst Frage von Z3R0C0MM4N0THiN6Windows Server10 Kommentare

Hallo zusammen, kann mir jemand auf kurzem Wege sagen ob 1) die per Task-Manager (oder damals tsadmin) an Benutzer ...