Question : MS Server 2003 R2 Standard x64 Blue Screen Shutdown every Saturday

I have a MS Server 2003 R2 Standard x64 Server that has shutdown on it's own for the last 3 saturdays.  The HP Mgm't Log shows the following errors:
- Blue Screen Trap (BugCheck, STOP: 0x000000C2 (0x0000000000000007, 0x000000000000121A, 0x0000000000000000, 0xFFFFFA8009069010)) 9/8/2007 6:10PM 9/8/2007 6:10PM 1
- Blue Screen Trap (BugCheck, STOP: 0x0000003B (0x00000000C0000005, 0xFFFFF8000103FB89, 0xFFFFFADF23EA9E20, 0x0000000000000000)) 9/1/2007 3:58AM 9/1/2007 3:58AM 1
- Blue Screen Trap (BugCheck, STOP: 0x000000C5 (0xFFFFFAEF2987BAF0, 0x0000000000000002, 0x0000000000000000, 0xFFFFF800011A98DE)) 8/25/2007 1:54PM 8/25/2007 1:54PM 1
- Blue Screen Trap (BugCheck, STOP: 0x000000C2 (0x0000000000000007, 0x000000000000121A, 0x0000000000000000, 0xFFFFFA800428B010)) 8/18/2007 7:09PM 8/20/2007 8:27AM 1
- ROM flashed (New version: 05/01/2007) 8/17/2007 7:18PM 8/17/2007 7:18PM
The server fails every saturday but does not correspond with any other event (Such as backups or exports) and the eventlog does not show any events at this time.
Could this be something caused by the HP Mgm't updates I ran which on the log show the ROM being flashed?  

Answer : MS Server 2003 R2 Standard x64 Blue Screen Shutdown every Saturday

Hey,
Bug Check 0xC2: BAD_POOL_CALLER.
This bug check has following paramenters according to the problem description:
0x0000000000000007, 0x000000000000121A, 0x0000000000000000, 0xFFFFFA8009069010
1st parameter tells us the possible cause.
0x0000000000000007 -- The current thread attempted to free the pool, which was already freed.

Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION.
The SYSTEM_SERVICE_EXCEPTION bug check has a value of 0x0000003B. This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

Parameters
The following parameters are displayed on the blue screen.

Parameter Description
1 The exception that caused the bug check
2 The address of the exception record for the exception that caused the bug check
3 The address of the context record for the exception that caused the bug check
4 0  

Possible Cause
This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

NOTE: It is difficult to pin point the culprit driver causing the bug check just looking at the error message.

Your machine must have created a memory dump. By default it is under %systemroot%\memory.dmp OR in case if you have minidump enabled then %systemroot%\minidump

To analyze this memory dump download Debugging Tools for Windows From Microsoft Website.
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx

Then before opening a this memory dump file in WinDbg (Windows Debugger) you will have set the symbol file path.

This is public symbol server : http://msdl.microsoft.com/download/symbols
Set the symbol file path as follows under WinDbg.
Srv*c:\localsymbols*http://msdl.microsoft.com/download/symbols

After installing Debugging Tools go through the CHM file for analyzing the memory dump OR if you have the minidump then please zip that minidump mail it to [email protected], i will reply you the analysis.

Regards,
Nikhil