Not certain what is going on. I have seen F4 related to HDD/RAM. Have replaced both, Also replaced the SATA Cable...So now i turn to some higher GURU's...
Last edited by MRComputer; 25 Apr 2014 at 14:02. Reason: fat finger typing
You are getting 0xF4 (or Critical Object Termination) bugchecks which indicate a process necessary for the operating system to run has been terminated.
More precisely the csrss.exe has been terminated which is the Win32 subsystem that handles the win32 console.
Now there isn't much information in the dump file so first of all lets rule out hardware.
We should run some tests.
Stress test your CPU by running Prime95 for around 2 hours.
Follow these instructions.
Hardware - Stress Test With Prime95
Stress test your GPU by running Furmark for around 30 minutest.
Follow these instructions.
Video Card - Stress Test with Furmark
Test your RAM by running Memtest86 for at least 8 passes.
Follow these instructions.
RAM - Test with Memtest86+
Finally stress test your HDD by running SeaTools.
Follow these instructions.
SeaTools for DOS and Windows - How to Use
Additionally run a disk check by following these instructions.
Disk Check
Then run a system file checker by following these instructions
SFC /SCANNOW Command - System File Checker
If it finds errors the first time then reboot and run it again an additional two more times.
Post back the results.
Ran all tests, No errors found. I might add, The system has a Brand new HDD, RAM, and Video. Ran All tests you suggested, all passed/no errors
Enable Driver Verifier to monitor the drivers.
Driver Verifier -Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Information
Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.
How Can we know that DV is enabled:
It will make the system bit of slow, laggy.
Warning
Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.
If there is no points, make a System Restore Point Manually before enabling DV.
Tip
- If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
- If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.
Let us know the results, with the subsequent crash dumps, if any.
New BSoD...The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007a (0xfffff6fcc02884d0, 0xffffffffc000000e, 0x000000005f4b38c0, 0xfffff9805109afb8). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 042914-23899-01.
Crash List
Created by using BlueScreenView
Dump File Crash Time Bug Check String Bug Check Code Parameter 1 Parameter 2 Parameter 3 Parameter 4 Caused By Driver Caused By Address File Description Product Name Company File Version Processor Crash Address Stack Address 1 Stack Address 2 Stack Address 3 Computer Name Full Path Processors Count Major Version Minor Version Dump File Size Dump File Time 042914-23899-01.dmp4/29/2014 1:46:02 AMKERNEL_DATA_INPAGE_ERROR0x0000007afffff6fc`c02884d0ffffffff`c000000e00000000`5f4b38c0fffff980`5109 afb8ntoskrnl.exentoskrnl.exe+75bc0NT Kernel & SystemMicrosoft® Windows® Operating SystemMicrosoft Corporation6.1.7601.18247 (win7sp1_gdr.130828-1532)x64ntoskrnl.exe+75bc0 C:\Windows\Minidump\042914-23899-01.dmp2157601299,2164/29/2014 1:47:42 AM 042814-26067-01.dmp4/28/2014 4:01:39 PMCRITICAL_OBJECT_TERMINATION0x000000f400000000`00000003fffffa80`07442060fffffa80`07442340fffff800`0 337f7b0ntoskrnl.exentoskrnl.exe+75bc0NT Kernel & SystemMicrosoft® Windows® Operating SystemMicrosoft Corporation6.1.7601.18247 (win7sp1_gdr.130828-1532)x64ntoskrnl.exe+75bc0 C:\Windows\Minidump\042814-26067-01.dmp2157601262,1444/28/2014 4:02:59 PM 042814-23212-01.dmp4/28/2014 3:53:24 PMPROCESS1_INITIALIZATION_FAILED0x0000006b00000000`0000000000000000`0000000000000000`000000000000000 0`00000000ntoskrnl.exentoskrnl.exe+75b90NT Kernel & SystemMicrosoft® Windows® Operating SystemMicrosoft Corporation6.1.7601.18247 (win7sp1_gdr.130828-1532)x64ntoskrnl.exe+75b90 C:\Windows\Minidump\042814-23212-01.dmp2157601266,5764/28/2014 4:00:43 PM 042514-21840-01.dmp4/25/2014 12:03:52 PMCRITICAL_OBJECT_TERMINATION0x000000f400000000`00000003fffffa80`05d271c0fffffa80`05d274a0fffff800`0 33c57b0ntoskrnl.exentoskrnl.exe+75bc0NT Kernel & SystemMicrosoft® Windows® Operating SystemMicrosoft Corporation6.1.7601.18247 (win7sp1_gdr.130828-1532)x64ntoskrnl.exe+75bc0 C:\Windows\Minidump\042514-21840-01.dmp2157601291,5524/25/2014 2:41:37 PM 042514-36129-01.dmp4/25/2014 10:15:14 AMCRITICAL_OBJECT_TERMINATION0x000000f400000000`00000003fffffa80`066132e0fffffa80`066135c0fffff800`0 33cf7b0ntoskrnl.exentoskrnl.exe+75bc0NT Kernel & SystemMicrosoft® Windows® Operating SystemMicrosoft Corporation6.1.7601.18247 (win7sp1_gdr.130828-1532)x64ntoskrnl.exe+75bc0 C:\Windows\Minidump\042514-36129-01.dmp2157601291,5524/25/2014 11:26:22 AM 042514-51386-01.dmp4/25/2014 8:29:48 AMCRITICAL_OBJECT_TERMINATION0x000000f400000000`00000003fffffa80`0665c060fffffa80`0665c340fffff800`0 338d7b0ntoskrnl.exentoskrnl.exe+75bc0NT Kernel & SystemMicrosoft® Windows® Operating SystemMicrosoft Corporation6.1.7601.18247 (win7sp1_gdr.130828-1532)x64ntoskrnl.exe+75bc0 C:\Windows\Minidump\042514-51386-01.dmp2157601291,5284/25/2014 8:32:01 AM 042514-56160-01.dmp4/25/2014 8:18:01 AMCRITICAL_OBJECT_TERMINATION0x000000f400000000`00000003fffffa80`066e0b30fffffa80`066e0e10fffff800`0 33857b0ntoskrnl.exentoskrnl.exe+75bc0NT Kernel & SystemMicrosoft® Windows® Operating SystemMicrosoft Corporation6.1.7601.18247 (win7sp1_gdr.130828-1532)x64ntoskrnl.exe+75bc0 C:\Windows\Minidump\042514-56160-01.dmp2157601282,3844/25/2014 8:20:16 AM 042414-25833-01.dmp4/24/2014 2:13:03 PMBAD_SYSTEM_CONFIG_INFO0x0000007400000000`00000002fffff880`02e14ae000000000`00000001ffffffff`c00000 3aACPI.sysACPI.sys+b7a7ACPI Driver for NTMicrosoft® Windows® Operating SystemMicrosoft Corporation6.1.7600.16385 (win7_rtm.090713-1255)x64ntoskrnl.exe+75c00 C:\Windows\Minidump\042414-25833-01.dmp2157601291,3924/24/2014 2:25:39 PM 042214-19063-01.dmp4/22/2014 12:01:55 PMCRITICAL_OBJECT_TERMINATION0x000000f400000000`00000003fffffa80`044a8b30fffffa80`044a8e10fffff800`0 2bc7260ntoskrnl.exentoskrnl.exe+6f880NT Kernel & SystemMicrosoft® Windows® Operating SystemMicrosoft Corporation6.1.7601.18247 (win7sp1_gdr.130828-1532)x64ntoskrnl.exe+6f880 C:\Windows\Minidump\042214-19063-01.dmp2157600277,0724/22/2014 12:08:50 PM 042214-23010-01.dmp4/22/2014 9:19:07 AMCRITICAL_OBJECT_TERMINATION0x000000f400000000`00000003fffffa80`03454b30fffffa80`03454e10fffff800`0 2bde260ntoskrnl.exentoskrnl.exe+6f880NT Kernel & SystemMicrosoft® Windows® Operating SystemMicrosoft Corporation6.1.7601.18247 (win7sp1_gdr.130828-1532)x64ntoskrnl.exe+6f880 C:\Windows\Minidump\042214-23010-01.dmp2157600277,0724/22/2014 11:27:29 AM 042214-29374-01.dmp4/22/2014 3:04:31 AMCRITICAL_OBJECT_TERMINATION0x000000f400000000`00000003fffffa80`04eeb060fffffa80`04eeb340fffff800`0 2b91260ntoskrnl.exentoskrnl.exe+6f880NT Kernel & SystemMicrosoft® Windows® Operating SystemMicrosoft Corporation6.1.7601.18247 (win7sp1_gdr.130828-1532)x64ntoskrnl.exe+6f880 C:\Windows\Minidump\042214-29374-01.dmp2157600277,0084/22/2014 3:05:55 AM 042214-15990-01.dmp4/22/2014 2:51:50 AMSYSTEM_THREAD_EXCEPTION_NOT_HANDLED0x1000007effffffff`c000001dfffff880`00dc993cfffff880`02fdc538ff fff880`02fdbd90ataport.SYSataport.SYS+1c4ceATAPI Driver ExtensionMicrosoft® Windows® Operating SystemMicrosoft Corporation6.1.7600.16385 (win7_rtm.090713-1255)x64ataport.SYS+1e93c C:\Windows\Minidump\042214-15990-01.dmp2157600317,5764/22/2014 2:52:45 AM 042214-14757-01.dmp4/22/2014 1:42:02 AMCRITICAL_OBJECT_TERMINATION0x000000f400000000`00000003fffffa80`04476060fffffa80`04476340fffff800`0 2bda240Ntfs.sysNtfs.sys+e54aNT File System DriverMicrosoft® Windows® Operating SystemMicrosoft Corporation6.1.7600.16385 (win7_rtm.090713-1255)x64ntoskrnl.exe+71f00 C:\Windows\Minidump\042214-14757-01.dmp2157600277,0004/22/2014 1:43:11 AM 042214-48719-01.dmp4/21/2014 9:05:14 PMCRITICAL_OBJECT_TERMINATION0x000000f400000000`00000003fffffa80`05874060fffffa80`05874340fffff800`0 2dce7b0ntoskrnl.exentoskrnl.exe+75bc0NT Kernel & SystemMicrosoft® Windows® Operating SystemMicrosoft Corporation6.1.7601.18247 (win7sp1_gdr.130828-1532)x64ntoskrnl.exe+75bc0 C:\Windows\Minidump\042214-48719-01.dmp2157601277,3604/22/2014 12:57:15 AM
That's not helpful, if you are going to post something like that then please use the CODE tags option it's marked with a #
Please upload the minidumps.
If it is a Kernel Memory Dump that is stored under
C:/Windows/memory.dmp then you'll need to upload it to a file sharing site.
One Drive is good.
Then post the link.
Heres the last 2 dmp files. Sorry about previous post.
Can you run SeaTools Long Generic Test.
There's something still not right with the dump files,
you are still getting memory corruption.
I think we might need to enable special pool for this one.
When setting up Driver Verifier choose these options instead.
Code:WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view entire output. 3794 errors : !ataport (fffff88000dc9000-fffff88000dc9fff)Code:************ NO PAGING FILE ********************* fffff80002b087d0: Unable to get paged pool info GetUlongPtrFromAddress: unable to read from fffff80002b08408 GetUlongPtrFromAddress: unable to read from fffff80002b08280 GetUlongPtrFromAddress: unable to read from fffff80002a9df18 GetUlongPtrFromAddress: unable to read from fffff80002a864b8 GetUlongPtrFromAddress: unable to read from fffff80002a715e8 GetUlongPtrFromAddress: unable to read from fffff80002a86490 GetUlongPtrFromAddress: unable to read from fffff80002a86500 GetUlongPtrFromAddress: unable to read from fffff80002b0a1c0 GetUlongPtrFromAddress: unable to read from fffff80002a47418 GetUlongPtrFromAddress: unable to read from fffff80002a5cdc0 GetUlongPtrFromAddress: unable to read from fffff80002a5cc00 unable to get nt!MmTotalFreeSystemPtes GetUlongPtrFromAddress: unable to read from fffff80002a71608 GetUlongFromAddress: unable to read from fffff80002a879f0 Available Pages: 0 ( 0 Kb) ResAvail Pages: 0 ( 0 Kb)
Quote