Kernel Data Inpage Error


  1. Posts : 2
    Windows 7
       #1

    Kernel Data Inpage Error


    My computer is having a serious problem.
    I got a Kernel Data Inpage Error BSOD. It appears more often lately, usually it happens when i leave the computer for about a couple of minutes. I'm not using any nvidia drivers like in other threads said. I have run disk check and have no errors. Please someone help me

    The BSOD technical information.

    *** STOP : 0x0000007A (0xC044F5D0, 0xc0000185, 0x6818c860, 0x89eba9c4 )
    *** ataport.SYS - Address 89eba9c4 base at 89ea2000. datestamp 4a5bbf16

    The minidump is in the attachments.

    Please help. Thanks :)
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    remmyzen said:
    My computer is having a serious problem.
    I got a Kernel Data Inpage Error BSOD. It appears more often lately, usually it happens when i leave the computer for about a couple of minutes. I'm not using any nvidia drivers like in other threads said. I have run disk check and have no errors. Please someone help me

    The BSOD technical information.

    *** STOP : 0x0000007A (0xC044F5D0, 0xc0000185, 0x6818c860, 0x89eba9c4 )
    *** ataport.SYS - Address 89eba9c4 base at 89ea2000. datestamp 4a5bbf16

    The minidump is in the attachments.

    Please help. Thanks :)

    Remmyzen

    These crashes appear to have 5 different causes including ESET, video driver, etc. But when one looks closer they all point to the same thing memory corruption.

    To test you memory
    Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.


    You also have drivers (including ESET) that are old and need to be updated. See the list below.

    If you are overclocking stop
    If you are running a RAID update its driver.

    Let us know if this doesn't fix the problem.


    Ken




    Analysis
    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\Minidump\053010-22105-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
    *http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16539.x86fre.win7_gdr.100226-1909
    Machine Name:
    Kernel base = 0x83e0c000 PsLoadedModuleList = 0x83f54810
    Debug session time: Sun May 30 04:17:54.289 2010 (GMT-4)
    System Uptime: 0 days 0:15:31.365
    Loading Kernel Symbols
    .
    
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    
    ..............................................................
    ................................................................
    .....................................
    Loading User Symbols
    Loading unloaded module list
    ......
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    KERNEL_DATA_INPAGE_ERROR (7a)
    The requested page of kernel data could not be read in.  Typically caused by
    a bad block in the paging file or disk controller error. Also see
    KERNEL_STACK_INPAGE_ERROR.
    If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
    it means the disk subsystem has experienced a failure.
    If the error status is 0xC000009A, then it means the request failed because
    a filesystem failed to make forward progress.
    Arguments:
    Arg1: c045d9e0, lock type that was held (value 1,2,3, or PTE address)
    Arg2: c0000185, error status (normally i/o status code)
    Arg3: 441698c0, current process (virtual address for lock type 3, or PTE)
    Arg4: 8bb3c000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
    
    Debugging Details:
    ------------------
    
    
    ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.
    
    DISK_HARDWARE_ERROR: There was error with disk hardware
    
    BUGCHECK_STR:  0x7a_c0000185
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  svchost.exe
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  b94f9704 -- (.trap 0xffffffffb94f9704)
    ErrCode = 00000002
    eax=8bb3c000 ebx=92a1b260 ecx=866d14a8 edx=00000003 esi=866d14a8 edi=8bb3c000
    eip=8408ab59 esp=b94f9778 ebp=b94f978c iopl=0         nv up ei ng nz ac pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010296
    nt!MiRelocateImageAgain+0x38:
    8408ab59 f00fba2800      lock bts dword ptr [eax],0   ds:0023:8bb3c000=00001298
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from 83ec061a to 83ee8d10
    
    STACK_TEXT:  
    b94f955c 83ec061a 0000007a c045d9e0 c0000185 nt!KeBugCheckEx+0x1e
    b94f95d0 83eb80e5 860eef04 b94f9628 83f40300 nt!MiWaitForInPageComplete+0x2fd
    b94f9664 83e93e5f 83f40300 8bb3c000 860eee70 nt!MiIssueHardFault+0x3b2
    b94f96ec 83e52638 00000001 8bb3c000 00000000 nt!MmAccessFault+0x2656
    b94f96ec 8408ab59 00000001 8bb3c000 00000000 nt!KiTrap0E+0xdc
    b94f978c 8402f689 8bb65bc0 00000000 00000000 nt!MiRelocateImageAgain+0x38
    b94f98a8 8403ce91 b94f98fc 0000000d b94f9950 nt!MmCreateSection+0x531
    b94f991c 84010cc4 b94f99ac 0000000d b94f9950 nt!NtCreateSection+0x16e
    b94f9998 84010712 b94f9a58 b504aab0 00000201 nt!PfpFileBuildReadSupport+0xe4
    b94f9a2c 840120f2 004f9a58 b94f9bb4 00000001 nt!PfpPrefetchFilesTrickle+0xdf
    b94f9ad0 84011daf b5048000 9de1c728 b94f9bc8 nt!PfpPrefetchRequestPerform+0x2a6
    b94f9b24 8402b9c7 b94f9bb4 84221b01 9de1c7e4 nt!PfpPrefetchRequest+0x16e
    b94f9be8 84097936 00faf5d8 00000014 84221b01 nt!PfSetSuperfetchInformation+0x182
    b94f9d20 83e4f44a 0000004f 00000000 00000014 nt!NtSetSystemInformation+0xb00
    b94f9d20 771664f4 0000004f 00000000 00000014 nt!KiFastCallEntry+0x12a
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    00faf5f0 00000000 00000000 00000000 00000000 0x771664f4
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiWaitForInPageComplete+2fd
    83ec061a cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!MiWaitForInPageComplete+2fd
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cacf
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  0x7a_c0000185_nt!MiWaitForInPageComplete+2fd
    
    BUCKET_ID:  0x7a_c0000185_nt!MiWaitForInPageComplete+2fd
    
    Followup: MachineOwner
    ---------
    old drivers needing update.
    Code:
    cvintdrv.SYS        0x949f0000    0x949f1000    0x00001000    0x432f2aa5    9/19/2005 17:16:21                        
    DPortIO.sys        0x8f33f000    0x8f342380    0x00003380    0x43abb190    12/23/2005 04:13:04                        
    windrvr6.sys        0x98736000    0x987656e0    0x0002f6e0    0x45336063    10/16/2006 06:35:15                        
    DKbFltr.sys        0x93c00000    0x93c0a000    0x0000a000    0x4537363c    10/19/2006 04:24:28                        
    AGRSM.sys        0x820b8000    0x821be000    0x00106000    0x49184ba5    11/10/2008 10:56:37                        
    Epfwndis.sys        0x9864e000    0x98659000    0x0000b000    0x498c35c8    2/6/2009 09:06:16                        
    epfw.sys        0x821cb000    0x821ee000    0x00023000    0x498c35ca    2/6/2009 09:06:18                        
    epfwwfp.sys        0x949f1000    0x949ff000    0x0000e000    0x498c35ca    2/6/2009 09:06:18                        
    eamon.sys    eamon.sys+507f    0x82338000    0x823f4000    0x000bc000    0x498c37ad    2/6/2009 09:14:21                        
    ehdrv.sys        0x8a543000    0x8a55f000    0x0001c000    0x498c37d5    2/6/2009 09:15:01                        
    RTKVHDA.sys        0x81e38000    0x8206fc40    0x00237c40    0x49a9ba0c    2/28/2009 18:26:20                        
    aghfgfzu.SYS        0x98600000    0x98638000    0x00038000    0x49c4fe02    3/21/2009 10:47:30                        
    sptd.sys        0x89c1b000    0x89d1c000    0x00101000    0x49c72e69    3/23/2009 02:38:33                        
    spldr.sys        0x8a3ea000    0x8a3f2000    0x00008000    0x4a084ebb    5/11/2009 12:13:47                        
    amdxata.sys        0x89eb9000    0x89ec2000    0x00009000    0x4a12f30f    5/19/2009 13:57:35
      My Computer


  3. Posts : 2
    Windows 7
    Thread Starter
       #3

    i've tried some of your ways man, so far so good, thanks

    i'll update this thread if the BSOD happen again. thanks :)
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 05:31.
Find Us