Very strange.
All dumps to date, even verifier_enabled ones, have searchindexer as the running process.
Honestly, the dumps point toward a software problem.
Where did you get your copy of Windows 7?
Try disabling Search. Search for "features" in the start menu, and select "Turn Windows features on or off".
Make sure the highlighted box is Clear:
Attachment 99147
I just don't get how it can pass hardware stress tests, run xp perfectly, but crash with win7 in a matter of minutes.
I'll try turning off windows search and I'll keep you updated.
I got my copy of win7 from newegg.
Well ran some typical apps that would always make win7 crash and it's still up... However it just seems like a band-aid fix. Turning off the indexing service won't affect me in the least, but knowing there is something wrong is a bit worrying.
I'll leave a benchmark running overnight and while I'm at work, but I'm pretty confident that you've solved the problem. I asked a friend if I could borrow his motherboard (Same board different revision) to ease my curiosity so I'll do another install sometime this week.
Yes - it is a bit of a stop-gap fix.
Try running the System File Checker (SFC) and Check Disk.
START -> type cmd.exe -> Right-click -> run as admin -> type sfc /scanonce -> restart computer.
Then, after the reboot
START -> type cmd.exe -> Right-click -> run as admin -> type chkdsk /r /f -> Press Y at prompt -> restart computer.
Then please follow these instructions and then upload the sfcdetails.txt file (this has the details about the SFC scan, but not the chkdsk).
How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program generates in Windows Vista
I was able to run the chkdsk but there weren't any errors.
I'm having some problems with sfc though. I can't seem to get the command prompt to open to an elevated level. I'm doing: Start > All Programs > Accessories > Right click on Command Prompt > Run as administrator.
Cmd still opens to Users\<username>. There isn't any option to do sfc /scanonce but I can do a sfc /scannow and that didn't have any errors after completing. Or I just did it completely wrong.
When I did the findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >sfcdetails.txt it doesn't look like it does anything. I obviously cannot search for the file manually :P I'll try doing the sfc in safe mode.
Yeah - try SFC in safe mode with sfc /scannow
Gah, so I couldn't open an elevated cmd because I had UAC turned off. Running that sfc now.
Last edited by Geotech; 22 Sep 2010 at 00:26. Reason: sfcdetails
That SFC log looks fine.
Run that chkdsk?
Yup, chkdsk was also error free. I found the culprit though. I was able to test another motherboard and did a fresh install. With Windows Search enabled there hasn't been a single crash at all. Before a fresh install crashed even before doing windows or driver updates.
Everything in the bios is exactly the same as my old motherboard so it wasn't my memory timing or voltage. We stuck my old motherboard in my friends system and bam Ntkrnlmp.exe. As I was swapping out motherboards I noticed the northbridge heatsink from my motherboard would rock back and fourth AS you moved the board. Sadly even after artic silver and reseating the heatsink the problem still persisted. I guess after overheating numerous times something screwed up, yet mysteriously only affected Win7 haha.
I'd like to thank you wonderful people for volunteering your free time to help me out. Very reassuring there are experienced and helpful people like you guys around.
PS. Is there a way to change the thread title to "BSOD ntkrnlmp.exe"?
No problem, we are here to help in any way possible.
The thread title change? Not without Admin involvement - and they already have plenty to do.
Anyway - the name doesn't really matter as there are literally hundreds of possible causes if ntkrnlmp.exe is blamed, it is better for anyone else looking for help to create a new thread so we can have a look at the info.
Quote