Kmode_exception_not_handled

fahro · 23 Feb 2014

How do I solv this problem
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
Hardware: INTEL_, Intel Corporation, DQ965GF
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU E4600 @ 2.40GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4225486848 total
VM: 2147352576, free: 1985138688

Crash Dump Analysis
crash dump file: C:\Windows\Minidump\022314-16656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000A8E490, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe

Thedoctor44 · 23 Feb 2014

Unfortunately I don't analyse crash dumps but you mention kmode_exception_not_handled which is a very common bug check. This indicates faulty hardware or incompatible hardware. Or a faulty device driver has corrupted the system. You also mentioned memory management, these are two different bug checks. From what it looks like I think it could be faulty RAM, try running memtest86 for at least 7 passes.

Follow these instructions:

RAM - Test with Memtest86+

Golden · 23 Feb 2014

I agree with running Memtest86+......run for 8 instead of 7 passes. I will look at the dmp files in more detail when I get home this evening.

Golden · 25 Feb 2014

Code:

Host Name:                 AMINA-PC
OS Name:                   Microsoft Windows 7 Ultimate 
OS Version:                6.1.7600 N/A Build 7600

Update Windows 7 fully - check Optional updates too.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a00bc93bd8, 0, fffff880012444e0, 2}


Could not read faulting driver name
Probably caused by : Ntfs.sys ( Ntfs!memcpy+250 )

Followup: MachineOwner
---------

Run MemTest86+ as recommended earlier.