Win8 Pro 64 - Bluescreen Ursache

D

djducky

Neuling
Thread Starter
Mitglied seit
25.01.2013
Beiträge
15
Ihr Lieben,

Kann jemand damit was anfangen?



Rechts unten sieht man auch, dass nach dem reboot die Symbole für die Festplatten nicht mehr richtig sind, das erste Symbol z.B. müsste so aussehen:

http://cdn.windows8beta.com/wp-content/images/2012/02/Windows_8_drive_icon.jpg

Danke erstmal. :)

PS: Auf meiner Platte sind plötzlich ca. 6GB mehr belegt?

Edit: nach noch nem reboot sind die richtigen Symbole wieder da.

---------- Post added at 23:09 ---------- Previous post was at 22:59 ----------

Hier noch mehr Infos:


System:
i5 3470
Thermalright Macho
Corsair Vengeance LP 1600
HD 7870 PCS+
ASRock Z77 Pro3
Crucial M4 128GB
Seagate Barracuda 2TB
 
Zuletzt bearbeitet:
Wenn Du diese Anzeige nicht sehen willst, registriere Dich und/oder logge Dich ein.
Also, das sind alles mir völlig unbekannte symbole.
Du hast doch nicht etwa irgendein Tool installiert was das wunderbare windows8 verändert und fragst jetzt hier nach was das Problem verursacht?
 
Zuletzt bearbeitet:
Erst einmal danke für die Antwort, auch wenn ein latenter Vorwurf drinhängt. ;)

Ich habe lediglich die *.ico-Dateien für meine Programme mit Windows-Bordmitteln geändert, eine Verknüpfung zum Papierkorb angelegt, damit ich ihn in der Taskleiste sehe sowie ClassicShell installiert für das Startmenü. Zudem läuft das seit fast 2 Wochen problemlos mit ClassicShell. Das rechts unten ist auch nur die Arbeitsplatz-Leiste, deren Symbole eben nach dem ersten Reboot nicht mehr korrekt waren. Im zweiten Bild sieht man, wie es aussehen sollte.

Wenn du einen echten Anhaltspunkt hast, dass ClassicShell das Problem verursachen könnte, dann bin ich für jeden Hinweis dankbar. Ansonsten würde ich mich fteuen, wenn man das ggf. anhand meiner Screenshots heraus finden könnte. Ich gebe auch gerne weitere Informationen her.


Von links nach rechts (erster Screenshot):
ClassicShell-Startknopf, Papierkorb, Windows-Explorer, Firefox, Opera, Thunderbird, Ereignisanzeige, Systemsteuerung, Taskmanager, Sandboxie --- Freiraum --- Arbeitsplatz
 
Zuletzt bearbeitet:
sowie ClassicShell installiert
Zum Vergrößern anklicken....
ja und damit bin ich hier rauß.
Deinstallieren den Mist oder Windows 8 neuinstallieren/ reparieren,
und wenn du so einen MIst unbedingt nutzen willst, dann wende dich an ClassicShell Foren oder den Entwickler direkt.

An deinen Screens kann man nur erkennen das Windows ein Problem meldet.
Und noch den Hinweis auf Aplication, was ja wohl klar ist.

Fast alle Problemthreads hier in Win8 Bereich handeln von Usern welche solche Tools installiert haben.
Oder andere Programme und Spiele welche nicht für Win8 gemacht sind und kaum ein anderer installiert.
 
Zuletzt bearbeitet:
Entschuldige bitte, aber muss man gleich so unfreundlich sein?

Ich habe mir auch die Mühe gemacht, den Bluescreen zu analysieren:

 
Danke, dass du dran bleibst. ;)

Uff... ich würde ClassicShell schon deinstallieren, wenn es denn wirklich daran liegt. Das will ich ja hier heraus finden. Zudem ist der BSOD erst einmal aufgetreten, ich möchte ja nur weitere Probleme vermeiden.

Beim refresh: verstehe ich das richtig, dass all meine installierten Programme erhalten bleiben?

