RTSS/EncoderServer crash relating to C++ runtime

Ok so for some reason with Beta 17 + RTSS 5.4.1 my game started to crash (Mass Effect 3). I could play a while and then it stopped working. That was before when prerecoring buffer ran in Game's address space. Now im using Beta 18 + RTSS 6.0.0 but now it's EncoderServer that crashes. Thankfully the game keeps running now because i've enabled the option to run it in it's own address space. Unfortunately that also means that recording/prerecording no longer works and i have to restart the game and AB + RTSS too.

But for some reason the crash always lists a specific C++ module as fault.
So the question is should i instead use the included C++ runtime (Microsoft Visual C++ 2008 v9.0.30729.5677) for maximum compatability or is it not important?
I use a newer 9.0.30729.7523 version ( http://www.wincert.net/forum/topic/9790-aio-microsoft-visual-bcfj-redistributable-x86x64/ ).

Here's an example from Event Viewer:

Code:

Log Name:      Application
Source:        Application Error
Date:          9.01.2014 2:19:28
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      PHOENIX
Description:
Faulting application name: EncoderServer.exe, version: 2.0.0.0, time stamp: 0x52ac1c1f
Faulting module name: MSVCR90.dll, version: 9.0.30729.7523, time stamp: 0x516f7f0f
Exception code: 0xc0000005
Fault offset: 0x00025e54
Faulting process id: 0x5a8
Faulting application start time: 0x01cf0ca1fd556df1
Faulting application path: C:\Program Files (x86)\RivaTuner Statistics Server\EncoderServer.exe
Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.7523_none_508f21ccbcbbb7a8\MSVCR90.dll
Report Id: b35dba19-78c3-11e3-9108-00c0df0d75fd
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-01-09T00:19:28.000000000Z" />
    <EventRecordID>2624</EventRecordID>
    <Channel>Application</Channel>
    <Computer>PHOENIX</Computer>
    <Security />
  </System>
  <EventData>
    <Data>EncoderServer.exe</Data>
    <Data>2.0.0.0</Data>
    <Data>52ac1c1f</Data>
    <Data>MSVCR90.dll</Data>
    <Data>9.0.30729.7523</Data>
    <Data>516f7f0f</Data>
    <Data>c0000005</Data>
    <Data>00025e54</Data>
    <Data>5a8</Data>
    <Data>01cf0ca1fd556df1</Data>
    <Data>C:\Program Files (x86)\RivaTuner Statistics Server\EncoderServer.exe</Data>
    <Data>C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.7523_none_508f21ccbcbbb7a8\MSVCR90.dll</Data>
    <Data>b35dba19-78c3-11e3-9108-00c0df0d75fd</Data>
  </EventData>
</Event>

Windows 7 Ultimate SP1 x64 (fully updated)
AMD Catalyst 13.12 WHQL
MSI Afterburner 3.0.0.2269 Beta 18
Rivatuner Statistics Server 6.0.0.6228

 

Hmm it is odd. The destination disk is Western Digital RED 3TB with over 1,5TB free space. I'll keep this topic bookmarked in case i figure out the culprit.

The crashes are happening after hours of gaming. Some other programs that are running in the background during gaming are:
HWiNFO64
RadeonPro
Origin

I will have to test without them to rule out possible interference.

EDIT: Ok bad news and good news.

Good news is that the problem is problably not with OS itself. Meaning it's not broken.
Bad news is that it's got something to do with MSI Afterburner settings ( C:\Program Files (x86)\MSI Afterburner\Profiles\MSIAfterburner.cfg ).
So this means i have a lot of testing to do to find the source of the problem.

I renamed the original CFG file with .bak extension and let afterburner create a new one. Then i played for a while with default settings (i only set prerecord and video capture hotkeys to get prerecording to work). No crashes. With old settings it would have crashed several times by now.

So now i reconfigured everything exept prerecording tab like i used to have. Time to test again. If successful (no crashes) then i can safely assume the problem is with a specific setting in the prerecord tab. Atleast that's the theory at the moment.

This month has been funny. Chasing obscure faulty settings (that apparently only i have problems with) in various apps (VLC, national ID card and so on). But so far i have found all of them and im confindent i will find this one too.

 

Update: Issue is likely solved now. Apparently theres a conflict between AB and Windows settings. AB records 16bit @ 48kHz but my windows was set to 24bit @ 192kHz and this caused encoderserver crash after 60> minutes. Setting windows back to default 16bit @ 44kHz or 16bit @ 48kHz fixes the problem.

So be advised when changing your windows audio quality settings!

 

I'm having the same issue. Encoderserver64 crashes right after I start recording. I've tried changing the audio settings on windows as described in the previous message with no effect.

Only "fix" I could find for this was to change the encoding codec to something else than x264wfv.

Win10
MSI R9 390
i5-4670K
Asus Z87-A

All drivers and software updated to the latest non-beta versions.

 

Try and delete all RTSS and AB settings and re-create your configuration. Lately it hasnt happened but in the past after upgrading to a new AB version i've had to do it when something was not working properly or crashed.