Server keeps blue screening, even after lots of successful testing

[BondUniverse]

I have a custom built server that just LOVES to crash. I've rebuilt it several times and even changed out a lot of the hardware, still it continues to frequently crash... I've also run several different hardware diagnostics and burnin software (PCI board based), but it never seems to have an issue with these... Starting to think it might be a driver, but I don't even know where to begin there...

I'm trying to start playing around with the Dump logs, but I've never really looked at them before, so I don't exactly know what I'm doing...

I ran DumpChk, and here is the analysis... Any ideas?

************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa8003544bc0, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )

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

Finished dump check


MiniDump: https://docs.google.com/leaf?id=0BwZ...MzA4ZDY3&hl=en

[BondUniverse]

From WinDbg...

************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8003544bc0
Arg3: 000000000000ffff
Arg4: 0000000000000000

Debugging Details:
------------------


BUGCHECK_STR: 0x1a_41790

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP

PROCESS_NAME: mmc.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff800016fa26e to fffff80001687f00

STACK_TEXT:
fffff880`0775d828 fffff800`016fa26e : 00000000`0000001a 00000000`00041790 fffffa80`03544bc0 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0775d830 fffff800`016bb5d9 : 00000000`00000000 00000000`6c6b5fff fffffa80`00000000 fffff800`01690000 : nt! ?? ::FNODOBFM::`string'+0x339d6
fffff880`0775d9f0 fffff800`0199de50 : fffffa80`08cf1290 0007ffff`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`0775db10 fffff800`0199e25b : 00000000`00000000 00000000`6b360000 fffffa80`00000001 fffffa80`08849440 : nt!MiUnmapViewOfSection+0x1b0
fffff880`0775dbd0 fffff800`01687153 : fffffa80`09377060 fffff880`0775dca0 fffffa80`07f37060 00000000`1dee1e30 : nt!NtUnmapViewOfSection+0x5f
fffff880`0775dc20 00000000`7758015a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`000ce8c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7758015a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+339d6
fffff800`016fa26e cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+339d6

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600

FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+339d6

BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+339d6

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

[Ferrit]

Well first off is it going to a blue screen?
If it is set it to not restart on blue screen then we can get the error numbers.
What SP's exactly?
What hardware? Especially power supply and motherboard models

[BondUniverse]

Service Pack: It's 2008 R2 Standard (so SP2)
Motherbaord: MSI 975X Platinum
PowerSupply: Rosewill RP550

BSOD picture: https://doc-0k-74-docs.googleusercon...M1MjAzMmVlYjRm

[Matridom]

is your ram ECC?
have you yanked out un-needed cards?
disabled everything onboard that is not needed?

[BondUniverse]

I've yanked out unneeded cards (I've yanked out ALL previously too)...

I'll have to check on the RAM, forget if it's ECC or not. Have been planning on testing with just 1 stick of RAM in at a time to see if I get different results, but we'll have to see when I can get time to do this test...

[CeeBee]

Bad memory/hardware or some wicked spyware.
Run a thorough memory test...

[BondUniverse]

Definitely not spyware, I know it's clean, but have even had it happen just after reinstalling the OS...

RAM is: Crucial Ballistix BL2566AA80A (800MHz-4-4-12 2.0V)
(http://www.crucial.com/store/mpartsp...642197A5CA7304)

I took all out but one and am letting it run for a couple of days (need to try and find time to run a memory test too)

[Matridom]

http://www.crucial.com/store/partspe...E=CT25672AA800

That's the memory you should have gotten. Let use know how the memory testing goes.

[CeeBee]

Did you set the voltage for the RAM to 2.0V??? Otherwise you may experience reliability issues. Also leave the speed to default.

[BondUniverse]

MB is already configure for 2.0V. Not sure if it always has or not, but I know I haven't changed it in a long time... Never overclocked it either...