Time-out on Windows start | Everything Service | ntdll.dll | SOLVED

[tuska]

Hi,
I let Everything start with Windows and therefore have "Start Everything on system startup" ticked.

Unfortunately, I have to find out quite often that it comes to a crash of Everything after PC-start.
For me to read in the folder: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\
File "Report.wer": Fault Module Name "ntdll.dll" - Fault Module Version: 10.0.17134.1

Therefore, I would like to ask if there is a setting that Everything will be started delayed,
eg 1 minute after PC start --> time-out on Windows start.

If this setting does not exist yet, then I would like to propose this.
Maybe then (with me) can be achieved that fewer program crashes occur.

Otherwise, I am very satisfied with Everything!

Regards,
Karl

Everything Version 1.4.1.901 (x64)
Windows 10 Pro (x64) Version 1803 (OS build 17134.48)
16,0 GB RAM | Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz

[horst.epp]

I have the same version of OS and Everything.
There is no problem to read the contents of the WER folders.
I guess you have not installed the Everything service.
Do this and also let Everything start with your normal windows logon.

[tuska]

"Everything Service" is ticked - UAC is on.
I also have no problems with reading the WER folder.

Everything usually works very well for me, but ...
- in rare cases, when I get the prompt window to install the "Everything Service", Everything has already crashed.
- in folder C:\ProgramData\Microsoft\Windows\WER\ReportArchive\ are the following subfolders with file "Report.wer":
AppCrash_Everything.exe_29f9278c4fa9f331f2e4c2dd7010245f8dda6d_6d213af6_33d1634f\ <DIR> 20.05.2018 11:33 ----c
AppCrash_Everything.exe_29f9278c4fa9f331f2e4c2dd7010245f8dda6d_6d213af6_29bb6a43\ <DIR> 19.05.2018 10:28 ----c
AppCrash_Everything.exe_29f9278c4fa9f331f2e4c2dd7010245f8dda6d_6d213af6_00aa2c73\ <DIR> 17.05.2018 11:16 ----c
AppCrash_Everything.exe_29f9278c4fa9f331f2e4c2dd7010245f8dda6d_6d213af6_2f602762\ <DIR> 15.05.2018 11:18 ----c
AppCrash_Everything.exe_29f9278c4fa9f331f2e4c2dd7010245f8dda6d_6d213af6_04d4bc7c\ <DIR> 13.05.2018 19:55 ----c
AppCrash_Everything.exe_29f9278c4fa9f331f2e4c2dd7010245f8dda6d_6d213af6_28074c8d\ <DIR> 11.05.2018 10:27 ----c
AppCrash_Everything.exe_29f9278c4fa9f331f2e4c2dd7010245f8dda6d_6d213af6_4888b58e\ <DIR> 08.05.2018 11:22 ----c
AppCrash_Everything.exe_29f9278c4fa9f331f2e4c2dd7010245f8dda6d_6d213af6_cab_21ddcf68\ <DIR> 05.05.2018 11:25 ----c

Although I'm not sure if all crashes were always done immediately after PC startup.
The vast majority of crashes are certainly from PC start.

[void]

Thanks for the info Karl,

Disabling allow_ntfs_open_file_by_id can help with crashes in ntdll.dll

Please try disabling allow_ntfs_open_file_by_id:
In Everything, type in the following search and press ENTER:
/allow_ntfs_open_file_by_id=0

You should see allow_ntfs_open_file_by_id=0 in the status bar for a few seconds.



To delay "Everything" from loading its database and starting the NTFS monitors (which is most likely causing the ntdll.dll crash) please start Everything with the -load-delay x command line options:
Everything.exe -load-delay 60000
where 60000 is the number of milliseconds (1 minute in this case) to delay loading of the Everything database.

The easiest way to use the -load-delay command line option would be to disable Everything from running on system startup and create a shortcut to Everything -load-delay 60000 in your start menu startup folder:

• In Everything, from the Tools menu, click Options.
• Click the General tab on the left.
• Uncheck Run Everything on system startup.
• Click OK.
• Open Windows Explorer and navigate to shell:startup
• Create a new shortcut to your Everything.exe
• Set the command line arguments to -load-delay 60000, the target should look something like:
  "C:\Program Files\Everything\Everything.exe" -load-delay 60000

