Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD "KMODE_EXCEPTION_NOT_HANDLED" ntkrnlmp.exe

25 Nov 2012   #11
x BlueRobot

 

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: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:CPU: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: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.


My System SpecsSystem Spec
.
25 Nov 2012   #12
Cuahchic

Windows 7 64-bit
 
 

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
My System SpecsSystem Spec
25 Nov 2012   #13
x BlueRobot

 

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.
My System SpecsSystem Spec
.

25 Nov 2012   #14
x BlueRobot

 

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
Make sure you have the latest and compatible DirectX runtime for your system.

From the 4th of November (above BSOD)
My System SpecsSystem Spec
04 Dec 2012   #15
Cuahchic

Windows 7 64-bit
 
 

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):
  1. prime95 - Ran small FFT test for > 2 hours, no stopped workers etc.
  2. FurMark - Ran for > 20 mins (until temperature levelled out) with no artefacts or crazy temperature issues.
  3. SFC - Tried this twice off Windows boot disk and both times it found nothing.
  4. 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
My System SpecsSystem Spec
04 Dec 2012   #16
x BlueRobot

 

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.
My System SpecsSystem Spec
12 Jun 2013   #17
Cuahchic

Windows 7 64-bit
 
 

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.
My System SpecsSystem Spec
13 Jun 2013   #18
x BlueRobot

 

Congratulations on solving your problem Cuahchic
My System SpecsSystem Spec
13 Jun 2013   #19
Cuahchic

Windows 7 64-bit
 
 

Thanks again for your help.
My System SpecsSystem Spec
13 Jun 2013   #20
x BlueRobot

 

Welcome
My System SpecsSystem Spec
Reply

 BSOD "KMODE_EXCEPTION_NOT_HANDLED" ntkrnlmp.exe




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
"Random" BSODs. Sometimes ntkrnlmp.exe but mostly ntoskrnl.exe
Hello, all. I don't have much experience diagnosing these issues; fortunately all my machines current and past have been solid. Unfortunately the machine I put together for work is BSODing with no pattern I can recognize -- sometimes she'll run fine for a few weeks other times she'll crash a few...
BSOD Help and Support
BSOD - "ntkrnlmp.exe" and "ntoskrnl.exe" are the cause
Hello all, a friend was helping me to find out what this BSOD all of a sudden was from but he is out of the country now away on business. We got the point of him looking at the crash files and us using WhoCrashed, and we found that the last handful of crashes I have are all caused by...
BSOD Help and Support
"ntkrnlmp.exe" related BSOD
I bought recently this PC and it had this problem from the beginning. I tested the hardware (except power supply) and everything is working, yet i'm still getting BSOD from time to time. If you have any idea what's happening please tell me! sorry for my english
BSOD Help and Support
BSOD random "Probably caused by : ntkrnlmp.exe"
So I randomly get a BSOD, sometimes while sitting idle, other times just running firefox. Used to happen frequently trying to run SolidWorks and was a Nvidia graphics issue I though- Reformatted machine with new ATI card and now have this problem. Hopefully someone can decipher the below...
BSOD Help and Support
BSOD when using RDP error: "KMODE_EXCEPTION_NOT_HANDLED" ntoskrnl.exe
Hi, My issue is to do with accessing my PC via RDP, I have a work PC which I should be able to access via RDP (mstsc) however whenever I attempt RDP access to my work PC from another, my work PC blue screens reboots, and then allows me access once rebooted. It will still grant me RDP access for...
BSOD Help and Support
BSOD when gaming "ntkrnlmp.exe"?? HELP please
I'm running windows 7 x64 pro and during gaming, at random times a BSOD would appear and the only useful info i found on the blue screen is that is says "ntkrnlmp.exe" and IRQL_not less or equal. I updated my bios and drivers and I have tested my memory using the windows memory test overnight...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 01:00.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App