You are viewing our Forum Archives. To view or take place in current topics click here.
Iso burning error
Posted:

Iso burning errorPosted:

10mejia
  • Challenger
Status: Offline
Joined: May 30, 201014Year Member
Posts: 121
Reputation Power: 4
Status: Offline
Joined: May 30, 201014Year Member
Posts: 121
Reputation Power: 4
I need help with imgburn, while it verifies the disk i get this error at 59%
[ Register or Signin to view external links. ]
It continues to happen even after i hit continue. Please help!
EDIT- this is the log

W 20:13:30 Failed to Read Sector 2259632 - Reason: Timeout on Logical Unit
W 20:13:43 Retrying (1)...
W 20:13:52 Retry Failed - Reason: Timeout on Logical Unit
W 20:13:54 Retrying (2)...
W 20:14:03 Retry Failed - Reason: Timeout on Logical Unit
W 20:14:11 Retrying (3)...
W 20:14:20 Retry Failed - Reason: Timeout on Logical Unit
W 20:14:22 Retrying (4)...
W 20:14:30 Retry Failed - Reason: Timeout on Logical Unit
W 20:14:46 Failed to Read Sector 2259632 - Reason: Timeout on Logical Unit
W 20:14:54 Failed to Read Sector 2259633 - Reason: Timeout on Logical Unit
W 20:16:14 Failed to Read Sector 2259633 - Reason: Timeout on Logical Unit
W 20:16:25 Failed to Read Sector 2259634 - Reason: Timeout on Logical Unit
W 20:17:30 Retrying (1)...
W 20:17:39 Retry Failed - Reason: Timeout on Logical Unit
W 20:19:12 Failed to Read Sector 2259634 - Reason: Timeout on Logical Unit
W 20:19:23 Failed to Read Sector 2259635 - Reason: Timeout on Logical Unit
W 20:19:32 Failed to Read Sector 2259635 - Reason: Timeout on Logical Unit
W 20:19:41 Failed to Read Sector 2259636 - Reason: Timeout on Logical Unit
W 20:19:49 Failed to Read Sector 2259636 - Reason: Timeout on Logical Unit
W 20:20:01 Failed to Read Sector 2259637 - Reason: Timeout on Logical Unit
W 20:20:01 Failed to Read Sector 2259637 - Reason: Timeout on Logical Unit
W 20:20:10 Failed to Read Sector 2259638 - Reason: Timeout on Logical Unit
W 20:20:10 Failed to Read Sector 2259638 - Reason: Timeout on Logical Unit
W 20:20:20 Failed to Read Sector 2259685 - Reason: Timeout on Logical Unit
W 20:20:20 Failed to Read Sector 2259685 - Reason: Timeout on Logical Unit
W 20:20:29 Failed to Read Sector 2259686 - Reason: Timeout on Logical Unit
W 20:20:29 Failed to Read Sector 2259686 - Reason: Timeout on Logical Unit
W 20:20:38 Failed to Read Sector 2259687 - Reason: Timeout on Logical Unit
W 20:20:38 Failed to Read Sector 2259687 - Reason: Timeout on Logical Unit
W 20:20:46 Failed to Read Sector 2259688 - Reason: Timeout on Logical Unit
W 20:20:46 Failed to Read Sector 2259688 - Reason: Timeout on Logical Unit
W 20:20:55 Failed to Read Sector 2259689 - Reason: Timeout on Logical Unit
W 20:20:55 Failed to Read Sector 2259689 - Reason: Timeout on Logical Unit
W 20:21:04 Failed to Read Sector 2259690 - Reason: Timeout on Logical Unit
W 20:21:04 Failed to Read Sector 2259690 - Reason: Timeout on Logical Unit
W 20:21:13 Failed to Read Sector 2259691 - Reason: Timeout on Logical Unit
W 20:21:13 Failed to Read Sector 2259691 - Reason: Timeout on Logical Unit
W 20:21:22 Failed to Read Sector 2259692 - Reason: Timeout on Logical Unit
W 20:21:22 Failed to Read Sector 2259692 - Reason: Timeout on Logical Unit
W 20:21:31 Failed to Read Sector 2259693 - Reason: Timeout on Logical Unit
W 20:21:31 Failed to Read Sector 2259693 - Reason: Timeout on Logical Unit
W 20:21:44 Failed to Read Sector 2259744 - Reason: Timeout on Logical Unit
W 20:21:44 Failed to Read Sector 2259744 - Reason: Timeout on Logical Unit
W 20:21:53 Failed to Read Sector 2259745 - Reason: Timeout on Logical Unit
W 20:21:53 Failed to Read Sector 2259745 - Reason: Timeout on Logical Unit
W 20:22:02 Failed to Read Sector 2259746 - Reason: Timeout on Logical Unit
W 20:22:02 Failed to Read Sector 2259746 - Reason: Timeout on Logical Unit
W 20:22:11 Failed to Read Sector 2259747 - Reason: Timeout on Logical Unit
W 20:22:11 Failed to Read Sector 2259747 - Reason: Timeout on Logical Unit
W 20:22:19 Failed to Read Sector 2259748 - Reason: Timeout on Logical Unit
W 20:22:19 Failed to Read Sector 2259748 - Reason: Timeout on Logical Unit
W 20:22:28 Failed to Read Sector 2259749 - Reason: Timeout on Logical Unit
W 20:22:28 Failed to Read Sector 2259749 - Reason: Timeout on Logical Unit


