Author Topic: DxTory not recording, FIN error after stopping recording  (Read 2599 times)


  • Noob
  • *
  • Posts: 4
DxTory not recording, FIN error after stopping recording
« on: July 29, 2017, 09:11:25 am »
Hi there,

I've been trying to get DxTory to work for the past while now, but I keep bumping into error codes and problems, and I hope someone can help.

When starting the recording, the recording indicator switches to red, but the RecFPS stays stuck at 0, no video length is being made, and I get a !ENCODE bottleneck warning. When trying to stop the recording, the indicator stays red, I get a FIN error and DxTory will keep recording, will only stop if the game is turned off or through Windows Task manager.

Whenever I try to start a recording

[Target program]
Rainbow 6: Siege, but it happens with all games

[Player of movie]
No video is being created

[Environment information]
Version: 2.0.142
UID: 17b2add2-61c2-4c40-82c1-b29f017b43a1

[Dxtory Files]
InstallPath: D:\Program Files (x86)\ExKode\Dxtory2.0
amd_ags_x86.dll Size: 94,208 bytes Ver:  SHA1: 07e93edac24c58e411430d61a2f7207d8a7bf078
AppNames.txt Size: 1,091 bytes SHA1: 04c76d2a467c788ad74de95a6d693222601eb82b
AudioStreamSplitter.exe Size: 38,432 bytes Ver: SHA1: 5195bb906a508f9e7175f3c9c7d62c6c76f8217c
AudioStreamSplitter_ja.txt Size: 134 bytes SHA1: 489a5264d73a47edcce7c92edb131cf63e5e5709
AVIFix.exe Size: 72,192 bytes Ver: SHA1: 8743067b975002d014008cfb0db363dfb606c375
AVIFix_ja.txt Size: 288 bytes SHA1: 9cab20780686687b84f604c77c73aaae3fd8126d
AVIMux.exe Size: 166,432 bytes Ver: SHA1: 434d85edc5d4bb77c64ca703f9790062cc87a117
AVIMuxCore.dll Size: 199,200 bytes Ver: SHA1: 53661b27f6f6f9f3e8316dca872fd4b01da93e49
AVIMux_ja.txt Size: 1,701 bytes SHA1: fa240715d701f450bb95377aa8517a252329b619
CryptData.pup Size: 84 bytes SHA1: cf9d724807f965d372da4d168bebd78c5258d6ae
Dxtory.exe Size: 609,488 bytes Ver: SHA1: b8525968062ea3fd9ea766e97a8d58b7fdda45ff
Dxtory64.exe Size: 130,112 bytes Ver: SHA1: 4cce60b896a04515767435c7fd29feefed3c1aac
DxtoryCore.dll Size: 8,295,592 bytes Ver: SHA1: 73d5b7794ac8b0e7abbdeaa10b6106d58d2449d2
DxtoryCore64.dll Size: 8,041,168 bytes Ver: SHA1: 452097b57d594095812ba28a999eed94a7bbd364
DxtoryHK.dll Size: 199,888 bytes Ver: SHA1: 3120931ccc52fbbc15c79e3c992dbe99d69f8536
DxtoryHK64.dll Size: 230,608 bytes Ver: SHA1: 59aaa313d46f273c2c89d6e07e67753c720bf432
DxtoryMM.dll Size: 1,125,952 bytes Ver: SHA1: b0b6fcc47b6b3f326de582975b269d57c2dd0594
DxtoryMM64.dll Size: 1,139,776 bytes Ver: SHA1: 4cc91746487d863e2eea7a572c498c7eddf83817
DxtoryVideo.dll Size: 435,408 bytes Ver: SHA1: 1aadce1a111f7ef840057129a673d6075c1f0edf
DxtoryVideo64.dll Size: 480,464 bytes Ver: SHA1: 36bc4cc08f82a5a605a77f2d58fbfcea1699e18e
DxtoryVideo64_Install.bat Size: 57 bytes SHA1: 5c00dcbc4b631932e7920e7e1bf69e1daf8e26fe
DxtoryVideo64_Uninstall.bat Size: 60 bytes SHA1: 97986d6e7a40eceb84609444ed621c6689526c4d
DxtoryVideoSetting.exe Size: 129,568 bytes Ver: SHA1: ee440e846cfeec2acb4a88f81f589e00c34e825e
DxtoryVideoSetting_ja.txt Size: 1,675 bytes SHA1: e532f36bd5ac6255659d240180637484661f0c83
DxtoryVideo_Install.bat Size: 55 bytes SHA1: 8494f535a15ea10b2d5e0fd62290a88758bf210e
DxtoryVideo_Uninstall.bat Size: 58 bytes SHA1: 6d05923ef8db62f30ee22582f06979f4b2b48a64
DxtoryVulkanLayer.dll Size: 109,776 bytes Ver: SHA1: b8550335c1367d808b2bc64183ecda4ca61927ee
DxtoryVulkanLayer.json Size: 385 bytes SHA1: 2416b04e3895149b4200c1777f470a768519642d
DxtoryVulkanLayer64.dll Size: 132,816 bytes Ver: SHA1: e9c6eaa8d2ad7d684c9525787455d3aca38f6598
DxtoryVulkanLayer64.json Size: 387 bytes SHA1: 13d84a82bda5f98cb6ad6069c13c9ce2304b7d38
Dxtory_ja.txt Size: 19,608 bytes SHA1: 3d0dd54fa0a9ef379f1c663436bfeb799c643963
EULA_en.txt Size: 1,356 bytes SHA1: 340c6b3425ab78d83c6a8bd344b6cc58d152ce8f
EULA_ja.txt Size: 1,814 bytes SHA1: cded0d38ec6a1cb0e86bc264496deaa28082cb51
filelist.txt Size: 279 bytes SHA1: 94b5914435669bca384151d07d728dd504c628b4
filelist64.txt Size: 289 bytes SHA1: 516292e689ee64bc4e19151dadfe6d2cf901b52d
ignore_module_list.txt Size: 1,346 bytes SHA1: 479ca301e9a14d3fc927ca80f6d12481a8644922
InstallVulkanLayer.bat Size: 69 bytes SHA1: 156439c9308c8b5a32d697e1f3c11c2c5199a64b
InstallVulkanLayer64.bat Size: 71 bytes SHA1: 35574f9f2a414e8ebc592a8cec5a83d030b07000
LicReg.dat Size: 13,663 bytes SHA1: e0402e4fb670ca646799839b5604b8f3dd9675e5
LicReg.exe Size: 95,952 bytes Ver: SHA1: 3382997b62809ac29762a6ea62197c6eb4c24094
LicRegNoUI.exe Size: 19,664 bytes Ver: SHA1: cfd4884e884e8fd708874bfcc660f3ea2301693a
LicReg_ja.txt Size: 707 bytes SHA1: 981af64897276c22867952f4972d9c29c6ee35e7
RawCapConv.exe Size: 208,928 bytes Ver: SHA1: 32b6ec5d2f6649df4a47aedc476965433a8bdec4
RawCapConv_ja.txt Size: 1,869 bytes SHA1: 12086976f07abfc8d435abeee6c450c3cb2b07cd
RCStream.dll Size: 164,352 bytes Ver: SHA1: 31266452f142cd7c856384945ffc410b2c9c8be9
readme.txt Size: 1,322 bytes SHA1: f8b7e31de7927309f7f3e03936374837906a94d9
Src16x10_Dest4x3.png Size: 40,081 bytes SHA1: 3b4f6332b8b3129ee351a9c96a9c4ac7f6f7a4cd
Src16x9_Dest4x3.png Size: 40,179 bytes SHA1: fcec824f4e95f7becf65bbabcc1a99c1470b99a1
unins000.dat Size: 24,102 bytes SHA1: 5787d28c072b84474b5dd119479b81f50c823da3
unins000.exe Size: 1,202,896 bytes Ver: 51.1052.0.0 SHA1: d10c3dbe22cec6419f2a81b557432856a7eb91b2
unins000.msg Size: 22,701 bytes SHA1: ab7961d64f8b22503c9c7ca4b335fa539b0278a3
UninstallVulkanLayer.bat Size: 71 bytes SHA1: f54f1fabd821b9e82086eebae8eb89e4e9322f86
UninstallVulkanLayer64.bat Size: 73 bytes SHA1: 3646bdc62ab4d18d3e8bf7e261dbc03ee7d77bfc
UpdateChecker.exe Size: 93,696 bytes Ver: SHA1: 221bd3663f4393b368ebf74d1a892f9379ddbe44
UpdateChecker.ini Size: 238 bytes SHA1: 796da23b4a505bf2ef370dc271d1a80585dff6e2
UpdateChecker_ja.txt Size: 190 bytes SHA1: 969913786a3497f3e448572f7810ee9814314928
UWPHelper.dll Size: 132,304 bytes Ver: SHA1: 5e6de832fad6d5d40bba66e568abc780cd93f9b4
UWPHelper64.dll Size: 159,440 bytes Ver: SHA1: 9ddfab3d06bb0894341ba63a8dab98c83222d38f
DxtoryCodec.dll 64bit Size: 2,606,144 bytes Ver: SHA1: 7ef69696fe270d8bf353ead32bd58681ee61e5fe
DxtoryCodec.dll 32bit Size: 2,499,648 bytes Ver: SHA1: cd610194e3ddceefa04bc0f28a5f2139fee0d615

