Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

KMODE_EXCEPTION_NOT_HANDLED on Windows 10 with Windows Hello


  • Please log in to reply
1 reply to this topic

#1 sadisticpotato

sadisticpotato

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:09:20 AM

Posted 16 May 2016 - 05:41 AM

Hello, I'm having some issues with getting Windows Hello to work on my SP4. The computer is randomly bluescreening when I try and login with Windows Hello from the lock screen with the error code "KMODE_EXCEPTION_NOT_HANDLED." Also, when I try and improve the recognition through the settings app, the process stops responding, but the recognition appears to work.

 

It's been an issue since I upgraded to Insider Preview build 14342, but I've only found one person that seems to have a similar issue.

 

Event viewer logs (regarding the Settings app glitch):

 

Faulting application name: BioEnrollmentHost.exe, version: 10.0.10011.16384, time stamp: 0x572d5b08
Faulting module name: BioEnrollmentUI.dll, version: 0.0.0.0, time stamp: 0x572d595d
Exception code: 0x80000003
Fault offset: 0x0000000000022164
Faulting process id: 0x1238
Faulting application start time: 0x01d1af5d86f1f8a8
Faulting application path: C:\Windows\SystemApps\Microsoft.BioEnrollment_cw5n1h2txyewy\BioEnrollmentHost.exe
Faulting module path: C:\Windows\SystemApps\Microsoft.BioEnrollment_cw5n1h2txyewy\BioEnrollmentUI.dll
Report Id: 7cfb8937-9d62-4f3e-9532-5dfd53d2cba5
Faulting package full name: Microsoft.BioEnrollment_10.0.14342.1000_neutral__cw5n1h2txyewy
Faulting package-relative application ID: App

 

Faulting application name: CredentialUIBroker.exe, version: 10.0.14342.1000, time stamp: 0x572d5b73
Faulting module name: BioCredProv.dll, version: 10.0.14342.1000, time stamp: 0x572d594d
Exception code: 0xc0000409
Fault offset: 0x000000000001786b
Faulting process id: 0x734
Faulting application start time: 0x01d1af5d8a1987fd
Faulting application path: C:\Windows\System32\CredentialUIBroker.exe
Faulting module path: C:\WINDOWS\System32\BioCredProv.dll
Report Id: a82b9182-883b-4bbf-8c9e-3912489aadb6
Faulting package full name:
Faulting package-relative application ID:

 

Faulting application name: CredentialUIBroker.exe, version: 10.0.14342.1000, time stamp: 0x572d5b73
Faulting module name: BioCredProv.dll, version: 10.0.14342.1000, time stamp: 0x572d594d
Exception code: 0xc0000409
Fault offset: 0x000000000001786b
Faulting process id: 0x1fbc
Faulting application start time: 0x01d1af5d37be009c
Faulting application path: C:\Windows\System32\CredentialUIBroker.exe
Faulting module path: C:\WINDOWS\System32\BioCredProv.dll
Report Id: 5316cf77-c1cb-472a-9e1d-c4d9d08d981d
Faulting package full name:
Faulting package-relative application ID:

 

Faulting application name: BioEnrollmentHost.exe, version: 10.0.10011.16384, time stamp: 0x572d5b08
Faulting module name: BioEnrollmentUI.dll, version: 0.0.0.0, time stamp: 0x572d595d
Exception code: 0x80000003
Fault offset: 0x0000000000022164
Faulting process id: 0x5b4
Faulting application start time: 0x01d1af5d22c956a3
Faulting application path: C:\Windows\SystemApps\Microsoft.BioEnrollment_cw5n1h2txyewy\BioEnrollmentHost.exe
Faulting module path: C:\Windows\SystemApps\Microsoft.BioEnrollment_cw5n1h2txyewy\BioEnrollmentUI.dll
Report Id: 3b2b4105-e2e8-4da3-afe4-7700702bf177
Faulting package full name: Microsoft.BioEnrollment_10.0.14342.1000_neutral__cw5n1h2txyewy
Faulting package-relative application ID: App

 

Faulting application name: CredentialUIBroker.exe, version: 10.0.14342.1000, time stamp: 0x572d5b73
Faulting module name: BioCredProv.dll, version: 10.0.14342.1000, time stamp: 0x572d594d
Exception code: 0xc0000409
Fault offset: 0x000000000001786b
Faulting process id: 0x1564
Faulting application start time: 0x01d1af5d241c1813
Faulting application path: C:\Windows\System32\CredentialUIBroker.exe
Faulting module path: C:\WINDOWS\System32\BioCredProv.dll
Report Id: b4605252-420f-4b91-a2af-4ff360ff8829
Faulting package full name:
Faulting package-relative application ID:

 



BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:01:20 AM

Posted 17 May 2016 - 09:15 AM

Please run this report collecting tool so that we can provide a complete analysis:  http://omgdebugging.com/bsod-inspector/
When done a Notepad document will open with the name of the file and it's location. (By default it'll be a .zip file located on your Desktop)
Simply upload the .zip file with your next post and we'll move on from there.

If it doesn't work for you, then please try this:  http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/



 


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users