BSOD idle in Windows, error 0x000000f4

Welcome to the forum.

Follow this:

Code:

Model	OCZ-VERTEX3

writhziden said:

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

• Use Crystal Disk Info to upload a screenshot of your Hard Drives (s).
  
  • Then test your Hard Drives (s) running a Hard Drive Diag.

• Remove Daemon Tools/Alchohol completely. SPTD.sys is known to cause BSODs.
  
  • How to remove sptd.sys from system
  • Registry and SPTD problems | DAEMON Pro Help

• Virus Check:
  
  • Make scans with these tools below:
    
    • TDSSKiller Rootkit Removal Utility Free Download | Kaspersky Lab US
    • Online Virus Scanner Eset
• Application conflict:
  
  • Reduce the start-up items. This will help avoid software conflicts:
    
    • Remove Startup Programs in Windows 7
    • Clean Startup in Windows 7

• System File Checker
  
  • The SFC /SCANNOW Command - System File Checker scans the integrity of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible. If you have modified your system files as in theming explorer/system files, running sfc /scannow will revert the system files to it's default state.
    
    • Link to full tutorial: SFC /SCANNOW Command - System File Checker
• Run Disk Check in Windows 7
  
  • Run this on your Hard Drive(s). This will show you how to run Check Disk or chkdsk in Windows 7 to check a selected hard disk for file system errors and bad sectors on it. With both boxes checked for all HDDs and with Automatically fix file system errors. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log
    
    • Link to full tutorial: Disk Check

• Use Crystal Disk Info to upload a screenshot of your Hard Drives (s).
  
  • Then test your Hard Drives (s) running a Hard Drive Diag.

• Microsoft Security Essentials & the Free version of Malwarebytes, update and make full scans separately:
  
  • Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase
  • Help protect your PC with Microsoft Security Essentials
  • Malwarebytes Free

   Note

Do not start the trial version of MalwareBytes

• Also take a look at: Good & Free System Security Combination

• Check for heating issues using Speccy or HWmonitor
  
  • HWMonitor CPUID - System & hardware benchmark, monitoring, reporting
  • Speccy - System Information - Free Download
    
    • Please upload a summary tab using Speccy. Screenshots and Files - Upload and Post in Seven Forums

Let us know the results.

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\USER\Downloads\unphoto\SF_18-11-2013\111813-13759-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
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`04064000 PsLoadedModuleList = 0xfffff800`042a76d0
Debug session time: Mon Nov 18 22:51:37.715 2013 (UTC + 6:00)
System Uptime: 0 days 0:43:58.512
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa800cff2b30, fffffa800cff2e10, fffff800043de7b0}

----- ETW minidump data unavailable-----
Probably caused by : csrss.exe

Followup: MachineOwner
---------

7: 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: fffffa800cff2b30, Terminating object
Arg3: fffffa800cff2e10, Process image file name
Arg4: fffff800043de7b0, Explanatory message (ascii)

Debugging Details:
------------------

----- ETW minidump data unavailable-----

KERNEL_LOG_FAILING_PROCESS:  <NULL>