Last edited by 10mejia ; edited 1 time in total
#2. Posted:
AskingAlexandria
  • TTG Senior
Status: Offline
Joined: Mar 02, 201113Year Member
Posts: 1,455
Reputation Power: 64
Status: Offline
Joined: Mar 02, 201113Year Member
Posts: 1,455
Reputation Power: 64
are you burning it to a disk or your PCs harddrive?
#3. Posted:
xBeastly123
  • Ladder Climber
Status: Offline
Joined: Mar 14, 201113Year Member
Posts: 318
Reputation Power: 16
Status: Offline
Joined: Mar 14, 201113Year Member
Posts: 318
Reputation Power: 16
try try again is my advice same thing happened to my bro but he kept trying and it worked eventuall
#4. Posted:
10mejia
  • Challenger
Status: Offline
Joined: May 30, 201014Year Member
Posts: 121
Reputation Power: 4
Status: Offline
Joined: May 30, 201014Year Member
Posts: 121
Reputation Power: 4
MonsterSolutionz wrote are you burning it to a disk or your PCs harddrive?

I'm burning it to a disk, Verbatim 8x DVD+R DL 8.5GB
#5. Posted:
10mejia
  • Challenger
Status: Offline
Joined: May 30, 201014Year Member
Posts: 121
Reputation Power: 4
Status: Offline
Joined: May 30, 201014Year Member
Posts: 121
Reputation Power: 4
xBeastly123 wrote try try again is my advice same thing happened to my bro but he kept trying and it worked eventuall
Tried that, i kept getting the error no matter what i did.
#6. Posted:
RepFairy
  • Gold Gifter
Status: Offline
Joined: Nov 26, 201014Year Member
Posts: 1,781
Reputation Power: 1991
Status: Offline
Joined: Nov 26, 201014Year Member
Posts: 1,781
Reputation Power: 1991
Make sure your speed is no higher than 2.4 or you will get errors like that.
so, retry blah blah blah, or I can teamviewer you and do it for you.
#7. Posted:
-RedRobin-
  • TTG Contender
Status: Offline
Joined: Sep 19, 201014Year Member
Posts: 3,943
Reputation Power: 180
Status: Offline
Joined: Sep 19, 201014Year Member
Posts: 3,943
Reputation Power: 180
just happend to me do you have the right settings and when it is burning dont go on your pc untill it is done i iso mod ALL THE TIME
#8. Posted:
sultehh
  • TTG Senior
Status: Offline
Joined: Jan 28, 201113Year Member
Posts: 1,104
Reputation Power: 46
Status: Offline
Joined: Jan 28, 201113Year Member
Posts: 1,104
Reputation Power: 46
You computers Drive might be screwed up...
I cleaned my laser and it worked. I had the same(ish) error
#9. Posted:
apocalyptic_WEBZ
  • New Member
Status: Offline
Joined: Feb 13, 201113Year Member
Posts: 24
Reputation Power: 1
Status: Offline
Joined: Feb 13, 201113Year Member
Posts: 24
Reputation Power: 1
your setting on imgburn are wrong it happend to me when i first started modding iso

this is not my vid but it should help you

[ Register or Signin to view external links. ]





link to my waw lobby vid is

plz sub you dont have to but i would appreciate it

[ Register or Signin to view external links. ]
Jump to:
You are viewing our Forum Archives. To view or take place in current topics click here.