Share via

KERNEL_DATA_INPAGE_ERROR (msrpc.sys)

Anonymous
2013-12-12T18:12:51+00:00

Hi,

I have ever so often this error message on my laptop ASUS running Windows 8.1 with a i5 Intel processor and 4GB RAM.

This only happens when the computer comes out of hibernation or sleep. It was even worse when Power Management was managed by ASUS Power4Gear software it would crash all the time. I changed it to "Balanced" and the crashes sort of stopped but now they are becoming more frequent.

This morning after leaving the computer overnight on sleep on battery when I pressed the power button the same alert happened "KERNEL_DATA_INPAGE_ERROR (msrpc.sys)" and it restarted but when it restarted the processor fan was blasting full speed as if the processor had overheated. How can this happen if the computer was off (and cold by the way).

It crashed again a few minutes ago with the same error but this time was when I was on desktop mode noticed the orange up arrow alert from the Microsoft Upload Center on the bottom right tray on (I did not have anything to upload by the way), pressed it an it crashed.

I am really puzzled with this behaviour and would welcome any suggestions to resolve this situation.

Thanks

Windows for home | Previous Windows versions | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

3 answers

Sort by: Most helpful
  1. Anonymous
    2013-12-15T20:40:32+00:00

    Thank you, Paulo. This worked fine!

    All of the attached DMP files are of the KERNEL_DATA_INPAGE_ERROR (7a) bug check.

    This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.

    *ERROR_CODE: (NTSTATUS) 0xc000000e - **A device which does not exist was specified.*DISK_HARDWARE_ERROR: There was error with disk hardware

    ^^ 0xC000000E, or STATUS_NO_SUCH_DEVICE, indicates a hardware failure or an incorrect drive configuration. Check your cables and check the drive with the diagnostic utility available from your drive manufacturer. If you are using older PATA (IDE) drives, this status code can indicate an incorrect master/subordinate drive configuration.

    ** If you have an SSD, be 100% sure the firmware is up to date!

    Before running hard disk diagnostics, you have various problematic Asus drivers listed and loaded (Ai Charger) for example. I am going to recommend removal of all Asus software on your system as it's very buggy bloatware. If you have Asus AI Suite, it's usually all bundled into that.

    -------------------------------------------------

    If you're still crashing after the above, it's time for some hard disk diagnostics. Start with a chkdsk (attach log afterwards) and then run Seatools:

    Chkdsk:There are various ways to run Chkdsk~

    Method 1:

    Start > Search bar > Type cmd (right click run as admin to execute Elevated CMD)

    Elevated CMD should now be opened, type the following:

    chkdsk x: /r

    x implies your drive letter, so if your hard drive in question is letter c, it would be:

    chkdsk c: /r

    Restart system and let chkdsk run.

    Method 2:

        Open the "Computer" window

        Right-click on the drive in question

        Select the "Tools" tab

        In the Error-checking area, click <Check Now>.

    If you'd like to get a log file that contains the chkdsk results, do the following:

    Press Windows Key + R and type powershell.exe in the run box

    Paste the following command and press enter afterwards:

    get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file Desktop\CHKDSKResults.txt

    This will output a .txt file on your Desktop containing the results of the chkdsk.

    If chkdsk turns out okay, run Seatools -

    http://www.seagate.com/support/downloads/seatools/

    You can run it via Windows or DOS. Do note that the only difference is simply the environment you're running it in. In Windows, if you are having what you believe to be device driver related issues that may cause conflicts or false positive, it may be a wise decision to choose the most minimal testing environment (DOS).

    Run all tests EXCEPT: Fix All, Long Generic, and anything Advanced.

    Regards,

    Patrick

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2013-12-15T18:04:04+00:00

    Hi Patrick

    I only had 3 .dmp files in the folder. The link to the SkyDrive location isÇ

    https://skydrive.live.com/redir?resid=17DADC828E294CA3!4060&authkey=!AP7aUDEaX1fByAo&ithint=file%2c.zip

    I hope this is OK and you can find what is causing this fault.

    Thanks

    Paulo

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2013-12-12T21:41:15+00:00

    Hi,

    In order to assist you, we will need the DMP files to analyze what exactly occurred at the time of the crash, etc.

    If you don't know where DMP files are located, here's how to get to them:

     1.    Navigate to the %systemroot%\Minidump folder.

     2.    Copy any and all DMP files in the Minidump folder to your Desktop and then zip up these files.

     3.    Upload the zip containing the DMP files to Skydrive or a hosting site of your choice and paste in your reply.

    If you are going to use Skydrive but don't know how to upload to it, please visit the following:

    http://www.wikihow.com/Use-SkyDrive

    Please note that any "cleaner" programs such as TuneUp Utilities, CCleaner, etc, by default will delete DMP files upon use.

    If your computer is not generating DMP files, please do the following:

    1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.
    2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.
    3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

    Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.

    1. Double check that the WERS is ENABLED:

    Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

    If you cannot get into normal mode to do any of this, please do this via Safe Mode.

    Regards,

    Patrick

    Was this answer helpful?

    0 comments No comments