Windows Connection Manager Crashes Computer

I'm running Win 10 1909 current through KB4541335

Lenovo thinkpad x1 Yoga 8 Gb 250 Gb SSD

The computer will flicker and reboot spontaneously 6 min and 30s after a restart

Event viewer shows a Kernal-Power fault with bugcheckcode 126

In SafeMode the machine is stable indefinitely

Problem seems to be the Windows Connection Manager Service, if I disable it in MSConfig, machine is stable indefinitely

But this turns off the wifi :-(

Intel Driver manager says all drivers are up to date

Lenovo update manager flickers and reboots during attempts to update 

How can I 'update' the Windows connection manager service, without using wifi?

I would like a solution that does not involve a system reset

Hi,

It may help to look at the minidump files from the blue screen crashes ( bugcheckcode 126 indicates a 0x7E blue screen error):

https://docs.microsoft.com/en-us/windows-hardwa...

Can you zip up the minidump files in the C:\Windows\Minidump folder and make available (provide link) via a public folder on OneDrive or similar site.

Here's a link on using OneDrive:

http://windows.microsoft.com/en-ca/onedrive/sha...

If you have problems zipping the minidump files copy the minidump files to another location such as a folder on the Desktop.

Also, you do not necessarily have to zip up the minidump files, you can upload them one at a time.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Thanks for the offer to help. While I can sort the debugcode, I can't read the dump :-( 

here are the .zipped dump files

https://drive.google.com/open?id=1PIXQQ1WUktLULecTy8hSo4ZRPtkXYmPn

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

The driver that appears to cause the crash is the lci_proxykmd.sys :

BugCheck 1000007E, {ffffffffc0000005, fffff8055f739696, fffff9865c510468, fffff9865c50fcb0}

*** WARNING: Unable to verify timestamp for lci_proxykmd.sys
*** WARNING: Unable to verify timestamp for win32k.sys
Probably caused by : lci_proxykmd.sys ( lci_proxykmd+9696 )

The lci_proxykmd.sys, which appears to be dated Aug 2016, appears to be a display driver - FrescoLogic Proxy Display Driver.

Do have an external monitor connected?

If so, is the monitor connected by an adapter?

Did you install a driver for the adapter?

If so, can you try updating the driver or remove the monitor and uninstall the driver.

Similar error in the following topic:

https://answers.microsoft.com/en-us/windows/for...

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Thank you very much!

I uninstalled that driver (haven't used that external monitor for some while) and the unit seems stable.

 So I can learn, how did you turn the 4 hex parameters from the error (I could see them in event viewer) into the name of the .sys file?

Stay healthy, again, thanks!

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

You're welcome.

If you open a .dmp file with a debugger it gives information on the crash and sometimes identifies the offending driver.

If you want to try - install the WinDbg Preview from the Windows Store and open one of the .dmp files with the WinDbg Preview.

Click !analyze -v to analyze the .dmp file and this is in the result:

MODULE_NAME: lci_proxykmd

IMAGE_NAME: lci_proxykmd.sys

WinDbg Preview:

https://www.microsoft.com/en-us/p/windbg-previe...

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

 
 

Question Info


Last updated July 3, 2020 Views 324 Applies to: