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

Toggle sidebar Toggle sidebar
S

ShotgunHobo

Reputable
May 2, 2015
2
0
4,510
Hello!
I'm having the strangest issue. 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
RAM: 6GB
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
User: SYSTEM
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
User: SYSTEM
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
User: SYSTEM
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
User: SYSTEM
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
User: SYSTEM
OpCode: Info
Logged: 02/05/2015 20:59:22


___________________________________________________________

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

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: 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 data written.This indicates the data was corrupted by the storage stack, or device hardware.

BUGCHECK_STR: 0x7a_c000003f

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

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

LAST_CONTROL_TRANSFER: from fffff80355776831 to fffff8035575dca0

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


STACK_COMMAND: kb

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

SYMBOL_STACK_INDEX: 1

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

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 53d0b7c3

BUCKET_ID_FUNC_OFFSET: 8681

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

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

ANALYSIS_SOURCE: KM

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!
 
Solution
J
note: seatools would not detect this problem because it is most likely a problem in the pagefile.sys or the actual location of where pagefile.sys is located on your drive.
-------
Error code: (NTSTATUS) 0xc000003f (3221225535) - {Bad CRC} A cyclic redundancy check (CRC) checksum error occurred.

basically a driver attempted to read data from storage and got a CRC error.

I would delete the pagefile.sys IE turn off virtual memory, unhide the pagefile.sys on your drive c: rename the file to pagefile.old, turn the virtual memory back on and reboot.

the fact that you got a memory dump means your storage driver and ports are most likely ok and that most likely your pagefile.sys is sitting on top of a bad sector.

if this is a SSD...
Sort by date Sort by votes
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
note: seatools would not detect this problem because it is most likely a problem in the pagefile.sys or the actual location of where pagefile.sys is located on your drive.
-------
Error code: (NTSTATUS) 0xc000003f (3221225535) - {Bad CRC} A cyclic redundancy check (CRC) checksum error occurred.

basically a driver attempted to read data from storage and got a CRC error.

I would delete the pagefile.sys IE turn off virtual memory, unhide the pagefile.sys on your drive c: rename the file to pagefile.old, turn the virtual memory back on and reboot.

the fact that you got a memory dump means your storage driver and ports are most likely ok and that most likely your pagefile.sys is sitting on top of a bad sector.

if this is a SSD, deletion of the pagefile.sys and running the trim commands or booting into BIOS and leave the drive idle or a hour should fix it. otherwise i would rename it and make another one. Windows 8.x can repair these problems but it takes time if the area is in use. IE, turn off your sleep functions in windows power management and leave your system running idle overnight and it might fix the problem.




 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom