dvdfab crashing computer getting BSOD

[kdpooh]

Didn't work for me
I still got the BSOD with the auto-eject disabled.

didnt work for me either. As soon as i manually ejected i got the BSOD.......:

[DSH8879]

As i stated earlier I have a new toshiba satellite and the only way I am able to get arounnd the BSoD is to rip and burn in a 2 stage process. Rip to hard drive and then write from hard drive to disc. hope this helps

[Gummigutta]

Seen on a Swedish forum about the ejecting causing problems, that a BIOS update was the fix. Not sure that's relevant here.

[extreme1980]

pleasee try this for us pleaseee

why is it that dvdfab 7 works flawless on my new dv6 laptop but newest 8.1.5 ect... doesnt couldnt the makers of fab use lets say dvdfab 5 version as a core for lets says dvdfab 9 figure of speech name it beta for us BSOD ppl to try something has to fix this i say again dvdfab 7 works perfect on dv6 laptop no BSOD how is this possible i encourage dvdfab team to at least look into this method even if we dont get bluray support i just want newest decrypt/security features added to rip lets say smurfs or newer with a new
dvdfab 9 beta -BSOD- test model made from the dvdfab 7 core seems like it would have to work as dvdfab 7 works perfect.

any one reading this try dvd fab 7 and see if you get BSOD on your new laptops and report here if it works for you try a older dvd to rip lets say
-carlitos way- or something older just to see if you get BSOD or not im
betting you dont again makers try this for us make a new dvdfab 9 out of dvdfab7 core so we can test it pleaseeeeeee. thanx for your time and listening

[unknownbluray]

Could this be due to riplock? Just curious I know its suppose to just slow down reading the BD but maybe the manufactures of certain drives have made it so it does stop reading completely and BSOD's it right away? I would say check you memory timing but its basically all laptops having issues. And one poster said they are using an external BD reader and having success, so I bet it doesnt have riplock.

[extreme1980]

but as i said not doing bluray could care less about bluray huge rips and quality is crap. im using standard dvd to to rip and as i said dvdfab 7 works so i dont think riplock has any thing to do with BSOD i think its how dvdfab 8-qt is made any thing from dvdfab 1 -2-3-4-5-6-7 all work perfect on my laptop that goes BSOD on dvdfab 8 and up its something thats in dvdfab 8 and up im thinking and not ALL these pc thats why i was hoping other users that were getting BSOD could try to use dvdfab 5 or 7 and see if they still get BSOD and post there results and then maybe fab can make us a build from dvdfab 7 with all upgrades to try hope this makes sense and others please post your finding using dvdfab 7 .

[E*C*H*O]

I would try copying an older DVD, but I have no idea how to download an old version of DVDFab. Can somebody advise?

[signals]

Try v8.0.8.5, you can still download it from the DVDFab website, on the download page. Other older versions are not officially supported. If you download them from somewhere else, do so at your own risk.

[rl0822]

BSOD

Hi kdpooh
I understand your frustration.
The reason that there is not a solution to the problem is that it can not be reproduced by the developers.
CBR929

Hey,

All the developers have to do is buy a Toshiba Protege. I reproduced it on two new Proteges and now I have a third one and have decided to pursue the only option which is to rip to the hard drive and then write the movie to the DVD. Everyone has the two step process down as a work around. Sucks, but works and I do love the Protege size and weight, just hate the two step process when using DVDFab

Ray

[maineman]

Hey,

All the developers have to do is buy a Toshiba Protege. I reproduced it on two new Proteges and now I have a third one and have decided to pursue the only option which is to rip to the hard drive and then write the movie to the DVD. Everyone has the two step process down as a work around. Sucks, but works and I do love the Protege size and weight, just hate the two step process when using DVDFab

Ray

Well, maybe not.
I certainly don't mean to discredit or disrespect anyone's post, but personally, I have had a much different experience.

I recently inherited my daughter's Toshiba Portege R705.
Both she and it were involved in an accident. She was hit by a car while crossing the street in front of Tufts med school...good place to get hit ...if you can choose.

She's doing great and only missed a couple days.
However, the laptop was renderd glitchy and unreliable.
We got her a new one and I resurrected the "survivor"
Easy, peasy, just did a new install to factory specs from the recovery partition on the hdd.

