Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Kernal Data Inpage Error

02 Feb 2011   #1
Kyle Denise

Windows 7 Pro 64-bit
 
 
Kernal Data Inpage Error

Please help me figure the kernal data inpage error BSOD. I cannot figure out where it's coming from. Seems to happen when I leave the computer for a period of time with Adobe InDesign and Internet Explorer running.
Win 7 Professional - 64-bit. OEM for system builders - I installed it when I built the computer 08/2011.

Any help you can provide is most appreciated.
Thanks,
Kyle Denise


My System SpecsSystem Spec
02 Feb 2011   #2
fimble

windows 7 ultimate
 
 

Hi Kyle Denise and Welcome.

STOP 0x0000007A: KERNEL_DATA_INPAGE_ERROR
Usual causes:
Memory, Paging file corruption, File system, Hard drive, Cabling, Virus infection, Improperly seated cards, BIOS, Bad motherboard, Missing Service Pack

Most of your dump files are giving the above stop error code.

As a Priority:

1. Download and install updates for your computer from Windows Update.
2. Scan your computer for computer viruses.
Run a full scan with your AV. Download, update and run a full scan with Malwarebytes' Free.
3. Check your hard disk for errors.
Run Chkdsk Open a command prompt. Type in Chkdsk /r /f You should get the response:
Code:
Chkdsk cannot run because the volume is in use by another process.
Would you like to schedule this volume
checked the next time the system restarts? (Y/N)
Answer Y. Check disk will run the next time you boot. Do this for all hard drives / partitions.
Then see Hard Drive Diagnostics for the correct HDD Diagnostics for your HDD's and run them.
3. Check your Memory.
Run Memtest86+
Run Memtest86+ overnight, after your computer has been off for about an hour . Let it run for at least 7 passes / 6-8 hours. If errors appear you can stop that particular test.
Note!! Any time Memtest86+ reports errors, it can be either bad RAM or a bad Mobo slot. Test RAM sticks individually. When you find a good one then test it in all slots. Post back with the results.
RAM - How to Test with Memtest86+
Guide to using Memtest86+

