Connected Standby Causing Buchecks - Workaround Included

Hello Windows Insiders,

As part of today's 14328 build, there is a known issue that will cause a bugcheck (and reboot) for machines capable of utilizing connected standby functionality, such as the Surface Book, Surface Pro 4, etc.

There is a workaround for this issue.  Please make the two following registry changes:

Registry Key 1

Before:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\8619B916-E004-4dd8-9B66-DAE86F806698\60C07FE1-0556-45CF-9903-D56E32210242\DefaultPowerSchemeValues\381b4222-f694-41f0-9685-ff5bb260df2e]

"DcSettingIndex"=dword:00000384

 

After:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\8619B916-E004-4dd8-9B66-DAE86F806698\60C07FE1-0556-45CF-9903-D56E32210242\DefaultPowerSchemeValues\381b4222-f694-41f0-9685-ff5bb260df2e]

"DcSettingIndex"=dword:00000000

 

Registry Key 2

Before:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\8619B916-E004-4dd8-9B66-DAE86F806698\C763EE92-71E8-4127-84EB-F6ED043A3E3D\DefaultPowerSchemeValues\381b4222-f694-41f0-9685-ff5bb260df2e]

"DcSettingIndex"=dword:0000012c

 

After:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\8619B916-E004-4dd8-9B66-DAE86F806698\C763EE92-71E8-4127-84EB-F6ED043A3E3D\DefaultPowerSchemeValues\381b4222-f694-41f0-9685-ff5bb260df2e]

"DcSettingIndex"=dword:00000000

  • Once completed,  reboot the PC for the changes to take effect.

These steps should bypass the issue and prevent the PC from hitting the bugcheck.

If there are any questions or issues in completing these steps, please post here with feedback.


Thank you as always,
Jason

 

Discussion Info


Last updated June 13, 2019 Views 3,581 Applies to:

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Does it have to be done before or after upgrading to 14328 Build?!
Bruno Blanes
I tried to do this after installing 14328 and the first section worked without issue.  The second one says "ERROR: Invalid syntax." when I try it.

Second key looks incomplete and doesn´t work either.

Please give us the correct one.

Thanks

I've been having this problem with build 14316 and won't install build 14328 til tonight. But I decided to try this and see if it works with 14316. The result was the same as SQ's reply. The 1st command executes fine but the 2nd command results in an "Invadid syntax" error. Please check, fix the syntax and repost as this problem has been causing me fits.
I've been having this problem with build 14316 and won't install build 14328 til tonight. But I decided to try this and see if it works with 14316. The result was the same as SQ's reply. The 1st command executes fine but the 2nd command results in an "Invadid syntax" error. Please check, fix the syntax and repost as this problem has been causing me fits.
2nd command is missing the parameter, parameter type, and parameter value. "DcSettingIndex" + "???"

The second registry entry gives me an error. There's no parameter I think.

Noting DA's reply of missing parameters I added ' "DcSettingIndex" /t REG_DWORD /d 0x0 /f' from the 1st command to the end of the 2nd and it completed successfully. Whether it's the correct parameters or not I don't know. But I'm going to see whether it works from now til 2am when I install 14328.

This sounded like the problem in 14316 where a crash(PAGE_FAULT_IN_NONPAGE_AREA) occurs after being idle for 10 to 15 minutes but may not be. At any rate this fix doesn't solve than problem.

Worked for my problem......

No start menu

No calendar

No action centre

Windows no longer activated............

Same problem here - the syntax of the 2nd registry value is wrong, and it's not clear what you want it to be, so adding the end of the first statement -- while it'll allow the setting to go through -- likely isn't the right solution.

Come on back, Jason, and post the right stuff! (It'd be nice to know what the change does, too.)

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.