PROCESS_OBJECT: fffffa800cff2b30

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:  WIN7_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`05f97e38 fffff800`04467ab2 : 00000000`000000f4 00000000`00000003 fffffa80`0cff2b30 fffffa80`0cff2e10 : nt!KeBugCheckEx
fffff880`05f97e40 fffff800`04412abb : ffffffff`ffffffff fffffa80`0d055b50 fffffa80`0cff2b30 fffffa80`0cff2b30 : nt!PspCatchCriticalBreak+0x92
fffff880`05f97e80 fffff800`04392674 : ffffffff`ffffffff 00000000`00000001 fffffa80`0cff2b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17486
fffff880`05f97ed0 fffff800`040d8e53 : fffffa80`0cff2b30 fffff800`c0000005 fffffa80`0d055b50 00000000`004c0580 : nt!NtTerminateProcess+0xf4
fffff880`05f97f50 fffff800`040d5410 : fffff800`0412482f fffff880`05f98a38 fffff880`05f98790 fffff880`05f98ae0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`05f980e8 fffff800`0412482f : fffff880`05f98a38 fffff880`05f98790 fffff880`05f98ae0 00000000`004c2090 : nt!KiServiceLinkage
fffff880`05f980f0 fffff800`040d9242 : fffff880`05f98a38 00000000`000713b8 fffff880`05f98ae0 00000000`004c1b68 : nt! ?? ::FNODOBFM::`string'+0x488e4
fffff880`05f98900 fffff800`040d7dba : 00000000`00000001 00000000`004c0c98 00000000`00000001 00000000`000713b8 : nt!KiExceptionDispatch+0xc2
fffff880`05f98ae0 00000000`76d48e5d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`004c0ca0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d48e5d


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
---------

Is the firmware of the SSD up to date?

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Usra\Downloads\SF_19-11-2013\111913-14274-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*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
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`04002000 PsLoadedModuleList = 0xfffff800`042456d0
Debug session time: Wed Nov 20 01:02:01.543 2013 (UTC + 6:00)
System Uptime: 0 days 0:37:01.339
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
.....
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, 0, fffff88003b84ab8, fffff88003b84310}

Probably caused by : nvlddmkm.sys ( nvlddmkm+1be795 )

Followup: MachineOwner
---------

4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: fffff88003b84ab8, Exception Record Address
Arg4: fffff88003b84310, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
+0
00000000`00000000 ??              ???

EXCEPTION_RECORD:  fffff88003b84ab8 -- (.exr 0xfffff88003b84ab8)
ExceptionAddress: 0000000000000000
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000008
   Parameter[1]: 0000000000000000
Attempt to execute non-executable address 0000000000000000

CONTEXT:  fffff88003b84310 -- (.cxr 0xfffff88003b84310)
rax=0000000000000000 rbx=0000000000000001 rcx=fffffa800cab9000
rdx=0000000000000044 rsi=fffffa800cab9000 rdi=fffffa800a551790
rip=0000000000000000 rsp=fffff88003b84cf8 rbp=fffffa800cc12f30
 r8=0000000000000000  r9=0000000000000000 r10=fffff80004002000
r11=0000000000000527 r12=fffffa80069eb000 r13=0000000000000001
r14=fffffa80069f0b00 r15=fffffa80069f8530
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
00000000`00000000 ??              ???
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000008

EXCEPTION_PARAMETER2:  0000000000000000

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800042af100
GetUlongFromAddress: unable to read from fffff800042af1c0
 0000000000000000 Nonpaged pool

FOLLOWUP_IP: 
nvlddmkm+1be795
fffff880`0fa1b795 ??              ???