[tuska]

Thanks for the prompt support and the detailed instructions David!
I've set everything up the way you recommended.
I give feedback here in a few days.

[tuska]

Here are the results with almost daily use of the PC:

On 31.5. -> no crash of Everything.exe
AppCrash_Everything.exe_29f9278c4fa9f331f2e4c2dd7010245f8dda6d_6d213af6_3ee09038\ <DIR> 30.05.2018 09:57 ----c and Rebuild index!
On 30.5. there were no crashes on two more PC starts (one after Update to Windows 10 Pro (x64) Version 1803 (OS build 17134.81))
On 28.5. with Start-Restart and Start-Exit-Restart there was no crash.
AppCrash_Everything.exe_29f9278c4fa9f331f2e4c2dd7010245f8dda6d_6d213af6_2ba86ebd\ <DIR> 26.05.2018 16:13 ----c
AppCrash_Everything.exe_df5d8567dcd4d1dfa6a02f7ffb98bfe0db476d_6d213af6_447c3d66\ <DIR> 25.05.2018 09:55 ----c
For two more restarts on 25 May 2018 (Start-Restart and Start-Exit-Restart) there was no crash.
AppCrash_Everything.exe_29f9278c4fa9f331f2e4c2dd7010245f8dda6d_6d213af6_003d2347\ <DIR> 24.05.2018 09:38 ----c
For two more restarts on 24 May 2018 (Start-Restart and Start-Exit-Restart) there was no crash.
AppCrash_Everything.exe_df5d8567dcd4d1dfa6a02f7ffb98bfe0db476d_6d213af6_60bcd9b2\ <DIR> 22.05.2018 08:15 ----c

Unfortunately, the indicated options did not succeed.

--------
I also use the program Listary with installed system-service (ListaryService), which sometimes crashes due to the file ntdll.dll:
AppCrash_ListaryService.e_96f1e2c08f9d8ad282c6f543a7be219e76c1b26a_da5bf675_34f89f09\ <DIR> 29.05.2018 13:07 ----c
AppCrash_ListaryService.e_96f1e2c08f9d8ad282c6f543a7be219e76c1b26a_da5bf675_3127e1f1\ <DIR> 24.05.2018 11:07 ----c
--------
I found these files on my pc related to ntdll.dll:
File Description: NT Layer DLL // Digital signature: Microsoft Windows - Digest algorithm: sha256

Time stamp: Wednesday, ‎11. ‎April ‎2018 06:38:12 - the two files below are identical ...
C:\Windows\System32\ntdll.dll 1.946.304 12.04.2018 01:34 -a--
C:\Windows\WinSxS\amd64_microsoft-windows-ntdll_31bf3856ad364e35_10.0.17134.1_none_3e576a9965581200\ntdll.dll 1.946.304 12.04.2018 01:34 -a--

Time stamp: Wednesday, ‎11. ‎April ‎2018 06:24:07 - the two files below are identical ...
C:\Windows\SysWOW64\ntdll.dll 1.622.408 12.04.2018 01:34 -a--
C:\Windows\WinSxS\wow64_microsoft-windows-ntdll_31bf3856ad364e35_10.0.17134.1_none_48ac14eb99b8d3fb\ntdll.dll 1.622.408 12.04.2018 01:34 -a--
--------

The internet (after Google queries) is full of suggested solutions regarding ntdll.dll - but I do not want to make my system worse.

I will increase the suggested value to 2 minutes (120000 milliseconds) for a few days.
If that does not help, then as a next step, I would consider removing the entry/link in the startup folder.

[tuska]

I will increase the suggested value to 2 minutes (120000 milliseconds) for a few days.
If that does not help, then as a next step, I would consider removing the entry/link in the startup folder.

Unfortunately that did not help:
AppCrash_Everything.exe_29f9278c4fa9f331f2e4c2dd7010245f8dda6d_6d213af6_0f03c42c\ <DIR> 01.06.2018 09:31 ----c ***)

I therefore remove the link in the startup folder and tick "Start Everything on system startup" again.
The error must be somewhere on my PC.

Should I be able to resolve the problem myself at some point, then I would announce the solution here.
Thank you for the support.

Regards
Karl

***) /EDIT
Only as info:
With two further restarts (start - restart) on 1 June 2018 in the evening there was no crash
--> Setting: "Start Everything on system startup" again ticked. <--

[therube]

Do you think there could there possibly be some interaction going on between Everything & Listary services?
So if you disable one from starting with Windows start, does the other always start successfully?
And then if you switch disabling that one & enabling the other, does it also work successfully that way?


(Was looking at my brothers laptop, issue with Win10 1803 & old version of Excel, causing Excel to crash [when entering data into a spreadsheet] - known issue [heh, at this point]. Anyhow, on computer startup, his desktop would display, & I'd click the Excel icon & Excel would open, but almost immediately go opaque & I'm like what? Well what it was, is that there was so much background crap loading that there was not enough CPU to go around to both open Excel (which should be a relatively light process) & also fire all the other crap that was still, & one might not necessarily be aware, loading. So until that activity subsided a bit, Excel was "frozen", opaque.)

[tuska]

Do you think there could there possibly be some interaction going on between Everything & Listary services?

I also suspected that the two system services could interfere with each other.
So far, however, I have both system-services started automatically and only the program Listary manually started.

So if you disable one from starting with Windows start, does the other always start successfully?
And then if you switch disabling that one & enabling the other, does it also work successfully that way?

Thanks for the hint!
In the first step I will set the service "ListaryService" to startup-type "manual" and check for a few days what happens.

Until now I had the impression that the crashes in both programs happen randomly (see also history above).

Everything Version 1.4.1.901 (x64)
Windows 10 Pro (x64) Version 1803 (OS build 17134.81)
Prozessor: Intel(R) Core(TM) i7-4770 CPU @ 3.4OGHZ, RAM: 16,0 GB

[horst.epp]

Do you think there could there possibly be some interaction going on between Everything & Listary services?

I also suspected that the two system services could interfere with each other.
So far, however, I have both system-services started automatically and only the program Listary manually started.

So if you disable one from starting with Windows start, does the other always start successfully?
And then if you switch disabling that one & enabling the other, does it also work successfully that way?

Thanks for the hint!
In the first step I will set the service "ListaryService" to startup-type "manual" and check for a few days what happens.

Until now I had the impression that the crashes in both programs happen randomly (see also history above).

Everything Version 1.4.1.901 (x64)
Windows 10 Pro (x64) Version 1803 (OS build 17134.81)
Prozessor: Intel(R) Core(TM) i7-4770 CPU @ 3.4OGHZ, RAM: 16,0 GB

I have the same OS config and Hardware.
Listary and Everything services are running.
Also both tools are addionaly started on log-on sitting in the tray.
Never had any crash from Listary or Everything in this scenario.

[tuska]

2horst.epp
You seem to have a perfect system, because everything always works for you.
Unfortunately that does not help me, except that I then know that there is/are a system(s) where my problem does not exist.

For me it currently looks like this:
I have set the service "ListaryService" to startup-type "manual" and then get the following results up to now...

Although I set Listary-Service to "manual" and have not yet started the program,
a) after a cold start, the Listary-Service was already displayed as "is running" (!?)
b) after a warm start, the Listary-Service is finished and must be started manually

2.6.2018 No crash of Everything + Listary Version 5.00.2843 after warm start.
3.6.2018 No crash of Everything + Listary after cold start and warm start.
4.6.2018 No crash of Everything + Listary after cold start and warm start.

I will continue to report ...

[tuska]

I will continue to report ...

 4.6.2018 No crash of Everything + Listary after cold start in the afternoon.
 5.6.2018 Crash of Everything after cold start - Everything Service had to be started manually
           Listary-Service was not started (OK)
 6.6.2018 No crash of Everything + Listary after cold start (Listary-Service was already started)
 7.6.2018 Crash of Everything after cold start - Everything Service had to be started manually
 8.6.2018 No crash of Everything + Listary after cold start (Listary-Service was already started)
 9.6.2018 Crash of Everything after cold start - Everything Service had to be started manually
           No crash of Listary (Listary-Service was already started)
