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-various culprits but ntkrnlmp.exe is common,clean install,no cure

30 Dec 2013   #1
nilojones

win 7 64bit pro
 
 
BSOD-various culprits but ntkrnlmp.exe is common,clean install,no cure

Hello, merry xmas.
Sorry to just jump straight in with a problem, but this has been bugging for months now until yesterday when 5 bsod's in a day. I use my PC for music production, video editing and photoshop so can push it pretty hard at times and it is (was) a pretty stable system - a random bsod once a month or so.

I have spent hours reading forums but just do not have the knowledge to figure it all out - windbg is mystical to those not in the know, i am hoping one of you clever people can help I have not installed any new software or hardware, excluding a D-link usb hub and denon mixer which has not been on at any point.

The history:
In the last year I had a system that i was happy with (as said earlier the odd crash which is all part of the windows experience in my, er, experience). I decided I wanted to upgrade to allow more ram and have access to usb 3 and 6gb sata ports. So I bought the asus m5a97 evo r2 mobo - everything was tickety boo (good) for 3 months, I benched the gigbyte mobo and the OCZ ram - i bought corsair vengence 2 x 8gb(cmz16gx3m2a1600c10). I upgraded to the samsung evo 840, a corsair h100 and win 7 pro - no OS issues (just a bad firmware update on the ssd) but that got sorted with an RMA. I added two more sticks of RAM to the corsair vengence a couple of months later (cml16gxm32a1600c10). The ram is of different serial numbers but close enough and after reading many posts I discerned it wouldn't be a problem (and i couldn't afford 4 new sticks!)- it defaults to the slightly lower timings but as I am not overclocking and am happy with stability as opposed to speed, that is ok with me. It all worked fine - but still the odd random BSOD, no more or less than with the gigbyte mobo system and ocz ram. I started to think PSU as that is a constant. I have monitored voltages using HWmonitor for a few months now and have seen nothing that concerns me (but im no expert, just no great voltage drops that i could see). So I started to think RAM (again) even though there has been no difference between the Corsair and the OCZ in terms of stability, either with 2 sticks of same serial number or 4 sticks with slightly different serials.
Yesterday after several BSOD's and after trying to work out the cause via windbg and reading forums I thought do a clean install, not a sys image from my back up. Honestly, windbg to me is like a baby trying to read shakespear! Several hours later I got a clean system that runs, that was until I tried to run MSE to check for viruses before i made another system image - it crashed. I tried again and it did it again. I uninstalled MSE and installed Avast. I ran avast and it crashed - bsod. The same thing seems to happens with anti malware bytes: this is new! Especially as ntkrnlmp.exe keeps popping up - I attached the dumps from today (4 of them) and the files as requested (nice little tool BTW).

I have d/l memtest and will run it when I buy some dvd's and can burn the ISO - damn, no disks! I ran prime 95 for an hour today and it worked a treat, I was especially pleased to see my cpu temp never got over 48 degrees.

So now I am utterly bewildered. Ram has been changed, mobo has been changed, clean install, cool running. It doesn't crash when i am on photoshop doing 3d whilst watching media centre, running a virus scan and surfing the net. It does crash when i run an anti virus! The only constant I can think of is the hardware (a driver fault that keeps re-occuring) and the PSU. I hope its not the PSU and is a driver that one of you guys can see straight off (drivers are fully up to date) - if indeed you are kind enough to help.

If you got this far, thank you very much and have a happy new year. Thanks in advance for any help or clues.

P.s. I got Traktor dj yesterday which i have been waiting for for 3 weeks, it couldn't have happend 3 weeks ago could it?!? No point putting it on at the moment. Bloody sods law!

p.p.s I have also run chkdsk on the OS drive.

Update: I forgot to mention i have updated to the the latest bios. I just booted in safe mode and tried to malwarebytes - it crashed with the same culprit - ntkrnlmp.exe. Thanks.

Update 2: I just ran furmark GPU stress test after following this thread: BSOD from ntoskrnl when explorer.exe is open
- 10 mins and the temps levelled out at 83 degrees.

Update 3: I ran driver verifier and it would not boot - the faulting driver was niwincdemu.sys which is form native instruments. I will uninstall all there stuff, run ccleaner and then try to run avast again. I will post back

Update 4: Ok so I found 4 instances of niwincdemu.sys on my system. I renamed 3 of them, one would not let me, restarted and ran malwarebytes and avast at the same time - NO CRASH! I did not delete their software, just a renamed the faulting file. So now I am unsure whether that driver has always been the issue (it would make sense as their software has always been on my system) or whether there is still another problem that is concerned with hardware. Are niwincdemu.sys and ntkrnlmp.exe related in some way? All I have now is a yellow exclamation mark in device mnaager under storage controller: ISO mounter (which is preferable to instability). Any techhie harry potter have any ideas. illuminatus. Cheers. BTW no viruses or malware found on any drive.


My System SpecsSystem Spec
.
30 Dec 2013   #2
matts6887

Windows 7 ultimate 64-bit
 
 

