Spam bots will do that. They pick a random topic, post into it, get found out and then the bot and its post are terminated with extreme prejudice.



That's the way to do it, one step at a time. Keep us posted!

Ahh never even occurred to me that it might have been a bot hehe.

Delayed a bit on further testing as there was a big windows update and a bunch of store app updates as well so need to run a couple days on the newer windows version to make sure it's stable before I start installing anything else.

winstep dev - Have you updated to 24H2 yet, or have you found what would cause the cpu increase. I'm thinking of updating again, but will have to not use the dock, if its still the same

Shouldn't be a major issue, simply restarting Nexus is enough to get the CPU to behave again.

At least I had no major issues, yes once in a while something seemed to get stuck and cpu usage would go up but restarting the program settles it back down. It wasn't something that happened all the time. Maybe once every few days.

Thanks for the information. Appreciate it.

Closing and reopening has no effect for me. It continues to run high all the time for me.

I'm assuming workshelf is part of your Nexus install (I only have nexus ultimate which doesn't have the workshelf stuff).

But it doesn't seem to be using all that much, 15% isn't that bad depending on what CPU you use and how many cores you have. But the task manager shows your CPU usage at 43% but it's not coming from anything nexus related according to that screenshot.

But I do see you have rainmeter installed, which I do have a lot of experience with as I use it myself and I know that certain skins will use a lot of cpu power, which won't show in task manager as it runs in a different process that doesn't turn up for some reason.

Especially if you use one that has things like monitoring tools, weather stuff etc, those kinds of things constantly refresh every couple seconds which puts a load on the cpu.

So could be the combination of nexus running alongside rainmeter is what is causing the higher load.

You can try turning rainmeter off for a bit and just run with nexus and see if that eases up on things a bit.

Might be other things going on there too as it seems like you have a fair amount of things running in the background and starting with windows etc but I'd need a more complete view of the background task section in task manager to see if there's anything else specific that might be causing that for you. But rainmeter is more than likely the main culprit there as I've had that issue myself and actually stopped using most of the stuff I had set up in rainmeter because it was just constantly using resources even when it didn't really need to.

*edit* Now that I think about it, your system interrupts shouldn't even make the top 30 of CPU usage so I suspect there's something going on in the background there that is causing a higher than normal workshelf load

Although I do still think it's rainmeter because it shouldn't be using more than the occasional 1% so a nearly 3% load just from rainmeter itself is a bit abnormal and suggests you have a lot of skins activated or a few really demanding ones and that will use more CPU and cause the system interrupts to be higher, which depending on how workshelf works could be causing it to use a higher than normal amount of CPU to constantly update itself due to the rainmeter stuff changing etc.

It's an issue with 24H2. Ran under all the previous win 11 builds without an issue. As you, I have used rainmeter for an eternity, and it's not that. In fact I booted with just Microsoft services and workshelf enabled, and it was running between 10-17%. It's not massive, but compared to 23H2 which was like 2%. Revert for now back to 23H2, and maybe clean install later.

Unfortunately (or fortunately?) still on 23H2 here, but from what I have been reading 24H2 has a TON of issues (with lots of applications, not just Winstep).

If there is one thing I have learned with modern day Microsoft, is to NEVER be one of the first to jump to the latest and greatest. Wait a few months at least. Microsoft now relies on their customers to be their guinea pigs, instead of a proper QA team.

Ok Finally got around to doing some testing. Not having any resource usage issues, but..... Nexus is back to crashing my system. Windbg analysis below:

: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_GT_ZERO_AT_SYSTEM_SERVICE (4a)
Returning to usermode from a system call at an IRQL > PASSIVE_LEVEL.
Arguments:
Arg1: 00007ffa62d5c444, Address of system function (system call routine)
Arg2: 0000000000000002, Current IRQL
Arg3: 0000000000000000, 0
Arg4: ffffd88e77b1eb60, 0

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1375

Key : Analysis.Elapsed.mSec
Value: 1433

Key : Analysis.IO.Other.Mb
Value: 11

Key : Analysis.IO.Read.Mb
Value: 1

Key : Analysis.IO.Write.Mb
Value: 22

Key : Analysis.Init.CPU.mSec
Value: 515

Key : Analysis.Init.Elapsed.mSec
Value: 45420

Key : Analysis.Memory.CommitPeak.Mb
Value: 87

Key : Analysis.Version.DbgEng
Value: 10.0.27725.1000

Key : Analysis.Version.Description
Value: 10.2408.27.01 amd64fre

Key : Analysis.Version.Ext
Value: 1.2408.27.1

Key : Bugcheck.Code.LegacyAPI
Value: 0x4a

Key : Bugcheck.Code.TargetModel
Value: 0x4a

Key : Failure.Bucket
Value: RAISED_IRQL_FAULT_Nexus-Ultimate.exe_nt!KiSystemServiceExitPico

Key : Failure.Hash
Value: {ee75eac8-e1b3-f99f-4097-9931279517ce}

Key : WER.OS.Branch
Value: rs_prerelease

Key : WER.OS.Version
Value: 10.0.27758.1000


BUGCHECK_CODE: 4a

BUGCHECK_P1: 7ffa62d5c444

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: ffffd88e77b1eb60

