1

I have a small problem with my Windows Server 2012 R2. At the moment the problem is that the threads from "NT Kernel & System" increase every second until they reach 16k, and then the server becomes very slow or hangs. When I try to debug the process with Process Explorer:

Process Explorer Screen Shot

Here you can see that something spawned a new thread and wait. I've tried to stop all my services but i can't find a solution. Have any of you had the same problem in the past?

SamErde
  • 3,409
  • 3
  • 24
  • 44
René Höhle
  • 1,438
  • 3
  • 17
  • 26
  • Can you right-click on the process and see the full path? – SamErde May 22 '17 at 19:54
  • No if i make a double-click i get the info "Unable to access thread" and right-click has no function. – René Höhle May 22 '17 at 20:04
  • 1
    Are you running Process Explorer as an elevated process? You may be logged in with an administrator account, but please be sure to still right-click on Process Explorer and select "Run as administrator." That should get you access to the process and thread info. – SamErde May 22 '17 at 20:11
  • Yes it's running as Administrator but the same. I'm loggedin as Domain Admin so a should have enough rights but i've testet it and no chance... – René Höhle May 22 '17 at 20:17
  • Just to be clear, you still need to "Run as administrator" even when you are logged in as a Domain Administrator. (You can thank UAC for that.) – SamErde May 22 '17 at 20:20
  • Yes ;) but i have no access... – René Höhle May 22 '17 at 20:21
  • Let us [continue this discussion in chat](http://chat.stackexchange.com/rooms/59142/discussion-between-stony-and-sturdyerde). – René Höhle May 22 '17 at 20:23
  • So, what was the answer here? – Brandon Langley Jun 09 '23 at 17:20

1 Answers1

3

This explains the issue. Combination of KB4019215 and bad iSCSI connections.

https://www.reddit.com/r/sysadmin/comments/6cum10/headsup_2012_r2_servers_with_iscsi/

Cedar
  • 46
  • 1
  • That fix isn't installed on my system. And i don't use iSCSI anymore. I have uninstalled all iSCSI packages. So i don't thing that this is the problem. – René Höhle May 25 '17 at 12:09
  • I've checked iSCSI again. The service was not running but the old connection was active after restart the service. Now i've deleted all connections and i think it looked good now. – René Höhle May 25 '17 at 12:58