[System Information]
CPU: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz
OS: Microsoft Windows 10 Pro x64
OSVersion: 10.0.14393
OSLanguage: 2057
Memory0: BANK 0 8,589,934,592 bytes
Memory1: BANK 1 8,589,934,592 bytes
Memory2: BANK 2 8,589,934,592 bytes
Memory3: BANK 3 8,589,934,592 bytes
TotalMemory: 34,359,738,368 bytes
Total Physical Memory: 34,305,863,680 bytes
Available Physical Memory: 24,229,961,728 bytes
Total Page File: 39,406,137,344 bytes
Available Page File: 28,399,628,288 bytes
Total Virtual Memory: 2,147,352,576 bytes
Available Virtual Memory: 1,601,372,160 bytes
PerformanceCounterFrequency: 3906248 (0x3B9AC8)
VideoCard: NVIDIA GeForce GTX 1080 Memory: 4,293,918,720 Processor: GeForce GTX 1080 DriverVer: DriverDate: 2017-05-17 02-00-00
Display0: 1920x1080 32bits 60Hz
Display1: 1920x1080 32bits 60Hz
SoundDevice: NVIDIA High Definition Audio Manufacturer: NVIDIA
SoundDevice: Realtek High Definition Audio Manufacturer: Realtek
SoundDevice: NVIDIA Virtual Audio Device (Wave Extensible) (WDM) Manufacturer: NVIDIA
SoundDevice: VB-Audio Cable A Manufacturer: VB-Audio Software
SoundDevice: VB-Audio Cable B Manufacturer: VB-Audio Software
SoundDevice: VB-Audio Virtual Cable Manufacturer: VB-Audio Software

