Beiträge von Dstyle

    Hey leute, ich bin gerade an diesem Befehl ausführen um zu checken ob noch alles bei meinem XP in Ordnung ist. sfc /Scannow

    Jezt verlangt aber Windows die XP Professional CD, obschon ich die Windows Home Edition habe SP 2. An was liegt das? Ich habe auch keine Raubkopie, sondern die Original samt Key Windows XP.

    Marvman4 simpson, ich habe mal diesen scan gemacht, und dann forderte es mich auf, das ich die windows xp professional cd soll einlegen. ich habe aber das home installiert, verlangt aber ausdrücklich nach der professional. gibt es eine andere vorgehensweise? also es zeigt mir an, das etwas mit den dll nicht in ordnung ist. und muss ich eigentlich den pc runterfahren und dann neu booten mit der cd drinn oder kann ich das auf windows ebene machen=?

    Hey leute, ja ich habe ein AntiVirus :D und auch schön übers system gelassen. ICh hatte ein Defektes RAM bei mir im PC und dann kamen dauerd Bluescreens. Als ich danach einige Progis unteranderem Ewido-anti-Malware übers system laufen liess kam eben eine Fehlermeldung.

    Hey leute ich habe ein Problem:

    Als ich den ewido anti-malware und a-squared über mein system lief kam jeweils folgende meldung:


    SecuritySuite.exe ist beschädigt

    Die Datei oder das Verzeichniss C:/Programme/Gemeinsame Dateien/Real/RCAPlugins/usiy3201.dll ist beschädigt und nicht lesbar, bitte CHKDSK ausführen.

    Beim ewido kam ne ähnliche Meldung, jedoch war es nicht genau dieser Pfad.

    An was liegt das, habe CHKDSK unter windows ausgeführt, ging aber so schnell und fand keine Fehler. Wie kann ich dieses Problem lösen?

    Hey leute, ich habe in letzter zeit sehr viele Probleme mit meinem pc gibt dauernd bluescreens, nach langem Suchen fand ich heraus, das es die RAM's waren die defekt sind. Bin aber ein wenig skeptisch ob es wirklich nur die RAM's waren. Gibt es daher eine Software die zb. den Prozessor, Graka und das Mainboard auf defekte überprüft?

    danke

    Hey leute da eines meiner RAM den Geist aufgegeben hatt, muss ich mir ein neues kaufen. Möchte aber anstatt 2 riegel an je 512mb ein riegel von 1gb kaufen. Habe mal gehört das es so weniger konflikte gibt. Meine Frage ist nun, was für ein RAM kann ich für mein Mainboard kaufen?

    also ich habe gerdae bemerkt, das der pc beim zocken abstürzt. liegt das nun an der graka,oder am ram`? denn auf einmal konnte ich das selbe game nicht mehr auf der höchsten auflösung gamen. und immer wenn mir die kiste abstürtz meldet spy boot kernel default cheked

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


    Loading Dump File [C:\WINDOWS\Minidump\Mini041306-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 ntoskrnl.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
    Debug session time: Thu Apr 13 09:25:27.218 2006 (GMT+2)
    System Uptime: 0 days 0:14:31.822
    *********************************************************************
    * 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 ntoskrnl.exe, Win32 error 2
    *** 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
    ...........
    Unable to load image Ntfs.sys, Win32 error 2
    *** WARNING: Unable to verify timestamp for Ntfs.sys
    *** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
    ERROR: FindPlugIns 8007007b
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 24, {1902fe, b0dae350, b0dae04c, 804f7242}

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

    *** WARNING: Unable to verify timestamp for sr.sys
    *** ERROR: Module load completed but symbols could not be loaded for sr.sys
    *** WARNING: Unable to verify timestamp for avgntmgr.sys
    *** ERROR: Module load completed but symbols could not be loaded for avgntmgr.sys
    *** WARNING: Unable to verify timestamp for PQV2i.sys
    *** ERROR: Module load completed but symbols could not be loaded for PQV2i.sys
    Probably caused by : Ntfs.sys ( Ntfs+32180 )

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

    32-bit Kernel triage dump: C:\WINDOWS\Minidump\Mini041306-01.dmp
    command line: '"C:\Programme\Debugging Tools for Windows\windbg.exe" ' Debugger Process 0xD88
    dbgeng: image 6.6.0003.5, built Thu Jan 19 00:06:52 2006
    [path: C:\Programme\Debugging Tools for Windows\dbgeng.dll]
    dbghelp: image 6.6.0003.5, built Thu Jan 19 00:06:37 2006
    [path: C:\Programme\Debugging Tools for Windows\dbghelp.dll]
    DIA version: 51108
    Extension DLL search Path:
    C:\Programme\Debugging Tools for Windows\winext;C:\Programme\Debugging Tools for Windows\winext\arcade;C:\Programme\Debugging Tools for Windows\WINXP;C:\Programme\Debugging Tools for Windows\pri;C:\Programme\Debugging Tools for Windows;C:\Programme\Debugging Tools for Windows\winext\arcade;C:\WINDOWS\SYSTEM32;C:\WINDOWS;C:\WINDOWS\SYSTEM32\WBEM;C:\PROGRAMME\GEMEINSAME DATEIEN\ULEAD SYSTEMS\MPEG;C:\PROGRA~1\THRIXXX\3D SEXVILLA;G:\PROGRA~1\THRIXXX\3D SEXVILLA;C:\PROGRAMME\ATI TECHNOLOGIES\ATI CONTROL PANEL;C:\PROGRAMME\GEMEINSAME DATEIEN\GTK\2.0\BIN;C:\Programme\Panda Software\Panda Platinum 2005 Internet Security\;C:\Programme\QuickTime\QTSystem\;"C:\Programme\Symantec\Norton Ghost 2003\";C:\Programme\ATI Technologies\ATI.ACE\
    Extension DLL chain:
    dbghelp: image 6.6.0003.5, API 6.0.6, built Thu Jan 19 00:06:37 2006
    [path: C:\Programme\Debugging Tools for Windows\dbghelp.dll]
    ext: image 6.6.0003.5, API 1.0.0, built Thu Jan 19 00:06:08 2006
    [path: C:\Programme\Debugging Tools for Windows\winext\ext.dll]
    exts: image 6.6.0003.5, API 1.0.0, built Thu Jan 19 00:06:06 2006
    [path: C:\Programme\Debugging Tools for Windows\WINXP\exts.dll]
    kext: image 6.6.0003.5, API 1.0.0, built Thu Jan 19 00:06:10 2006
    [path: C:\Programme\Debugging Tools for Windows\winext\kext.dll]
    kdexts: image 6.0.5278.0, API 1.0.0, built Thu Jan 19 00:20:33 2006
    [path: C:\Programme\Debugging Tools for Windows\WINXP\kdexts.dll]
    kd> !analyze –v
    ERROR: FindPlugIns 8007007b
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 24, {1902fe, b0dae350, b0dae04c, 804f7242}

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

    Probably caused by : Ntfs.sys ( Ntfs+32180 )

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


    Was sagst du zu dem?

    @ yoyo, also hast du mir vll eine anleitung? ich habe nun probier chkdsk /r auszuführen, kam aber die meldung, das das aktuelle nfts system nicht gesperrt werden kann. und ob ich eine überprüfung beim nächsten systemstart möchte. habe mal ja gedrückt.

    Was meinst du mit der wiederherstellungskonsole?

    ich habe jetzt mal ein debugger progi laufen lassen, und ese kam das heraus.


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


    Loading Dump File [C:\Dokumente und Einstellungen\All Users\Anwendungsdaten\Microsoft\Dr Watson\user.dmp]
    User Mini Dump File: Only registers, stack and portions of memory are available

    Comment: 'Dr. Watson generated MiniDump'
    Windows XP Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: SingleUserTS Personal
    Debug session time: Fri Mar 24 19:27:47.000 2006 (GMT+2)
    System Uptime: not available
    Process Uptime: 0 days 0:00:38.000
    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:
    .....................................................................................
    This dump file has an exception of interest stored in it.
    The stored exception information can be accessed via .ecxr.
    (8c0.c7c): Access violation - code c0000005 (first/second chance not available)
    eax=00000008 ebx=00000000 ecx=ffffffff edx=00000000 esi=00000000 edi=00000011
    eip=005b6b2f esp=0022ef24 ebp=00000002 iopl=0 nv up ei pl nz na pe nc
    cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202
    *** WARNING: Unable to verify checksum for gta_sa.exe
    *** ERROR: Module load completed but symbols could not be loaded for gta_sa.exe
    gta_sa+0x1b6b2f:
    005b6b2f 8886d0020000 mov [esi+0x2d0],al ds:0023:000002d0=??
    0:000> !analyze –v
    ERROR: FindPlugIns 8007007b
    *******************************************************************************
    * *
    * Exception Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

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

    *********************************************************************
    * 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 kernel32.dll -
    *********************************************************************
    * 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 wdmaud.drv -
    *********************************************************************
    * 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 dsound.dll -
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *** ERROR: Symbol file could not be found. Defaulted to export symbols for QuickTime.qts -
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * 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 user32.dll -
    *** ERROR: Symbol file could not be found. Defaulted to export symbols for dinput8.dll -
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Probably caused by : memory_corruption

    Followup: memory_corruption
    ---------

    0:000> !analyze –v
    ERROR: FindPlugIns 8007007b
    *******************************************************************************
    * *
    * Exception Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

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

    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Probably caused by : memory_corruption

    Followup: memory_corruption


    Was könnte das sein?

    Hallo, ehm könnte sein, weiss es nicht. also ich habe jetzt mal so ein debugger progi benutzt, und es ist das herausgekommen. Nun leider weiss ich nicht was es bedeutet


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


    Loading Dump File [C:\Dokumente und Einstellungen\All Users\Anwendungsdaten\Microsoft\Dr Watson\user.dmp]
    User Mini Dump File: Only registers, stack and portions of memory are available

    Comment: 'Dr. Watson generated MiniDump'
    Windows XP Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: SingleUserTS Personal
    Debug session time: Fri Mar 24 19:27:47.000 2006 (GMT+2)
    System Uptime: not available
    Process Uptime: 0 days 0:00:38.000
    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:
    .....................................................................................
    This dump file has an exception of interest stored in it.
    The stored exception information can be accessed via .ecxr.
    (8c0.c7c): Access violation - code c0000005 (first/second chance not available)
    eax=00000008 ebx=00000000 ecx=ffffffff edx=00000000 esi=00000000 edi=00000011
    eip=005b6b2f esp=0022ef24 ebp=00000002 iopl=0 nv up ei pl nz na pe nc
    cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202
    *** WARNING: Unable to verify checksum for gta_sa.exe
    *** ERROR: Module load completed but symbols could not be loaded for gta_sa.exe
    gta_sa+0x1b6b2f:
    005b6b2f 8886d0020000 mov [esi+0x2d0],al ds:0023:000002d0=??
    0:000> !analyze –v
    ERROR: FindPlugIns 8007007b
    *******************************************************************************
    * *
    * Exception Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

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

    *********************************************************************
    * 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 kernel32.dll -
    *********************************************************************
    * 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 wdmaud.drv -
    *********************************************************************
    * 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 dsound.dll -
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *** ERROR: Symbol file could not be found. Defaulted to export symbols for QuickTime.qts -
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * 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 user32.dll -
    *** ERROR: Symbol file could not be found. Defaulted to export symbols for dinput8.dll -
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Probably caused by : memory_corruption

    Followup: memory_corruption
    ---------

    0:000> !analyze –v
    ERROR: FindPlugIns 8007007b
    *******************************************************************************
    * *
    * Exception Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

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

    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Probably caused by : memory_corruption

    Followup: memory_corruption
    ---------

    :cry::cry: