Aquinus
Resident Wat-man
- Joined
- Jan 28, 2012
- Messages
- 13,153 (2.87/day)
- Location
- Concord, NH, USA
System Name | Apollo |
---|---|
Processor | Intel Core i9 9880H |
Motherboard | Some proprietary Apple thing. |
Memory | 64GB DDR4-2667 |
Video Card(s) | AMD Radeon Pro 5600M, 8GB HBM2 |
Storage | 1TB Apple NVMe, 4TB External |
Display(s) | Laptop @ 3072x1920 + 2x LG 5k Ultrafine TB3 displays |
Case | MacBook Pro (16", 2019) |
Audio Device(s) | AirPods Pro, Sennheiser HD 380s w/ FIIO Alpen 2, or Logitech 2.1 Speakers |
Power Supply | 96w Power Adapter |
Mouse | Logitech MX Master 3 |
Keyboard | Logitech G915, GL Clicky |
Software | MacOS 12.1 |
A hard fault is any time the "page file" is accessed. So you can be idling and Windows will decide to take stuff out of memory to make more room. You can disabled the page file and still get hard faults, the difference is that the hard faults aren't accessing a real drive but, rather essentially a ram disk instead of a real disk.Windows has a lot to do with that, I have 8 GB of RAM and when I am using only 3 GB or 4 GB I keep seeing hard faults which is kind of weird since there is so much RAM available this should not be happening .
Maybe Windows is also guilty for this, a while back I was getting "Close programs to prevent information loss" constantly after leaving Firefox or some other program open for a few hours. I was getting this on Windows 8.1 but it never happened to me on Windows 7, well expect when I formated external USB drive and explorer started eating all the memory because of the memory leak (Thank you Microsucks for not fixing that, idiots).
You don't need to fill system memory in Windows for it to start hard faulting, it just does it a lot more often when you start running out of space. Another reason why I run without a page file.