Lately, I’ve been trying to burn xbox 360 backups, but every single time I try, Imgburn shows a scsistatus 0x02 error at around 50%.
I would post the error text, but I would not like to waste a perfectly good DL disc is not necessary (Unless there is a way to check that without wasting another disc…?).
I’ve already searched through many Imgburn forums concerning this issue, yet I still could not find my answer.
I am not very experienced with this program, so if my question is stupid, I apologize.
Is there any solution? Can anyone please explain this problem to me?
Family tree:
ACPI x64-based PC
Microsoft ACPI-Compliant System
PCI bus
Intel® 5 Series 6 Port SATA AHCI Controller (Ven_8086&DEV_3B2F — Intel — iaStorA — v7.0.0.1013
Cd_Rom Drive (TSSTcorp DVD+-RW TS-L633C SCSI CdRom Device)
(Bus Number 1, Target Id 0, LUN 0)
Disc: Verbatim DVD+R DL 2.4x
Here is the log:
I 19:30:51 ImgBurn Version 2.5.7.0 started!
I 19:30:51 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7600)
I 19:30:51 Total Physical Memory: 3,985,944 KB — Available: 2,423,428 KB
I 19:30:51 Initialising SPTI…
I 19:30:51 Searching for SCSI / ATAPI devices…
I 19:30:51 -> Drive 1 — Info: TSSTcorp DVD+-RW TS-L633C DW50 (D:) (SATA)
I 19:30:51 Found 1 DVD±RW/RAM!
I 19:41:03 Operation Started!
I 19:41:03 Source File: C:UsersDylanDesktopGamesXbox 360 GamesResident Evil 5R-45447-999-63-2.dvd
I 19:41:03 Source File Sectors: 3,825,924 (MODE1/2048)
I 19:41:03 Source File Size: 7,835,492,352 bytes
I 19:41:03 Source File Volume Identifier: XGD2DVD_NTSC
I 19:41:03 Source File Volume Set Identifier: 34672923
I 19:41:03 Source File Implementation Identifier: Sonic Scenarist 3.1
I 19:41:03 Source File File System(s): ISO9660, UDF (1.02)
I 19:41:03 Destination Device: [0:0:0] TSSTcorp DVD+-RW TS-L633C DW50 (D:) (SATA)
I 19:41:03 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00)
I 19:41:03 Destination Media Supported Write Speeds: 2.4x
I 19:41:03 Destination Media Sectors: 4,173,824
I 19:41:03 Write Mode: DVD
I 19:41:03 Write Type: DAO
I 19:41:03 Write Speed: MAX
I 19:41:03 DVD+R DL Reserve Track: No
I 19:41:03 Link Size: Auto
I 19:41:03 Lock Volume: Yes
I 19:41:03 Test Mode: No
I 19:41:03 OPC: No
I 19:41:03 BURN-Proof: Enabled
W 19:41:03 Write Speed Miscompare! — MODE SENSE: 2,770 KB/s (2x), GET PERFORMANCE: 3,324 KB/s (2.4x)
I 19:41:03 Write Speed Successfully Set! — Effective: 3,324 KB/s (2.4x)
I 19:41:03 Book Type Setting: DVD-ROM
I 19:41:03 Optimal L0 Data Zone Capacity: 1,913,760
I 19:41:03 Optimal L0 Data Zone Method: Copied From Original Disc
I 19:54:28 Set L0 Data Zone Capacity Succeeded!
I 19:54:29 Filling Buffer… (80 MB)
I 19:54:30 Writing LeadIn…
I 19:54:32 Writing Session 1 of 1… (1 Track, LBA: 0 — 3825923)
I 19:54:32 Writing Track 1 of 1… (MODE1/2048, LBA: 0 — 3825923)
I 19:54:32 Writing Layer 0… (LBA: 0 — 1913759)
W 20:15:39 Failed to Write Sectors 1803616 — 1803647 — Reason: Write Error
W 20:15:39 Retrying (1 of 20)…
W 20:15:39 Retry Failed — Reason: Invalid Address For Write
W 20:15:39 Retrying (2 of 20)…
W 20:15:39 Retry Failed — Reason: Invalid Address For Write
W 20:15:39 Retrying (3 of 20)…
W 20:15:39 Retry Failed — Reason: Invalid Address For Write
W 20:15:39 Retrying (4 of 20)…
W 20:15:39 Retry Failed — Reason: Invalid Address For Write
W 20:15:39 Retrying (5 of 20)…
W 20:15:39 Retry Failed — Reason: Invalid Address For Write
W 20:15:39 Retrying (6 of 20)…
W 20:15:39 Retry Failed — Reason: Invalid Address For Write
W 20:15:39 Retrying (7 of 20)…
W 20:15:39 Retry Failed — Reason: Invalid Address For Write
W 20:15:39 Retrying (8 of 20)…
W 20:15:39 Retry Failed — Reason: Invalid Address For Write
W 20:15:39 Retrying (9 of 20)…
W 20:15:39 Retry Failed — Reason: Invalid Address For Write
W 20:15:39 Retrying (10 of 20)…
W 20:15:39 Retry Failed — Reason: Invalid Address For Write
W 20:15:39 Retrying (11 of 20)…
W 20:15:39 Retry Failed — Reason: Invalid Address For Write
W 20:15:39 Retrying (12 of 20)…
W 20:15:39 Retry Failed — Reason: Invalid Address For Write
W 20:15:39 Retrying (13 of 20)…
W 20:15:39 Retry Failed — Reason: Invalid Address For Write
W 20:15:39 Retrying (14 of 20)…
W 20:15:39 Retry Failed — Reason: Invalid Address For Write
W 20:15:39 Retrying (15 of 20)…
W 20:15:39 Retry Failed — Reason: Invalid Address For Write
W 20:15:39 Retrying (16 of 20)…
W 20:15:39 Retry Failed — Reason: Invalid Address For Write
W 20:15:39 Retrying (17 of 20)…
W 20:15:39 Retry Failed — Reason: Invalid Address For Write
W 20:15:39 Retrying (18 of 20)…
W 20:15:39 Retry Failed — Reason: Invalid Address For Write
W 20:15:39 Retrying (19 of 20)…
W 20:15:39 Retry Failed — Reason: Invalid Address For Write
W 20:15:39 Retrying (20 of 20)…
W 20:15:39 Retry Failed — Reason: Invalid Address For Write
W 20:15:47 Retrying (21)…
W 20:15:47 Retry Failed — Reason: Invalid Address For Write
W 20:15:47 Retrying (22)…
W 20:15:47 Retry Failed — Reason: Invalid Address For Write
W 20:15:47 Retrying (23)…
W 20:15:47 Retry Failed — Reason: Invalid Address For Write
W 20:15:47 Retrying (24)…
W 20:15:47 Retry Failed — Reason: Invalid Address For Write
W 20:15:48 Retrying (25)…
W 20:15:48 Retry Failed — Reason: Invalid Address For Write
W 20:15:48 Retrying (26)…
W 20:15:48 Retry Failed — Reason: Invalid Address For Write
W 20:15:48 Retrying (27)…
W 20:15:48 Retry Failed — Reason: Invalid Address For Write
W 20:15:48 Retrying (28)…
W 20:15:48 Retry Failed — Reason: Invalid Address For Write
W 20:15:48 Retrying (29)…
W 20:15:48 Retry Failed — Reason: Invalid Address For Write
W 20:15:48 Retrying (30)…
W 20:15:48 Retry Failed — Reason: Invalid Address For Write
W 20:15:49 Retrying (31)…
W 20:15:49 Retry Failed — Reason: Invalid Address For Write
W 20:15:49 Retrying (32)…
W 20:15:49 Retry Failed — Reason: Invalid Address For Write
W 20:15:49 Retrying (33)…
W 20:15:49 Retry Failed — Reason: Invalid Address For Write
W 20:15:50 Retrying (34)…
W 20:15:50 Retry Failed — Reason: Invalid Address For Write
W 20:15:50 Retrying (35)…
W 20:15:50 Retry Failed — Reason: Invalid Address For Write
W 20:15:50 Retrying (36)…
W 20:15:50 Retry Failed — Reason: Invalid Address For Write
W 20:15:51 Retrying (37)…
W 20:15:51 Retry Failed — Reason: Invalid Address For Write
W 20:15:51 Retrying (38)…
W 20:15:51 Retry Failed — Reason: Invalid Address For Write
W 20:15:51 Retrying (39)…
W 20:15:51 Retry Failed — Reason: Invalid Address For Write
W 20:15:52 Retrying (40)…
W 20:15:52 Retry Failed — Reason: Invalid Address For Write
W 20:15:52 Retrying (41)…
W 20:15:52 Retry Failed — Reason: Invalid Address For Write
W 20:15:52 Retrying (42)…
W 20:15:52 Retry Failed — Reason: Invalid Address For Write
W 20:15:52 Retrying (43)…
W 20:15:52 Retry Failed — Reason: Invalid Address For Write
W 20:15:52 Retrying (44)…
W 20:15:52 Retry Failed — Reason: Invalid Address For Write
W 20:15:52 Retrying (45)…
W 20:15:52 Retry Failed — Reason: Invalid Address For Write
W 20:15:53 Retrying (46)…
W 20:15:53 Retry Failed — Reason: Invalid Address For Write
W 20:15:53 Retrying (47)…
W 20:15:53 Retry Failed — Reason: Invalid Address For Write
E 20:20:14 Failed to Write Sectors 1803616 — 1803647 — Reason: Write Error
E 20:20:14 Next Writable Address: 1802944
I 20:20:15 Synchronising Cache…
W 20:20:17 User opted to skip the ‘Close Track/Session/Disc’ functions.
E 20:20:17 Failed to Write Image!
I 20:20:17 Exporting Graph Data…
I 20:20:17 Graph Data File: C:UsersDylanAppDataRoamingImgBurnGraph Data FilesTSSTcorp_DVD+-RW_TS-L633C_DW50_OCTOBER-02-12_7-41_PM_MKM-001-00_MAX.ibg
I 20:20:17 Export Successfully Completed!
E 20:20:17 Operation Failed! — Duration: 00:39:14
I 20:20:17 Average Write Rate: 2,339 KB/s (1.7x) — Maximum Write Rate: 3,430 KB/s (2.5x)
Edited October 3, 2012 by Thaepicasian
Номер ошибки: | Ошибка Scsistatus 0x02 | |
Название ошибки: | Imgburn Error Scsistatus 0X02 | |
Описание ошибки: | Ошибка Scsistatus 0x02: Возникла ошибка в приложении ImgBurn. Приложение будет закрыто. Приносим извинения за неудобства. | |
Разработчик: | Lightning UK! | |
Программное обеспечение: | ImgBurn | |
Относится к: | Windows XP, Vista, 7, 8, 10, 11 |
Описание «Imgburn Error Scsistatus 0X02»
Это наиболее распространенное условие «Imgburn Error Scsistatus 0X02», известное как ошибка времени выполнения (ошибка). Разработчики программного обеспечения, такие как SoftwareDeveloper, обычно работают через несколько этапов отладки, чтобы предотвратить и исправить ошибки, обнаруженные в конечном продукте до выпуска программного обеспечения для общественности. К сожалению, некоторые критические проблемы, такие как ошибка Scsistatus 0x02, часто могут быть упущены из виду.
Некоторые люди могут столкнуться с сообщением «Imgburn Error Scsistatus 0X02» во время работы программного обеспечения. Когда это происходит, конечные пользователи могут сообщить Lightning UK! о наличии ошибок «Imgburn Error Scsistatus 0X02». Затем Lightning UK! будет иметь знания, чтобы исследовать, как и где устранить проблему. Если есть уведомление об обновлении ImgBurn, это может быть решением для устранения таких проблем, как ошибка Scsistatus 0x02 и обнаруженные дополнительные проблемы.
Что вызывает ошибку времени выполнения Scsistatus 0x02?
«Imgburn Error Scsistatus 0X02» чаще всего может возникать при загрузке ImgBurn. Следующие три наиболее значимые причины ошибок выполнения ошибки Scsistatus 0x02 включают в себя:
Ошибка Scsistatus 0x02 Crash — это очень популярная ошибка выполнения ошибки Scsistatus 0x02, которая приводит к завершению работы всей программы. Эти ошибки обычно возникают, когда входы ImgBurn не могут быть правильно обработаны, или они смущены тем, что должно быть выведено.
Утечка памяти «Imgburn Error Scsistatus 0X02» — этот тип утечки памяти приводит к тому, что ImgBurn продолжает использовать растущие объемы памяти, снижая общую производительность системы. Это может быть вызвано неправильной конфигурацией программного обеспечения Lightning UK! или когда одна команда запускает цикл, который не может быть завершен.
Ошибка Scsistatus 0x02 Logic Error — «логическая ошибка», как говорят, генерируется, когда программное обеспечение получает правильный ввод, но генерирует неверный вывод. Это связано с ошибками в исходном коде Lightning UK!, обрабатывающих ввод неправильно.
Как правило, ошибки Imgburn Error Scsistatus 0X02 вызваны повреждением или отсутствием файла связанного ImgBurn, а иногда — заражением вредоносным ПО. Для устранения неполадок, связанных с файлом Lightning UK!, большинство профессионалов ПК заменят файл на соответствующую версию. В качестве дополнительного шага по устранению неполадок мы настоятельно рекомендуем очистить все пути к неверным файлам и ссылки на расширения файлов Lightning UK!, которые могут способствовать возникновению такого рода ошибок, связанных с Imgburn Error Scsistatus 0X02.
Классические проблемы Imgburn Error Scsistatus 0X02
Частичный список ошибок Imgburn Error Scsistatus 0X02 ImgBurn:
- «Ошибка в приложении: Imgburn Error Scsistatus 0X02»
- «Недопустимый файл Imgburn Error Scsistatus 0X02. «
- «Imgburn Error Scsistatus 0X02 столкнулся с проблемой и закроется. «
- «Imgburn Error Scsistatus 0X02 не может быть найден. «
- «Отсутствует файл Imgburn Error Scsistatus 0X02.»
- «Ошибка запуска программы: Imgburn Error Scsistatus 0X02.»
- «Imgburn Error Scsistatus 0X02 не работает. «
- «Ошибка Imgburn Error Scsistatus 0X02. «
- «Неверный путь к программе: Imgburn Error Scsistatus 0X02. «
Проблемы ImgBurn Imgburn Error Scsistatus 0X02 возникают при установке, во время работы программного обеспечения, связанного с Imgburn Error Scsistatus 0X02, во время завершения работы или запуска или менее вероятно во время обновления операционной системы. Важно отметить, когда возникают проблемы Imgburn Error Scsistatus 0X02, так как это помогает устранять проблемы ImgBurn (и сообщать в Lightning UK!).
Корень проблем Imgburn Error Scsistatus 0X02
Заражение вредоносными программами, недопустимые записи реестра ImgBurn или отсутствующие или поврежденные файлы Imgburn Error Scsistatus 0X02 могут создать эти ошибки Imgburn Error Scsistatus 0X02.
В частности, проблемы с Imgburn Error Scsistatus 0X02, вызванные:
- Недопустимая (поврежденная) запись реестра Imgburn Error Scsistatus 0X02.
- Загрязненный вирусом и поврежденный Imgburn Error Scsistatus 0X02.
- Другая программа (не связанная с ImgBurn) удалила Imgburn Error Scsistatus 0X02 злонамеренно или по ошибке.
- Другая программа, конфликтующая с Imgburn Error Scsistatus 0X02 или другой общей ссылкой ImgBurn.
- ImgBurn (Imgburn Error Scsistatus 0X02) поврежден во время загрузки или установки.
Продукт Solvusoft
Загрузка
WinThruster 2022 — Проверьте свой компьютер на наличие ошибок.
Совместима с Windows 2000, XP, Vista, 7, 8, 10 и 11
Установить необязательные продукты — WinThruster (Solvusoft) | Лицензия | Политика защиты личных сведений | Условия | Удаление
-
DEM90
Well-Known Member- Сообщения:
- 58
- Симпатии:
- 1
- Баллы:
- 61
Такая проблема: записываю игру на двуслойную болванку, а он мне выдаёт ошибку. Если записываю через CloneCD, то он пишет просто ПРОИЗОШЛА ОШИБКА, а если через ImgBurn, то:
С третьей попытки CloneCD записал диск. Записывал на сокрости 2x. Но вот проблема, когда вставляю диск в главном меню пишется не ЗАПУСТИТЬ «НАЗВАНИЕ ИГРЫ» (Наруто новый), а просто ВОСПРОИЗВЕСТИ DVD. Когда запускаю, он мне показывает логотип XBox и всё. Если нажать какую-нибудь кнопку он выдаёт мини-меню, будто я смотрю фильм (воспроизведение, стоп, пауза и т.д.). У меня не та прошивка или я что-то сделал не так? Хотя делал всё по инструкции (http://rutracker.org/forum/viewtopic.php?t=435442) ((((
-
Ну так если у тебя ошибка на этапе записи, то проблема либо в том, чем записывает, либо в том, на что пишет. Если болванки и образы нормальные, то остается только привод, по-моему. Лично я писал ImgBurn-ом на 4-ой скорости всегда. Образы всегда проверял abgx-ом перед записью. Всё было ок.
-
Вероятнее всего дело именно в болванках. Нужно использовать плюсовые Verbatim — и будет счастье.
-
DEM90
Well-Known Member- Сообщения:
- 58
- Симпатии:
- 1
- Баллы:
- 61
Записал на Mirex программой CloneCD, но он мне всё равно выдаёт логотип XBox и если нажать какую-то кнопку внизу появляется «меню» в котором можно ВОПРОИЗВЕСТИ, ОСТАНОВИТЬ, СДЕЛАТЬ ПАУЗУ и т.д.
Может есть руководство, как записывать ImgBurn? Просто на рутреккере руководство есть, но у меня более новая версия ImgBurn и там настройки немного отличаются (((( -
DEM90, пиши КлонСиДи. без проблем пишет. лично записывал штук 100 игр. и мирексы и вербатимы и левые китайские болванки, все работали на боксе.
какой резак у тебя?
-
1. 2. Если проверяешь исо с помощью abgx, то abgx сама создаст или исправит файл .dvd. В этом файле просто информация, какой образ записывать и где делать layer break. Т.е. даже в настройки лезть не надо, чтобы выставить layer break. Дальше всё просто. Выбрать файл — не сам исо, а .dvd, выставить скорость и писать. Я еще выставлял бук тайп на DVD-ROM, на всякий. Это иконка с книжечкой. Писал на Вербатим +ДЛ.
-
Illias
Well-Known Member- Сообщения:
- 319
- Симпатии:
- 10
- Баллы:
- 68
Если в процессе записи не было ошибки подобной той, что ты указал в первом посте, то тогда поздравляю — твоя прошивка привода ниже требуемой. Метод лечения: использовать Activate Iso (тыЦк) или перешивать привод более свежей прошей. И пожалей привод в ящике, не подсовывай ему всякое гумно IMHO, типа Mirex’a.
z1rc0n, у него PIONEER DVD-RW DVR-112D — нормальный резак (у самого такой, ток перешитый в L).
-
или пропатчивать новые перед записью
-
SAMuel
Alpian Warrior Glegleddore Gleglezavr- Сообщения:
- 660
- Симпатии:
- 13
- Баллы:
- 68
иногда прогоняю agbx, а пишу всегда клономСД, качественные болванки все пашут а дешовые пробовал так из 5 дисков токо 1 играет, лучше юзать качественные: Verbatim, Arita, Datex…
This article features error number Code Scsistatus 0x02, commonly known as Imgburn Error Scsistatus 0X02 described as Error Scsistatus 0x02: ImgBurn has encountered a problem and needs to close. We are sorry for the inconvenience.
About Runtime Code Scsistatus 0x02
Runtime Code Scsistatus 0x02 happens when ImgBurn fails or crashes whilst it’s running, hence its name. It doesn’t necessarily mean that the code was corrupt in some way, but just that it did not work during its run-time. This kind of error will appear as an annoying notification on your screen unless handled and corrected. Here are symptoms, causes and ways to troubleshoot the problem.
Symptoms of Code Scsistatus 0x02 — Imgburn Error Scsistatus 0X02
Runtime errors happen without warning. The error message can come up the screen anytime ImgBurn is run. In fact, the error message or some other dialogue box can come up again and again if not addressed early on.
There may be instances of files deletion or new files appearing. Though this symptom is largely due to virus infection, it can be attributed as a symptom for runtime error, as virus infection is one of the causes for runtime error. User may also experience a sudden drop in internet connection speed, yet again, this is not always the case.
(For illustrative purposes only)
Causes of Imgburn Error Scsistatus 0X02 — Code Scsistatus 0x02
During software design, programmers code anticipating the occurrence of errors. However, there are no perfect designs, as errors can be expected even with the best program design. Glitches can happen during runtime if a certain error is not experienced and addressed during design and testing.
Runtime errors are generally caused by incompatible programs running at the same time. It may also occur because of memory problem, a bad graphics driver or virus infection. Whatever the case may be, the problem must be resolved immediately to avoid further problems. Here are ways to remedy the error.
Repair Methods
Runtime errors may be annoying and persistent, but it is not totally hopeless, repairs are available. Here are ways to do it.
If a repair method works for you, please click the upvote button to the left of the answer, this will let other users know which repair method is currently working the best.
Please note: Neither ErrorVault.com nor it’s writers claim responsibility for the results of the actions taken from employing any of the repair methods listed on this page — you complete these steps at your own risk.
Method 1 — Close Conflicting Programs
When you get a runtime error, keep in mind that it is happening due to programs that are conflicting with each other. The first thing you can do to resolve the problem is to stop these conflicting programs.
- Open Task Manager by clicking Ctrl-Alt-Del at the same time. This will let you see the list of programs currently running.
- Go to the Processes tab and stop the programs one by one by highlighting each program and clicking the End Process buttom.
- You will need to observe if the error message will reoccur each time you stop a process.
- Once you get to identify which program is causing the error, you may go ahead with the next troubleshooting step, reinstalling the application.
Method 2 — Update / Reinstall Conflicting Programs
Using Control Panel
- For Windows 7, click the Start Button, then click Control panel, then Uninstall a program
- For Windows 8, click the Start Button, then scroll down and click More Settings, then click Control panel > Uninstall a program.
- For Windows 10, just type Control Panel on the search box and click the result, then click Uninstall a program
- Once inside Programs and Features, click the problem program and click Update or Uninstall.
- If you chose to update, then you will just need to follow the prompt to complete the process, however if you chose to Uninstall, you will follow the prompt to uninstall and then re-download or use the application’s installation disk to reinstall the program.
Using Other Methods
- For Windows 7, you may find the list of all installed programs when you click Start and scroll your mouse over the list that appear on the tab. You may see on that list utility for uninstalling the program. You may go ahead and uninstall using utilities available in this tab.
- For Windows 10, you may click Start, then Settings, then choose Apps.
- Scroll down to see the list of Apps and features installed in your computer.
- Click the Program which is causing the runtime error, then you may choose to uninstall or click Advanced options to reset the application.
Method 3 — Update your Virus protection program or download and install the latest Windows Update
Virus infection causing runtime error on your computer must immediately be prevented, quarantined or deleted. Make sure you update your virus program and run a thorough scan of the computer or, run Windows update so you can get the latest virus definition and fix.
Method 4 — Re-install Runtime Libraries
You might be getting the error because of an update, like the MS Visual C++ package which might not be installed properly or completely. What you can do then is to uninstall the current package and install a fresh copy.
- Uninstall the package by going to Programs and Features, find and highlight the Microsoft Visual C++ Redistributable Package.
- Click Uninstall on top of the list, and when it is done, reboot your computer.
- Download the latest redistributable package from Microsoft then install it.
Method 5 — Run Disk Cleanup
You might also be experiencing runtime error because of a very low free space on your computer.
- You should consider backing up your files and freeing up space on your hard drive
- You can also clear your cache and reboot your computer
- You can also run Disk Cleanup, open your explorer window and right click your main directory (this is usually C: )
- Click Properties and then click Disk Cleanup
Method 6 — Reinstall Your Graphics Driver
If the error is related to a bad graphics driver, then you may do the following:
- Open your Device Manager, locate the graphics driver
- Right click the video card driver then click uninstall, then restart your computer
Method 7 — IE related Runtime Error
If the error you are getting is related to the Internet Explorer, you may do the following:
- Reset your browser.
- For Windows 7, you may click Start, go to Control Panel, then click Internet Options on the left side. Then you can click Advanced tab then click the Reset button.
- For Windows 8 and 10, you may click search and type Internet Options, then go to Advanced tab and click Reset.
- Disable script debugging and error notifications.
- On the same Internet Options window, you may go to Advanced tab and look for Disable script debugging
- Put a check mark on the radio button
- At the same time, uncheck the «Display a Notification about every Script Error» item and then click Apply and OK, then reboot your computer.
If these quick fixes do not work, you can always backup files and run repair reinstall on your computer. However, you can do that later when the solutions listed here did not do the job.
Other languages:
Wie beheben Fehler Scsistatus 0x02 (Imgburn-Fehler Scsistatus 0X02) — Fehler Scsistatus 0x02: ImgBurn hat ein Problem festgestellt und muss geschlossen werden. Wir entschuldigen uns für die Unannehmlichkeiten.
Come fissare Errore Scsistatus 0x02 (Errore Imgburn Scsistatus 0X02) — Errore Scsistatus 0x02: ImgBurn ha riscontrato un problema e deve essere chiuso. Ci scusiamo per l’inconveniente.
Hoe maak je Fout Scsistatus 0x02 (Imgburn-fout Scsistatus 0X02) — Fout Scsistatus 0x02: ImgBurn heeft een probleem ondervonden en moet worden afgesloten. Excuses voor het ongemak.
Comment réparer Erreur Scsstatus 0x02 (Erreur Imgburn Scsstatus 0X02) — Erreur Scsistatus 0x02 : ImgBurn a rencontré un problème et doit fermer. Nous sommes désolés du dérangement.
어떻게 고치는 지 오류 Scsstatus 0x02 (Imgburn 오류 Scsstatus 0X02) — 오류 Scsstatus 0x02: ImgBurn에 문제가 발생해 닫아야 합니다. 불편을 끼쳐드려 죄송합니다.
Como corrigir o Erro Scsistatus 0x02 (Erro Imgburn Scsistatus 0X02) — Erro Scsistatus 0x02: O ImgBurn encontrou um problema e precisa fechar. Lamentamos o inconveniente.
Hur man åtgärdar Fel Scsistatus 0x02 (Imgburn-fel Scsistatus 0X02) — Fel Scsistatus 0x02: ImgBurn har stött på ett problem och måste avslutas. Vi är ledsna för besväret.
Как исправить Ошибка Scsistatus 0x02 (Ошибка Imgburn Scsistatus 0X02) — Ошибка Scsistatus 0x02: Возникла ошибка в приложении ImgBurn. Приложение будет закрыто. Приносим свои извинения за неудобства.
Jak naprawić Błąd Scsistatus 0x02 (Imgburn Błąd Scsistatus 0X02) — Błąd Scsistatus 0x02: ImgBurn napotkał problem i musi zostać zamknięty. Przepraszamy za niedogodności.
Cómo arreglar Error Scsistatus 0x02 (Error de Imgburn Scsistatus 0X02) — Error Scsistatus 0x02: ImgBurn ha detectado un problema y debe cerrarse. Lamentamos las molestias.
About The Author: Phil Hart has been a Microsoft Community Contributor since 2010. With a current point score over 100,000, they’ve contributed more than 3000 answers in the Microsoft Support forums and have created almost 200 new help articles in the Technet Wiki.
Follow Us:
This repair tool can fix common computer problems such as blue screens, crashes and freezes, missing DLL files, as well as repair malware/virus damage and more by replacing damaged and missing system files.
STEP 1:
Click Here to Download and install the Windows repair tool.
STEP 2:
Click on Start Scan and let it analyze your device.
STEP 3:
Click on Repair All to fix all of the issues it detected.
DOWNLOAD NOW
Compatibility
Requirements
1 Ghz CPU, 512 MB RAM, 40 GB HDD
This download offers unlimited scans of your Windows PC for free. Full system repairs start at $19.95.
Article ID: ACX05003EN
Applies To: Windows 10, Windows 8.1, Windows 7, Windows Vista, Windows XP, Windows 2000
Speed Up Tip #43
Use DeepFreeze to Wipe Out Changes Upon Restart:
Software tools like DeepFreeze can save your computer from a lot of mess especially if you are sharing it with other people. For instance, kids can easily install crappy programs into your pc that might slow it down. With DeepFreeze, all you have to do is restart your computer and the changes made will be wiped out.
Click Here for another way to speed up your Windows PC
Microsoft & Windows® logos are registered trademarks of Microsoft. Disclaimer: ErrorVault.com is not affiliated with Microsoft, nor does it claim such affiliation. This page may contain definitions from https://stackoverflow.com/tags under the CC-BY-SA license. The information on this page is provided for informational purposes only. © Copyright 2018
-
ImgBurn gives me this error log when after failing to burn Blue Ray image files and ruinning my disk. Can anyone help me interpret the problem? I’ll also try the ImgBurn forum. Thanks.
I/O Error
ScsiStatus: 0X02
Interpretation: Check condition
CDB: 28 00 00 A3 B3 E1 00 00 01 00
Sense Area: 7100 03 00 00 00 00 0A 00 00 00 00 11 05 00 00 00 00
Interpretation: L-EC Uncorrectable ErrorAny thoughts would be appreciated.
-
No idea, your best bet would be the imgburn forum
-
Thanks for the response—quick question—is it best to rip iso’s or the entire file structure?
-
Last edited by a moderator: May 27, 2016
-
After ripping, I want to burn to DVDs or BDs. I use Clone DVD for my DVDs and usually rip BDs with AnyDVD. I was wondering whether it makes a difference to rip an image or files for burining purposes.
I use Verbatim DLs, Verbatim BD and TYs for DVD.
I am using latest Img and it burns DVDs just fine.
Tks.
-
No surprise it writes DVD’s fine as they use a different laser to Blu-ray. Where did you get the BD-R’s from. Did Imgburn give you any other message than this?
Also what drive are you using to burn with?
-
Thanks for the response Adbear.
1. I bought the BD’s from Super Media—they’ve always been trustworthy in the past.
2. Ligthening UK (imgburn creator) looked at a variety of error logs and couldn’t come up with an answer.
3. I use PDL DVD and BD drives that came with the Dell Studio.
4. I decided to uninstall and re-install. Waiting to test. -
Hawk
Well-Known MemberI ran into problem just like that and it happens when using bad media. Underline words may give hint about the problem.
-
You could try using Imgburn to see if there’s a firmware update for the drive. Choose an option in imgburn then go to the ‘tools/drive/update firmware’ option. This should take you to a webpage with a list of firmware for the drive. It may also say who actually makes the drive
-
muttman
Member- Joined:
- Dec 30, 2004
- Messages:
- 3
- Likes Received:
- 0
- Trophy Points:
- 11
Hi all, I’m a newbie here, but have been using DVD Decrypter and DVD Shrink for a while now. I’ve managed to back up a large proportion of my DVD’s (at lease 30 done already) and have never had any problems — until now that is.
I’m trying to back up Pirates of the Caribbean (r2), but keep getting the following message while DVD Decrypter is decrypting the disc:
—————-
I/O Error!
Device: [1:0:0]_NEC DVD_RW ND-2510A 2.54 (D (ATA)
ScsiStatus: 0x02
Interpretation: Check ConditionCDB: 28 00 00 0C EF C0 00 00 01 00
Interpretation: Read (10) — Sector: 847808Sense Area: F0 00 03 00 0C EF C0 0A 00 00 00 00 11 00 00 00 00 00
Interpretation: Unrecovered Read Error—————-
Having looked around, the consensus for this error seems to be that the disc is most probably damaged/dirty. However, this is highly unlikely in this case, as not only is the disc immaculate, but it plays perfectly on my home DVD players, as well as on the DVD drive that DVD Decrypt is reading from.
Basically, has anyone else had a similar problem with Decrypter, and is there any established explanation for why this is happening?
-
tarmac
Member- Joined:
- Jan 11, 2005
- Messages:
- 14
- Likes Received:
- 0
- Trophy Points:
- 11
I just received the same error! I was just trying to backup using DVD Decryptor, and I got to 92% ripped to the hard drive.
I/O error!
Device: (3:1:0)AOPEN DUW1608/ARR A060 (F(ATA)
ScsiStatus: 0:02
Interpretation: Check Condition
CDB: 28 00 00 34 7B D0 00 00 01 00
Interpretation: Read (10) — Sector: 3439568
Sense Area: F0 00 03 00 34 7B D0 0E 00 00 00 00 15 82 00 00 00 00 03 00
Interpretation: Unknown (Positioning Error) (0x15, 0x82)I am using a AOPEN DVD burner 16X dual layer.
I read that if you ASPI is not correct, DVD Decryptor will not work properly. Do you know if this could be reason for this error?
-
rahxephan
Member- Joined:
- Nov 28, 2004
- Messages:
- 8
- Likes Received:
- 0
- Trophy Points:
- 11
I am getting the same error as well. It rips through 98% and then gives me the error.
Can anyone address this issue?
I also noticed as I am ripping, my buffer is exhausted and only goes up 1-2% before it goes back to zero. Also my read time varies from 1.4x to 2.5x or something to that regards?
Can anyone give me insights to my wrong doings?
thanks
-nghia
-
laddyboy
Regular member- Joined:
- Jan 4, 2005
- Messages:
- 4,188
- Likes Received:
- 0
- Trophy Points:
- 46
Are you using the newest version of decrypter 3.5.2? Have you tried ripping with DVDShrink? Or try the beta version of AnyDVD in conjunction with either Shrink or Decrypter. If you can rip with Shrink, the problem is most likely with your copy of Decrypter.
-
rahxephan
Member- Joined:
- Nov 28, 2004
- Messages:
- 8
- Likes Received:
- 0
- Trophy Points:
- 11
I attempted to rip using nero 6 , dvd decryptor, and alcohol 120%. All give me a error. I tried the previous copy of decryptor as well as the lastest version when it didn’t work.
I didn’t know shrink had ripper. I will try that and update if I have any problems.
Im also using a lite-on dvd writer.
Thanks
-
hursty
Active member- Joined:
- Nov 22, 2004
- Messages:
- 4,618
- Likes Received:
- 1
- Trophy Points:
- 66
you cannot rip copyright movies with nero
with regards hursty -
rroettger
Regular member- Joined:
- Sep 3, 2004
- Messages:
- 395
- Likes Received:
- 0
- Trophy Points:
- 26
Even a brand new prefect disc can have read errors. They do not have to be prefect to be used in a stand alone, do have to be to copy.
.. Try these settings for DVD Decrypter.
First, it should be version 3.5.1.0 or later.Open Decrypter, click on Tools,then Settings
Click on Defaults, then select these;
General tab
Options — Removal Method — AggressiveFile Mode tab
Options — Remove PUOs (IFO and/or VOB)ISO Read Mode tab
Options — Remove PUOs (IFO and/or VOB)CSS tab
CSS Cracking Method — Brute Force ~> I/O Key ExchangeOn Failure — Yes
IMPORTANT:
I/O tab
Options — Ignore read errors.This is an excellent setting for dealing with scratched discs which may cause ripping problems.
Source: ScubaPete
Last edited: Jan 13, 2005
-
pulsar
Active member- Joined:
- Dec 31, 2003
- Messages:
- 2,420
- Likes Received:
- 1
- Trophy Points:
- 68
Scuba is indeed a saviour!
-
burn_it
Member- Joined:
- Jan 14, 2005
- Messages:
- 3
- Likes Received:
- 0
- Trophy Points:
- 11
was anybody able to solve the I/O error …i am also getting the same ..all the dvds are new settings are as per scuba pete’s instructions but still the same error .. thanks in advance for the help guys ..
-
laddyboy
Regular member- Joined:
- Jan 4, 2005
- Messages:
- 4,188
- Likes Received:
- 0
- Trophy Points:
- 46
burnit:Is this happening with all DVDs or just one?
-
burn_it
Member- Joined:
- Jan 14, 2005
- Messages:
- 3
- Likes Received:
- 0
- Trophy Points:
- 11
hi laddyboy .. thanks so much for taking sometime and replying back to me .. really appreciate that .. ok here is my problem list .. I/O error is coming up with some of the disks and not all of them and i am not sure why ??
i am getting cyclic redundancy error on almost evry disk .. i am using dvd shrink 3.2 , dvd decryptor 3.5.2 and i have tried dvd clone as well .. this is what i do : first i insert the movie and try to read it via dvd shrink so i say open disc and it starts loading it .. once it gets loaded i run analysis ..once that is done i say create ISO image and burn with dvd decryptor … dvd shrink creates the ISO image and when decryptor tries to write it it says data error in the process … and i end up with a half written bad disk … sometimes when dvd shrink gives me the problem in creating the ISO file i do it with dvd decryptor as Pete has suggested in one of his forum .. i get the ISO file from decryptor and then i go back to shrink as i cannot burn with decryptor becoz of the size issue (4.7 gb) .. now my question is that if u open an ISO image with dvd shrink software it truly does not do anything it simply loads it first while analysing it and then shows me the option to burn it with nero or decryptor .. nero does not work for me so i try to do it with decryptor ..the weird thing is that shrink creates its own ISO file .. a new one and then it uses that one for sending it to decryptor .. so there is no point in creating one from decryptor coz shrink anyway will create it again .. and i looked at all the options in shrink but it does not just say » burn » .. first option it says create iso and the second option is create iso and burn with decryptor … so there is no point in creating the ISO image with decryptor … am i missing something here laddyboy ??
for cyclic redundancy check i have tried all the options suggested by scuba pete like changing the settings and evrything but its same … its like one dvd out of 4 goes fine and rest three end up giving me coasters … not really sure what to do?
tell me one thing once the dvd has been read and i have an ISO file … what could be the issue after that .. could the ISO file itself be bad .. becoz i normally get errors when i have my ISO image already created either with shrink or with decryptor … i am using Khypermedia dvds , and IO magic burner 16X … i keep like real low speed while burning .. it normally gets burnt at 1.2X ..and i am ok with it but still errors … i am trying to burn Friends disk and i am getting cyclic redundancy error on both of them though i have created ISO image for both of them … what other softwares are good to create DVDs from ISO image except DVD clone as that dint work too …. again thanks for ur time laddyboy ….. glad that somebody is there to help …. let me know if u need any other info…
-
deadcat
Regular member- Joined:
- Apr 12, 2004
- Messages:
- 710
- Likes Received:
- 0
- Trophy Points:
- 26
if your getting errors trying to burn an iso then it is either media (khyper is not a recommended brand so should be first suspect), burning program (uninstall and reinstall latest version), dvd drive (make sure its in dma mode and latest firmware). Dont multitask, keep plenty of free space on hard drive
-
i have the exact same problem as muttman, i took iroettger’s advise and changed all the settings he listed. i then tried to decrypt the dvd.it was fine untill 30% then just frose at that percentage while counting the elapsed time.
-
hursty
Active member- Joined:
- Nov 22, 2004
- Messages:
- 4,618
- Likes Received:
- 1
- Trophy Points:
- 66
the only reason you rip it with decrypter first,is because shrink has had a problem,you decrypt with decrypter first, which will remove copyright,then you have to run it through shrink to compress it,the iso file you run through shrink(the one you create with decrypter)is not the same as the one you would have created using shrink first time around.the data has already been ripped.if thats makes any sense you are a cleverer man than i will be ever be!!!lol
with regards hursty -
laddyboy
Regular member- Joined:
- Jan 4, 2005
- Messages:
- 4,188
- Likes Received:
- 0
- Trophy Points:
- 46
burn_it: Here’s what I would do.
1. Uninstall Shrink, Decrypter, and Nero.
2. Reinstall newest Shrink, Decrypter, and Nero.
3. Update your DVD burner/reader to latest firmware.If you have problems with read errors (cyclical redundancy) after doing this, it could be from any of the usual culprits.
a. dirty/scratched disk (clean and wipe).
b. sector protected disk (try beta version of AnyDVD).
c. bad burner firmware (update to newest firmware).
d. bad cabling (unplug and plug back in).
e. other bad firmware/hardware on the the same channel (IDE, USB, FW)
e. bad burning media (try alternative media. use erasable RW media until you solve the problem)
f. bad DVD reader.Some of the newer disks are using protected sector anti piracy schemes that will cause the redundancy error. Try the beta version of AnyDVD.
Are you using your burner to rip the disks as well? Some burners are not good readers.
Who’s the OEM for your IO Magic burner? Lite-On, NEC, BenQ, AOpen, Asus?
-
darkdayz
Member- Joined:
- Jan 17, 2005
- Messages:
- 2
- Likes Received:
- 0
- Trophy Points:
- 11
after i write a cd with dvd decryptor and it completes 100% i get the finished sucessfully click OK box. but after i click OK this error pops up..
I/O Error!
Device: [1:0:0] PIONEER DVD-RW DVR-206D 1.07 (D (ATA)
ScsiStatus: 0x02
Interpretation: Check ConditionCDB: 25 00 00 00 00 00 00 00 00 00
Interpretation: Read CapacitySense Area: 70 00 03 00 00 00 00 0E 00 00 00 00 57 00 00 00 00 00 00 00 00 00
Interpretation: Unable to Recover TOCmy dvd writer is a PIONEER DVD-RW DVR-206D 1.07
the media i am using are Memorex DVD+R 8x 4.7gb 120mini have never had any problems with dvd decryptor in the past. my dvd writer has always worked fine and works with cd-r’s at the moment. i started getting these errors around the same time i started using this media but im not exactly sure if thats the problem. if anyone has information on this your help would be greatly appreciated.. thanks
-
hursty
Active member- Joined:
- Nov 22, 2004
- Messages:
- 4,618
- Likes Received:
- 1
- Trophy Points:
- 66
firstly is your pioneer compatible with dvd+r??
you can check with alcohol cd/dvd manager if you have it,or nero toolkit can also tell you.
secondly memorex is a poor quality media. -
darkdayz
Member- Joined:
- Jan 17, 2005
- Messages:
- 2
- Likes Received:
- 0
- Trophy Points:
- 11
i have used nothing but dvd+r media with my pioneer since i purchased it. it has always worked fine. im guessing thats it’s the Memorex but i don’t understand why the burn completes and i don’t get the error until i click OK.
-
hursty
Active member- Joined:
- Nov 22, 2004
- Messages:
- 4,618
- Likes Received:
- 1
- Trophy Points:
- 66
sorry,mis-read you post,
it must be a media issue then,you only have to flick through the forum to find if anyone has got a good word to say about memorex,you’ll have a job to find one.
with kind regards hursty
Share This Page