I just ripped and burned the standard dvd, R1, The Lion King with 8163 Qt.
Did this with opening Fab only once (I had to physically swap the original and blank when prompted since I'm using only the matshita internal drive),
but again, I did not do the 2-step work-around that other users have had to do.

I did use Img as my default burn engine, but so have others without success.
I did not set up AWS, but it behaved and burned at a max of 8X.

Dunno what this means to the developers of Fab and owners of these Toshiba laptops, but I experienced no crash, no issues at all.

DVDFab 8.1.6.3 (2012/02/17 06:59:04)

0m 00.85s: Qt Translator file load success
0m 00.92s: Load config successful.
0m 00.92s: Init profile data driver sucessful.
0m 03.51s: Init GPU settings sucessful.
0m 03.51s: option dvd2dvd 1 dvd2mobile 1 bluray2bluray 1 bd2mobile 1 bd23d 1 bd2dvd 1 file2dvd 1 file2bluray 1 file2mobile 1 filemover 1
0m 03.51s: dvd2dvd:dvd2mobile:blu-ray2blu-ray:blu-ray2mobile:blu-ray23d:blu-ray2dvd:file2mobile:file2dvd:file2bluray:
0m 03.88s: Config ExBar successful.
0m 03.88s: dvd2dvd have 3 elements.
0m 03.97s: dvd2mobile have 28 elements.
0m 05.31s: blu-ray2blu-ray have 4 elements.
0m 05.56s: blu-ray2mobile have 17 elements.
0m 06.27s: blu-ray23d have 7 elements.
0m 06.48s: blu-ray2dvd have 1 elements.
0m 06.53s: file2mobile have 27 elements.
0m 07.55s: file2dvd have 1 elements.
0m 07.58s: file2bluray have 1 elements.
0m 07.95s: Config work ui controls successful.
0m 20.93s: Init burn engine successful.
0m 20.96s: StartNotify successful.
0m 21.15s: detected dvd
0m 21.18s: drive D
0m 21.18s: dvd type 1
0m 21.18s: volume label LKD-0N-NW1.1_DES
0m 21.28s: got copyright 1 f6
0m 23.32s: got udf/iso
0m 28.35s: got discinfo
0m 28.36s: pathplayer enabled
0m 11.25s: got dvdinfo
0m 11.25s: opened dvd
0m 18.46s: detected dvd
0m 18.49s: drive D
0m 18.57s: dvd type 1
0m 18.57s: volume label
0m 13.52s: failed to report agid: sensekey 00 asc 00 acsq 00
0m 13.72s: failed to report agid: sensekey 00 asc 00 acsq 00
0m 13.92s: failed to report agid: sensekey 00 asc 00 acsq 00
0m 14.13s: got copyright 0 0
0m 15.83s: got udf/iso
0m 16.75s: got discinfo
0m 16.75s: pathplayer enabled
0m 17.25s: no main title, turn off pathplayer
0m 17.25s: failed to open disc 1


I can't explain the failed to report or fail to open.
The analyzing phase took 1-2 minutes to complete, but this isn't that unusual with PP enabled and certain dvds.
It analyzed and ripped without problems


I 07:20:26 ImgBurn Version 2.5.6.0 started!
I 07:20:26 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7600)
I 07:20:26 Total Physical Memory: 3,916,212 KB - Available: 2,176,568 KB
I 07:20:26 Initialising SPTI...
I 07:20:26 Searching for SCSI / ATAPI devices...
I 07:20:26 -> Drive 1 - Info: MATSHITA DVD-RAM UJ892ES 1.20 (D (SATA)
I 07:20:26 Found 1 DVD±RW/RAM!
I 07:20:26 Operation Started!
I 07:20:26 Building Image Tree...
I 07:20:26 Checking Directory Depth...
I 07:20:26 Calculating Totals...
I 07:20:27 Preparing Image...
I 07:20:27 Checking Path Length...
I 07:20:27 Contents: 8 Files, 2 Folders
I 07:20:27 Content Type: DVD Video
I 07:20:27 Data Type: MODE1/2048
I 07:20:27 File System(s): ISO9660, UDF (1.02)
I 07:20:27 Volume Label: LKD-0N-NW1.1_DES
I 07:20:27 IFO/BUP 32K Padding: Enabled
I 07:20:27 Region Code: 1, 2, 3, 4, 5, 6, 7, 8
I 07:20:27 TV System: NTSC
I 07:20:27 Size: 4,272,041,984 bytes
I 07:20:27 Sectors: 2,085,958
I 07:20:27 Image Size: 4,272,652,288 bytes
I 07:20:27 Image Sectors: 2,086,256
I 07:20:27 Operation Successfully Completed! - Duration: 00:00:00
I 07:20:27 Operation Started!
I 07:20:27 Source File: -==/\/[BUILD IMAGE]\/\==-
I 07:20:27 Source File Sectors: 2,086,256 (MODE1/2048)
I 07:20:27 Source File Size: 4,272,652,288 bytes
I 07:20:27 Source File Volume Identifier: LKD-0N-NW1.1_DES
I 07:20:27 Source File Volume Set Identifier: 40513A8D001FD56C
I 07:20:27 Source File Application Identifier: IMGBURN V2.5.6.0 - THE ULTIMATE IMAGE BURNER!
I 07:20:27 Source File Implementation Identifier: ImgBurn
I 07:20:27 Source File File System(s): ISO9660, UDF (1.02)
I 07:20:27 Destination Device: [1:0:0] MATSHITA DVD-RAM UJ892ES 1.20 (D (SATA)
I 07:20:27 Destination Media Type: DVD+R (Disc ID: MCC-004-00)
I 07:20:27 Destination Media Supported Write Speeds: 2.4x, 4x, 6x, 8x
I 07:20:27 Destination Media Sectors: 2,295,104
I 07:20:27 Write Mode: DVD
I 07:20:27 Write Type: DAO
I 07:20:27 Write Speed: MAX
I 07:20:27 DVD+R Reserve Track: No
I 07:20:27 Link Size: Auto
I 07:20:27 Lock Volume: Yes
I 07:20:27 Test Mode: No
I 07:20:27 OPC: No
I 07:20:27 BURN-Proof: Enabled
I 07:20:27 Write Speed Successfully Set! - Effective: 11,080 KB/s (8x)
I 07:20:28 Filling Buffer... (40 MB)
I 07:20:29 Writing LeadIn...
I 07:20:44 Writing Session 1 of 1... (1 Track, LBA: 0 - 2086255)
I 07:20:44 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 2086255)
I 07:30:13 Synchronising Cache...
I 07:30:16 Closing Track...
I 07:30:17 Finalising Disc...
I 07:30:33 Exporting Graph Data...
I 07:30:33 Graph Data File: C:\Users\Tom\AppData\Roaming\ImgBurn\Graph Data Files\MATSHITA_DVD-RAM_UJ892ES_1.20_FRIDAY-FEBRUARY-17-2012_7-20_AM_MCC-004-00_MAX.ibg
I 07:30:33 Export Successfully Completed!
I 07:30:33 Operation Successfully Completed! - Duration: 00:10:05
I 07:30:33 Average Write Rate: 7,345 KB/s (5.3x) - Maximum Write Rate: 10,798 KB/s (7.8x)
I 07:30:33 Close Request Acknowledged
I 07:30:33 Closing Down...
I 07:30:34 Shutting down SPTI...
I 07:30:34 ImgBurn closed!

[TnVmax]

Maineman,
Does you Protege have BluRay burning capability?

[maineman]

Maineman,
Does you Protege have BluRay burning capability?

Nope, just the factory installed MATSHITA DVD-RAM UJ892ES 1.20.
I know the OP, as well as others, were talking BD, but it seems a number of users are experiencing the same crash with standard dvds.

Sorry for the confusion

[TnVmax]

Nope, just the factory installed MATSHITA DVD-RAM UJ892ES 1.20.
I know the OP, as well as others, were talking BD, but it seems a number of users are experiencing the same crash with standard dvds.

Sorry for the confusion

I was hoping to narrow down the hardware a little more.
(Mine's a Satellite with BluRay read/burn)

[maineman]

I was hoping to narrow down the hardware a little more.
(Mine's a Satellite with BluRay read/burn)

Yeah, "you guys" must be tearing your hair out over this one.

I never did see where any of the Beijing team trialed a toshiba like yours.
Maybe I missed it, but it'd sure be helpful.
It would also be useful to hear from someone with a Portege and internal BD that cannot reproduce this issue with BD's.

I haven't burned more than a handful of discs in the last 2 years and I have no plans to use the Toshiba with Fab...still it's curiouser and curioser.

Do you experience any problems with standard dvds?

[TnVmax]

Yeah, "you guys" must be tearing your hair out over this one.

I never did see where any of the Beijing team trialed a toshiba like yours.
Maybe I missed it, but it'd sure be helpful.
It would also be useful to hear from someone with a Portege and internal BD that cannot reproduce this issue with BD's.

I haven't burned more than a handful of discs in the last 2 years and I have no plans to use the Toshiba with Fab...still it's curiouser and curioser.

Do you experience any problems with standard dvds?

Yep, it doesn't seem to matter what it's reading or writing. It BSOD's the instant it ejects the drawer (even if the "don't eject the disk" is checked).
However, out of frustration, I bought an external Plextor BluRay burner (USB3.0), and I read the original with my Toshiba's internal drive, and burn to the external drive, and it works fine that way. Just aggravating that I spec'd out this Satellite to have an internal BluRay burner (wasted expense) then had to buy an external burner (another expense), and the aggravation of having to get out the external burner, plug into the wall, hook up the USB3.0 cable...