10.6.2018 No crash of Everything + Listary after cold start (Listary-Service had to be started manually)
11.6.2018 No crash of Everything + Listary after cold start (Listary-Service had to be started manually)
12.6.2018 Crash of Everything after cold start - Everything Service had to be started manually
           No crash of Listary (Listary-Service was already started)
12.6.2018 No crash of Everything + Listary after warm start (Listary-Service had to be started manually)
13.6.2018 No crash of Everything + Listary after cold start (Listary-Service had to be started manually)
---------------------------------------------------------------------------------------------------------------------------------
Installation of Everything 1.4.1.895 and updating to version 1.4.1.903 -> using the same Everything.ini as for portable version!
13.6.2018 No crash of Everything + Listary after cold start (Listary-Service had to be started manually)
13.6.2018 No crash of Everything + Listary after 5(!) warm starts (Listary-Service had to be started manually)
14.6.2018 No crash of Everything + Listary after cold start (Listary-Service had to be started manually)
15.6.2018 No crash of Everything + Listary after cold start (Listary-Service had to be started manually)
16.6.2018 Crash of Everything after cold start - Everything Service had to be started manually

Unfortunately, it always comes back to crashes and for me no rule is derivable.
The ntdll.dll files are from 8/6/2018 - Windows 10 Version 1803 (OS build 17134.112).

Whatever goes wrong on my PC - I can not fix it.
So this topic is temporarily over for me.

[tuska]

By now I mean to have found out that the crashes of Everything with me almost exclusively cohere with the Everything Service.

If the PC has been started and the Task-Manager displays the Service as "Finished" (without the Everything.exe being called!),
then a folder is created in C:\ProgramData\Microsoft\Windows\WER\ReportQueue\ with the file Report.wer (error module name: ntdll.dll).

Both the folder, e.g. "AppCrash_Everything.exe_42e2dd77dfbaa742b4177b8fef4649f2e9561b7_37a69905_301f3424" and the file Report.wer
will then in a few seconds automatically moved by Windows to C:\ProgramData\Microsoft\Windows\WER\ReportArchive\.

It also did not help that in the properties of the Everything Service I have set the startup type to "Automatic (Delayed start)".

If I press Ctrl+Shift+ESC immediately after PC start to see in Task-Manager if the Everything Service is running
- without having started the Everything.exe - then there are the following results:
1. Status: "Running" -> Everything.exe can be called and used problem-free
2. Status: "Finished" -> Report.wer

Unfortunately, the Everything Service is still randomly started/not started on my Windows PC.

[OT: It's the same with ListaryService, but if this service is finished, then there is still no entry in ...WER\ReportArchive\.
On a request I received the following information on 19.7.2018 by "Listary":
"The service has been completely rewritten in Listary 6 (coming soon). It fixes some compatibility issues and crashes."OT\]

Windows 10 Pro (x64) Version 1803 (OS Build 17134.191) | Everything Version 1.4.1.906 (x64).

[therube]

Perhaps uncheck, Options | General -> Start Everything on system startup.

Run that way for a while & see what happens?
(I suspect the results will be the same.
As it seems to be the Everything Service that is the issue on your end?
And by the same token, leave the Everything Service enabled in Options.)


