KMODE_EXCEPTION_NOT_HANDLED BSOD Please Help

[MeesterYellow]

Hello,

My sister had a few BSODs on her laptop and I wanted to try and help her fix the problem. I ran WhoCrashed on it and came up with this:

Welcome to WhoCrashed (HOME EDITION) v 5.53
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution.

Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue or black screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...



--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.

Please note that this version of WhoCrashed is not licensed for use by professional support engineers.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.


--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

Computer name: NGOCHA-LAPTOP
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: HP EliteBook 8540p, Hewlett-Packard, 1521
CPU: GenuineIntel Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4149555200 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 2/20/2017 7:14:23 PM your computer crashed
crash dump file: C:\Windows\Minidump\022017-13977-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70400)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x7FEE3D82E82, 0x0, 0x35C10000615D)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 2/20/2017 7:14:23 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x7FEE3D82E82, 0x0, 0x35C10000615D)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 2/19/2017 12:54:14 PM your computer crashed
crash dump file: C:\Windows\Minidump\021917-12729-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70400)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x7FEE8482E82, 0x0, 0x73E10000D46F)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 2/13/2017 8:36:13 PM your computer crashed
crash dump file: C:\Windows\Minidump\021317-12698-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70400)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x7FEEAF52E82, 0x0, 0x4A260000E8E9)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 2/6/2017 8:53:03 PM your computer crashed
crash dump file: C:\Windows\Minidump\020617-12589-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70400)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x7FEDC2B2E82, 0x0, 0x6C200001FBB)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

9 crash dumps have been found and analyzed. Only 5 are included in this report. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.


How can we fix this?

 

[scout_03]

do a sfc/scannow and after go to hp with is laptop model and number to update all driver .

 

[MeesterYellow]

Sorry for not reporting back. I will follow your instructions with her laptop once she has time and will report back to you. She's very busy with her school work.

 

[scout_03]

be around .

 

[MeesterYellow]

be around .

Okay.

 

[MeesterYellow]

be around .

Okay, so the sfc /scannow's result was:
Windows Resource Protection did not find any integrity violations.

 

[johnbl]

C0000005 is a error code that means a bad memory address was passed to a driver.
all of your memory dumps showed this error code. You should run memtest on its own boot image to confirm your memory timings are correct. if memtest works as expected you should put your actual memory dumps on a server like microsoft one drive, share them for public access and post a link to them here.

generally, to attempt to fix this you would update the BIOS and all of the motherboard drivers from the motherboard vendor. I would suggest you do this first before running memtest just because if memtest finds a problem you have to update the BIOS to attempt a fix anyway and rerun memtest to confirm the fix worked.

 

[Jwpanz]

Exceptions not handled are a sign of video drivers causing problems. Try updating or reinstalling the video driver from device manager.