Announcement

Collapse
No announcement yet.

neustart des Betriebssystems

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    neustart des Betriebssystems

    ich habe ein problem. ich habe mir die neue testversion von daemon tool herruntergeladen. wenn ich sie installieren will, kommt die meldung vom sptd treiber wegen dem neustart. also gemacht und getan. nach dem neustart fährt der rechner aber nicht mehr hoch. er kommt bis zu der stelle wo der sptd treiber geladen wird. dann startet er neu (getestet im abgesicherten modus, mit esc ohne sptd treiber fährt er hoch). das problem hatte ich mit einer älteren version schon einmal, jedoch musste ich damals im geräte manager was deaktivieren um den fehler zu beheben. leider ist mir das entfallen. in meinem rechner ist ein K8Upgrade-NF3 mainboard mit einem ASRock Future CPU Port. darauf befindet sich 3 GB DDR2 und ein AMD Athlon X2 6000+. mehr angaben findet ihr hier -> sysProfile: ID: 92826 - PansenC Baustelle .
    ich hoffe ihr könnt mir helfen.
    Tags: None
  • #2
    Hast du SPTD 1.60 drauf?
    Ausserdem kannst du mal schauen, ob ein Minidump (c:\windows\minidump) verfuegbar ist und wenn ja, den mal hier posten.

    Der Neustart klingt wie ein BSOD.
    Make something idiot proof, but then they just make a better idiot
    Peace Through Power

    Comment

    • #3
      SPTD 1.60 war drauf. da muss ich erstmal daemon tool wieder installieren.

      Comment

      • #4
        das steht in der minidump.

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


        Loading Dump File [\Minidump\Mini092909-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 0n2
        *** 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 3) MP (2 procs) Free x86 compatible
        Product: WinNt, suite: TerminalServer SingleUserTS
        Machine Name:
        Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
        Debug session time: Mon Sep 28 19:20:33.125 2009 (GMT+2)
        System Uptime: 0 days 0:12:52.809
        ************************************************** *******************
        * 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 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
        ...................
        Unable to load image DB3G.sys, Win32 error 0n2
        *** WARNING: Unable to verify timestamp for DB3G.sys
        *** ERROR: Module load completed but symbols could not be loaded for DB3G.sys
        ************************************************** *****************************
        * *
        * Bugcheck Analysis *
        * *
        ************************************************** *****************************

        Use !analyze -v to get detailed debugging information.

        BugCheck 1000008E, {c0000047, 80521d1c, f78ae764, 0}

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

        *** WARNING: Unable to verify timestamp for USBPORT.SYS
        *** ERROR: Module load completed but symbols could not be loaded for USBPORT.SYS
        *** WARNING: Unable to verify timestamp for sptd.sys
        *** ERROR: Module load completed but symbols could not be loaded for sptd.sys
        ************************************************** ***********************
        *** ***
        *** ***
        *** 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 ***
        *** ***
        ************************************************** ***********************
        ************************************************** *******************
        * 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 : DB3G.sys ( DB3G+855 )

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

        Comment

        • #5
          Lad den minidump mal bitte noch irgendwo hoch, z.B. bei sendspace o.ä. Filehostern.

          Wie du wahrscheinlich schon gegooglet hast handelt es sich bei
          der DB3G.sys um den Treiber deiner Razer Diamonback 3G.
          I'm not employed by Disc Soft and my views do not necessarily reflect the ones of the company.

          Comment

          • #6
            ich kann auch die maus deinstallieren und alle treiberleichen löschen. sobald der spdt treiber installiert wird und der rechner nen neustart macht, startet er neu sobalt der spdt treiber geladen wird. da kannste ihn ruhig ne halbe stunde laufen lassen -> neustarts ohne ende. im gerätemanager kann man auch alle versteckten treiber usw. anzeigen lassen. unter nicht-pnp-treiber hatte ich damals was deaktiviert. leider weis ich nicht mehr was. ich möchte jetzt aber nicht jedes einzelne ausprobieren, da ich mein system nicht unbedingt zerschießen möchte.

            Comment

            • #7
              hier ist die minidump datei RapidShare: 1-CLICK Web hosting - Easy Filehosting


              und mal ein screenshot von dem reiter nicht-pnp-treiber

              Comment

              Previous template Next
              Working...
              X

              We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.

              By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.

              I Agree