We are running MS Windows Server 2003 Standard x64 Edition Service pack 2 on a virtual private server. Suddenly we have got blue screen errors. About 10 minutes after start it goes down with a blue screen. All other virtual private servers on the same machine are running without these problems. Can anyone give a hint on what's the problem? The machine is running important batch updates so we have to get it up as soon as possible. Any help is welcome. Examples of error messages below. Thanks in advance Lage Event Type: Error Event Source: System Error Event Category: (102) Event ID: 1003 Date: 2010-09-24 Time: 14:11:25 User: N/A Computer: DV1 Description: Error code 0000000000000019, parameter1 0000000000000020, parameter2 fffffa80034aa290, parameter3 fffffa80034aa300, parameter4 0000000006070129. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 53 79 73 74 65 6d 20 45 System E 0008: 72 72 6f 72 20 20 45 72 rror Er 0010: 72 6f 72 20 63 6f 64 65 ror code 0018: 20 30 30 30 30 30 30 30 0000000 0020: 30 30 30 30 30 30 30 31 00000001 0028: 39 20 20 50 61 72 61 6d 9 Param 0030: 65 74 65 72 73 20 30 30 eters 00 0038: 30 30 30 30 30 30 30 30 00000000 0040: 30 30 30 30 32 30 2c 20 000020, 0048: 66 66 66 66 66 61 38 30 fffffa80 0050: 30 33 34 61 61 32 39 30 034aa290 0058: 2c 20 66 66 66 66 66 61 , fffffa 0060: 38 30 30 33 34 61 61 33 80034aa3 0068: 30 30 2c 20 30 30 30 30 00, 0000 0070: 30 30 30 30 30 36 30 37 00000607 0078: 30 31 32 39 0129 Event Type: Error Event Source: System Error Event Category: (102) Event ID: 1003 Date: 2010-09-24 Time: 14:10:32 User: N/A Computer: DV1 Description: Error code 0000000000000019, parameter1 0000000000000020, parameter2 fffffa8000867b30, parameter3 fffffa8000867ba0, parameter4 0000000006070303. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 53 79 73 74 65 6d 20 45 System E 0008: 72 72 6f 72 20 20 45 72 rror Er 0010: 72 6f 72 20 63 6f 64 65 ror code 0018: 20 30 30 30 30 30 30 30 0000000 0020: 30 30 30 30 30 30 30 31 00000001 0028: 39 20 20 50 61 72 61 6d 9 Param 0030: 65 74 65 72 73 20 30 30 eters 00 0038: 30 30 30 30 30 30 30 30 00000000 0040: 30 30 30 30 32 30 2c 20 000020, 0048: 66 66 66 66 66 61 38 30 fffffa80 0050: 30 30 38 36 37 62 33 30 00867b30 0058: 2c 20 66 66 66 66 66 61 , fffffa 0060: 38 30 30 30 38 36 37 62 8000867b 0068: 61 30 2c 20 30 30 30 30 a0, 0000 0070: 30 30 30 30 30 36 30 37 00000607 0078: 30 33 30 33 0303

0x19: BAD_POOL_HEADER http://msdn.microsoft.com/en-us/library/ff557389%28v=VS.85%29.aspx It appears that the pool block header size was corrupt on at least one of the entries each crash. Have you recently made any changes to the hardware or the drivers of the system? You might try running the driver verifier to see if it can isolate a particular driver that is misbehaving, http://support.microsoft.com/kb/244617 If you haven't made any recent hardware/driver changes (including upgrading antivirus software), I might look into this as a possible memory issues by running an extended test with Windows Memory Diagnostic or a longer test with memtest86+ (preferred), http://oca.microsoft.com/en/windiag.asp http://www.memtest.org/ -- Mike Burr

Hi, Colleague of Lage, it turned out to be ntfs.sys which had been corrupted. Decided to repair the file via the repair installation option of the server 2003 cd. However we can't get passed the first gui loading screen of the setup due to an error with lsass.exe; lsass.exe - Buffer Overflow The data was too large to fit into the specified buffer. I first thought it might be sasser that somehow got in during the installation, or was already dorment on the server, so I scanned the drives with both kaspersky and avira - no hits. Does anyone know what might be causing this error? // Spelon

Hi Mike, thank you for your answer. We have made thorough hardware tests and everything was ok with the hardware. The server worked in safe mode but did crashed in normal mode. By analyzing the dump file with the debugger in sdk/framework4 we found that the file ntfs.sys was loaded each time just before the crash. When trying to repair we get the problem with buffer overflow for lsass.exe described below by Spelon. Any idea? Lage

Hi, If the issue continues, I would like to suggest that you contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. Because it seems to be system crash issue and we need to analyze the crash dump file to narrow down the root cause of the issue. Unfortunately, it is not effective for us to debug the crash dump file here in the forum. Thanks for your understanding. 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 Hope the issue will be resolved soon. Best Regards, Vincent Hu