BSOD "KMODE_EXCEPTION_NOT_HANDLED" ntkrnlmp.exe

x BlueRobot · 25 Nov 2012

Good work so far :)

csrss.exe is the real version of the Windows file which is good, and your hard-drive is in good working order also. I wouldn't worry with moving the RAM sticks, I usually recommend it when MemTest86+ finds some errors, but in this case it seems to be fine.

A few of your crashes pointed to hardware issues, so you could run a few stress tests to make sure it isn't a 'false positive':

Graphics Card:

Video Card - Stress Test with Furmark

Read all the steps within the hardware test tutorials very carefully, as stress tests is designed run components to their maximum capacity, in order to point out failing or faulty hardware components.

Use the following program to monitor your hardware temperatures during the stress test:

CPUID HWMonitor

CPU:

Hardware - Stress Test With Prime95

High Definition Audio Device:

Code:

HDAUDIO \FUNC_01&VEN_8086&DEV_2806&SUBSYS_80860101&REV_1000\4&36B8CB0&0&0301	This device cannot start.

Code:

c:\windows\system32\drivers\hdaudio.sys (6.1.7601.17514, 342.00 KB (350,208 bytes), 21/11/2010 03:23)

This device is produced by Microsoft and will be taken as part of the operating system, run:

SFC /SCANNOW : Run in Command Prompt at Boot

System File Checker scan for corrupted and missing protected Windows files, and attempts to repair or replace these files automatically from within the operating system itself if possible.

Cuahchic · 25 Nov 2012

Hi x BlueRobot,

Thanks again for posting. Unfortunately, I am away with work without internet access and this will be my last post until Saturday 1st December, but I will try all your suggestions before posting back.

I have used prime95 before and already have it, I have set the CPU back to the default values (no overclock) and therefore will retry to ensure it's stable, but I am 99% certain it will pass as it passed when overclocked. I haven't used the GPU stress tester, I haven't modified my GPU in any way. Anyway, I will try both of these to rule them out!

A couple of questions to help me understand the process:

You have mentioned on a few occasions that you are seeing hardware faults. Can you please point me to where it tells me this in the logs?
Are these hardware faults pre-September 2012? If so, this could be caused by an unstable overclock. I got greedy and tried to run at 4.4GHz but I had major stability issues, so around Sept 2012 I reverted to the stable 4.2GHz. (At the moment I am running at the default ~3.5GHz)
I realise we still have hardware items to rule out, but are you seeing any software/driver issues?

Thanks again for the assistance and speak to you on Dec 1st.

Cheers,

Colin

x BlueRobot · 25 Nov 2012

Code:

BugCheck 124, {0, fffffa800705e028, f2000040, 10005}

Probably caused by : GenuineIntel

The Stop 0x124 is a hardware BSOD, in rare circumstances a faulty driver can cause a 'false-positive', and the GenuineIntel line is a generic probably caused line produced by Stop 0x124 crashes.

Code:

BugCheck 3B, {c0000005, fffff80002fd9d7e, fffff88009986b20, 0}

Probably caused by : hardware ( nt!ObpLookupDirectoryEntry+8e )

There was a few other Stop 0x3B BSODs, however these are all pre-September (July 2012), so these were most probably produced when you were overclocking your hardware.

The only driver issues I've mentioned to you so far were related to AVG, however did notice one or two pointing to DirectX, and will have to look through your dumps again.

x BlueRobot · 25 Nov 2012

Code:

BugCheck 50, {fffffffffa0f2ce8, 0, fffff80002f86995, 2}


Could not read faulting driver name
Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGFASTMUTEX::Acquire+13 )

Code:

DirectX Graphics Kernel

How to download and install DirectX

Make sure you have the latest and compatible DirectX runtime for your system.

From the 4th of November (above BSOD)

Cuahchic · 04 Dec 2012

Hi x BlueRobot,

Apologies for my delayed response but had to deal with a few items upon my return from my work trip. Here is what I have done (see attached screenshots):

prime95 - Ran small FFT test for > 2 hours, no stopped workers etc.
FurMark - Ran for > 20 mins (until temperature levelled out) with no artefacts or crazy temperature issues.
SFC - Tried this twice off Windows boot disk and both times it found nothing.
Confirmed my Direct X version is up-to-date.

So I think that although no test is perfect we can rule out an unstable processor and/or graphics card.

The strange thing about the audio device in device manager is this appears to be an issue with the motherboard I have, see this post: First Ever Build! - Page 3 - [H]ard|Forum. It'd be nice to solve this but it's less important than the BSOD crashes.

So it's looking more like a driver issue than hardware...any more ideas? I haven't had any additional crashes recently but will add more dumps if any do occur.

Again, many thanks for all your assistance.

Cheers,

Colin

x BlueRobot · 04 Dec 2012

At least no BSODs have occured recently :)

Run Driver Verifier for at least 24 hours, it will place stress on your drivers, and cause any corrupted drivers to act out and cause a crash (i.e. BSOD), hopefully this will pinpoint the exact driver(s) causing the problem.

Driver Verifier - Enable and Disable

Cuahchic · 12 Jun 2013

Hi all (especially x BlueRobot),

I know it's been some time since I last posted. but I believe I fixed this problem, therefore I thought that I'd share how I fixed it in case someone else has the same problems.

Firstly a quick update. When we last spoke in December 2012, I tried the Driver Verifier option as you suggested. However, I ran the machine for a short time (probably 6-8 hours) with it on and didn't get a single BSOD. At this stage I was pretty fed up with the machine and had accepted that the problem would never be solved.

So I continued using the machine with the BSOD events occurring infrequently. In around May 2013 the BSOD events got a lot worse, where they were happening 2-3 times per day. I got totally fed up and reinstalled Windows and reinstalled all my programs. Sadly, this did not solve the problems, and infrequent BSODs continued.

I realised that I had to do methodical testing on all components (again!). I have attached all the tests I did including a spreadsheet [edit: I couldn't get this to upload?] I created for methodical testing purposes. However, when I tested the HDD, RAM, CPU and GPU no failures were detected! Frustrated, I decided to try Driver Verifier again.

So I enabled Driver Verifier, and ran the PC for a bit. Nothing happened. However, this time I kept running it and I got a couple of BSODs pointing to Windows services, which wasn't very helpful. Eventually, turning the machine on one day I got 3 or 4 BSODs in a row. When viewing the logs, I noticed that the driver Pxhlpa64.sys was mentioned. That was the "Eureka!" moment.

When I did a bit of research into this driver, I found many people complaining about this driver (example). My understanding is that it was installed as part of Adobe Premier Elements which I installed again when I reinstalled Windows.

I followed the instructions in this thread on the Microsoft forums and I have been running the machine for about 2 weeks without a single BSOD!

I hope this might have helped someone. What I learned was that it is worth persevering with these problems even if you do lose hope at times!

I would like to say a big thanks to 'x BlueRobot' for all his/her help.

x BlueRobot · 13 Jun 2013

Congratulations on solving your problem Cuahchic

Cuahchic · 13 Jun 2013

Thanks again for your help.

x BlueRobot · 13 Jun 2013

Welcome :)