Bugcheck Analysis
Code:
Loading Dump File [D:\ DOWNLOADS\ DUMPS\Kyle Denise\020111-20857-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\XSymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0321b000 PsLoadedModuleList = 0xfffff800`03458e50
Debug session time: Wed Feb  2 02:30:12.554 2011 (UTC + 0:00)
System Uptime: 0 days 2:25:26.631
Loading Kernel Symbols
................................................Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000

Loading User Symbols
Missing image name, possible paged-out or corrupt data.
Loading unloaded module list
..Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {20, ffffffffc000009d, fffffa8006716078, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4c5e0 )

Followup: MachineOwner
---------

5: 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: 0000000000000020, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009d, error status (normally i/o status code)
Arg3: fffffa8006716078, current process (virtual address for lock type 3, or PTE)
Arg4: 0000000000000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c000009d

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  1

LAST_CONTROL_TRANSFER:  from fffff800032c33fc to fffff8000328b740

STACK_TEXT:  
fffff880`033d9828 fffff800`032c33fc : 00000000`0000007a 00000000`00000020 ffffffff`c000009d fffffa80`06716078 : nt!KeBugCheckEx
fffff880`033d9830 fffff800`03275637 : fffffa80`06716010 00000000`c000009d 00000000`00000000 fffffa80`067160a8 : nt! ?? ::FNODOBFM::`string'+0x4c5e0
fffff880`033d98f0 fffff800`032680c7 : fffffa80`06732b60 fffffa80`06732bb0 00000000`00000000 00000000`00000000 : nt!IopCompletePageWrite+0x57
fffff880`033d9920 fffff800`03292b9d : fffffa80`06732b60 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`033d99a0 fffff800`0328ed4b : 00000103`0935b801 00000000`00000000 fffff800`00000000 fffff880`033d9a50 : nt!KiCommitThreadWait+0x3dd
fffff880`033d9a30 fffff800`03225abf : fffffa80`00000002 fffff880`033d9d20 00000000`00000001 fffffa80`00000013 : nt!KeWaitForMultipleObjects+0x271
fffff880`033d9ce0 fffff800`0352fc06 : fffffa80`06732b60 cab70f44`20244c89 00000000`00000080 00000000`00000001 : nt!MiModifiedPageWriter+0xcf
fffff880`033d9d40 fffff800`03269c26 : fffff880`009b2180 fffffa80`06732b60 fffff880`009bd0c0 d1f748af`f266f98b : nt!PspSystemThreadStartup+0x5a
fffff880`033d9d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4c5e0
fffff800`032c33fc cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4c5e0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+4c5e0

BUCKET_ID:  X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+4c5e0

Followup: MachineOwner
Drivers:
Code:
fffff880`00f17000 fffff880`00f6e000   ACPI     ACPI.sys     Tue Jul 14 00:19:34 2009 (4A5BC106)
fffff880`01112000 fffff880`0111d000   amdxata  amdxata.sys  Tue May 19 18:56:59 2009 (4A12F2EB)
fffff880`00deb000 fffff880`00df4000   atapi    atapi.sys    Tue Jul 14 00:19:47 2009 (4A5BC113)
fffff880`010dd000 fffff880`01107000   ataport  ataport.SYS  Tue Jul 14 00:19:52 2009 (4A5BC118)
fffff880`00cc2000 fffff880`00d82000   CI       CI.dll       Tue Jul 14 02:32:13 2009 (4A5BE01D)
fffff880`01904000 fffff880`01934000   CLASSPNP CLASSPNP.SYS Tue Jul 14 00:19:58 2009 (4A5BC11E)
fffff880`00c64000 fffff880`00cc2000   CLFS     CLFS.SYS     Tue Jul 14 00:19:57 2009 (4A5BC11D)
fffff880`01000000 fffff880`01073000   cng      cng.sys      Tue Jul 14 00:49:40 2009 (4A5BC814)
fffff880`018ee000 fffff880`01904000   disk     disk.sys     Tue Jul 14 00:19:57 2009 (4A5BC11D)
fffff880`01169000 fffff880`0117d000   fileinfo fileinfo.sys Tue Jul 14 00:34:25 2009 (4A5BC481)
fffff880`0111d000 fffff880`01169000   fltmgr   fltmgr.sys   Tue Jul 14 00:19:59 2009 (4A5BC11F)
fffff880`0122b000 fffff880`01235000   Fs_Rec   Fs_Rec.sys   Tue Jul 14 00:19:45 2009 (4A5BC111)
fffff880`018b4000 fffff880`018ee000   fvevol   fvevol.sys   Sat Sep 26 03:34:26 2009 (4ABD7DB2)
fffff880`0148b000 fffff880`014d5000   fwpkclnt fwpkclnt.sys Tue Jul 14 00:21:08 2009 (4A5BC164)
fffff800`037f7000 fffff800`03840000   hal      hal.dll      Tue Jul 14 02:27:36 2009 (4A5BDF08)
fffff880`018ab000 fffff880`018b4000   hwpolicy hwpolicy.sys Tue Jul 14 00:19:22 2009 (4A5BC0FA)
fffff880`00d82000 fffff880`00da2000   jraid    jraid.sys    Wed Jan 27 08:58:17 2010 (4B600029)
fffff800`00b9b000 fffff800`00ba5000   kdcom    kdcom.dll    Tue Jul 14 02:31:07 2009 (4A5BDFDB)
fffff880`01200000 fffff880`0121a000   ksecdd   ksecdd.sys   Tue Jul 14 00:20:54 2009 (4A5BC156)
fffff880`01460000 fffff880`0148b000   ksecpkg  ksecpkg.sys  Fri Dec 11 06:03:32 2009 (4B21E0B4)
fffff880`00c0c000 fffff880`00c50000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Tue Jul 14 02:29:10 2009 (4A5BDF66)
fffff880`00dd1000 fffff880`00deb000   mountmgr mountmgr.sys Tue Jul 14 00:19:54 2009 (4A5BC11A)
fffff880`01107000 fffff880`01112000   msahci   msahci.sys   Tue Jul 14 01:01:01 2009 (4A5BCABD)
fffff880`00f77000 fffff880`00f81000   msisadrv msisadrv.sys Tue Jul 14 00:19:26 2009 (4A5BC0FE)
fffff880`0117d000 fffff880`011db000   msrpc    msrpc.sys    Tue Jul 14 00:21:32 2009 (4A5BC17C)
fffff880`01899000 fffff880`018ab000   mup      mup.sys      Tue Jul 14 00:23:45 2009 (4A5BC201)
fffff880`014f2000 fffff880`015e4000   ndis     ndis.sys     Tue Jul 14 00:21:40 2009 (4A5BC184)
fffff880`01400000 fffff880`01460000   NETIO    NETIO.SYS    Tue Jul 14 00:21:46 2009 (4A5BC18A)
fffff800`0321b000 fffff800`037f7000   nt       ntkrnlmp.exe Sat Jun 19 05:16:41 2010 (4C1C44A9)
fffff880`01244000 fffff880`013e7000   Ntfs     Ntfs.sys     Tue Jul 14 00:20:47 2009 (4A5BC14F)
fffff880`00fc1000 fffff880`00fd6000   partmgr  partmgr.sys  Tue Jul 14 00:19:58 2009 (4A5BC11E)
fffff880`00f81000 fffff880`00fb4000   pci      pci.sys      Tue Jul 14 00:19:51 2009 (4A5BC117)
fffff880`00e5c000 fffff880`00e63000   pciide   pciide.sys   Tue Jul 14 00:19:49 2009 (4A5BC115)
fffff880`00feb000 fffff880`00ffb000   PCIIDEX  PCIIDEX.SYS  Tue Jul 14 00:19:48 2009 (4A5BC114)
fffff880`0121a000 fffff880`0122b000   pcw      pcw.sys      Tue Jul 14 00:19:27 2009 (4A5BC0FF)
fffff880`00c50000 fffff880`00c64000   PSHED    PSHED.dll    Tue Jul 14 02:32:23 2009 (4A5BE027)
fffff880`0185f000 fffff880`01899000   rdyboost rdyboost.sys Tue Jul 14 00:34:34 2009 (4A5BC48A)
fffff880`00da2000 fffff880`00dd1000   SCSIPORT SCSIPORT.SYS Tue Jul 14 01:01:04 2009 (4A5BCAC0)
fffff880`014e5000 fffff880`014ed000   spldr    spldr.sys    Mon May 11 17:56:27 2009 (4A0858BB)
fffff880`01602000 fffff880`017ff000   tcpip    tcpip.sys    Mon Jun 14 04:39:04 2010 (4C15A458)
fffff880`00fb4000 fffff880`00fc1000   vdrvroot vdrvroot.sys Tue Jul 14 01:01:31 2009 (4A5BCADB)
fffff880`014d5000 fffff880`014e5000   vmstorfl vmstorfl.sys Tue Jul 14 00:42:54 2009 (4A5BC67E)
fffff880`00fd6000 fffff880`00feb000   volmgr   volmgr.sys   Tue Jul 14 00:19:57 2009 (4A5BC11D)
fffff880`00e00000 fffff880`00e5c000   volmgrx  volmgrx.sys  Tue Jul 14 00:20:33 2009 (4A5BC141)
fffff880`01073000 fffff880`010bf000   volsnap  volsnap.sys  Tue Jul 14 00:20:08 2009 (4A5BC128)
fffff880`00e64000 fffff880`00f08000   Wdf01000 Wdf01000.sys Tue Jul 14 00:22:07 2009 (4A5BC19F)
fffff880`00f08000 fffff880`00f17000   WDFLDR   WDFLDR.SYS   Tue Jul 14 00:19:54 2009 (4A5BC11A)
fffff880`00f6e000 fffff880`00f77000   WMILIB   WMILIB.SYS   Tue Jul 14 00:19:51 2009 (4A5BC117)
Missing image name, possible paged-out or corrupt data.

Unloaded modules:
e2e1e000`00000000 e2e1e000`e6e5e4e3   Unknown_Module_e2e1e000`00000000
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  E6E5E4E3
8a000000`00000000 8a000000`8e008c00   Unknown_Module_8a000000`00000000
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  8E008C00
Missing image name, possible paged-out or corrupt data.
5251504f`4e4d4c4b 5251504f`56555453   Unknown_Module_5251504f`4e4d4c4b
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  08080808
Missing image name, possible paged-out or corrupt data.
6a696867`66656463 6a696867`6e6d6c6b   Unknown_Module_6a696867`66656463
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  08080808
Missing image name, possible paged-out or corrupt data.
10101010`10101010 10101010`10101010   Unknown_Module_10101010`10101010
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00000000
Missing image name, possible paged-out or corrupt data.
20000000`00000000 20000000`00000000   Unknown_Module_20000000`00000000
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00000000
Let us know how it goes. If you get further problems with blue screens, attach your new dump files and details and we'll move on from there.
My System SpecsSystem Spec
14 Feb 2011   #3
Kyle Denise

Windows 7 Pro 64-bit
 
 
Hopefully, issue resolved

All of the items on your list I'd already done, but went through a second time to be sure I'd not missed something.
I was also working on an unrelated issue with win 7 power management and went into device manager for my Realteck network adapter and unchecked "allow computer to turn off this device". Bam, BSOD, critical object termination error. After searching for clues on other's experiences with this error it lead me to the MS hotfix 30615. I have a 1tb HD, so I installed the hotfix and I've not had any BSOD for 8 days.
Hopefully, all is solved. Now my other issue with win 7 power management is resolved also.
Thanks for the help, I learn a lot ready this forum.
Cheers,
Kyle Denise
My System SpecsSystem Spec
Reply

 Kernal Data Inpage Error




Thread Tools



Similar help and support threads for2: Kernal Data Inpage Error
Thread Forum
BSOD Kernal Data Inpage Error BSOD Help and Support
Bsod - inpage kernal error - ntfs.sys BSOD Help and Support
BSOD 000F4 and 0004C Kernal Data Inpage Error BSOD Help and Support
Kernel Data Inpage Error BSOD Help and Support
BSOD - Kernal Data Inpage Error BSOD Help and Support
Kernel data inpage error BSOD Help and Support
Kernal data inpage error BSOD Help and Support

Our Sites

Site Links

About Us

Find 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 10:47 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App