Hi TheArtful2342 ) !

I had similar problems with Memorex Disks even tough they looked clean.

I'm using an HP Pavillion dv9825nr Notebook PC, running Windows Vista Home Premium SP1+.
I also have an HP PhotoSmart C8180 All-In-One Printer.  Both have built-in LS Drives.
Everything has been running LSS fine since 4/08.

I use Memorex disks and also HP disks almost all the time, because they are the only ones I seem to find.

If I have any problems with labeling a disk, I clean the center (hub) of the disk before burning the LABEL side first.

I use the LS Template Labeler for the LABEL side and NERO 9 for the DATA side.

I had trouble with the first two spindles I bought.

One disk had a bad DATA side and another (Memorex) had to be re-cleaned in the center (hub) of the disk 3 times of 20 turns of the cleaner, but it burned successfully.

I've also fooled around a little with the LS Simple Labeler.

I've developed 259 Custom Templates (in 44 Collections + 5 Private Ones), 108 Images (in 12 Collections), 174 Icons, and 4 Test Background Images for the LS SL, and have shared them with 223 Forum Users.

Rev. 2010-04-24 1000 EDT

I'm using an HP Pavillion dv9825nr Notebook PC, running Windows Vista Home Premium SP1+.
I also have an HP PhotoSmart C8180 All-In-One Printer.  Both have built-in LS Drives.
Everything has been running LSS fine since 4/08.

I had 2 Instances of the LS TL running;
The one which had the highest percent done got a 4231 Error;
Both labeling processes stopped;
I rebooted the system several times;
I ran both the LS_Update and the Diagnostic Install in repair mode and rebooted the system again;
The DU would "Not Respond" until I popped the tray in my system out and pushed it back in;
The DU would not recognize the media in my printer's drive until I popped the tray out and pushed it back in;
The DU would not recognize the drive in my system until I told it to "Scan for LightScribe drives and media" again;
I tried to restart the First Instance (the one in my system)  and got a "(520)" Error saying there might be dirt or a smudge on the disk and to wipe it;
It gave me the options "Help" "Cancel Print" "Try Again";
The "Help" option brought up the "Troubleshooting" webpage;
I wiped the LABEL side (nothing had been burnt) and selected "Try Again";
The burning process started again;
I waited until the First Instance finished;
It finished successfully;
I restarted the Second Instance;
I got a "(4225)" Error;
It gave me the options "Help" "Cancel Print";
I selected "Cancel Print";
I restarted the Second Instance again;
It restarted successfully;
I waited until the Second Instance finished;
It finished successfully;
I started 2 new Instance again both running at the same time;
They both finished successfully;
I started a new First Instance when the Second Instance was at 40%;
The Second Instance finished successfully and was shut down;
The First Instance got another 4231 Error, but was left up until the Second Instance finished successfully;
Only a small portion (about 10%) of the label had been burned;
I rebooted the system and wiped the LABEL side surface;
I restarted the LS TL and selected the same LSL File and restarted the burning process;
It started burning and got beyond 10%;
It finished successfully.

CONCLUSION:
The effected disks were Memorex LightScribe V1.2;
The drives got "hung-up" possibly due to dirt or a smudge on the LABEL side surface;
Wiping the LABEL side surface with a dry cloth helped "fix" the burning problem;
As several Users on the Forum attest, it appears most of the problems in the LightScribe Template Labeler seem to happen in the burn process.

REV. 2009-11-30 0850 EST

I'm using an HP Pavillion dv9825nr Notebook PC, running Windows Vista Home Premium SP1+.
I also have an HP PhotoSmart C8180 All-In-One Printer.  Both have built-in LS Drives.
Everything has been running LSS fine since 4/08.

I was attempting to burn a simple 2 Arc Text Item Label.
I received a 4231 Error at 37% and had to "Cancel Print."
The "Simulated Visual Label Progress (estimate)" showed approx. 50%.
The process started again.
The process completed successfully and the label was OK.

REV. 2009-12-17 1235 EST