Issue with memory allocation restrictions in the system.
Issue with memory allocation restrictions in the system.
Your Dell Latitude 7480 has 16 GB of RAM installed, but only 4.8 GB is actively usable while the remaining 11.2 GB are reserved for hardware. You've already adjusted settings via msconfig and regedit, verified the BIOS, and replaced the RAM. I'm confused about what's happening—could you clarify if the issue persists or if there are further steps to take?
Have you verified if it's being assigned virtual memory? Open File Explorer, left-click on this PC, go to Properties. Under the About tab, scroll down and choose Advanced System Properties. Select Advanced, then click on Performance settings again. You should see information about virtual memory allocation. Edited October 28, 2022 by lopj245 Missed the section where you attempted to run msconfig.
Many users experience significant RAM consumption on Windows. Often they assume a hardware issue, but frequently the cause lies in software. Switching to a Unix-like environment can help assess actual memory usage. Personally, I run FreeBSD and my system has remained stable for over three years without reinstallation. It shows about 117 MB of active RAM, with the remainder being cache or free memory.
What are you talking about with The Hope? I'm using Linux and have limited memory—only 32GB RAM, sometimes the software needs more than that. I'm curious why people still think 16GB is enough for their computers. If they often ran out of memory, they probably wouldn't settle for less. FreeBSD handles memory well, but it seems to be a bigger issue on desktops, especially with its NFS setup. @PoBidauBen I've noticed this with memory issues on some Lenovo machines (old Think Stations), but I never found out what caused it. Linux and FreeBSD work just fine on those systems. It might be a Windows problem. I'd appreciate your help since I might encounter it again and want to know how to fix it.
The performance remains similar when transferring large files to and from the NFS-mounted zpool. With many files, FreeBSD delivers noticeably better speed. My Microsoft LifeCam HD 3000 runs flawlessly on FreeBSD, whereas Windows 10 no longer supports it. I’ve noticed more limitations with Windows 10 in general compared to FreeBSD. On my system, RAM usage can drop below 40MB during extended PC sessions.
Consider sharing directories on a file system to various NFS clients on FreeBSD and you'll grasp the point. What about Wayland? PS: The manual still mentions (https://docs.freebsd.org/en/books/handbo...guring-nfs) that "the file systems which the NFS server will share are listed in /etc/exports." Each line tells clients which files they can access. Read that closely. I only realized this after discovering NFS doesn't work well on FreeBSD. Except for that, FreeBSD feels familiar—it's quite similar to Linux from a few years ago. But why stick with it? NFS isn't recommended, and virtualization was still in its early stages. Switching to FreeBSD would demand more effort, and I wouldn't feel confident doing anything better or more efficiently without the extra learning. I accept the learning curve, but I don’t want to face issues where fixing something becomes complicated because of FreeBSD.
I usually avoid such pages, but this looks like a solid guide. The max memory section is particularly useful, as well as the one for iGPU memory. Definitely worth checking out. Also, it might be interesting to explore. However, I think some laptops have RAM that’s already soldered in.