-
Problems adding to projects together
Posted by Rennie Cluver on December 5, 2011 at 7:57 pmI am trying to add to vegas projects together to make a 28 minute video and I received a NOT RESPONDING error which read as the following…
Application Version = 9.0e (Build 1147)
Problem: Unmanaged Exception (0xc06d007e)
Fault Module: C\windows\system32\KERNELBASE.dll
Fault Address: Ox7513D36F
Fault Offset: 0x0000D36FCan anyone help me with this issue? Do I need to prerender projects before putting them together? I need to finish the 28minute video and send to DVD Architect as soon as possible.
Don Cobble replied 14 years, 9 months ago 3 Members · 6 Replies -
6 Replies
-
Stephen Mann
December 5, 2011 at 11:05 pm“Unmanaged Exception” errors are almost always a driver issue.
You could simply open a new project and drag each veg file to the timeline to make a single parent project.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
Rennie Cluver
December 6, 2011 at 3:33 amThanks for the info…I was able to combine projects but now it wont render. Says system low on memory (try closing other applications that are runnin etc.) I have ran into this before and not sure how I fixed it. I have plenty of RAM because I just had more installed and they put in the max which is 16GB. Any thoughts?
-
Stephen Mann
December 6, 2011 at 3:18 pm[Rennie Cluver] “. Says system low on memory”
“… but that’s not the case because I have X Gb of RAM so that shouldn’t be the problem.”
Low Memory or Out of Memory does not mean “Not enough RAM”, though adding RAM can sometimes fix a “Low Memory” waning. A “Low Memory” warning usually means that you have exceeded your commit limit. You need either a bigger page file, more physical memory, or both.
One of the biggest sources of confusion over Windows memory usage is the whole concept of virtual memory compared to physical memory. Windows organizes memory, physical and virtual, into pages. Each page is a fixed size (typically 4 KB). To make things more confusing, there’s also a page file (sometimes referred to as a paging file and dynamic RAM). Many Windows users still think of this as a swap file, a bit of disk storage that is only called into play when you absolutely run out of physical RAM. In versions of Windows starting with Vista, that is no longer the case. The most important thing to realize is that physical memory and the page file added together equal the commit limit, which is the total amount of virtual memory that all processes can reserve and commit.
Start the Task Manager, click on the “Processes” tab, then click on “Commit Size” to sort by size. This will show you which processes are memory hogs that you may be able to shut down.
In this screenshot, the two biggest memory hogs are Firefox and Thunderbird. Neither of which are needed during rendering.
All Windows since XP (and Unix/Linux for that matter) always wants to have page space. Always. Programs (including drivers and codecs) like to and are allowed to pre-allocate as much memory as they want. Even if they are never ever going to actually use it. Sometimes those programs properly deallocate memory, sometimes they don’t (resulting in “memory leak”). Sometimes, programs leave parts of themselves in allocated memory just in case you are going to run that program again. (MS Word, Excel and other Office programs are particularly adept at this). If you have no page file and a program wants to commit some for itself, your PC will crash (AKA, BSOD, or Blue Screen of Death).
Paging file configuration is in the System properties, which you can get to by typing “sysdm.cpl” into the Run dialog, clicking on the Advanced tab, clicking on the Performance Options button, clicking on the Advanced tab, and then clicking on the Change button. I would suggest a value of 1.5X the currently allocated value. The old advice of 2X or 3X your RAM is, well, old advice when a few MB of RAM was normal. The largest paging file that you can select in Windows is 4,095 megabytes (MB).
Also, Windows supports up to 16 paging files, but each must be on a separate volume, so if you have more than one internal disk drive you could try enabling a Paging File on your second hard-disk. DO NOT put a paging file on an external drive because if it’s not present when Windows boots, then Windows will crash.
For more information, see https://support.microsoft.com/kb/237740 and https://support.microsoft.com/kb/2267427
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
Don Cobble
December 7, 2011 at 12:05 amSir Stephen, I also am having shut downs ever time I try to render in V11. If I understand correctly, adding page filing may help the rendering process? and that I can have page filing on more than 1 internal HD and that is an advantage? Last do you recommend page filing on my OS drive?
thank UPC
I7 2.8 Ghz 8GB Ram
Win 7 Pro 64bit OS
PNY Quadro 40003-4 TB HD
Vegas 10 64bit & Vegas 11 64Bit & Adobe Production Premium CS5.5Camera
Sony EX1 shoot in 1920×1080 30P -
Stephen Mann
December 7, 2011 at 5:17 amPlease clarify your question. I am seeing two unrelated questions in your posts. First you say the program is shutting down, and then you say you are low on memory. Adding more pagefiles, or making your single pagefile bigger, as well as closing memory hogging programs like Firefox and Thunderbird may help the low memory error from windows.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
Don Cobble
December 7, 2011 at 8:32 pmClarification:
My problem is Vegas will not render without shutting down.
My questions were based on your post about page filing.
1) will increase page filing help rendering?
2) can you have page filing on multiple drives?
3) If yes, do you recommend page filing on the drive that contains the OS?
this is what i meant to be asking
thank UPC
I7 2.8 Ghz 8GB Ram
Win 7 Pro 64bit OS
PNY Quadro 40003-4 TB HD
Vegas 10 64bit & Vegas 11 64Bit & Adobe Production Premium CS5.5Camera
Sony EX1 shoot in 1920×1080 30P
Reply to this Discussion! Login or Sign Up
