Hello, Twice this week I logon to my SCDPM server in the morning and notice that it has recovered from an unexpected system shutdown. Apparently it has BSODd and iLO's ASR has restarted the machine. Trying to find out what happend, the Event Log gave me this information: The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 (0x0000000000000021, 0xfffffa8029e64000, 0x00000000000031a0, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 050911-47112-01. Using WinDBG I didn't get more than this: BAD_POOL_HEADER (19) The pool is already corrupt at the time of the current request. This may or may not be due to the caller. The internal pool links must be walked to figure out a possible cause of the problem, and then special pool applied to the suspect tags or the driver verifier to a suspect driver. Arguments: Arg1: 0000000000000021, the data following the pool block being freed is corrupt. Typically this means the consumer (call stack ) has overrun the block. Arg2: fffffa8029e64000, The pool pointer being freed. Arg3: 00000000000031a0, The number of bytes allocated for the pool block. Arg4: 0000000000000000, The corrupted value found following the pool block. It is frustrating me that I cannot find out what exactly caused the BSDO. Yes, a memory allocation error - but due to drivers or the memory itself? Before making someone replace the memory - the machine is on a remote location - I would like to find out what is happening. I'd love to hear if anyone has an idea what else I can try to find out the culprit. Note though: I have read the KBs on wireless adapters causing this (no such device) and on iSCSI connecters causing this (FiberChannel to our SAN). Software: Windows Server 2008 R2 Standard / SCDPM 2010 Hardware: HP ProLiant DL380 G7 / Xeon E5630 / 24GB RAM Thank you in advance.My grandmother always used to say: "::1: sweet ::1:"

Hello, Bug Check Code 0x19: http://msdn.microsoft.com/en-us/library/ff557389(VS.85).aspx This problem is due to a driver that you have to determine. You can use Driver Verifier to determine the faulty driver or just update all possible drivers / firmwares. You can also contact Microsoft CSS for support. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration

Hi, I would like to suggest you update the BIOS and the hardware drivers first. You may also analyze the dump files with Debugging Tools by yourself. You can install it and it’s Symbol Packages from the following link: http://www.microsoft.com/whdc/Devtools/Debugging/default.mspx WinDbg will tell you the possible cause. For more information, please read Microsoft KB article below: How to read the small memory dump files that Windows creates for debugging http://support.microsoft.com/kb/315263 If no clue can be found, you may contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. Please be advised that contacting phone support will be a charged call. To obtain the phone numbers for specific technology request please take a look at the web site listed below: http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607 Regards,Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.