Announcement

Collapse
No announcement yet.

BSOD when unmounting & removing DT Lite

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

  • BSOD when unmounting & removing DT Lite

    I have an HP pavillion laptop running on Vista 32.

    After havind D/Led and installed DT Lite 4, all went fine up to a certain pont when BSOD started to appear from time to time when unmounting virtual units. On occasion it took me to manually remove the virtual USB from system.

    Finally, DT refused to mount whatsoever unit/image.

    I tried to re-install it but BSOD appeared when uninstalling (actually when the uninstall program runs some kind of registry modding application).

    I tried uninstall DT by miself (both via the control panel and the DT sidebar menu) but it failed, BSOD again.

    Please, don't aske me to post the minidump here - my PC can't read dmp files and I don't want to install some other weird MS software in order to do that. But I can send it by email if you provide me an address.

    Many thanks to all who will be of help to a useless Italian girl.

    Bye

  • #2
    You don't have to post the contents of minidump files, you only need to upload it here either as an attachment (zip it first) or upload it to a file hoster like megaupload.com.

    Also which exact version of DT Lite did you install?
    DT Lite creates virtual SCSI drives, not virtual USB drives.
    Make something idiot proof, but then they just make a better idiot
    Peace Through Power

    Comment


    • #3
      Hi Blaz,

      I'm actually on DT Lite 4402-0131, I believe it's the latest release... as per your suggestion I attached a zip file containing the last minidump.

      As you probably have already understood, I'm not really into DT, usb & similar issues.

      When my DT Lite started giving me troubles while unmounting units, I searched the web & found a hint to try and unmount things from the system folder... there I found something that sounded like "virtual", "usb" and "daemon" (but I may be mistakening some word, my memory isn't that good either) and removed it.

      The strange thing is that this seemed to work, since every time after doing that DT allowed me unmounting the unit w/o BSODs... or I was just lucky ;o)

      I really appreciate your help, ty so much.

      Sy
      Attached Files

      Comment


      • #4
        Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1be6 )

        Please try to enable Advanced Emulation in Settings -> Advanced, this will remove the usage of above Simple Driver and then please try again.

        Note in current DT Pro there is a newer dtsoftbus01.sys included and therefore the BSOD may be already fixed.
        Make something idiot proof, but then they just make a better idiot
        Peace Through Power

        Comment


        • #5
          Hmm... it didn't work. I set Adv Emulation to Advanced, DT started installing SPTD, but after a while BSOD again.

          And this time it was a hard one, upon restarting Vista went to resuming mode, worked on it for a long while, then told me that resume had failed! But at the second restart Vista loaded correctly.

          No minidump file was generated this time.


          Sy

          Comment


          • #6
            Please try to install latest SPTD from DuplexSecure - Downloads and then reboot and retry with Advanced Emulation.
            Make something idiot proof, but then they just make a better idiot
            Peace Through Power

            Comment


            • #7
              I downloaded SPTDinst-v178-x86.exe, the version suitable to Vista 32, tried to install it but without success. It says that SPTDinst-v178-x86.exe isn't a Win32 valid application.

              Any guess?

              Sy

              Comment


              • #8
                You have to redownload the setup.
                Make something idiot proof, but then they just make a better idiot
                Peace Through Power

                Comment


                • #9
                  I did it, and now everything seems OK! I tried mounting & unmounting several times, and no BSODs!!

                  Ty so much, Blaz, you're my fav German helper

                  SY

                  Comment


                  • #10
                    I'm getting the same issue as well with it BSOD upon removal of the device.

                    Sorry I wasnt able to upload it as a zip file the page kept on timing out so here it is unpacked.


                    ************************************************** *****************************
                    * *
                    * Bugcheck Analysis *
                    * *
                    ************************************************** *****************************

                    Use !analyze -v to get detailed debugging information.

                    BugCheck 3B, {c0000005, fffff80002e7bd40, fffff8800dc37d90, 0}

                    Probably caused by : ntkrnlmp.exe ( nt!IofCallDriver+50 )

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

                    2: kd> !analyze -v
                    ************************************************** *****************************
                    * *
                    * Bugcheck Analysis *
                    * *
                    ************************************************** *****************************

                    SYSTEM_SERVICE_EXCEPTION (3b)
                    An exception happened while executing a system service routine.
                    Arguments:
                    Arg1: 00000000c0000005, Exception code that caused the bugcheck
                    Arg2: fffff80002e7bd40, Address of the instruction which caused the bugcheck
                    Arg3: fffff8800dc37d90, Address of the context record for the exception that caused the bugcheck
                    Arg4: 0000000000000000, zero.

                    Debugging Details:
                    ------------------


                    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

                    FAULTING_IP:
                    nt!IofCallDriver+50
                    fffff800`02e7bd40 49ff64c070 jmp qword ptr [r8+rax*8+70h]

                    CONTEXT: fffff8800dc37d90 -- (.cxr 0xfffff8800dc37d90)
                    rax=0000000000000002 rbx=fffffa800c699120 rcx=fffffa800a60d080
                    rdx=fffffa800c699120 rsi=fffffa800c6993a0 rdi=fffffa800b354030
                    rip=fffff80002e7bd40 rsp=fffff8800dc38768 rbp=fffffa8007199d20
                    r8=0000000000000000 r9=0000000000000002 r10=fffff88002f64fa0
                    r11=fffffa800a140010 r12=fffffa800c699300 r13=0000000000000000
                    r14=fffffa800c6993a0 r15=fffffa8007199e70
                    iopl=0 nv up ei ng nz na pe nc
                    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
                    nt!IofCallDriver+0x50:
                    fffff800`02e7bd40 49ff64c070 jmp qword ptr [r8+rax*8+70h] ds:002b:00000000`00000080=????????????????
                    Resetting default scope

                    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

                    BUGCHECK_STR: 0x3B

                    PROCESS_NAME: DTShellHlp.exe

                    CURRENT_IRQL: 0

                    LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002e7bd40

                    STACK_TEXT:
                    fffff880`0dc38768 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x50


                    FOLLOWUP_IP:
                    nt!IofCallDriver+50
                    fffff800`02e7bd40 49ff64c070 jmp qword ptr [r8+rax*8+70h]

                    SYMBOL_STACK_INDEX: 0

                    SYMBOL_NAME: nt!IofCallDriver+50

                    FOLLOWUP_NAME: MachineOwner

                    MODULE_NAME: nt

                    IMAGE_NAME: ntkrnlmp.exe

                    DEBUG_FLR_IMAGE_TIMESTAMP: 4fa38fe2

                    STACK_COMMAND: .cxr 0xfffff8800dc37d90 ; kb

                    FAILURE_BUCKET_ID: X64_0x3B_nt!IofCallDriver+50

                    BUCKET_ID: X64_0x3B_nt!IofCallDriver+50

                    Followup: MachineOwner

                    Comment

                    Working...
                    X