(On my end, while I use Everything [including its' Service] all the time, I do not start it [or anything] on system startup.
Rarely reboot.
Don't shut down [use sleep instead].
So in that respect, have never had the opportunity to see...
Hmm... but... a "service", being a service, you don't actually "run" it separately, rather it's "installed", & run by the OS, if you will.
So not particularly user action or inaction that is causing the issue, I'd think...)

[tuska]

Perhaps uncheck, Options | General -> Start Everything on system startup.
Run that way for a while & see what happens? ...

Thanks, I'll try it out for a few days now.

Don't shut down [use sleep instead]

That's a little too much to ask for.

[tuska]

[ ] Start Everything on system startup
[x] Everything Service: Startup type "Automatic (Delayed start)"

10.8.2018 Although Everything.exe was not started and does not start automatically after PC start, i.e. started with Windows
                the Everything Service had the status "Will be executed"! With that a trouble-free start of "Everything.exe" was possible!
10.8.2018 12:52h Crash (ntdll.dll)
11.8.2018 No Crash
12.8.2018 Although Everything.exe was not started and does not start automatically after PC start, i.e. started with Windows
                the Everything Service had the status "Will be executed"!
                Start of Everything.exe -> Crash and Everything Service ended automatically.

At this point, I am finally giving up my observations.
In case of need, I reboot both the Everything Service and Everything.exe.

Thanks for the support!

Everything Version 1.4.1.907 (x64)
Windows 10 Pro (x64) Version 1803 (OS Build 17134.191)

[NotNull]

Something to be aware of when testing:
Since Windows 10 (or 8?) Shutdown isn't the same as it used to be .... It doesn't really shutdown, but stops some processes (not all) and writes that state to disk, like hibernate does.
When you turn on your PC again, that state got loaded into RAM.
So, for accurate results it's better to do a Restart


You can make Windows' Shutdown behave "normal" again:
- Start powercfg.cpl
- Select Choose what the power button does
- Click Change settings that are currently unavailable
- Uncheck Turn on fast startup


BTW: Did you also test with Listary completely uninstalled? THere might be a conflict in accessing (or connecting to) the MFT/ USN Journal

[tuska]

2NotNull
I have now made the settings that you have advised me.
Next week I will do tests with uninstalled Listary and then report, as I did not test with Listary completely uninstalled.

Thanks for your support!

Regards
Karl

[void]

Please try Everything 1.4.1.908.

This version has OpenByFileID disabled, which is most likely causing the issue.

[tuska]

2NotNull
I have made the settings above that you have advised me.
It should be noted that with this setting it was lost that I could start my PC, for example, by pressing the Ctrl key,
instead of the on/off switch.

I tested up from 19 Aug. 2018 as follows:

Everything
[x] Start Everything on system startup
[x] Everything Service - startup-type: Automatic
    BTW, startup-type has automatically changed from "Automatic (Delayed start)" ... to Automatic without my intervention on 19.08.

Listary
- I did not start Listary.exe (portable version)
- I removed the "ListaryService" as follows, based on this topic in German:
  https://www.windows-faq.de/2017/05/21/d ... indows-10/
  Click Start-button, type in dos, Right click on the "Command prompt desktop app", click on "Run as administrator"
  sc delete ListaryService <ENTER> ... ([SC] DeleteService SUCCESS ... is shown)
  exit <ENTER> closes the DOS window

Up to now - after 7 PC restarts - "Everything Service" started automatically - no crash!

2void

Please try Everything 1.4.1.908.

Thank you!
Up from now I use this version portable and will Listary "turn on" again.
I will report again in a few days.

Regards
Karl

[tuska]

If the "Everything Service" is running, "Everything" is running!
Unfortunately that was not always the case with me.

I have now performed new tests under the following conditions:
- Everything Version 1.4.1.908 (x64) since 23.8.2018 and Version 1.4.1.909 (x64) since 2.9.2018 - (portable version)
- [x] Start Everything on system startup
- [x] Everything Service: Automatic
- After starting the PC, I regularly started Everything after about 1 minute
- Windows - Shutdown: Checked "Turn on fast startup"
- Listary Version 5.00.2843 - Reinstallation and use of the installed version (formerly the portable version was used)

Results:
Listary Version 5.00.2843 has worked without crashing from 23.8.-3.9.

Everything
The PC was only once "restarted", otherwise always "shut down" and then turned on again [the next day].
23.8. OK
24.8. OK
25.8. Crash ("Everything Service" had to be restarted, since it was finished) - 2 folders with error messages:
- AppCrash_bad_module_info_b81c57fcbcaff8b63f8da6b9b20c7e7d67e3b95_85207d7d_27156f27 - NsAppName=bad_module_info,
  TargetAppVer=1970//01//01:00:00:00!0!Everything.exe, Sig[1].Name=Anwendungsversion; Sig[1].Value=0.0.0.0
  AppCrash_Everything.exe_176c5c2ffec745282d4c63237494c9591221a7dd_57b888b9_cab_387964e6
- AppCrash_Everything.exe_176c5c2ffec745282d4c63237494c9591221a7dd_57b888b9_cab_387964e6 --> ntdll.dll
26.8. OK
27.8. OK (2x); PC restarted (1x) ==> in total: 3x OK!
28.8. OK
29.8. Crash - ntdll.dll - Everything Service ended
30.8. OK
31.8. Crash - ntdll.dll - Everything Service ended
31.8. OK
01.9. Crash - ntdll.dll - Everything Service ended
01.9. OK
01.9. OK - Windows 10 Pro (x64) Version 1803 (OS Build 17134.254)
02.9. OK - Everything Version 1.4.1.909 (x64)
03.9. OK

Conclusion:
With a total of 17 starts there were 4 crashes with the portable version.
I can live with that

Theoretically, I could now do more tests with an installed Everything version,
At the moment I want to leave it as it is.

[void]

I would really like to help solve this issue, but I will need your help.

Would you mind downloading and installing systernals Procdump and capturing an Everything Service crash?

• Please download procdump.
• Create the following folder C:\crashdumps
• Extract procdump to C:\crashdumps
• From an administrator control panel, navigate to: C:\crashdumps
  Run the following command:
  procdump.exe -i -ma
  -This will install the procdump as the debugger.
• Reproduce the Everything Service crash.
• From an administrator control panel, navigate to: C:\crashdumps
  Run the following command:
  procdump.exe -u
  -This will uninstall the procdump as the debugger.
  There should be a dmp file in your C:\crashdumps folder.
  Could you please send this file to support@voidtools.com

https://needleinathreadstack.wordpress. ... -procdump/

[tuska]

Thank you for your support!
I've set everything up as you've described.

After 3 more PC cold starts and 1 PC warm start today, Everything worked every time.
If "Everything" crashes again, I'll send you the .dmp file.

[tuska]

• Run the following command:
  procdump.exe -i -am

Just one question about the parameters:

https://needleinathreadstack.wordpress. ... -procdump/
Under pt. 1. the parameter is specified as follows: procdump.exe -i -ma

According to your instructions I have prepared this with: procdump.exe -i -am
Can I leave it that way or do I have to start the action again with: procdump.exe -i -ma?

[tuska]

I'll give myself the answer:
I suspect that procdump.exe -i -ma is correct and have therefore executed procdump.exe -u.
Then I ran procdump.exe -i -ma.

[void]

Sorry, the procdump installation should be:
procdump.exe -i -ma

[NotNull]

Not for now (don't want to interfere with your testing), but you can make Windows restart the Everything service when it crashes:
(I'm posting this now because otherwise I probably forget ..)

From an administrative command prompt, issue these commands:

Code: Select all

sc failure everything actions=restart/3000/restart/3000/restart/3000 reset=86400
sc failureflag Everything 1

This will restart the Everything service - multiple times if needed - after 3 seconds (=3000 ms)
The 'crash counter' will be reset after 86400 seconds (= 1 day)

With a GUI:
Start services.msc as an administrator, double-click Everything and configure as follows:

2018-09-03 22_50_19-Everything Properties (Local Computer).png (14.46 KiB) Viewed 36745 times

(Note that you don't have an option here to configure the 'wait period' (default is 5 seconds IIRC)

[tuska]

2void
Thanks for the message and correction.

After 2 more PC cold starts - no crash (Everything Service is running).
Thus it stands 23/4 (23.8.-4.9.).

2NotNull
Thank you for your interesting hints and solutions.

[tuska]

2void

Today the "Everything Service" was finished and several .dmp files were created because of procdump.exe:

Code: Select all

Name                                            Size            Creation date/time      Attr.
---------------------------------------------------------------------------------------------
backgroundTaskHost.exe_180905_105225.dmp	      119.704.986	 05.09.2018 10:52	      -a--  *)
backgroundTaskHost.exe_180905_105227.dmp	      119.704.986	 05.09.2018 10:52	      -a--  *)
Everything.exe_180905_105237.dmp	               63.254.397	 05.09.2018 10:52	      -a--
Everything.exe_180905_105244.dmp	               63.254.397	 05.09.2018 10:52	      -a--

(After a file comparison - the files are different).

Due to the file sizes I have sent you a download link via e-mail and ask you to check the files.
Many Thanks!

Windows 10 Pro (x64) Version 1803 (OS Build 17134.254)
Everything - Version 1.4.1.909 (x64)

*) EDIT:
An error concerning backgroundTaskHost.exe, error module name: msvcrt.dll has not been noticed by me yet.
(Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy)
---
I also uploaded the Report.wer files to OneDrive.

[NotNull]

Code: Select all

Name                                            Size            Creation date/time      Attr.
---------------------------------------------------------------------------------------------
backgroundTaskHost.exe_180905_105225.dmp	      119.704.986	 05.09.2018 10:52	      -a--  *)
backgroundTaskHost.exe_180905_105227.dmp	      119.704.986	 05.09.2018 10:52	      -a--  *)
Everything.exe_180905_105237.dmp	               63.254.397	 05.09.2018 10:52	      -a--
Everything.exe_180905_105244.dmp	               63.254.397	 05.09.2018 10:52	      -a--

