LIGHTNING UK!

Really? I just googled 'rapid storage technology 10.8' and the first result was the download page on Intel's website. https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=20768

That's correct, those options will not work with Pioneer drives.

Ok, it uses the H57 chipset. Try loading on the v10.8 rapid storage tech driver then, that's the one I'm using. Check for motherboard bios updates too.

Download CPU-Z, run it and switch to the 'Mainboard' tab. Take a screenshot of it and post it please. http://www.cpuid.com/softwares/cpu-z.html

It doesn't really matter, it'll fail to send it to that drive anyway and you'll be left trying to burn an image onto a disc that isn't big enough for it.

What version is on there now? You aren't getting the real error from the drive, it's being swallowed up by Windows / the drivers. Which chipset does your motherboard actually use? Do you know which series it is? Z68, Z77, Z87 etc?

You'll have to buy the right hardware for burning those oversized images properly.

Then you should try the other suggestions.

From Intel's (download) website.

It isn't, no.

OpenCandy is an advertising plugin for installers. http://www.opencandy.com/

Try some different versions of the Intel rapid storage technology drivers.

It's probably due to the controller you've attached the drive to and its drivers. Right click the drive selection box when you're in Write mode and select 'Family Tree'. Close the box that comes up and then copy + paste everything from the Log window please.

You don't need to do anything manually, the program takes care of it all automatically. Post a log of you burning and verifying a DVD+R DL disc.

It doesn't pop up adverts. OpenCandy inserts a page (or two... or maybe none) in the installation wizard offering you a 3rd party app. Accept the offer(s) or decline it(them), the choice is yours. If you decline it(them), you'll only get ImgBurn and that is 100% clean.

From what I've seen in other people's log files, the booktype stuff seems to work ok on DVD+R DL discs. What are you trying to burn / booktype to DVD-ROM?

Try burning faster. If that fails, clean the drive with a cleaning disc. If that fails, buy some different discs or another drive.

Sorry, no. It does these things in a loop and you're asking for a user specific request here really.

You're getting a semaphore timeout... which is then causing windows to disconnect the drive. There aren't really any settings to get around this, it's a hardware issue (between the USB ports and your adapter). Try other USB ports, cables and adapters.

Your drive appears to have issues with burning those discs. That could just be at 4x, or it may not really like them at all. You could try enabling the 'Perform OPC Before Write' option in the settings on the 'Write' tab to see if that makes a difference. Failing that, buy some disc using a different MID/dye (not more 'CMCMAG-BA5-000' ones).

Your 2nd suggestion (editing the size of single layer media) is the right one big_duggy.

Can you look at the CD-TEXT info of the burnt disc in ImgBurn please? Go into Read mode and click on the little 'View Media Information' button in the Source box. See if it shows the correct info where dBpoweramp isn't.

If you haven't already done so, please revert the settings to their default values (Tools -> Settings -> Defaults) or uninstall+reinstall the program. Can I assume your drive D: is meant to be your burner? How is it connected to the PC? Sata? USB?

There will be more virtualallocs going on when using build mode as there's a buffer for reading in the files and one for data going to the drive. Plus more memory is being used for handling the info about the files you're burning - and don't forget it's only a 32bit application. Have you (or can you, please) try what I said in my previous reply? After that, we'd have to examine a few things in Task Manager at the point when that error box is on the screen.

VirtualAlloc is the Windows API function call being used and you can see the error Windows is returning. Regardless of how much memory you have, you (we) can only go by what you're being told. Maybe try searching Google to find out why VirtualAlloc might fail like that when there should be enough memory. Can I assume the 'amount of I/O buffer selected' does actually change as you change the sliders? I only ask because there are a few different buffer related ones in the settings and they'll all come into play at different times within the program flow. If in doubt, revert the settings to their default values. You should also try running the program in safe mode - some other app may be causing the issue (A/V or whatever). Oh and don't run it as admin, run it as a normal user (don't elevate).