Windows 10: BSOD after accidently changing msconfig sittings

Hello

My sister accidentally changed the numbers in "msconfig>boot advanced options>maximum memory" from "4096" to "34" after she restarted the laptop the blue screen appeared i tried system restore,startup repair and command prompt but nothing worked for me.


Please help if you know how to fix it without losing any files, Thank you.

:)

 

Accidently disabled all services via msconfig

I was trying to debug explorer hangs and accidently disabled all services via msconfig. Now the Windows 10 boots up but there is no login screen. Trying to get into safe mode but shift+restart does not work.

How can I restore my system back to working condition?

 

msconfig doesn't save changes


Dang. Well, if you haven't already done so, search on a search engine (such as Bing) for your issue for more suggestions that you can find. I searched for:

msconfig doesn't save changes


and gave you that link. Hopefully you can try other suggestions that were attempted by others. There's a bunch of results that you will find, so hopefully that variety of results will have something useful.

 

Overclocking / Undervolting guide for Vega 56 or 64?

Here's a quick laundry list:

List of software to use for overclocking and testing
Examples:
Wattman (and how to find and use it, like an overview, including profiles)
Unigine Valley or Heaven (use this for quick testing while changing settings in Wattman and checking for stability / artifacts) ...just suggesting this
How to monitor cores / mem speeds and temps during testing (I've seen screen overlays, and others using GPUz)

Step-by step overclocking in Wattman
Fan speeds
Power limit
Temp limit
Voltages
Core speeds
Memory speeds