Announcement

Collapse
No announcement yet.

Initialization Error (Kernel Debugger)

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #46
    stuck on the problem

    First i try to uninstall daemon tools on my windows xp pro 32bit
    which of course says it can't uninstall because it wasn't instally properly SO.....
    I went to my system32/drivers to look for any daemon tools drivers sitting around and found nothing resembling any of the daemon tools drivers.

    However, while using regedit i found the most recent drivers sitting around at "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servi ces"
    and removed those

    so just incase that the installation bugs me about a old SPTDi installation I just went to their site to download the latest version 1.42
    duplexsecure.com ist die beste Quelle für alle Informationen die Sie suchen. Von allgemeinen Themen bis hin zu speziellen Sachverhalten, finden Sie auf duplexsecure.com alles. Wir hoffen, dass Sie hier das Gesuchte finden!


    I also turned off write debugging information to "none"
    even though I highly doubt that's the problem.

    I reboot
    and then reinstall
    and try to run daemon tools with the same error appearing up

    "Initialzation error 7.
    This program requires at least Windows 2000 with SPTD 1.37 or higher.
    Kernel debugger must be deactivated."

    I check my event log just to dig up the error that comes up when i try to run it which is below

    Event Type: Error
    Event Source: sptd
    Event Category: None
    Event ID: 4
    Date: 3/11/2007
    Time: 11:26:04 PM
    User: N/A
    Computer: 52H
    Description:
    Driver detected an internal error in its data structures for .

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 00 00 00 00 01 00 52 00 ......R.
    0008: 00 00 00 00 04 00 04 c0 .......А
    0010: dc 00 00 00 08 00 00 00 Ü.......
    0018: 00 00 00 00 00 00 00 00 ........
    0020: 00 00 00 00 00 00 00 00 ........

    Comment


    • #47
      a problem

      before a couple of weeks i tryed to install dt and i have msg like this above (kernel..) , after that comp rebooted and i needed like 2h to get in win (xp sp2 - i think) , and unistall it. then i wait untill yesterday, download newer ver. of dt (4.8. x86) and tryed again- with allmost same results.. the msg now wouse "please wait..." and it took a couple of hours to uninstall it again.. before this win i used alcohol52% and it work properly, after the first problem with dt, either alcohol wont work.. how can i see whot win (32/64bit) i use?? i have amd turion 64 2.0, win firewall, no antivirus ( i used avast) ,and using nero 6 ultra edition, easy cd da extractor, clonedvd 2 .. please h.e.l.p. !?

      Comment


      • #48
        enyone?

        i reallly need help with this! can enyone answer me how can i handle this problem ? i'm stupid and cant find nothing usefull or understandible in this sea of posts..

        Comment


        • #49
          You are not alone, I posted a similar if not the same problem and a lot of people read it but I don't see any solutions posted. I think DT no longer works on an updated system. Bet microsoft did something in their updates to thwart it.

          Comment


          • #50
            die bill

            crap! will formating and installing winXP with old service pack help?

            Comment


            • #51
              If you get Initialization error 7 un- and re-install Daemon Tools.
              Everybody be cool! You, be cool!
              They'll keep fighting! And they'll win!

              Comment


              • #52
                I'm having this problem, and Daemon-Tools is not allowing me to uninstall! It says that setup is unable to validate the installation... even if I re-run setup.

                How can I uninstall it? Thanks.

                Comment


                • #53
                  Check thread about how to remove v4 in common problems and solutions forum.
                  Everybody be cool! You, be cool!
                  They'll keep fighting! And they'll win!

                  Comment


                  • #54
                    Ok, I registered specially to say that there is definately something wrong with the latest build of DT.

                    4 pcs of mine crash now upon booting, after some 17 hours I have managed to get 3 back up and running the 4th i am writing this on in safe mode..

                    the error, when I use debugging mode is always the same as mentioned above.. this program is designed for win2k with sptd1.27 yada yada yada.

                    Thank you all by the way for your comments, I managed to get 3 pcs back to life thanks to you, this pc.. is .. well.. I need a drink.

                    issues on the other pcs.. CloneCD and Daemon tools were mounting on one pc to same drive letter..

                    Also, in no particular order :-
                    I changed in device config the sata/pata nforce drivers to microsoft's generic,
                    updated the sptd.sys to 1.4,
                    loaded the latest logitech drivers for the mx518's that were on, (used ms generic drivers before)
                    disabled the logging of debugging messages.
                    uninstalled and re-installed daemon tools..

                    Either way, after 17 hours 3 pcs are now back, but this last pc is driving me nuts.. same initialisation error as everyone else..

                    1 small point though, If i mount images made for 4.08 no issues, but when I load in images that were made for 3.47 the issues return.. Thats something for daemon tools people to think about..

                    Right im off to carry on rebooting this damn pc.. god i hate it when things do this..

                    Comment


                    • #55
                      What do you mean by using debugging mode? You did read that v4.0x won't work with kernel debuggers?
                      And what do you mean by images created for v4.08 or for v3.47?
                      Everybody be cool! You, be cool!
                      They'll keep fighting! And they'll win!

                      Comment


                      • #56
                        This pc, crashes almost immediately after reaching windows desktop screen, sometimes just before other times just after..

                        If I reboot, and press "F8" one of the options is startup in debugging mode.. using this mode windows boots fine, except that the only error listed is the "Daemon tools initilisation error run using win2k with sptd 1.27 yada yada yada.."-

                        Disabling daemon tools and pc boots perfectly and has no issues at all.

                        this pc is :-
                        Intel Conroe E6600
                        Windows Xp Professional Service pack 2 plus all updtes.
                        Asus P5N32 Sli SE Delux (bios 0401 (v2)).
                        2Gb G.E.I.L. 800Mhz ram.
                        Geforce 7950Gt (using 93.71 drivers)
                        250GB Western Digital Sata II.
                        650W PSU (thermaltake)
                        Thermaltake Cool Orb II cooler..

                        As to image versions, I have "call of Duty 2", and "battle for middle earth", they were originally loading with daemon 3.47 and worked on this pc flawlessly.

                        now recently i purchased "Supreme Commander" unfortunately the mini image available will only work with daemon tools 4.08.

                        So, now loading daemon tools 4.08 and mounting "supreme commander" and no issues are found.. BUT..

                        As soon as i load the other two games as well and then restart the pc the pc then crashes as soon as it reaches the desktop, unmounting the two older game images, and the pc works..

                        This was happening on all 4 pcs, but I managed to get 3 of them back working (see post above) however this 4th and final pc will not work with the new version of daemon.

                        I have loaded the newer sptd.sys as well, but no difference..

                        It has to be said, that daemon 3.47 worked flawlessly, but the newer version of 4.08 is causing a few issues for a few people, I am one of them.. if you want more details please contact me via my registered email.. (i dont like leaving my email on forums for people to see).

                        Comment


                        • #57
                          well, I completely reformatted the pc.

                          used the sata driver as provided on the cd for the mainboard and installed Xp with SP2.

                          installed drivers off CD, Validated Windows, loaded all critical service packs and updates.

                          updated the drivers to latest for all components.

                          Added Antivirus, updated.
                          Added 90% of games and programs,
                          Added Daemon Tools 4.08
                          Added and installed Virtual dvds into Daemon.
                          rebooted Pc, pc CRASHED at loading of windows.

                          Rebooted pc into safe mode, uninstalled Daemon.

                          pc rebooted perfectly, re-installed Daemon, rebooted..

                          PC Crashed..

                          Uninstalled Daemon, pc ok again..

                          i think its fair to say Daemon has an issue.. let me know what details you need to debug this..

                          Comment


                          • #58
                            First off, if you had SPTD 1.27 installed, then you weren't running the latest build of Daemon Tools. Are you sure about that SPTD version? Because if you are, that means you were running an earlier version of v4.

                            Comment


                            • #59
                              ...i resolve my issue - problem was in regional setings. dt cant work properly (slows down everything so bad that i got a beard grown up from waiting for unistall) if language is not same in "regional options" , "languages" and "advanced" tab. i had a combination of croatian and bosnian. when i switch (just) to croatian it works perfectly!

                              Comment

                              Working...
                              X