Possible segfault(?) after a few frames rendering

'Lo all,

I’ve been pulling my hair out all day today trying to figure this out. I’m rendering out my own take on this tutorial

and every time I get to around 10 to 20 rendered images completed in a 110 frame animation that is saving out to pngs, Blender inexplicably crashes. I’ve run memory checks on my 16 gigs of ram (of which while rendering blender never consumed more than two gigs), I’ve updated my graphics drivers for my GeForce 560 up, down, and beta, I’ve switched from my Windows 7 installation to my dual boot Ubuntu distro, and the bios is up to date as of a month ago, I’ve even tested on newer and older builds from graphicall, and no matter what I change, the crash consistently happens.

I ran Blender this past time through the cli with the -d option, here’s what it output up to the moment it crashed - I had to trim the header of the output off to fit within the posting limits, not sure how to attach a larger text.

 1 (   0.000     0.203) spacetype logic
 1 (   0.000     0.203) spacetype info
 1 (   0.000     0.203) spacetype nla
 1 (   0.000     0.203) spacetype userpref
 1 (   0.000     0.203) spacetype text
 1 (   0.000     0.203) spacetype clip
 1 (   0.000     0.203) spacetype buttons
 1 (   0.000     0.203) spacetype action
 1 (   0.000     0.203) spacetype console
 1 (   0.000     0.203) spacetype node
 1 (   0.000     0.203) spacetype sequencer
 1 (   0.000     0.203) spacetype file
 1 (   0.000     0.203) spacetype script
 1 (   0.000     0.203) ButsContextPath
 1 (   0.000     0.203) spacetype image
 1 (   0.000     0.203) spacetype view3d
 1 (   0.000     0.195) spacetype info menu recent files
 1 (   0.000     0.195) spacetype node menu add
 2 (   0.000     0.094) window timer
 8 (   0.000     0.023) fsme
 1 (   0.000     0.164) spacetype clip region tools
 1 (   0.000     0.164) RENDER_OT_render
 1 (   0.000     0.164) spacetype view3d tool properties region
 1 (   0.000     0.164) spacetype clip region properties
 1 (   0.000     0.164) spacetype clip region preview
 1 (   0.000     0.164) spacetype view3d tools region
 1 (   0.000     0.164) spacetype view3d buttons region
 1 (   0.000     0.164) spacetype view3d header region
 1 (   0.000     0.164) spacetype view3d main region
 1 (   0.000     0.164) spacetype clip tool properties region
18 (   0.000     0.008) UI UnitSettings
 1 (   0.000     0.133) render job
 1 (   0.000     0.133) event modal handler
 3 (   0.000     0.039) memarena
 1 (   0.000     0.109) bContext
 1 (   0.000     0.109) window event state
 1 (   0.000     0.102) DM-BoundBox
 1 (   0.000     0.102) cached frames array
 1 (   0.000     0.090) file_layout
 1 (   0.000     0.086) ParticlDrawData
 1 (   0.000     0.078) bAddon
 1 (   0.000     0.070) wmDrawTriple
 1 (   0.000     0.063) mtfacenames
 1 (   0.000     0.063) view2d tab offset
 1 (   0.000     0.055) BVHTree
 1 (   0.000     0.055) threadslot
 1 (   0.000     0.047) make_sss_tree gh
 1 (   0.000     0.047) imb_thread_cache_init gh
 1 (   0.000     0.047) tile_cache_params gh
 1 (   0.000     0.047) wm_operatortype_init gh
 1 (   0.000     0.047) menutypes_hash gh
 1 (   0.000     0.047) dag_add_node gh
 1 (   0.000     0.047) icons_init gh
 2 (   0.000     0.021) Data from TXT
 1 (   0.000     0.039) wmOperatorReportList
 1 (   0.000     0.039) DAG root
 1 (   0.000     0.023) fsmenu
 1 (   0.000     0.023) wmOperatorPtrRNA
 1 (   0.000     0.023) RecentFile
 1 (   0.000     0.016) effectors list
 1 (   0.000     0.016) folderlist
 2 (   0.000     0.008) rng

Evaluate all animation - 2.400000
No Actions, so no animation needs to be evaluated…
recalcob Text
recalcdata Text
recalcob Camera
pass on evt 260 val 0

I dropped a compsci major for graphics a few years ago, so most of that goes over my head. Maybe someone here will notice something of value?

It may be important to note that the exact same files function just fine on two other machines running Ubuntu, and a 2008 era MacBook Pro. Only on this brand new machine I built for this express purpose does this happen. Any ideas or suggestions?

I’m running additional memory tests on each stick after an extended windows memory diagnostic testing session stated that there could be a problem with one of my four gig sticks. This could be good news. Just wish it didn’t take so long.

Testing showed that 2 of the four memory sticks in my system are faulty, and running solely on the two functional sticks seems to have solved the crashing issue. Word to the wise, don’t trust the Windows Memory Diagnostic tool. It passed over my sticks as if they were fine. Use Memtest instead.