Replies

Does it “Boost your PC’s performance”?

Releasing even a Beta with headlining functions inoperable probably indicates the devs are still in Beta too.

Did Neowin just copy some ancient blurb too?

Y’all could do with spending some time actually using/testing before you post/advertise randomly collected articles with ‘interesting’ names.

‘Your’ Beta version of Storage Manager couldn’t perform a cleanup. ‘Easily uninstall infrequently used apps’ – tricky without any way of filtering to ‘last used on… ‘.

Pop-up Management didn’t put in an appearance on either Beta.

That’s not all I could pick holes in, go on – do a number on it for yourself, get some further education and post your own opinion on it.

Clues about what it manages and how it boosts performance might be useful, otherwise it’s just another Amazon/Ebay/Walmart empty boast.

The current beta actually does a little ‘cleaning’ which ‘your’ version didn’t.

Good to read about Windows XP in the present tense, too.

“Must try harder” comes to mind – was this a kindergarten project, or Fisher-Price’s My First AI App?

Providing the machines were activated legitimately, no re-activation will be needed.

Only a change of motherboard is likely to trigger activation issues. Common hardware changes/upgrades, like memory, drives and graphics cards should be allowed.

2 users thanked author for this post.

BobbyB, SupremeLaW

How much free space do you have and what % of that does the file take up?

Add PoolMon to the list; Use PoolMon to find a kernel-mode memory leak

Alex5723 wrote:

Energy Saver and Memory Saver are on by default on my

…notebook, desktop, fondleslab, AIO… ?

Linked to a previous test file of the same name?

Alex5723 wrote:

There is no other fix.

Assuming the cause is the same, which is a big step.

Alex5723 wrote:

its not OS/Software bug.

That’s why I used ‘bug’ fix.

1 user thanked author for this post.

Alex5723

Alex5723 wrote:

I don’t understand why no one (at least I haven’t read about) asking about the bug has been advised to replace the antenna hardware part.

Perhaps that’s a less well known ‘bug’ fix.

References are commonly and usefully posted from external sources but questions from non-members here are largely irrelevant – fluff, filler. They’re not asking us for help and the subject would have little to no bearing especially when there is no cause or preventative/repair actions listed – in either of the Topics (I believe you missed the original, which should have been the first reference used by any news reporter).

Half a ‘story’ omitted could be taken as a deliberate measure to attempt to bias others against a product or company, try to reduce any possibility of such attitudes creeping in.

If ntoskernel.exe was the cause, we’d all be running *nix or Mac. The Windows Kernel will call a Bugcheck (halt) to protect data/hardware whenever a serious problem is detected or flagged.

Productive options: check your drivers are up to date and actually needed on your machine. This goes double for any non MS-installed drivers – and – any running, or loaded, security or ‘utility’ software, either processes, drivers, or Services.

WinDbg comes in at least two forms, a traditionally installed download and an ‘App’ from the MSFT Store. Don’t give up after failing on one version (and check that you have any library requirements fullfilled).

It usually takes me over an hour to install, setup and get some dumps loaded correctly in WinDbg for the first time. Researching which analysis ‘calls’ to make can take just as long per step.

I sometimes find the output from DriverView/BlueScreenView/MSInfo32 can give very useful insights into what’s happening.

1 user thanked author for this post.

Mr. Austin

As per the online description, BlueScreenView scans the data from minidumps, larger dumps need different tools and more input/learning to get useful pointers.

Nirsoft’s DriverView displays the list of all device drivers currently loaded on your system: https://www.nirsoft.net/utils/driverview.html To narrow down the list to 3rd party drivers, View> Mark non-Microsoft drivers and Hide non-Microsoft drivers. MSFT-supplied (built-in) drivers, assumed to be fully tested and never causing Bugchecks, can sometimes be listed in there – see the Service Display Column for entries with an ‘@oem’ prefix and categorised as 3rd party.

BSOD Kernel Dump Analysis Debugging Information Kernel and full dumps require WinDbg (MSFT debugging tool) to follow these up.

Best self-help resources and debugging of Bugchecks/BSODs:
BSOD Bugcheck Codes (STOP Error Codes) and lots more on this site.

MSFT ‘help’ pages for your listed Bugchecks:

0xD1: https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xd1–driver-irql-not-less-or-equal
0xA: https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xa–irql-not-less-or-equal
0x139: https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x139–kernel-security-check-failure
0xB8: https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xb8–attempted-switch-from-dpc

1 user thanked author for this post.

Mr. Austin

Rick Corbett wrote:

Could it be just be a laptop thing?

Don’t have a notebook.

1 user thanked author for this post.

Rick Corbett