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.


[HELP] Possible memory error, crash dump and event viewer logs included!

  • Please log in to reply
2 replies to this topic

#1 ShawtgunHobo


  • Members
  • 5 posts
  • Local time:03:02 PM

Posted 04 May 2015 - 03:50 AM

First off, I apologise if this is in the wrong thread, I'm not sure. I've used this site in the past, with great satisfaction, however I need help again. My computer decides to crash, with no error message in site (just a plain reboot) whenever I attempt to play some games, mainly me and my friends' Civilization V game, however this has occurred in other games such as Garry's Mod and Just Cause 2.

However, I am 100% convinced this is not a game issue, nor an overheating problem- I have monitored the temperatures with hardware monitor whilst I play these games, and they never exceed temperatures which would overheat my PC and cause a crash.

Before I provide more details, here are my specs:

Processor: AMD A10-6700 APU 
Graphics: GeForce GTX 660 
PSU: Corsair CX 500
OS: Windows 8.1

I have looked in the Event Viewer, and spotted something strange. Before the crash, four events happen (I once crashed three times in a night, and all of the events were the same in the same order.) These are the events:


In order of appearance: 


Volume C: (\Device\HarddiskVolume4) is healthy. No action is needed.

Source: Ntfs (Microsoft-Windows-Ntfs)
Event ID: 98
Level: Information
OpCode: Info
Logged: 02/05/2015 20:59:21


File System Filter 'npsvctrig' (6.3, ?2013?-?08?-?22T12:38:22.000000000Z) has successfully loaded and registered with Filter Manager.

Source: FilterManager
Event ID: 6
Level: Information
OpCode: Info
Logged: 02/05/2015 20:59:22


File System Filter 'eeCtrl' (6.1, ?2014?-?11?-?25T21:15:44.000000000Z) has successfully loaded and registered with Filter Manager.

Source: FilterManager
Event ID: 6
Level: Information
OpCode: Info
Logged: 02/05/2015 20:59:22


File System Filter 'BHDrvx64' (6.1, ?2015?-?04?-?04T05:27:40.000000000Z) has successfully loaded and registered with Filter Manager.

Source: FilterManager
Event ID: 6
Level: Information
OpCode: Info
Logged: 02/05/2015 20:59:22


The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Source: Kernel-Power
Event ID: 41
Level: Critical
OpCode: Info
Logged: 02/05/2015 20:59:22


I then look in the Memory dump files, and I see this: 

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

Debugging Details:

ERROR_CODE: (NTSTATUS) 0xc000003f - {Bad CRC} A cyclic redundancy check (CRC) checksum error occurred.

ADDITIONAL_DEBUG_TEXT: Memory Manager detected corruption of a pagefile page while performing an in-page operation.The data read from storage does not match the original datawritten.This indicates the data was corrupted by the storage stack, or device hardware.

BUGCHECK_STR: 0x7a_c000003f




ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER: from fffff80355776831 to fffff8035575dca0

ffffd001`a379b6f8 fffff803`55776831 : 00000000`0000007a fffff6e8`00111db8 ffffffff`c000003f 00000000`8934ebe0 : nt!KeBugCheckEx
ffffd001`a379b700 fffff803`556e4222 : ffffd001`a379b7f0 00000000`00000000 fffff803`55956ec0 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x8681
ffffd001`a379b7f0 fffff803`556e4187 : 00000000`00000000 ffffd001`a379b898 00000000`00000002 00000000`00000000 : nt!MiPfCompleteInPageSupport+0x3a
ffffd001`a379b830 fffff803`556381c2 : ffffd001`a379b9b0 ffffd001`a379b8f1 00000000`00000000 00000000`00000002 : nt!MiPfCompletePrefetchIos+0x6f
ffffd001`a379b860 fffff803`557af5e9 : 00000000`00000002 ffffd001`a379b9b0 fffffff6`00000000 00000000`00000001 : nt!MiPrefetchVirtualMemory+0x3fa
ffffd001`a379b950 fffff803`55742fc7 : ffffe000`dbafa958 00000000`00000080 ffffe000`dbd3d958 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x41439
ffffd001`a379bb20 fffff803`556e3514 : ffffe000`d68a3040 ffffe000`d68a3040 00001f80`0010000f ffffd001`a3770010 : nt!KeSwapProcessOrStack+0xb3
ffffd001`a379bb80 fffff803`557642c6 : ffffd001`a7917180 ffffe000`d68a3040 ffffd001`a79232c0 ffffd001`a377af20 : nt!PspSystemThreadStartup+0x58
ffffd001`a379bbe0 00000000`00000000 : ffffd001`a379c000 ffffd001`a3795000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


nt! ?? ::FNODOBFM::`string'+8681
fffff803`55776831 cc int 3


SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+8681



IMAGE_NAME: ntkrnlmp.exe



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

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


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

FAILURE_ID_HASH: {35f7dc2f-9d4e-79ab-5aab-b1994d114d0f}

Followup: MachineOwner

I've checked my disk with SeaTools and Windows Check Disk, both have said no issues found.

I am aware of the fact that filters like BHDrvx64 are from Norton, however if a solution could be found without removing it, it would be desirable, as I feel as this problem is more deeprouted.

I am convinced that this is what crashes my computer. This is all the information I can gather on the issue- as I said, there is no crash screen.

If anyone knows anything about this issue, please let me know. Thank you!

BC AdBot (Login to Remove)


#2 YeahBleeping


  • Members
  • 1,258 posts
  • Gender:Male
  • Local time:09:02 AM

Posted 04 May 2015 - 03:49 PM

ERROR_CODE: (NTSTATUS) 0xc000003f - {Bad CRC} A cyclic redundancy check (CRC) checksum error occurred


This error indicates that a file could not be read, either by a hardware failure or corruption.  Have you tried running SFC scannow from an elevated prompt?  From the error it is hard to tell if the file that is corrupt is a system file or some other file type.  But the other option would be to attempt a windows 8 installation repair.


You will need the windows 8 disk to run the scan option.


Neither of these two above options is destructive-  Meaning you will not lose anything on your hard drive.

#3 hamluis



  • Moderator
  • 56,383 posts
  • Gender:Male
  • Location:Killeen, TX
  • Local time:08:02 AM

Posted 05 May 2015 - 10:28 AM

I see that you have posted your issues on several forums.


IMO, this is not wise...since it may lead to conflicting suggestions/ideas that may not be in your best interests and merely lead to more confusion.



0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users