Announcement

Collapse
No announcement yet.

"Virtual SCSI driver not detected" error

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

  • "Virtual SCSI driver not detected" error

    Daemon tools version 3.26 and 3.29 have same error. After install it works good but when i restart my computer it will give a blue screen and restatr one more time and after that i can choose "last good configuriation" in dos or something and it will gi into my Windows XP. There it will come a error message from Daemon tools that yped "Virtual SCSI driver not detected" and after that daemon tools dont work. This problem dont come up in daemon tools older version like 3.23 or older.

    Thanx for the help

    // Pulse

  • #2
    I have same problem... plz fix it. thx :wink:

    Comment


    • #3
      First, please post more information. We require knowing what burning software you have installed, and full os details (service packs, major updates, etc...)

      Please both of you try the following:
      1) Run devmgmt.msc, goto SCSI, and report what is displayed there. Goto System Devices and verify PNP Bios Extension (two should be present if you use alcohol 120).

      2) If any of the above devices are not loaded, etc..., please try updating or reinstalling the drivers of each.

      3) Try uninstalling, rebooting (twice to be safe);
      then installing again.

      Comment


      • #4
        I got same problem...

        My Computer:

        ThunderBird800
        KT133A
        SDRAM512M
        MX400
        IBM30G+SG80G
        SB16Value

        WINXP English Version with Service Pack 1 and all the lastest updates
        Nero and Norton Antiviurs Corp. Edition 8.0 were installed

        Comment


        • #5
          @youth: Please check the status of the PNP Bios Extension. Also check if antyhing is under SCSI section in device manager.

          If they have yellow exclamations, goto properties, and report the exact error.

          Comment


          • #6
            after two times of rebooting,i installed 3.29,this time the WinXP didn't require me to restart and the PNP Bios Ext. & SCSI Device in Device Manager were all working properly,without any yellow exclamations.

            then i restart the computer, it gave me a blue screen(too fast to obtain any useful information) and restarted again automatically. i have to choose "last good configuration" to enter XP,then the damned prompt -"virtual SCSI driver not detected" came out again. now the PNP Bios Ext. & SCSI Section in Device Manager all disappeared

            do u still need more information?

            ps: yesterday i found some yellow exclamations on SCSI Device after install 3.29, but i didn't check the propertes

            Comment


            • #7
              I am haveing the same issue with DT I have a G4 mx460, Santa Cruz, No Anti-Virus, Nero 5.10.0.0, XP SP 1 and all updates, Samsung 48\24\48 from what i am reading this is a common issue with this software So if u have any info PLZ HELP !!!!!!!!!

              Comment


              • #8
                1) I am having the same problem with DT 3.29 on WinXP +SP1:
                Clean install of XP-SP1, still setting up ie not "used" yet, no burning prog yet, Norton SystemWorks 2003- everything disabled- for manual use only. Intel BX board, ATI Rage Pro, Soundblaster 16 ISA, Promise Ultra66; stock drivers auto-installed by WinXP. DT worked perfect on the same machine with Win98SE.

                DT 3.29 installs OK, then blue screens on reboot with error
                Stop: ox0000007E and indicates a problem with st3mp28.sys
                The only escape is to go back to "Last good setup" as in above posts. Then I get the "Virtual drive not detected/present" message. Under SCSi the Promise controller is OK, nothing else showing. PNPBios shows OK. I can get to daemon.msi and use it to "repair" OK, but then it blue screens again. I still can fool with BIOS settings and services, but if you have any ideas and can point me in a direction I'll appreciate.

                2) Youth- you can stop the blue screen flashing by: press F8 after the Bios but before Windows boots- MS doesn't indicate just when so I just keep tapping it. That get you a boot menu- start in Safe mode. Then find your way to Contol Panel-System-Advanced-Startup&Recovery. At the "system failure" section uncheck "auto reboot".

                Comment


                • #9
                  haha,it's all ok in 3.32

                  haha,it's all ok in 3.32, happy, bow to all :P

                  Comment


                  • #10
                    just installed 3.32 and i have the same exact error
                    so what can i do about it?

                    Comment


                    • #11
                      Yes the problem seems to occur in 3.32 too.. I have been suffering from this problem too and it's making the usage of daemon tools almost impossible. Weird thing was that it worked perfectly with 3.29 before, but then I formated my drives and re-istalled Windows XP professional and got all updates + sp1( I had all the same updates before re-formating) and now 3.29 is causing the blue screen on boot.

                      Anyway the problem has definetly something to do with the SCSI & Raid controller drivers provided with D-Tools.

                      ERROR occure:
                      Blue Screen on booting > Using last configuration that worked enables windows to work again > SCSI & Raid Controller driver is gone.

                      So far 3.26, 3.29, 3.32 have caused this error, I'm gonna try 3.23 now since some people claim that it doesn't cause the blue screen.

                      Comment


                      • #12
                        Hi, I'am encoutering the same problem with W2K+SP2 but not only with DT, even with alcohol 120 and clone CD. In fact, with all major prog which try to install a virtual drive. Think my system is clean : all motherboard drivers applied (Asus A7V-266E / Athlon XP 1700+);
                        via4in1 (latest) installed, aspi (adaptec) 4.72 installed. the only other burning prog installed is nero 5.5.10.15 and it is fully fonctionnal.
                        I have also fully disabled the onboard sound card (sound + game port).
                        When my system boots correctly, it show a problem with the Pnp Bios Extension. CCD works correctly, because I haven't installed the virtual drive.
                        Thinks my problem may become from interrupt sharing. but I can't fix them. For info, my system also have a SB audigy player (latest drivers). Could Creatives drivers may conflict with virtual scsi adapters ?
                        Other thing : If I try to remove manually the virtual drive or the virtual scsi adapter in the system manager, my system crash and re-boot, exactly the same symptoms like during the standard/automatic installation/removing of DT.

                        Hope these line could help in finding the problem.

                        Comment


                        • #13
                          I also seem to be having this (or a very similar) problem:

                          AMD XP 2000+
                          KT133A
                          Windows XP SP1
                          512MB RAM
                          c-media cmi8738 chipset based sound card

                          I recently decided to do a complete reinstall of my machine, with all the latest drivers for all the equipment in my machine. Once all drivers were installed I installed daemon tools. Installation went fine, first reboot ok. But second reboot never made it to login screen. The machine simply reboots and I can only successfully reboot if I choose "last known good.." or "safe mode". When I am able to boot I gat the famous error message "scsi driver not loaded". I have made several ghost images during various stages of the driver installation proces, but no matter how far I went back allways trouble.

                          So, I dedided to do a new clean install of win xp sp1 and install daemon tools before installing anything alse. That seemed to work. I was able to boot with daemon tools working. I then installed the latest via 4in1 drivers and everything still worked (each time I rebooted at least 3 times to be sure). But then I installed the latsest drivers for my sound card with the default settings and problems started again, crash befor login screeen, need to start in safe mode, daemon tools didn't work.

                          I then checked the default options of the sound card drivers and noticed I had choosen for a sound chipset on board and left the on board midi & game ports enabled. I changed all that to their correct settings (sound card and not on-board and on-board midi and game ports disabled) and everything worked fine again. I only rebooted a couple of times and didn't do anything specific so I can not guarantee that the problems is solved for my, but I have good hope ;-)

                          Anyway, I don't know if all this information is helpfull or not, just wanted to let you guys know.

                          cheers,
                          Kryptonneke

                          Comment


                          • #14
                            virtual scsi driver error

                            Same problem here
                            xp sp1
                            no real scsi devices in system
                            aspi drivers 4.6 and temporally 4.7
                            blue screens and the other errors same here

                            in version 3.29 of daemon-tools the scsi driver is "st3mp28.sys"
                            in 3.33 it is "st3Wolf.sys".

                            daemon-tools installs a virtual scsi drive and it runs the first time before reboot, after this windows doesn't detects this drive and daemon-tool shows the error message.
                            Deactivating the virtual drive(marked yellow now) in the windows device manager and reactivating makes windows accept it and it runs like the first time after installation of daemon-tools. Actually any operation like reinstalling the driver in the device manager makes it run.
                            So as long as this bug remains just do as i have explained and your daemon-tool will work for one windows session. :idea:

                            Comment


                            • #15
                              I had the exact same problem with these specifications:

                              WinXP Prof. SP1
                              Celeron 1.7ghz
                              Nero 5.5.7.1
                              Daemon Tools 3.33

                              No SCSI drives at all :P

                              All I did was went to the control panel>system>hardware>device manager then down to SCSI and RAID Controllers where I only had one option which did have the yellow exclamation point, so I just disabled it, tried to run DAEMON-Tools again, got the same error, then I re-enabled it without getting the yellow exclamation mark again...

                              I don't know if it was fluke or not but you can try it...

                              Comment

                              Working...
                              X