BSOD Kernel Data INPAGE


  1. igi0n
    Posts : 1
    Windows 7 Ultimate 32 bit
       New #1

    BSOD Kernel Data INPAGE


    Hello fellow people!

    I've got a BSOD since a half year now and it bugs me out. It always happens when i boot up a game, sometimes it doesn't. It gives me the KERNEL_DATA_INPAGE error and it says 0x000007 or something like that.

    In the attachement there is my minidump!
      My Computer
    Quote Quote

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

    igi0n said:
    Hello fellow people!

    I've got a BSOD since a half year now and it bugs me out. It always happens when i boot up a game, sometimes it doesn't. It gives me the KERNEL_DATA_INPAGE error and it says 0x000007 or something like that.

    In the attachement there is my minidump!

    Easy, memory corruption.

    Run memtest to test your 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.


    Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

    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\110410-24289-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.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82848000 PsLoadedModuleList = 0x82990810
Debug session time: Thu Nov  4 08:16:05.958 2010 (GMT-5)
System Uptime: 0 days 2:04:08.003
Loading Kernel 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: c0443098, lock type that was held (value 1,2,3, or PTE address)
Arg2: c0000185, error status (normally i/o status code)
Arg3: 102a6860, current process (virtual address for lock type 3, or PTE)
Arg4: 886139e8, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------

GetPointerFromAddress: unable to read from 829b0700

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:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  8a923c68 -- (.trap 0xffffffff8a923c68)
ErrCode = 00000010
eax=00000001 ebx=86522460 ecx=00000000 edx=828897dd esi=8557e0e0 edi=84872838
eip=886139e8 esp=8a923cdc ebp=8a923cec iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
ataport!IdePortScanChannel:
886139e8 650020          add     byte ptr gs:[eax],ah            gs:00000001=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from 828fc60a to 82924d10

