Asus CRW-5224A Drive Malfunction
Titoy
-
peps Posted messages 2225 Status Contributeur -
peps Posted messages 2225 Status Contributeur -
Hello,
I'm having a major issue with my Asus CRW 5224A burner. In Nero 6.0.0.11, when I start the burning process, the progress bar gets stuck at 5%, and the buffer bar below it freezes at 8%. The computer becomes very slow, the disk speeds up but then just stops. I tried cleaning the lens with a special CD, which allowed me to burn a new CD without problems. But the issue resurfaced with the next one. I decided to update the firmware (I installed version 1.40). Again, I was able to burn just one CD. Even reading CDs shows malfunctions except for music CDs. The problem appeared suddenly without any changes made to the computer. It happened overnight. I investigated the virus angle, and found nothing. I'm thinking about getting a newer version of Nero, but I'm hesitant since everything was working perfectly with this Nero and without any change in configurations.
If anyone can shed some light on this for me, I would be grateful.
See you later!
I'm having a major issue with my Asus CRW 5224A burner. In Nero 6.0.0.11, when I start the burning process, the progress bar gets stuck at 5%, and the buffer bar below it freezes at 8%. The computer becomes very slow, the disk speeds up but then just stops. I tried cleaning the lens with a special CD, which allowed me to burn a new CD without problems. But the issue resurfaced with the next one. I decided to update the firmware (I installed version 1.40). Again, I was able to burn just one CD. Even reading CDs shows malfunctions except for music CDs. The problem appeared suddenly without any changes made to the computer. It happened overnight. I investigated the virus angle, and found nothing. I'm thinking about getting a newer version of Nero, but I'm hesitant since everything was working perfectly with this Nero and without any change in configurations.
If anyone can shed some light on this for me, I would be grateful.
See you later!
9 réponses
Hello,
And on the memory side, have you checked if any abnormal memory clutter has occurred in your memory spaces (for example: ntma.exe, xpv.exe, or others; these are very interesting spyware programs but use a lot of memory space and CPU resources to transfer your configuration to a website).
Also, check all the processes that start upon booting your PC (you probably have some exciting background activities that are reducing your burning possibilities).
And on the memory side, have you checked if any abnormal memory clutter has occurred in your memory spaces (for example: ntma.exe, xpv.exe, or others; these are very interesting spyware programs but use a lot of memory space and CPU resources to transfer your configuration to a website).
Also, check all the processes that start upon booting your PC (you probably have some exciting background activities that are reducing your burning possibilities).
I do have a list of processes, but how can I tell which ones are useful and which ones are not? What is certain is that no application supposedly designed to improve performance, protect my system, or whatever other "memory optimizer" like Norton utilities is installed on my PC. There is only the bare minimum. Furthermore, between the day I was burning without any problem and the day I wasn't, I haven't modified or installed anything. Could the burner be to blame despite being just a year old???
Alright,
But it's like many things: You have to eliminate all possibilities before making a judgment; Especially since I don't have your machine in front of me. Regarding the two processes mentioned, it's not you who installs them; others take care of it when you browse the WEB (they are used by sites to track your navigation for ntma.exe; and the software installed on your PC for xpv.exe).
Now, there are still many possibilities:
If you are on XP Pro, go into the "administrative tools," and make sure that the "IMAPI burning service" is set to "Manual," otherwise, in addition to NERO, you will have the ROXIO EASY CD integrated by default in XP that will take over (it mainly manages the burning of multimedia formats). Running two burning software simultaneously is not viable.
But it's like many things: You have to eliminate all possibilities before making a judgment; Especially since I don't have your machine in front of me. Regarding the two processes mentioned, it's not you who installs them; others take care of it when you browse the WEB (they are used by sites to track your navigation for ntma.exe; and the software installed on your PC for xpv.exe).
Now, there are still many possibilities:
If you are on XP Pro, go into the "administrative tools," and make sure that the "IMAPI burning service" is set to "Manual," otherwise, in addition to NERO, you will have the ROXIO EASY CD integrated by default in XP that will take over (it mainly manages the burning of multimedia formats). Running two burning software simultaneously is not viable.
I'm running on a 2000 Pro. It’s not equipped with burning protocol. I tried to install the latest version of Nero as I mentioned (6.3) but nothing changes. Still stuck at 5% on the burning progress bar and 8% on the buffer. It's the buffer that’s causing the trouble... Usually, it runs between 97 and 100%. Now it stays at 8%, no wonder it won’t burn. But the question is, what could have affected this buffer overnight without changing anything on the PC, and why did it work twice without problems since this malfunction?
Well then, let's try something:
I haven't heard from you about the results of the test drive under NERO.
So you need to check that you have installed your utilities:
"Nero Info Tools", "Nero Drive Speed", "Nero CD Speed".
Take different discs that you have burned at different times at different speeds (4x; 8x; 16x; 24x; 48x).
Normally your burner is a 52x-24x, get it recognized by Drive Speed, then use Info Tools to analyze the disc and various sub-parameters; Finally, try Nero CD SPEED to test the quality of your burner’s work.
NOTE: I fully understand that you were below the desired memory threshold for burning (if the buffer falls below 92% for more than 10 seconds and your burner is not burn proof/steamless or equivalent: Crash), but several factors can come into play:
-Deactivation of DMA
-Registry modifications on memory management.
-Program interfering with Lead in/Lead out.
IMPORTANT: Under Win 2000, certain parameters and *.dll need to be updated to stabilize memory management; Install Service Pack 4, and load the necessary SYS and OCX DLLs to alleviate issues like: Unbuffered..., Unchecked Buffer...., Physical memory dump. If the installation of a program has modified and replaced some of these files with an older version, the problem currently encountered may result from this.
I haven't heard from you about the results of the test drive under NERO.
So you need to check that you have installed your utilities:
"Nero Info Tools", "Nero Drive Speed", "Nero CD Speed".
Take different discs that you have burned at different times at different speeds (4x; 8x; 16x; 24x; 48x).
Normally your burner is a 52x-24x, get it recognized by Drive Speed, then use Info Tools to analyze the disc and various sub-parameters; Finally, try Nero CD SPEED to test the quality of your burner’s work.
NOTE: I fully understand that you were below the desired memory threshold for burning (if the buffer falls below 92% for more than 10 seconds and your burner is not burn proof/steamless or equivalent: Crash), but several factors can come into play:
-Deactivation of DMA
-Registry modifications on memory management.
-Program interfering with Lead in/Lead out.
IMPORTANT: Under Win 2000, certain parameters and *.dll need to be updated to stabilize memory management; Install Service Pack 4, and load the necessary SYS and OCX DLLs to alleviate issues like: Unbuffered..., Unchecked Buffer...., Physical memory dump. If the installation of a program has modified and replaced some of these files with an older version, the problem currently encountered may result from this.
I did all the tests and got a rather satisfactory series of results.
Regarding the *.dll files, two weeks ago I caught a virus that forced me to delete a *.dll file. It was in "downloaded program files," so I thought it wasn't important for the system given its location. It seems that it was called Run32.dll, but I'm not sure.
Otherwise, given the weird noises the burner is making, I might ultimately prefer the possibility of a real breakdown.
Regarding the *.dll files, two weeks ago I caught a virus that forced me to delete a *.dll file. It was in "downloaded program files," so I thought it wasn't important for the system given its location. It seems that it was called Run32.dll, but I'm not sure.
Otherwise, given the weird noises the burner is making, I might ultimately prefer the possibility of a real breakdown.
Hello,
so you must have used an antivirus, and you sincerely think that it only deleted a RUN32.DLL. Surprise, it’s a file for linking various software in 32-bit mode! An amusing detail is that drivers, being primarily linking software, imagine the problems that can arise from the absence of dynamic links between your 16 and 32-bit burning software and the concerned device, knowing that an antivirus deletes all the *.dll *.ocx *.sys and *.exe files suspected of containing a viral writing error directly in 16-bit mode.
I recommend you take the following precautions:
a) Go to a healthy machine, create a bootable antivirus floppy disk.
b) Put this floppy disk in your A drive, set your setup to boot A first.
c) Run a test for the residual presence of viral packs, then check the results.
d) Once this control is done, you will be sure that your C drive boot contains no viral replicators, and you'll see an impressive list of destroyed files that were not replaced.
e) You will likely need to redo your entire system installation, but once this step is completed, your problem should certainly be resolved. Let’s say the virus is a derivative of KLETZH, it attacks the hardware (hard drive, peripherals), distorting their handling by the system and imposing abnormal usage: rapid wear of your hardware.
NOTE: I hope you have a backup of your work and the installation of all your software, because you will likely need to destroy your entire current installation to redo it (including the FAT or NTFS present).
so you must have used an antivirus, and you sincerely think that it only deleted a RUN32.DLL. Surprise, it’s a file for linking various software in 32-bit mode! An amusing detail is that drivers, being primarily linking software, imagine the problems that can arise from the absence of dynamic links between your 16 and 32-bit burning software and the concerned device, knowing that an antivirus deletes all the *.dll *.ocx *.sys and *.exe files suspected of containing a viral writing error directly in 16-bit mode.
I recommend you take the following precautions:
a) Go to a healthy machine, create a bootable antivirus floppy disk.
b) Put this floppy disk in your A drive, set your setup to boot A first.
c) Run a test for the residual presence of viral packs, then check the results.
d) Once this control is done, you will be sure that your C drive boot contains no viral replicators, and you'll see an impressive list of destroyed files that were not replaced.
e) You will likely need to redo your entire system installation, but once this step is completed, your problem should certainly be resolved. Let’s say the virus is a derivative of KLETZH, it attacks the hardware (hard drive, peripherals), distorting their handling by the system and imposing abnormal usage: rapid wear of your hardware.
NOTE: I hope you have a backup of your work and the installation of all your software, because you will likely need to destroy your entire current installation to redo it (including the FAT or NTFS present).
Yes, but I remind you that this file was located in the "Downloaded program files" folder, which is a sort of trash folder for certain Internet files. So it shouldn't have any impact on the functioning of my machine. I would like to avoid reinstalling everything just because of that. I'm doing a final test and I'll let you know how it goes.
@+
@+
Hello,
Well, we’re not going to beat around the bush for two centuries:
You downloaded a program or software from a monitored site (certainly illegal material). You find a RUN32.dll in the Internet Download files because it couldn't load: So, you're running on Win 2000 or XP (rundll32.exe); This file was supposed to be registered in the system directory (replacing the modified one during activity), called up by those listed in your FAT and your registry, and moreover, command lines meant to prevent access to the burner by software like WinCD, Clone CD, Nero, etc... Under Win 98 and Win Me. Example:
the Clone CD startup line:
Run CloneCD Run32.dll C:\Windows\System\run32.dll services/run-C
you will note that the -C command excludes the hard drive from the process and thus the access to system resources for this software, guess what happens next.
Result: You found a parasite that didn’t load because your system doesn’t meet its standards; But you didn’t find the others, which do meet those standards, and are registered in the first contiguous sectors at the boot of your hard drive, or have inserted command lines into vital files and are now part of your operating system's loading scheme.
By the way, you will notice that you reach 8% burning under NERO, so we must admit that the pack is poorly finished. Normally you should open Nero and receive a message about insufficient memory or a full and/or write-protected disk (we can assume that this is due to the standards incorporated into your burner to counteract data transfer interruptions).
Well, we’re not going to beat around the bush for two centuries:
You downloaded a program or software from a monitored site (certainly illegal material). You find a RUN32.dll in the Internet Download files because it couldn't load: So, you're running on Win 2000 or XP (rundll32.exe); This file was supposed to be registered in the system directory (replacing the modified one during activity), called up by those listed in your FAT and your registry, and moreover, command lines meant to prevent access to the burner by software like WinCD, Clone CD, Nero, etc... Under Win 98 and Win Me. Example:
the Clone CD startup line:
Run CloneCD Run32.dll C:\Windows\System\run32.dll services/run-C
you will note that the -C command excludes the hard drive from the process and thus the access to system resources for this software, guess what happens next.
Result: You found a parasite that didn’t load because your system doesn’t meet its standards; But you didn’t find the others, which do meet those standards, and are registered in the first contiguous sectors at the boot of your hard drive, or have inserted command lines into vital files and are now part of your operating system's loading scheme.
By the way, you will notice that you reach 8% burning under NERO, so we must admit that the pack is poorly finished. Normally you should open Nero and receive a message about insufficient memory or a full and/or write-protected disk (we can assume that this is due to the standards incorporated into your burner to counteract data transfer interruptions).