Unusual large payment fees with unclear origin – what can be done to trace them?

F5F Stay Refreshed Software Operating Systems Unusual large payment fees with unclear origin – what can be done to trace them?

Unusual large payment fees with unclear origin – what can be done to trace them?

Unusual large payment fees with unclear origin – what can be done to trace them?

Pages (2): 1 2 Next

F

Fluffycakes123
Senior Member

696

04-01-2023, 10:00 AM

#1

Due to an unexpected spike in committed memory—84GB in this instance—the usual diagnostics didn’t reveal anything unusual in Resource Monitor or Process Hacker. I recall reading about potential causes before, but can’t recall the exact methods now. One possibility was checking the non-paged pool for driver issues, though everything appears normal here.

F

Fluffycakes123

04-01-2023, 10:00 AM #1

Due to an unexpected spike in committed memory—84GB in this instance—the usual diagnostics didn’t reveal anything unusual in Resource Monitor or Process Hacker. I recall reading about potential causes before, but can’t recall the exact methods now. One possibility was checking the non-paged pool for driver issues, though everything appears normal here.

P

peyesta
Member

212

04-02-2023, 11:07 AM

#2

Thanks in advance! The WDK rings up familiar, so it seems poolmonX is definitely superior. I restarted after about half an hour, checking for any leftover services that might be paused, but nothing came to the surface—especially since it was running at driver level. I disabled the pagefile to free up space, as it had ballooned to 70GB and my drive was nearly full. I’ll keep an eye out if this happens again.

P

peyesta

04-02-2023, 11:07 AM #2

Thanks in advance! The WDK rings up familiar, so it seems poolmonX is definitely superior. I restarted after about half an hour, checking for any leftover services that might be paused, but nothing came to the surface—especially since it was running at driver level. I disabled the pagefile to free up space, as it had ballooned to 70GB and my drive was nearly full. I’ll keep an eye out if this happens again.

S

Super_Chach
Junior Member

11

04-03-2023, 05:09 AM

#3

Hmm looks like it's the storage, actually paged... 3.5GB already, was at 2.5 when I started looking. It might have started with the 21H1 update or KB5003214 that I installed 2 days ago since it wasn't an issue before and nothing else changed

S

Super_Chach

04-03-2023, 05:09 AM #3

Hmm looks like it's the storage, actually paged... 3.5GB already, was at 2.5 when I started looking. It might have started with the 21H1 update or KB5003214 that I installed 2 days ago since it wasn't an issue before and nothing else changed

A

AngryCarrots
Member

72

04-03-2023, 06:51 AM

#4

Consider checking the web browser first, as Chrome is often associated with memory issues.

A

AngryCarrots

04-03-2023, 06:51 AM #4

Consider checking the web browser first, as Chrome is often associated with memory issues.

N

Nixelord03
Member

182

04-03-2023, 09:57 PM

#5

And of course I can't since KB5003214 is non-removable It's at 4+GB now, I reenabled pagefile so it doesn't crash during the night, and it'll give me an opportunity to take a screenshot with a freaking 80GB kernel mem leak to submit to the feedback hub, with a bit of luck it'll spark some attention...

N

Nixelord03

04-03-2023, 09:57 PM #5

And of course I can't since KB5003214 is non-removable It's at 4+GB now, I reenabled pagefile so it doesn't crash during the night, and it'll give me an opportunity to take a screenshot with a freaking 80GB kernel mem leak to submit to the feedback hub, with a bit of luck it'll spark some attention...

C

catseecoo
Senior Member

662

04-10-2023, 01:30 PM

#6

It depends on whether the update was a complete install rather than a minor patch shared via WU. For minor updates, PoolmonX shows columns as 32-bit integers because they shouldn't reach that size, which is why it looks broken—we'll need to check the source tomorrow.

C

catseecoo

04-10-2023, 01:30 PM #6

It depends on whether the update was a complete install rather than a minor patch shared via WU. For minor updates, PoolmonX shows columns as 32-bit integers because they shouldn't reach that size, which is why it looks broken—we'll need to check the source tomorrow.

V

Vesuviuz
Junior Member

37

04-10-2023, 02:14 PM

#7

You can also include the commit size in the task manager details section. Just a note (sometimes extra tools aren’t necessary to view certain information)

V

Vesuviuz

04-10-2023, 02:14 PM #7

You can also include the commit size in the task manager details section. Just a note (sometimes extra tools aren’t necessary to view certain information)

H

hassi
Member

78

04-17-2023, 08:39 PM

#8

I understand the point, though in this scenario no odd commit numbers appear beyond poolmon...

H

hassi

04-17-2023, 08:39 PM #8

I understand the point, though in this scenario no odd commit numbers appear beyond poolmon...

T

thorpops12
Member

244

04-17-2023, 10:01 PM

#9

Updated the visuals, now supports larger scaling and captures screenshots.

T

thorpops12

04-17-2023, 10:01 PM #9

Updated the visuals, now supports larger scaling and captures screenshots.

Z

Zackdakiller
Member

204

04-21-2023, 02:07 PM

#10

Considering ISLC? It doesn't seem tailored to the exact issue, but it could be connected. Give it a shot. Adjust settings to half of your installed RAM. https://www.wagnardsoft.com/forums/viewtopic.php?t=1256

Z

Zackdakiller

04-21-2023, 02:07 PM #10

Considering ISLC? It doesn't seem tailored to the exact issue, but it could be connected. Give it a shot. Adjust settings to half of your installed RAM. https://www.wagnardsoft.com/forums/viewtopic.php?t=1256

Pages (2): 1 2 Next