Windows 10: NTFS event ID 138 help?

Hello So on my 8.1 laptop I had got this error 20 mins after I woke it up from sleep.

The transaction resource manager at C:\ encountered a fatal error and was shut down. The data contains the error code.

Here is the C log.

I know its a 10 forum, but the 8 forum is kinda slow.

Code: 2017-10-14 18:26:56, Info CSI 0000000b Scavenge: Begin processing lists 2017-10-14 18:26:56, Info CSI 0000000c Scavenge: Begin planning 2017-10-14 18:27:00, Info CSI 0000000d Scavenge: Planning Complete. The following actions will be performed: Regeneration Candidates: 0 Removal Candidates: 0 Superseded/LDR (Delta Compression) Candidates: 136 NTFS Compression Candidates: 0 Null-Delta Compression Candidates: Mutable file Candidates: 6 Boot-Recovery Candidates: 29 Deletion Candidates (Non Driver): 0 Driver Deletion Candidates: 0 2017-10-14 18:27:02, Info CSI 0000000e Beginning Delta compression of LDR / Superseded Components 2017-10-14 18:27:02, Info CSI 0000000f Creating NT transaction (seq 2), objectname [6]"(null)" 2017-10-14 18:27:02, Info CSI 00000010 Created NT transaction (seq 2) result 0x00000000, handle @0x5d4 2017-10-14 18:27:02, Info CSI 00000011@2017/10/14:22:27:02.816 Beginning NT transaction commit... 2017-10-14 18:27:03, Info CSI 00000012@2017/10/14:22:27:03.175 CSI perf trace: CSIPERF:TXCOMMIT;416548 2017-10-14 18:27:03, Info CSI 00000013 Creating NT transaction (seq 3), objectname [6]"(null)" 2017-10-14 18:27:03, Info CSI 00000014 Created NT transaction (seq 3) result 0x00000000, handle @0x5d4 2017-10-14 18:27:03, Info CSI 00000015@2017/10/14:22:27:03.253 Beginning NT transaction commit... 2017-10-14 18:27:03, Info CSI 00000016@2017/10/14:22:27:03.519 CSI perf trace: CSIPERF:TXCOMMIT;309846 2017-10-14 18:27:03, Info CSI 00000017 Creating NT transaction (seq 4), objectname [6]"(null)" 2017-10-14 18:27:03, Info CSI 00000018 Created NT transaction (seq 4) result 0x00000000, handle @0x45c 2017-10-14 18:27:03, Info CSI 00000019@2017/10/14:22:27:03.644 Beginning NT transaction commit... 2017-10-14 18:27:03, Info CSI 0000001a@2017/10/14:22:27:03.831 CSI perf trace: CSIPERF:TXCOMMIT;219703 2017-10-14 18:27:03, Info CSI 0000001b Creating NT transaction (seq 5), objectname [6]"(null)" 2017-10-14 18:27:03, Info CSI 0000001c Created NT transaction (seq 5) result 0x00000000, handle @0x518 2017-10-14 18:27:03, Info CSI 0000001d@2017/10/14:22:27:03.972 Beginning NT transaction commit... 2017-10-14 18:27:04, Info CSI 0000001e@2017/10/14:22:27:04.394 CSI perf trace: CSIPERF:TXCOMMIT;481038 2017-10-14 18:27:04, Info CSI 0000001f Creating NT transaction (seq 6), objectname [6]"(null)" 2017-10-14 18:27:04, Info CSI 00000020 Created NT transaction (seq 6) result 0x00000000, handle @0x5a4 2017-10-14 18:27:04, Info CSI 00000021@2017/10/14:22:27:04.644 Beginning NT transaction commit... 2017-10-14 18:27:04, Info CSI 00000022@2017/10/14:22:27:04.909 CSI perf trace: CSIPERF:TXCOMMIT;296885 2017-10-14 18:27:05, Info CSI 00000023 Creating NT transaction (seq 7), objectname [6]"(null)" 2017-10-14 18:27:05, Info CSI 00000024 Created NT transaction (seq 7) result 0x00000000, handle @0x5a4 2017-10-14 18:27:05, Info CSI 00000025@2017/10/14:22:27:05.034 Beginning NT transaction commit... 2017-10-14 18:27:05, Info CSI 00000026@2017/10/14:22:27:05.425 CSI perf trace: CSIPERF:TXCOMMIT;443133 2017-10-14 18:27:06, Info CSI 00000027 Creating NT transaction (seq 8), objectname [6]"(null)" 2017-10-14 18:27:06, Info CSI 00000028 Created NT transaction (seq 8) result 0x00000000, handle @0x5c0 2017-10-14 18:27:07, Info CSI 00000029@2017/10/14:22:27:07.103 Beginning NT transaction commit... 2017-10-14 18:27:08, Info CSI 0000002a@2017/10/14:22:27:08.784 CSI perf trace: CSIPERF:TXCOMMIT;1965661 2017-10-14 18:27:10, Info CSI 0000002b Creating NT transaction (seq 9), objectname [6]"(null)" 2017-10-14 18:27:10, Info CSI 0000002c Created NT transaction (seq 9) result 0x00000000, handle @0x5a4 2017-10-14 18:27:11, Info CSI 0000002d@2017/10/14:22:27:11.366 Beginning NT transaction commit... 2017-10-14 18:27:11, Info CSI 0000002e@2017/10/14:22:27:11.947 CSI perf trace: CSIPERF:TXCOMMIT;678617 2017-10-14 18:27:14, Info CSI 0000002f Creating NT transaction (seq 10), objectname [6]"(null)" 2017-10-14 18:27:14, Info CSI 00000030 Created NT transaction (seq 10) result 0x00000000, handle @0x5b0 2017-10-14 18:27:15, Info CSI 00000031@2017/10/14:22:27:15.528 Beginning NT transaction commit... 2017-10-14 18:27:16, Info CSI 00000032@2017/10/14:22:27:16.209 CSI perf trace: CSIPERF:TXCOMMIT;793726 2017-10-14 18:27:19, Info CSI 00000033 Creating NT transaction (seq 11), objectname [6]"(null)" 2017-10-14 18:27:19, Info CSI 00000034 Created NT transaction (seq 11) result 0x00000000, handle @0x5b0 2017-10-14 18:27:21, Info CSI 00000035 Sharing violation encountered during generating Delta for: [l:174{87}]"amd64_microsoft-windows-smbserver_31bf3856ad364e35_6.3.9600.18790_none_e9a451f7bede6278", file: [l:20{10}]"sscore.dll", this is likely a hardlink to the winning version, skip for now 2017-10-14 18:27:21, Info CSI 00000036@2017/10/14:22:27:21.627 Beginning NT transaction commit... 2017-10-14 18:27:23, Info CSI 00000037@2017/10/14:22:27:23.112 CSI perf trace: CSIPERF:TXCOMMIT;1728298 2017-10-14 18:27:26, Info CSI 00000038 Creating NT transaction (seq 12), objectname [6]"(null)" 2017-10-14 18:27:26, Info CSI 00000039 Created NT transaction (seq 12) result 0x00000000, handle @0x5bc 2017-10-14 18:27:27, Info CSI 0000003a@2017/10/14:22:27:27.666 Beginning NT transaction commit... 2017-10-14 18:27:28, Info CSI 0000003b@2017/10/14:22:27:28.300 CSI perf trace: CSIPERF:TXCOMMIT;735703 2017-10-14 18:27:31, Info CSI 0000003c Creating NT transaction (seq 13), objectname [6]"(null)" 2017-10-14 18:27:31, Info CSI 0000003d Created NT transaction (seq 13) result 0x00000000, handle @0x5c4 2017-10-14 18:27:37, Error CSI 0000003e (F) STATUS_TRANSACTION_NOT_ACTIVE #2527109# from Windows::Rtl::SystemImplementation:irectRegistryProvider::SysQueryValueKey(flags = 3, key = 5b4 ("\REGISTRY\MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-t..platform-input-core_31bf3856ad364e35_6.3.9600.17415_none_c21b475fb08b58fa"), vn = [ml:88{44},l:24{12}]"f!tabsvc.dll", kvic = 2, kvi = 2, disp = 0)[gle=0xd0190003] 2017-10-14 18:27:37, Error CSI 0000003f@2017/10/14:22:27:37.447 (F) base\wcp\sil\merged\ntu\ntsystem.cpp(4295): Error STATUS_TRANSACTION_NOT_ACTIVE originated in function Windows::Rtl::SystemImplementation:irectRegistryProvider::SysQueryValueKey expression: (null) [gle=0x80004005] 2017-10-14 18:27:39, Info CBS Added C:\Windows\Logs\CBS\CBS.log to WER report. 2017-10-14 18:27:39, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20171011220052.cab to WER report. 2017-10-14 18:27:39, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20171011192129.cab to WER report. 2017-10-14 18:27:40, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20171011025033.cab to WER report. 2017-10-14 18:27:40, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20170929012650.cab to WER report. 2017-10-14 18:27:40, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20170916230359.cab to WER report. 2017-10-14 18:27:41, Info CBS Not able to add current session file to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND] 2017-10-14 18:27:41, Info CBS Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND] 2017-10-14 18:27:41, Info CBS Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND] 2017-10-14 18:27:43, Info CBS Succesfully flushed NtfsLog.etl 2017-10-14 18:27:52, Error CSI 00000040 (F) STATUS_TRANSACTION_NOT_ACTIVE #2527108# from Windows::Rtl::SystemImplementation::CKey::QueryValue(flags = 3, kn = [l:306{153}]"\Registry\Machine\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-t..platform-input-core_31bf3856ad364e35_6.3.9600.17415_none_c21b475fb08b58fa", vn = [ml:88{44},l:24{12}]"f!tabsvc.dll", ic = KeyValuePartialInformation (2), info = {l:0 b:}, disp = 0)[gle=0xd0190003] 2017-10-14 18:27:52, Error CSI 00000041 (F) STATUS_TRANSACTION_NOT_ACTIVE #311# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 0[gle=0xd0190003] 2017-10-14 18:27:52, Error CSI 00000042 (F) HRESULT_FROM_WIN32(6701) #243# from Windows::COM::CComponentStore::InternalTransact(...)[gle=0x80071a2d] 2017-10-14 18:27:52, Error CSI 00000043 (F) HRESULT_FROM_WIN32(6701) #241# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_Commit(Flags = 22 (0x00000016), pSink = NULL, disp = 0, coldpatching = FALSE)[gle=0x80071a2d] 2017-10-14 18:27:52, Error CSI 00000044 (F) HRESULT_FROM_WIN32(6701) #240# 67825549 us from Windows::ServicingAPI::CCSITransaction_ICSITransaction::Commit(flags = 0x00000016, pSink = NULL, disp = 0) [gle=0x80071a2d] 2017-10-14 18:27:52, Info CBS Scavenge: Failed to commit scavenging of CSI store. [HRESULT = 0x80071a2d - ERROR_TRANSACTION_NOT_ACTIVE] 2017-10-14 18:27:52, Info CSI 00000045@2017/10/14:22:27:52.601 CSI Transaction @0xc6538fd030 destroyed 2017-10-14 18:27:52, Info CBS Warning: Failed to scavenge CSI store. [HRESULT = 0x80071a2d - ERROR_TRANSACTION_NOT_ACTIVE] 2017-10-14 18:27:52, Info CBS Failed maintenance scavenge [HRESULT = 0x80071a2d - ERROR_TRANSACTION_NOT_ACTIVE] 2017-10-14 18:27:52, Info CBS Maint: end scavenge, scavenge time so far: 58 seconds 2017-10-14 18:27:52, Info CBS Maint: TransientManifestCache disabled in config. 2017-10-14 18:27:52, Info CBS Maint: incomplete, interruptions: 1, (this pass: time: 58 seconds, used space change: 68432 KB, hr: 0x80071a2d, source: Scavenge) 2017-10-14 18:27:52, Info CBS Reboot mark cleared 2017-10-14 18:27:52, Info CBS Winlogon: Deregistering for CreateSession notifications 2017-10-14 18:27:52, Info CBS Winlogon: Stopping notify server 2017-10-14 18:27:52, Info CBS Winlogon: Unloading SysNotify DLL 2017-10-14 18:27:52, Info CBS Maint: processing complete. Session: 30623035_2307924391. [HRESULT = 0x80071a2d - ERROR_TRANSACTION_NOT_ACTIVE] 2017-10-14 18:27:52, Info CBS Failed performing maintenance task [HRESULT = 0x80071a2d - ERROR_TRANSACTION_NOT_ACTIVE] 2017-10-14 18:27:52, Info CBS Warning: Failed while executing service idle processing. [HRESULT = 0x80071a2d - ERROR_TRANSACTION_NOT_ACTIVE] 2017-10-14 18:27:52, Info CBS Failed to run idle scavenge [HRESULT = 0x80071a2d - ERROR_TRANSACTION_NOT_ACTIVE] 2017-10-14 18:27:52, Info CBS Warning: Failed to execute idle scavenge start. Error code: 0X80071a2d [HRESULT = 0x80071a2d] 2017-10-14 18:27:52, Info CBS Signalling IdleScavenge Complete.[/quote]