FILE_IN_CAB: 120624-5937-01.dmp

FAULTING_THREAD: ffffdd83bd3e0080

PROCESS_NAME: Nexus-Ultimate.exe

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

STACK_TEXT:
ffffd88e`77b1e998 fffff802`e4aa6ca9 : 00000000`0000004a 00007ffa`62d5c444 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffd88e`77b1e9a0 fffff802`e4aa6b1f : ffffdd83`bd3e0080 ffffd88e`77b1eb60 00000000`00000000 00000000`00000020 : nt!KiBugCheckDispatch+0x69
ffffd88e`77b1eae0 00007ffa`62d5c444 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x3cc
00000000`06a1e828 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`62d5c444


SYMBOL_NAME: nt!KiSystemServiceExitPico+3cc

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.27758.1000

STACK_COMMAND: .process /r /p 0xffffdd83ba69e080; .thread 0xffffdd83bd3e0080 ; kb

BUCKET_ID_FUNC_OFFSET: 3cc

FAILURE_BUCKET_ID: RAISED_IRQL_FAULT_Nexus-Ultimate.exe_nt!KiSystemServiceExitPico

OS_VERSION: 10.0.27758.1000

BUILDLAB_STR: rs_prerelease

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {ee75eac8-e1b3-f99f-4097-9931279517ce}

Followup: MachineOwner
---------

I eliminated everything but Nexus to ensure it was Nexus and not a conflict between it and another background app like rainmeter etc. Same result. Something Nexus is doing is causing some sort of conflict on 24H2. I don't have time to dig too much deeper but at a quick glance I'm guessing it's using an older shell api that is no longer 100% compatible with newer windows versions.

Ignore the OSNAME above, for some reason it says windows 10 when it is in fact windows 11 I'm running.

Ok I did make time to dig a bit deeper into this. It would seem it's not setting the IRQ level to the proper level after finishing a system call. So it's trying to go from system to user level when the IRQ is still above passive which causes the crash. So something needs to be adjusted to lower the IRQ level to passive before it transitions back to user mode.

The Nexus code does not mess with IRQ levels or directly talk to the hardware in any way. If anything, the problem would be in the Windows API itself.

24H2 is still on hold here because it crashes very popular Ubisoft games like Assassin's Creed Origin and Odyssey, and Microsoft still have not fixed that despite 24H2 being officially out for how long? At this point I have zero faith in them. They are destroying Windows and taking a lot of 3rd party applications down with them.

I just read that the percentage of Windows 11 users actually went DOWN this month, and the percentage of Windows 10 users up by an equivalent amount, despite support for it ending next October. I wonder why.

And for very good reasons - remember the problems some replacement shells and other customisation apps trying that had back in the day (1990s/00s)?

Never mind the games - albeit a pretty big market! - but all the other problems should be enough to turn anyone away from Windblows for good.

Jorge, it's been going down from the beginning of Win 11, and overall the shift has been largely towards Linux - with Ubuntu getting the Lion's share. (And macOS has lost some market share as well lately though not on the scale of Win 11.) All good stuff, virtually 5% market share, good for Linux. 10% and more, here we come!

Well I suspect at some point they may have changed something about how the API works, that's why I brought it up, might be you need to tweak a bit of code to conform to whatever half assed standards MS has come up with this time

I'm sure it's API changes. Or rather possibly using older API calls. I can duplicate the issue with exactly 3 programs and only 3 programs. Nexus, CrystalDiskInfo and OneCommander. All 3 are programs that have been around awhile and the only common factor is they all use the windows API, which I suspect is an older version of it and some code needs to be updated somewhere to make it compatible again.

It's not even a specific thing that triggers the crash, in the case of the Nexus crashes today the computer was just sitting idle at the desktop and not doing anything. I've had the same happen with the other two programs in my testing. Just open but not actively doing anything with them and they'll just take the whole system down and they all report similar errors.

So without really getting into the guts of everything it just seems like the API stuff must have changed somewhere along the way.

It's not specific to 24h2 btw, this issue started when I was on 23h2 and now 24h2 so it's not specific to this version of win11.

And not that I'm a windows fan, I'm really not lol. But the fact that win11 is going backwards user wise is because the OS itself is going backwards. Not only is win11 still not complete in terms of unified interfaces etc but they have in fact removed a lot of things that ppl liked about win10 (like moving the taskbar, resizing the start menu etc). Toss in the TPM requirements compared to all the ppl running older systems that can't properly run win11 and ppl can't afford to upgrade and that all adds up.

I myself still have win10 installed on one of my drives so I can boot into it if win11 craps its pants and I'm in a hurry (although I also have a working image I can restore at any time in about 3 minutes flat if I need to.

MS has just half assed everything in their rush to get it out the door and shoehorn copilot and ads into everything. Not surprising that ppl would stick with 10 because it was more polished and complete. Most of win11 is just erm.... windows dressing.....

I use it because my job requires me to know the ins and outs of the latest MS botch job. Aside from this 1 PC everything else I have is either Android or Linux.

You might want to look at a driver or hardware problem in that case. I'm running 23H2 here and I see no crashes. Not only that, but normally only drivers (or very low level stuff) are capable of generating BSODs that take the whole system down with them.