Update to 4.3.0.13 Broke

[n8xja]

Is anyone else experiencing this crashing after installing the update to 4.3.0.13?
After the update, BI would crash. So I backed up the config, uninstalled, rebooted, installed fresh full copy of 4.3.0.13, crash behavior continued.

I sent the XML of the event viewer output of the crash to support and its included below.

After uninstalling again, I installed an archived copy of 4.2.2.x - full install and BI runs without the crash behavior.

I'd like to find a full install of 4.3.0.0 to 4.3.0.10.

Any pointers to download an older version that's not on the BI site?

Thanks

- <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="2016-03-25T12:58:06.848500400Z" />

<EventRecordID>3639</EventRecordID>

<Channel>Application</Channel>

<Computer>WIN-SCBTKM862PA</Computer>

<Security />

</System>


- <EventData>
<Data>BlueIris.exe</Data>

<Data>4.3.0.13</Data>

<Data>56f16e3e</Data>

<Data>MSVCR120.dll</Data>

<Data>12.0.21005.1</Data>

<Data>524f83ff</Data>

<Data>c0000409</Data>

<Data>0000000000074a30</Data>

<Data>1700</Data>

<Data>01d18695f7295689</Data>

<Data>C:\Program Files\Blue Iris 4\BlueIris.exe</Data>

<Data>C:\Program Files\Blue Iris 4\MSVCR120.dll</Data>

<Data>ce6a86d7-91e2-4eab-85db-8ed3e719b61c</Data>

<Data />

<Data />

</EventData>


</Event>

 

[josalamanca007]

My intention is not to high jack this thread, but I am also looking for full install of 4.3.0.0 or prior update to 4.3.0.12.

Brief issue I am experiencing after installing 4.3.0.12:
Cameras will stop responding ("No Signal" screen). Nothing has changed besides updating to the latest build.

 

[bp2008]

This 4.3.0.9 is stable for me. This is the 64 bit update file: https://dl.dropboxusercontent.com/u/72769267/Blue Iris/update64_4.3.0.9.exe

 

[josalamanca007]

This 4.3.0.9 is stable for me. This is the 64 bit update file: https://dl.dropboxusercontent.com/u/72769267/Blue Iris/update64_4.3.0.9.exe

Thanks, I'll give it a try.

 

[Zorac]

i have the full version of 4.3.0.3 if your still looking for a full version.

 

[Zorac]

i have the full version of 4.3.0.3 if your still looking for a full version.

 

[beepsilver]

Here's 4.3.0.12 and I'll keep it available for a few days: https://dl.dropboxusercontent.com/u/17674025/Version 4.3.0.12 (March 21, 2016).exe

And here's 4.3.0.10, also available for a few days: https://dl.dropboxusercontent.com/u/17674025/Version 4.3.0.10 (March 14, 2016).exe

EDIT, I apparently can't read--these are updates only...sorry about that.

 

[Zorac]

full version of 4.3.0.3
https://mega.nz/#!FZcVWDrQ!cjc1IOqwQ1NZV0QQEJVbRYuOtlpFmwDgDEtgKVwBUJA

 

[n8xja]

Thank you everyone for offering downloads of older versions. I'm back up and running.

 

[n8xja]

Thought I would give an update.

The update alone doesn't break BI. There was something in the config. Here's how I figured that out:

Fresh install 4.2.x.x -> Install lic. key -> restore backup config -> update to 4.3.0.3 = broke on the update (use a full package install)
Fresh install 4.3.0.3 -> Start BI - Its good -> Update 4.3.0.13 -> Start BI -Its good -> Apply License Key - Rejects key (too many activation) -> Restore Config -> Good BI install but in demo mode.

So I think the combo of something in the config and the update caused the exception.

Now waiting on support to fix my key (know now not to activate while testing).

Thanks.

 

[josalamanca007]

Not so sure I can say that an update alone does not break BI.

After reverting from 4.3.0.13 to 4.3.0.9, I have not had a single "No Signal" camera in about 10 hours.

I am now archiving updates, will probably archive full versions.

Thanks everyone for being so quick to help fellow BI users.

 

[n8xja]

Latest Update - and Possible Solution

My BI install on Windows 10 runs in VMware, not directly on a physical host. I noticed today while troubleshooting that BI hangs with the MSVCR120.dll error that I opened this thread with when the storage is full, which is the cause to the problem I was experiencing. The drive is normally 99% full most of the time, but seem to be possible to configure BI to fill the drive and cause a crash. This was not entirely obvious to me before, but it is now. Cleaning off some space and tweaking the retention settings, presto - BI starts and runs without issues.