Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(+1)

Ok, so I just solved it.

I have NO clue how in the world this happened, and amazed at how precisely specific the issue was.

My Null registry was corrupt.

By going into (Windows Key+R) -> Regedit, I navigated to HKEY_LOCAL_MACHINE/SYSTEM/ControlSet001/Services/Null.

The Registry "Start" was set to a value of 4... but the value should be 1.

I'm starting to question how that happened. I do recall at one point having to modify the registry to fix my RAM from allocating too much virtual memory, but I don't remember navigating to this particular location in Regedit to do so.

However, all this sounds a bit familiar when I was discovering that sourcetree wasn't installing properly, and it turned into a discovery that git simply wasn't working because it claimed "dev/null could not be found".

This all seems to link up with what the Squirrel process (or whatever the itch app uses to pull from a git repo) was having issues with.

Sorry for the confusion, but at least it's all fixed now.

and most importantly, thanks for giving the effort in helping me with this strange problem. 👍

Oh wow, kudos for finding out the source of the problem! Never seen that one before :) But I'll keep it in my book of weird bugs. Thanks for continuing to try & make it work, enjoy the app!

(+1)

I'm back with some very particularly interesting information on the matter.

I found out why this happened in the first place...

So this past week, after I changed Null's registry back to the defaults, I discovered an issue that's been happening a long time ago since I first got this alienware laptop. The computer will sometimes come to a crawl, which is totally unnatural, since it was pretty new at the time (and still is). I would check task manager to find that the memory was near 100%, System process taking up most of it, and causing the OS to occasionally freeze for a second, and resume again. Well, now it's been happening again, and naturally I look for a solution to the problem...


that same video I remember finding tells me to set Null's Start registry to 4. That's why this problem happened.

So on the one hand, I get my non-paged pool back to normal, tolerable levels, but I'm pretty sure that will now mess up dev/null for any git related work. Thankfully, I've only had to rely on Unity collab for any projects, but this is just.... weird. Windows 10 seems to straight up have an issue with this and to have to modify the registry to fix it just seems way off. It actually does remove the memory issue though, a long time after I didn't have anymore freezing, but if only there was a better solution than this. I don't really mind anymore now that I know what was happening, but long story short... Windows 10 has got some issues to fix 0.o

(+1)

Hmmm... maybe disregard all of this actually, it might be a mistake in setting Start from 1 to 4 in Null, when instead it should be set to 4 in "Ndu".

Apparently there's an issue with some alienware on windows 10 where if you got your pc with "killer ethernet" installed, it has memory leak issues in the non-paged pool. setting Ndu's Start value to 4 fixed all issues for me.