Home > Blue Screen > Blue Screen Error CRITICAL_OBJECT_TERMINATION And KERNEL_DATA_INPAGE_ERROR

Blue Screen Error CRITICAL_OBJECT_TERMINATION And KERNEL_DATA_INPAGE_ERROR

Click here to Register a free account now! Bug Check Code : ... It is suggested you look for an update for the following driver: mfehidk.sys (McAfee Link Driver, McAfee, Inc.). The crash took place in a standard Microsoft module. http://flvtomp4mac.com/blue-screen/blue-screen-kernal-stack-inpage-error.php

You would hate to send the original poster chasing their tail for non-existent malware, only to realize it was just simply an out-of-date/incorrect driver. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. CRITICAL_OBJECT_TERMINATION. All drivers updated, internal components reseated, memtest run, chkdsk, driver verifier, video card test, everything has been fine. https://social.technet.microsoft.com/Forums/windows/en-US/3b2b1742-14e6-4c9e-8067-4e17dea1004a/blue-screen-error-criticalobjecttermination-and-kerneldatainpageerror?forum=w7itprohardware

It is suggested you look for an update for the following driver: iastor.sys (Intel Rapid Storage Technology driver - x86, Intel Corporation). Here is the report from the dumpfile's: -------------------------------------------------------------------------------- System Information (local) -------------------------------------------------------------------------------- computer name: BUREAU-VAST windows version: Windows 7 , 6.1, build: 7600 windows dir: C:\Windows CPU: GenuineIntel Intel(R) Core(TM) i7 Google query: iastor.sys Intel Corporation CUSTOM_ERROR On Fri 10/12/2010 17:22:18 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini121010-01.dmp This was probably caused by the following module: pci.sys (pci+0x16624) Bugcheck code: 0x7A Poll No poll found Latest Battlelog News Battlefield 4 CTE Sunset 2 weeks ago 483 Comments Catch A Free Trial Of Battlefield 1 This Weekend 2 weeks ago 72 Comments Welcome

Most BSOD occurs while playing Diablo 3. CRITICAL_OBJECT_TERMINATION On Fri 17/12/2010 14:04:49 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini121710-02.dmp This was probably caused by the following module: mfehidk.sys (mfehidk+0x38D40) Bugcheck code: 0x7A (0xFFFFFFFFC040E968, 0xFFFFFFFFC000009D, 0x7424B8C0, 0xFFFFFFFF81D2D000) Error: Find More...>> [Solved] Computer BSOD/freezes - Blue Screen - Windows 7 ... These crashes were related to memory corruption (probably caused by a driver).

Driver download goes there for your 560 TI. CRITICAL_OBJECT_TERMINATION On Tue 14/12/2010 10:21:01 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini121410-01.dmp This was probably caused by the following module: mfehidk.sys (mfehidk+0x2DF8C) Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF87984BB0, 0xFFFFFFFF87984CFC, 0xFFFFFFFF82439710) Error: A third party driver was identified as the probable root cause of this system error. description: McAfee Link Driver Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.

STOP error 0x000000f4 on EMACHINES M-Series computer. ... This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. CRITICAL_OBJECT_TERMINATION On Tue 14/12/2010 10:21:01 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini121410-01.dmp This was probably caused by the following module: mfehidk.sys (mfehidk+0x2DF8C) Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF87984BB0, 0xFFFFFFFF87984CFC, 0xFFFFFFFF82439710) Error: Global error EMACHINES W Series Blue ...

Like Show 0 Likes(0) Actions 5. It is suggested you look for an update for the following driver: mfehidk.sys (McAfee Link Driver, McAfee, Inc.). The crash took place in the Windows kernel. Hesitating about issue weeding can become deadly for your operating system.

As far as I know it has been fine for months up until the past 2-3 weeks. http://flvtomp4mac.com/blue-screen/blue-screen-error-bccode-a-please-help.php Skip navigationHomeForumsGroupsContentCommunity SupportLog inRegister0SearchSearchCancelError: You don't have JavaScript enabled. This is the only tool I know which is widely used even by PC technicians to remove Windows errors in automatic mode. Google query: mfehidk.sys McAfee, Inc.

description: McAfee Link Driver Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. Re: mcafee causing bsod,help please? The crash took place in the Windows kernel. this content It is suggested you look for an update for the following driver: mfehidk.sys (McAfee Link Driver, McAfee, Inc.).

If the problem is getting worse I recommend you to back up all your data and install OS using Toshiba recovery DVD. By calling forth CRITICAL OBJECT TERMINATION error on MSI U2 laptop the computer gives you a caution so as to exclude the following corruption of the system. My System Specs System Manufacturer/Model Number Brewed OS Microsoft Windows 7 Ultimate: x64 (SP1) CPU Intel® Core™ i5-2500K Processor Motherboard ASUS P8Z68-V PRO Memory Kingston DDR3 HyperX 1600MHz 8GB Graphics Card

After the first BSOD on a particular day, it tends to happen again.

Please turn JavaScript back on and reload this page. granted that a problem of that type set in after some new driver activation renew or deactivate them in Safe Mode. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. Check your Windows Update installation history in your “Add or remove Programs” in your Control Panel.

Google query: mfehidk.sys McAfee, Inc. skuzzbag 27 Dec 2010 23:30:10 5,950 posts Seen 4 months ago Registered 13 years ago A bad driver can cause BSOD. CRITICAL_OBJECT ... 3 year old Dell Inspiron 9400 notebook computer with a new and ... have a peek at these guys The crash took place in a standard Microsoft module.

It is a reoccurring problem and only seems to happen when no one is using the computer. description: McAfee Link Driver Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. Any exaplanation... but its a CRITICAL_OBJECT_TERMINATION ntoskrnl.exe+7efc0 error. ...

On Tue 7/31/2012 6:07:55 AM GMT your computer crashedcrash dump file: C:\Windows\Minidump\073112-18156-01.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0x7A (0x20, 0xFFFFFFFFC000009D, 0xFFFFFA8005A8C7C8, 0x0)Error: KERNEL_DATA_INPAGE_ERRORfile path: C:\Windows\system32\ntoskrnl.exeproduct: Possibly this problem is caused by another driver on your system which cannot be identified at this time. If the problem is getting worse I recommend you to back up all your data and install OS using Toshiba recovery DVD. The quickest and easiest thing to do is just update all available drivers.

A third party driver was identified as the probable root cause of this system error. Google query: mfehidk.sys McAfee, Inc. If the problem is not solved, THEN go digging for malware. samj 27 Dec 2010 22:57:23 3 posts Seen 6 years ago Registered 6 years ago Please Help SG 27 Dec 2010 23:05:30 1,896 posts Seen 3 years ago Registered 8 years

The crash took place in a standard Microsoft module. The crash took place in the Windows kernel. description: McAfee Link 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. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

Bluescreen while gaming --Stijn--BEL-- Enlisted: 2011-10-28 2012-02-02 21:15 HI, Afther some time of gaming, various from 15min to 2 hours, my game is freezing and i get a blue screen and Google query: mfehidk.sys McAfee, Inc. Your system configuration may be incorrect. I will be sure to monitor things a bit more closely though. 4.

CRITICAL_OBJECT_TERMINATION On Sun 12/12/2010 13:22:31 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini121210-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0xCDB8D) Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF8DE9ED90, 0xFFFFFFFF8DE9EEDC, 0xFFFFFFFF82434710) Error: