Jump to content
larkin

Failure after updating to Win 10 1803

Recommended Posts

ImgBurn has been working normally until my company updated my computer to Win 10 1803. After that, I've been experiencing issues burning. I was able to burn a disc normally once following the update, then the next time I tried to burn a disc, I got an error:

"The system cannot find the file specified."

When I tried to burn again, I got a new error:

"Failed to Reserve Track! - Reason: No More Track Reservations Allowed"

Any further attempts to burn give the same track reservations error message. When I try burning after rebooting, I get the "cannot find the file specified" error, and then the track reservations error for all subsequent attempts until I reboot again.

IT tried Uninstalling/Reinstalling the drivers (along with a reboot), which allowed me to burn a disc normally once, then I get the same exact errors as above all over again. The IT rep tried fiddling with a bunch of the ImgBurn settings, following advice online, but nothing seemed to help.

I tried burning with the native Windows 10 burning tool, but my computer blue-screened partway into the burn. I've read that CMC MAG disks are poor quality disks, but I've been successfully using them for months before this problem arose.

Here's the log of one of my sessions today:

I 13:14:14 ImgBurn Version 2.5.8.0 started!
I 13:14:14 Microsoft Windows 8 Professional x64 Edition (6.2, Build 9200)
I 13:14:14 Total Physical Memory: 8,054,304 KiB  -  Available: 5,123,260 KiB
I 13:14:14 Initialising SPTI...
I 13:14:14 Searching for SCSI / ATAPI devices...
I 13:14:25 -> Drive 1 - Info: HL-DT-ST DVDRAM GP65NS60 PB01-10 (E:) (USB 2.0)
I 13:14:25 Found 1 DVD±RW/RAM!
I 13:15:12 Operation Started!
I 13:15:12 Building Image Tree...
I 13:15:16 Calculating Totals...
I 13:15:16 Preparing Image...
I 13:15:16 Contents: 1 File, 0 Folders
I 13:15:16 Content Type: Data
I 13:15:16 Data Type: MODE1/2048
I 13:15:16 File System(s): UDF (1.02)
I 13:15:16 Volume Label: Desktop
I 13:15:16 Size: 613,397 bytes
I 13:15:16 Sectors: 300
I 13:15:16 Image Size: 1,245,184 bytes
I 13:15:16 Image Sectors: 608
I 13:15:17 Operation Successfully Completed! - Duration: 00:00:04
I 13:15:17 Operation Started!
I 13:15:17 Source File: -==/\/[BUILD IMAGE]\/\==-
I 13:15:17 Source File Sectors: 608 (MODE1/2048)
I 13:15:17 Source File Size: 1,245,184 bytes
I 13:15:17 Source File Volume Identifier: Desktop
I 13:15:17 Source File Volume Set Identifier: 4F0969E600000257
I 13:15:17 Source File Application Identifier: ImgBurn v2.5.8.0
I 13:15:17 Source File Implementation Identifier: ImgBurn
I 13:15:17 Source File File System(s): UDF (1.02)
I 13:15:17 Destination Device: [0:0:0] HL-DT-ST DVDRAM GP65NS60 PB01 (E:) (USB)
I 13:15:17 Destination Media Type: DVD-R (Disc ID: CMC MAG. AM3)
I 13:15:17 Destination Media Supported Write Speeds: 4x, 8x
I 13:15:17 Destination Media Sectors: 2,297,888
I 13:15:17 Write Mode: DVD
I 13:15:17 Write Type: DAO
I 13:15:17 Write Speed: MAX
I 13:15:17 Link Size: Auto
I 13:15:17 Lock Volume: Yes
I 13:15:17 Test Mode: No
I 13:15:17 OPC: No
I 13:15:17 BURN-Proof: Enabled
I 13:15:17 Write Speed Successfully Set! - Effective: 11,080 KB/s (8x)
I 13:15:19 Filling Buffer... (80 MiB)
I 13:15:19 Writing LeadIn...
W 13:15:19 Failed to Write Sectors 0 - 31 - Reason: The system cannot find the file specified.
W 13:15:20 Retrying (1 of 20)...
W 13:15:20 Retry Failed - Reason: The system cannot find the file specified.
W 13:15:20 Retrying (2 of 20)...
W 13:15:20 Retry Failed - Reason: The system cannot find the file specified.
W 13:15:20 Retrying (3 of 20)...
W 13:15:20 Retry Failed - Reason: The system cannot find the file specified.
W 13:15:20 Retrying (4 of 20)...
W 13:15:20 Retry Failed - Reason: The system cannot find the file specified.
W 13:15:20 Retrying (5 of 20)...
W 13:15:20 Retry Failed - Reason: The system cannot find the file specified.
W 13:15:20 Retrying (6 of 20)...
W 13:15:20 Retry Failed - Reason: The system cannot find the file specified.
W 13:15:20 Retrying (7 of 20)...
W 13:15:20 Retry Failed - Reason: The system cannot find the file specified.
W 13:15:20 Retrying (8 of 20)...
W 13:15:20 Retry Failed - Reason: The system cannot find the file specified.
W 13:15:20 Retrying (9 of 20)...
W 13:15:20 Retry Failed - Reason: The system cannot find the file specified.
W 13:15:20 Retrying (10 of 20)...
W 13:15:20 Retry Failed - Reason: The system cannot find the file specified.
W 13:15:20 Retrying (11 of 20)...
W 13:15:20 Retry Failed - Reason: The system cannot find the file specified.
W 13:15:20 Retrying (12 of 20)...
W 13:15:20 Retry Failed - Reason: The system cannot find the file specified.
W 13:15:20 Retrying (13 of 20)...
W 13:15:20 Retry Failed - Reason: The system cannot find the file specified.
W 13:15:20 Retrying (14 of 20)...
W 13:15:20 Retry Failed - Reason: The system cannot find the file specified.
W 13:15:20 Retrying (15 of 20)...
W 13:15:20 Retry Failed - Reason: The system cannot find the file specified.
W 13:15:20 Retrying (16 of 20)...
W 13:15:20 Retry Failed - Reason: The system cannot find the file specified.
W 13:15:20 Retrying (17 of 20)...
W 13:15:20 Retry Failed - Reason: The system cannot find the file specified.
W 13:15:20 Retrying (18 of 20)...
W 13:15:20 Retry Failed - Reason: The system cannot find the file specified.
W 13:15:20 Retrying (19 of 20)...
W 13:15:20 Retry Failed - Reason: The system cannot find the file specified.
W 13:15:20 Retrying (20 of 20)...
W 13:15:20 Retry Failed - Reason: The system cannot find the file specified.
W 13:15:29 Retrying (21)...
W 13:15:29 Retry Failed - Reason: The system cannot find the file specified.
W 13:15:30 Retrying (22)...
W 13:15:30 Retry Failed - Reason: The system cannot find the file specified.
E 13:15:32 Failed to Write Sectors 0 - 31 - Reason: The system cannot find the file specified.
I 13:15:32 Synchronising Cache...
E 13:15:39 Failed to check for ImgBurn update!
E 13:15:45 Failed to Write Image!
E 13:15:45 Operation Failed! - Duration: 00:00:28
I 13:15:45 Average Write Rate: N/A - Maximum Write Rate: N/A
I 13:15:51 Operation Started!
I 13:15:51 Building Image Tree...
I 13:15:53 Calculating Totals...
I 13:15:53 Preparing Image...
I 13:15:53 Contents: 1 File, 0 Folders
I 13:15:53 Content Type: Data
I 13:15:53 Data Type: MODE1/2048
I 13:15:53 File System(s): UDF (1.02)
I 13:15:53 Volume Label: Desktop
I 13:15:53 Size: 613,397 bytes
I 13:15:53 Sectors: 300
I 13:15:53 Image Size: 1,245,184 bytes
I 13:15:53 Image Sectors: 608
I 13:15:54 Operation Successfully Completed! - Duration: 00:00:03
I 13:15:55 Operation Started!
I 13:15:55 Source File: -==/\/[BUILD IMAGE]\/\==-
I 13:15:55 Source File Sectors: 608 (MODE1/2048)
I 13:15:55 Source File Size: 1,245,184 bytes
I 13:15:55 Source File Volume Identifier: Desktop
I 13:15:55 Source File Volume Set Identifier: 4F0969F900000257
I 13:15:55 Source File Application Identifier: ImgBurn v2.5.8.0
I 13:15:55 Source File Implementation Identifier: ImgBurn
I 13:15:55 Source File File System(s): UDF (1.02)
I 13:15:55 Destination Device: [0:0:0] HL-DT-ST DVDRAM GP65NS60 PB01 (E:) (USB)
I 13:15:55 Destination Media Type: DVD-R (Disc ID: CMC MAG. AM3)
I 13:15:55 Destination Media Supported Write Speeds: 4x, 8x
I 13:15:55 Destination Media Sectors: 608
I 13:15:55 Write Mode: DVD
I 13:15:55 Write Type: DAO
I 13:15:55 Write Speed: MAX
I 13:15:55 Link Size: Auto
I 13:15:55 Lock Volume: Yes
I 13:15:55 Test Mode: No
I 13:15:55 OPC: No
I 13:15:55 BURN-Proof: Enabled
I 13:15:55 Write Speed Successfully Set! - Effective: 11,080 KB/s (8x)
E 13:16:01 Failed to Reserve Track! - Reason: No More Track Reservations Allowed
E 13:16:03 Operation Failed! - Duration: 00:00:08
I 13:16:03 Average Write Rate: N/A - Maximum Write Rate: N/A
I 13:16:05 Close Request Acknowledged
I 13:16:05 Closing Down...
I 13:16:05 Shutting down SPTI...
I 13:16:05 ImgBurn closed!

