Windows 10 dos window running my own program runs with CPU 0%

Question

Windows 10 dos window running my own program runs with CPU 0%

regressist 0

Hi all, I am running on a pc with Windows 10 a program written by me (no bug) which makes some computations very simple but very time consuming: it runs in a dos window and outputs some integer numbers in the window and sometimes in a file. I am running in parallel two instances of the program but all of a sudden after two weeks one seems frozen: the performance meter reports running but the cpu is at 0%. For both the priority is normal, I tried to change the priority of the second to high or even real time but nothing changes. Is it possible that the CPU is dying and keeps only the first process launched freezing the other? Any suggestion to unfreeze the process or at least an explanation of what is going on? Thanks in advance to whomever will reply

2 answers

Your answer

Answer 1

MotoX80 36,291

Download and run Process Explorer. https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer Find one of your processes and select it. In the lower half of the window select Threads. Look at their state and CPU cycles. You can double click on a thread to look at it's call stack. Here I put Powershell in a computation loop. User's image

If you wrote the code in C# or VB.Net, double click on the program and view the .Net performance. You may have a memory leak. User's image

Compare the one that is running vs the one that is hung. Or restart one of them and monitor over time as it executes.

regressist 0 Reputation points

2024-01-19T09:55:50.83+00:00

Thank you, I will download it. The program is written in Pascal. I hope I am able to find the difference with the one running, looks like it will not be easy
MotoX80 36,291 Reputation points

2024-01-19T13:28:41.81+00:00

The easiest thing to do is to periodically write out an "I'm alive" message to the console. Include the current time of day, and some detail about what processing the code is doing.
regressist 0 Reputation points

2024-01-19T14:02:06.92+00:00

Hi, I checked threads of the frozen process (right) versus another started a few hours before and here is the result, the frozen has a Wait:Executive while the other is running.

For the stack there is quite a difference:

Sorry to harass you: is this enough to understand why the process is stuck? And if so is there any way to have it released?
regressist 0 Reputation points

2024-01-19T14:28:29.4966667+00:00

I repost my comment since it seems to be vanished. I have no doubt at all that the program is working properly, it's more than two years I am running it on various pc with perfect results; it shows what is doing on the console, this is how I found it was frozen, no data were coming out from days, very suspicious. This can only be an OS problem. I run process-explorer and found that the frozen program has a Wait:Executive in the state of the thread (versus another instance of the program running from a few hours before

Checked also the stack and there is quite a difference. Sorry to harass you again, is this sufficient to find why this is happening?
MotoX80 36,291 Reputation points

2024-01-19T15:40:50.4566667+00:00

The last update to this forum has introduced some bugs Comments/answers sometime take a while to show up. And line breaks also disappear so if the text of my reply all runs together, that's why.
.
.
With a wait:executive hang, you're looking at really low level debugging. It could be anything. Check your System eventlog to see if there are any events with fatal looking messages like "out of memory". . .
If the program has been running fine for a long time, then it could be something else that you are running that is impacting that process. Anti-virus software is a common suspect. .
.
Open task manager and make note of the handle count and the paged and non page pool values. With procexp monitor your programs memory and handle counts. .
.

.
.
Then reboot. When it comes back up, again make note of those values. Watch them over time and see if any of the values get extreme. .
.
If the problem reoccurs, then you'll have to get a dump of the process and let DebugDiag analyze it. I would hold off on that for now and hope that the reboot clears up the hang. .
.
https://learn.microsoft.com/en-us/sysinternals/downloads/procdump .
https://www.microsoft.com/en-US/download/details.aspx?id=58210

Answer 2

Hello, According to your description, I also suggest that check application event log, if we could find any event id 1001. It always means process hang or crash. If so, it may need to use WinDbg to analysis WER process dump. Check Resource Usage: Open the Task Manager and see how much CPU, memory, and disk usage the process is using. If it’s using a lot of resources, it might be causing your system to slow down. Check for Updates: Make sure your operating system and all drivers are up to date. Sometimes, outdated software can cause issues with running programs. Best Regards, Hania Lian

If the Answer is helpful, please click "Accept Answer" and upvote it.

Share via

Windows 10 dos window running my own program runs with CPU 0%

2 answers

Your answer