KERNEL_DATA_INPAGE_ERROR help please!

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by C0BRA, Jul 14, 2012.

  1. C0BRA

    C0BRA Well-Known Member

    Joined:
    Jul 13, 2012
    Messages:
    22
    Likes Received:
    0
    This BSoD problem has been going on for a while and I'm fed up with it and ready to solve it. I came here hoping to finally get rid of this. All the files needed are attached below. The computer I'm using is a HP dv6500 running Windows 7 Home Premium. I also put a text file in the folder telling what Windows Solutions said about the problem. If any other information is needed, please let me know. Thanks for any help, it is surely appreciated.
     

    Attached Files:

  2. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,850
    Likes Received:
    1,569
    Hi Cobra,

    For some reason your dmp files are not opening properly. Do you have others you could post?
     
  3. C0BRA

    C0BRA Well-Known Member

    Joined:
    Jul 13, 2012
    Messages:
    22
    Likes Received:
    0
    Could you tell me where those might be located?
     
  4. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,850
    Likes Received:
    1,569
    Look in your C:Windows/Minidump folder. Also are you sure your system is configured correctly for creating dmp files? Check my screenie and make sure your settings are the same. (I know I'm using win 8 but it's the same regardless)

    dmp.
     
  5. C0BRA

    C0BRA Well-Known Member

    Joined:
    Jul 13, 2012
    Messages:
    22
    Likes Received:
    0
    Ok, I changed it and made it look like yours. It was set to Kernel dump so I had to change it to Small memory dump (128 KB). Now what?
     
  6. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,850
    Likes Received:
    1,569
    Great. Now as soon as you get a bsod please post...
     
  7. C0BRA

    C0BRA Well-Known Member

    Joined:
    Jul 13, 2012
    Messages:
    22
    Likes Received:
    0
    Here ya go
     

    Attached Files:

  8. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,850
    Likes Received:
    1,569
    Got it to open eventually lol.. Well to start off your drivers are out of the ark. I tried the manufacturers web page for your machine but noticed only vista drivers. Here's the link anyway please try and update where possible.

    http://h10025.www1.hp.com/ewfrf/wc/product?cc=us&lc=en&dlc=en&product=3380544&jumpid=re_r163_eolproducts_psg_mar2011_dv6500_support_top

    Can you also run a chkdsk as the dmp file mentions a possible disk error.

    Lastly you also need to check your RAM. Test using this app: http://www.memtest.org/ and only on one stick at a time so you know one which errors out.
     
    #8 kemical, Jul 16, 2012
    Last edited: Jul 16, 2012
  9. C0BRA

    C0BRA Well-Known Member

    Joined:
    Jul 13, 2012
    Messages:
    22
    Likes Received:
    0
    I've tried updating the drivers before but that didn't help. I've also run chkdsk multiple times (does it on its own usually when theres a BSoD). I've also checked my RAM and, although it isn't the best (1GB is ungodly slow), it seems to be perfectly fine. This was happening before I reinstalled Windows as well. Of course, when I reinstalled Windows, it came back. I used BlueScreenViewer to open the .dmp files and it looks like the problem is coming from ntoskrnl.exe although I'm not sure on how to fix this problem. A different blue screen has come up twice but with the same error, the Kernel Data Inpage Error. But two were effected by dxgkrnl.exe and another by volmgrx.sys but when viewed in BlueScreenViewer, it seemed it was ntoskrnl.exe at fault. Whew, that was a lot of typing.
     
  10. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,850
    Likes Received:
    1,569
    dxgkrnl.exe=Display driver


    volmgrx.sys=Microsoft Windows volume manager extension driver


    Kernel Data Inpage Error=This Stop message indicates that the requested page of kernel data from the paging file could not be read into memory. This Stop message is usually caused by a bad block (sector) in a paging file, a virus, a disk controller error, or failing RAM. In rare cases, it is caused when nonpaged pool resources run out. It is also caused by defective hardware.

    How did you check your RAM?

    Also when you say you 'tried' to update your drivers what does that mean?

    What happens with chkdsk does it run though correctly?


    I've just been reading the web page of your machine. It isn't supported by HP for Windows 7. Did you ever run the windows 7 compatibility tool? I'm sure we have had similar posts with the same system as yours as the name of the machine was kinda familiar. Try running this app and please post the results:

    Download: Windows 7 Upgrade Advisor - Microsoft Download Center - Download Details
     
  11. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    As Kemical has already indicated you need to perform a complete and comprehensive check on your memory and hard drive.
    Code:
    KERNEL_DATA_INPAGE_ERROR (7a)
    [U][B][COLOR=#ff0000]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[/COLOR][/B][/U]. Also see
    KERNEL_STACK_INPAGE_ERROR.
    [COLOR=#ff0000][U][B]If the error status is[/B][/U][/COLOR] [COLOR=#ff0000][U][B]0xC000000E[/B][/U][/COLOR], 0xC000009C, 0xC000009D or 0xC0000185,
    [COLOR=#ff0000][U][B]it means the disk subsystem has experienced a failure[/B][/U][/COLOR].
    If the error status is 0xC000009A, then it means the request failed because
    a filesystem failed to make forward progress.
    Arguments:
    Arg1: c0416820, lock type that was held (value 1,2,3, or PTE address)
    [COLOR=#ff0000][U][B]Arg2: c000000e, error status (normally i/o status code)[/B][/U][/COLOR]
    Arg3: 12389860, current process (virtual address for lock type 3, or PTE)
    Arg4: 82d04d37, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
    ERROR_CODE: (NTSTATUS) 0xc000000e - [U][B][COLOR=#ff0000]A device which does not exist was specified[/COLOR][/B][/U].
    [COLOR=#ff0000][U][B]DISK_HARDWARE_ERROR: There was error with disk hardware[/B][/U][/COLOR]
    [COLOR=#ff0000][U][B]BUGCHECK_STR:  0x7a_c000000e[/B][/U][/COLOR]
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  0
    TRAP_FRAME:  88f1fa14 -- (.trap 0xffffffff88f1fa14)
    ErrCode = 00000010
    eax=84aacc01 ebx=00010000 ecx=2c000128 edx=00010000 esi=84aacb80 edi=84a97008
    eip=82d04d37 esp=88f1fa88 ebp=88f1fab0 iopl=0         nv up ei pl nz na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
    nt!PnpRequestDeviceRemoval:
    82d04d37 8bff            mov     edi,edi
    Resetting default scope
    LOCK_ADDRESS:  82bacbe0 -- (!locks 82bacbe0)
    Resource @ nt!PiEngineLock (0x82bacbe0)    Available
    WARNING: SystemResourcesList->[COLOR=#ff0000][U][B]Flink chain invalid. Resource may be corrupted, or already deleted.[/B][/U][/COLOR]
    WARNING: SystemResourcesList->[COLOR=#ff0000][U][B]Blink chain invalid. Resource may be corrupted, or already deleted.[/B][/U][/COLOR]
    1 total locks
    PNP_TRIAGE: 
        Lock address  : 0x82bacbe0
        Thread Count  : 0
        Thread address: 0x00000000
        Thread wait   : 0x0
    LAST_CONTROL_TRANSFER:  from 82ae9dd8 to 82b24e9c
    STACK_TEXT:  
    88f1f874 82ae9dd8 0000007a c0416820 c000000e nt!KeBugCheckEx+0x1e
    88f1f8e4 82aed6b9 88f1f938 82bb0300 88f1f958 nt!MiWaitForInPageComplete+0x302
    88f1f974 82ad691b 82bb0300 82d04d37 854ada00 nt!MiIssueHardFault+0x3b3
    88f1f9fc 82a87468 00000008 82d04d37 00000000 nt!MmAccessFault+0x2656
    88f1f9fc 82d04d37 00000008 82d04d37 00000000 nt!KiTrap0E+0xdc
    88f1fa84 82c040e3 00000018 84a97008 00000000 nt!PnpRequestDeviceRemoval
    88f1fab0 82c03093 95c2f8c0 84a97008 00000002 nt!PipEnumerateCompleted+0x12e
    88f1fca4 82c03e29 84a97008 95c2f8c0 88f1fcd0 nt!PipProcessDevNodeTree+0x352
    88f1fcd8 82a5ad10 82baab00 841ba798 82b813bc nt!PiProcessReenumeration+0x74
    88f1fd00 82ac3a6b 00000000 00000000 841ba798 nt!PnpDeviceActionWorker+0x224
    88f1fd50 82c4f056 00000001 9c185680 00000000 nt!ExpWorkerThread+0x10d
    88f1fd90 82af71a9 82ac395e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt!MiWaitForInPageComplete+302
    82ae9dd8 cc              int     3
    SYMBOL_STACK_INDEX:  1
    SYMBOL_NAME:  nt!MiWaitForInPageComplete+302
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    DEBUG_FLR_IMAGE_TIMESTAMP:  4f766ae5
    IMAGE_NAME: [COLOR=#ff0000][U][B] memory_corruption[/B][/U][/COLOR]
    FAILURE_BUCKET_ID:  0x7a_c000000e_nt!MiWaitForInPageComplete+302
    BUCKET_ID:  0x7a_c000000e_nt!MiWaitForInPageComplete+302
    So........
    and from an elevated command prompt type
    chkdsk C: /R
    answer yes "Y" when prompted and reboot, let it finish all five stages and check the event viewer for the results
    also determine the manufacturer of your hard drive and obtain their vendor specific proprietary hard disk diagnostic software for a more in-depth examination of the drive. A partial list and links can be found here Hard Drive Diagnostics Tools and Utilities (Storage) - TACKtech Corp.
    Finally update the following out dated drivers
    [TABLE="width: 1753"]
    [TR]
    [TD]netw5v32.sys[/TD]
    [TD="align: right"]3/26/2009[/TD]
    [TD]Intel(R) PRO/Wireless 3945ABG Network Connection[/TD]
    [TD]http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=21244&ProdId=2259&lang=eng&OSVersion=Windows%207%20%2832-bit%29*&DownloadType=Software%20Applications[/TD]
    [/TR]
    [TR]
    [TD]rimmptsk.sys[/TD]
    [TD="align: right"]6/25/2009[/TD]
    [TD]Ricoh Memory Card Reader Driver[/TD]
    [TD][/TD]
    [/TR]
    [TR]
    [TD]rimsptsk.sys[/TD]
    [TD="align: right"]6/25/2009[/TD]
    [TD]Ricoh Memory Card Reader Driver[/TD]
    [TD][/TD]
    [/TR]
    [TR]
    [TD]rixdptsk.sys[/TD]
    [TD="align: right"]6/25/2009[/TD]
    [TD]Ricoh Memory Card Reader Driver[/TD]
    [TD][/TD]
    [/TR]
    [TR]
    [TD]Rt86win7.sys[/TD]
    [TD="align: right"]2/26/2009[/TD]
    [TD]Realtek Network Adapter[/TD]
    [TD]Realtek[/TD]
    [/TR]
    [TR]
    [TD]RTKVHDA.sys[/TD]
    [TD="align: right"]1/15/2008[/TD]
    [TD]Realtek HD Audio Codec Driver [/TD]
    [TD]Realtek[/TD]
    [/TR]
    [/TABLE]
     
    1 person likes this.
  12. Rahul Mhatre

    Joined:
    Nov 11, 2013
    Messages:
    1
    Likes Received:
    0
    i have same blue screen prob ,,
     

    Attached Files:

  13. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,850
    Likes Received:
    1,569
    Code:
    *******************************************************************************
    *                                                                            *
    *                        Bugcheck Analysis                                    *
    *                                                                            *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {4, 12c, ffffe00005d0b880, ffffd0002079b860}
    
    Implicit thread is now ffffe000`05d0b880
    Probably caused by : BthEnum.sys
    
    Followup: MachineOwner
    
    Hi,
    your dmp file points to a bluetooth driver as the culprit. Checking your laptops website I see there are updates specifically for 8.1 and Bluetooth (along with other updates too)
    Download and install updates and if issue continues post back:

    http://www.sony.co.in/product/sve15117fn
     

Share This Page

Loading...