:)

 

System Crashes and Instability following power-loss (via reset button) while in sleep-mode

auggy,

I have placed both files in the same OneDrive location: MiniDump

A few interesting events as I scrolled through in the event viewer:

Date: 5/13/2017 9:55:51AM

Source: Disk

Event ID: 7

Description: "The device, \Device\Harddisk1\DR1, has a bad block."

(There are over 300 of these events in a very short period of time!)

Date: 5/12/2017 8:11:38PM

Source: Ntfs (Ntfs)

Event ID: 55

Description: "A corruption was discovered in the file system structure on volume C:.

A corruption was found in a file system index structure. The file reference number is 0x9000000000009. The name of the file is "<unable to determine file name>". The corrupted index attribute is ":$SII:$INDEX_ALLOCATION"."

Once again, this all seems to stem from the computer being reset (by a physical switch on the case) while the computer was asleep. Thanks for your help.

 

Event IDs 55 and 98 request chkdsk /F but \Device\HarddiskVolume# does not exist when doing diskpart => list volume

Very recently (November 7, 2017 and November 13) has issued a notification and event logs that *SEEM* to indicate a problem.

The sequence is:

(Event ID 98): Volume D: (\Device\HarddiskVolume6) needs to be taken offline to perform a Full Chkdsk. Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.

