This is not really an accurate description of how things work. One thing you could do is try and run OBS studio on a windows 7 computer if you have one and see if the problem is there this only leaves the possibility of another kind of page fault being caused, most likely some kind of illegal memory access. So far OBS seems to be working fine, except it generates these page faults and that can take quite some CPU it seems though not entirely sure. Perhaps it is calling some kind of API that is not available on windows 7 or something deep in the graphics driver. So this only leaves the possibility of another kind of page fault being caused, most likely some kind of illegal memory access. OBS needs only 1 gigabyte of RAM so 6 gigabyte of RAM is fine. It can also indicate an illegal memory access.ĭisabling pagefile.sys will keep windows very fast, but will limit what it can do.ĭisabling pagefile.sys forces the applications to stay in RAM at all times, and thus these kinds of page faults should be illiminated this you can try yourself. These "missing' 4 kilobyte pages in RAM is what causes the page faults, it signals to the system that something is not there and should be loaded. Once the user switches back to an inactive application this can cause freezes because now windows has to load these 4 kilobyte pages back into RAM from the disk. Windows pretends to be capable of doing more than it really can by sometimes writing these 4 kilobyte pages to disk for memory which is not recently accessed, or when there is a shortage of memory. These pages are stored in lists in Windows. Windows divides the RAM into 4 kilobyte blocks called pages. There is nothing further for us to investigate. As written, this Issue is not actionable. These things together would lead me to conclude that the issue you are seeing is caused by your system configuration (RAM constraints, disabled PageFile, possible issue with GPU). This may or may not contribute to the high count of page faults on your system. OBS relies heavily on graphics hardware to render its graphics. This toshiba laptop does have a broken 3D graphics chip, not sure if that has anything to do with it This is most likely leading to the large number of page faults that you are seeing. I've certainly not seen 40,000+ per second of any type of page fault.Īdditionally, given that your system only has 6GB of RAM, disabling PageFile.sys will only exacerbate the low availability of RAM by not allowing the system to allocate virtual memory when needed. At most, I've seen single/double digit numbers of those. What would be concerning are a large number of hard faults, which I am not seeing when checking Performance Monitor or Resource Monitor. As far as I know within my limited understanding, applications can generate page faults through normal operation. While OBS does produce some page faults on my system, this is not, by itself, evidence of anything particularly wrong. Most likely this is being caused by "the OS denying illegal memory access". Here you can see my youtube stream and you can see OBS is working on this laptop:Īt 2:05 minutes approx you can see me right now and see the task manager in action and the page faults. (This toshiba laptop does have a broken 3D graphics chip, not sure if that has anything to do with it, at least I believe this is the case, could also be a broken driver but I don't think so, I turn off hardware acceleration in all software, including webbrowser/firefox, but this should not effect streaming since OBS can be used even when firefox is not running). Please fix it, this lags the system incredibly and it forces me to switch to another streaming software solution. Watch the page fault difference counter/column. The operating system is Windows 7 Home Edition with PageFile.sys disabled. Generating 40.000+ page faults per second. Be efficient and don't generate page faults.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |