Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question #16

Open
PJVol opened this issue Apr 11, 2024 · 0 comments
Open

Question #16

PJVol opened this issue Apr 11, 2024 · 0 comments

Comments

@PJVol
Copy link

PJVol commented Apr 11, 2024

Hi!
Have you got an idea, what could be the reason for the Ring0 file remained open after the app exit on some PC's ?
Thanks!

PS: Here's a way to reproduce this, using ZenTimings as an example, just to illustrate what some users came across:

  1. Run ZenTimings
  2. Search for the winring0 handle in a Process Explorer (from Sysinternals)
  3. Close found handle

After you close ZenTimings, the file ZenStates-Core.sys is still in the app folder. The issue is that the WinRing0 handle no longer exists, and yet the explorer says the file ZenStates-Core.sys is opened elsewhere when you try to delete it.
I also couldn't find out the lock source, as no tool (system or 3rd-party) I tried were able to identify it.

My guess is this can be caused by the Ring0 driver crash on the user’s PC

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant