Realtek HD Audio Driver Revision History – Windows 8.1 x86/x64 and Windows 10 x86/x64
220.127.116.1168 – 28/03/2019
18.104.22.16870 – 19/06/2018
22.214.171.12425 – 17/04/2018
126.96.36.19963 – 30/01/2018
188.8.131.5202 – 14/11/2017
R2.82 – 184.108.40.20686 –
R2.81 – 220.127.116.1136 –
R2.80 – 18.104.22.16804 –
????? – 22.214.171.12410 – 16/08/2016
????? – 126.96.36.19948 – 30/06/2015
R2.79 – 188.8.131.5241 –
R2.78 – 184.108.40.20612 –
R2.77 – 220.127.116.1103 –
Having recently purchased a Samsung SM961 PCIe MVMe SSD I was shocked to find that my write speeds were only 350MB/s. I have the SM961 installed in a Lycom DT-129 PCIe card but I only have a x4 PCIe 2.0 slot on my current motherboard. When I purchased the SM961 I was aware that my speeds would be impacted by the PCIe 2.0 slot but did not anticipate such poor Write speeds. With it being an OEM product the SM961 also has no drivers supplied and at the time of writing this article Samsung and no other PC manufacturers appear to have posted optimised drivers. I was aware that Windows 10 provides native NVMe driver support and expected reasonable performance from them.
Unhappy with the Write speeds I started to experiment and eventually found that if I disable windows write cache buffer flush in Device Manager then my Write speeds jump to just over 800MB/s which I can happily live with.
Here are my findings:
The default setting is for Write caching to be enabled and write-cache buffer flushing to be enabled
I tested with write caching and write cache buffer flushing disabled
I then tested with write caching enabled and write-cache buffer flushing disabled.
I would be interested to hear for you so please do post your feedback or questions.
Disclaimer: Please ensure that you have and maintain a full backup of all your data before making any changes to your system. These changes may make your system more susceptible to data loss should a power failure occur whilst your system is in operation.
3CX Version 14 Service Pack 3 seems to include/use very old and insecure versions of OpenSSL 1.0.1e (11th February 2013) and 1.0.1g (5th June 2014).
More info about the locations is below:
C:\Program Files\3CX Phone System\Instance1\Bin\libeay32.dll
C:\Program Files\3CX Phone System\Instance1\Bin\ssleay32.dll
1.0.1g (5 Jun 2014)
1.0.1e (11 Feb 2013)
OpenSSL 1.0.1t is the latest release and resolves a number of serious vulnerabilities
This means that 3CX V14 Service Pack 3 is likely to be vulnerable to all of the documented vulnerabilities prior to the 1.0.1t OpenSSL release. Using an IPS firewall may help to reduce the risk to your system until an updated version of OpenSSL is integrated into 3CX.
RC4 cipher suite is still enabled in Abyss Web Server X2 (Version 18.104.22.168) that is supplied with 3CX Version 14 Service Pack 3.
Version 2.11 of Abyss Web server X2 that was released on 5th April 2016 disabled the obsolete RC4 cipher suite as per RFC7465.
Abyss Web Server X2 in 3CX Version 14 Service Pack 3 also negotiates TLS_RSA_WITH_DES_CBC_SHA which is only a 56-bit key and is considered insecure.
3CX support have provided a workaround for this
You may edit the ciphers configured in Abyss by doing the following:
– change Ciphers dropdown to “Custom Ciphers Specification”
– replace RC4-SHA:HIGH:MEDIUM:LOW:DEFAULT:-EXP:!SSLv2:!ADH:!aNULL:!eNULL:!NULL
– validate, clicking OK on each screen until you are back to the webserver homepage then click Restart button.