Hi I'm new here and new to Nero. I have been pulling my hair out for several days over the fact that Nerovision is "crashing" during the transcoding of my first projedt. I am trying to make a DVD slide show with 69 pictures, random transitions, and music. I run W2000, on a Gateway with a 1GHZ Athlon and 128MB memory. I was crashing as soon As I started to transcode. Sometimes I got an error from W200 that my virtual memory was set to low. Just for the heck of it I ran W2000 Task monitor at the same time as Nerovision and discovered that Nerovision crashed when the the Task Monitoor indicated that the Comit Charge limit had been reached. So I wnet in and increased the Virtual memory limit to 1000MB and now she is running fine. For some reason the Comit Charge (dont ask me what that means) keeps creeping up while Nerovision is doing it's thing. I dont know it this is a problem with Nerovision or if it is normal. Thos of you who know more about w2000 might wnat to venture an opinion here because I would be interested in knowing what the "comit Charge" is and if it is normal for this number to keep on creeping up as Nerovision runs. It looks like Nerovision is using all the memory it can get and not releasing it back into the available memory pool when it is through with it. JMHO Please try running your task monitor in w2000 alongside Nerovision just to see what kind of results you get on the "comit charge" numbers. Bob
I just found this in the web <snip> The commit charge is the cumulative amount of memory used by all of your open/running applications and processes. As you continue to use programs, the amount of memory they use may grow; an abnormal increase in memory consumption could also be indicative of a "memory leak" in a program. If you sort the processes listed in Task Manager's Process tab by "Mem Usage" and monitor them, you should be able to determine which processes are responsible for "chewing up" your memory. Have a look at that and tell us the names of the programs which seem to be the most "piggy" in terms of memory usage. <snip> It would appear my hunch about a bug in Nerovision not releasing the memory is correct. The above article states that there is a probable "memory leak" in Nerovision which causes the phenomenom I described in the previous post. Bob
