MQ goes into endless unproductive state at cycle 98 in MSMS_first search

[EgonBechHansen]

Describe the bug
MQ goes into endless unproductive state at cycle 98 in MSMS_first search
I am using a Windows labtop:
Edition Windows 10 Enterprise
Version 22H2
Installed on ‎24-‎05-‎2022
OS build 19045.3930
Experience Windows Feature Experience Pack 1000.19053.1000.0

Device name DTU-CND212408M
Full device name DTU-CND212408M.win.dtu.dk
Processor 11th Gen Intel(R) Core(TM) i7-11850H @ 2.50GHz 2.50 GHz
Installed RAM 32,0 GB (31,7 GB usable)
Device ID CCF460AF-721B-4AC7-BF69-059A7CBD10EA
Product ID 00329-00000-00003-AA072
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display

With 16 cores.

I was using on a set of 37 raw files and running
MaxQuant 2.4.0.0 with parameters previously used for similar files. I was using 14 cores.
The start is normal but progress stops in cycle 98 in MSMS_first search on the first set of 14 files.
The program does not crash it just goes idle producing no progress and the load on CPUs goes down from 100% tp close to 0.
Each CPU seems to go idle when a file reach cycle 98. It does not happen simultaneously
, but gradually when each file reach 98.

I then upgraded to the latest version of MQ 2.4.13.0
It gave exactly the same problem.
Also when running MQ as administrator.
I attach a set of screen shots.
I have been running MQ several months ago without any problems, and I had not upgraded MQ before yesterday. I therefore suspect the bug to arise due to a change in our windows environment.
Can there be a problem with just the number 98?

Best regards
Egon

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

[JurgenCox]

98 files is not a big number, so that should not be the reason. Can you reproduce the problem with just a few raw files, maybe even only one? That would make it easier for us to debug the problem.