New
#1
BSOD while idle, error 0x000000f4
Computer is recently built running 2008 server R2. Everything seemed fine until a couple days ago when I started coming home to a BSOD. The code is always F4 (Critical Object Termination) on ntoskrnl.exe save for once when it crashed on a bios update.
Since then I have updated my bios to the latest version, removed a troublesome NIC card (not yet replaced), and tried unsuccessfully to find a pattern to the problem.
sfc /scannow comes back clean. There is no overclocking. Hard drive load does not seem to be a factor. Hard drive scans have come back clean. Disabled Symantec Endpoint Protection with no effect. Malwarebytes reports clean. Not sure what else to do now. I've seen it run for 10 minutes and crash. I've also seen it run for 24+ hours before it crashes again.
Left the system running using Driver Verifier for a while (3+ hours) with no issues.
Last edited by matrixhacker; 07 Aug 2012 at 19:34. Reason: Minor update