May 28, 2020

Fix KMODE_EXCEPTION_NOT_HANDLED BSOD Error

KMODE_EXCEPTION_NOT_HANDLED commonly occur when there is conflict between 2 component, and in most cases for HP PCs is HP software component (Touchpoint Analytics Client) and (Updated) Windows Defender. Although there are no rock solid solution, people had been sharing what they did to fix the problem and here I list out what best to start fixing it and how to proceed if the problem still persist.

Run windows updates - HP Software Component 4.1.4.3079

Run Windows automatic updates because this updates released by HP to fix BSOD from the KB4556799. This updates available for WIndows 10 ver 1903 and 1909. This would also fix the boot loop.

Disable Windows Defender.

Although it is not an effective steps to take, however you could use a third party antivirus to replace current Windows Defender. Here is how to disable Windows Defender:

  1. Go to troubleshoot - advanced options - command prompt.
  2. Login with your password
  3. In the command prompt enter regedit and press enter.
  4. Double-click hkey local machine
  5. Click file - load hive
  6. Browse to C( was D in my recovery environment):\windows\system32\config
  7. Open software
  8. Enter a Key Name, I used temp
  9. Open the temp key, then expand policies - Microsoft - windows defender
  10. Create a 32bit dword DisableAntiSpyware. Set it to 1
  11. Right click windows defender in the left and create a new key Real-Time Protection and create these 32 bit dwords set to 1
  12. DisableBehaviorMonitoring
  13. DisableOnAccessProtection
  14. DisableScanOnRealtimeEnable
  15. Scroll back up and highlight the temp key, and then click file unload hive.
  16. Then highlight hkey local machine again, and choose load hive. This time load system from the same location, and set 
  17. Temp\contolset001\services\windefend start to 4
Whats Next?

Now the best this to do if you still have the problem is to reset you PC, and then pause Windows updates. this way you can avoid Windows Defender to update the component that cause the BSOD.

No comments:

Post a Comment