RCX 262 CONSTANTLY crashing

[Chris Ratledge]

Okay, I'm kina at my wit's end with this....

I'm using RedCine-X 262 to review footage, apply light look correction and export 1080 QT's for offline editing, and I must have 4-8 hard, kernel panic machine crashes per day.

I have the latest driver version for my rocket card, no old legacy versions of RCX installed, in fact no remaining legacy software at all. Even backed up my layouts and such before trashing prefs and application support in OSX before re-downloading and installing new. Still with the crashes. It appears to be totally random. Sometimes during playback, sometimes during transcoding. Sometimes when RCX is the only thing running, sometimes when ingesting with R3D data manager (to a different destination than I am reviewing in RCX), and sometimes while running when R3D DM is just open in the background but not copying footage. Doesn't seem to matter which volume I'm accessing when playback causes the crash, could be my RAID, the Primary, or the BU.

So what do I need to submit the next time I have one? I'm due for at least another 3 or so today based on my track record. Really frustrating. Didn't have these problems last week, this week all hell is breaking loose. I'm about to just rebuild the entire system from scratch over the weekend, but I'm not sure that'll solve anything at this rate.

Anyone?

 

[David Ibbitson]

Hi Chris,

Please send a system profile, and any log files relevant to your crashing to redcinex at red dot com. Make sure verbose logging is enabled. Also in your email please include any details you think are relevant.

You could also try upgrading to Build 340. However, from what you are describing it sounds like something is wrong with your system.

David

 

[Chris Ratledge]

I was afraid you would say that.... terrific!

Okay, I'll collect that this weekend and send it along, before rebuilding the system and sending a new version after the rebuild. I don't have time on location to do this all today.

 

[Chris Ratledge]

You could also try upgrading to Build 340.

I thought about doing this, but this is just a beta, correct? Isn't 262 supposed to be the "stable" beta? Or is the thinking at this point it can't really be any worse?

 

[David Ibbitson]

No problem, send when ready. We try to maintain a pretty quick turnaround on bug reports. So if there is a bug, and not already addressed in a later build, we'll get it fixed asap.

David

 

[David Ibbitson]

262 is a stable beta, for the feature set it contains. Newer builds always go up on RedUser first, because we're always pushing new features and looking for feedback from the community.

340 is pretty stable, and theres been some good feedback from the community since its release. We've fixed some issues with it. The goal is to get a solid and stable build up on the support site in the near future.

David

 

[Johnny Friday]

I'm using build 340 DAILY and only issue i have is with saving a project. It's been very stable as long as when you go to open up your project you open up RCX first, then to go "open project" then choose your project...about 70/30 crash this way...if you go to the .rcx project file or when i do...100% crash. BUT for transcoding, color and saving RMD's.....works brilliant. WAY better than previous builds.
Better try that before rebuilding your system.

 

[Chris Ratledge]

...if you go to the .rcx project file or when i do...100% crash. BUT for transcoding, color and saving RMD's.....works brilliant. WAY better than previous builds.
Better try that before rebuilding your system.

Good info here Johnny, thank you. I too have noticed weirdness when trying to save/open project files.

I think I'm opting for doing BOTH actually, rebuild AND 340.

 

[David Ibbitson]

Also the crashing on project load has been fixed and will be included in the next release.

 

[Chris Ratledge]

Had a software crash today, first one! This time no GSOD, but RCX itself crashed in the middle of ROCKET transcoding. Simple finder copy going on in background from separate source/destination, but that was the only other thing going on at the time of the crash.

Collected RCX log file, apple crash report, and system profile and will be emailing shortly.

 

[Chris Ratledge]

I just wiped my system over the weekend, did a fresh OSX install on a new boot disc, lean and mean with crucial system software only. (boot disc is now only about 30GB) Now running 10.6.3, RCX 340, Rocket, eSATA, GT120. Reset PRAM, re-seated all cards, drives, memory.

Just playing clips back this morning, GSOD. Twice. I sent my crash reports off to RED right away. It ALWAYS happens when running RCX. If I'm reading the text below from the Kernel Panic report correctly, it looks like I'm having some sort of memory read error?

Wed Oct 27 09:19:05 2010
Machine-check capabilities (cpu 4) 0x0000000000001c09:
family: 6 model: 26 stepping: 5 microcode: 17
Intel(R) Xeon(R) CPU E5520 @ 2.27GHz
9 error-reporting banks
threshold-based error status present
extended corrected memory error handling present
Machine-check status 0x0000000000000004:
machine-check in progress
MCA error-reporting registers:
IA32_MC0_STATUS(0x401): 0x0000000000000800 invalid
IA32_MC1_STATUS(0x405): 0x0000000000000800 invalid
IA32_MC2_STATUS(0x409): 0x0000000000000000 invalid
IA32_MC3_STATUS(0x40d): 0x0000000000000000 invalid
IA32_MC4_STATUS(0x411): 0x0000000000000000 invalid
IA32_MC5_STATUS(0x415): 0x0000000000000000 invalid
IA32_MC6_STATUS(0x419): 0x0000000000000000 invalid
IA32_MC7_STATUS(0x41d): 0x0000000000000000 invalid
Package 0 logged:
IA32_MC8_STATUS(0x421): 0xfe0001000001009f valid
Channel number: 15 (unknown)
Memory Operation: read
Machine-specific error: Read ECC
COR_ERR_CNT: 8
Status bits:
Processor context corrupt
ADDR register valid
MISC register valid
Error enabled
Uncorrected error
Error overflow
IA32_MC8_ADDR(0x422): 0x0000000127a2d480
IA32_MC8_MISC(0x423): 0xfa3fdc1900081487
DIMM: 0
Channel: 2
Syndrome: 0xfa3fdc19
Package 1 logged:
IA32_MC8_STATUS(0x421): 0x0000000000000000 invalid
panic(cpu 4 caller 0x2a7c94): Machine Check at 0x002945e1, thread:0x1437b7a8, trapno:0x12, err:0x0,registers:
CR0: 0x80010033, CR2: 0x258dd000, CR3: 0xcc024000, CR4: 0x00000660
EAX: 0x00000000, EBX: 0x27a2d000, ECX: 0x00000260, EDX: 0x00001000
ESP: 0x8e963d78, EBP: 0x8e963da8, ESI: 0x00000001, EDI: 0x819b2680
EFL: 0x00010206, EIP: 0x002945e1

Backtrace (CPU 4), Frame : Return Address (4 potential args on stack)
0x81994fb8 : 0x21b449 (0x5ce420 0x81994fec 0x2238a5 0x0)
0x81995008 : 0x2a7c94 (0x590140 0x59022d 0x2945e1 0x1437b7a8)
0x819950f8 : 0x29f912 (0x1 0x4f493e79 0x766f7250 0x72656469)
0x8e963da8 : 0x2a6df6 (0x27a2d000 0x1 0x1000 0x27bbfd)
0x8e963dc8 : 0x254256 (0x127a2d 0x1 0x802128 0x5309f50)
0x8e963df8 : 0x258157 (0x13a66b90 0xb5000 0x0 0x3)
0x8e963f38 : 0x2a839c (0x13605d74 0x258dd000 0x1 0x3)
0x8e963fc8 : 0x29e80a (0x14a99a64 0x0 0x10 0x0)

BSD process name corresponding to current thread: REDCINE-X