Any assistance would be greatly appreciated.

Share this post


Link to post
Share on other sites

I'd start by stop using that cheap crappy blanks type 'cmc mag am3'. I'd be willing to bet that's your problem right there

Sent from my Pixel 3 XL using Tapatalk

Share this post


Link to post
Share on other sites

I've been successfully using those disks for months, so unless they have some sort of interaction with the new version of Windows 10 update 1803, the disks are not the problem.

Share this post


Link to post
Share on other sites
4 minutes ago, Ch3vr0n said:

I'd start by stop using that cheap crappy blanks type 'cmc mag am3'. I'd be willing to bet that's your problem right there

Sent from my Pixel 3 XL using Tapatalk
 

I've been successfully using those disks for months, so unless they have some sort of interaction with the new version of Windows 10 update 1803, the disks are not the problem. And I have successfully burned after a driver install with the same disks.

Share this post


Link to post
Share on other sites

Yeah, what it looks like is happening, though I can't say for sure, is Windows is "forgetting" where the image file is for burning.  BSOD's attempting to write to external media are generally reserved for 1.) bad media or 2.) a fault in Windows.  Given how you were just updated to an admittedly older version of Windows 10, it sounds like the update messed something up.  Given how you said it was working before the update, I would think even using CMC media would not be the problem here.

 

You shouldn't be using CMC media to begin with, but if you want to really nail down the problem, trying getting some Verbatim DataLife Plus AZO DVD media (NOT Life Series you find in stores.  DataLife can only be found in online stores.) and see if the problem persists.  If it does, then you can be relatively sure it's some kind of Windows or hardware problem.  It could also just be your drive decided at that moment to just happen to die like my Pioneer did Wednesday night.  However, given how this happened just after updating Windows 10, that is the more likely culprit.

Share this post


Link to post
Share on other sites

W 13:15:19 Failed to Write Sectors 0 - 31 - Reason: The system cannot find the file specified.

For whatever reason, your machine is returning a really weird error when the program asks your drive to burn the sectors. That error is not from the drive, it's from the OS.

It could be a dodgy driver issue or something. Maybe try uninstalling the usb controller from within Device Manager (so it wipes out the controller, hubs and the devices connected to them), reboot and let Windows find it all again.

Share this post


Link to post
Share on other sites

×

Important Information

By using this site, you agree to our Terms of Use.