locked
Server crashing sometimes with blue screen RRS feed

  • Question

  • Fresh install of WHS upgraded to PP3 keeps crashing on me, I am at a loss as to how to identify the source of the crash. Often times the server just crashes (complete failure without recovery and without event in event viewer or blue screen), sometimes with blue screen and error in event viewer. Most recent event: System Error, category (102), EventID 1003 Error code 000000d1, parameter1 6a107560, parameter2 000000ff, parameter3 00000008, parameter4 6a107560. I have tested the drives using Seatool Long Drive Self Test, Short Drive Self Test, and Long Generic Test. One drive failed Long Drive Self Test once out of three tries. I removed the drive and even reinstalled WHS - now 2 days after getting the server back up it has crashed twice this evening. Board: P5Q-EM Drives: 5X Seagate 1TB 5900 RPM ST31000520AS - about half full CPU: Celeron 450 2GB Kingston DDR2-800 Antec Earthwatts 500 PSU No cards
    Tuesday, December 22, 2009 4:12 AM

Answers

  • Hi,
    is there a file name mentioned on the BSOD?
    (To get a BSOD shown, you will have to disable the automatic restart in Control Panel/System on Advanced tab/section Startup and Recovery/Settings button.)
    There are a lot of articles related to that stop error, here a selection:

    You receive a "Stop 0xD1" error message when you try to establish a TCP/IP session (829120) - When you try to establish a TCP/IP session, your computer may
    stop responding, and you may receive a "Stop 0xD1" error message.
    http://support.microsoft.com/kb/829120/en-us

    You receive a "DRIVER_IRQL_NOT_LESS_OR_EQUAL STOP 0xD1" error message, and your Windows Server 2003-based computer stops responding
    (835166) - Provides a resolution for a problem that occurs when your Windows Server 2003-based computer stops responding and you receive a STOP 0xD1
    error message.
    http://support.microsoft.com/kb/835166/en-us

    "DRIVER_IRQL_NOT_LESS_OR_EQUAL (0xD1)" Stop error occurs in Windows Server 2003 when you remove a USB device (867754) - A Microsoft Windows Server 2003-based computer may stop responding, and you may receive a "DRIVER_IRQL_NOT_LESS_OR_EQUAL (0xD1)" Stop error.
    http://support.microsoft.com/kb/867754/en-us

    "STOP 0xD1" error message when you run the Device Path Exerciser tool in Windows Server 2003 64-Bit Edition (833869) - Fixes a problem in the Scsiport.sys file that generates a Stop error during Device Path Exerciser testing. Device Path Exerciser is a component of the Hardware Compatibility Test Kit.
    http://support.microsoft.com/kb/833869/en-us

    Computer Stops Responding with "DRIVER_IRQL_NOT_LESS_OR_EQUAL" Stop Error If CD-ROM Drive or Tape Device Is Connected to SCSI Controller (821138) - Computer stops responding with 0xD1 bug check if the computer has a CD-ROM drive or tape device on a boot controller that uses a Storport.sys  storage driver.
    http://support.microsoft.com/kb/821138/en-us

    The Afd.sys file triggers a "Stop 0x000000D1" error on a Windows Server 2003-based computer (894070) - Fixes a problem where the Afd.sys file triggers a Stop 0xD1 error
    in Windows Server 2003.
    http://support.microsoft.com/kb/894070/en-us

    You receive a "Stop 0x000000D1" error message in Ipnat.sys on a Windows Server 2003-based computer that is configured to use NAT (834831) - Describes a fix for an issue in Windows Server 2003 where a "stop  0x000000D1IRQL_NOT_LESS_OR_EQUAL" error occurs in Ipnat.sys on a server that is configured to use NAT
    http://support.microsoft.com/kb/834831/en-us

    You receive a "Stop 0x000000D1" Stop error message when you back up data to a tape device on a computer that is running Windows Server 2003, Windows XP, or Windows 2000
    (884590) - Discusses an issue where you receive a Stop error message when you back up data to a tape device on a computer that has a MegaRAID controller.
    http://support.microsoft.com/kb/884590/en-us

    "STOP: 0x000000D1" error occurs after Windows Server 2003 stops unexpectedly (867772) - Fixes a problem where a Windows Server 2003-based computer stops unexpectedly and where you receive a "STOP: 0x000000D1" error message.
    http://support.microsoft.com/kb/867772/en-us

    You receive a "STOP 0x000000D1" error message on a blue screen in Windows Server 2003 (890554) - Fixes a problem that occurs when the computer is under a heavy load. To resolve the problem, you must install a hotfix.
    http://support.microsoft.com/kb/890554/en-us

    You receive a "STOP 0x000000D1" error message in Windows Server 2003 or in Windows 2000 Server (831694) - Fixes an issue in Windows Server 2003 and Windows 2000 where you may receive a "STOP 0x000000D1" error message on a computer that uses an IDE controller that requires synchronization across all channels.
    http://support.microsoft.com/kb/831694/en-us

    "STOP 0x000000D1" error message when Windows Server 2003 is under a heavy network load (842840) - resolves a problem where a Windows Server 2003-based computer may
    intermittently stop responding (hang) with a STOP D1 error message during periods of heavy network use.
    http://support.microsoft.com/kb/842840/en-us

    0x77 or 0x7A Stop error message may occur when you press the power button on an ACPI-compliant computer that is running Windows 2000 or Windows Server 2003
    (884056) - Hotfix resolves a problem where a 0x77 or 0x7A Stop error message occurs when you press the power button on an ACPI-compliant computer that is running Windows 2000.
    http://support.microsoft.com/kb/884056/en-us

    "Stop 0x000000D1" error message on your Windows Server 2003-based computer (834630) - Discusses a problem that occurs if you are running Windows Server 2003 on a multiprocessor computer, and there is a heavy network load on your server. Requires that you install a hotfix to resolve the problem.
    http://support.microsoft.com/kb/834630/en-us

    Error Message: STOP 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL (293077) - You may receive the following error message on a blue screen: STOP 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL (0x0,0x0,0x0,0x0) Parameters 1 - memory that is referenced 2 - IRQL 3 - value 0 = read operation, 1 =
    write operation 4 - address that...
    http://support.microsoft.com/kb/293077/en-us

    Computer stops responding with "Stop 0x000000D1 Driver_IRQL_Not_Less_Or_Equal" error message (817789) - Provides a resolution for an issue that occurs when your Windows
    Server 2003-based computer stops responding and you receive a Stop error message.
    http://support.microsoft.com/kb/817789/en-us

    IRPStackSize parameter in Windows 2000 and Windows Server 2003 (285089) - This article describes the functionality of the IRPStackSize parameter in Microsoft Windows 2000 Server and Microsoft Windows Server 2003. IRPStackSize specifies the number of stack locations in I/O request packets (IRPs) used by Windows 2000...
    http://support.microsoft.com/kb/285089/en-us

    The updated Storport storage driver, version 5.2.3790.217, fixes a range of Storport-related problems in Windows Server 2003 (883646) - Fixes a variety of Storport-related problems that are associated with earlier versions of the Storport.sys driver.
    http://support.microsoft.com/kb/883646/en-us

    Best greetings from Germany
    Olaf
    Tuesday, December 22, 2009 11:28 AM
    Moderator