FAILED_INSTRUCTION_ADDRESS: 
+1be795
00000000`00000000 ??              ???

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff8800fa1b795 to 0000000000000000

STACK_TEXT:  
fffff880`03b84cf8 fffff880`0fa1b795 : 00000000`00000001 fffffa80`0ce5ceb0 fffffa80`0ce5ce00 fffffa80`0cc12f30 : 0x0
fffff880`03b84d00 00000000`00000001 : fffffa80`0ce5ceb0 fffffa80`0ce5ce00 fffffa80`0cc12f30 fffffa80`069f8530 : nvlddmkm+0x1be795
fffff880`03b84d08 fffffa80`0ce5ceb0 : fffffa80`0ce5ce00 fffffa80`0cc12f30 fffffa80`069f8530 fffffa80`069f0b00 : 0x1
fffff880`03b84d10 fffffa80`0ce5ce00 : fffffa80`0cc12f30 fffffa80`069f8530 fffffa80`069f0b00 00000000`00000001 : 0xfffffa80`0ce5ceb0
fffff880`03b84d18 fffffa80`0cc12f30 : fffffa80`069f8530 fffffa80`069f0b00 00000000`00000001 fffffa80`0a550268 : 0xfffffa80`0ce5ce00
fffff880`03b84d20 fffffa80`069f8530 : fffffa80`069f0b00 00000000`00000001 fffffa80`0a550268 00000000`00002001 : 0xfffffa80`0cc12f30
fffff880`03b84d28 fffffa80`069f0b00 : 00000000`00000001 fffffa80`0a550268 00000000`00002001 fffffa80`0cc12f30 : 0xfffffa80`069f8530
fffff880`03b84d30 00000000`00000001 : fffffa80`0a550268 00000000`00002001 fffffa80`0cc12f30 fffffa80`0a551790 : 0xfffffa80`069f0b00
fffff880`03b84d38 fffffa80`0a550268 : 00000000`00002001 fffffa80`0cc12f30 fffffa80`0a551790 fffff880`0fa1c39f : 0x1
fffff880`03b84d40 00000000`00002001 : fffffa80`0cc12f30 fffffa80`0a551790 fffff880`0fa1c39f fffffa80`07c49590 : 0xfffffa80`0a550268
fffff880`03b84d48 fffffa80`0cc12f30 : fffffa80`0a551790 fffff880`0fa1c39f fffffa80`07c49590 00000000`00002001 : 0x2001
fffff880`03b84d50 fffffa80`0a551790 : fffff880`0fa1c39f fffffa80`07c49590 00000000`00002001 fffffa80`4d52564e : 0xfffffa80`0cc12f30
fffff880`03b84d58 fffff880`0fa1c39f : fffffa80`07c49590 00000000`00002001 fffffa80`4d52564e fffff880`0fa734ab : 0xfffffa80`0a551790
fffff880`03b84d60 fffffa80`07c49590 : 00000000`00002001 fffffa80`4d52564e fffff880`0fa734ab fffffa80`0a550268 : nvlddmkm+0x1bf39f
fffff880`03b84d68 00000000`00002001 : fffffa80`4d52564e fffff880`0fa734ab fffffa80`0a550268 fffff880`0fc5feab : 0xfffffa80`07c49590
fffff880`03b84d70 fffffa80`4d52564e : fffff880`0fa734ab fffffa80`0a550268 fffff880`0fc5feab fffffa80`07c49590 : 0x2001
fffff880`03b84d78 fffff880`0fa734ab : fffffa80`0a550268 fffff880`0fc5feab fffffa80`07c49590 00000000`00002001 : 0xfffffa80`4d52564e
fffff880`03b84d80 fffffa80`0a550268 : fffff880`0fc5feab fffffa80`07c49590 00000000`00002001 00000000`00000000 : nvlddmkm+0x2164ab
fffff880`03b84d88 fffff880`0fc5feab : fffffa80`07c49590 00000000`00002001 00000000`00000000 00000000`bfee0100 : 0xfffffa80`0a550268
fffff880`03b84d90 fffffa80`07c49590 : 00000000`00002001 00000000`00000000 00000000`bfee0100 00000000`00000000 : nvlddmkm+0x402eab
fffff880`03b84d98 00000000`00002001 : 00000000`00000000 00000000`bfee0100 00000000`00000000 00000000`bfee0100 : 0xfffffa80`07c49590
fffff880`03b84da0 00000000`00000000 : 00000000`bfee0100 00000000`00000000 00000000`bfee0100 00000000`00000000 : 0x2001


SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nvlddmkm+1be795

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52676afe

STACK_COMMAND:  .cxr 0xfffff88003b84310 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_NULL_IP_nvlddmkm+1be795

BUCKET_ID:  X64_0x7E_NULL_IP_nvlddmkm+1be795

Followup: MachineOwner
---------

4: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f85d000 fffff880`10494000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Wed Oct 23 12:21:50 2013 (52676AFE)
    CheckSum:         00C0CF0F
    ImageSize:        00C37000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Arc said:

Lately we have experienced some issues with the latest driver. Install the 314.22 WHQL only.

• Uninstall All nvidia items in Control Panel > Programs and features
  
  • 3D Vision Control Driver
  • 3D Vision Driver
  • Graphics Driver
  • HD Audio Driver
  • PhysX
  • nvidia Update
  
  (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
• Now follow Drivers - Clean Left over Files after Uninstalling
• Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

Let us know the results.

Thanks for the update, keep us posted.

Good to hear!