none
Error nativerd.dll + I/O error + Crashing IIS worker process RRS feed

  • Question

  • Hi,

    Getting I/O error on IIS for the IIS workers process,  so IIS is not able to read the few contents.   Please find below the application event logs

    Immediate resolution or fix to the problem is appreciated

    Analysis symbol:

    Rechecking for solution: 0

    Report Id: 39cdc543-e4b9-11e0-8c5b-78e3b518b572

    Report Status: 4</Message><Level>Information</Level><Task></Task><Opcode>Info</Opcode><Channel></Channel><Provider></Provider><Keywords><Keyword>Classic</Keyword></Keywords></RenderingInfo></Event><Event xmlns='http://schemas.microsoft.com/win/2004/08/events/event'><System><Provider Name='Application Error'/><EventID Qualifiers='49152'>1005</EventID><Level>2</Level><Task>100</Task><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime='2011-09-22T01:21:42.000000000Z'/><EventRecordID>1054</EventRecordID><Channel>Application</Channel><Computer>INGEST-IIS-STF</Computer><Security/></System><EventData><Data></Data><Data>IIS Worker Process</Data><Data>C00000E9</Data><Data>0</Data></EventData><RenderingInfo Culture='en-US'><Message>Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program IIS Worker Process because of this error.

    Program: IIS Worker Process

    File:

    The error value is listed in the Additional Data section.

    User Action

    1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.

    2. If the file still cannot be accessed and

    - It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.

    - It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.

    3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.

    4. If the problem persists, restore the file from a backup copy.

    5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

    Additional Data

    Error value: C00000E9

    Disk type: 0</Message><Level>Error</Level><Task>Application Crashing Events</Task><Opcode></Opcode><Channel></Channel><Provider></Provider><Keywords><Keyword>Classic</Keyword></Keywords></RenderingInfo></Event><Event xmlns='http://schemas.microsoft.com/win/2004/08/events/event'><System><Provider Name='Application Error'/><EventID Qualifiers='0'>1000</EventID><Level>2</Level><Task>100</Task><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime='2011-09-22T01:21:42.000000000Z'/><EventRecordID>1053</EventRecordID><Channel>Application</Channel><Computer>INGEST-IIS-STF</Computer><Security/></System><EventData><Data>w3wp.exe</Data><Data>7.5.7600.16385</Data><Data>4a5bd0eb</Data><Data>nativerd.dll</Data><Data>7.5.7600.16385</Data><Data>4a5bdfcb</Data><Data>c0000006</Data><Data>0000000000012ddf</Data><Data>11a8</Data><Data>01cc78c5fbb743cd</Data><Data>c:\windows\system32\inetsrv\w3wp.exe</Data><Data>c:\windows\system32\inetsrv\nativerd.dll</Data><Data>39cdc543-e4b9-11e0-8c5b-78e3b518b572</Data></EventData><RenderingInfo Culture='en-US'><Message>Faulting application name: w3wp.exe, version: 7.5.7600.16385, time stamp: 0x4a5bd0eb

    Faulting module name: nativerd.dll, version: 7.5.7600.16385, time stamp: 0x4a5bdfcb

    Exception code: 0xc0000006

    Fault offset: 0x0000000000012ddf

    Faulting process id: 0x11a8

    Faulting application start time: 0x01cc78c5fbb743cd

    Faulting application path: c:\windows\system32\inetsrv\w3wp.exe

    Faulting module path: c:\windows\system32\inetsrv\nativerd.dll

    Report Id: 39cdc543-e4b9-11e0-8c5b-78e3b518b572</Message><Level>Error</Level><Task>

    Application Crashing Events</Task><Opcode>Info</Opcode><Channel></Channel><Provider></Provider><Keywords><Keyword>

    Classic</Keyword></Keywords></RenderingInfo></Event>

    <Event xmlns='http://schemas.microsoft.com/win/2004/08/events/event'><System><Provider Name='Windows Error Reporting'/>

    <EventID Qualifiers='0'>1001</EventID><Level>4</Level><Task>0</Task><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime='2011-09-22T01:21:33.000000000Z'/><EventRecordID>1052</EventRecordID><Channel>Application</Channel><Computer>INGEST-IIS-STF</Computer><Security/></System><EventData><Data></Data><Data>0</Data><Data>InPageError</Data><Data>Not available</Data><Data>0</Data><Data>c00000e9</Data><Data>00000000</Data><Data></Data><Data></Data><Data></Data><Data></Data><Data></Data><Data></Data><Data></Data><Data></Data><Data></Data><Data>C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_c00000e9_3b41138e0d6a3a5999551a9b476a72f74aebbf_1dc524a7</Data><Data></Data><Data>0</Data><Data>337a1c2c-e4b9-11e0-8c5b-78e3b518b572</Data><Data>0</Data></EventData><RenderingInfo Culture='en-US'><Message>Fault bucket , type 0

    Event Name: InPageError

    Response: Not available

    Cab Id: 0

    Problem signature:

    P1: c00000e9

    P2: 00000000

    P3:

    P4:

    P5:

    P6:

    P7:

    P8:

    P9:

    P10:

    Attached files:

    These files may be available here:

    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_c00000e9_3b41138e0d6a3a5999551a9b476a72f74aebbf_1dc524a7

     

    Thanks,

    Snehal

    Thursday, November 24, 2011 8:31 PM

All replies

  • What's crazy is I am getting this on Windows 2012R2 six years later. Mine is crashing in w3wp.exe in module oleaut32.dll. I suspect MSXML6 but I'm not sure as WinDBG and DebugDiag2 are vague and all the stack dumps show UNKNOWN for most address locations.

    Faulting application name: w3wp.exe, version: 8.5.9600.16384, time stamp: 0x5215df96
    Faulting module name: OLEAUT32.dll, version: 6.3.9600.18434, time stamp: 0x57a6178c
    Exception code: 0xc000001d
    Fault offset: 0x0000000000001123
    Faulting process id: 0x1f80
    Faulting application start time: 0x01d2ae3bbdbe01c2
    Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
    Faulting module path: C:\Windows\system32\OLEAUT32.dll
    Report Id: 6fd586b6-1a3a-11e7-80e1-0cc47a5625fd
    Faulting package full name:
    Faulting package-relative application ID:

    Then is the 1005 event id:

    Windows cannot access the file  for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program IIS Worker Process because of this error.
    Program: IIS Worker Process
    File:
    The error value is listed in the Additional Data section.
    User Action
    1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
    2. If the file still cannot be accessed and
     - It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
     - It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
    3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
    4. If the problem persists, restore the file from a backup copy.
    5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.
    Additional Data
    Error value: 00000000
    Disk type: 0

    Some things you don't want to become a classic.  Such as, a crashing bug.


    • Edited by Brain2000 Wednesday, April 5, 2017 8:18 PM
    Wednesday, April 5, 2017 8:15 PM