Announcement

Collapse
No announcement yet.

Initialization Error (Kernel Debugger)

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

  • #16
    I'm having the same problem.

    I dumped every driver loaded on my system, and I can't really see anything it could be. I already uninstalled a couple things which really shouldn't have done anything. (wehntrust, overflow guard, starforce, tried killing firewall) (I only removed, from this list, obvious windows drivers).
    Driver/Module list by traversal of PsLoadedModuleList


    F7D2E000 - \WINDOWS\system32\KDCOM.DLL
    F773A000 - sptd.sys
    F7D30000 - \WINDOWS\System32\Drivers\WMILIB.SYS
    F7722000 - \WINDOWS\System32\Drivers\SPTD6093.SYS
    F7DF6000 - PCIIde.sys
    F7AAE000 - \WINDOWS\System32\Drivers\PCIIDEX.SYS
    F7D32000 - intelide.sys
    F785E000 - MountMgr.sys
    F76C4000 - ftdisk.sys
    F7D34000 - dmload.sys
    F769E000 - dmio.sys
    F7AB6000 - PartMgr.sys
    F786E000 - VolSnap.sys
    F7686000 - atapi.sys
    F787E000 - ultra.sys
    F766E000 - \WINDOWS\system32\DRIVERS\SCSIPORT.SYS
    F7656000 - SI3112r.sys
    F788E000 - disk.sys
    F789E000 - \WINDOWS\system32\DRIVERS\CLASSPNP.SYS
    F75BE000 - dcpp2k.sys \\This ones disk encryption
    F759F000 - fltMgr.sys
    F7C42000 - SiWinAcc.sys
    F74CE000 - NDIS.sys
    F78AE000 - baserand.sys
    F74B3000 - Mup.sys
    F7A5E000 - \SystemRoot\system32\DRIVERS\intelppm.sys
    F67AA000 - \SystemRoot\system32\DRIVERS\ati2mtag.sys
    F28F1000 - \SystemRoot\system32\DRIVERS\VIDEOPRT.SYS
    F28D3000 - \SystemRoot\system32\DRIVERS\e1000325.sys
    F7B5E000 - \SystemRoot\system32\DRIVERS\usbuhci.sys
    F28B0000 - \SystemRoot\system32\DRIVERS\USBPORT.SYS
    F7C1E000 - \SystemRoot\system32\DRIVERS\usbehci.sys
    F7A1E000 - \SystemRoot\system32\DRIVERS\nic1394.sys
    F276B000 - \SystemRoot\system32\drivers\P16X.sys
    F2748000 - \SystemRoot\system32\drivers\ks.sys
    F2724000 - \SystemRoot\system32\drivers\portcls.sys
    F7A7E000 - \SystemRoot\system32\drivers\drmk.sys
    F26F8000 - \SystemRoot\system32\DRIVERS\ctoss2k.sys
    F26D8000 - \SystemRoot\system32\DRIVERS\ctsfm2k.sys
    F25CB000 - \SystemRoot\system32\DRIVERS\BCMSM.sys
    F7ACE000 - \SystemRoot\System32\Drivers\Modem.SYS
    F7BBE000 - \SystemRoot\system32\DRIVERS\fdc.sys
    F7A2E000 - \SystemRoot\system32\DRIVERS\serial.sys
    F744F000 - \SystemRoot\system32\DRIVERS\serenum.sys
    F25B7000 - \SystemRoot\system32\DRIVERS\parport.sys
    F6AC7000 - \SystemRoot\system32\DRIVERS\cdrom.sys
    F3F4F000 - \SystemRoot\system32\DRIVERS\redbook.sys
    F7BC6000 - \SystemRoot\System32\Drivers\GEARAspiWDM.sys
    F3F1F000 - \SystemRoot\system32\DRIVERS\imapi.sys
    F7BD6000 - \SystemRoot\system32\DRIVERS\bcbus.sys
    F7F83000 - \SystemRoot\system32\DRIVERS\audstub.sys
    F3F3F000 - \SystemRoot\system32\DRIVERS\rasl2tp.sys
    F7D26000 - \SystemRoot\system32\DRIVERS\ndistapi.sys
    F25A0000 - \SystemRoot\system32\DRIVERS\ndiswan.sys
    F7A4E000 - \SystemRoot\system32\DRIVERS\raspppoe.sys
    F6AF7000 - \SystemRoot\system32\DRIVERS\raspptp.sys
    F7BCE000 - \SystemRoot\system32\DRIVERS\TDI.SYS
    F258F000 - \SystemRoot\system32\DRIVERS\psched.sys
    F6AE7000 - \SystemRoot\system32\DRIVERS\msgpc.sys
    F7BE6000 - \SystemRoot\system32\DRIVERS\ptilink.sys
    F7BEE000 - \SystemRoot\system32\DRIVERS\raspti.sys
    F7BF6000 - \SystemRoot\system32\DRIVERS\RadProbe.sys
    F255E000 - \SystemRoot\system32\DRIVERS\rdpdr.sys
    F3F2F000 - \SystemRoot\system32\DRIVERS\termdd.sys
    F7C06000 - \SystemRoot\system32\DRIVERS\kbdclass.sys
    F7BFE000 - \SystemRoot\system32\DRIVERS\mouclass.sys
    F7D94000 - \SystemRoot\system32\DRIVERS\swenum.sys
    F252A000 - \SystemRoot\system32\DRIVERS\update.sys
    F7423000 - \SystemRoot\system32\DRIVERS\mssmbios.sys
    F7C36000 - \SystemRoot\system32\DRIVERS\vdiskbus.sys
    F7D0A000 - \SystemRoot\system32\DRIVERS\vmnetadapter.sys
    F7D2A000 - \SystemRoot\system32\DRIVERS\VMNET.SYS
    F6A97000 - \SystemRoot\System32\Drivers\NDProxy.SYS
    F3EFF000 - \SystemRoot\system32\DRIVERS\usbhub.sys
    F7D98000 - \SystemRoot\system32\DRIVERS\USBD.SYS
    F7467000 - \SystemRoot\system32\drivers\MODEMCSA.sys
    F41F3000 - \SystemRoot\system32\DRIVERS\flpydisk.sys
    F6D8B000 - \SystemRoot\System32\Drivers\BC_BFish.SYS
    F41C3000 - \SystemRoot\System32\Drivers\BC_DES.SYS
    F7D9E000 - \SystemRoot\System32\Drivers\BC_Gost.SYS
    F41E3000 - \SystemRoot\System32\Drivers\BC_RIJN.SYS
    F41EB000 - \SystemRoot\System32\Drivers\BC_TFISH.SYS
    F7453000 - \SystemRoot\System32\Drivers\fsh.SYS
    F7DA0000 - \SystemRoot\System32\Drivers\Fs_Rec.SYS
    F7E35000 - \SystemRoot\System32\Drivers\Null.SYS
    F7DA2000 - \SystemRoot\System32\Drivers\Beep.SYS
    F41DB000 - \SystemRoot\system32\DRIVERS\HIDPARSE.SYS
    F41BB000 - \SystemRoot\System32\drivers\vga.sys
    F7DA6000 - \SystemRoot\System32\Drivers\mnmdd.SYS
    F7DA8000 - \SystemRoot\System32\DRIVERS\RDPCDD.sys
    B2E97000 - \SystemRoot\system32\drivers\fwdrv.sys
    F7B16000 - \SystemRoot\System32\Drivers\Msfs.SYS
    F41B3000 - \SystemRoot\System32\Drivers\Npfs.SYS
    F6D8F000 - \SystemRoot\system32\DRIVERS\rasacd.sys
    B2E84000 - \SystemRoot\system32\DRIVERS\ipsec.sys
    B2E2C000 - \SystemRoot\system32\DRIVERS\tcpip.sys
    F2B9C000 - \systemroot\system32\drivers\tdimsys.sys
    B2DDC000 - \SystemRoot\system32\DRIVERS\netbt.sys
    F6D83000 - \SystemRoot\System32\drivers\ws2ifsl.sys
    B2DBA000 - \SystemRoot\System32\drivers\afd.sys
    F6AA7000 - \SystemRoot\system32\DRIVERS\netbios.sys
    B2D8F000 - \SystemRoot\system32\DRIVERS\rdbss.sys
    B2D20000 - \SystemRoot\system32\DRIVERS\mrxsmb.sys
    B2D0C000 - \SystemRoot\system32\drivers\khips.sys
    F6A77000 - \SystemRoot\system32\DRIVERS\wanarp.sys
    F6940000 - \SystemRoot\System32\Drivers\Fips.SYS
    F7DB2000 - \??\C:\Program Files\Radeon Omega Drivers\v2.6.42\ATI Tray Tools\atit
    ray.sys
    F793E000 - \SystemRoot\system32\DRIVERS\arp1394.sys
    F2B84000 - \SystemRoot\system32\DRIVERS\usbccgp.sys
    F743F000 - \SystemRoot\system32\DRIVERS\hidusb.sys
    F799E000 - \SystemRoot\system32\DRIVERS\HIDCLASS.SYS
    B2FBC000 - \SystemRoot\system32\DRIVERS\kbdhid.sys
    F7DAA000 - \SystemRoot\System32\Drivers\mhk.SYS
    B2FB0000 - \SystemRoot\system32\DRIVERS\mouhid.sys
    F7F62000 - \SystemRoot\System32\Drivers\moh.SYS
    B2CC1000 - \SystemRoot\System32\Drivers\Fastfat.SYS
    F2AAC000 - \SystemRoot\System32\Drivers\Cdfs.SYS
    B2CA9000 - \SystemRoot\System32\Drivers\dump_atapi.sys
    F7DDA000 - \SystemRoot\System32\Drivers\dump_WMILIB.SYS
    BF800000 - \SystemRoot\System32\win32k.sys
    F748F000 - \SystemRoot\System32\drivers\Dxapi.sys
    F7B6E000 - \SystemRoot\System32\watchdog.sys
    BF9C2000 - \SystemRoot\System32\drivers\dxg.sys
    F7ECE000 - \SystemRoot\System32\drivers\dxgthk.sys
    BF9D4000 - \SystemRoot\System32\ati2dvag.dll
    BFA10000 - \SystemRoot\System32\ati2cqag.dll
    BFA43000 - \SystemRoot\System32\atikvmag.dll
    BFA76000 - \SystemRoot\System32\ati3duag.dll
    BFCB4000 - \SystemRoot\System32\ativvaxx.dll
    B0C0B000 - \??\C:\WINDOWS\system32\Drivers\ino_fltr.sys
    F7DEA000 - \??\C:\WINDOWS\system32\drivers\ebnetbt.sys
    F7DD4000 - \SystemRoot\system32\DRIVERS\svsnet.sys
    F7B3E000 - \SystemRoot\system32\DRIVERS\vmnetbridge.sys
    B0BDF000 - \SystemRoot\system32\DRIVERS\ndisuio.sys
    B0ADE000 - \SystemRoot\system32\drivers\wdmaud.sys
    F2945000 - \SystemRoot\system32\drivers\sysaudio.sys
    B07DC000 - \SystemRoot\system32\DRIVERS\mrxdav.sys
    F2CE1000 - \??\C:\WINDOWS\system32\Drivers\hcmon.sys
    F7DAE000 - \SystemRoot\System32\Drivers\ParVdm.SYS
    B07C9000 - \SystemRoot\System32\Drivers\SENTINEL.SYS
    F7B66000 - \??\C:\WINDOWS\system32\Drivers\VMparport.sys
    B07B2000 - \??\C:\WINDOWS\system32\Drivers\vmx86.sys
    B050A000 - \SystemRoot\system32\DRIVERS\secdrv.sys
    B0BB3000 - \??\C:\WINDOWS\system32\drivers\svs.sys
    B06E6000 - \??\C:\WINDOWS\system32\drivers\svspth.sys
    B0552000 - \??\C:\WINDOWS\system32\drivers\vmnetuserif.sys
    B054E000 - \??\C:\Program Files\Common Files\VMware\VMware Virtual Image Editing
    \vstor2.sys
    B02D8000 - \SystemRoot\system32\DRIVERS\srv.sys
    B01F7000 - \SystemRoot\System32\Drivers\HTTP.sys
    F7EA0000 - \SystemRoot\System32\DRIVERS\KProcCheck.sys
    AFED5000 - \SystemRoot\system32\drivers\kmixer.sys

    Total number of drivers = 163

    Comment


    • #17
      Do you have any error messages in system event log?

      Comment


      • #18
        None involving d-tools or sptd, or that are at all recent, I should have mentioned as well i'm using sp2 xp.

        Comment


        • #19
          I'm getting this too, but I've noticed a couple of other people getting this are using Anti-Vir. I've tried disabling it and restarting in safe mode (as well as removing Starforce games and drivers, and virtually everything short of a format), could the Anti-Vir Guard feature be mistaken or conflict similarly to a kernel debugger? I'm going to try uninstalling it right now.

          Comment


          • #20
            Nope, that didn't work
            Any ideas would really be appreciated, I'm stuck.

            Comment


            • #21
              Ok, I was chatting with vortex from the unofficial tech support channel, and he suggested that my hotfixed SP2 build was confusing the program. Is there any way to skip the OS check?

              Comment


              • #22
                I doubt it, if the OS check could be disabled then the other protections could be too.

                Comment


                • #23
                  Originally Posted by SCVirus
                  I doubt it, if the OS check could be disabled then the other protections could be too.
                  I'm sorry, what? I'm talking about the Daemon installer.

                  Comment


                  • #24
                    Originally Posted by shinryuu
                    Ok, I was chatting with vortex from the unofficial tech support channel, and he suggested that my hotfixed SP2 build was confusing the program. Is there any way to skip the OS check?
                    Here's something you might try:

                    Go to the properties sheet for the installation .exe and then to the 'Compatibiliy' tab.

                    Check the box to run it in Compatibilty mode and set it to Windows 2000 compatibility.

                    NOTE: This should make the installer think that it's running on Win2k, which may well screw-up any part of the install that's different between Win2k and WinXP. But maybe there aren't any and it'll work.

                    Comment


                    • #25
                      ...

                      I don't think there's actually an issue with the OS check. But anything is worth a try.
                      the modern world:
                      net helpmsg 4006

                      Comment


                      • #26
                        @ i k a r i: Did you use the DT 3.47 before and unistalled it?

                        Comment


                        • #27
                          Hello there! Im having the same problem as all the others!
                          I get the deactivate karnell...or what ever error...

                          And yes bladeinger, I was running Daemon tools 3.47 when i installed daemon tools v4!
                          I know it wasn't such a good idea...But...anywho! Now Im stuck with that error message!!=(

                          Help?!....anyone?=)

                          Comment


                          • #28
                            How i got it to work!

                            Ok this is what you got to do!

                            Uninstall Daemon 4.0 if you can if not its ok
                            Right click on my computer and select properties
                            click the Advanced tab
                            Under start up and recovery select settings
                            Under write debugging information set it to none
                            Hit all the oks and applys on the way out
                            You can try and run the program if installed but i suggest reinstalling!

                            After running daemon for the first time you can set the debugging information back to whatever you want!

                            ENJOY!

                            Comment


                            • #29
                              Mary, Mother of God

                              Enviro, thank you. You are a prince among men. A saint. A God. You are Jesus, Mohammed, Confucius and Shakyamuni rolled into a ball and smothered in a creamy sauce of really great guy. I have lost nights of sleep over this. I have tried everything and spoken to everyone who would listen. Not only that, but you fixed a random error on my computer that had been happening since the day I bought it, through at least 3 reformats. I'm so happy, I'm nearly crying. Sweet blessed relief.

                              Ok, enough gushing, here's what I did:
                              1. Disabled debugger logging, as per Enviro's instructions
                              2. Opened the DT4 installer
                              3. With the installer open, copied SPTDinst.exe from the temp
                              4. Ran SPTDinst.exe from the command line with the /add switch (it refused to work any other way)
                              5. Rebooted, reinstalled DT4 and now it's humming away happily.

                              I saw at least one other person getting exactly the same error I was (entry_point_not_found), and plenty of people are getting the kernel debugger error, so hopefully Enviro's inspired advice will spread joy to the masses, and not just me

                              Comment


                              • #30
                                Ok, everyone with this Problem, pease try this out (I had the same Problem on my Server):
                                - Run the Uninstall-Routine, either of the 3.47 or the 4.0.
                                - Reboot the System.
                                - Remove manualy all Registry Entries and Files from the previous Version, as described by VeNoM386 in the Section "Commmon Problems and Solutions", again either of the 3.47 or the 4.0.
                                - Reboot and check Event Log for Errors related to missing Files of DT.
                                - If everything is ok, install the new Version.
                                That was the way to solve the Problem on my System.

                                Comment

                                Working...
                                X