Vorschau drücken, Bluescreen bekommen - Systemabsturz 
Autore: Rüdiger R.Hallo!
Ich habe Website Evolution X5 10 gekauft, nachdem ich bereits positive Erfahrungen mit Website Evolution X5 8 sowie 9 gemacht habe.
Bei der aktuellen Version jedoch, stürzt der Rechner sobald ich "Vorschau" drücke ab. Es erscheint ein Bluescreen (screen of death) und der Rechner wird dann neugestartet.
Hier ein Auszug aus der Dump-Datei die Windows erstellt. (Leider kann ich die 700MB Dump Datei hier nicht uploaden) Ich verwende Windows 7 64bit auf einer SSD-Festplatte.
################################################################ *******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff8800ca715e0, 0, 0}
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for tdx.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for kl1.sys
***** 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 ***
*** ***
*************************************************************************
Probably caused by : tdx.sys ( tdx+164c5 )
) ###############################################################
Wie kann ich das Problem beheben bzw. wann wird es einen Patch für dieses Problem geben?
Vielen Dank!
bei win7 ein Bluescreen...das kommt alle paar jahre mal vor....
stürzt er immer ab - auch bei einem leeren Projekt?
vermutlich stimmt was an deinem windows nicht.
Autore
Danke für die zügige Antwort.
Ich habe ein leeres Projekt erstellt. Dieses erzeugt auch eine Vorschau, ohne dabei ein Bluescreen oder Systemabsturz zu erzeugen, jedoch ist die Vorschau leer - eine weiße Seite.
Autore
Unter der Einschränkung: wenn ich automatische Vorschau unter Einstellungen aktiviere, und dann auf Vorschau drücke, tritt der Fall aus meinem 1. Beitrag ein: Vorschau drücken, Bluescreen erhalten.
deinstalliere mal Kaspersky....