Hier mal, was das Windows debug tool sagt, klingt wirklich nach irgendwelchen Symbolsachen:
Code: 
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\012513-9250-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 8 Kernel Version 9200 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
Machine Name:
Kernel base = 0xfffff800`e1a09000 PsLoadedModuleList = 0xfffff800`e1cd3a80
Debug session time: Fri Jan 25 22:37:34.621 2013 (UTC + 1:00)
System Uptime: 2 days 1:32:13.263
*********************************************************************
* 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
............................................
*** WARNING: Unable to verify timestamp for watchdog.sys
*** ERROR: Module load completed but symbols could not be loaded for watchdog.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 119, {1, c223a7, c223a9, c223a6}

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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 : watchdog.sys ( watchdog+255d )

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

Eine Lösung wird hier angeboten, allerdings verwirrt mich der Buchstabe e:\ in der Angabe, die man setzen soll. Warum nicht c:\ ?

---------- Post added at 01:42 ---------- Previous post was at 01:24 ----------

Und das sagt die MEMORY.dmp:

Code: 
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Daniel\Desktop\MEMORY.DMP]
Kernel Bitmap 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 8 Kernel Version 9200 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
Machine Name:
Kernel base = 0xfffff800`e1a09000 PsLoadedModuleList = 0xfffff800`e1cd3a80
Debug session time: Fri Jan 25 22:37:34.621 2013 (UTC + 1:00)
System Uptime: 2 days 1:32:13.263
*********************************************************************
* 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

Loading unloaded module list
............................................
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for watchdog.sys - 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 119, {1, c223a7, c223a9, c223a6}

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for dxgmms1.sys - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for dxgkrnl.sys - 
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Page 2189bc not present in the dump file. Type ".hh dbgerr004" for details
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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 : dxgmms1.sys ( dxgmms1+70b2 )

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

Ohjeh, der RAM... Woanders vermutet jemanden den VRAM bzw. die Treiber. hatte mit Catalyst 13.1 auch Probleme mit Firefox und der hardwarebeschleunigung:

 
Zuletzt bearbeitet:
ich würde ClassicShell schon deinstallieren, wenn es denn wirklich daran liegt. Das will ich ja hier heraus finden. Zudem ist der BSOD erst einmal aufgetreten, ich möchte ja nur weitere Probleme vermeiden.
Zum Vergrößern anklicken....
also übervorsichtiger.
ein BSOD macht noch keinen zerstörten PC, also abwarten.
Ansonsten musst du selbst entscheiden was du machen willst und was schnell geht.
Die ein klick, eine Sekunde Lösung wird es nicht geben.

Wiederherstellungspunkt auswählen.
Programme Tools deinstallieren welche nicht jeder verwendet.
ich verwende schon aus deine Aufzählung oben mindestens 3 nicht und kann nicht sagen ob diese immer mit Win 8 laufen.
Windows Refresh oder Neuinstallation

Na klar nicht übertakten.
und wenn das alles nichts bringt Hardware testen Memtest usw.
 
Zuletzt bearbeitet:
Memtest werde ich wohl machen, ich frage mich aber, ob du aus den Absturzberichten selbst schlau wirst. Vram würde mich nicht wundern, ich hatte ja die gezeigten Darstellungsfehler.

naja, was heißt übervorsichtig... ich hatte diese Probleme und jetzt bekomme ich einen BSOD, hatte ich in zwei jahren Win7 noch nie.

Ohjeh, ich muss schlafen :(
 
Was sagen schon Absturzberichte.
Die kann man ja höchstens mit XP vergleichen.
Wer hat den mit Win8 Bluescreens, es gibt da keine Seiten im Web wo man die Ursache ablesen kann wie bei XP.
Selbst da kamen immer mehrere Möglichkeiten in Frage.

Da steht doch genug Text in den Berichten.
Problem mit dem Symbolen.
Und ich vermute ClassicShell oder irgendein anderes Tool was symbole verändert oder installiert.
Kann ja hier nie einer sehen was so alles auf dem PC rumschwirrt an Müll.
 
Zuletzt bearbeitet:
Naja, ich werde mal memtest versuchen. Mit der Grafikkarte hatte ich halt schon Probleme mit Firefox, deshalb ist das ja nicht soooo weit hergeholt. Okay, ich muss aber echt mal ins Bett. danke erstmal bis hierhin..
 
Okay, 10 Stunden Memtest ohne einen Fehler...

Langsam haben ich und andere den GraKa-Treiber in verdacht. Evtl. ist der einfach noch nicht besonders gut.
 
Zuletzt bearbeitet:
Die im Memory.dmp genannte dxgmms1.sys gehört zu DirectX. Naheliegend ist daher ein Problem mit der Grafikkarte. Ich würde mal den AMD Catalyst deinstallieren und wieder neu installieren.
 
thb schrieb:
Die im Memory.dmp genannte dxgmms1.sys gehört zu DirectX. Naheliegend ist daher ein Problem mit der Grafikkarte. Ich würde mal den AMD Catalyst deinstallieren und wieder neu installieren.
Zum Vergrößern anklicken....

Ja, vermute ich auch... jetzt ist halt die Frage, wie genau ich das so rausfinden kann, da ich den BSOD ja nicht reproduzieren kann. Im Ersten beitrag erwähnte ich ja, dass ich mit 13.1 starke Anzeigebugs unter Firefox mit aktivierter Hardwarebeschleunigung hatte (lila Kachelmuster). Jetzt mit 12.10 kommen ab und zu mal ganz minimale Bugs - ganz feine schleifenförmige Streifchen überm vor/zurück Knopf und ein dünner lila querstreifen über der Adressleiste. Anyway, ich mach mal wie du vorschlägst und teste dann mal wieder 13.1.

Und dazu muss ich sagen: In Spielen und sonstigen 3D-Anwendungen gibt es keine Probleme.

PS: hat jemand ne Ahnung, warum nach dem BSOD 6GB mehr belegt sind auf meiner Systemplatte?

---------- Post added at 14:28 ---------- Previous post was at 13:35 ----------

13.1 installiert und da sind sie wieder, meine geliebten Anzeigebugs unter Firefox mit Hardwarebeschleunigung:



Edit: Chrome mit hardwarebeschleunigung zeigt keine Fehler, Spiele (Dirt Showdown) auch nicht. GGf. ist das Ganze einfach ne Inkompatibilität von Firefox im Zusammenspiel mit Catalyst und Win8, was hoffentlich bald bereinigt wird. Firefox lieft auch beim BSOD, ich habe da jetzt einfach mal die GPU-Beschleunigung wieder ausgestellt. Evtl. hilft ja das nächste FF-Update oder der nächste Catalyst.

Ich möchte Euch für die Vorschläge bis hierhin danken. Vielleicht fällt Euch ja noch was ein, dann würde ich mich freuen. Ansonsten ist es wohl erstmal wie es ist.
 
Zuletzt bearbeitet:
Hast DU den 13.1er mal NEU von AMD geladen? Es gab letzte Woche bei AMD in dem ersten Rel. der 13.1er einen Packfehler! Die neue 13.1er Version ist auch ein paar Bytes größer! Ggfs. liegt es daran! Mal ganz neu laden!
 
Hallo Tekkno_Frank,

Danke für deine Antwort. Ich habe den 13.1 neu geladen und beim FF nach wie vor die Bildfehler. Deshalb habe ich Hardwarebeschleunigung im Fuchs erst einmal deaktiviert und hoffe auf das nächste Update von FF oder Catalyst. Bisher ist auch kein Bluescreen mehr aufgetreten. :)

PS:
Die Verbindungsfehler zum Monitor nach Standby oder Beenden von Spielen etc., die ich auch hatte, lagen wohl am Monitor. Ich habe hier ein anderes Exemplar meines Dell und der tut, was er soll.

Falls wieder was schief läuft, melde ich mich hier. :d
 
Anmelden, um zu antworten.
Hardwareluxx setzt keine externen Werbe- und Tracking-Cookies ein. Auf unserer Webseite finden Sie nur noch Cookies nach berechtigtem Interesse (Art. 6 Abs. 1 Satz 1 lit. f DSGVO) oder eigene funktionelle Cookies. Durch die Nutzung unserer Webseite erklären Sie sich damit einverstanden, dass wir diese Cookies setzen. Mehr Informationen und Möglichkeiten zur Einstellung unserer Cookies finden Sie in unserer Datenschutzerklärung.


Zurück
Oben Unten refresh