The whole system crashes ("Blue Screen"), the whole system gets stuck:

If the whole system crashes or gets stuck, then it is NOT Feurio!'s fault - as a normal application Feurio! doesn't have the rights to cause such a crash.
As a general rule, this is a driver problem.
Suggestions for remedy:

• Call up system diagnosis:
  Feurio! has integrated system diagnosis which can recognize most problems.
  Start the Feurio! CD-Writer and in the menu there call up: "Extras" "Carry out system diagnosis" and deactivate the driver recognized by the system diagnosis as being problematic.
  
  
• Deactivate Busmaster operation for the CD-Writer
  SomeCD burners are not busmaster-capable or some busmaster drivers don't work correctly with CD writers - if in doubt, deactivate the Busmaster operation for the CD-Writer.
  For more information on this, see: "Busmaster drivers".
  
  
• Faulty Busmaster driver
  Unfortunately some Busmaster drivers are faulty (in particular e.g. VIA drivers) - here the only remedy is unfortunately to deinstall the Busmaster driver completely and install the Windows standard driver.
  VIA themselves in the meantime expressly recommend NOT using the VIA Busmaster driver for CD writers!
  You will find details on deinstalling the Busmaster driver in the documentation provided with your computer.
  For more information on this, see: "Busmaster drivers".
  
  
• Interrupt Collisions
  Interrupt collisions (or other resource collisions) are a reason for this. Call up the device manager (Start -> Settings -> Control Panel -> System -> Device Manager) and check if a device is marked with an exclamation mark. If so, follow the advice given by the device manager.
  
  
• Interrupt-Sharing
  The PCI-Bus supports so-called "Interrupt-Sharing", i.e. several PCI cards "share" an Interrupt. This makes sense and is necessary, as only a limited number of interrupts are available.
  Unfortunately this "Interrupt-Sharing" is not implemented correctly in all cards/drivers. Some drivers just crash if the interrupt of "their" card is "shared" with another card.
  Call up the device manager (see above) and double-click on the "Computer" icon. You will then be given a list of interrupts and the devices sharing these interrupts. (Windows NT: Call up "Start" -> "Programs" -> "Management (General)" -> "Windows NT-Diagnosis" -> "Resources").
  If two devices are "sharing" the same interrupt, this CAN be a problem - as mentioned, it SHOULDN'T actually be a problem - but practice has shown that not all drivers work correctly!
  Try to allocate individual interrupts to the devices (activate manual resource distribution in the device manager or reset the resource distribution in the computer's BIOS. On this, refer to your manuals / documentation with your computer / operating system).
  TIP: To see if interrupt sharing is the problem at all, it can also make sense to remove unnecessary components from the computer while burning (e.g. network card, ISDN card, etc.) or to deactivate them in the BIOS. If components are removed, then interrupt sharing is no longer necessary.
  If the error no longer occurs after removing the components, then there is either a problem with interrupt sharing or the driver for the components is not working correctly. In this case contact Support of the manufacturer of the components.
• Other faulty drivers
  Unfortunately drivers for hardware components which are NOTHING to do with burning (e.g. graphics card drivers) have turned out to be the cause of such problems. As every driver runs in "Kernel mode", unfortunately errors in the driver are "disastrous".
  Here we can unfortunately only recommend reinstalling Windows and - as far as possible - only using the Windows standard drivers.
• Insufficient power supply
  More often than you would think, the POWER SUPPLY is responsible for such errors. In particular "Cheap PCs" from supermarkets are often supplied with a very tightly calculated power supply which is just enough to run the PC. The few watts that the CD writer needs in addition can already be too much for the power supply - under the high load it no longer supplies a 100% clean voltage which can then lead to computer errors in the CPU. This error is particularly mean as it only occurs sometimes.
  A power supply should have AT LEAST 200 watts - if a "power hungry" CPU and maybe a "modern" (i.e. also "power hungry") graphics card, a lot of memory or even several CD writers should all be used, 230 watts is the minimum - if several of the factors are simultaneous (i.e. 700 MHz processor, GeForce graphics card) it has better be 300 watts!
• Other devices attached to the BUS
  Sometimes such problems are caused by other devices connected to the SCSI or IDE-BUS. In particular SCSI scanners often don't have a "correct" SCSI interface.
  Also e.g. SCSI-ZIP drives can interrupt the SCSI-Bus!
  Remove all unnecessary hardware (Scanner, ZIP, MO, other CD-ROM) from the system and test the "Basic configuration" again. If the error no longer occurs, then it was due to one of the other devices. Now connect up all the other devices one at a time and thus test to find out which device it is.
  Once you have found the "faulty" device, unfortunately there are only 2 possibilities: a) turn to the vendor of the device and hope that he can remedy the error or b) clamp off the device when you are going to write CDs.
  
  
• Hardware Error
  Sometimes it is just that e.g. the IDE cable is loose, the SCSI cabling is incorrect (wrong termination) or there is another hardware error.
  Just test and see what happens with another burner program. If the error occurs here as well, then there is either a conflict between drivers or a hardware error.
  

Feurio! crashes

If Feurio! crashes ("This application is being closed due to an invalid procedure"), then as a general rule this is an error by Feurio.
First of all, have a look and see if there is already a newer version of Feurio! out (See: "Updates") - the error has often already been remedied.
If there is no newer version of Feurio!, please contact our Support (See: "Support"). Describe the error as accurately as possible - if you just say "Feurio! crashes" we can't do much about it.
If a message appears, send us the exact message - including the crash details in particular or the "Dr.Watson-Log" which are very important for us.
We will also need information on your system configuration. The simplest thing to do is: In the Feurio! CD.-Writer under "Extras" select "Generate Report " and enclose the report with the mail.

Feurio! gets stuck while burning!

If in principle Feurio! is still running (i.e. the dialog box still reacts), but the burning process isn't running any more, the following could help:

• Call up system diagnosis:
  This can also be caused by faulty outside drivers. In the Feurio! CD-Writer under "Extras", call up "Carry out system diagnosis" and deactivate the driver recognized as causing a problem.
  
  
• Problems with the option "Don't fill recorder buffer completely";
  Feurio! offer an option in which it doesn't fill the buffer of a recorder completely. This prevents the bus getting blocked (in particular with IDE-CD writers). It can thus sometimes help to deactivate this option:
  • Start Feurio! CD-Writer
  • Select the CD-Writer with which the problem is occurring
  • Click on "Info"
  • Select theindex card "Settings"
  • Deactivate the switch "don't full recorder buffer completely", if it was activated
  
  If this doesn't help, see point 2.

You are the 123. visitor of this page (today: 2)