Share via

Windows11 kmode exception not handled

Anonymous
2023-07-19T08:56:03+00:00

I am getting the KMODE_EXCEPTION_NOT_HANDLED error while working in a Windows11 environment.

Please let me know how to resolve it.

Below is a link to the zipped minidump file. https://drive.google.com/file/d/1jP5RbrkU6qQpPhrfM5BpxPntBs0KFFKL/view?usp=sharing

Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

Sakiko 39,240 Reputation points Independent Advisor
2023-07-19T09:43:17+00:00

Hello, I'm A&K, here to help.

Your dump file shows a problem with the system kernel, usually caused by the driver. We need further verification, please create a restore point for your system and then refer to the "How to start Driver Verifier" section of this article: https://learn.microsoft.com/en-us/windows-hardw..., in the third step select "Automatically select all drivers installed on this computer" to verify the driver and share the new dump file with me.

Turning on driver verification may cause your system to fail to boot, if this happens please use restore points to recover.

If the computer has any auto-overclocking feature enabled (including XMP, PBO, etc.) or manual overclocking, please restore the default first.

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Anonymous
    2023-07-24T09:14:16+00:00

    안녕하세요, 저는 A&K입니다. 도와드리겠습니다.

    덤프 파일은 일반적으로 드라이버로 인해 발생하는 시스템 커널 문제를 보여줍니다. 추가 확인이 필요합니다. 시스템의 복원 지점을 생성한 다음 이 문서의 "드라이버 확인 프로그램 시작 방법" 섹션을 참조하십시오: https ://learn.microsoft.com/en-us/windows-hardw...
    드라이버 확인을 켜면 시스템이 부팅되지 않을 수 있습니다. 이 경우 복원 지점을 사용하여 복구하십시오.
    컴퓨터에 자동 오버클러킹 기능(XMP, PBO 등 포함)이 활성화되어 있거나 수동 오버클럭킹이 있는 경우 먼저 기본값을 복원하십시오.

    We believe the issue was resolved by an update that occurred during the reboot process.

    Thank you for your response.

    Was this answer helpful?

    0 comments No comments