(Event ID 55)

A corruption was discovered in the file system structure on volume D:.

The exact nature of the corruption is unknown. The file system structures need to be scanned and fixed offline.

(Repeat of Event ID 98 ).

In the first of the two cases, I also immediately (2 seconds later) got Event ID 130, which indicated it has been repaired, even though I had NOT run CHKDSK at that point.

The thing is, the Volume it identifies as being associated with drive D: DOES NOT EXIST:

------------------------------------------------------

C:\WINDOWS\system32>diskpart

Microsoft DiskPart version 10.0.15063.0

Copyright (C) Microsoft Corporation.

On computer: JAYW7

DISKPART> list volume

Volume ### Ltr Label Fs Type Size Status Info

---------- --- ----------- ----- ---------- ------- --------- --------

Volume 0 I DVD-ROM 0 B No Media

Volume 1 Z STORAGE NTFS Partition 3725 GB Healthy

Volume 2 System Rese NTFS Partition 100 MB Healthy System

Volume 3 C NTFS Partition 222 GB Healthy Boot

Volume 4 NTFS Partition 858 MB Healthy Hidden

Volume 5 D RAID-D NTFS Partition 924 GB Healthy

DISKPART>

-------------------------------------------------------------

The only thing I can think of is that "D:" is mapped to a Intel ICH10R RAID array, and that somehow it is getting confused at times, and trying to access a physical drive directly for some reason.

(Volume 1 , Z: is one physical drive. Volumes 2, 3 and 4 are a second physical drive, and Volume 5 is the RAID array)

After the first one, I did run a CHKDSK /F, and it ran the check and there did not seem to be any errors.

 

You need to paste it as a file, not the whole error, but that is fine. If it is a BSOD, you can use WhoCrashed to show you the problem. There is also online sites that can help you. The problems in 8 are very close to 10. OSR has a online dmp log analyzer. This tells you how to read the dmp log. https://support.microsoft.com/en-us/...y-windows-if-a

 

Oh I didn't get any bsod or anything like that.

 

The original dump log in a zip file needs to be posted, not the output.