Please Please someone help! My PC is crashing at random times and is really starting to annoy me! Through the magic of Google I have been able to get my minidump file which looks like : Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\041012-48141-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330 Machine Name: Kernel base = 0xfffff800`03655000 PsLoadedModuleList = 0xfffff800`03899650 Debug session time: Tue Apr 10 17:45:41.335 2012 (UTC + 1:00) System Uptime: 0 days 6:17:50.209 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ...... Loading User Symbols Loading unloaded module list ................ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck F4, {3, fffffa800ffa1b30, fffffa800ffa1e10, fffff800039d45f0} Probably caused by : csrss.exe Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CRITICAL_OBJECT_TERMINATION (f4) A process or thread crucial to system operation has unexpectedly exited or been terminated. Several processes and threads are necessary for the operation of the system; when they are terminated (for any reason), the system can no longer function. Arguments: Arg1: 0000000000000003, Process Arg2: fffffa800ffa1b30, Terminating object Arg3: fffffa800ffa1e10, Process image file name Arg4: fffff800039d45f0, Explanatory message (ascii) Debugging Details: ------------------ PROCESS_OBJECT: fffffa800ffa1b30 IMAGE_NAME: csrss.exe DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: csrss FAULTING_MODULE: 0000000000000000 PROCESS_NAME: csrss.exe EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. BUGCHECK_STR: 0xF4_C0000005 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT CURRENT_IRQL: 0 STACK_TEXT: fffff880`0a319e38 fffff800`03a5b7b2 : 00000000`000000f4 00000000`00000003 fffffa80`0ffa1b30 fffffa80`0ffa1e10 : nt!KeBugCheckEx fffff880`0a319e40 fffff800`03a08c9b : ffffffff`ffffffff fffffa80`15c14060 fffffa80`0ffa1b30 fffffa80`0ffa1b30 : nt!PspCatchCriticalBreak+0x92 fffff880`0a319e80 fffff800`03988094 : ffffffff`ffffffff 00000000`00000001 fffffa80`0ffa1b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6 fffff880`0a319ed0 fffff800`036d0fd3 : fffffa80`0ffa1b30 fffff800`c0000005 fffffa80`15c14060 00000000`00ab08c0 : nt!NtTerminateProcess+0xf4 fffff880`0a319f50 fffff800`036cd570 : fffff800`0371caff fffff880`0a31aa38 fffff880`0a31a790 fffff880`0a31aae0 : nt!KiSystemServiceCopyEnd+0x13 fffff880`0a31a0e8 fffff800`0371caff : fffff880`0a31aa38 fffff880`0a31a790 fffff880`0a31aae0 00000000`00ab23d0 : nt!KiServiceLinkage fffff880`0a31a0f0 fffff800`036d13c2 : fffff880`0a31aa38 00000000`00010fff fffff880`0a31aae0 00000000`00ab1ea8 : nt! ?? ::FNODOBFM::`string'+0x48e24 fffff880`0a31a900 fffff800`036cff3a : 00000000`00000001 00000000`00ab0fd8 00000000`00aeb301 00000000`00010fff : nt!KiExceptionDispatch+0xc2 fffff880`0a31aae0 00000000`778f8e3d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a 00000000`00ab0fe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778f8e3d STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: X64_0xF4_C0000005_IMAGE_csrss.exe BUCKET_ID: X64_0xF4_C0000005_IMAGE_csrss.exe Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CRITICAL_OBJECT_TERMINATION (f4) A process or thread crucial to system operation has unexpectedly exited or been terminated. Several processes and threads are necessary for the operation of the system; when they are terminated (for any reason), the system can no longer function. Arguments: Arg1: 0000000000000003, Process Arg2: fffffa800ffa1b30, Terminating object Arg3: fffffa800ffa1e10, Process image file name Arg4: fffff800039d45f0, Explanatory message (ascii) Debugging Details: ------------------ PROCESS_OBJECT: fffffa800ffa1b30 IMAGE_NAME: csrss.exe DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: csrss FAULTING_MODULE: 0000000000000000 PROCESS_NAME: csrss.exe EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. BUGCHECK_STR: 0xF4_C0000005 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT CURRENT_IRQL: 0 STACK_TEXT: fffff880`0a319e38 fffff800`03a5b7b2 : 00000000`000000f4 00000000`00000003 fffffa80`0ffa1b30 fffffa80`0ffa1e10 : nt!KeBugCheckEx fffff880`0a319e40 fffff800`03a08c9b : ffffffff`ffffffff fffffa80`15c14060 fffffa80`0ffa1b30 fffffa80`0ffa1b30 : nt!PspCatchCriticalBreak+0x92 fffff880`0a319e80 fffff800`03988094 : ffffffff`ffffffff 00000000`00000001 fffffa80`0ffa1b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6 fffff880`0a319ed0 fffff800`036d0fd3 : fffffa80`0ffa1b30 fffff800`c0000005 fffffa80`15c14060 00000000`00ab08c0 : nt!NtTerminateProcess+0xf4 fffff880`0a319f50 fffff800`036cd570 : fffff800`0371caff fffff880`0a31aa38 fffff880`0a31a790 fffff880`0a31aae0 : nt!KiSystemServiceCopyEnd+0x13 fffff880`0a31a0e8 fffff800`0371caff : fffff880`0a31aa38 fffff880`0a31a790 fffff880`0a31aae0 00000000`00ab23d0 : nt!KiServiceLinkage fffff880`0a31a0f0 fffff800`036d13c2 : fffff880`0a31aa38 00000000`00010fff fffff880`0a31aae0 00000000`00ab1ea8 : nt! ?? ::FNODOBFM::`string'+0x48e24 fffff880`0a31a900 fffff800`036cff3a : 00000000`00000001 00000000`00ab0fd8 00000000`00aeb301 00000000`00010fff : nt!KiExceptionDispatch+0xc2 fffff880`0a31aae0 00000000`778f8e3d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a 00000000`00ab0fe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778f8e3d STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: X64_0xF4_C0000005_IMAGE_csrss.exe BUCKET_ID: X64_0xF4_C0000005_IMAGE_csrss.exe Followup: MachineOwner I cannot even think of where to begin with this information! Could anyone throw me some breadcrumbs to start looking in the right place? Pretty please, before I tear all my hair out!

Sorry I am running OS Name Microsoft Windows 7 Home Premium Version 6.1.7601 Service Pack 1 Build 7601 Other OS Description Not Available OS Manufacturer Microsoft Corporation System Name SLEEPY-PC System Manufacturer System manufacturer System Model System Product Name System Type x64-based PC Processor Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz, 3401 Mhz, 4 Core(s), 8 Logical Processor(s) BIOS Version/Date American Megatrends Inc. 0606, 24/06/2011 SMBIOS Version 2.6 Windows Directory C:\Windows System Directory C:\Windows\system32 Boot Device \Device\HarddiskVolume1 Locale United Kingdom Hardware Abstraction Layer Version = "6.1.7601.17514" User Name Sleepy-PC\Sleepy Time Zone GMT Daylight Time Installed Physical Memory (RAM) 16.0 GB Total Physical Memory 16.0 GB Available Physical Memory 651 MB Total Virtual Memory 31.9 GB Available Virtual Memory 15.0 GB Page File Space 16.0 GB Page File D:\pagefile.sys Alan

* * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck F4, {3, fffffa800ffa1b30, fffffa800ffa1e10, fffff800039d45f0} Probably caused by : csrss.exe http://support.microsoft.com/kb/555021 Try rebuilding your user profile like suggested in this artible and see if things get any better. Also try to see if you can capture what you do when the computer gets BSOD. For example are you using IE, Word, etc....

you can try to run "sfc /scannow" http://www.processlibrary.com/directory/files/csrss/26031/ Try scanning your computer for viruses as well, that could be another problem. (update windows updates and virus definitions)

I agree with the sfc /scannow, the c0000005 exception indicates user mode memory corruption an an error that caused csrss to exit. http://mikemstech.blogspot.com/2011/12/troubleshooting-0xf4.html -- Mike Burr Enterprise High Availability, Disaster Recovery, and Business Continuity Planning Learn to Troubleshoot Windows BSODs

Hello, Bug Check Code 0xF4: http://msdn.microsoft.com/en-us/library/windows/hardware/ff560372%28v=vs.85%29.aspx Like Brano mentioned, start by running sfc /scannow. If this does not help then proceed like that: Update all possible driversUninstall all unused programsRun chkdsk /r /fPerform a clean boot: http://support.microsoft.com/kb/929135Disable all used security softwaresRun memtest86+ and check if all is okay with your RAM. If an error was detected then replace the faulty RAM or contact your manufacturer Technical Support for assistance You can also contact Microsoft CSS for assistance. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations Microsoft Certified IT Professional: Enterprise Administrator Microsoft Certified IT Professional: Server Administrator Microsoft Certified Trainer

Crikes, such quick and helpful responses! I awoke this morning after leaving my PC on overnight to another BSOD. After restarting poor Windows started a disk check, and was deleting this, changing that and updating that. When it did finally boot everything was extremely slow.... I restarted and then my PC had obviously really fell out with me as it would just not boot. Various things went wrong, but with the help of Google I appear to have copied the boot manager from my windows 7 installation disc to my hard drive and everything started up beautifully. Just took me half a day to figure out..... The reason for this rant? Well during the trying to fix the above, I have performed the sfc /scannow, chkdsk /r /f and all manner of things I truly know little about. I have ran the memtest86+ and let the tests finish their course with no issues :-) I will leave the PC again overnight - normally encoding video, and see if the BSOD is there again and get my pen and paper out and write the issue(s) down. Really thankful for the help that has been given to such a new person at such speed! If I get a further BSOD I will go through the new profile as suggested. I am using Kaspersky Internet Security which I a quite strict at keeping updating and run every now and then and I aways accept Windows Updates when they pop up and regularly go to check for anything new. Cheers for the help and will keep up updated on my progress - I am presuming the constant BSOD caused the hard drive issues forcing all the fiddling today, but I am possibly hoping all the scans etc and corrected the BSOD issue too. But I always have been an optimistic! Just as well I had my little Iphone handy to keep trawling google for those new error messages! Many thanks to all. Alan

My 'root' hard drive is a SSD - would this make any difference?Alan

Crikes, such quick and helpful responses! I awoke this morning after leaving my PC on overnight to another BSOD. After restarting poor Windows started a disk check, and was deleting this, changing that and updating that. When it did finally boot everything was extremely slow.... I restarted and then my PC had obviously really fell out with me as it would just not boot. Various things went wrong, but with the help of Google I appear to have copied the boot manager from my windows 7 installation disc to my hard drive and everything started up beautifully. Just took me half a day to figure out..... The reason for this rant? Well during the trying to fix the above, I have performed the sfc /scannow, chkdsk /r /f and all manner of things I truly know little about. I have ran the memtest86+ and let the tests finish their course with no issues :-) I will leave the PC again overnight - normally encoding video, and see if the BSOD is there again and get my pen and paper out and write the issue(s) down. Really thankful for the help that has been given to such a new person at such speed! If I get a further BSOD I will go through the new profile as suggested. I am using Kaspersky Internet Security which I a quite strict at keeping updating and run every now and then and I aways accept Windows Updates when they pop up and regularly go to check for anything new. Cheers for the help and will keep up updated on my progress - I am presuming the constant BSOD caused the hard drive issues forcing all the fiddling today, but I am possibly hoping all the scans etc and corrected the BSOD issue too. But I always have been an optimistic! Just as well I had my little Iphone handy to keep trawling google for those new error messages! Many thanks to all. Alan Alan If it does BSOD can you upload the DMP's to skydrive or a file sharing service? We can do much more with them than without. Given the memory exception parameter I would run memtest for 6-8 passes and driver verifier. If you are overclocking anything reset to default before running these tests 1-Memtest -Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. "http://www.memtest.org/#downiso -Boot from the CD, and leave it running for at least 5 or 6 passes. -Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. -Test the sticks individually, and if you find a good one, test it in all slots. -Any errors are indicative of a memory problem. -If a known good stick fails in a motherboard slot it is probably the slot 2-Driver verifier -Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. -Other times it'll crash before you can log in to Windows. -If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier. -I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature) -In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu . -Then, here's the procedure:- Go to Start and type in "verifier" (without the quotes) and press Enter- -Select "Create custom settings (for code developers)" and click "Next"- Select "Select individual settings from a full list" and click "Next" - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next" - Select "Select driver names from a list" and click "Next"Then select all drivers NOT provided by Microsoft and click "Next" - Select "Finish" on the next page.Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. -The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part). -If you can't get into Windows because it crashes too soon, try it in Safe Mode. -If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created. -Further Reading"http://support.microsoft.com/kb/244617"]Using Driver Verifier to identify issues with Windows drivers for advanced users