locked
KERNEL_DATA_INPAGE_ERRORs RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi


    I have had kernel_data_inpage_errors almost daily for a few weeks. I have followed everything on this link:

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

    as well as another thread that mentions malware bites anti malware and other virus checks.

    RAM is fine (ran memtest86). I also replaced it as a precaution. 

    chkdsk does not find anything. The error check in C:\ properties, tools, error checking doesn't find anything either. I ran HD Tune pro as well. It found 32 damaged sectors and said there were 1.5% damaged blocks. below is the health report

    HD Tune Pro: ST1000LM024 HN-M101MBB Health

    ID                              Current  Worst    ThresholdData          Status   
    (01) Raw Read Error Rate        100      100      51       5795          ok       
    (02) Throughput Performance     252      252      0        0             ok       
    (03) Spin Up Time               89       57       25       3474          ok       
    (04) Start/Stop Count           100      100      0        961           ok       
    (05) Reallocated Sector Count   252      252      10       0             ok       
    (07) Seek Error Rate            252      252      51       0             ok       
    (08) Seek Time Performance      252      252      15       0             ok       
    (09) Power On Hours Count       100      100      0        10824         ok       
    (0A) Spin Retry Count           252      252      51       0             ok       
    (0B) Calibration Retry Count    100      100      0        141           warning  
    (0C) Power Cycle Count          100      100      0        961           ok       
    (BF) G-sense Error Rate         100      100      0        22            ok       
    (C0) Unsafe Shutdown Count      252      252      0        0             ok       
    (C2) Temperature                53       29       0        304943005743  ok       
    (C3) Hardware ECC Recovered     100      100      0        0             ok       
    (C4) Reallocated Event Count    252      252      0        0             ok       
    (C5) Current Pending Sector     99       99       0        270           warning  
    (C6) Offline Uncorrectable      252      252      0        0             ok       
    (C7) Interface CRC Error Count  200      200      0        0             ok       
    (C8) Write Error Rate           100      100      0        24220         ok       
    (DF) Load/Unload Retry Count    100      100      0        141           ok       
    (E1) Load/Unload Cycle Count    61       61       0        396109        ok       

    Health Status         : warning

    I have uploaded the last 2 minidumps. They look different from each other. I also noticed that not all errors are generating minidumps.

    https://onedrive.live.com/redir?resid=C4DF0C7328972A99!135&authkey=!ACMmDn-5sfT1gm8&ithint=folder%2ctxt

    If it is my hard drive, is it possible to get the disk copied even though it has damaged blocks? I did not get a copy of windows with my laptop. From what I understand, a copy of windows is hidden on the drive.

    Thanks

    Tuesday, November 25, 2014 3:48 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    This is a very corrupt dump.

    KERNEL_DATA_INPAGE_ERROR (7a)

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

    BugCheck 7A, {fffff6fc80a15ee8, ffffffffc0000185, 173bb9880, fffff90142bddaa8}

    2nd argument is the NT status code for STATUS_IO_DEVICE_ERROR. This indicates improper termination or defective cabling on SCSI devices or that two devices are trying to use the same IRQ. It can also imply faulty hard disk in general.

    We can see many different pages aren't present, a sign of a bad hard disk:

    Page 11a379 not present in the dump file. Type ".hh dbgerr004" for details
