Server blue screens when cold booted, need help with minidumps

[provideo]

I am just about at my wits end with this rackmount server I built and the crashes it has been giving me every time it boots up.

Basically what the machine does is if it has been shut off for more than a day then cold booted, it will reach the windows 7 login screen and then blue screen.
sometimes it will continue to do this infinitely unless I hard power it off and start it over again, then it will usually start up properly after that with no issue.
Sometimes the screen will also go completely black right after logging in and the cursor will freeze requiring a hard reset.

The error is nearly every time a BAD_POOL_CALLER 0x000000c2 (0x00000007, 0x00001097, 0x00053370, 0x8cda6a40) with some variation in the values

Here's the kicker though - other than that, I've left this server up for weeks at a time with no reboot or shutdown and no reliability issues or problems.

here's a little background on the machine and it's purpose:

I work at a video production house and the main purpose of this server is to offload P2 memory cards (essentially PCMCIA memory cards) from cameras for archival and then to pass them along over a gigabit switch to our editing workstation where they are worked on.

The only special parts this machine has that may not be familiar are the two readers used to interface with the cards:

Drives Bay or External Mounting PCMCIA & CardBus PC Card Reader-Writer for Standard and Low_Profile Desktop Computers

These go into a standard PCI slot and work with built in drivers that come with Win7x32.

Here's the rest of it's parts:
Hitachi 500GB Boot disk
2x Western Digital 2TB Green drives for storing the video (all 3 are sat)
Phenom II X4 925 (does not run hot, has a zalman cooler)
G.SKILL Ripjaws Series 4GB (2 x 2GB) DDR3 (PC3 12800)
MSI sata DVD-RW
OCZ 500W Modular PSU
m4a88td-v evo/usb3 (using Motherboard graphics+sound)

No special software installed, machine has no internet connection and has been scanned with nod32 so there are no viruses or malware

Other things I've tried:
checking temperatures with hwmonitor - all ok the case is extremely well ventilated and has a lot of fans

letting windows 7 try to repair the installation (it doesn't do anything)

running various ram test utilities and boot cds for a few days straight (ram is fine)

running various burn in tools to try and pinpoint the problem piece of hardware (no results)

reinstalling windows 7 (issue still persists)

updating windows (it's all current)

updating motherboard bios and other drivers (didn't help)

replacing the cmos battery on the motherboard (nothing)


I've attached a collection of minidumps from some of the crashes.
I would be deeply grateful if someone could help me figure out what's wrong with this system

 

[zigzag3143]

I am just about at my wits end with this rackmount server I built and the crashes it has been giving me every time it boots up.

Basically what the machine does is if it has been shut off for more than a day then cold booted, it will reach the windows 7 login screen and then blue screen.
sometimes it will continue to do this infinitely unless I hard power it off and start it over again, then it will usually start up properly after that with no issue.
Sometimes the screen will also go completely black right after logging in and the cursor will freeze requiring a hard reset.

The error is nearly every time a BAD_POOL_CALLER 0x000000c2 (0x00000007, 0x00001097, 0x00053370, 0x8cda6a40) with some variation in the values

Here's the kicker though - other than that, I've left this server up for weeks at a time with no reboot or shutdown and no reliability issues or problems.

here's a little background on the machine and it's purpose:

I work at a video production house and the main purpose of this server is to offload P2 memory cards (essentially PCMCIA memory cards) from cameras for archival and then to pass them along over a gigabit switch to our editing workstation where they are worked on.

The only special parts this machine has that may not be familiar are the two readers used to interface with the cards:

Drives Bay or External Mounting PCMCIA & CardBus PC Card Reader-Writer for Standard and Low_Profile Desktop Computers

These go into a standard PCI slot and work with built in drivers that come with Win7x32.

Here's the rest of it's parts:
Hitachi 500GB Boot disk
2x Western Digital 2TB Green drives for storing the video (all 3 are sat)
Phenom II X4 925 (does not run hot, has a zalman cooler)
G.SKILL Ripjaws Series 4GB (2 x 2GB) DDR3 (PC3 12800)
MSI sata DVD-RW
OCZ 500W Modular PSU
m4a88td-v evo/usb3 (using Motherboard graphics+sound)

No special software installed, machine has no internet connection and has been scanned with nod32 so there are no viruses or malware

Other things I've tried:
checking temperatures with hwmonitor - all ok the case is extremely well ventilated and has a lot of fans

letting windows 7 try to repair the installation (it doesn't do anything)

running various ram test utilities and boot cds for a few days straight (ram is fine)

running various burn in tools to try and pinpoint the problem piece of hardware (no results)

reinstalling windows 7 (issue still persists)

updating windows (it's all current)

updating motherboard bios and other drivers (didn't help)

replacing the cmos battery on the motherboard (nothing)


I've attached a collection of minidumps from some of the crashes.
I would be deeply grateful if someone could help me figure out what's wrong with this system

For it to BSOD 13 seconds after boot it has to be either an early load driver, or hardware. I notice some very unusual drivers that I cant find any information for like p2cata.sys.

I propose that since you have 5 different kinds of BSOD's and they all relate to memory you run a memory test

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.


Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

Then I would run a system file check to verify and repair system files.

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html?ltr=S

Finally There is something unusual about the OS version you are running. We dont have the tools (symbols) for the core OS files. Where did you buy or download it from?

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


Loading Dump File [C:\Users\K\Desktop\New folder\120110-16333-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82c16000 PsLoadedModuleList = 0x82d5e810
Debug session time: Wed Dec  1 18:15:24.652 2010 (GMT-5)
System Uptime: 0 days 0:00:13.260
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
............................................................
Loading User Symbols
3: kd> Analyze -v
*** WARNING: Unable to verify timestamp for p2cata.sys
*** ERROR: Module load completed but symbols could not be loaded for p2cata.sys
*** WARNING: Unable to verify timestamp for amdxata.sys
*** ERROR: Module load completed but symbols could not be loaded for amdxata.sys
*** WARNING: Unable to verify timestamp for MDPMGRNT.sys
*** ERROR: Module load completed but symbols could not be loaded for MDPMGRNT.sys
*** WARNING: Unable to verify timestamp for rdprefmp.sys
*** ERROR: Module load completed but symbols could not be loaded for rdprefmp.sys
*** WARNING: Unable to verify timestamp for ksecpkg.sys
*** ERROR: Module load completed but symbols could not be loaded for ksecpkg.sys
*** WARNING: Unable to verify timestamp for MDFSYSNT.sys
*** ERROR: Module load completed but symbols could not be loaded for MDFSYSNT.sys
*** WARNING: Unable to verify timestamp for AtiPcie.sys
*** ERROR: Module load completed but symbols could not be loaded for AtiPcie.sys
*** WARNING: Unable to verify timestamp for snapman.sys

 

[provideo]

I re-ran memtest for about 10 passes and got a couple thousand errors, so I gave my ram manufacturer a call about RMA, and they recommended I first turn down the timings from 9-9-9 24 (motherboard defaults) to 8-8-8 24 and set the clockrate to 1333mhz (it was on auto, i think defaulting to something higher) I didn't touch the voltage settings.

I've been running memtest again for about two hours and have passed six times with no errors yet, will post back with results later.