I have two problems. I was installing Visual Studio 2003 in Windows Server 2003 and I received a BAD_POOL_HEADER message and my screen went to the blue screen. Thereafter, I try to turn on my computer and it continuously reboots. I can't even get it to stay in safe mode. How can I solve this problem?

Does the computer stay up for a while, or does it immediately reboot at a certain point in the boot-up process? When it reboots, does it BSOD? If so, what is the error?

Either a driver issue or hardware. With this being a server, I'd run a full HD scan and memory scan (like Memtest86 or the MS memory test) before going too much further. It's more common than you might think to have a bad memory stick and most administrators are quite used to being the victim of a bad HD. After that, start looking for software issues. If you don't like my long answer, you could always start up the computer using "Last Known Good Configuration" just to see if it a CurrentConfig rollback would help. C Shane Cribbs http://www.georgiatechnologies.com

Thanks for your response, Bigteddy. It reboots after the Windows Server 2003 screen with the progress dots. I do not receive the BSOD. I only initially went to the BSOD, along with a BAD_POOL_HEADER message. I rebooted and now it only does the continual boot loop.

Thanks, Shane. I restarted the computer and tried "Last Known Good Configuration," and it just rebooted again. How do I run MS memory test or Memtest86 if I can't get it to stop doing the constant boot loop?

Both of these utilities can be run from a bootable CD. You can run the MS memory test tool from a Windows 2008 DVD. On the second screen, select "Repair My Computer". For Memtest86, just go to another computer, google (or BING) "MemTest86+", download it, burn it to CD and boot from it. If it's continually rebooting BEFORE you can even boot from CD/DVD, there's a hardware issue and you'll have to resolve that with your vendor. C Shane Cribbs http://www.georgiatechnologies.com

Bug Check Code 0x19: http://msdn.microsoft.com/en-us/library/ff557389(v=VS.85).aspx This indicates that a pool header is corrupt. You can use Driver Verifier to determine the faulty driver. It will be better to start updating all drivers. You can also contact Microsoft CSS. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 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 Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified IT Professional: Enterprise Administrator

Since you can't get into Windows to run any diagnostics or update drivers, try the MDOP Crash Dump Analyzer which can tell you which driver is most likely the cause. However, disabling that driver when even safe mode won't work may mean some manual registry editing from Windows PE. C Shane Cribbs http://www.georgiatechnologies.com

Hi, You may contact Microsoft Customer Service and Support (CSS) via telephone as Mr X mentioned 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.

Okay. Here's what I did that seems to have worked so far. I put the Windows Server 2003 disk in. That solved the constant reboot problem. Duh. I then ran chkdisk which found one or more errors on the volume. So I ran chkdisk /r at the C:\prompt. I received a message that chkdsk found and fixed one or more errors. I am now able to boot up successfully. I have reinstalled all updates. All seems to be well. I will start the system tomorrow morning and see if all is still well . . . Thanks for everyone's help!