Page 11a379 not present in the dump file. Type ".hh dbgerr004" for details
Page 11a379 not present in the dump file. Type ".hh dbgerr004" for details
Page 1227e5 not present in the dump file. Type ".hh dbgerr004" for details
Page 11a379 not present in the dump file. Type ".hh dbgerr004" for details
Page 11a379 not present in the dump file. Type ".hh dbgerr004" for details
Page 11a379 not present in the dump file. Type ".hh dbgerr004" for details
Page 1227e5 not present in the dump file. Type ".hh dbgerr004" for details
Page 11a379 not present in the dump file. Type ".hh dbgerr004" for details
Page 11a379 not present in the dump file. Type ".hh dbgerr004" for details
    ...etc

    Run Chkdsk and 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 driver related issues that may cause conflicts or a false positive, it may be a wise decision to choose the most minimal testing environment (DOS). I always recommend running Seatools in DOS if absolutely possible.

    -- Run all tests EXCEPT: Fix All and anything Advanced.

    Regards,

    Patrick

    “Be kind whenever possible. It is always possible.” - Dalai Lama

    • Marked as answer by Yolanda Zhu Monday, December 1, 2014 10:49 AM
    Wednesday, November 26, 2014 7:55 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    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.

    -- %systemroot% is the environment variable for your Windows directory. For example, C:\Windows.

    2. Copy any and all .DMP files in the Minidump folder to your Desktop, create a new folder on the Desktop to put these .DMP files in, and then zip the folder. You can then either use a 3rd party tool such as 7-Zip/Winrar, or you can use Windows' default method of zipping folders.

    Compress and uncompress files (zip files).

    Please note that any "cleaner" programs such as TuneUpUtilities, CCleaner, etc, by default will delete .DMP files upon use. With this said, if you've run such software, and your Minidump folder is empty, you will need to allow the system to crash once again to generate a crash dump.

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

    Preferred sites: Onedrive, Mediafire, Dropbox, etc. Nothing with wait-timers, download managers, etc.

    4 (optional): The type of .DMP files located in the Minidump folder are known as Small Memory Dumps. In %systemroot% there will be what is known as a Kernel Memory Dump (if your system is set to generate). It is labeled MEMORY.DMP. The difference between Small Memory Dumps and Kernel Memory Dumps in the simplest definition is a Kernel Memory Dump contains much more information at the time of the crash, therefore allowing further debugging of your issue. If your upload speed permits it, and you aren't going against any strict bandwidth and/or usage caps, etc, the Kernel Memory Dump is the best choice. Do note that Kernel Memory Dumps are much larger in size due to containing much more info, which is why I mentioned upload speed, etc.

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

    Upload photos and files to Onedrive.

    After doing that, to learn how to share the link to the file if you are unaware, please visit the following link - Share files and folders and change permissions and view 'Get a link'.

    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.

    4. 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

    “Be kind whenever possible. It is always possible.” - Dalai Lama

    Wednesday, November 26, 2014 7:07 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Minidump files zipped in 110814-167921-1.zip. Kernel Memory Dump in Memory.zip.

    https://onedrive.live.com/redir?resid=C4DF0C7328972A99%21135

    Thanks.

    Wednesday, November 26, 2014 10:19 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    This is a very corrupt dump.

    KERNEL_DATA_INPAGE_ERROR (7a)

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

    BugCheck 7A, {fffff6fc80a15ee8, ffffffffc0000185, 173bb9880, fffff90142bddaa8}

    2nd argument is the NT status code for STATUS_IO_DEVICE_ERROR. This indicates improper termination or defective cabling on SCSI devices or that two devices are trying to use the same IRQ. It can also imply faulty hard disk in general.

    We can see many different pages aren't present, a sign of a bad hard disk:

    Page 11a379 not present in the dump file. Type ".hh dbgerr004" for details
Page 11a379 not present in the dump file. Type ".hh dbgerr004" for details
Page 11a379 not present in the dump file. Type ".hh dbgerr004" for details
Page 1227e5 not present in the dump file. Type ".hh dbgerr004" for details
Page 11a379 not present in the dump file. Type ".hh dbgerr004" for details
Page 11a379 not present in the dump file. Type ".hh dbgerr004" for details
Page 11a379 not present in the dump file. Type ".hh dbgerr004" for details
Page 1227e5 not present in the dump file. Type ".hh dbgerr004" for details
Page 11a379 not present in the dump file. Type ".hh dbgerr004" for details
Page 11a379 not present in the dump file. Type ".hh dbgerr004" for details
    ...etc

    Run Chkdsk and 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 driver related issues that may cause conflicts or a false positive, it may be a wise decision to choose the most minimal testing environment (DOS). I always recommend running Seatools in DOS if absolutely possible.

    -- Run all tests EXCEPT: Fix All and anything Advanced.

    Regards,

    Patrick

    “Be kind whenever possible. It is always possible.” - Dalai Lama

    • Marked as answer by Yolanda Zhu Monday, December 1, 2014 10:49 AM
    Wednesday, November 26, 2014 7:55 PM