Windows 10: BSOD when changing page file to system managed

Hello,

i got BSOD, when i was changing page file to system managed from custom size. I am not sure, but i think i did not click even ok yet, when i got it.

Issue seems complicated, it could be multiple things, so i rather post log. Then trying to fix it myself...

I used V2 log collector to collect the log, i got some error on the way. I uploaded a picture.

Thanks for help!

BTW how do i see an error message of BSOD, after a BSOD happened? I have a BSOD viewer too, but it doesn't show an error message, only an error code. This would help in future. Also i didn't find this in Event Viewer.

EDIT: ah i found how, by a bug check code. I found the page, but it is complicated. Don't know what that means anyways... https://docs.microsoft.com/en-us/win...ory-management

:)

 

System Paging File Help

You don't need a page file on C:, but there might be good reasons for having one that is static - please explain what these are.

I've set up my system with no paging file on c: and system managed file on other drive(s) and it works fine. Plus, if you run up against your pagefile's current limit, having it set to system managed with reduce the chance of a freeze/bsod/etc.

If you set the page file as static and you run out of virtual memory, you have problems. However having too big a page file reduces performance. I'm more concerned with stability so I always go system managed.

 

System Paging File Help

Is this a question or an answer mate? *Wtf :wtf:

 

System Paging File Help

the problem with letting the system manage the page file is you will end up with more defragmented files as the page file grows and shrinks,

you should set a min page file size of say the same size of your ram and then double it and add just a bit more for the maximum size so you wont run into problems running out of ram.


or the smart thing to do is to watch the amount of total ram your system use's and modify your page file to suite.