Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

KERNEL_DATA_INPAGE_ERROR BSODs occurring regularly [Windows 8.1]


  • Please log in to reply
No replies to this topic

#1 rickoslyder

rickoslyder

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:06:47 AM

Posted 03 January 2015 - 12:58 PM

So for the last few weeks, I've been having BSODs pretty oftenwith this error. Sometimes I can go days without it happening, but sometimes it can occurs 4-5 times in 24 hours. I've updated Windows Update, all my drivers are up to date, I've run sfc /scannow and chdsk -f, etc. etc. but everything seems to be fine. I downloaded both Avast and MalwareBytes the other day and now my dumps tell me that software conflicts with AvastSvc.exe (error code is 0 - STATUS_SUCCESS so it's the only conclusion I've been able to come to) are the cause but BSODs have been occurring since over a month before they've been installed so I sincerely doubt either of them are the cause.

 

My most recent dumps have been:

 

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

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


ERROR_CODE: (NTSTATUS) 0 - STATUS_SUCCESS

BUGCHECK_STR:  0x7a_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  AvastSvc.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

LAST_CONTROL_TRANSFER:  from fffff802355a0d0b to fffff8023555f1a0

STACK_TEXT:  
ffffd000`24133798 fffff802`355a0d0b : 00000000`0000007a 00000000`00000004 00000000`00000000 ffffe001`b2494110 : nt!KeBugCheckEx
ffffd000`241337a0 fffff802`3545d0ac : 00000000`00000002 ffffd000`24133908 ffffe001`b7ed9798 ffffd000`00000000 : nt! ?? ::FNODOBFM::`string'+0x3165b
ffffd000`24133890 fffff802`35474c44 : ffffe001`b7ed9798 ffffe001`b84e0080 ffffd000`24133b00 fffff680`000181b0 : nt!MiIssueHardFault+0x184
ffffd000`24133950 fffff802`3556942f : 00000000`10378840 00000000`000028d8 00000000`0b97fd01 ffffd000`24133b00 : nt!MmAccessFault+0x524
ffffd000`24133b00 00000000`771bd10d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x12f
00000000`0ba7f280 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x771bd10d


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+3165b
fffff802`355a0d0b cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+3165b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  53fe6f2e

IMAGE_VERSION:  6.3.9600.17328

BUCKET_ID_FUNC_OFFSET:  3165b

FAILURE_BUCKET_ID:  0x7a_0_nt!_??_::FNODOBFM::_string_

BUCKET_ID:  0x7a_0_nt!_??_::FNODOBFM::_string_

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x7a_0_nt!_??_::fnodobfm::_string_

FAILURE_ID_HASH:  {87ed9903-76d8-bd16-10fb-61b59edbe1ad}

Followup: MachineOwner

 

I'm really not sure what to do at this stage. Any help would be greatly appreciated. Thanks in advance!

 

Speccy snapshot:

http://speccy.piriform.com/results/bZsNiyiAVkkR8AFNp8iAmDm

 

The speccy again (just in case, in xml format) and Minidumps (zipped):

https://drive.google.com/open?id=0BxD1t_XNbqTldXNGVDRQaHBBNGc&authuser=0



BC AdBot (Login to Remove)

 


m



0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users