Share via

Potential Memory Leak issue (high non-paged pool) observed on Windows Server 2022 while running FIO

Anonymous
2024-04-17T03:25:25+00:00

Summary: Non-paged pool continuously increasing to abnormally high value during FIO IO test, eventually lead to FIO returning "fio: windows error 1453 not handled," system slowness and occasional BSOD.

Host platform: Supermicro SYS-221H-TN24R

Chipset: Intel(R) Xeon(R) Silver 4410Y (gen5 Sapphire Rapids)

OS: Windows Server 2019 and 2022

Tool: FIO v3.36 (latest) tool generating randomized access pattern (any pattern generated seems to be causing the increase in non-paged pool, regardless of Sequential or Random write), writing to a secondary drive. Issue happens anywhere between 12 - 25hrs+ guessing until memory runs out.

Memory usage under task manager:

FIO running and error message:

Kernel Pool Monitor showing FS01 pool tag responsible for the non-paged pools, but could not link it to any driver:

Based on definition this seems to be a memory leak issue:

I have tried increasing VRAM to 64GB, increasing RAM to 256GB, disabling all network drivers, check all drivers under device manager are up-to-date, no luck so far. Please help. Thanks.

Windows Server Performance and maintenance

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-04-17T06:10:11+00:00

    Hello,

    Thank you for posting in Microsoft Community forum.

    Based on the description, I understand your question is related to memory leak.

    Here are some methods to fix this issue:

    1. Check if there are any known issues with FIO v3.36 and Windows Server 2022. You can check the FIO documentation or contact their support team for assistance.
    2. Install latest windows update by Settings/windows update/check for updates
    3. Update your drivers, if Driver Verifier has detected a specific one, you can update that driver and see if that fixes the problem.

    Press Windows + 'R' and type devmgmt.msc to open Device Manager.

    Locate the device and double-click on it to expand.

    Double-click on the driver and go to the Drivers tab.

    Click "Update Driver" and select "Automatic Search" for drivers.

    Have a nice day. 

    Best Regards,

    Molly

    0 comments