Ntfs 137 windows 7 - Windowsa.top - ваш верный помощник с OS Windows

So, I was looking through the system event logs of a 2008R2 SP1 server today. And, I found some error 57 several times followed by error 137. This pattern repeated itself every five seconds. The server was experiencing no problems other than this repeating error message. What could it be?

Turns out that this error is documented as appearing in more than 2008R2. Specifically, it can happen with Vista, Windows 7, and with 2008 release candidate one. The underlying cause is a corrupted file, which can be easily reset. To resolve the issue, follow these procedures:

Open a command prompt:
- Login to the machine experiencing the error
- Run the DOS command prompt with administrative privileges
Run a reset command:
- At the DOS prompt: fsutil resource setautoreset true c:\
- Validate that the command completes successfully
- Close the DOS prompt: exit
Reboot the machine:
- From the start menu, run shutdown | restart
  (Note: if this option is not available, you can run in the DOS prompt: shutdown -r)

Once the machine restarts, the error should no longer happen. You can open Control Panel | Administrative Tools | Event Viewer | System to validate that the error is no longer getting logged. Here is a good article for further information:
http://support.microsoft.com/kb/939399

Источник

Forum
Windows Operating Systems
Windows 7
Ntfs event 137

April 29th, 2011, 12:03 PM

#1

I’m getting a lot of those in my event viewer can anybody tell me what may be causing it.
Log Name: System
Source: Ntfs
Date: 4/29/2011 9:17:35 AM
Event ID: 137
Task Category: (2)
Level: Error
Keywords: Classic
User: N/A
Computer: Richard
Description:
The default transaction resource manager on volume C: encountered a non-retryable error and could not start. The data contains the error code.
Event Xml:
<Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
<System>
<Provider Name=»Ntfs» />
<EventID Qualifiers=»49156″>137</EventID>
<Level>2</Level>
<Task>2</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime=»2011-04-29T14:17:35.978806100Z» />
<EventRecordID>32117</EventRecordID>
<Channel>System</Channel>
<Computer>Richard</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>C:</Data>
<Binary>1C0004000200300002000000890004C000000000BB0000C000000000000000000000000000000000BB0000C0</Binary>
</EventData>
</Event>

squid13
April 29th, 2011, 01:45 PM

#2

squid13—What are you doing when this happens? Does this KB have any relationship to what you are doing?
http://support.microsoft.com/default…b;en-us;971905
This is what EventID says:
«The default transaction resource manager on volume <drive letter> encountered a non-retryable error and could not start. The data contains the error code.»
One Google source translates that as: «Unable to start the standard resource handler for transactions on volume C: due to an error.»
Here is a reference that claims to be a fix—at least for Vista. It might work in Win7 also.

Jim
WIN7 Ultimate SP1 64bit, IE 11, NTFS,
cable, MS Security Essentials, Windows 7 firewall
April 29th, 2011, 02:43 PM

#3
April 29th, 2011, 04:33 PM

#4

That KB seems to be for Raid and I’m not using raid. Welshjim where is that reference, you forgot to put it in your response. While I’m at it I have this greyed out driver in plug and play, Fs_Rec and from what I can tell through searches in system 32 I don’t have this system on my computer and from what I’ve read it should be there. If I did a repair with the disk would that install it? Windows 7 64 bit.

Last edited by squid13; April 29th, 2011 at 04:58 PM.

squid13
April 29th, 2011, 06:56 PM

#5

I just checked my wifes computer Windows 7 SP1 and it doesn’t have Fs_Rec sys on it either.

squid13

April 30th, 2011, 06:35 AM

FWIW, here’s a screencap of what I see here on a laptop running Windows 7 Ultimate 64-bit with SP1:

Code:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\>dir fs_rec.sys /a /s

Volume in drive C is Hard Drive
Volume Serial Number is 68D5-8E93

Directory of C:\Windows\System32\drivers

07/13/09  09:47 PM            23,104 fs_rec.sys
               1 File(s)         23,104 bytes