NVDriver: 382.33 r381_00
GPU0: GeForce GTX 1080 Memory: 8192MB MemoryClock: 5005MHz BaseClock: 1683MHz BoostClock: 1823MHz

[Audio Device]
CABLE-A Input (VB-Audio Cable A) - CoreAudioOut
CABLE-B Input (VB-Audio Cable B) - CoreAudioOut
CABLE Input (VB-Audio Virtual Cable) - CoreAudioOut
S22D390-C (NVIDIA High Definition Audio) - CoreAudioOut
S22D390-8 (NVIDIA High Definition Audio) - CoreAudioOut
Speakers (Realtek High Definition Audio) - CoreAudioOut
CABLE-A Output (VB-Audio Cable A) - CoreAudioIn, Volume 99
CABLE Output (VB-Audio Virtual Cable) - CoreAudioIn, Volume 100
Microphone (Realtek High Definition Audio) - CoreAudioIn, Volume 100
CABLE-B Output (VB-Audio Cable B) - CoreAudioIn, Volume 99

[Video Codec 64bit]
Intel IYUV codec FCC:i420
Intel IYUV codec FCC:iyuv
Lagarith Lossless Codec FCC:lags
Microsoft RLE FCC:mrle
Microsoft Video 1 FCC:msvc
x264vfw - H.264/MPEG-4 AVC codec FCC:x264

