Jump to content

Recommended Posts

Posted

Hello there. A few weeks ago, this error started popping everytime I started to record something:

 

wujm2s.jpg

 

 

The part after reason says "The device doesn't recognize the command".

Posted

1) Well, if I hit Retry the error doesn't appear again (like it's supposed to, it ignores mounted file system drivers) and if I hit Continue the burn goes like normal, but the strange thing is that the error didn't appear until a few weeks ago, after I successfully burned several disks.

 

2) AIDA64 shows two controllers: Standard AHCI 1.0 Serial ATA Controller and JMicron JMB363 SATA-II RAID Controller.

 

Thanks in advance, you've done a great job with the program.

Posted

Right click the drive selection box in ImgBurn (when in Write mode), pick 'Family Tree', close the prompt and then copy + paste everything from the Log window please.

Posted

I 01:36:57 ImgBurn Version 2.5.7.0 started!

I 01:36:57 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7601 : Service Pack 1)

I 01:36:57 Total Physical Memory: 8.379.568 KB - Available: 6.540.768 KB

I 01:36:57 Initialising SPTI...

I 01:36:57 Searching for SCSI / ATAPI devices...

I 01:36:58 -> Drive 1 - Info: ATAPI iHAS224 B GL0A (D:) (SATA)

I 01:36:58 Found 1 DVD±RW/RAM!

I 01:37:05 Device: [3:0:0] ATAPI iHAS224 B GL0A (D:) (SATA)

I 01:37:05 Family Tree:

I 01:37:05 -> ACPI x64-based PC

I 01:37:05 -> Sistema Microsoft compatible con ACPI

I 01:37:05 -> Bus PCI

I 01:37:05 -> Controladora ATA de serie AHCI 1.0 estándar (VEN_8086&DEV_3A22 - Intel - msahci - v6.1.7601.17514)

I 01:37:05 -> Canal IDE (ATA Channel 1)

I 01:37:05 -> Unidad de CD-ROM (ATAPI iHAS224 B ATA Device) (Channel 1, Target 0, Lun 0)

Posted

I installed both files and is still giving me the same error. Just for curiosity, what are the likely (and unlikely) causes for the error?

Posted

Can you post an updated log showing the family tree info again please.

 

Can you also post the filter driver list (use the feature in the Tools menu and copy to clipboard+paste).

 

The likely causes for the problem are drivers - hence my comment in post #2.

Posted (edited)

I 16:31:44 ImgBurn Version 2.5.7.0 started!

I 16:31:44 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7601 : Service Pack 1)

I 16:31:44 Total Physical Memory: 8.379.568 KB - Available: 6.579.860 KB

I 16:31:44 Initialising SPTI...

I 16:31:44 Searching for SCSI / ATAPI devices...

I 16:31:45 -> Drive 1 - Info: ATAPI iHAS224 B GL0A (D:) (ATAPI)

I 16:31:45 Found 1 DVD±RW/RAM!

I 16:31:49 Device: [0:0:0] ATAPI iHAS224 B GL0A (D:) (ATAPI)

I 16:31:49 Family Tree:

I 16:31:49 -> ACPI x64-based PC

I 16:31:49 -> Sistema Microsoft compatible con ACPI

I 16:31:49 -> Bus PCI

I 16:31:49 -> Intel® ICH10R SATA AHCI Controller (VEN_8086&DEV_3A22 - Intel - iaStor - v11.2.0.1006)

I 16:31:49 -> Unidad de CD-ROM (ATAPI iHAS224B ) (1)

 

===============================================

Filter Driver Load Order - ImgBurn v2.5.7.0

===============================================

 

Upper Device Filter: [None Found]

Upper Class Filter: GEARAspiWDM

Device: CD/DVD-ROM Device

Lower Class Filter: PxHlpa64

Lower Device Filter: [None Found]

 

Filter Name: GEARAspiWDM

File Name: C:\Windows\System32\Drivers\GEARAspiWDM.sys

File Version: 2.0.6.1

File Description: CD/DVD Class Filter Driver

Product Name: GEAR.wrks

Product Version: 8.xx [2.0.6.1]

Company Name: GEAR Software Inc.

Copyright: Copyright © GEAR Software Inc. 2006

 

Filter Name: PxHlpa64

File Name: C:\Windows\system32\Drivers\PxHlpa64.sys

File Version: 3.00.43J [3.0.43.9]

File Description: Px Engine Device Driver for 64-bit Windows

Product Name: PxHelp64

Product Version: [2.0.0.0]

Company Name: Sonic Solutions

Copyright: Copyright © Sonic Solutions

Edited by Orimarc
Posted

Tried that, still gives the same error, except that the second line now says:

 

Device: [0:0:0] ATAPI iHAS224 B GL0A (D:) (ATAPI)

Posted

Try it in safe mode and see if you have the same problem.

 

It must be something installed/running on your PC because it's working fine for me and you appear to be the only person with the issue.

×
×
  • Create New...

Important Information

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