locked
Windows Server 2003 R2 System Error --- Blue screen RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    My comany I use windows Server 2003 R2 run our C.NET application.

    Windows OS Server was stop and show blue screen.

    2 msg event log in below.    after restart OS everything work well.

    "Event Type: Warning
    Event Source: USER32
    Event Category: None
    Event ID: 1076
    Date:  7/11/2012
    Time:  11:22:54 PM
    User:  TTI_COM_B_SV1\Administrator
    Computer: TTI_COM_B_SV1
    Description:
    The reason supplied by user TTI_COM_B_SV1\Administrator for the last unexpected shutdown of this computer is: System Failure: Stop error
     Reason Code: 0x805000f
     Bug ID:
     Bugcheck String: 0x000000d1 (0x00000000, 0xd000001b, 0x00000008, 0x00000000)
     Comment: 0x000000d1 (0x00000000, 0xd000001b, 0x00000008, 0x00000000)

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 0f 00 05 08               ....   

    and

    Event Type: Error
    Event Source: System Error
    Event Category: (102)
    Event ID: 1003
    Date:  7/11/2012
    Time:  11:23:02 PM
    User:  N/A
    Computer: TTI_COM_B_SV1
    Description:
    Error code 000000d1, parameter1 00000000, parameter2 d000001b, parameter3 00000008, parameter4 00000000.

    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 64    000000d
    0020: 31 20 20 50 61 72 61 6d   1  Param
    0028: 65 74 65 72 73 20 30 30   eters 00
    0030: 30 30 30 30 30 30 2c 20   000000,
    0038: 64 30 30 30 30 30 31 62   d000001b
    0040: 2c 20 30 30 30 30 30 30   , 000000
    0048: 30 38 2c 20 30 30 30 30   08, 0000
    0050: 30 30 30 30               0000   

    Do you have any idea? what it root couse of problem?

    Monday, July 16, 2012 3:46 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Here's some general info. You'll probably need to call Microsoft CSS for specific trouble shooting.

     http://msdn.microsoft.com/en-us/library/windows/hardware/ff560244(v=vs.85).aspx

    http://support.microsoft.com/kb/319726

     

     

    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    • Proposed as answer by Santosh Bhandarkar Monday, July 16, 2012 5:03 AM
    • Marked as answer by Miya Yao Wednesday, July 25, 2012 9:03 AM
    Monday, July 16, 2012 4:03 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    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,

    Miya

       

    Miya Yao

    TechNet Community Support

    • Marked as answer by Miya Yao Wednesday, July 25, 2012 9:03 AM
    Monday, July 16, 2012 8:14 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Here's some general info. You'll probably need to call Microsoft CSS for specific trouble shooting.

     http://msdn.microsoft.com/en-us/library/windows/hardware/ff560244(v=vs.85).aspx

    http://support.microsoft.com/kb/319726

     

     

    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    • Proposed as answer by Santosh Bhandarkar Monday, July 16, 2012 5:03 AM
    • Marked as answer by Miya Yao Wednesday, July 25, 2012 9:03 AM
    Monday, July 16, 2012 4:03 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    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,

    Miya

       

    Miya Yao

    TechNet Community Support

    • Marked as answer by Miya Yao Wednesday, July 25, 2012 9:03 AM
    Monday, July 16, 2012 8:14 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    If this only happened once, well, maybe you are lucky and it won't happen again. In any case, the most relevant information in these events is the first error code (or Bugcheck string): 000000d1. This particular error is the hex code for "DRIVER_IRQL_NOT_LESS_OR_EQUAL" type of error (see Error code: 0x000000D1). In just few words, a software attempted to use regions of memory reserved just for the operating system. This typically indicates a bug in a device driver. Try to identify the culprit and then installing the latest drives for it or remove it if necessary. On a blue screen of death, the device driver can be easily identified. It could be that your custom application is at fault but since you mention that it is a .Net application it is unlikely as any fault with the application would be caught by the .Net runtime before it has any chance to reach the operating system directly.

    You may want to check Event ID 1003 from source System as well...

    Monday, July 16, 2012 6:10 PM