All replies

  • Hi,
    is there a file name mentioned on the BSOD?
    (To get a BSOD shown, you will have to disable the automatic restart in Control Panel/System on Advanced tab/section Startup and Recovery/Settings button.)
    There are a lot of articles related to that stop error, here a selection:

    You receive a "Stop 0xD1" error message when you try to establish a TCP/IP session (829120) - When you try to establish a TCP/IP session, your computer may
    stop responding, and you may receive a "Stop 0xD1" error message.
    http://support.microsoft.com/kb/829120/en-us

    You receive a "DRIVER_IRQL_NOT_LESS_OR_EQUAL STOP 0xD1" error message, and your Windows Server 2003-based computer stops responding
    (835166) - Provides a resolution for a problem that occurs when your Windows Server 2003-based computer stops responding and you receive a STOP 0xD1
    error message.
    http://support.microsoft.com/kb/835166/en-us

    "DRIVER_IRQL_NOT_LESS_OR_EQUAL (0xD1)" Stop error occurs in Windows Server 2003 when you remove a USB device (867754) - A Microsoft Windows Server 2003-based computer may stop responding, and you may receive a "DRIVER_IRQL_NOT_LESS_OR_EQUAL (0xD1)" Stop error.
    http://support.microsoft.com/kb/867754/en-us

    "STOP 0xD1" error message when you run the Device Path Exerciser tool in Windows Server 2003 64-Bit Edition (833869) - Fixes a problem in the Scsiport.sys file that generates a Stop error during Device Path Exerciser testing. Device Path Exerciser is a component of the Hardware Compatibility Test Kit.
    http://support.microsoft.com/kb/833869/en-us

    Computer Stops Responding with "DRIVER_IRQL_NOT_LESS_OR_EQUAL" Stop Error If CD-ROM Drive or Tape Device Is Connected to SCSI Controller (821138) - Computer stops responding with 0xD1 bug check if the computer has a CD-ROM drive or tape device on a boot controller that uses a Storport.sys  storage driver.
    http://support.microsoft.com/kb/821138/en-us

    The Afd.sys file triggers a "Stop 0x000000D1" error on a Windows Server 2003-based computer (894070) - Fixes a problem where the Afd.sys file triggers a Stop 0xD1 error
    in Windows Server 2003.
    http://support.microsoft.com/kb/894070/en-us

    You receive a "Stop 0x000000D1" error message in Ipnat.sys on a Windows Server 2003-based computer that is configured to use NAT (834831) - Describes a fix for an issue in Windows Server 2003 where a "stop  0x000000D1IRQL_NOT_LESS_OR_EQUAL" error occurs in Ipnat.sys on a server that is configured to use NAT
    http://support.microsoft.com/kb/834831/en-us

    You receive a "Stop 0x000000D1" Stop error message when you back up data to a tape device on a computer that is running Windows Server 2003, Windows XP, or Windows 2000
    (884590) - Discusses an issue where you receive a Stop error message when you back up data to a tape device on a computer that has a MegaRAID controller.
    http://support.microsoft.com/kb/884590/en-us

    "STOP: 0x000000D1" error occurs after Windows Server 2003 stops unexpectedly (867772) - Fixes a problem where a Windows Server 2003-based computer stops unexpectedly and where you receive a "STOP: 0x000000D1" error message.
    http://support.microsoft.com/kb/867772/en-us

    You receive a "STOP 0x000000D1" error message on a blue screen in Windows Server 2003 (890554) - Fixes a problem that occurs when the computer is under a heavy load. To resolve the problem, you must install a hotfix.
    http://support.microsoft.com/kb/890554/en-us

    You receive a "STOP 0x000000D1" error message in Windows Server 2003 or in Windows 2000 Server (831694) - Fixes an issue in Windows Server 2003 and Windows 2000 where you may receive a "STOP 0x000000D1" error message on a computer that uses an IDE controller that requires synchronization across all channels.
    http://support.microsoft.com/kb/831694/en-us

    "STOP 0x000000D1" error message when Windows Server 2003 is under a heavy network load (842840) - resolves a problem where a Windows Server 2003-based computer may
    intermittently stop responding (hang) with a STOP D1 error message during periods of heavy network use.
    http://support.microsoft.com/kb/842840/en-us

    0x77 or 0x7A Stop error message may occur when you press the power button on an ACPI-compliant computer that is running Windows 2000 or Windows Server 2003
    (884056) - Hotfix resolves a problem where a 0x77 or 0x7A Stop error message occurs when you press the power button on an ACPI-compliant computer that is running Windows 2000.
    http://support.microsoft.com/kb/884056/en-us

    "Stop 0x000000D1" error message on your Windows Server 2003-based computer (834630) - Discusses a problem that occurs if you are running Windows Server 2003 on a multiprocessor computer, and there is a heavy network load on your server. Requires that you install a hotfix to resolve the problem.
    http://support.microsoft.com/kb/834630/en-us

    Error Message: STOP 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL (293077) - You may receive the following error message on a blue screen: STOP 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL (0x0,0x0,0x0,0x0) Parameters 1 - memory that is referenced 2 - IRQL 3 - value 0 = read operation, 1 =
    write operation 4 - address that...
    http://support.microsoft.com/kb/293077/en-us

    Computer stops responding with "Stop 0x000000D1 Driver_IRQL_Not_Less_Or_Equal" error message (817789) - Provides a resolution for an issue that occurs when your Windows
    Server 2003-based computer stops responding and you receive a Stop error message.
    http://support.microsoft.com/kb/817789/en-us

    IRPStackSize parameter in Windows 2000 and Windows Server 2003 (285089) - This article describes the functionality of the IRPStackSize parameter in Microsoft Windows 2000 Server and Microsoft Windows Server 2003. IRPStackSize specifies the number of stack locations in I/O request packets (IRPs) used by Windows 2000...
    http://support.microsoft.com/kb/285089/en-us

    The updated Storport storage driver, version 5.2.3790.217, fixes a range of Storport-related problems in Windows Server 2003 (883646) - Fixes a variety of Storport-related problems that are associated with earlier versions of the Storport.sys driver.
    http://support.microsoft.com/kb/883646/en-us

    Best greetings from Germany
    Olaf
    Tuesday, December 22, 2009 11:28 AM
    Moderator
  • I will disable the automatic restart this evening in anticipation of trapping future BSOD info.

    Regarding file name referenced by BSOD - there was a crash dump file referenced.

    If I am able to locate the crash dump file what do I do with it?
    Tuesday, December 22, 2009 6:27 PM
  • Olaf,

    I did scan through the list you sent, and none seem to hit the vague error I am seeing.

    I did also turn off automatic restart several days ago.

    My server generated the same error at least once since turning off automatic restart, but no blue screen was generated.  So now I am thinking its just a "serious error" windows has recovered from without an actual blue screen (didn't know there was such a thing, I'm somewhat of a noob).

    Do you have further advice for troubleshooting?
    Monday, December 28, 2009 6:10 PM
  • From here it is even more difficult to troubleshoot then, since this indicates either a driver or hardware problem.
    Since there is no BSOD visible, one could assume, it is deep in the system which is needed to present this error - video adapter comes into my mind. If this stops functioning, this would explain a BSOD related error still logged, but not presented.
    Open the box and check the condition of coolers (remove dust, check, if the fans are still moving etc) and the mainboard for boiling up capacitors.
    Also check, if the memory and the cards are still well seated in their slots.
    Debugging a memory dump is possible (if you search for the keywords in Internet you will find many hits), but is not very good to handle by somebody, who is not deep in that stuff.
    Best greetings from Germany
    Olaf
    Tuesday, December 29, 2009 11:02 PM
    Moderator
  • Thank you for the additional ideas Olaf.

    In the end, this was both hardware and software - two separate issues:
    * 1 intermittently failing hard drive (brand new Seagate 1TB LP drive, grrr)
    * A "serious error" apparently triggered by WHS failing to install client printer / fax devices when I log into server from client via remote desktop.

    Was difficult to find the HD issue, but SeaTools failed the drive once out of 4 or 5 long self tests.  With that one failure signal I removed the drive and the crashes without blue screen ceased. 

    I was left with only the "serious error" without a crash and troubleshot that via viewing the event logs showing errors trying to install printer / fax devices upon remote desktop login.  I followed your recommendation to stop WHS from trying to install the devices and the "seriuos error" is gone.

    Hope this also helps someone else too.

    • Marked as answer by evergreen.97 Thursday, January 7, 2010 5:37 PM
    • Unmarked as answer by evergreen.97 Saturday, January 9, 2010 4:55 AM
    Thursday, January 7, 2010 5:37 PM
  • * A "serious error" apparently triggered by WHS failing to install client printer / fax devices when I log into server from client via remote desktop.

    Ignore these, they're umimportant warnings that your remote computer is trying to forward printers that the host (your server) doesn't have drivers for.
    I'm not on the WHS team, I just post a lot. :)
    Thursday, January 7, 2010 6:31 PM
    Moderator
  • Alas, I thought myself triumphant one day to early. After 15 days of uptime the server crashed again tonight. Upon reboot I get the following: Error signature info: BCCode:a BCP1:0C15FF02 BCP2:D000001F BCP3:00000000 BCP4:80828B4D OSVer:5_2_3790 SP:2_0 Product:33073_3 I don't find these codes doing Google search and have never figured out how to debug crash dump files (not for lack of trying). Any help to troubleshoot would be greatly appreciated.
    Saturday, January 9, 2010 5:01 AM
  • BCCCode:a is still an incarnation of the above BSOD, although this time packed as stop 0x0000000A. So here you find another KB article dedicated to that stop error. The potential reasons are probably still the same - either an incompatible driver or faulty hardware.
    There are multiple guides for crash dump analysis, one example just linked.
    Best greetings from Germany
    Olaf

    Monday, January 11, 2010 9:05 AM
    Moderator
  • For anyone experiencing mystery BSOD using ASUS P5Q-EM and Windows Home Server (PP3):

    I gave up on the P5Q-EM, re-installed on a trusty old ASUS P5LD2 and for the month its been live I have seen none of the crashes I saw on the P5Q-EM.  Its been quite reliable with only one driver crash, probably related to the Promise SATA300 TX4 card I installed to add more SATA dirves (the P5LD2 only has 4 SATA ports vs. the P5Q-EM's 6 - the two extra ports were why I chose to use the P5Q-EM even though I suspected the G45 based HTPC oriented board might have driver challenges with WHS).
    Friday, February 26, 2010 2:27 AM