NTFS ERROR ”137” Topic is solved

FAQ, getting help, user experience about Primo Ramdisk
User avatar
Support
Support Team
Support Team
Posts: 3627
Joined: Sun Dec 21, 2008 2:42 am

Re: NTFS ERROR ”137”

Post by Support »

Can you tell which volume get NTFS error? Is this NTFS error happens on ramdisk volume?

BTW, since your ramdisk only stores temp files, is it necessary to use an image file?
curioususer
Level 1
Level 1
Posts: 2
Joined: Fri Aug 09, 2013 3:58 pm

Re: NTFS ERROR ”137”

Post by curioususer »

Thank you so much for following up, support! :)

It is the ramdisk volume that gets the error, and I didn't have an image file associated originally, but after reading the FAQs on your site, and since I was going to set the SysTemp and UserTemp folders on the drive, I decided to have it associated with an image.

But here's the awesome news: after not changing ANYTHING I have not received the error the past 2 restarts. I received it the ENTIRE WEEK, but not since I posted my message, so maybe I scared the app into submission, but I will definitely keep you posted!

Thanks again!
User avatar
Support
Support Team
Support Team
Posts: 3627
Joined: Sun Dec 21, 2008 2:42 am

Re: NTFS ERROR ”137”

Post by Support »

a little strange... I'm thinking it may be a corruption of the image file. Anyway, just let us know if you find any problems.
Thank you.
sandok
Level 1
Level 1
Posts: 1
Joined: Sat Jan 11, 2014 12:15 pm

Re: NTFS ERROR ”137”

Post by sandok »

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?
Post Reply