Hinweise


Willkommen

Navigation


Partner Links

 
Antwort Themen-Optionen Ansicht
Ungelesen 08.06.10, 21:24   #1
Benutzerbild von Striker2006_archive
Mitglied seit: Mar 2009
Beiträge: 0
Striker2006_archive ist offline
Striker2006_archive
Ich brauche keinen Titel
 
BlueScreen schon das 3mal !!!

Hallo und zwar habe ich heute zum 3ten mal ein Bluescreen bekommen !!!!!

Und zwar stand das im Debug: Habe auch schon bei google gesucht allerdings nichts gefunden:

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


Loading Dump File [C:\Windows\Minidump\Mini060810-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 Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`01a14000 PsLoadedModuleList = 0xfffff800`01bd8dd0
Debug session time: Tue Jun 8 19:34:52.172 2010 (UTC + 2:00)
System Uptime: 0 days 1:21:29.299
************************************************** *******************
* 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, {fffffa806b605cee, c, 1, fffff80001a71e4e}

Unable to load image \SystemRoot\system32\DRIVERS\NETw5v64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5v64.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 ***
*** ***
************************************************** ***********************
Probably caused by : NETw5v64.sys ( NETw5v64+8da4d )

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

Mit Zitat antworten Beitrag melden
   
Ungelesen 08.06.10, 21:50   #2 Top
Benutzerbild von uwe1590_archive
Mitglied seit: Dec 2008
Beiträge: 0
uwe1590_archive ist offline
uwe1590_archive
Member
 
BlueScreen schon das 3mal !!!

Als erstes würde ich Vorschlagen, aktualisiere mal den Treiber der Netzwerkkarte/W-Lankarte

 

COMPUTER ARBEITEN BINAER: ENTWEDER SIE FUNKTIONIEREN ODER SIE SIND KAPUTT
Mit Zitat antworten Beitrag melden
   
Ungelesen 09.06.10, 00:47   #3 Top
Benutzerbild von Striker2006_archive
Threadstarter
Mitglied seit: Mar 2009
Beiträge: 0
Striker2006_archive ist offline
Striker2006_archive
Ich brauche keinen Titel
 
BlueScreen schon das 3mal !!!

ja habe ich gemacht lol !!! und bisher geht es danke UWE !!!!

Mit Zitat antworten Beitrag melden
   
Ungelesen 09.06.10, 22:55   #4 Top
Benutzerbild von uwe1590_archive
Mitglied seit: Dec 2008
Beiträge: 0
uwe1590_archive ist offline
uwe1590_archive
Member
 
BlueScreen schon das 3mal !!!

Zitat:
Zitat von Striker2006 Beitrag anzeigen
ja habe ich gemacht lol !!! und bisher geht es danke UWE !!!!
War ja nahe liegend.

 

COMPUTER ARBEITEN BINAER: ENTWEDER SIE FUNKTIONIEREN ODER SIE SIND KAPUTT
Mit Zitat antworten Beitrag melden
   
Antwort


 

Ähnliche Themen
Thema Forum
BlueScreen BcCode 19 Windows 7


Themen-Optionen
Ansicht



Jetzt registrieren


Registrieren | Forum-Mitarbeiter | Kontakt | Nutzungsbedingungen | Archiv

Alle Zeitangaben in WEZ +2. Es ist jetzt 17:22 Uhr.

All trademarks are the property of their respective owners.
Copyright ©2019 Boerse.IM/AM/IO/AI



().