Windows 10: is this normal or should i be worried ? ntoskrnl and registry?

ntoskrnl and regestiry?

- - - Updated - - -

bump

:)

 

Registry editing

Hello,

This issue may have occurred after one of the following situations:

• You upgrade the Windows operating system.
• You install or uninstall CD or DVD recording programs.
• You uninstall Microsoft Digital Image.

Given that, we suggest performing the methods in this article:
Your CD or DVD drive is not recognized by Windows or other programs.
The resolutions that are listed in that article may help solve some instances but not all instances of this problem.

Important:This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow
these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, refer to the following Microsoft Knowledge Base
article.

Feel free to update us with the results.

 

HyperSLI (Enabling SLI on non-sli motherboards)

Boot problems

Hi everyone.

I've got some problems during instalation. I disabled UAC, passed the first install step, rebooted and completed install. But after consequent reboot Windows detects 'ntoskrnl' or something is corrupted.

Everything was fine on 'old' windows, but after I made a clean windows installation, everything goes this way.

Any suggestions?

 

ntoskrnl problem?

I am pretty certain the issue has nothing to do with proxy settings. Let me recap the symptoms.

• after a reboot everything is "normal and functioning" except if I open resmon it shows that the ntoskrnl process is creating a new thread about every 8-10 seconds so the thread count continuously climbs,
• in 24 hours after the reboot the thread count on the kernel reaches about 16524+ at which time the browsers can no longer open a new connection
• at this point in time resmon shows the thread count on the kernel no longer incrementing.
• if I do a "pslist64 4 -x" ( from PS Tools) it shows thousands of theads in the "wait:executive" state with runtime durations that decrease by about 8 seconds per line
• if I use process explorer to check the kernel process it shows that the thousands of threads have a start address of ntoskrnl.exe+0x3dbd0

I do not have a kernel debugger or process link map to find out which module is creating all these zombie threads.