Random BSOD critcal object termination and kernel data inpage error

Hello,

Every times randomly, i have a BSOD critical_object_termination same with new installation of windows.
I solved problem with a downgrade and new update Nvidia drivers but today my problem of BSOD restart.

I uploaded the SF diagnostic tool file but Whocrashed said :
On Tue 09/09/2014 18:44:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090914-5522-01.dmp
This was probably caused by the following module: volmgrx.sys (volmgrx+0x1000)
Bugcheck code: 0x7A (0xFFFFF6FC400082F8, 0xFFFFFFFFC00000C0, 0x1B6201860, 0xFFFFF8800105F000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\volmgrx.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote d’extension du gestionnaire de volumes
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 09/09/2014 18:44:09 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: volmgr.sys (volmgr+0xECB9)
Bugcheck code: 0x7A (0xFFFFF6FC400082F8, 0xFFFFFFFFC00000C0, 0x1B6201860, 0xFFFFF8800105F000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\volmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Volume Manager Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

If it helps to solve the problem.

Neyoh

up

up

up !

up !

Sorry about the long response, you seem to have slipped through the cracks,

I'm not seeing any obvious drivers being flagged but there does seem to be a hint of corruption or disk failure,

Let's start with these,

Please perform the following tests,

chkdsk /r

SeaTools for DOS and Windows

SFC /SCANNOW Command - System File Checker

Testing your RAM would be a good idea as well,

Code:

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffff6fc400082f8, ffffffffc00000c0, 1b6201860, fffff8800105f000}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
GetPointerFromAddress: unable to read from fffff80003113278
Probably caused by : memory_corruption

Followup: memory_corruption

   Information

MemTest86+

Run a minimum of 8 passes, preferably overnight, or until errors occur using MemTest86+.

Use this tutorial to help you use MemTest86+:
RAM - Test with MemTest86+