[Video Codec 32bit]
Cinepak Codec by Radius FCC:cvid
Intel IYUV codec FCC:i420
Intel IYUV codec FCC:iyuv
Lagarith Lossless Codec FCC:lags
Microsoft RLE FCC:mrle
Microsoft Video 1 FCC:msvc
VP60® Simple Profile  FCC:vp60
VP61® Advanced Profile FCC:vp61
x264vfw - H.264/MPEG-4 AVC codec FCC:x264

[Audio Codec]
Microsoft IMA ADPCM
Microsoft CCITT G.711
Microsoft GSM 6.10
IEEE Float

[License Information]
License: Registered
Expire: Unlimited
LicVerify: 36966617b60c2972bdd89acc9b6dea069b3d65c6

[Additional Information]
Dxtory_log.txt: Empty
ErrorLog.txt: Empty

[Global Setting]
OptionFlag: SharedJavaProfile

[Ignore List]


Name: Default

Position: LeftTop
Flag: VidoeFPS RecordFPS RecordState Time Size Rate Warn
Layout: Vert
Color: Sleep FF00FF00, Active FFFF0000, Movie  FF00FF00, ScreenShot FF00FF00

x C:\Users\Lars\Dxtory Temporary  Speed: 400MB/sec  Free: 266,803,679,232 Total: 499,514,339,328 Format: NTFS

MovieCapture: \ (0x0000002B)
PushToTalk: None
ScreenShotSingle: None
ScreenShotRepeat: None
ScreenShotAuto: None
ToggleStatus: None
MovieCaptureFrame: None
ScreenShotCaptureFrame: None

ClipMargin: 0,0,0,0
ClipSize: 0,0
Scaling: Size 100% 1280x720
Codec: x264vfw - H.264/MPEG-4 AVC codec, Quality 10000, KeyFrameRate 15, DataRate 0, 64bit
FrameRate: 30
Output: File AVI

Enabled: True
PushToTalk: False
Device: Speakers (Realtek High Definition Audio)
Codec: PCM
Format: PCM 48000 Hz, 16 bit, Stereo

Enabled: True
PushToTalk: False
Device: Microphone (Realtek High Definition Audio)
Codec: PCM
Format: PCM 48000 Hz, 16 bit, Stereo

ClipMargin: 0,0,0,0
ClipSize: 0,0
Scaling: Percent 100% 0x0
HighSpeedLimit: 0
RepeatInterval: 1000
Format: PNG
JpegQuality: 97

ThreadCount: 1
ThreadMask: 00000000000000FF
LimitedFPS: False
FPSLimit: 60
DelayHook: False
DelayHookTime: 5


Name: Rainbow Six
Path: D:\Program Files (x86)\Ubisoft\Ubisoft Game Launcher\games\Tom Clancy's Rainbow Six Siege\RainbowSix.exe

DateTime: 2017/07/29 02:01:24
Version: 2.0.142
64bit Process
DeviceType: GL DX9 DX11
View0.WindowTitle=Rainbow Six

VerifyHash: 2a7814c40095e3c36674a32a308331f195dc23fe

[Error log]
These logs are blank when trying to open them

[x264vfw Codec Settings]

« Last Edit: July 29, 2017, 03:40:59 pm by Poetepoet »


  • Monster
  • ****
  • Posts: 274