STACK_TEXT:  
8a923af4 828fc60a 0000007a c0443098 c0000185 nt!KeBugCheckEx+0x1e
8a923b68 828f40d5 863f809c 8a923b90 8297c540 nt!MiWaitForInPageComplete+0x2fd
8a923bcc 828cfe3f 8297c540 886139e8 863f8008 nt!MiIssueHardFault+0x3b2
8a923c50 8288e5f8 00000008 886139e8 00000000 nt!MmAccessFault+0x2656
8a923c50 886139e8 00000008 886139e8 00000000 nt!KiTrap0E+0xdc
8a923cd8 886184ee 8557e0e0 8557e028 829825bc ataport!IdePortScanChannel
8a923cec 82a687b5 8557e028 8557e0e0 848bdd48 ataport!ChannelQueryBusRelation+0x40
8a923d00 828b5f2b 84872838 00000000 848bdd48 nt!IopProcessWorkItem+0x23
8a923d50 82a5666d 00000001 a92d4092 00000000 nt!ExpWorkerThread+0x10d
8a923d90 829080d9 828b5e1e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !ataport
    88613000 - ataport!___PchSym_ <PERF> (ataport+0x13000)
    [ 00:67 ]
    88613002 - ataport!___PchSym_ <PERF> (ataport+0x13002) (+0x02)
    [ 00:65 ]
    88613004 - ataport!___PchSym_ <PERF> (ataport+0x13004) (+0x02)
    [ 00:73 ]
    88613006-8861302a  37 bytes - ataport!ChannelInitializeAcpiTiming (+0x02)
    [ 8b ff 55 8b ec 8b 45 0c:70 00 65 00 6c 00 64 00 ]
    8861302c-88613038  13 bytes - ataport!ChannelInitializeAcpiTiming+26 (+0x26)
    [ cc cc cc cc cc cc 8b ff:20 00 61 00 70 00 70 00 ]
    8861303a-8861303c  3 bytes - ataport!IdeAllocateCrbLog+8 (+0x0e)
    [ 20 61 88:61 00 74 ]
    8861303e-88613046  9 bytes - ataport!IdeAllocateCrbLog+c (+0x04)
    [ 74 2e 56 68 49 64 65 50:20 00 77 00 6f 00 72 00 ]
    88613048 - ataport!IdeAllocateCrbLog+16 (+0x0a)
    [ 18:74 ]
    8861304a-8861304c  3 bytes - ataport!IdeAllocateCrbLog+18 (+0x02)
    [ 00 56 6a:20 00 67 ]
    8861304e-8861305a  13 bytes - ataport!IdeAllocateCrbLog+1c (+0x04)
    [ ff 15 80 12 61 88 8b 4d:65 00 73 00 6c 00 6f 00 ]
    8861305c-88613062  7 bytes - ataport!IdeAllocateCrbLog+2a (+0x0e)
    [ 00 85 c0 74 0c 56 6a:2e 00 20 00 57 00 61 ]
    88613064-88613070  13 bytes - ataport!IdeAllocateCrbLog+32 (+0x08)
    [ 50 e8 58 ba ff ff 83 c4:63 00 68 00 74 00 20 00 ]
    88613072-88613086  21 bytes - ataport!IdeAllocateCrbLog+40 (+0x0e)
    [ cc cc cc cc cc cc 8b ff:20 00 61 00 61 00 6e 00 ]
    88613088-8861308e  7 bytes - ataport!IdeFreeCrbLog+10 (+0x16)
    [ 8b 06 85 c0 74 13 6a:6f 00 6e 00 64 00 65 ]
    88613090-88613098  9 bytes - ataport!IdeFreeCrbLog+18 (+0x08)
    [ 50 ff 15 7c 12 61 88 83:6e 00 20 00 65 00 6e 00 ]
    8861309a-8861309e  5 bytes - ataport!IdeFreeCrbLog+22 (+0x0a)
    [ 83 a7 a8 03 00:70 00 72 00 6f ]
    886130a0-886130b8  25 bytes - ataport!IdeFreeCrbLog+28 (+0x06)
    [ 00 5f 5e 5d c2 04 00 cc:62 00 65 00 65 00 72 00 ]
    886130ba - ataport!IdeAllocateEnumInfo+e (+0x1a)
    [ 08:65 ]
    886130bc-886130be  3 bytes - ataport!IdeAllocateEnumInfo+10 (+0x02)
    [ 00 57 6a:75 00 77 ]
    886130c0-886130dc  29 bytes - ataport!IdeAllocateEnumInfo+14 (+0x04)
    [ ff 15 80 12 61 88 8b f0:2e 00 52 00 44 00 65 00 ]
    886130de-886130e4  7 bytes - ataport!IdeAllocateEnumInfo+32 (+0x1e)
    [ 88 4e 02 8a 80 48 11:61 00 6c 00 69 00 61 ]
    886130e6-886130f2  13 bytes - ataport!IdeAllocateEnumInfo+3a (+0x08)
    [ 00 83 c4 0c 88 06 5f 8b:73 00 20 00 77 00 6f 00 ]
    886130f4-88613104  17 bytes - ataport!IdeAllocateEnumInfo+48 (+0x0e)
    [ cc cc cc cc cc cc 8b ff:20 00 61 00 6c 00 20 00 ]
    88613106-88613110  11 bytes - ataport!IdeFreeDeviceParameters+c (+0x12)
    [ 75 08 8b 4d 0c 89 48 04:69 00 6b 00 74 00 20 00 ]
    88613112-8861313d  44 bytes - ataport!IdeFreeDeviceParameters+18 (+0x0c)
    [ ff 75 0c ff 15 7c 12 61:20 00 64 00 65 00 7a 00 ]
    8861313f-88613144  6 bytes - ataport!IdeAllocateTargetInfo+1b (+0x2d)
    [ 08 c7 45 f8 9a 00:00 69 00 6b 00 20 ]
    88613146-8861316c  39 bytes - ataport!IdeAllocateTargetInfo+22 (+0x07)
    [ c0 88 5d fd e8 93 a8 ff:65 00 65 00 6e 00 20 00 ]
    8861316e-88613186  25 bytes - ataport!IdeAllocateTargetInfo+4a (+0x28)
    [ fe 46 01 83 65 f8 00 eb:20 00 6f 00 70 00 67 00 ]
    88613188-886131a2  27 bytes - ataport!IdeAllocateTargetInfo+64 (+0x1a)
    [ cc cc cc cc cc cc 8b ff:72 00 61 00 6d 00 65 00 ]
    886131a4-886131c8  37 bytes - ataport!IdeFreeTargetInfo+16 (+0x1c)
    [ 8b 1f 8d 44 86 08 8b 08:65 00 6c 00 64 00 69 00 ]
    886131ca-886131e0  23 bytes - ataport!IdeFreeTargetInfo+3c (+0x26)
    [ cc cc cc cc cc cc 8b ff:72 00 61 00 63 00 68 00 ]
    886131e2-88613217  54 bytes - ataport!IdeComputeCheckSum+12 (+0x18)
    [ e8 3f 5d ff ff 8b f8 6a:74 00 75 00 75 00 72 00 ]
    88613219-8861323a  34 bytes - ataport!IdeDigestIdentifyData+9 (+0x37)
    [ 0c 0f b7 06 33 db 84 c0:00 69 00 6b 00 2e 00 20 ]
    8861323c - ataport!IdeDigestIdentifyData+2c (+0x23)
    [ b9:65 ]
    8861323e - ataport!IdeDigestIdentifyData+2e (+0x02)
    [ 01:6e ]
    88613240-8861324a  11 bytes - ataport!IdeDigestIdentifyData+30 (+0x02)
    [ 00 66 3b c1 75 06 81 cb:2c 00 20 00 6d 00 6f 00 ]
    8861324c-88613250  5 bytes - ataport!IdeDigestIdentifyData+3c (+0x0c)
    [ 56 e8 20 20 00:20 00 75 00 20 ]
    88613252-8861325a  9 bytes - ataport!IdeDigestIdentifyData+42 (+0x06)
    [ 84 c0 74 61 81 cb 00 01:64 00 65 00 20 00 70 00 ]
    8861325c-88613264  9 bytes - ataport!IdeDigestIdentifyData+4c (+0x0a)
    [ 83 7d 10 01 75 55 8a 86:72 00 61 00 6d 00 65 00 ]
    88613266 - ataport!IdeDigestIdentifyData+56 (+0x0a)
    [ 00:65 ]
    88613268-88613274  13 bytes - ataport!IdeDigestIdentifyData+58 (+0x02)
    [ 24 03 3c 01 75 03 83 cb:72 00 20 00 27 00 73 00 ]
    88613276-8861327c  7 bytes - ataport!IdeDigestIdentifyData+66 (+0x0e)
    [ 00 40 74 0f f6 86 ae:65 00 61 00 62 00 6c ]
    8861327e - ataport!IdeDigestIdentifyData+6e (+0x08)
    [ 00:65 ]
    88613280-88613284  5 bytes - ataport!IdeDigestIdentifyData+70 (+0x02)
    [ 40 74 06 81 cb:27 00 20 00 62 ]
    88613286 - ataport!IdeDigestIdentifyData+76 (+0x06)
    [ 10:69 ]
    88613288-8861328c  5 bytes - ataport!IdeDigestIdentifyData+78 (+0x02)
    [ 00 0f b7 86 a4:6a 00 20 00 65 ]
    8861328e - ataport!IdeDigestIdentifyData+7e (+0x06)
    [ 00:6c ]
    88613290-8861329a  11 bytes - ataport!IdeDigestIdentifyData+80 (+0x02)
    [ a8 04 74 0b f6 06 80 74:6b 00 65 00 20 00 6f 00 ]
    8861329c - ataport!IdeDigestIdentifyData+8c (+0x0c)
    [ 20:72 ]
    8861329e-886132a6  9 bytes - ataport!IdeDigestIdentifyData+8e (+0x02)
    [ 00 a8 20 75 14 0f b7 86:61 00 63 00 68 00 74 00 ]
WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view  entire output.
3833 errors : !ataport (88613000-88613fff)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE_4096

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE_4096

BUCKET_ID:  MEMORY_CORRUPTION_LARGE_4096

Followup: memory_corruption
---------
    If you are overclocking stop. If you are running a raid update its driver.

    let us know if you need further assistance

    Ken
      My Computer
    Quote Quote

 

  Related Discussions
BSOD - Kernel Data inpage error
in BSOD Help and Support

I've had this problem for a month now and it only seems to be getting worse - that is my laptop is starting to crash even more frequently. I've tried running "chkdsk” but get the "Autochk cannot run due to an error caused by a recently installed software package" error. EDIT: I uninstalled my...
Hi, I've got BSOD with this message. I tried to fix this with the Hotfix which I downloaded from http://support.microsoft.com/kb/977178 but when I press Windows6.1-KB977178-v2-x64.msu file, I got a message: The update is not applicable to your computer. What can I do to fix it? My OS is...
BSOD Kernel Data Inpage Error
in BSOD Help and Support

Hello, Had this computer for a couple of years now and been getting 07a bug. The drives are all reporting healthy (HD Sentinel), ran chkdsk /f and sfc, malwarebytes. partmgr.sys and classpnp.sys are showing up in the crash reports. If someone can take a look and throw me a bone! Thanks!
Kernel Data Inpage Error BSOD
in BSOD Help and Support

More and more lately, I have been getting Kernel Data Inpage Error BSODs. They mostly happen when I am using Photoshop or other high memory tasks. Attached is the SF_DD_MM_YYYY.zip crash report thing. Any help is appreciated.
BSOD Kernel Data Inpage Error
in BSOD Help and Support

I have been experience BSOD when I run a graphics heavy program for an extended time (4+ hrs), such as games or movies. The blue screen will state that there is a Kernel Data Inpage Error and shuts down my computer immediately. 1. OS Windows 7 Home Premium 64bit Service Pack 1 OEM ...
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 21:24.
Find Us