Tag Archives: Cache

Mrxsmb20.sys – Pre Service Pack 2 Revision History for Windows Server 2008 R2 SP1, Windows 7 SP1 and Windows Small Business Server 2011 (SBS 2011)

Mrxsmb20.sys – Pre Service Pack 2 Revision History for Windows Server 2008 R2 SP1, Windows 7 SP1 and Windows Small Business Server 2011 (SBS 2011)

09-Apr-2015 – 6.1.7601.23031 – Mrxsmb20.sys – x86/x64 – https://support.microsoft.com/en-us/kb/3054251 – Stop Error in Rdbss.sys and unsaved documents in Windows 7 SP1 or Windows Server 2008 R2 SP1

25-Sep-2014 – 6.1.7601.22819 – Mrxsmb20.sys – x86/x64 – http://support.microsoft.com/kb/3002297 – The SMB Redirector may hang when the SMB protocol is used in Windows 7 SP1 or Windows 8.1

25-Sep-2014 – 6.1.7601.22819 – Mrxsmb20.sys – x86/x64 – https://support.microsoft.com/en-us/kb/3002286 – Delay in accessing a file server when a Windows 7-based computer connects to the file server

25-Jan-2013 – 6.1.7601.22231 – Mrxsmb20.sys – x86/x64 – http://support.microsoft.com/kb/2807716 – Error message when you try to map a drive to a network share in Windows 7 or Windows Server 2008 R2

01-Nov-2012 – 6.1.7601.22149 – Mrxsmb20.sys – x86/x64 – http://support.microsoft.com/kb/2778834 – File becomes corrupted when you try to overwrite the file while it is opened by another user on a computer that is running Windows 7 or Windows Server 2008 R2

01-Nov-2012 – 6.1.7601.17988 – Mrxsmb20.sys – x86/x64 – http://support.microsoft.com/kb/2778834 – File becomes corrupted when you try to overwrite the file while it is opened by another user on a computer that is running Windows 7 or Windows Server 2008 R2

12-Oct-2012 – 6.1.7601.22133 – Mrxsmb20.sys – x86/x64 – http://support.microsoft.com/kb/2769790 – File that a user adds to a remote folder is not displayed in Windows Explorer on a computer that is running Windows 7 or Windows Server 2008 R2

09-Oct-2012 – 6.1.7601.22130 – Mrxsmb20.sys – x86/x64 – http://support.microsoft.com/kb/2739674 – You cannot connect to remote computers by using the SMB protocol on a computer that is running Windows 7 or Windows Server 2008 R2

09-Oct-2012 – 6.1.7601.17970 – Mrxsmb20.sys – x86/x64 – http://support.microsoft.com/kb/2739674 – You cannot connect to remote computers by using the SMB protocol on a computer that is running Windows 7 or Windows Server 2008 R2

04-Apr-2012 – 6.1.7601.21957 – Mrxsmb20.sys – x86/x64 – http://support.microsoft.com/kb/2559767 – File corruption occurs when you perform file operations on a file server that is running Windows 7 or Windows Server 2008 R2

24-Nov-2011 – 6.1.7601.21866 – Mrxsmb20.sys – x86/x64 – http://support.microsoft.com/kb/2646563 – SMB2 directory cache is not updated correctly if a file is deleted in Windows 7 or in Windows Server 2008 R2

22-Nov-2011 – 6.1.7601.21864 – Mrxsmb20.sys – x86/x64 – http://support.microsoft.com/kb/2628582 – “STATUS_OBJECT_NAME_NOT_FOUND” error message when you open a newly-created file in a shared folder in Windows 7 or in Windows Server 2008 R2

17-Sep-2011 – 6.1.7601.21822 – Mrxsmb20.sys – x86/x64 – http://support.microsoft.com/kb/2618096 – Data corruption when one user on a computer that is running Windows 7 or Windows Server 2008 R2 updates a shared file that is open on multiple computers by using SMB Version 2

15-Sep-2011 – 6.1.7601.21819 – Mrxsmb20.sys – x86/x64 – http://support.microsoft.com/kb/2612966 – Paged pool memory leak when you access some shared files in Windows 7 or in Windows Server 2008 R2

