Hi, I'm running Windows 7 Ultimate (64 bit) on my laptop, and, recently, I noticed that after the machine has been idle for awhile (and displaying screensaver), and then I start using it again, I get a BSOD 0x000000F4. Here's the latest minidump: Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\060610-58999-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 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02c13000 PsLoadedModuleList = 0xfffff800`02e50e50 Debug session time: Sun Jun 6 08:19:52.983 2010 (UTC - 4:00) System Uptime: 0 days 9:56:16.028 Loading Kernel Symbols ............................................................... ................................................................ .......................................................... Loading User Symbols Loading unloaded module list ........ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck F4, {3, fffffa800580db30, fffffa800580de10, fffff80002f8d240} Probably caused by : csrss.exe Followup: MachineOwner --------- Does anyone have any idea what this might be? I use AVG for antivirus, and I also ran the latest Malwarebytes, and neither found any problems. Thanks, Jim

You get the following BSOD: Bug Check 0xF4: CRITICAL_OBJECT_TERMINATION The CRITICAL_OBJECT_TERMINATION bug check has a value of 0x000000F4. This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. Please upload the dmp file to your SkyDrive! "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

Hi Andre, I'm not sure what you are suggesting? Are you saying to upload the .dmp file to Windows Live Skydrive in the Public folder? Jim

Hi Jim, yes upload the dmp to your public SkyDrive folder and post a link here."A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

Hi, Since Windows system uses separated user mode and kernel mode memory space, stop errors are usually caused by kernel portion components, such as a hardware device, third-party drivers, backup software or anti-virus services (buggy services). Please refer to the following steps to troubleshoot the issue. 1. Boot the computer in Clean Boot for a test. 2. Temporarily disable all unnecessary hardware devices in Device Manager, such as Modem, sound card or external device. For detail steps, we can refer to the link below: Device Clean Boot 3. Run antivirus program and perform a full scanning. If the issue persists, please also refer to the following article to troubleshoot the BSOD issue. http://social.technet.microsoft.com/Forums/en/w7itproperf/thread/537602b2-e930-4596-a2f6-2e4c361a54e7 ; Thanks, Novak

Hi, Sorry that I haven't posted back for awhile. I restored an older Windows 7 image, but still get BSODs. Most of them are 0x000000F4, but I think I also got a couple of 0x0000007A ones. I dual-boot this machine (an HP laptop) and I think that when I boot into Win2K3, I don't get the BSODs (am in Win2K3 now). It seems like the BSODs mostly occur when I'm browsing, mostly with IE, but I think that it even happened with Firefox. I've uploaded the latest two dmp files to Skydrive: http://cid-82b2a530e0d09239.office.live.com/browse.aspx/.Public?uc=2 If anyone has any idea why these BSODs might be happening, please let me know. This HP laptop is kind of my main machine, so I'd really like to be able to fix this problem. Thanks, Jim

Novak, I'll try what you suggested, but as I just posted, I restored a Win7 image and still get the BSODs. That image was from just after I had originally installed Win7, so I'm kind of doubtful that it might be because of a virus. Thanks, Jim

Hi Jim, the dumps ways, csrss.exe was closed, because of an IO Error. This means, the HDD may be damaged. Run the HDD diagnostic tool for your HDD model. André"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

Andre, I was starting to wonder about the hard drive. I used MS VPC, and I was just noticing that some of my VPC guests are taking a really long time to save. Can you tell from the dump which drive (my laptop has 2 drives)? Thanks again, Jim

Hi, FYI, I ran chkdsk on the partitions on the system, and noticed that that was showing errors on my F: partition, which is where I have my pagefile/swap configured. I changed the pagefile back to my C: partition temporarily, then deleted that F: partition, re-created it, and did a surface scan using a tool that I have. I don't know if this'll help or not :(... Anyway, I've ordered a new drive, but am still trying to see if it'd be possible to determine which drive might've been causing that BSOD from the dmp files? Thanks, Jim

Hi, This issue also can occur by fault RAM. I suggest you replace RAM to check the result. For more information about the issue, please refer to the link below: http://social.technet.microsoft.com/Forums/en/w7itproperf/thread/537602b2-e930-4596-a2f6-2e4c361a54e7 Thanks, Novak

Novak, I've run MS Memory Diagnostics multiple times, with no errors. I'm currently running Memtest86 to see if that finds anything. Jim

Hi, I ran memtest overnight, and no errors were found. I'll try the new drive that I'm waiting for as soon as it gets in. Jim

Your RAM is ok, only the disk is broken. I don't understand why Novak told you this *shrug my shoulders*."A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

Andre (and Novak), No problem. I understand solving this kind of thing is a process of elimination (been there, done that :)). I only hope that the problem is eventually eliminated, because having the laptop BSOD randomly is making it hard to get anything done. I think that I'll be getting the new drive today, so we'll see how that goes. Thanks, Jim

Andre, I think/hope that I may have just discovered a problem. I removed the covers over the two drives on the bottom of the laptop, and was going to try to reseat the drives. When I did that, I found that one of the drives (the 2nd one) was really easy to pull out (the drives go into a caddy, and have a right-angle connector which seats into a connector on the motherboard). I am guessing that at least that drive was not making very good connection with the motherboard connector. There are four screws to hold the drive to the caddy, but the way that the caddy+drive is secured to the laptop itself seems kind of insecure, to me. There aren't any fasteners/screws for that. Rather, there are two captive screws in the plastic cover that go through 'ears' in the caddy, into some posts on the motherboard or laptop itself. Each of those two captive screws has a washer on it, so I guess that the washer is suppose to put enough pressure on the 'ears' on the caddy to hold the caddy down, but maybe it's not, so I added some 'pads' between the cover and the drive, to put some additional pressure on it when the cover is screwed down. I'll keep an eye on things, to see if the BSODs go away now :)... Jim

Hi Jim, ok, this can also be the cause. I hope that it fixes your BSOD :) André"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

Hi, My HP laptop requires a small adapter for SATA drives. As a followup, after more close examination, it appears that the SATA connector adapter that I got (from Ebay) that came with the caddy is just a little shorter than the one that is attached to the original SATA drive. From more research, it appears that there are two different adapters, for different HP laptops, an "H8S" and an "H8L". I'm guessing that the one that I got is an "H8S" ("S"==> "short"?), whereas I probably need an "H8L". For now, what I've done is not push the adapter all the way into the SATA connector on the drive, and it seems to be working ok so far (no more BSODs, so far, crossed fingers). I've also ordered an "H8L" connector. Jim