getting driver memory footprint possible ?

Discussion in 'Windows 10' started by LiteOS, Jun 22, 2021.

  1. LiteOS

    LiteOS Windowizer

    Mar 7, 2014
    2,343
    1,048
    90
    is it possible to get the memory footprint of each driver in windows 10 ?

    ty
     
  2. Are you asking about saved RAM State after each n every driver gets installed in win10 .
    If its Then Question is Related to Forensic POV but whats the use of dumping RAM State for this driver installation Scenario.
     
  3. LiteOS

    LiteOS Windowizer

    Mar 7, 2014
    2,343
    1,048
    90
    Im afraid i duno :D
    just looking to reduce memory footprint
    by seeing which drivers taking the most
     
  4. endbase

    endbase MDL Guru

    Aug 12, 2012
    4,694
    1,717
    150
    I use CAM from NZXT for that Top processes gives me a oversight of what uses most RAM at that moment maybe take a look at it. If that is what you mean with your question I could be wrong of course
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. murphy78

    murphy78 MDL DISM Enthusiast

    Nov 18, 2012
    7,419
    11,688
    240
    It seems that the problem is a lot of drivers load bloatware and custom control panels. Graphics card drivers are notorious for this. Printer drivers are also notorious. If you are looking to do this, it will really be a lot more work than you can possibly imagine. There are like hundreds of thousands of drivers and thousands of those are full of bloat. My suggestion is to maybe just look for lited graphics card drivers and leave it at that. If you go through all of the bloated drivers, you will never stop. There's just too many.
     
  6. LiteOS

    LiteOS Windowizer

    Mar 7, 2014
    2,343
    1,048
    90
    what about windows 10's drivers or any bloated os
    any hope there ?
    mb will be able to tweak it better
     
  7. But i know you if i am not wrong.
    You are the one who helped legolash2o in install wim tweak tool which is awesome till date .
     
  8. LiteOS

    LiteOS Windowizer

    Mar 7, 2014
    2,343
    1,048
    90
    offtopic
    just the idea of the hidden packages not with the coding :)
    i know u too ?

    im pretty much done in that area with tweaking and disabling i think
    i was hopping to find more ways to reduce the memory
    better the os so i took this approach
     
  9.  
  10. murphy78

    murphy78 MDL DISM Enthusiast

    Nov 18, 2012
    7,419
    11,688
    240
    Win10 includes default drivers. Some of those have some bloat. Not all of them are loaded. It depends what hardware you are using. Like I said, I'd really only bother trying to de-bloat and replace the graphics drivers because you'd just never stop. AMD, Intel, and Nvidia are notorious for the bloat. I'd isolate the ones that are included in the distributions you are trying to lite and try to find lited replacements. Or just remove them altogether and let people rely on generic graphics card drivers. That's an option. I don't think I've ever installed Windows and had it recognize my graphics card. It always uses the default graphics driver until I install one.
     
  11. LiteOS

    LiteOS Windowizer

    Mar 7, 2014
    2,343
    1,048
    90
    I agree
    But maybe there something that do good at the middleground
    cos i saw tweakers kills "all" the drivers in the os and get handles lower by 4k from 13k
    and memory reduced by 150mb

    So if getting more info about those drivers would be easier maybe cutting here and there and
    os will be still working as well and gain more smoothness
     
  12. murphy78

    murphy78 MDL DISM Enthusiast

    Nov 18, 2012
    7,419
    11,688
    240
    Well, allocating memory and actively using memory is not the same thing. As far as what is safe to remove, well... that's debatable.
    There are a lot of drivers that IMO shouldn't even be included in Windows anymore because they're for hardware that nobody uses anymore.
    I mean there are drivers for old ISA video cards and video capture cards from the early 2000s. Old printers that connect via printer port.
    Most of the drivers that Windows includes are very small but pointless. They never actually get loaded at all because the hardware is not present.

    If I were to lite an OS, I would remove all of the old hardware that nobody uses and leave stuff that people need like usb hub drivers and wifi and generic drivers and such.
    I would leave it so that people could install their own drivers as necessary, but the system didn't really provide its own drivers for hardware.
    I'd remove all the graphics card and sound card drivers. I'd remove all printer drivers. Basically I'd just leave people with the ability to download their own drivers from the internet.
    Then if you really want to get nerdy beyond that, you'd need to talk with other lite'ers about reducing memory footprint. I'd start with gutting the services, then the drivers. Then re-evaluate.