Everything Service 'Hung' Eating CPU

Discussion related to "Everything" 1.5 Alpha.
Post Reply
therube
Posts: 4985
Joined: Thu Sep 03, 2009 6:48 pm

Everything Service 'Hung' Eating CPU

Post by therube »

Everything Service 'Hung' Eating CPU, & Everything GUI went opaque.

Never seen that before.

Had to kill GUI, & then also the Service.
(As in killing the GUI did not affect the hungry Service.)

.
Everything Service 100 of 1 CPU after Index Pause.png
Everything Service 100 of 1 CPU after Index Pause.png (65.87 KiB) Viewed 615 times

Of late*

Of late, heh. Of late, very infrequently (on office computer) when I'll go to Safely Remove a couple of USB (flash &/or SSD) drives, I'll get a "busy".

AFAIK, there is no "busy", as in I have nothing open... on the drives.

Though, in particular instances of Everything - those that actually Index said USB drives (& that is all they index, only said USB drives, & no other drives, & no other instances index those USB drives), if I 'Index | Pause Updates' (followed immediately by 'Index | Resume Updates), I can then Safe Remove the USB drive - every time.

Checking other avenues, manually "sync'ing"... provide no relief.
Index, Pause, Index, Resume, works.

So yesterday, I Index, Pause, (& I suppose I then also Index, Resume, as I would normally do), & for whatever reason Everything Service starting eating CPU & GUI went opaque. And at that point, I was unable to interact with either the Service (-uninstall-service) or the GUI (& had to kill both).

In all the years, I've never had issues with Safely Remove.
More recently, yes.
My USB's (well except for any HDD based in a USB adapter) have always been "flash" drives (with Kingston, my "regular"). More recently I picked up a newer (old) PNY (flash) drive, & more recently again, I got a M.2 SSD that I put into a USB adapter.

Initially, it was the SSD that I ran into troubles with (Safely Remove), never having had any issues with the Kingston. And initially, it was only on my home computer*. More recently, very, very infrequently, the Kingston also failed to Safely Remove. And now, I've seen it on both computers (but more often on home).

*Home computer.
Oh, I pretty sure is on its way out. Motherboard most likely. At least some of my M/B SATA connectors have gone bad. Or at least when multiple disks are (now) plugged in, depending on which SATA connectors are in use, a drive may or may not be there, or may be there but at some will hang the computer (out of the blue, & totally). So I'm avoiding those particular connectors, & I believe I'm good, at present.

So some of my issues (seen on home computer) may be hardware related.

Anyhow, this Service issue was not on my home, & I've never see that before.
(Which drive was it that it hung on... was going to say, not sure, don't recall, but thinking, not certain, it was on Kingston - cause SSD (S.M.A.R.T.) reports Unsafe Shutdowns, & I don't think (?) that it incremented? (Or might I have actually Safely Removed after killing GUI, Service, & then restarting both & going through the Index, Pause procedure?)

(Yeah, & I would have gotten around to bring up the Safely Remove issue, at some point, but since I ran into the Service issue...)

KKK, 60K files, 800 GB, .db is only 2 MB:

Code: Select all

Everything:	1.5.0.1383a (x86)
OS:	Windows NT 6.1 7601 (x64)
Admin:	0
Service:	6 (connected / partially installed)
Command line:	-instance KKK -no-auto-include
Binary:	C:\DEV\LOCATE\KKK\Everything.exe
Profile:	C:\DEV\LOCATE\KKK\Everything-KKK.ini
Database:	C:\DEV\LOCATE\KKK\Everything-KKK.db
Instance:	KKK
Config:	match_path=1
Config:	ignore_punctuation=1
Config:	shell_execute_short_parameters=1
Config:	show_mouseover=0
Config:	dupe_group_colors=1
Config:	highlight_max_or_paths=256
Config:	zoom=134
Config:	auto_include_fixed_volumes=0
Config:	auto_remove_offline_ntfs_volumes=0
Config:	auto_move_ntfs_volumes=0
Config:	auto_move_refs_volumes=0
Config:	auto_move_fat_volumes=0
Config:	find_first_file_path_not_found_retry_timeout=30000
Config:	icon_blend_hidden=1
Config:	thumbnail_medium_text_lines=3
Config:	thumbnail_large_text_lines=2
Config:	filelist_context_menu=0
Config:	open_many_files_warning_threshold=9
Config:	set_foreground_window_attach_thread_input=0
Config:	home_sort=1
Config:	snap_toggle_on_shift=1
Config:	rename_overwrite=1
Config:	allow_literal_operators=1
Config:	convert_forward_slash_to_backslash=1
Config:	operator_precedence=1
Config:	size_format=1
Config:	size_number_format=4
Config:	ellipsis=0
Config:	jump_to_timeout=99999
Config:	folder_rescan_timeout=60000
Config:	find_and_select_clear_selection=0
Config:	find_and_select_select_folders=0
Config:	find_and_select_select_files=0
Config:	context_menu_parent_folder=1
Config:	custom_open_command01=$exec("C:\WLIB\PLAYERS\mpv.net\mpvnet.exe" %*)
Config:	custom_open_command02=$exec("C:\BIN\chk.4.EVERYTHING.exe" %*)
Config:	filter=EVERYTHING
Config:	preview_icon=1
Config:	treeview_everything_expand_button=1
Config:	findbar_highlight_all=0
Config:	search_for_text_when_you_start_typing=1
Config:	search_history_always_suggest=1
Config:	columns=[{"name":"Name","width":315},{"name":"Path","width":148},{"name":"Size","width":84},{"name":"Length","width":54},{"name":"Extension","width":36},{"name":"Date Modified","width":112}]
Config:	ntfs_volumes=[{...
Config:	properties=[{"name":"Length","include_only_files":"*.3gp;*.asf;*.asx;*.avi;*.divx;*.f4v;*.flv;*.m2t;*.m2ts;*.m2v;*.m4v;*.mkv;*.mp4;*.mpe;*.mpeg;*.mpg;*.mov;*.mts;*.ogm;*.ogv;*.qt;*.ram;*.rm;*.rmvb;*.smil;*.swf;*.ts;*.vob;*.vp6;*.webm;*.wmv;*.h264;*.srt;*.part","fast_sort":1}]
void
Developer
Posts: 16771
Joined: Fri Oct 16, 2009 11:31 pm

Re: Everything Service 'Hung' Eating CPU

Post by void »

Thank you for the issue report therube,

I am reviewing the service code and what happens when a volume goes offline.

Maybe Everything is getting hung reading some sort of cache over and over on the offline volume..



If you see this issue again, could you please send a mini crash dump of the Everything Service process.
The mini crash dump will show what Everything was doing when it hung.
therube
Posts: 4985
Joined: Thu Sep 03, 2009 6:48 pm

Re: Everything Service 'Hung' Eating CPU

Post by therube »

I've never had issues with Safely Remove.
More recently, yes.
if/when i cannot Safely Remove
ideas on what (else) to try, to look for (prior to using the Pause Updates/Update Indexes "fix") ?


Might System Volume Information &/or $RECYCLE.BIN (if existent) be playing in?
(One drive has $RECYCLE.BIN, but it is empty [save the desktop.ini].
System Volume Information, I've not bothered to enable access to, so not sure what might or might not be there, offhand. But based on Size, which Everything shows, I'd say, not much, 88 & 20,480 bytes ;-))
void
Developer
Posts: 16771
Joined: Fri Oct 16, 2009 11:31 pm

Re: Everything Service 'Hung' Eating CPU

Post by void »

Debug logs would show if Everything receives the removal request:
  • In Everything, from the Tools menu, under the Debug submenu, check Start Debug Logging.
    ---Attempt to remove your device.
  • In Everything, from the Tools menu, under the Debug submenu, click Stop Debug Logging.
    ---Your %TEMP%\Everything Debug Log will open in Notepad.
  • Please reply with the contents of this file.
therube
Posts: 4985
Joined: Thu Sep 03, 2009 6:48 pm

Re: Everything Service 'Hung' Eating CPU

Post by therube »

Code: Select all

Safely Remove (fail)
Safely Remove (fail) (heh, not sure if i did it the 2nd time here?)
sync.exe
sync.exe
sync.exe
Safely Remove (fail) (heh, ditto, i think i did this here?)
Index | Pause Updates
(at which time i heard "disk" activity, as if they were being flushed
- odd, cause no spinner disks are monitored in this instance-KKK)
Index | Update Indexes
Safely Remove (success)

O: drive, the one that wouldn't remove (actually, I didn't try K:,
cause i need that to copy this on to) does have a $Recycle.Bin, in
case that has any bearing & I assume it is set (in Device Manager)
for Quick Removal



2024-11-22 09:27:05.637: disconnected from service
2024-11-22 09:27:05.637: Everything: 1.5.0.1383a (x86)
2024-11-22 09:27:05.637: OS: Windows NT 6.1 7601 (x64)
2024-11-22 09:27:05.637: Admin: 0
2024-11-22 09:27:05.637: Service: 6 (connected / partially installed)
2024-11-22 09:27:05.647: Command line: -instance KKK -no-auto-include
2024-11-22 09:27:05.647: Binary: C:\DEV\Locate\K-DRIVE\Everything.exe
2024-11-22 09:27:05.647: Profile: C:\DEV\Locate\K-DRIVE\Everything-KKK.ini
2024-11-22 09:27:05.647: Database: C:\DEV\Locate\K-DRIVE\Everything-KKK.db
2024-11-22 09:27:05.647: Instance: KKK
2024-11-22 09:27:05.647: Config: match_path=1
2024-11-22 09:27:05.647: Config: ignore_punctuation=1
2024-11-22 09:27:05.647: Config: shell_execute_short_parameters=1
2024-11-22 09:27:05.647: Config: show_mouseover=0
2024-11-22 09:27:05.647: Config: dupe_group_colors=1
2024-11-22 09:27:05.647: Config: highlight_max_or_paths=256
2024-11-22 09:27:05.647: Config: zoom=134
2024-11-22 09:27:05.647: Config: select_focus_on_lost_selection=1
2024-11-22 09:27:05.647: Config: auto_include_fixed_volumes=0
2024-11-22 09:27:05.647: Config: auto_remove_offline_ntfs_volumes=0
2024-11-22 09:27:05.647: Config: auto_move_ntfs_volumes=0
2024-11-22 09:27:05.647: Config: auto_move_refs_volumes=0
2024-11-22 09:27:05.647: Config: auto_move_fat_volumes=0
2024-11-22 09:27:05.647: Config: find_first_file_path_not_found_retry_timeout=30000
2024-11-22 09:27:05.647: Config: icon_blend_hidden=1
2024-11-22 09:27:05.647: Config: thumbnail_medium_text_lines=3
2024-11-22 09:27:05.647: Config: thumbnail_large_text_lines=2
2024-11-22 09:27:05.647: Config: filelist_context_menu=0
2024-11-22 09:27:05.647: Config: open_many_files_warning_threshold=9
2024-11-22 09:27:05.647: Config: set_foreground_window_attach_thread_input=0
2024-11-22 09:27:05.647: Config: snap_toggle_on_shift=1
2024-11-22 09:27:05.647: Config: rename_overwrite=1
2024-11-22 09:27:05.647: Config: allow_literal_operators=1
2024-11-22 09:27:05.647: Config: convert_forward_slash_to_backslash=1
2024-11-22 09:27:05.647: Config: operator_precedence=1
2024-11-22 09:27:05.647: Config: size_format=1
2024-11-22 09:27:05.647: Config: size_number_format=4
2024-11-22 09:27:05.647: Config: ellipsis=0
2024-11-22 09:27:05.647: Config: jump_to_timeout=99999
2024-11-22 09:27:05.647: Config: folder_rescan_timeout=60000
2024-11-22 09:27:05.647: Config: find_and_select_clear_selection=0
2024-11-22 09:27:05.647: Config: find_and_select_select_folders=0
2024-11-22 09:27:05.647: Config: find_and_select_select_files=0
2024-11-22 09:27:05.647: Config: context_menu_parent_folder=1
2024-11-22 09:27:05.647: Config: custom_open_command01=$exec("C:\WLIB\PLAYERS\mpv.net\mpvnet.exe" %*)
2024-11-22 09:27:05.647: Config: custom_open_command02=$exec("C:\BIN\chk.4.EVERYTHING.exe" %*)
2024-11-22 09:27:05.647: Config: custom_open_command03=$exec("C:\BIN\MI_COMPARE.BAT" %*)
2024-11-22 09:27:05.647: Config: custom_open_command04=$exec("C:\BIN\HEX.exe" %*)
2024-11-22 09:27:05.648: Config: filter=EVERYTHING
2024-11-22 09:27:05.648: Config: preview_icon=1
2024-11-22 09:27:05.648: Config: treeview_everything_expand_button=1
2024-11-22 09:27:05.648: Config: findbar_highlight_all=0
2024-11-22 09:27:05.648: Config: search_for_text_when_you_start_typing=1
2024-11-22 09:27:05.648: Config: search_history_always_suggest=1
2024-11-22 09:27:05.648: Config: columns=[{"name":"Name","width":315},{"name":"Path","width":148},{"name":"Size","width":84},{"name":"Extension","width":36},{"name":"Date Modified","width":112}]
2024-11-22 09:27:05.648: Config: ntfs_volumes=[{"path":"K:","volume_name":"\\\\?\\Volume{...}"},{"path":"O:","volume_name":"\\\\?\\Volume{...}"},{"path":"P:","volume_name":"\\\\?\\Volume{...}"}]
2024-11-22 09:27:11.399: MoveFile:
2024-11-22 09:27:11.399: C:\DEV\Locate\K-DRIVE\Session-KKK.json.tmp
2024-11-22 09:27:11.399: to:
2024-11-22 09:27:11.399: C:\DEV\Locate\K-DRIVE\Session-KKK.json
2024-11-22 09:27:11.739: WM_ACTIVATE 00000000 00000000
2024-11-22 09:27:11.739:  lastfocus 00080320
2024-11-22 09:27:11.739:  current focus 00080320
2024-11-22 09:27:11.739:  current foreground 00010050
2024-11-22 09:27:11.739:  minimized 00000000
2024-11-22 09:27:17.303: WM_DEVICECHANGE 00008001 0019dd80
2024-11-22 09:27:17.315: stop monitor dbh 06554278
2024-11-22 09:27:17.315: stop ntfs monitor 030da3d0
2024-11-22 09:27:17.315: stop ntfs_monitor O: 8 007f0500
2024-11-22 09:27:17.315: stop refs monitor 00000000
2024-11-22 09:27:17.409: WM_DEVICECHANGE 00008002 0019dd80
2024-11-22 09:27:17.409: update m 8 030da3d0
2024-11-22 09:27:17.409: update index O:
2024-11-22 09:27:17.409: USN DATA_OVERWRITE $TxfLog.blf
2024-11-22 09:27:17.409: USN CLOSE DATA_OVERWRITE $TxfLog.blf
2024-11-22 09:27:17.409: USN CLOSE $TxfLog.blf
2024-11-22 09:27:17.409: read usn journal O: in 0.000156 seconds
2024-11-22 09:27:17.429: updated O: in 0.020042 seconds
2024-11-22 09:27:17.429: resume ntfs monitor 8
2024-11-22 09:27:17.429: unable to add ntfs file: $TxfLog.blf: parent 000100000000001d not found
2024-11-22 09:27:17.429: processed 2 usn records in 0.000019 seconds
2024-11-22 09:27:17.429: DB_WAIT: _db_monitor_finished_process_fd_update_events_event_proc waiting for _db_monitor_ntfs_process_fd_update_events_thread_proc...
2024-11-22 09:27:17.429: DB_WAIT: _db_monitor_finished_process_fd_update_events_event_proc waited 0.000014 seconds
2024-11-22 09:27:19.429: WM_ACTIVATE 00000001 00000000
2024-11-22 09:27:19.429:  lastfocus 00080320
2024-11-22 09:27:19.429:  current focus 00000000
2024-11-22 09:27:19.429:  current foreground 000f0386
2024-11-22 09:27:19.429:  minimized 00000000
2024-11-22 09:27:19.429: FOCUS 0 
2024-11-22 09:27:19.429: FOCUS restore 00080320
2024-11-22 09:27:19.430: FOCUS restore 00080320
2024-11-22 09:27:21.590: WM_ACTIVATE 00000000 00000000
2024-11-22 09:27:21.590:  lastfocus 00080320
2024-11-22 09:27:21.590:  current focus 00080320
2024-11-22 09:27:21.590:  current foreground 00010050
2024-11-22 09:27:21.590:  minimized 00000000
2024-11-22 09:27:42.380: WM_DEVICECHANGE 00008001 0019dd80
2024-11-22 09:27:42.380: stop monitor dbh 06554278
2024-11-22 09:27:42.380: stop ntfs monitor 030da3d0
2024-11-22 09:27:42.380: stop ntfs_monitor O: 8 007f0500
2024-11-22 09:27:42.388: stop refs monitor 00000000
2024-11-22 09:27:42.489: WM_DEVICECHANGE 00008002 0019dd80
2024-11-22 09:27:42.489: update m 8 030da3d0
2024-11-22 09:27:42.489: update index O:
2024-11-22 09:27:42.489: USN DATA_OVERWRITE $TxfLog.blf
2024-11-22 09:27:42.489: USN CLOSE DATA_OVERWRITE $TxfLog.blf
2024-11-22 09:27:42.489: USN CLOSE $TxfLog.blf
2024-11-22 09:27:42.489: read usn journal O: in 0.000143 seconds
2024-11-22 09:27:42.509: updated O: in 0.019655 seconds
2024-11-22 09:27:42.509: resume ntfs monitor 8
2024-11-22 09:27:42.509: unable to add ntfs file: $TxfLog.blf: parent 000100000000001d not found
2024-11-22 09:27:42.509: processed 2 usn records in 0.000021 seconds
2024-11-22 09:27:42.509: DB_WAIT: _db_monitor_finished_process_fd_update_events_event_proc waiting for _db_monitor_ntfs_process_fd_update_events_thread_proc...
2024-11-22 09:27:42.509: DB_WAIT: _db_monitor_finished_process_fd_update_events_event_proc waited 0.000017 seconds
2024-11-22 09:27:46.380: WM_ACTIVATE 00000001 00000000
2024-11-22 09:27:46.380:  lastfocus 00080320
2024-11-22 09:27:46.380:  current focus 00000000
2024-11-22 09:27:46.380:  current foreground 000f0386
2024-11-22 09:27:46.380:  minimized 00000000
2024-11-22 09:27:46.380: FOCUS 0 
2024-11-22 09:27:46.380: FOCUS restore 00080320
2024-11-22 09:27:46.380: FOCUS restore 00080320
2024-11-22 09:27:48.369: SYSCOMMAND 0000f095 00c3017d
2024-11-22 09:27:50.059: COMMAND 41804
2024-11-22 09:27:50.059: monitor thread exit
2024-11-22 09:27:50.059: monitor cleanup
2024-11-22 09:27:50.059: service client monitor clear all
2024-11-22 09:27:50.059: service client monitor clear all2 
2024-11-22 09:27:50.059: processed 0 usn records in 0.000001 seconds
2024-11-22 09:27:50.059: service client monitor clear all
2024-11-22 09:27:50.059: service client monitor clear all2 
2024-11-22 09:27:50.060: disconnected from service
2024-11-22 09:27:50.060: RDC START 00000000 0
2024-11-22 09:27:50.060: REMOVE _db_indexed_property_request_available_event_proc
2024-11-22 09:27:50.061: online status changed
2024-11-22 09:27:54.774: SYSCOMMAND 0000f095 00cb0185
2024-11-22 09:27:55.988: COMMAND 41803
2024-11-22 09:27:55.988: index NTFS 0 K: 1 start monitor
2024-11-22 09:27:55.988: index NTFS 0 O: 1 start monitor
2024-11-22 09:27:55.988: index NTFS 0 P: 1 start monitor
2024-11-22 09:27:56.415: start all monitors (ntfs: 3 refs: 0)
2024-11-22 09:27:56.415: open volume \\?\Volume{74142c58-cbd1-11ed-b7e1-bc5ff444bb7d}
2024-11-22 09:27:56.416: opened 00000290 0.001342
2024-11-22 09:27:56.416: RegisterDeviceNotification volume_handle 00000290
2024-11-22 09:27:56.417: ntfs monitor 065d63f0 00000000 ffffffff
2024-11-22 09:27:56.417: open volume \\?\Volume{3791a45a-a3db-4c8f-8b9d-ed59b5d6e0a7}
2024-11-22 09:27:56.417: opened 00000290 0.000137
2024-11-22 09:27:56.417: RegisterDeviceNotification volume_handle 00000290
2024-11-22 09:27:56.417: ntfs monitor 065d6410 00000000 ffffffff
2024-11-22 09:27:56.417: open volume \\?\Volume{5325feeb-54b4-11ef-96ae-bc5ff444bb7d}
2024-11-22 09:27:56.417: GetVolumeInformationW \\?\Volume{5325feeb-54b4-11ef-96ae-bc5ff444bb7d} 3
2024-11-22 09:27:56.417: opened ffffffff 0.000049
2024-11-22 09:27:56.417: RegisterDeviceNotification volume_handle ffffffff
2024-11-22 09:27:56.417: open volume \\?\Volume{5325feeb-54b4-11ef-96ae-bc5ff444bb7d}
2024-11-22 09:27:56.417: GetVolumeInformationW \\?\Volume{5325feeb-54b4-11ef-96ae-bc5ff444bb7d} 3
2024-11-22 09:27:56.417: opened ffffffff 0.000039
2024-11-22 09:27:56.417: RegisterDeviceNotification service_volume_handle ffffffff
2024-11-22 09:27:56.417: ntfs service monitor 00000000 00000000 ffffffff 0
2024-11-22 09:27:56.417: ntfs monitor 00000000 00000000 ffffffff
2024-11-22 09:27:56.417: RDC START 00000000 0
2024-11-22 09:27:56.417: service monitor offline m 0 030da388
2024-11-22 09:27:56.418: check for folder updates 00000000
2024-11-22 09:27:56.418: _db_indexed_property_request_available_event_proc 0
2024-11-22 09:27:56.418: open volume \\?\Volume{74142c58-cbd1-11ed-b7e1-bc5ff444bb7d}
2024-11-22 09:27:56.419: opened 000002b4 0.001159
2024-11-22 09:27:56.419: open volume \\?\Volume{3791a45a-a3db-4c8f-8b9d-ed59b5d6e0a7}
2024-11-22 09:27:56.419: opened 00000638 0.000112
2024-11-22 09:27:56.419: online status changed
2024-11-22 09:27:59.128: WM_ACTIVATE 00000000 00000000
2024-11-22 09:27:59.128:  lastfocus 00080320
2024-11-22 09:27:59.128:  current focus 00080320
2024-11-22 09:27:59.128:  current foreground 00010050
2024-11-22 09:27:59.128:  minimized 00000000
2024-11-22 09:28:03.474: WM_DEVICECHANGE 00008001 0019dd80
2024-11-22 09:28:03.474: stop monitor dbh 065d6410
2024-11-22 09:28:03.474: stop ntfs monitor 065d4a68
2024-11-22 09:28:03.474: stop ntfs_monitor O: 4294967295 007f04d8
2024-11-22 09:28:03.475: monitor thread exit
2024-11-22 09:28:03.475: monitor cleanup
2024-11-22 09:28:03.475: start all monitors (ntfs: 3 refs: 0)
2024-11-22 09:28:03.475: ntfs monitor 065d63f0 00000000 ffffffff
2024-11-22 09:28:03.475: ntfs monitor 065d6410 00000000 ffffffff
2024-11-22 09:28:03.475: open volume \\?\Volume{5325feeb-54b4-11ef-96ae-bc5ff444bb7d}
2024-11-22 09:28:03.475: GetVolumeInformationW \\?\Volume{5325feeb-54b4-11ef-96ae-bc5ff444bb7d} 3
2024-11-22 09:28:03.475: opened ffffffff 0.000053
2024-11-22 09:28:03.475: RegisterDeviceNotification volume_handle ffffffff
2024-11-22 09:28:03.475: open volume \\?\Volume{5325feeb-54b4-11ef-96ae-bc5ff444bb7d}
2024-11-22 09:28:03.475: GetVolumeInformationW \\?\Volume{5325feeb-54b4-11ef-96ae-bc5ff444bb7d} 3
2024-11-22 09:28:03.475: opened ffffffff 0.000039
2024-11-22 09:28:03.475: RegisterDeviceNotification service_volume_handle ffffffff
2024-11-22 09:28:03.475: ntfs service monitor 00000000 00000000 ffffffff 1
2024-11-22 09:28:03.475: ntfs monitor 00000000 00000000 ffffffff
2024-11-22 09:28:03.475: stop refs monitor 00000000
2024-11-22 09:28:03.475: service monitor offline m 1 030da388
2024-11-22 09:28:03.475: open volume \\?\Volume{74142c58-cbd1-11ed-b7e1-bc5ff444bb7d}
2024-11-22 09:28:03.475: online status changed
2024-11-22 09:28:03.476: opened 000002e8 0.001102
2024-11-22 09:28:03.476: online status changed
2024-11-22 09:28:03.618: WM_DEVICECHANGE 00008003 0019dd80
2024-11-22 09:28:03.618: dbch_devicetype 6, dbch_size 44
2024-11-22 09:28:03.618: stop monitor dbh 065d6410
2024-11-22 09:28:03.618: stop ntfs monitor 065d4a68
2024-11-22 09:28:03.618: stop ntfs_monitor O: 4294967295 007f07a8
2024-11-22 09:28:03.618: monitor thread exit
2024-11-22 09:28:03.618: monitor cleanup
2024-11-22 09:28:03.618: start all monitors (ntfs: 3 refs: 0)
2024-11-22 09:28:03.618: ntfs monitor 065d63f0 00000000 ffffffff
2024-11-22 09:28:03.618: ntfs monitor 065d6410 00000000 ffffffff
2024-11-22 09:28:03.618: open volume \\?\Volume{5325feeb-54b4-11ef-96ae-bc5ff444bb7d}
2024-11-22 09:28:03.618: GetVolumeInformationW \\?\Volume{5325feeb-54b4-11ef-96ae-bc5ff444bb7d} 3
2024-11-22 09:28:03.618: opened ffffffff 0.000029
2024-11-22 09:28:03.618: RegisterDeviceNotification volume_handle ffffffff
2024-11-22 09:28:03.618: open volume \\?\Volume{5325feeb-54b4-11ef-96ae-bc5ff444bb7d}
2024-11-22 09:28:03.618: GetVolumeInformationW \\?\Volume{5325feeb-54b4-11ef-96ae-bc5ff444bb7d} 3
2024-11-22 09:28:03.619: opened ffffffff 0.000018
2024-11-22 09:28:03.619: RegisterDeviceNotification service_volume_handle ffffffff
2024-11-22 09:28:03.619: ntfs service monitor 00000000 00000000 ffffffff 2
2024-11-22 09:28:03.619: ntfs monitor 00000000 00000000 ffffffff
2024-11-22 09:28:03.619: stop refs monitor 00000000
2024-11-22 09:28:03.619: service monitor offline m 2 030da388
2024-11-22 09:28:03.619: open volume \\?\Volume{74142c58-cbd1-11ed-b7e1-bc5ff444bb7d}
2024-11-22 09:28:03.619: online status changed
2024-11-22 09:28:03.620: opened 00000638 0.000991
2024-11-22 09:28:03.621: WM_DEVICECHANGE 00000007 00000000
2024-11-22 09:28:03.621: online status changed
2024-11-22 09:28:03.701: WM_DEVICECHANGE 00008004 0019df20
2024-11-22 09:28:03.701: dbch_devicetype 2, dbch_size 20
2024-11-22 09:28:03.701: unregister_device_notification dbv 00004000
2024-11-22 09:28:03.701: unregister_device_notification volume 065d4a68
2024-11-22 09:28:03.701: stop ntfs_monitor O: 4294967295 007f0370
2024-11-22 09:28:03.701: monitor thread exit
2024-11-22 09:28:03.701: monitor cleanup
2024-11-22 09:28:03.701: start all monitors (ntfs: 3 refs: 0)
2024-11-22 09:28:03.701: ntfs monitor 065d63f0 00000000 ffffffff
2024-11-22 09:28:03.701: ntfs monitor 065d6410 00000000 ffffffff
2024-11-22 09:28:03.701: open volume \\?\Volume{5325feeb-54b4-11ef-96ae-bc5ff444bb7d}
2024-11-22 09:28:03.701: GetVolumeInformationW \\?\Volume{5325feeb-54b4-11ef-96ae-bc5ff444bb7d} 3
2024-11-22 09:28:03.701: opened ffffffff 0.000028
2024-11-22 09:28:03.701: RegisterDeviceNotification volume_handle ffffffff
2024-11-22 09:28:03.701: open volume \\?\Volume{5325feeb-54b4-11ef-96ae-bc5ff444bb7d}
2024-11-22 09:28:03.701: GetVolumeInformationW \\?\Volume{5325feeb-54b4-11ef-96ae-bc5ff444bb7d} 3
2024-11-22 09:28:03.701: opened ffffffff 0.000017
2024-11-22 09:28:03.701: RegisterDeviceNotification service_volume_handle ffffffff
2024-11-22 09:28:03.701: ntfs service monitor 00000000 00000000 ffffffff 3
2024-11-22 09:28:03.701: ntfs monitor 00000000 00000000 ffffffff
2024-11-22 09:28:03.701: service monitor offline m 3 030da388
2024-11-22 09:28:03.701: open volume \\?\Volume{74142c58-cbd1-11ed-b7e1-bc5ff444bb7d}
2024-11-22 09:28:03.701: online status changed
2024-11-22 09:28:03.702: opened 000002e8 0.000787
2024-11-22 09:28:03.702: open volume \\?\Volume{3791a45a-a3db-4c8f-8b9d-ed59b5d6e0a7}
2024-11-22 09:28:03.702: online status changed
2024-11-22 09:28:03.702: GetVolumeInformationW \\?\Volume{3791a45a-a3db-4c8f-8b9d-ed59b5d6e0a7} 3
2024-11-22 09:28:03.702: opened ffffffff 0.000031
2024-11-22 09:28:03.702: ntfs monitor read error 3 retrying in 30 seconds...
2024-11-22 09:28:03.702: online status changed
2024-11-22 09:28:03.739: WM_DEVICECHANGE 00000007 00000000
2024-11-22 09:28:03.745: WM_DEVICECHANGE 00000007 00000000
2024-11-22 09:28:03.747: WM_DEVICECHANGE 00000007 00000000
2024-11-22 09:28:03.748: WM_DEVICECHANGE 00000007 00000000
2024-11-22 09:28:04.250: SHCNE 00000080 O:\ 
2024-11-22 09:28:04.251: SHCNE 00001000 Computer 
2024-11-22 09:28:06.113: WM_ACTIVATE 00000001 00000000
2024-11-22 09:28:06.113:  lastfocus 00080320
2024-11-22 09:28:06.113:  current focus 00000000
2024-11-22 09:28:06.113:  current foreground 000f0386
2024-11-22 09:28:06.113:  minimized 00000000
2024-11-22 09:28:06.113: FOCUS 0 
2024-11-22 09:28:06.113: FOCUS restore 00080320
2024-11-22 09:28:06.113: FOCUS restore 00080320
2024-11-22 09:28:06.114: SYSCOMMAND 0000f095 00c8020f
2024-11-22 09:28:06.622: Check for volume change.
2024-11-22 09:28:06.622: is rebuild required
2024-11-22 09:28:06.622: config ntfs volume: \\?\Volume{f3fc665b-d4e6-4a51-a1b7-09c64c792a24} | C: |  | 0 | 0
2024-11-22 09:28:06.622: add volume: 1 | \\?\Volume{f3fc665b-d4e6-4a51-a1b7-09c64c792a24} | FLAME96C8 (C:) |  | 0 | 0
2024-11-22 09:28:06.622: config ntfs volume: \\?\Volume{71b6901a-0343-45fb-8ba4-7713ca54f116} | E: |  | 0 | 0
2024-11-22 09:28:06.622: add volume: 1 | \\?\Volume{71b6901a-0343-45fb-8ba4-7713ca54f116} | E-WIN7-X64 (E:) |  | 0 | 0
2024-11-22 09:28:06.622: config ntfs volume: \\?\Volume{d5872c50-1cee-11e8-b2e6-806e6f6e6963} | H: |  | 0 | 0
2024-11-22 09:28:06.622: add volume: 1 | \\?\Volume{d5872c50-1cee-11e8-b2e6-806e6f6e6963} | HIT2G (H:) |  | 0 | 0
2024-11-22 09:28:06.622: config ntfs volume: \\?\Volume{bbc7e66f-74de-4147-a8a9-5139169e8464} | I: |  | 0 | 0
2024-11-22 09:28:06.622: add volume: 1 | \\?\Volume{bbc7e66f-74de-4147-a8a9-5139169e8464} | HIT4TB (I:) |  | 0 | 0
2024-11-22 09:28:06.622: config ntfs volume: \\?\Volume{74142c58-cbd1-11ed-b7e1-bc5ff444bb7d} | K: |  | 1 | 0
2024-11-22 09:28:06.622: add volume: 1 | \\?\Volume{74142c58-cbd1-11ed-b7e1-bc5ff444bb7d} | KINGSTON-DTX-128 (K:) |  | 1 | 0
2024-11-22 09:28:06.622: config ntfs volume: \\?\Volume{e0785845-0ef4-11e9-aaf4-bc5ff444bb7d} | K: |  | 0 | 0
2024-11-22 09:28:06.622: add volume: 1 | \\?\Volume{e0785845-0ef4-11e9-aaf4-bc5ff444bb7d} | Win10-ISO (K:) |  | 0 | 0
2024-11-22 09:28:06.622: config ntfs volume: \\?\Volume{bb960cf1-bbda-44fd-857d-3a83d8b46a3a} | L: |  | 0 | 0
2024-11-22 09:28:06.622: add volume: 1 | \\?\Volume{bb960cf1-bbda-44fd-857d-3a83d8b46a3a} | LIB (L:) |  | 0 | 0
2024-11-22 09:28:06.622: config ntfs volume: \\?\Volume{901e4abd-4f33-4ddf-b4ed-fc757594da94} | M: |  | 0 | 0
2024-11-22 09:28:06.622: add volume: 1 | \\?\Volume{901e4abd-4f33-4ddf-b4ed-fc757594da94} | MUSIC (M:) |  | 0 | 0
2024-11-22 09:28:06.622: config ntfs volume: \\?\Volume{3791a45a-a3db-4c8f-8b9d-ed59b5d6e0a7} | O: |  | 1 | 0
2024-11-22 09:28:06.622: add volume: 1 | \\?\Volume{3791a45a-a3db-4c8f-8b9d-ed59b5d6e0a7} | MSI2TBSSD (O:) |  | 1 | 0
2024-11-22 09:28:06.622: config ntfs volume: \\?\Volume{5325feeb-54b4-11ef-96ae-bc5ff444bb7d} | P: |  | 1 | 0
2024-11-22 09:28:06.622: add volume: 1 | \\?\Volume{5325feeb-54b4-11ef-96ae-bc5ff444bb7d} | USB20FD (P:) |  | 1 | 0
2024-11-22 09:28:06.622: config ntfs volume: \\?\Volume{4175fac7-af2d-4d59-ba44-40d21d415d94} | T: |  | 0 | 0
2024-11-22 09:28:06.622: add volume: 1 | \\?\Volume{4175fac7-af2d-4d59-ba44-40d21d415d94} | TOSH_8TB (T:) |  | 0 | 0
2024-11-22 09:28:06.622: config ntfs volume: \\?\Volume{a1b6dc51-91c6-4659-a7b9-2796ba3da1c3} | V: |  | 0 | 0
2024-11-22 09:28:06.622: add volume: 1 | \\?\Volume{a1b6dc51-91c6-4659-a7b9-2796ba3da1c3} |  (V:) |  | 0 | 0
2024-11-22 09:28:06.622: config ntfs volume: \\?\Volume{678c4cca-6de6-43d3-a3e0-41c94e744371} | W: |  | 0 | 0
2024-11-22 09:28:06.622: add volume: 1 | \\?\Volume{678c4cca-6de6-43d3-a3e0-41c94e744371} | easystore (W:) |  | 0 | 0
2024-11-22 09:28:06.622: config ntfs volume: \\?\Volume{acc08045-efee-4c63-9621-aec9ea04d92e} | Y: |  | 0 | 0
2024-11-22 09:28:06.622: add volume: 1 | \\?\Volume{acc08045-efee-4c63-9621-aec9ea04d92e} | Y-NOT26 (Y:) |  | 0 | 0
2024-11-22 09:28:06.622: VEH 066f1218
2024-11-22 09:28:06.622: volume \\?\Volume{f3fc665b-d4e6-4a51-a1b7-09c64c792a24}: drive type 3
2024-11-22 09:28:06.622: GetVolumePathNamesForVolumeName 234
2024-11-22 09:28:06.622: GetVolumePathNamesForVolumeName OK C:\
2024-11-22 09:28:06.622: GetVolumePathNamesForVolumeName C:
2024-11-22 09:28:06.622: ignoring new excluded volume 3 \\?\Volume{f3fc665b-d4e6-4a51-a1b7-09c64c792a24} C: 
2024-11-22 09:28:06.622: volume \\?\Volume{71b6901a-0343-45fb-8ba4-7713ca54f116}: drive type 3
2024-11-22 09:28:06.623: GetVolumePathNamesForVolumeName 234
2024-11-22 09:28:06.623: GetVolumePathNamesForVolumeName OK E:\
2024-11-22 09:28:06.623: GetVolumePathNamesForVolumeName E:
2024-11-22 09:28:06.623: ignoring new excluded volume 3 \\?\Volume{71b6901a-0343-45fb-8ba4-7713ca54f116} E: 
2024-11-22 09:28:06.623: volume \\?\Volume{901e4abd-4f33-4ddf-b4ed-fc757594da94}: drive type 3
2024-11-22 09:28:06.623: GetVolumePathNamesForVolumeName 234
2024-11-22 09:28:06.623: GetVolumePathNamesForVolumeName OK M:\
2024-11-22 09:28:06.623: GetVolumePathNamesForVolumeName M:
2024-11-22 09:28:06.623: ignoring new excluded volume 3 \\?\Volume{901e4abd-4f33-4ddf-b4ed-fc757594da94} M: 
2024-11-22 09:28:06.623: volume \\?\Volume{bb960cf1-bbda-44fd-857d-3a83d8b46a3a}: drive type 3
2024-11-22 09:28:06.623: GetVolumePathNamesForVolumeName 234
2024-11-22 09:28:06.623: GetVolumePathNamesForVolumeName OK L:\
2024-11-22 09:28:06.623: GetVolumePathNamesForVolumeName L:
2024-11-22 09:28:06.623: ignoring new excluded volume 3 \\?\Volume{bb960cf1-bbda-44fd-857d-3a83d8b46a3a} L: 
2024-11-22 09:28:06.623: volume \\?\Volume{acc08045-efee-4c63-9621-aec9ea04d92e}: drive type 3
2024-11-22 09:28:06.623: GetVolumePathNamesForVolumeName 234
2024-11-22 09:28:06.623: GetVolumePathNamesForVolumeName OK Y:\
2024-11-22 09:28:06.623: GetVolumePathNamesForVolumeName Y:
2024-11-22 09:28:06.623: ignoring new excluded volume 3 \\?\Volume{acc08045-efee-4c63-9621-aec9ea04d92e} Y: 
2024-11-22 09:28:06.623: volume \\?\Volume{a1b6dc51-91c6-4659-a7b9-2796ba3da1c3}: drive type 3
2024-11-22 09:28:06.623: GetVolumePathNamesForVolumeName 234
2024-11-22 09:28:06.623: GetVolumePathNamesForVolumeName OK V:\
2024-11-22 09:28:06.624: GetVolumePathNamesForVolumeName V:
2024-11-22 09:28:06.624: ignoring new excluded volume 3 \\?\Volume{a1b6dc51-91c6-4659-a7b9-2796ba3da1c3} V: 
2024-11-22 09:28:06.624: volume \\?\Volume{4175fac7-af2d-4d59-ba44-40d21d415d94}: drive type 3
2024-11-22 09:28:06.624: GetVolumePathNamesForVolumeName 234
2024-11-22 09:28:06.624: GetVolumePathNamesForVolumeName OK T:\
2024-11-22 09:28:06.624: GetVolumePathNamesForVolumeName T:
2024-11-22 09:28:06.624: ignoring new excluded volume 3 \\?\Volume{4175fac7-af2d-4d59-ba44-40d21d415d94} T: 
2024-11-22 09:28:06.624: volume \\?\Volume{c81673bb-5d07-42a4-81ab-bd601c5ecf5d}: drive type 3
2024-11-22 09:28:06.624: GetVolumePathNamesForVolumeName 234
2024-11-22 09:28:06.624: GetVolumePathNamesForVolumeName OK S:\
2024-11-22 09:28:06.624: GetVolumePathNamesForVolumeName S:
2024-11-22 09:28:06.624: found volume 3 \\?\Volume{c81673bb-5d07-42a4-81ab-bd601c5ecf5d} S: 
2024-11-22 09:28:06.624: check media \\?\Volume{c81673bb-5d07-42a4-81ab-bd601c5ecf5d}
2024-11-22 09:28:06.624: add found volume: 1 | \\?\Volume{c81673bb-5d07-42a4-81ab-bd601c5ecf5d} | S: |  | 1
2024-11-22 09:28:06.624: existing volume: 00000000
2024-11-22 09:28:06.624: add new found volume: 1 | \\?\Volume{c81673bb-5d07-42a4-81ab-bd601c5ecf5d} | S: |  | 0
2024-11-22 09:28:06.624: add volume: 1 | \\?\Volume{c81673bb-5d07-42a4-81ab-bd601c5ecf5d} | SEAGATE-EXOS-8TB (S:) |  | 0 | 0
2024-11-22 09:28:06.624: volume \\?\Volume{678c4cca-6de6-43d3-a3e0-41c94e744371}: drive type 3
2024-11-22 09:28:06.624: GetVolumePathNamesForVolumeName 234
2024-11-22 09:28:06.624: GetVolumePathNamesForVolumeName OK W:\
2024-11-22 09:28:06.624: GetVolumePathNamesForVolumeName W:
2024-11-22 09:28:06.624: ignoring new excluded volume 3 \\?\Volume{678c4cca-6de6-43d3-a3e0-41c94e744371} W: 
2024-11-22 09:28:06.624: volume \\?\Volume{74142c58-cbd1-11ed-b7e1-bc5ff444bb7d}: drive type 2
2024-11-22 09:28:06.624: GetVolumePathNamesForVolumeName 234
2024-11-22 09:28:06.625: GetVolumePathNamesForVolumeName OK K:\
2024-11-22 09:28:06.625: GetVolumePathNamesForVolumeName K:
2024-11-22 09:28:06.625: K:
2024-11-22 09:28:06.625: QueryDosDevice K: \Device\HarddiskVolume59
2024-11-22 09:28:06.625: dos device \Device\HarddiskVolume59
2024-11-22 09:28:06.625: found volume 2 \\?\Volume{74142c58-cbd1-11ed-b7e1-bc5ff444bb7d} K: 
2024-11-22 09:28:06.625: check media \\?\Volume{74142c58-cbd1-11ed-b7e1-bc5ff444bb7d}
2024-11-22 09:28:06.625: add found volume: 1 | \\?\Volume{74142c58-cbd1-11ed-b7e1-bc5ff444bb7d} | K: |  | 1
2024-11-22 09:28:06.625: existing volume: 064f7b90
2024-11-22 09:28:06.626: VOLUME \\?\Volume{f3fc665b-d4e6-4a51-a1b7-09c64c792a24} C:  0 0 1 0 0 1 3
2024-11-22 09:28:06.626: VOLUME \\?\Volume{71b6901a-0343-45fb-8ba4-7713ca54f116} E:  0 0 1 0 0 1 3
2024-11-22 09:28:06.626: VOLUME \\?\Volume{d5872c50-1cee-11e8-b2e6-806e6f6e6963} H:  0 0 1 0 0 1 3
2024-11-22 09:28:06.626: VOLUME \\?\Volume{bbc7e66f-74de-4147-a8a9-5139169e8464} I:  0 0 1 0 0 1 3
2024-11-22 09:28:06.626: VOLUME \\?\Volume{74142c58-cbd1-11ed-b7e1-bc5ff444bb7d} K:  1 0 1 0 1 1 2
2024-11-22 09:28:06.626: VOLUME \\?\Volume{e0785845-0ef4-11e9-aaf4-bc5ff444bb7d} K:  0 0 1 0 0 1 2
2024-11-22 09:28:06.626: VOLUME \\?\Volume{bb960cf1-bbda-44fd-857d-3a83d8b46a3a} L:  0 0 1 0 0 1 3
2024-11-22 09:28:06.626: VOLUME \\?\Volume{901e4abd-4f33-4ddf-b4ed-fc757594da94} M:  0 0 1 0 0 1 3
2024-11-22 09:28:06.626: VOLUME \\?\Volume{3791a45a-a3db-4c8f-8b9d-ed59b5d6e0a7} O:  1 0 1 0 0 1 3
2024-11-22 09:28:06.626: VOLUME \\?\Volume{5325feeb-54b4-11ef-96ae-bc5ff444bb7d} P:  1 0 1 0 0 1 2
2024-11-22 09:28:06.626: VOLUME \\?\Volume{c81673bb-5d07-42a4-81ab-bd601c5ecf5d} S:  0 0 1 0 1 1 3
2024-11-22 09:28:06.626: VOLUME \\?\Volume{4175fac7-af2d-4d59-ba44-40d21d415d94} T:  0 0 1 0 0 1 3
2024-11-22 09:28:06.626: VOLUME \\?\Volume{a1b6dc51-91c6-4659-a7b9-2796ba3da1c3} V:  0 0 1 0 0 1 3
2024-11-22 09:28:06.626: VOLUME \\?\Volume{678c4cca-6de6-43d3-a3e0-41c94e744371} W:  0 0 1 0 0 1 3
2024-11-22 09:28:06.626: VOLUME \\?\Volume{acc08045-efee-4c63-9621-aec9ea04d92e} Y:  0 0 1 0 0 1 3
2024-11-22 09:28:06.626: volume list created in 0.004080 seconds
2024-11-22 09:28:06.626: refs volume list count cur: 0 db: 0
2024-11-22 09:28:06.626: update register device notify (ntfs: 3 refs: 0)
2024-11-22 09:28:06.626: open volume \\?\Volume{3791a45a-a3db-4c8f-8b9d-ed59b5d6e0a7}
2024-11-22 09:28:06.626: GetVolumeInformationW \\?\Volume{3791a45a-a3db-4c8f-8b9d-ed59b5d6e0a7} 3
2024-11-22 09:28:06.626: opened ffffffff 0.000044
2024-11-22 09:28:06.626: open volume \\?\Volume{3791a45a-a3db-4c8f-8b9d-ed59b5d6e0a7}
2024-11-22 09:28:06.626: GetVolumeInformationW \\?\Volume{3791a45a-a3db-4c8f-8b9d-ed59b5d6e0a7} 3
2024-11-22 09:28:06.626: opened ffffffff 0.000039
2024-11-22 09:28:06.626: open volume \\?\Volume{5325feeb-54b4-11ef-96ae-bc5ff444bb7d}
2024-11-22 09:28:06.626: GetVolumeInformationW \\?\Volume{5325feeb-54b4-11ef-96ae-bc5ff444bb7d} 3
2024-11-22 09:28:06.626: opened ffffffff 0.000040
2024-11-22 09:28:06.626: open volume \\?\Volume{5325feeb-54b4-11ef-96ae-bc5ff444bb7d}
2024-11-22 09:28:06.626: GetVolumeInformationW \\?\Volume{5325feeb-54b4-11ef-96ae-bc5ff444bb7d} 3
2024-11-22 09:28:06.626: opened ffffffff 0.000038
2024-11-22 09:28:09.146: COMMAND 40209
2024-11-22 09:28:10.728: SYSCOMMAND 0000f095 00c6021b
2024-11-22 09:28:12.933: COMMAND 40210
therube
Posts: 4985
Joined: Thu Sep 03, 2009 6:48 pm

Re: Everything Service 'Hung' Eating CPU

Post by therube »

This was from the other day, & I couldn't Safely Remove - at all - even after having closed Everything (-instance KKK, only).
I saw that Handle to O:, & I thought, ah..., but seems ? that might not be out of the ordinary (as in checking just before a Safely Remove - that did work, I also saw Handle to O:).

And again, can't rule out hardware issues (at least partially playing in, sometimes)?
.
Everything - could NOT Safely Remove O - even AFTER closing E-KKK.png
Everything - could NOT Safely Remove O - even AFTER closing E-KKK.png (510.98 KiB) Viewed 365 times
void
Developer
Posts: 16771
Joined: Fri Oct 16, 2009 11:31 pm

Re: Everything Service 'Hung' Eating CPU

Post by void »

Thank you for the logs.
2024-11-22 09:27:17.303: WM_DEVICECHANGE 00008001 0019dd80
2024-11-22 09:27:17.315: stop monitor dbh 06554278
2024-11-22 09:27:17.315: stop ntfs monitor 030da3d0
2024-11-22 09:27:17.315: stop ntfs_monitor O: 8 007f0500
2024-11-22 09:27:17.315: stop refs monitor 00000000
2024-11-22 09:27:17.409: WM_DEVICECHANGE 00008002 0019dd80
Everything does not monitor system volumes for device changes.

I wonder why Windows is treating this O: drive as a system drive.
Is there a page file on this drive? are you using the drive for quick boot?



I am working on adding support for monitoring system volumes for device changes..
void
Developer
Posts: 16771
Joined: Fri Oct 16, 2009 11:31 pm

Re: Everything Service 'Hung' Eating CPU

Post by void »

After working on this...
2024-11-22 09:27:17.315: stop ntfs_monitor O: 8 007f0500
The Everything client is sending a request to the Everything Service to stop monitoring your O: drive.
The stop is successful. (server returns with no error)
2024-11-22 09:27:17.409: WM_DEVICECHANGE 00008002 0019dd80
The system immediately fails the device removal.
Something is still holding an open handle..



If you can reproduce the issue, could you please send the Everything Service verbose debug logs:
  • Plug in your device.
  • In Everything, Hold down Shift, from the Tools menu, under the Debug submenu, check Service verbose.
  • Hold down Shift, from the Tools menu, under the Debug submenu, click Start Service Debug Logging...
  • Attempt to remove your device.
  • Hold down Shift, from the Tools menu, under the Debug submenu, click Stop Service Debug Logging...
    Open your C:\Windows\Temp\Everything Service Debug Log-1.5a.txt
  • Please reply with the contents of the file.
The log will show if the Everything Service has closed all handles...
I'm wondering if there's a stale client with an open handle.



Please make sure you are using the latest version of Everything for your service.
Client requests to stop monitoring was only recently added.
therube
Posts: 4985
Joined: Thu Sep 03, 2009 6:48 pm

Re: Everything Service 'Hung' Eating CPU

Post by therube »

I wonder why Windows is treating this O: drive as a system drive.
Is there a page file on this drive? are you using the drive for quick boot?
No & No.

It is a M2 SSD, in a housing like, M.2 SATA SSD Enclosure Reader (though I believe mine does both NVMe [that is what's in there] & also SATA).
Please make sure you are using the latest version of Everything for your service.
Pretty sure it will be 1383 (& x86 at that), but I'll check.


(In the meantime...
So this morning, when it would not Safely Remove...

I specifically first attempted SR while I was creating a backup, so some fairly heavy I/O & CPU usage, & it failed.
After backup done, I threw in a few sync's, to no avail, & then Pause Updates - which I expected to work, but that also did not.
So then I figured that Quitting Everything (GUI) -instance KKK would also fail to help, but it did, I was able to Safely Remove.)
void
Developer
Posts: 16771
Joined: Fri Oct 16, 2009 11:31 pm

Re: Everything Service 'Hung' Eating CPU

Post by void »

I have a similar drive.

One issue I ran into was an old stale FAT index using the same volume name and drive letter.
Everything will hold a handle open to this volume.
Please check for any volumes under Tools -> Options -> FAT that are using the same drive letter as your NTFS volume that cannot be removed.
-If there are any, please click Remove.
Please also check ReFS, Network drives and Folders.
therube
Posts: 4985
Joined: Thu Sep 03, 2009 6:48 pm

Re: Everything Service 'Hung' Eating CPU

Post by therube »

Everything Service Debug Logs.


Service (version) IS 1383.

I'm not getting a Service Debug Log (I even searched for it with Everything ;-))?
1383 x86, using named instance (all my instances are self-named)

x64, i only had 1340 x64 on hand, so i ran that with default name (1.5)
(in case x64 or 1.5 [name] mattered)
& still no SDL
(though that assumes that SDL existed in 1340, March 2023)

(anyhow, even though i didn't get a SDL, i also didn't run into the problem again - yet :evilgrin:)

Service itself is ambidextrous, working with both x86 & x64 GUI's,
but is the Service the same in x86 & x64? (Or is there even a concept of such a thing?)
(I tried uninstall-service x86, then install x64 - oh, that's not going to matter as 1340 is too
old anyhow.)
so... i'm out of ideas (without a 1383 x64 to test [now downloading...])

---
1383 x64 & still not seeing it (SDL)?
OK, I'm blind (or I was doing it wrong, or ?).
So SDL is there in 1383 - the menu items.
It's been there since 1357.

But...

Oh.
Now that I actually have SDL enabled, I see it wrote to
E:\Windows\Temp\Everything Service Debug Log-1.5a.txt

And while E: is my system drive, it is not my %TMP% drive.
C:\>echo %tmp%
C:\Local\RUBEN7\Temp

OK, now that that's all settled, all I need to do is to not Safely Remove.


(Heh. I don't have access to, E:\Windows\Temp\ - now I do.)
therube
Posts: 4985
Joined: Thu Sep 03, 2009 6:48 pm

Re: Everything Service 'Hung' Eating CPU

Post by therube »

One issue I ran into was an old stale FAT index using the same volume name and drive letter. ...
Pretty sure FAT will be empty.

Pretty sure NTFS will have some dup'd drive letters, with some marked as (Offline)
(that I've just left hang around).

Though the particular drive I most often have trouble with is O:, & that is a letter I'd not used before.

There might be a Network Index (G:) displaying, but not Included/Indexed.
Post Reply