Loading...

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

CRITICAL_OBJECT_TERMINATION On Wed 15/12/2010 00:08:01 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini121510-01.dmp This was probably caused by the following module: mfehidk.sys (mfehidk+0x2DF8C) Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF8E7C6D90, 0xFFFFFFFF8E7C6EDC, 0xFFFFFFFF8245E710) Error: If you areover-clockinganythingreset to default before running these tests. It is suggested you look for an update for the following driver: mfehidk.sys (McAfee Link Driver, McAfee, Inc.). This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. Homepage

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. A third party driver was identified as the probable root cause of this system error. If the problem is getting worse I recommend you to back up all your data and install OS using Toshiba recovery DVD. Log In Return to Forum quote blizzardlogo netEaselogo Thanks for visiting the Blizzard Forums (2.15.1) · Patch Notes Support Feedback Americas - English (US) Region Americas Europe Asia China Language English https://social.technet.microsoft.com/Forums/windows/en-US/3b2b1742-14e6-4c9e-8067-4e17dea1004a/blue-screen-error-criticalobjecttermination-and-kerneldatainpageerror?forum=w7itprohardware

Thank you all for your help! (: Back to top Page 1 of 2 1 2 Next Back to Windows 7 2 user(s) are reading this topic 0 members, 2 guests, This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. My WebsiteMy help doesn't cost a penny, but if you'd like to consider a donation, click Back to top #4 embeeezy embeeezy Topic Starter Members 4 posts OFFLINE Gender:Female Brief Info: blue screen KERNEL_DATA_INPAGE_ERROR and CRITICAL_OBJECT_TERMINATION AD.

Computer Name : ... KERNEL_DATA_INPAGE_ERRORcrash dump file: C:\Windows\Minidump\Mini121510-02.dmpThis was probably caused by the following module: mfehidk.sys (mfehidk+0x2DF8C) Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF87826020, 0xFFFFFFFF8782616C, 0xFFFFFFFF82472710)Error: CRITICAL_OBJECT_TERMINATIONfile path: C:\Windows\system32\drivers\mfehidk.sysproduct: SYSCOREcompany: McAfee, Inc.description: McAfee Link DriverBug check description: It is suggested you look for an update for the following driver: mfehidk.sys (McAfee Link Driver, McAfee, Inc.). Your system configuration may be incorrect.

Find More...>> [Solved] Computer BSOD/freezes - Blue Screen - Windows 7 ... 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 Good luck and be patient. BSOD Help and Support 0xf4 BSOD Critical_Object_TerminationAfter a clean install of Windows 7 x64 on my new Crucial M4 SSD, I am getting random f4 bsod's.

It can take days or even weeks to be declared clean after the first AII post is made. thanks for replying..I did a crash test report and got this, maybe it will give better info : Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. Drivers should always be updated anyway. If i don"t game it does not happen.

Google query: mfehidk.sys McAfee, Inc. http://www.0x000000f4.com/critical-object-termination-error-on-msi-u2-laptop.html It is suggested you look for an update for the following driver: mfehidk.sys (McAfee Link Driver, McAfee, Inc.). Post version of Security centre and build no. Please make sure that you read the information about getting started before you start your thread.It would be helpful if you post a note here once you have completed the steps

Full vid: https://t.co/dwmY2Bw2O5 https://t.co/dcXLEsFsO9 3 hours ago @battlefield Take in Battlefield 1 They Shall Not Pass with your friendly, neighborhood Stream Team member. Bonuses Google query: mfehidk.sys McAfee, Inc. I will be sure to monitor things a bit more closely though. 4. Updating drivers is always the first step in any troubleshooting regarding blue screens.

coastal 27 Dec 2010 23:26:21 5,418 posts Seen 2 days ago Registered 11 years ago Could easily be dust. Back to top BC AdBot (Login to Remove) BleepingComputer.com Register to remove ads #2 cryptodan cryptodan Bleepin Madman Members 21,868 posts OFFLINE Gender:Male Location:Catonsville, Md Local time:01:29 AM Posted This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. http://sortpictures.net/blue-screen/new-ram-blue-screen-error.html This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

description: McAfee Link Driver Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. Hayton Dec 24, 2010 9:35 AM (in response to samj) Sorry, samj, for the delay in spotting this. Update drivers to alleviate software issues then go from there.

It is suggested you look for an update for the following driver: mfehidk.sys (McAfee Link Driver, McAfee, Inc.).

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: The crash took place in a standard Microsoft module. Your system configuration may be incorrect. and a BSOD in ntoskernel is a generic kernel panic.

Even if it has been removed.3. Google query: mfehidk.sys McAfee, Inc. Whatever he'll decide, it's fine with me.Bed time for me anyway.Good Night My WebsiteMy help doesn't cost a penny, but if you'd like to consider a donation, click Back to find this Best Regards, Frederik.

Possibly this problem is caused by another driver on your system which cannot be identified at this time. Expand...>> Topic Starter: Mickey Started On: 11.13.10 Problem: CRITICAL_OBJECT_TERMINATION (0xF4) - Experts Exchange Laptops having the same problem: Sony Vaio VPC-EA Series VPCEA1S1RL Case Summary: ... That's my 2 cents. Site Changelog Community Forum Software by IP.Board Sign In Use Facebook Use Twitter Need an account?

Computer was built in April: CPU: I7-2700K (Running @ stock), After-market cooler Motherboard: ASROCK|Z68 EXTREME3 GEN3 1155 R RAM: CORSAIR CMZ8GX3M2A1600C9 4GBx2 Video: EVGA GeForce GTX 560 Ti FPB 1024 MB 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: 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

If Atheros that could be the issue. EDIT: Adding zip file per instructions. Re: mcafee causing bsod,help please? Privacy statement  © 2017 Microsoft.

Google query: mfehidk.sys McAfee, Inc. Salaman 28 Dec 2010 11:42:08 22,317 posts Seen 3 hours ago Registered 13 years ago I was going to say, wouldn't uninstalling McAfee sort the underlying problem? CRITICAL_OBJECT_TERMINATION error on MSI U2 laptop CRITICAL_OBJECT_TERMINATION is a critical error message that appears when Windows is forced to terminate abnormally due to a kernel problem to prevent further damage to On Mon 13/12/2010 14:44:58 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini121310-01.dmp This was probably caused by the following module: ntfs.sys (Ntfs+0xD09ED) Bugcheck code: 0x7A (0xFFFFFFFFC04418B0, 0xFFFFFFFFC000009D, 0x79DF860, 0xFFFFFFFF883169ED) Error: KERNEL_DATA_INPAGE_ERROR

Graphics driver is up to date. 2. STOP error 0x000000f4 on EMACHINES M-Series computer. ... A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: iastor.sys (Intel Rapid Storage Technology driver - x86, Intel Corporation).