BSOD Ntoskrnl.exe

-64 bit Win7 Home Premium
-Fresh install (9-17-10)
-Full Retail version
-System is about a year and a half old
-Two day old install.

I've been dealing with my win7 bsod for two months now and after reinstalling and changing various hardware out I'm all out of ideas. So far I've changed memory, power supply, reinstalled and messed with various bios settings dealing with ram timings and voltages. My most stable settings are memory set to EPP, voltage 2.075 and +.075 to the North bridge. However this is only stable enough to do light browsing and checking email. As soon as I fire up a game or try a stress test I'll get a bsod.

My system wasn't always like this. It only happened after I left my system off for about a week while I went on vacation. When I got back my system wouldn't even boot up. I had to reset the bios and put everything on auto. Every single time I get a bsod it's always from ntkrnlmp.exe or ntoskrnl.exe. I can get it while checking e-mail, right after a reboot, surfing the net, and just idle. It's just really random. I usually can't get an uptime of over four hours.

I thought it was my memory at first so I did a memtest86+ overnight and while at work for a total of 18 hours and not one error. I've tried various benchmarks and stess test programs but those always bsod after a few hours. I took the plunge and bought another set of 2x2gb memory which obviously didn't fix the problem.

The bsod only occurs while under Win7. I have XP 32bit dual booted and I can play games and do stess tests on that ALL day. I really don't want to go back to XP since I'm so comfortable with win7 but this is really bothering me.

All my various updates are current. Chipset, graphics, sound, etc etc. The only things I have installed after my fresh install are firefox, thunderbird, Steam and windows debugging tools + symbols. Even after a fresh install I got a bsod while downloading firefox...

I don't exactly know what to look for when looking into crash dumps so I'm asking for help. Any help would be greatly appreciated.

I wonder if hard drive is the cause. XP is on a different hard drive, which may explain why it does not get BSODs.

I notice in all BSODs from today, SearchIndexer was running. Granted, this is a fresh install, so it has much indexing to do. However, it is still worth noting...lots of hard drive activity!

Test your Western Digital hard drive with Data Lifeguard Tools: WD Support > Downloads > SATA & SAS > WD Caviar Black

...Summary of the Dumps:

Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Sep 18 21:43:29.536 2010 (UTC - 4:00)
System Uptime: 0 days 0:40:08.002
BugCheck A, {ffffda000e810160, 2, 0, fffff8000305ed5b}
Probably caused by : ntkrnlmp.exe ( nt!KeUnstackDetachProcess+13b )
BUGCHECK_STR:  0xA
PROCESS_NAME:  SearchIndexer.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Sep 18 21:01:47.535 2010 (UTC - 4:00)
System Uptime: 0 days 0:49:10.000
BugCheck A, {ffffda000e9c0160, 2, 0, fffff8000304ed5b}
Probably caused by : ntkrnlmp.exe ( nt!KeUnstackDetachProcess+13b )
BUGCHECK_STR:  0xA
PROCESS_NAME:  SearchIndexer.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Sep 18 18:18:57.848 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:10.002
BugCheck A, {ffffda000e602160, 2, 0, fffff80002e50d5b}
Probably caused by : ntkrnlmp.exe ( nt!KeUnstackDetachProcess+13b )
BUGCHECK_STR:  0xA
PROCESS_NAME:  SearchIndexer.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Sep 18 18:16:12.624 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:29.012
BugCheck A, {ffffda000ee0e160, 2, 0, fffff80002c9cd5b}
Probably caused by : ntkrnlmp.exe ( nt!KeUnstackDetachProcess+13b )
BUGCHECK_STR:  0xA
PROCESS_NAME:  SearchIndexer.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Sep 18 18:11:53.617 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:06.004
BugCheck A, {ffffda000e61d160, 2, 0, fffff80002cabd5b}
Probably caused by : ntkrnlmp.exe ( nt!KeUnstackDetachProcess+13b )
BUGCHECK_STR:  0xA
PROCESS_NAME:  SearchIndexer.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Sep 18 07:27:01.536 2010 (UTC - 4:00)
System Uptime: 0 days 2:50:56.001
BugCheck A, {ffffda000e61c160, 2, 0, fffff80002ca6d5b}
Probably caused by : ntkrnlmp.exe ( nt!KeUnstackDetachProcess+13b )
BUGCHECK_STR:  0xA
PROCESS_NAME:  SearchIndexer.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Sep 18 04:17:45.035 2010 (UTC - 4:00)
System Uptime: 0 days 0:34:23.001
BugCheck A, {ffffda000566a160, 2, 0, fffff80002ca8d5b}
Probably caused by : ntkrnlmp.exe ( nt!KeUnstackDetachProcess+13b )
BUGCHECK_STR:  0xA
PROCESS_NAME:  SearchIndexer.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

Run driver verifier: Driver Verifier - Enable and Disable

Good luck, keep us posted!

Came back and my pc had restarted from a bsod with driver verifier running, another ntkrnlmp.exe.