FAIR USE NOTICE

FAIR USE NOTICE: The information and materials used on this blog, i.e. articles, videos,etc., may contain copyrighted (© ) material the use of which has not always been specifically authorized by the copyright owner. Such material is made available to advance understanding of ecological, political, human rights, economic, democracy, scientific, moral, ethical, and social justice issues, spiritual, religious, etc. It is believed that this constitutes a 'fair use' of any such copyrighted material as provided for in section 107 of the US Copyright Law. In accordance with Title 17 U.S.C. Section 107, this material is distributed without profit to those who have expressed a prior general interest in receiving similar information for research and educational purposes. For more information go to: /http://www.law.cornell.edu/uscode

Sunday, May 16, 2021

Event ID 55 Microsoft info to fix my computer===hotfix


https://support.microsoft.com/en-us/topic/event-id-55-is-logged-in-windows-7-or-windows-server-2008-r2-and-windows-may-crash-cf96a58c-b43a-9b75-b8e1-0a296200ec4f#bkmk_prerequisites




Event ID 55 is logged in Windows 7 or Windows Server 2008 R2 and Windows may crash

Windows Server 2008 R2 Enterprise Windows Server 2008 R2 Datacenter Windows Server 2008 R2 for Itanium-Based Systems Windows Server 2008 R2 Foundation Windows Server 2008 R2 Standard Windows Server 2008 R2 Web Edition Windows 7 Enterprise Windows 7 Home Basic Windows 7 Home Premium Windows 7 Professional Windows 7 Starter Windows 7 Ultimate Less

Symptoms




When both of the following conditions are met, event ID 55 may be logged.

  • You have a file server that is running Windows 7 or Windows Server 2008 R2.

  • The cluster size (also known as the allocation unit size) for an NTFS volume is larger than 4 kilobytes (KB).


Specifically, the following event is logged in the System log: Additionally, because of file system corruption, the server may crash.

Cause

This issue occurs because the BITMAP attribute of the NTFS metafile cannot roll back when an exception is raised after you modify the metafile. When the system tries to extend the BITMAP attribute, there is no transaction in progress, and the attribute snapshots are purged before the system starts to process the exception. In this situation, file corruption may occur, and NTFS event ID 55 may be logged.

Resolution

To resolve this issue, we have released hotfixes for Windows 7 or Windows Server 2008 R2. Check out the prerequisites of the hotfix.

Note This hotfix does not fix the existing file system corruption. Therefore, you have to run the Chkdsk command together with the /f or /r parameter after you apply the hotfix.

For more information about the Chkdsk command, see Chkdsk.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:

http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have Service Pack 1 installed in Windows 7 or Windows Server 2008 R2.

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows 7 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    Version

    Product

    Milestone

    Service branch

    6.1.760 1.18xxx

    Windows 7 and Windows Server 2008 R2

    SP1

    GDR

    6.1.760 1.22xxx

    Windows 7 and Windows Server 2008 R2

    SP1

    LDR

  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows 7 and for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows 7

File name

File version

File size

Date

Time

Platform

Ntfs.sys

6.1.7601.18397

1,212,352

14-Feb-2014

02:08

x86

Ntfs.sys

6.1.7601.22602

1,213,376

13-Feb-2014

02:11

x86

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Ntfs.sys

6.1.7601.18397

1,684,928

14-Feb-2014

02:29

x64

Ntfs.sys

6.1.7601.22602

1,684,416

13-Feb-2014

02:39

x64

For all supported IA-64-based versions of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Ntfs.sys

6.1.7601.18397

3,548,608

14-Feb-2014

01:51

IA-64

Ntfs.sys

6.1.7601.22602

3,554,240

13-Feb-2014

01:53

IA-64


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

Usually, event ID 55 is logged when file system corruption occurs. The file system corruption occurs when one or more of the following issues occur:

  • A disk has bad sectors.

  • I/O requests that are delivered by the file system to the disk subsystem are not completed successfully.

For the issue that is described in this article, event ID 55 is logged because the I/O requests are not completed successfully. When this issue happens, the bitmap information that manages file records proves to be inconsistent. Therefore, the user can’t find the file and folder properties. In this situation, the file index experiences an inconsistency, but in fact there is no file corruption. However, because of the logged event, it may seem like file corruption has occurred.

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7

