BSOD

[danrb]

The last two weeks I've experiencing fairly frequent (1 or 2 a day) BSODs. They are 4 or 5 different ones that happen.

I'm running the following equipment:

MSI P55-GD65
Win 7 64 bit
i7-860
Two sets of G.SKILL Ripjaws Series 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model F3-12800CL7D-4GBRM
SAPPHIRE Vapor-X 100281VX-2SR Radeon HD 5870 1GB 256-bit GDDR5
APC BR1500LCD 1500VA 865 Watts 8 Outlets BACK-UPS RS
SAMSUNG Spinpoint F3 HD103SJ 1TB 7200 RPM 32MB Cache SATA 3.0Gb/s 3.5" (raid 5)
CORSAIR HX Series CMPSU-850HX 850W
LG Black 8X BD-ROM 16X DVD-ROM 40X CD-ROM SATA
Thermaltake Armor water cooled box.

This system has been running this configuration for about 3 months. Temps are around 19 at idle and high 40s under 100% load. When the BSODs started I first ran memtest86 and found no problems. I have a second rig and swapped out the following

Replaced CPU with second i7-860.
Replaced memory with two sets of CORSAIR XMS3 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10666)
Replaced Video card with SAPPHIRE 100215L Radeon HD 3870 512MB 256-bit GDDR4
Made sure that all the drivers were up to date and tried various versions of bios.

I'm still getting BSODs. Only thing the same are Motherboard, disks, OS and PSU. I've attached my minidumps.

Thanks,

Dan

 

[CarlTR6]

Wow, 37 dump files. This will take a while. You have a variety of error codes which usually means hardware problems.

STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control


STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL (go to top of page)

Usual causes: Device driver



STOP 0x000000F5: FLTMGR_FILE_SYSTEM

The FLTMGR_FILE_SYSTEM bug check has a value of 0x000000F5. This indicates that an unrecoverable failure occurred in the Filter Manager.


STOP 0x00000034: CACHE_MANAGER

Usual causes: Insufficient physical memory, Indexing, Device driver


STOP 0x0000004E: PFN_LIST_CORRUPT

Usual causes: Device driver, ?memory


STOP 0x00000001: APC_INDEX_MISMATCH

Usual causes: Checked build kernel error. I suspect that this can be caused by something else, as I've seen 2 of these over the past several months - and none appeared to be a checked build


STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION

Usual causes: System service, Device driver, graphics driver, ?memory

BSOD Index

I looked at your dumps dated 6/5 through the latest. All are pointing to hardware problems.

 

[danrb]

My Guess is the mother board

I'm guessing the motherboard is having problems. I've RMA'd it twice so far. First on had a burnt cap. Second didn't post. This one the OC genie doesn't work. I keep the board busy 24/7. The HD is a raid 5 and is suspicious too. It's performance has been cut in half since the BSODs started.

Thanks for any help!

Dan

 

[CarlTR6]

I'm guessing the motherboard is having problems. I've RMA'd it twice so far. First on had a burnt cap. Second didn't post. This one the OC genie doesn't work. I keep the board busy 24/7. The HD is a raid 5 and is suspicious too. It's performance has been cut in half since the BSODs started.

Thanks for any help!

Dan

I only posted a smattering of the errors I found. All are hardware or driver errors. I am going to ask for help on this one since you already suspect your motherboard and your hard drive.

 

[Jonathan_King]

Could be a bad power supply unit (PSU) frying the motherboard. Could you borrow one from a friend and test it out?

Do you know how powerful your current one is?

Test your hard drive with one of these tools: HD Diagnostic

 

[CarlTR6]

You also have one very old driver that is even pre Vista, speedfan.sys Sep 24 2006. I suggest that after you diagnose your hardware you update the program this driver is associated with or uninstall it.

 

[danrb]

Could be a bad power supply unit (PSU) frying the motherboard. Could you borrow one from a friend and test it out?

Do you know how powerful your current one is?

Test your hard drive with one of these tools: HD Diagnostic

I've worried about the PSU too, if it's fried the mother board then putting a different one in won't help. I did run with a different board against this PSU for a few weeks with no problems. The PSU is 850W. Corsair HX has a good reputation, but it could be why 3 Mother boards have gone bad. Is there anyway to test a PSU? I guess I could RMA the PSU and Motherboard.

I've extensively tested the HDs. There are three in a RAID 5 configuration. Small chance, but possible the RAID controller is bad.

Thanks!

Dan

 

[Jonathan_King]

Test the PSU by seeing the number of boards it has fried!

Try updating your RAID drivers, and get a different PSU if possible. Are you hooked up to a surge protector? Do you have frequent lighting storms where you live?

 

[danrb]

You also have one very old driver that is even pre Vista, speedfan.sys Sep 24 2006. I suggest that after you diagnose your hardware you update the program this driver is associated with or uninstall it.

Speedfan.sys is the system service for Speedfan.exe. It just monitors temps. I have it running all the time. It's the latest version, but I'll try uninstalling it.

Thanks,

Dan

 

[Capt.Jack Sparrow]

Hello !!

I just looked at your Dump files McAfee seems to cause the problem. The Dump is pointing to mfehidk.sys Host Intrusion Detection Link Driver which belongs McAfee. Uninstall it completely then run the Removal Tool and make sure it comes clean.

Hope this helps,
Captain

 

[CarlTR6]

Danrb, what we are trying to do is eliminate all of the common driver conflicts to narrow down the problem. You can always reinstall speedfan and McAfee one you are up and running smoothly. If it were me, I would look for a more up to date program to monitor the temps.

 

[danrb]

No problem. I already removed speedfan.

Thanks!

 

[CarlTR6]

No problem. I already removed speedfan.

Thanks!

Very good. Please let us know what you try and the results.

 

[danrb]

Removed Speedfan, McAfee and found a newer raid drivers on the Intel site. 24 hours and no BSOD. Looking good.

Thanks!

 

[CarlTR6]

Wow, that is great news. If you get another one please upload it to us. Here's hoping that was your main hardware issue.

 

[danrb]

Well just got my latest BSOD.

 

[Tews]

Well, this new one is pretty straight forward ... memory corruption ... Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and leave it running for at least 5 passes.

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\060910-22370-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`03460000 PsLoadedModuleList = 0xfffff800`0369de50
Debug session time: Wed Jun  9 01:53:44.011 2010 (UTC - 4:00)
System Uptime: 1 days 3:17:01.088
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
..................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff680000ec388, 0, 0, fffff800035183a8}

Probably caused by : memory_corruption ( nt!MiPageMightBeZero+8 )

Followup: MachineOwner
---------

These drivers should be updated..

LMouFilt.Sys Fri Feb 29 05:08:31 2008 
LHidFilt.Sys Fri Feb 29 05:08:27 2008
AmdTools64.sys Mon Apr 28 13:03:39 2008

 

[danrb]

I've run Memtest86 several times with no problems. I also used totally different memory from a different system that is running fine.

I'll try the drivers.

Thanks!

 

[CarlTR6]

Let us know, Dan.

 

[danrb]

Still having BSODs, even after the latest changes. I've attached the most current.

Thanks,

Dan