Windows 8.1: Constant 'Low Memory' warnings with 5GB of free memory

***a full 4GB of main memoryfor 32bit another 4GB for 64bit) and a 12.5GB paging file***

that does make sense

are you in 8.1 x64 with 4gb physical ram with 12.5gb page files or does windows say your comitt limit is 12.5gb? The second means 4gb ram plus 8.5gb in page files

your mixing 4gb twice with 32 then 64gb so it's a tad confusing. 

8GB of physical RAM and a manually set minimum 4.5GB, maximum 12.5GB paging file.

When the error pops up resource mon shows between 35% and 40% memory usage.  It remains stable at this level until the eventual crash.  No processes show any significant changes (+/- 2%) from the time of the first warning.

Ok. 8gb ram with dynamic page file. 

Unless u need space, pagefiles should always be fixed in size.. When windows extends the pagefile, it takes time, resources, and often fragments the file.  With fixed, windows tries to out the whole think in 1 block on the next reboot. If it were me, I'd fix ur pagefile to min and max of 12.5gb .. That's more than enough pagefile space. You will perform better with a fixed file(s)

YOUR issue is different from the other guy as all his ram and pagefiles fill before he crashes , you show no obvious leak.. Keep in mind any 32driver or game will crash once it's gone over 2gb (unless it's large address aware... Then it's 4gb) 

Since neither her your paged and non paged pools are out of control, I'd say it's a driver leak into the memory set aside for drivers 

if it's a driver , then windows won't show memory being used as drivers have a special memory space they run in, you need a 3rd party tool...I'm on my ipad now... When I go to my desktop, I'll tell u the name of the program I use which can show you all the drivers and what they use... Then u can identify the driver 

I'll tell u what I told the other guy.. Back up saved games, important data. Go back to win 8 until intel releases drivers DEDICATED to 8.1

If all your committed memory is being used, that means it's a paged pool leak

what I meant by not MS fault was, 8/8.1 share the same memory management. But a lot of the os was changed.. Especially video areas 

So is it intels fault for not updating the driver? Or ms for updating the os? if this were a major bug in 8.1... The net would be flooded with people screaming.. And I don't see it. I vote intels fault. They should have an 8.1 driver 

Technically, my i7-2600k CPU has intel graphics in it , but u have it shut off in bios. But if you guys have an intel graphics gpu on the mobo, different story

historically, built in graphics have always caused issues... Especially when u add a real gpu system. Back in the days of agp video, mobo GPUs were common... And it caused mega issues in windows

cant you guys disable the intel graphics in bios and use an nvidia or ati PCI card? That should erase the issue. If intel graphics are disabled, windows won't see it, and you don't need drivers for it. Unless u guys actually use intel graphics

Either case.. This is a paged pool leak.. Since it's 64 bit drivers.... They can leak up to 8tb before crashing. You could have a 1tb page file, and eventually it would fill and crash.

Since this doesn't happen on non gpu mobos that rely on a video card, it's probably an intel issue and they need drivers made for 8.1. The only way I can see as a ms issue would be if it's a ms driver , service, Process, Etc leaking.

And you can't fault ms for changing stuff in 8.1 vs 8. Ms ms also changed graphics from 8 to 8.1 required new graphics drivers as 8.1 supports dx 12.

So if u are using the same drive u used in 8... That's a no no. Nvidia and ati both have different drivers for 8 and 8.1. If I install an nvidia driver for win 8... All sorts of weird **** happens.

Intel NEEDS an driver made for just 8.1 This is won't be a quick and easy fix. I suggest backing up saved game files, pics, data, important stuff and going back to 8.0 until the issue is fixed

***a full 4GB of main memoryfor 32bit another 4GB for 64bit) and a 12.5GB paging file***

that does make sense

are you in 8.1 x64 with 4gb physical ram with 12.5gb page files or does windows say your comitt limit is 12.5gb? The second means 4gb ram plus 8.5gb in page files

your mixing 4gb twice with 32 then 64gb so it's a tad confusing. 

8GB of physical RAM and a manually set minimum 4.5GB, maximum 12.5GB paging file.

When the error pops up resource mon shows between 35% and 40% memory usage.  It remains stable at this level until the eventual crash.  No processes show any significant changes (+/- 2%) from the time of the first warning.

@TallBear-

I am following 4 threads here on Microsoft and 1 on Intel in regards to this issue.  The behavior is as I described above. 

In my case I have 16gig real RAM and an 8 gig page file.  When I force the issue to happen my system commit level will be at 24gig.  It is easy to get to happen as well.  Just display a full screen video (not in a window) and then physically power off your monitor for about 10 minutes.

As for who's fault it is that is a tossup.  I am hoping that Intel figures it out because after months of telling them about it they apparently have reproduced the issue and are working on the root cause.  I could figure out if AMD or Nvidia are affected by installing discrete GPUs but I dont have time.  I have figured out a work around for the issue in my case (viewing full screen WMC video) so I really dont care anymore.

If AMD or Nvidia were affected it seems like we would see threads on their sights about it and I have yet to find one.  Also, when people here say that Nvidia is affected I tend to doubt it.  Apparently if you have a hybrid laptop with both Intel and Nvidia installed then Nvidia does all the heaving computing but passes the frames to display through the Intel driver.  This could explain why people think that Nvidia is affected.

So if you take the latest Intel Driver and you run it under windows 8 this behavior is not seen.  If you take the same driver and run it under 8.1 you will see the issue.  So the only thing that changes in the test is the OS.  However, there is a good chance that 8.1 causes the driver to take a different path though the code.  So maybe Intel was getting lucky in the past.

Also, for people with older Intel Display Drivers (up to HD4000) they can take "non-8.1" drivers and run them under 8.1 without seeing the issues.  This is why you see people telling others to back up to 2875, 2884 or 3107. 

Time will tell how this gets fixed.  I think that we are within a month of seeing something out of Intel.

I tend to agree with you that this is an Intel driver issue, not a Microsoft issue.  However, as a programmer I can not bring myself to take your stance of "there is no way that this is a Microsoft issue".  Too many variables are involved.