15-Jul-2011 – 6.1.7601.21771 – Mrxsmb20.sys – x86/x64 – http://support.microsoft.com/kb/2550581 – When you try to access files on a network share, Windows Explorer stops responding on a computer that is running Windows 7, Windows Server 2008 R2, Windows Vista or Windows Server 2008

27-Apr-2011 – 6.1.7601.21714 – Mrxsmb20.sys – x86/x64 – http://support.microsoft.com/kb/2536276 – MS11-043: Vulnerability in SMB Client could allow remote code execution: June 14, 2011

23-Feb-2011 – 6.1.7601.21666 – Mrxsmb20.sys – x86/x64 – http://support.microsoft.com/kb/2511455 – MS11-019: Vulnerabilities in SMB Client could allow remote code execution: April 12, 2011

Verify the Health and Operation of your Intel® Processor with the Intel® Processor Diagnostic Tool

A 32 and 64 bit version of the IPDT or Intel Processor Diagnostic Tool can be downloaded from here: http://www.intel.com/support/processors/sb/CS-031726.htm

You can also see a video on how to use it here: http://www.youtube.com/watch?v=tpPOqh_Bq78

You can use the diagnostic tool to test the various features of your Intel Processor and perform a stress test to ensure that it is operating in a  stable manner.

Remote Desktop Sessions Pause Or Exhibit Unresponsiveness – Lag Whilst Typing And Session Will Not Accept Mouse Inputs

Remote Desktop Services can be extremely useful, allowing users to access a terminal server or their company desktop computer from another location.  One very common complaint with RDP sessions is screen refresh delays and a delay when typing or trying to click on items using the mouse cursor.  It will appear to most that the session has become unresponsive for a period of 5-20 seconds, after this delay the session will return to normal for a period of several minutes before once again becoming unresponsive.  You may find that this issue becomes more apparent as more users connect to the specific terminal server in question and if all these users utilise several applications (i.e. Outlook, Word and Excel) together.

Causes for poor user experience when connected via RDP are varied but one of the most common is resource exhaustion or contention.  This in turn causes a delay in processing that appears as a pause or unresponsiveness.

Check that your computer or terminal server has sufficient Memory to cope with the current load.

The next thing to verify by using performance monitor is that the PhysicalDisk\% Idle Time is consistently high, that’s correct this should be 90-100% when the server is not very busy.

It is worth running performance monitor using the PhysicalDisk\% Idle Time counter whilst you are seeing the slowdowns, this will help identify if your hard disk or controller are causing contention and in turn the pausing or unresponsiveness.

If you do find that the “%Idle Time” keeps going very low then it’s time to consider some of the options below to help resolve the issue

  • Install a second drive or mirror set, move the Windows Page File to this second disk/array to reduce the load on the drive/array holding your operating system
  • Install additional memory into the computer or server, this will reduce paging to disk and will generally improve overall system performance
  • Migrate to or upgrade your existing RAID controller to a unit that had a Battery Backed Cache (Fast) or Flash Backed Cache (Newer – Faster) to significantly improve performance and alleviate the system
  • Migrate to faster hard disk drives, 7200, 10,000 or 15,000 RPM drives are amongst the fastest.  The SATA interface is slower than the SAS interface but is cheaper.  Try to invest in the fastest drives that you can to future proof the system and avoid future performance issues if you have to scale for more users.
  • Ensure that you have at least 20-25% free disk space on all partitions/drives
  • Defragment all drives on a regular basis to optimise read and write operations
  • A cheap solution for improving disk performance may be to turn on the Hard Disk Cache using “Device Manager” or in the event that you are using a RAID controller without a battery backed Cache module you will need to open the RAID Array Management Software and then enable Disk Cache within the management software as this feature will not be available within “Device Manager” in this instance.  Please note that this does have some risks and should be used with caution, you may loose data in the event of a sudden/unexpected loss of power to the system.  Consider using this option with a UPS and redundant power supplies to reduce the risk of power loss to the system.  As always ensure you have a reliable backup that is carried out at regular intervals.

Example – HP RAID Array Configuration Utility:

Example – Windows Device Manager: