dvdfab crashing computer getting BSOD

[DSH8879]

just bought toshiba satellite 755 windows 7 home premium with an i7. Just downloaded the 8.1.3.3, and as soon as 100% of dvd is temporarily copied the dvd burner ejects it and out comes the BSoD, i tried running earlierversions off an external harddrive which now are causing the same BSoD. What is going on?!!

[CBR929]

Hi alanbs
Please try the latest version found here

Have you also tried disabling Path Player?
You should not have to do this but give it a try

Open Fab Click the Green √ top right > Protection > Path Player click Disable Path Player click OK restart Fab and try again, just remember to set it back to Always Enabled.

If you want to use ImgBurn you will find instructions in the link in my signature on setting it up.
Remember to set up the AWS and burn at 1/2 the rated speed of your disc.
CBR929

[alanbs]

@rl0822 It is happening to new laptops that have BD drives. The brand doesn't seem to matter or specifics have not been isolated.

I don't think this is getting reported properly as most people first think it is something wrong with their new laptop, as the same DVDfab program version is working fine on their other machine(s) with a DVD drive.

Thanks to your posting and others, I will try the ImgBurn software instead of VSO. I've never had issues with using VSO before.

I hate having to do work-arounds.

Lets keep our fingers crossed that the engineers are getting a handle on what is wrong.

[alanbs]

The most recent internal log indicates that the source disc was never opened, so it has nothing to do with the burn part of the process.

Are you refering to the logs attached to #93? Where the source was the HDD copy created in a prior DVDcopy from the DVD to the HDD, and the write operation to the DVD completed successfully then BSOD occured?

[rl0822]

IRQL

I have the same issue and originally thought it was the laptop that I had purchased and returned it. After reading more posts on the net, I realize now that there is an issue.I have the same issue as everyone else out there, when it finishes the copy and it's ready to start the burn process, I get the BSOD every time.

Some sites said that there is an issue with vso and to try imgburn, but I use nero and it does it everyone; I;m afraid. Interesting enough if you let the copy done to the hard disk and then do a write, it only fails under vso burning engine, but not under imgburn or nero.

I matched the settings from my old computer to the new laptop and they are identical, so frustrated with this.

I love this product and wish that it would do it like it used to and run ask for the DVD to be loaded and then write it, but I have to work around it with a hard disk copy then a write.

Could it be a compatibility issue with the dvd drive? Most of the people that have posted on sites own toshibas, which is my machine as well and if the manufacturer uses the same type of dvd drives/drivers maybe that is it.

Any new insight will be helpful.

Thanks

Ray

[signals]

The most recent internal log indicates that the source disc was never opened, so it has nothing to do with the burn part of the process.

[alanbs]

Well, anyway. So I tried the write to disk as destination, and then write to DVD as a seperate operation. This to isolate the read operation from the write operation on the built-in BDRW.
Using the disk as destination was fine. However, when I did the write to DVD on the BDRW the laptop BSOD again. This was after the write operation was completed/finalized.
It was like DVDfab was doing closing/cleanup after being done with the write and then it happend.
Attached are mini and standard memory dumps, and the DVDfab logs.
At this point I'm feeling that DVDfab is not doing proper close/release instructions to the BD drive and it is causing the driver to fault and go BSOD.
I wish the engineers good luck in finding the cure. Until then i'll be using my old pc with only a DVD drive to do my backups on.

[alanbs]

Anybody following up on this after I posted the dumps and logs on 11/11?

[alanbs]

Would you please post the Memory.dump file where it is in %SystemRoot%\Minidump
And sure that your system have set Kernel memory dump.
How to check this?
Please do below steps: run sysdm.cpl -> Advanced -> Settings(Startup and Recovery) -> Kernel memory dump (Write debugging info).

Thanks,
Potti

Hello 1st, Thank you for your assistance. Attached are the Win7 BSOD files created at the time of the error. The Kernel mem dmp (Minidump) and also a sysdata.xml file (since the file upload system doesn't allow xml this size I appended .dmp to the file). I also included the DVDfab internal and vso logs.
Best regards, ALANBS

[Potti]

Would you please post the Memory.dump file where it is in %SystemRoot%\Minidump
And sure that your system have set Kernel memory dump.
How to check this?
Please do below steps: run sysdm.cpl -> Advanced -> Settings(Startup and Recovery) -> Kernel memory dump (Write debugging info).

Thanks,
Potti

[GregiBoy]

I would suggest it is some driver or hardware incompatibility with all the internal drives, ie something non-standard.

[E*C*H*O]

When your computer gets fixed!!!

Huh? Many different laptops all brand new with bluray drives. It's not a matter of needing to fix the computer.

alanbs,

I am also able to burn to an external USB drive, but it BSOD's if I try to copy and burn with the internal drive.

I haven't tried to see what would happen if I copy and burn with just the external drive. I wonder what would happen then?

[GregiBoy]

When your computer gets fixed!!!

[scout]

a guy i work with talked good about dvdfab so i got it to try out and have not been able to complete a dvd clone on my laptop everytime the disc ejects i get the BSOD also tech support hasnt been much help.

any idea when this is going to get fixed ???

[alanbs]

If I use the internal burner, it BSOD's when the drive ejects to swap in a blank... However, If I use a USB external burner, no BSOD. Wierd...

Hmm... that seems to support the theory that the optical drive is not being released and attached (driver accessed?) when only one optical drive is used for both the source and the destination. That release and attach scenario doesn't need to happen when using different optical drives for source and destination. Or if it does happen it is not for the same one and therefore doesn't find the drive already in use and unaccessible.
I'm sure the programmers at Fengtao will get this figured out. I've been loving DVDFAB since 2007 and they always come through no matter what mysteries are.