Re: DxTory not recording, FIN error after stopping recording
« Reply #1 on: July 29, 2017, 12:39:25 pm »
Please post / attach a screenshot of x264vfw settings.
Using Windows 10 ?  Try the latest version first


  • Noob
  • *
  • Posts: 4
Re: DxTory not recording, FIN error after stopping recording
« Reply #2 on: July 29, 2017, 03:41:31 pm »
I have added a screenshot to the original post, at the bottom.

Thanks for helping!


  • Monster
  • ****
  • Posts: 403
    • Youtube channel
Re: DxTory not recording, FIN error after stopping recording
« Reply #3 on: July 30, 2017, 03:26:44 am »
iirc realtime usage of x264vfw requires the zero latency option enabled


  • Noob
  • *
  • Posts: 4
Re: DxTory not recording, FIN error after stopping recording
« Reply #4 on: July 30, 2017, 11:53:27 am »
Malix, your suggestion seems to have worked! I can record now. I will run some more tests with all HUD elements on for confirmation.]

I do however get the !GPU bottleneck warning. Do you know what that means, and do you have a potential fix?

Thanks a million though!


  • Monster
  • ****
  • Posts: 403
    • Youtube channel
Re: DxTory not recording, FIN error after stopping recording
« Reply #5 on: July 30, 2017, 08:34:41 pm »
the !GPU warning means that the game isn't running atleast on at the fps you are recording. Essentially: Disable vsync, lower details, overclock, aquire better hardware... Though hardware should be fine in your case :P Maybe put on one of the faster presets, like ultrafast in the x264 settings

« Last Edit: July 30, 2017, 08:56:35 pm by Malix »


  • Monster
  • ****
  • Posts: 274
Re: DxTory not recording, FIN error after stopping recording
« Reply #6 on: July 31, 2017, 12:09:47 am »
I've found that sometimes when those warnings ( storage, gpu, ect ) show up that its not always the true source of the problem.  Maybe Ex will refine them some day or allow users to set the tolerances.   In any case, I'd first try "Multi device processing" under the advanced tab before doing anything else.
Using Windows 10 ?  Try the latest version first


  • Monster
  • ****
  • Posts: 403
    • Youtube channel
Re: DxTory not recording, FIN error after stopping recording
« Reply #7 on: July 31, 2017, 12:44:07 am »
edit: I actually went on a "rant" instead of even trying to answer. I did a derp.

I've only seen the !GPU warning pop up when my game's fps drops below my recording fps. !storage happens when the recording drive can't keep up with the codec's bitrate, !Encode happens when cpu can't process the recording framerate, even if game fps and storage could.

--End of edit.

For me, the crucial option to enable is "Wait for Available Buffer", it was one of the 2.0.14x (iirc) versions that made it pretty much mandatory. I've never really needed the "Multi Device Processing" (I do have a SLI setup, not entirely sure if its related to the option as "Multi GPU stable processing" is separate thing.)

As much as I love Dxtory, the english translation leaves quite a bit room for improvement. I wish that he would at least crow/out-source the translations a bit to make the options and whatnot a bit easier to understand.

Or at minimum post detailed explanations of the options, like what they do and under which circumstances they should/shouldn't be used.

Pretty please :)
« Last Edit: July 31, 2017, 12:59:55 am by Malix »


  • Noob
  • *
  • Posts: 4
Re: DxTory not recording, FIN error after stopping recording
« Reply #8 on: August 01, 2017, 10:25:41 am »
Regardless, you saved me. I was saddened having spent 30 euros on software that refused to run, and you made it work. I turned on all HUD elements and !GPU seems to show up when entering menus and the game FPS drop to 58-ish. Seems in line with what you mentioned. I'm glad the !STORAGE doesn't mean not enough room, my SSD had 250GB remaining. I will invest in a recording only SSD, people seem to recommend not writing to the OS SSD.

Thank you both for helping me out!