Jump to content

olger901

Members
  • Posts

    3
  • Joined

  • Last visited

Posts posted by olger901

  1. Hi all,

     

    I do not really know if it is either a bug of NOD32 or a bug of ImgBurn, but would like to report it anyway, because the rising of CPU usage, can sometimes occur because of security bugs, and potentionally lead to DoS attacks. Every time ImgBurn finishes downloading from a website (to update), or whenever I run the installation of ImgBurn, all of the processor usage suddenly goes to nod32krn.exe and have to kill nod32krn.exe to be able to let the installation continue. (The exact moments it occurs on is when the download finishes at 100% (using Mozilla Firefox 2.0.0.3; it just hangs) and when the copying of the files start during the installation process.)

  2. EDIT: Ah but you might have hit a more general bug that I just fixed in 2.3.2.0 that calculated the sector size used in the image incorrectly.

     

    I don't think it being a small image was the problem at all.

     

    Try 2.3.2.0 and let me know how you get on.

     

    This bug seems to be fixed in 2.3.2.0 indeed, I had a similar bug occurring, while burning memtest 86+ v1.70, just tried burning it with 2.3.2.0 and seems to have burned okay.

×
×
  • Create New...

Important Information

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