Off-topic:
This layout looks very familiar, but I can't pinpoint where I've seen it.
Please tell me how you generated it, so I can get this annoying riddle out of my system

[tuska]

Off-topic:
This layout looks very familiar, but I can't pinpoint where I've seen it.
Please tell me how you generated it, so I can get this annoying riddle out of my system

In a standard view in Total Commander 9.21a I marked the files and used a button with command: cm_CopyFileDetailsToClip.
In the forum I inserted the content of the clipboard and then I used the code field and added the heading (Name, Size,...) myself.

[NotNull]

Yes, that was it .. Total Commander!
This was bugging me all day long, like a song or a person's name you can't remember. Now I can sleep tonight ...

Thanks!! (and also thanks for the Total Commander lesson; I didn't know about button commands)

[tuska]

Yes, that was it .. Total Commander!
This was bugging me all day long, like a song or a person's name you can't remember. Now I can sleep tonight ...

Thanks!! (and also thanks for the Total Commander lesson; I didn't know about button commands)

[OT]
Don't sleep too long, because there is much to discover if you enter the following in the TC's commandline and press ENTER: cm_CommandBrowser
Btw, a combination of commands is also possible, e.g. command: cm_VerticalPanels,cm_50Percent

[/OT]

[tuska]

2void
I have also uploaded Everything.ini to OneDrive in case you need this file.

[tuska]

I tested with version 1.4.1.911 (x64) and version 1.4.1.912 (x64) and gave feedback via email on 8.9.2018.
From now on I use the latest version, currently version 1.4.1.913 (x64).

[void]

Thanks for the help Tuska,

We haven't found the exact cause yet.

An exception is thrown, however, when unwinding the stack, more exceptions are thrown, this repeats forever, causing a stack overflow.

Most of the time, the original exception is caused by the OS being unable to read the page file from disk back into ram:
Unhandled exception at 0x00007FFC76DE80E8 (ntdll.dll) in Everything.exe_180915_115802.dmp: 0xC0000006: In page error reading location 0x000000014020E234 (status code 0xC000026E).

Which may indicate a hard disk fault.

Could also be stack corruption which makes it tricky to debug..

Somethings which may help others:

• Disable paging executive
• Disable the page file (not recommended)

[tuska]

A big thank from me - especially to you - and all the others who have tried to give support here.
Fortunately, this phenomenon only occurs very rarely in connection with "Everything".

[tuska]

2David
Thank you for checking this topic again so thoroughly!

Due to your program changes
- since version 1.4.1.927 the "Everything" Service on my PC always runs in the status "Will be executed" after PC start
- the problem with crashes of "Everything" --> File "Report.wer": Fault Module Name "ntdll.dll" is fixed in my opinion as well

Thank you very much for your efforts!

Regards
Karl
________________________________________________
Windows 10 Pro (x64) Version 1809 (OS Build 17763.253)
Intel(R) Core(TM) i7-4770 CPU @ 3.4OGHz, 16 GB RAM
Everything - Version 1.4.1.930 (x64) - Beta Nightly Builds

[void]

To recap, the Everything Service was crashing on startup for Tuska.

My guess is an issue with Windows Hibernation and a hard disk driver:
When the PC is powered on from hibernate, memory is restored from disk.
The Everything Service would crash immediately, because its program memory was not restored from disk. (Exception: In Page Error: 0xC0000006 Status Code: 0xC000026E)

Disabling Hibernation or moving Everything.exe to a system drive fixed the issue.