CHKDSK fails

[JimF]

With Primo Ramdisk 5.7.0, I am not able to run a CHKDSK on my Win7 64-bit machine after a ramdisk is created. I get an error message upon reboot to the effect that autocheck has failed because of some newly-installed software. When I remove the ramdisk volume, the problem goes away and I can run CHKDSK. This is an i7-4771 machine on a Gigabyte Z87 motherboard. I can supply details of the board, firmware, drivers, etc. as needed.

Primo Ramdisk.PNG (52.79 KiB) Viewed 6325 times

[JimF]

Also, when CHKDSK fails, I usually (but not always) get Event ID 137 error report in the Event Viewer:

Log Name: System
Source: Ntfs
Date: 3/11/2017 9:26:54 AM
Event ID: 137
Task Category: (2)
Level: Error
Keywords: Classic
User: N/A
Computer: Jim-PC
Description:
The default transaction resource manager on volume Z: 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="2017-03-11T14:26:54.311609900Z" />
<EventRecordID>53181</EventRecordID>
<Channel>System</Channel>
<Computer>Jim-PC</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>Z:</Data>
<Binary>1C0004000200300002000000890004C000000000220000C000000000000000000000000000000000220000C0</Binary>
</EventData>
</Event>

I have tried the fix given here, but that does not fix the CHKDSK problem, though it may fix the error code for a while:
https://answers.microsoft.com/en-us/win ... bf5?auth=1

[Support]

We did some testing but so far haven't reproduced the problem you reported. I'd like to know if this problem happens frequently and it happened with Primo Ramdisk 5.6? Thanks.

[JimF]

I don't think that it ever happened with Primo Ramdisk 5.6. I would try 5.6 again, but I don't have a copy. Is there a way to download it?

But it happens 100% of the time with 5.7. Fortunately, I am past the frequent crashes (due to bad disks, cables and even video cards), so I don't have to use CHKDSK now. But I am worried that if I do need it to fix a crash, I won't have it available.

By the way, I do have two video cards (GTX 960s) on this machine, which is a bit unusual, but I use them only for distributed computing projects and they are not connected to a monitor. I use the internal Intel graphics adapter to drive the monitor. Otherwise, I don't know what could be happening so early in the boot process that it might cause a problem with CHKDSK. I have a Samsung 850 Pro SSD as the OS drive, and several other SSDs for backup and video storage purposes, but otherwise it is fairly conventional with no other hardware attached except some USB devices (scanner, printer, GPS and Uninterruptible Power Supply).

I think I will try disabling as many applications and services as I can to see if I can isolate some other factor, and will post back in a couple of days if I find it.

[JimF]

I was unable to isolate the cause by disabling applications, services and unplugging USB ports. I even uninstalled my anti-virus. So I will have to uninstall 5.7.0 for now. Thanks for checking, it may not happen again on another installation.

[Support]

Thanks for the information!
Primo Ramdisk Pro v5.6.0 can be downloaded by the following link.
http://www.romexsoftware.com/download/p ... .Setup.zip

[JimF]

I tried 5.6.0, but it has the same problem, and CHKDSK fails. I guess I did not see it before because I never had to use CHKDSK during the time I was using it. But thanks for sending the link to try it.