So; did what you did above in renaming the 2 of the 3 files with no crash work to solve your issue; or is there still a underlying issue left to solve; cause it seems like you may have solved your own issue?
My System SpecsSystem Spec
30 Dec 2013   #3
nilojones

win 7 64bit pro
 
 

Quote   Quote: Originally Posted by matts6887 View Post
So; did what you did above in renaming the 2 of the 3 files with no crash work to solve your issue; or is there still a underlying issue left to solve; cause it seems like you may have solved your own issue?
Merry xmas, thanks for the reply.
I really do not know? arghh. For the last 2 hours no issues and no crash. It could have been that driver all along but time will tell on that one. As i said, i am no expert and windbg is mystical - i was hoping that someone cleverer than me (not hard) would shed some technical light on the situation by analysing the dmp files. For now I can run virus scans and for 2 hours firefox or IE have not restarted; another recent issue. So things are looking better - are they fixed? I am unable to say right now, time will tell. I still have the yellow exclamation mark but have sent a ticket to Native intruments - but in my experince they are not very good at replying.

It would be nice if someone could confirm, deny or support my theory - i posted the updates so other people might benefit if they have similar probs. I am just taking a stab in the dark. poke, poke, stab
My System SpecsSystem Spec
.

31 Dec 2013   #4
nilojones

win 7 64bit pro
 
 

Hello again,
So i ran memtest v4.3.6 overnight but am unsure what the results mean. Most threads I have been reading say errors appear in red. But my results still say errors. Can anyone help? Is a stick of my ram screwy? Any ideas which one or should I test each stick individually?
Thanks.
My System SpecsSystem Spec
01 Jan 2014   #5
nilojones

win 7 64bit pro
 
 

OK, so I decided to do another clean install. Loaded all the basic stuff on (no progs) and 3 BSOD's when trying to scan the system with malware bytes and antivirus. I tried it with just the 2 newer sticks in and it went BSOD. I have just one stick in at the moment (old) and I have managed to get through the scans.

Can someone help me to conclude that the ram is to blame please? I take it the pic above does mean faulty stick!

Thanks.
My System SpecsSystem Spec
01 Jan 2014   #6
matts6887

Windows 7 ultimate 64-bit
 
 

It does sound like the ram could be a probable cause. Otherwise there may be some other
Piece of hardware that's also on the fritz like possibly the CPU.
My System SpecsSystem Spec
01 Jan 2014   #7
nilojones

win 7 64bit pro
 
 

Quote   Quote: Originally Posted by matts6887 View Post
It does sound like the ram could be a probable cause. Otherwise there may be some other
Piece of hardware that's also on the fritz like possibly the CPU.
How do I test the cpu? It's never easy. Tomorrow I will swap the RAM with the newer stuff only and see if it crashes, if it does I will run memtest (although I have no ideas what the answers mean) on that ram alone, but so far it's running sweet with no BSOD in 4 hours.

Does that memtest pic look like ram to you?

Thanks v much for the help
My System SpecsSystem Spec
Reply

 BSOD-various culprits but ntkrnlmp.exe is common,clean install,no cure




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Burned CD music skipping--multiple culprits possible
I used ImgBurn to burn some MP3s to a CD. Once burned most skip, with blank bits of silence (they sound perfect on the PC players). Even though the burner was tested to check everything and was used at half its speed. I then, just for testing purposes took those same MP3s and put them through...
Sound & Audio
BSOD's after clean install
Hi all, Since installing W7 Ultimate 64bit SP1, on my Desktop, I have experience 5 BSOD's within a 10 day period. There doesn't seem to be any particular point in time or anything--just random---and the BSOD disappears before I get chance to read the Code. I'm left with no choice but to...
BSOD Help and Support
Various BSOD after clean install
Please Help I have had to re install Windows 7 64 bit today on a clients PC. Since the install has completed i have had various BSOD including SYSTEM_SERVICE_EXCEPTION NTFS_FILE_SYSTEM and just now BAD_POOL_HEADER
BSOD Help and Support
What are the most common repair install issues/errors
Going to try my first attempt at a repair install based on the tutorial. Have a Win 7 Pro 32bit system. Have read thru Brinks tutorial pretty thoroughly but I'm wondering: 1) Assuming a successful system repair...how long should the whole operation take ? 2) Other than the SP1 issue -...
Installation & Setup
Restores didn't cure my BSOD 0x0000007E
Well, 0x0000007E was the most recent...also have had 0x0000001A, and perhaps more. I have had a BSOD almost every day for weeks, and no amount of restoring the system back has been able to fix it. I don't know what most of the information in the attached files means, but I can tell you my mouse...
BSOD Help and Support
BSODs- tcpip.sys and netio.sys the most common culprits
Over the last week or so, I've had 22 BSODs, out of which most signified errors with tcpip.sys and netio.sys. I followed the advice of a user with a similar problem and set up a static IP through the IPv4 properties of my network adapter, which was a potential solution for fixing the netio.sys...
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 07:33.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App