File property

Value

File name

Update.mum

File version

Not applicable

File size

2,138

Date (UTC)

14-Feb-2014

Time (UTC)

08:32

Platform

Not applicable

File name

X86_3f7cc3a24c30d2e673c340e361b93f2f_31bf3856ad364e35_6.1.7601.18397_none_07dc2437c0fbe8ae.manifest

File version

Not applicable

File size

692

Date (UTC)

14-Feb-2014

Time (UTC)

08:32

Platform

Not applicable

File name

X86_7792928346a8f26cb81f83b3d2312aee_31bf3856ad364e35_6.1.7601.22602_none_53af81e470fbe949.manifest

File version

Not applicable

File size

692

Date (UTC)

14-Feb-2014

Time (UTC)

08:32

Platform

Not applicable

File name

X86_microsoft-windows-ntfs_31bf3856ad364e35_6.1.7601.18397_none_a824fa927b6bfd7e.manifest

File version

Not applicable

File size

14,508

Date (UTC)

14-Feb-2014

Time (UTC)

02:32

Platform

Not applicable

File name

X86_microsoft-windows-ntfs_31bf3856ad364e35_6.1.7601.22602_none_a90ae90394451d6a.manifest

File version

Not applicable

File size

14,508

Date (UTC)

13-Feb-2014

Time (UTC)

02:34

Platform

Not applicable

Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File property

Value

File name

Amd64_4b0c9bce6885d53fda4773c4f7e2554b_31bf3856ad364e35_6.1.7601.22602_none_f6e942c3407435ec.manifest

File version

Not applicable

File size

696

Date (UTC)

14-Feb-2014

Time (UTC)

08:32

Platform

Not applicable

File name

Amd64_78bb574ac84b57e4c2da771e272cbff5_31bf3856ad364e35_6.1.7601.18397_none_3f4c0fe7020b621d.manifest

File version

Not applicable

File size

696

Date (UTC)

14-Feb-2014

Time (UTC)

08:32

Platform

Not applicable

File name

Amd64_microsoft-windows-ntfs_31bf3856ad364e35_6.1.7601.18397_none_0443961633c96eb4.manifest

File version

Not applicable

File size

14,514

Date (UTC)

14-Feb-2014

Time (UTC)

02:52

Platform

Not applicable

File name

Amd64_microsoft-windows-ntfs_31bf3856ad364e35_6.1.7601.22602_none_052984874ca28ea0.manifest

File version

Not applicable

File size

14,514

Date (UTC)

13-Feb-2014

Time (UTC)

03:02

Platform

Not applicable

File name

Update.mum

File version

Not applicable

File size

2,352

Date (UTC)

14-Feb-2014

Time (UTC)

08:32

Platform

Not applicable

Additional files for all supported IA-64-based versions of Windows Server 2008 R2

File property

Value

File name

Ia64_9af650c2bfd2ba56ba7e2055503f7e42_31bf3856ad364e35_6.1.7601.18397_none_73aeec346d7cc839.manifest

File version

Not applicable

File size

694

Date (UTC)

14-Feb-2014

Time (UTC)

08:32

Platform

Not applicable

File name

Ia64_e640176d63db85d7529cff21b9a372f9_31bf3856ad364e35_6.1.7601.22602_none_4a2ff4b6ae2bb687.manifest

File version

Not applicable

File size

694

Date (UTC)

14-Feb-2014

Time (UTC)

08:32

Platform

Not applicable

File name

Ia64_microsoft-windows-ntfs_31bf3856ad364e35_6.1.7601.18397_none_a8269e887b6a067a.manifest

File version

Not applicable

File size

14,511

Date (UTC)

14-Feb-2014

Time (UTC)

02:23

Platform

Not applicable

File name

Ia64_microsoft-windows-ntfs_31bf3856ad364e35_6.1.7601.22602_none_a90c8cf994432666.manifest

File version

Not applicable

File size

14,511

Date (UTC)

13-Feb-2014

Time (UTC)

02:23

Platform

Not applicable

File name

Update.mum

File version

Not applicable

File size

1,447

Date (UTC)

14-Feb-2014

Time (UTC)

08:32

Platform

Not applicable



Posted by at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)