Directory of C:\Windows\winsxs\amd64_microsoft-windows-coreos_31bf3856ad364e35_6.1.7600.16385_none_814737ee58024dde

07/13/09  09:47 PM            23,104 fs_rec.sys
               1 File(s)         23,104 bytes

Directory of C:\Windows\winsxs\amd64_microsoft-windows-coreos_31bf3856ad364e35_6.1.7601.17514_none_83784bb654f0d178

07/13/09  09:47 PM            23,104 fs_rec.sys
               1 File(s)         23,104 bytes

     Total Files Listed:
               3 File(s)         69,312 bytes
               0 Dir(s)  345,121,091,584 bytes free

C:\>

April 30th, 2011, 10:02 AM

#7

Should I have the Fs_Rec system on these computers cause as far as I can tell it’s not there. How did you go about getting that read out?

squid13
April 30th, 2011, 12:41 PM

#8

squid13—The reference in my last post is the reference from EventID. (Sorry to have mixed up the order in my post.) But you say you do not use RAID.
EventID is EventID.net.

«What are you doing when this (Event Viewer errors) happens?»

Jim
WIN7 Ultimate SP1 64bit, IE 11, NTFS,
cable, MS Security Essentials, Windows 7 firewall
April 30th, 2011, 01:04 PM

#9

Most of the time I’m just surfing through the web reading tech forums trying to get educated or news sites.

squid13
April 30th, 2011, 03:32 PM

#10

Ok, I get this Ntfs problem when I start the computer or do a restart, that’s when it shows. It only does it then.

squid13
April 30th, 2011, 06:07 PM

#11

Originally Posted by squid13

How did you go about getting that read out?

Got to a C:\> prompt and typed:

dir fs_rec.sys /a /s
April 30th, 2011, 08:08 PM

#12

I ran that and it came back OK. The file is in the system 32 driver folder. Thank you for that. My problem is I get that Ntfs event 137 every time I boot or restart and that’s the only time I get it and I can’t figure out what’s causing it.

squid13
May 1st, 2011, 05:10 AM

#13

Originally Posted by squid13

I ran that and it came back OK. The file is in the system 32 driver folder. Thank you for that.

You’re welcome.

Originally Posted by squid13

My problem is I get that Ntfs event 137 every time I boot or restart and that’s the only time I get it and I can’t figure out what’s causing it.

I’m afraid I don’t have a clue. Even did a Google search using EventRecordID 32117 -squid13 and didn’t get squat.
May 1st, 2011, 02:55 PM

#14

squid13—Have you looked in System Configuration Utility (msconfig) to see what is starting at boot? Maybe you will see something you do not need at boot and deleting it will get rid of the message.
Concerning Fs_Rec have you tried to update that driver?

Jim
WIN7 Ultimate SP1 64bit, IE 11, NTFS,
cable, MS Security Essentials, Windows 7 firewall
May 1st, 2011, 03:33 PM

#15

No I haven’t looked in misconfig yet, good idea. As far as the fs_rec is concerned it was grayed out, what ever was using it is not installed anymore so I uninstalled it. The file size in my system 32 is the right size according to this http://www.thefiledb.com/filedatabas…c.sys-id24256/ so I’m not going to worry about it anymore. The computer is running good.

squid13

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
[VIDEO] code is On
HTML code is Off

Forum Rules

Источник

Hakvinius

Hi,
Today, I suddenly found a new error in my log. The event id is 137 and
source is NTFS. A translation of the message would be something like this:

«Unable to start the standard resource handler for transactions on volume C:
due to an error.»

From log:
— <Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
— <System>
<Provider Name=»Ntfs» />
<EventID Qualifiers=»49156″>137</EventID>
<Level>2</Level>
<Task>2</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime=»2007-07-24T07:43:44.301Z» />
<EventRecordID>36340</EventRecordID>
<Channel>System</Channel>
<Computer>More-dator</Computer>
<Security />
</System>
— <EventData>
<Data />
<Data>C:</Data>
<Binary>1C0004000200300002000000890004C000000000300019C000000000000000000000000000000000300019C0</Binary>
</EventData>
</Event>

I tried a chckdsk, but no errors there.

Thanks in advance for any help!

/Hakan

Hakvinius said:

Hi,
Today, I suddenly found a new error in my log. The event id is 137 and
source is NTFS. A translation of the message would be something like this:

«Unable to start the standard resource handler for transactions on volume
C: due to an error.»

From log:
— <Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
— <System>
<Provider Name=»Ntfs» />
<EventID Qualifiers=»49156″>137</EventID>
<Level>2</Level>
<Task>2</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime=»2007-07-24T07:43:44.301Z» />
<EventRecordID>36340</EventRecordID>
<Channel>System</Channel>
<Computer>More-dator</Computer>
<Security />
</System>
— <EventData>
<Data />
<Data>C:</Data>

<Binary>1C0004000200300002000000890004C000000000300019C000000000000000000000000000000000300019C0</Binary>
</EventData>
</Event>

I tried a chckdsk, but no errors there.

Thanks in advance for any help!

/Hakan

After some research, I found the solution here:
http://blogs.vertigo.com/personal/alexark/Blog/Lists/Posts/Post.aspx?ID=5

This error was apparently stopping Windows Update and System Restore.
As this seems to have happened with others before, it’s strange that nothing
can be found on MS KB.

Peter Foldes

External HD ?? This error usually suggests that either the HD has not been formatted properly or it is in a FAT 32 scenario and you are installing NTFS volumes on to it

conte49

Peter Foldes said:

External HD ?? This error usually suggests that either the HD has not been formatted properly or it is in a FAT 32 scenario and you are installing NTFS volumes on to it

—
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

conte49

Peter Foldes said:

External HD ?? This error usually suggests that either the HD has not been formatted properly or it is in a FAT 32 scenario and you are installing NTFS volumes on to it

—
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

After purchase the ext HD was formatted in FAT 32. I used it that way for a short while, until I realized I could not save large files (4 Gb).

At that point I reformatted to NFTS and reloaded the previous files.
From there on, I had problems with infinite time to tead end write.
What can I do now ? Shloud I for example go back to FAT 32 ?
Thank you

Источник

Hallo, I have the same issue also:

Log Name: System
Source: Ntfs
Event ID: 137
Task Category: (2)
Level: Error
Keywords: Classic
Description:
The default transaction resource manager on volume R: encountered a non-retryable error and could not start. The data contains the error code.
Event Xml:
<Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
<System>
<Provider Name=»Ntfs» />
<EventID Qualifiers=»49156″>137</EventID>
<Level>2</Level>
<Task>2</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime=»2014-01-10T19:07:17.911170400Z» />
<EventRecordID>36522</EventRecordID>
<Channel>System</Channel>
<Computer>ANUBIS</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>R:</Data>
<Binary>1C0004000200300002000000890004C000000000EB0200C000000000000000000000000000000000EB0200C0</Binary>
</EventData>
</Event>

My settings are:
Primo:
7168MB (automatically bei Primo Ramdisk Professional 5.6.0), SCSI disk, Drive Letter R:\, DMM Compact, NTFS, default cluster size (4KB), Volume label RAMDISK, associated image file C:\PR-Image-R.vdf (on SSD, new created, saved one time, contains not the paging file), Smart Image, load only
Microsoft:
— Windows memory dumping is OFF
— Windows user rights @default on ramdisk: authenticated users=modify; SYSTEM=full; Admins=full; Users=read&execute; Owner is SYSTEM
— recycle bin and system restore for ramdisk are OFF
System: Windows 7 HP SP1, x64, 16 GB RAM, SSD, HD

The error orrcurs always if the paging file set to the ramdisk and then on every system shutdown.
It appears regardless of whether the following settings are ON or OFF:
Primo:
— disable NTFS indexing service
— create TEMP folder automatically
Microsoft:
— paging file only on ramdisk or second on primary system disk (SSD)
— fixed or dynamic values for paging file size
— enabled or disabled Windows write caching for the ramdisk

Any other ideas to fixing this?

Источник