CRITICAL_OBJECT_TERMINATION (f4)

Similar Questions

• Laptop Dell - blue screen of death - CRITICAL_OBJECT_TERMINATION caused by driver: ntkrnlpa.exe

  Hello

  I searched for a solution to a major problem, as we have seen with some Dell systems I work with.

  three models who know that exact blue screen: Dell E6430, E7240, and E7440.

  Every accident is due to random, indicating the following:

  Bug Check String: CRITICAL_OBJECT_TERMINATION

  Bug check code: 0x000000f4

  P1: 0 X 00000003

  (the others are always different)

  Caused by the driver: ntkrnlpa.exe

  Address: ntkrnlpa.exe + dedd8

  32 bit OS/processor.

  So far, we tried the following:

  Update the BIOS of the systems to the latest versions.

  Update the version of the driver from the hard drive from the site of the manufacturer (not one Samsungs)

  Replace most of the internal parts (motherboard, RAM, CPU) with known work of Dell parts.

  Recreate the image on the computer entirely. (re - install windows, but still receive the error re-)

  In the end, we end up making a complete replacement of the HD.

  We carried out Diagnostics using a few tools (SMART data reading using SpeedFan) and it is not to report all errors. We used the Dells built in the diagnosis on the RAM, hard drive and nothing seems made of any hardware failure during testing of large 4 hours.

  I was wondering if someone had met these blue screens on other systems, and what other tools and resources, we could use to try and fix these without doing a complete system replacement.

  The most recent crash in this issue is 29 October so it may not be the same as the current problem

  These accidents were related to the corruption of memory (probably caused by a driver).

  Run these two tests to check your memory and find which driver is causing the problem.  Launch auditor.  You don't need to run memtest again unless the auditor is not the cause, or you want to.

  If you are overclocking anything reset by default before running these tests.
  In other words STOP! If you don't know what it means that you're probably not  
  
  
  
  
  1-Driver Verifier (for full instructions, see our wiki here)
  
  2-Memtest. (You can learn more about running memtest here)

• BSOD on shutdown/reboot bugcheckcode CRITICAL_OBJECT_TERMINATION error 0x000000F4

  Hi guys im currently crashes BSOD every time that I restart or shutdown my desktop im running windows 7 Ultimate SP1 and I used bluescreenview, but the results were so vague, that I'm a hard time figuring what went wrong

  the error is bugcheckcode 0x000000F4 CRITICAL_OBJECT_TERMINATION

  Thank you.

  CRITICAL_OBJECT_TERMINATION (f4)

  This indicates that a process or thread crucial to system operation has unexpectedly is released or ended.

  BugCheck F4, {3, fffffa80060f8aa0, fffffa80060f8d80, fffff800031d7db0}

  1st argument is 3, indicating that it was a process as opposed to a thread that is stopped.

  1: kd >! fffffa80060f8aa0 process 3
  GetPointerFromAddress: unable to read from fffff80003105000
  PROCESS fffffa80060f8aa0
  SessionId: no Cid: 08C 8 Peb: 7efdf000 ParentCid: 06f4
  DirBase: 7c47d000 ObjectTable: fffff8a001ddaa00 HandleCount:
  Image: winlogon.exe

  The process that ended a winlogon.exe.

  1: kd > k
  Call child-SP RetAddr site
  00000000'00000000 00000000'00000000, 0 x 0

  Battery set to zero.

  -----------------------------------

  With only a minidump, it is impossible to say what caused the end of winlogon. If I had to guess, it's probably a software conflict. However, if I had a kernel image, I would have a solid answer as well as the question of whether or not there is the possibility of a rootkit. With only a minidump, it is impossible to say.

  For now, we will do the following:

  1. make sure that your Asmedia ASM-106 x Sata 6 G controller drivers are up-to-date.

  2 uninstall all Asus bloatware.

  3 uninstall cFosSpeed - The Internet Accelerator, software bug.

  If the above does not stop the breaks down, I'll need a kernel image.

  Kind regards

  Patrick

• KERNEL_DATA_INPAGE_ERROR then CRITICAL_OBJECT_TERMINATION

  I rarely post on a Web site because I can generally understand the answer, but this one really got me.  I had 2 BSOD.  The KERNEL_DATA_INPAGE_ERROR on 10/04/13 then the CRITICAL_OBJECT_TERMINATION 04 12, 13.  Yesterday, I got both of them 10 minutes apart.

  It is a brand new system installed at the beginning of February, which has had a hard drive failure, so I bought a new drive and installed Win 7 3/20/13.   Any help is greatly appreciated!

  https://DL.dropboxusercontent.com/u/4504718/041013-24476-01.dmp
  https://DL.dropboxusercontent.com/u/4504718/041213-24102-01.dmp

  This is the result I got from WinDbg.

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

  Loading dump file [C:\Windows\Minidump\041013-24476-01.dmp]
  The mini kernel dump file: only registers and the trace of the stack are available

  Symbol search path is: SRV * your local folder for symbols * http://msdl.microsoft.com/download/symbols
  Executable search path is:
  Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) free x 64
  Product: WinNt, suite: TerminalServer personal TerminalServer
  By: 7601.18044.amd64fre.win7sp1_gdr.130104 - 1431
  Computer name:
  Kernel base = 0xfffff800 '02c0c000 PsLoadedModuleList = 0xfffff800' 02e50670
  The debugging session: 17:34:08.826 Wed 10 April 2013 (UTC - 04:00)
  System Uptime: 0 days 4:53:58.122
  Loading the kernel symbols
  ...............................................................
  ................................................................
  .............................
  Loading user symbols
  Loading unloaded module list
  ...................
  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  Use! analyze - v to obtain detailed debugging information.

  7 has error checking, {fffff6fc50029768, ffffffffc000000e, 215018880, fffff8a0052ed340}

  Probably caused by: ntkrnlmp.exe (nt! FNODOBFM: 'string' + 36c1a)

  Follow-up: MachineOwner
  ---------

  3: kd >! analyze - v
  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  KERNEL_DATA_INPAGE_ERROR (7A)
  The requested page of kernel data could not be read in.  Usually caused by
  a bad block in the disk controller or paging file error. See also
  KERNEL_STACK_INPAGE_ERROR.
  If the error status 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
  This means that the disk subsystem has suffered a failure.
  If the status of the error is 0xC000009A, it means the query failed because
  a file system has failed to move forward.
  Arguments:
  Arg1: fffff6fc50029768, type of lock which took place (1,2,3 or PTE address value)
  Arg2: ffffffffc000000e, error state (state code of e/s normally)
  Arg3: 0000000215018880, current process (virtual address for the lock type 3 or PTE)
  Arg4: fffff8a0052ed340, virtual address that could not be paged in (or PTE contents if arg1 is a PTE address)

  Debugging information:
  ------------------

  Error_code: (NTSTATUS) 0xc000000e - a device which does not exist was specified.

  DISK_HARDWARE_ERROR: Error occurred with disc material

  BUGCHECK_STR: 0x7a_c000000e

  CUSTOMER_CRASH_COUNT: 1

  DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

  Nom_processus: System

  CURRENT_IRQL: 0

  DEVICE_OBJECT: fffffa800809d000

  TRAP_FRAME: fffff880035d5500-(.trap 0xfffff880035d5500)
  NOTE: The frame trap does contain not all registers.
  Some registry values can be set to zero or incorrect.
  Rax = fffff8a0052ed340 rbx = 0000000000000000 rcx = fffff8a0052da9e0
  RDX = fffffa80066b9de0 rsi = 0000000000000000 rdi = 0000000000000000
  RIP = fffff80002c98d5a rsp = fffff880035d5690 rbp = fffff80002ebda00
  R8 = fffff880035d5838 r9 = fffff880035d5840 = 0000000000000000 r10
  R11 = fffff880035d58b8 r12 = 0000000000000000 r13 = 0000000000000000
  R14 = 0000000000000000 r15 = 0000000000000000
  iopl = 0 nv up ei pl zr po nc
  NT! MmMapViewInSystemCache + 0x3a:
  fffff800 '02c98d5a 4c8b20 mov r12, qword ptr [rax] ds:fffff8a0' 052ed340 = ffffffffffffffff
  Reset the default scope

  LAST_CONTROL_TRANSFER: from fffff80002cf4812 to fffff80002c81c40

  STACK_TEXT:
  "fffff880 '035d51e8 fffff800' 02cf4812: 00000000' 0000007 a fffff6fc ' 50029768 ffffffff c000000e ' 00000002'15018880: nt! KeBugCheckEx
  "fffff880 '035d51f0 fffff800' 02ca8a0f: fffffa80 ' 0d5fae00 fffff880 ' 035 d 5360 fffff800 ' 02ebd600 fffffa80 ' 0d5fae00: nt! : FNODOBFM: 'string' + 0x36c1a
  fffff880 '035d52d0 fffff800' 02c8f2a9: 00000000'00000000 00000000'00000000 ffffffff 'ffffffff fffff880' 016c8c14: nt! MiIssueHardFault + 0x28b
  "fffff880 '035d53a0 fffff800' 02c7fd6e: 00000000 ' fffff8a0 00000000 ' 052ed340 fffff880 '00000000 fffff880' 031d 7830: nt! MmAccessFault + 0 x 1399
  "fffff880 ' 035 d 5500 fffff800 ' 02c98d5a: fffffa80 00000000 00000001" 00000001 00000000'00000000 00000000'00000000: nt! KiPageFault + 0x16e
  fffff880 '035 d 5690 fffff800' 02c 98127: fffff880 ' 035d5cb0 fffff880 '031 d 7830 fffff880' 035d 5838 fffffa80 ' 0b21c320: nt! MmMapViewInSystemCache + 0x3a
  "fffff880 ' 035 d 5800 fffff800 ' 02c9708f: fffffa80'00000000 00000000'00000048 00000000'00000000 00000000'00000000: nt! CcGetVacbMiss + 0 x 177
  "fffff880 '035d58c0 fffff800' 02caa0b6: fffffa80 ' 00000000 00000000'00000048 fffff880 ' 035d59a8 fffff880'035 d 5988: nt! CcGetVirtualAddress + 0x2e0
  "fffff880 ' 035 d 5950 fffff800 ' 02caa734: fffffa80'093f5910 fffffa80 '067b 7000 fffff880' 035d5a90 00000000' 0000ff78: nt! CcMapAndCopyInToCache + 0 x 146
  "fffff880 '035d5a40 fffff880' 01625eb6: 00000000 ' fffff880 00000000 '035d5cb0 fffffa80' 0a0aeb00 fffffa80 ' 0a0aeb00: nt! CcCopyWrite + 0 x 194
  fffff880'035d5ad0 fffff880'01626463: fffffa80 ' 0a0aeb00 fffffa80 '0809cc60 fffff880' 035d5c01 fffff880 ' 035d5c00: Ntfs! NtfsCommonWrite + 0 x 3390
  fffff880 '035d5c80 fffff880' 0114bbcf: fffffa80'0809cfb8 fffffa80 '0809cc60 fffffa80' 09ddcbb0 00000000 00000001': Ntfs! NtfsFsdWrite + 0x1c3
  "fffff880 '035d5d40 fffff880' 0114a6df: fffffa80'076018f0 00000000 00000001' fffffa80 ' 07601800 fffffa80 ' 0809cc60: fltmgr! FltpLegacyProcessingAfterPreCallbacksCompleted + 0x24f
  fffff880 '035d5dd0 fffff800' 02f8de0b: 00000000 00000001' fffffa80 '093916a 0 00000000 00000001' fffffa80' 0809cc60: fltmgr! FltpDispatch + 0xcf
  "fffff880 '035d5e30 fffff800' 02f98803: fffffa80 ' 0809 d 000 00000000 00000000' fffffa80 ' 093916a 0 fffff880'031 d 7180: nt! IopSynchronousServiceTail + 0xfb
  fffff880 '035d5ea0 fffff800' 02c80ed3: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: nt! NtWriteFile + 0x7e2
  fffff880 '035d5fa0 fffff800' 02c7d490: fffff800 ' 02eec693 fffffa80 '0674d3c0 fffffa80' 0a07c310 fffffa80 ' 067b 7000: nt! KiSystemServiceCopyEnd + 0x13
  fffff880 '035d61a8 fffff800' 02eec693: fffffa80 ' 0674d3c0 fffffa80 '0a07c310 fffffa80' 067b 7000 fffff800 ' 02fcda03: nt! KiServiceLinkage
  fffff880 '035d61b0 00000000' 00000000: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: nt! EtwpRealtimeSaveBuffer + 0 x 93

  STACK_COMMAND: kb

  FOLLOWUP_IP:
  NT! : FNODOBFM: 'string' + 36c1a
  fffff800'02cf4812 cc int 3

  SYMBOL_STACK_INDEX: 1

  SYMBOL_NAME: nt! : FNODOBFM: 'string' + 36c1a

  FOLLOWUP_NAME: MachineOwner

  MODULE_NAME: nt

  Nom_image: ntkrnlmp.exe

  DEBUG_FLR_IMAGE_TIMESTAMP: 50e79935

  FAILURE_BUCKET_ID: X64_0x7a_c000000e_nt! _ ?? _::FNODOBFM:_string_ + 36c1a

  BUCKET_ID: X64_0x7a_c000000e_nt! _ ?? _::FNODOBFM:_string_ + 36c1a

  Follow-up: MachineOwner
  ---------

  I know that it is basically a year later, but I understood the problem and that you wanted to post a reply.  As part of my solution to prevent other disk hard breaks down ruining the system I've set up a mirror of RAID hard drive.  I proceeded to install windows and the RAID broke immediately.  After several attempts to rebuild the RAID and reproduce the problem, at one point one of the hard drives started clicking.  I was seriously confused, but concluded that the only possible cause for such ridiculous behavior could be the power supply.  Keep in mind, I swapped the SATA cables and used different SATA power connectors.

  After replacing the power supply the problem has not happened since.

• Blue screens during playback of Skyrim: CRITICAL_OBJECT_TERMINATION (f4)

  Hey guys! So I get random Bsod during playback of Skyrim, something strange is no other games I had installed don't this. Battlefield 3 works great with many others. Skyrim crashes when loading screens and menus of the inventory for the 2-3 minutes then the blue screen appears.  At first I noticed loss of sound, so I thought it might be something to do with my sound card drivers. I've updated all the people and the problem persists. I really don't feel the urge to do a clean install just to be able to play skyrim, but would like to know if it could be one of my hardware dying.

  My system specs are:

  ASUS M5A88-
  AMD Phenom II x 4 980 3.7 GHz
  4.00 GB of OCZ Platinum DDR3 1333 MHz

  NVIDIA Geforce 470GTX with the latest drivers (301.42)
  Western Digital Caviar Blue 320 GB (system disk)
  
  Western Digital Caviar Black 1 TB (storage)
  I will paste my last dump for you guys to take a look at as I don't really have any idea.
  Microsoft (R) Windows debug 6.12.0002.633 AMD64 Version
  Copyright (c) Microsoft Corporation. All rights reserved.
  Loading dump file [C:\Windows\Minidump\082612-22354-01.dmp]
  The mini kernel dump file: only registers and the trace of the stack 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 (4 procs) free x 64
  Product: WinNt, suite: TerminalServer SingleUserTS
  By: 7600.16695.amd64fre.win7_gdr.101026 - 1503
  Computer name:
  Kernel base = 0xfffff800 '02e1a000 PsLoadedModuleList = 0xfffff800' 03057e50
  The debugging session: 20:30:07.617 Sun August 26, 2012 (UTC + 01:00)
  System Uptime: 0 days 0:04:51.021
  Loading the kernel symbols
  ...............................................................
  ................................................................
  ........................
  Loading user symbols
  Loading unloaded module list
  .....
  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************
  Use! analyze - v to obtain detailed debugging information.
  BugCheck F4, {3, fffffa8005e72b30, fffffa8005e72e10, fffff800031932d0}
  Probably caused by: wininit.exe
  Follow-up: MachineOwner
  ---------
  1: kd >
  ! analyze - v
  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************
  CRITICAL_OBJECT_TERMINATION (f4)
  A process or thread crucial to system operation has unexpectedly left or been
  terminated.
  Several processes and threads are necessary to the functioning of the
  System; When they are finished (for some reason any), the system may not
  function longer.
  Arguments:
  Arg1: 0000000000000003, process
  Arg2: fffffa8005e72b30, object of ends
  Arg3: fffffa8005e72e10, name of the process image file
  Arg4: fffff800031932d0, explanatory message (ascii)
  Debugging information:
  ------------------
  PROCESS_OBJECT: fffffa8005e72b30
  Nom_image: wininit.exe
  DEBUG_FLR_IMAGE_TIMESTAMP: 0
  MODULE_NAME: wininit
  FAULTING_MODULE: 0000000000000000
  Nom_processus: wininit.exe
  EXCEPTION_RECORD: fffff880062d5b78-(.exr 0xfffff880062d5b78)
  ExceptionAddress: 00000000774d57cd
  ExceptionCode: c0000005 (access violation)
  ExceptionFlags: 00000000
  NumberParameters: 2
  Parameter [0]: 0000000000000001
  Parameter [1]: 00000000022e0b58
  Try to write at the address 00000000022e0b58
  EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - the instruction at 0 x % lx 08 referenced memory at 0 x % 08 lx. The memory could not be %s.
  CUSTOMER_CRASH_COUNT: 1
  DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
  CURRENT_IRQL: 0
  Error_code: (NTSTATUS) 0xc0000005 - the instruction at 0 x % lx 08 referenced memory at 0 x % 08 lx. The memory could not be %s.
  EXCEPTION_PARAMETER1: 0000000000000001
  EXCEPTION_PARAMETER2: 00000000022e0b58
  WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c20e0
  00000000022e0b58
  FOLLOWUP_IP:
  + 3564393033373837
  00000000' 774d57cd?              ???
  FAULTING_IP:
  + 3564393033373837
  00000000' 774d57cd?              ???
  FAILED_INSTRUCTION_ADDRESS:
  + 3564393033373837
  00000000' 774d57cd?              ???
  BUGCHECK_STR: 0xF4_C0000005
  STACK_TEXT:
  fffff880 '062d50f8 fffff800' 03216f62: 00000000' 000000f4 00000000 00000003' fffffa80 '05e72b30 fffffa80' 05e72e10: nt! KeBugCheckEx
  "fffff880 ' 062 d 5100 fffff800 ' 031bea23: ffffffff 'ffffffff fffffa80' 067f5b60 fffffa80 '05e72b30 fffffa80' 05e72b30: nt! PspCatchCriticalBreak + 0 x 92
  fffff880 '062 d 5140 fffff800' 0314690c: ffffffff 'ffffffff 00000000 00000001' fffffa80' 05e72b30 fffff6fb'00000008: nt! : NNGAKEGL: 'chain' + 0 x 17666
  "fffff880 ' 062 d 5190 fffff800 ' 02e89993: fffffa80 ' 05e72b30 fffff800 'ffffe77a c0000005' ebc7f56e fffffa80 ' 067f5b60: nt
  ! NtTerminateProcess + 0x20c
  "fffff880 ' 062 d 5210 fffff800 ' 02e85f30: fffff800 ' 02ec4dbc fffff880 '062d5b78 fffff880' 062d58e0 fffff880 ' 062d5c20: nt! KiSystemServiceCopyEnd + 0x13
  fffff880 '062d53a8 fffff800' 02ec4dbc: fffff880'062d5b78 fffff880 '062d58e0 fffff880' 062d5c20 00000000' 022e1de0: nt! KiServiceLinkage
  fffff880 '062d53b0 fffff800' 02e89d82: fffff880 '062d5b78 00000000' 0000aab7 fffff880' 062d5c20 00000000' 022e18b8: nt! KiDispatchException + 0x53b
  fffff880 '062d5a40 fffff800' 02e888fa: 00000000'00000001 00000000' 0000aab7 00000000' 775f4401 00000000' 00000000: nt
  ! KiExceptionDispatch + 0xc2
  fffff880 '062d5c20 00000000' 774d57cd: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: nt! KiPageFault + 0x23a
  00000000' 022e0b60 00000000'00000000: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: 0x774d57cd
  STACK_COMMAND: kb
  FOLLOWUP_NAME: MachineOwner
  FAILURE_BUCKET_ID: X64_0xF4_C0000005_IMAGE_wininit.exe
  BUCKET_ID: X64_0xF4_C0000005_IMAGE_wininit.exe
  Follow-up: MachineOwner
  ---------
  Any response would be much appreciated

  See you soon.

  Finally got my food, the store, I ordered home in trouble with their provider.
  They ended up giving me that the GX750w instead of the 650w so out something this nice.

  Good news at least I had a nice game of 4 hours with the 470gtx session in my computer and all is well. I'm surprised I've never caught how important a PSU can be, never once again at least.

  Thanks for all the guys help back to the game for me :)

  Anonter

• BSOD 0X000000F4 CRITICAL_OBJECT_TERMINATION

  I have frequent BSOD at random moments. Currently in safe mode.

  I already uninstalled the software installed recently, checked the connection of hardware, reinstalled and updated all my drivers, run a complete antivirus scan, but still fail to fix.

  Link to the dmp files
  https://www.dropbox.com/s/bwkmipk4b76rle8/minidump.rar

  Please help Daniel

  Daniel, please run Malwarebytes:

  https://www.Malwarebytes.org/MWB-download/

  Kind regards

  Patrick

• BSOD on Windows 7 "KERNEL_DATA_INPAGE_ERROR" and "CRITICAL_OBJECT_TERMINATION.

  Hello everyone, I'm having a problem with my computer where it crashes frequently (about 2 or 3 times a day) usually after something as simple as look a PDFs or random navigation and I would be grateful to receive help to solve this problem.

  Of all the BSOD, only three of them have generated the dmp, here attached files:

  https://onedrive.live.com/redir?RESID=B57DC5EDA9D56305%21281

  I don't really know how to analyze the dmp files, so an explanation would be nice.

  Thanks in advance. o /.

  Run the tool linked below, the update to download, install, and run a complete scan with Microsoft Security Essentials.

  Uninstall tools for Bitdefender products.

  http://www.BitDefender.com/uninstall/

  Microsoft Security Essentials.

  http://Windows.Microsoft.com/en-us/Windows/Security-Essentials-download

  Chip Alcor card reader was updated.

  AlcGener.sys Thu Dec 16 07:35:22 2010 (4D0A078A): http://support.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-w-series-laptops/thinkpad-w540/downloads/DS038415

  If accidents continue, run the Verifier (DV) according to the instructions in the link below.

  Note: Be sure to read and remember the steps to reset the DV in case of crash and post a link to the newly generated crash dump here.

  Driver Verifier - stalking a bad driver to behave. Co-written by ZigZag3143 & JMH3143

  http://answers.Microsoft.com/en-us/Windows/wiki/windows_other-system/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4B6D-95b3-c48669e4c983

• Windows 7 clean installation Blue Screen of Death (BSoD) on a loop of reboot

  Aloha everyone,
  I did an install customized windows 7 on a new Western Digital 1 TB sata hard drive, which has been formatted, partitioned, scandisk, and a ntfs c drive was created prior to installation.
  The installation ended safely.  I then install my screen reader, Window-Eyes, requiring a reboot.  After the reboot, I started to install critical updates to Windows.  On my fourth update and restarting, I got the blue screen of death, that of some people call a BSoD.  I rebooted and Windows itself restored to a previous state of good, of my just accept the default choice.  Then the rear computer works, but if I stop, restart I get the blue screen of death (BSod) is back, and the loop begins again, i.e. windows restores good condition that works well, until you stop, but on reboot - BSoD is BACK!
  I removed the automatic update option, I disabled ScanDisk, drivers updated, bluetooth devices, deactivated sideshow, etc., without any positive result.  I called Microsoft for assisstance and the technician acted like this isn't a known issue, but he assured me that he could solve the problem.  He took control of my computer remotely and do not tell me anything except that the computer would check and repair any problem on reboot, and if he did does not resolve the problem, I have to remember.  The computer has rebooted without the BSod, but I stopped to check if the loop went, and it is not!  To restart the BSOd was back.  It is to note that if I put the computer to sleep, I get a clean start, but stop, restart or hibernation, I get the blue screen of death (BSoD)!
  It is a Dell Dimension XPS 420 with a intel Q6600 processer, 3 GB of ddr2 memory, which came with OS Vista Home premium 32-bit.  The Vista system, the last time I got a BSoD has been for more than a year.

  After researching this problem on Google, it appears that there is a problem without a solution.
  I ran "which has crashed, you can get:
  http://www.resplendence.com/downloads

  The following accident report:
  Monday, December 21, 2009 23:23:44 your computer crashed
  This was probably caused by the following module:
  Wininit.exe
  Bug check code: 0xF4 (0x3, 0xFFFFFA800573B060, 0xFFFFFA800573B340, 0xFFFFF80002D91240)
  Error:
  CRITICAL_OBJECT_TERMINATION
  Empty the file: C:\Windows\Minidump\122109-16972-01.dmp
  file path: C:\Windows\system32\wininit.exe
  product:
  Microsoft® Windows® operating system
  company:
  Microsoft Corporation
  Description: Application to Windows startup
  The accident took place in a standard Microsoft module. Your system configuration can
  be incorrect, perhaps the culprit may be another driver on your system which cannot
  be identified at this time.
  Monday, December 21, 2009 20:22:10 crashed your computer
  This was probably caused by the following module:
  Ntoskrnl.exe
  Verification of error code: 0 x 50 (1, 0xFFFFF80002A9300C, 0xFFFFFFFFFFFFFFD0, 0 x 0 x 0)
  Error:
  PAGE_FAULT_IN_NONPAGED_AREA
  Empty the file: C:\Windows\Minidump\122109-33306-01.dmp
  file path: C:\Windows\system32\ntoskrnl.exe
  product:
  Microsoft® Windows® operating system
  company:
  Microsoft Corporation
  Description: NT Kernel System &
  The accident took place in a standard Microsoft module. Your system configuration can
  be incorrect, perhaps the culprit may be another driver on your system which cannot
  be identified at this time.
  Sunday, December 20, 2009 15:28:42 crashed your computer
  This was probably caused by the following module:
  Ntoskrnl.exe
  Verification of error code: 0 x 50 (1, 0xFFFFF80002ADC00C, 0xFFFFFFFFFFFFFFD0, 0 x 0 x 0)
  Error:
  PAGE_FAULT_IN_NONPAGED_AREA
  Empty the file: C:\Windows\Minidump\122009-17565-01.dmp
  file path: C:\Windows\system32\ntoskrnl.exe
  product:
  Microsoft® Windows® operating system
  company:
  Microsoft Corporation
  Description: NT Kernel System &
  The accident took place in a standard Microsoft module. Your system configuration can
  be incorrect, perhaps the culprit may be another driver on your system which cannot
  be identified at this time.
  Thursday, December 17, 2009 12:27:45 AM your computer crashed
  This was probably caused by the following module:
  Ntoskrnl.exe
  Verification of error code: 0 x 50 (1, 0xFFFFF80002A9300C, 0xFFFFFFFFFFFFFFD0, 0 x 0 x 0)
  Error:
  PAGE_FAULT_IN_NONPAGED_AREA
  Empty the file: C:\Windows\Minidump\121609-28111-01.dmp
  file path: C:\Windows\system32\ntoskrnl.exe
  product:
  Microsoft® Windows® operating system
  company:
  Microsoft Corporation
  Description: NT Kernel System &
  The accident took place in a standard Microsoft module. Your system configuration can
  be incorrect, perhaps the culprit may be another driver on your system which cannot
  be identified at this time.
  Monday, December 14, 2009 20:59:21 crashed your computer
  This was probably caused by the following module:
  Wininit.exe
  Bug check code: 0xF4 (0x3, 0xFFFFFA80059A3060, 0xFFFFFA80059A3340, 0xFFFFF80002DC4240)
  Error:
  CRITICAL_OBJECT_TERMINATION
  Empty the file: C:\Windows\Minidump\121409-25506-01.dmp
  file path: C:\Windows\system32\wininit.exe
  product:
  Microsoft® Windows® operating system
  company:
  Microsoft Corporation
  Description: Application to Windows startup
  The accident took place in a standard Microsoft module. Your system configuration can
  be incorrect, perhaps the culprit may be another driver on your system which cannot
  be identified at this time.
  Sunday, December 13, 2009 02:17:55 your computer crashed
  This was probably caused by the following module:
  Wininit.exe
  Bug check code: 0xF4 (0x3, 0xFFFFFA80058A4060, 0xFFFFFA80058A4340, 0xFFFFF80002D8A240)
  Error:
  CRITICAL_OBJECT_TERMINATION
  Empty the file: C:\Windows\Minidump\121209-24648-01.dmp
  file path: C:\Windows\system32\wininit.exe
  product:
  Microsoft® Windows® operating system
  company:
  Microsoft Corporation
  Description: Application to Windows startup
  The accident took place in a standard Microsoft module. Your system configuration can
  be incorrect, perhaps the culprit may be another driver on your system which cannot
  be identified at this time.
  Conclusion
  6 dumps were found and analysed. Note that it is not always possible to
  assert with certainty whether a reported driver is really responsible for crashing
  your system or that the cause is in another module. However, it is suggested
  looking for updates for the products that these drivers belong to and regularly
  Visit the Windows Update or activate the automatic updates for Windows. In the case of a piece of
  defective material is in trouble, a Google search on the bug control
  Errors, as well as the name of the model and brand of your computer can help you investigate
  This further.
  end of the crash report.
  A side comment:
  Them are 56 reported problems, and none of them have solutions. If I go through each problem report and check for solutions, about 80% of the times I ask myself to send to Microsoft for more information about the problem and I click on send, but I always get the following:
  [Window title]
  Incident reports

  [Main instruction]
  Problem connecting to the Windows error reporting service

  [Content]
  Some of the reports can not be uploaded to the Windows error reporting service. Please try again later.

  [Close] »
  I tried several times with the same result, that is, the details of the problem which has need of Microsoft is not be received.  To this end, the problem will not be found.
  Thanks much for any help.
  Manny
  P.S. I'll never upgrade a Windows operating system.  My recommendation for anyone who is planning to upgrade to Windows 7 is to try first on a dual boot using the free download.  If it works for you, consider yourself lucky and buy the upgrade.  If it does not, then remove Windows 7 and stay with your old system.

  Please check your RAM for errors (use memtest86 + to test). "A programmer is just a tool that converts the caffeine in code" Deputy CLIP - http://www.winvistaside.de/

• Stop: 0 x 000000f4 (0 x 00000003, 0x89d114338, 0x89d144AC, 0x8060577E)

  What I quoted above... a few times with the same code, change environment appears... Often, my computer shows blue screen whenever I start my computer... I have no virus in my computer... and not installed any software and everything I installed the last, I even uninstalled, but my problem not solved...

  Hi AslamMohammed,

  CRITICAL_OBJECT_TERMINATION bug control has a value of 0x000000F4. This indicates that a process or thread crucial to system operation has unexpectedly is released or ended.

  Follow the steps listed in the article given below to resolve this issue:

  Bug Check 0xF4: CRITICAL_OBJECT_TERMINATION

  Additional reference on:

  Connect a HDD mode single slave led to the shutdown of the system during recovery from sleep mode

• Displaying the right information to get a BSOD error help

  When your computer crashes and displays a blue screen there are often very valuable information about the photo that will allow users to help you solve your problem and to know what is causing this blue screen appears.

  Looking at the image at the end of the article you will see two sections highlighted, you will always want to post this information in your forum thread when looking for help she will be the most critical part of troubleshooting. The top tells us what's happening and said background where it goes to. We have just responded to two of the most important issues when you try to solve a problem.

  What's not?

  Where is the problem isolated to?

  Most of the text is quite annoying, but if that's important to you then it may be important for us. We have all seen what looks like a BSOD, but we do not know what your BSOD.

  There are more important questions that you can answer that will help your troubleshoot BSOD error message.

  1. What is your system brand and model? We know that you have an HP computer, but there are tons of computers. We need to know your specific model to ensure you use the appropriate drivers and we recommend the proper drivers.
  2. What is your version of Windows and the Service pack?
  3. Are you running a 64 bit or 32 bit OS?
  4. What is your Internet browser and version?
  5. Does your system use IDE or SATA disk drives?
  6. What virus protection software and current malicious software do you use? Is up to date?
  7. The issue occurred after an interruption of the power supply as an abnormal termination or power failure?
  8. What has changed recently?
  9. Does this happen often you can effectively reproduce the problem? If you can easily reproduce what steps can you take to reproduce the problem.

  Here is a list of the most common mistakes of the BSOD you can see

  • Stop 0 x 00000003 UNSYNCHRONIZED_ACCESS
  • Stop 0x0000000A IRQL_NOT_LESS_OR_EQUAL
  • Stop 0x0000001E KMODE_EXCEPTION_NOT_HANDLED
  • Stop 0 x 00000023 FAT_FILE_SYSTEM
  • Stop 0 x 00000024 NTFS_FILE_SYSTEM
  • Stop 0x0000002E DATA_BUS_ERROR
  • Stop 0x0000003F NO_MORE_SYSTEM_PTES
  • Stop 0 x 00000044 MULTIPLE_IRP_COMPLETE_REQUESTS
  • Stop 0 x 00000050 PAGE_FAULT_IN_NONPAGED_AREA
  • Stop 0x0000006B PROCESS1_INITIALIZATION_FAILED
  • Stop 0 x 00000073 CONFIG_LIST_FAILED
  • Stop 0 x 00000074 BAD_SYSTEM_CONFIG_INFO
  • Stop 0 x 00000076 PROCESS_HAS_LOCKED_PAGES
  • Stop 0 x 00000077 KERNEL_STACK_INPAGE_ERROR
  • Stop 0 × 00000079 MISMATCHED_HAL
  • Stop 0x0000007A KERNEL_DATA_INPAGE_ERROR
  • STOP 0x0000007B INACCESSIBLE_BOOT_DEVICE
  • Stop 0x0000007E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
  • Stop 0x0000007F UNEXPECTED_KERNEL_MODE_TRAP
  • Stop 0x0000008E KERNEL_MODE_EXCEPTION_NOT_HANDLED
  • Stop 0x0000009C MACHINE_CHECK_EXCEPTION
  • STOP 0x0000009F DRIVER_POWER_STATE_FAILURE
  • Stop 0x000000BE ATTEMPTED_WRITE_TO_READONLY_MEMORY
  • Stop 0x000000C2 BAD_POOL_CALLER
  • Stop DRIVER_VERIFIER_DETECTED_VIOLATION 0x000000C4
  • Stop 0x000000CA PNP_DETECTED_FATAL_ERROR
  • Stop 0x000000CB DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS
  • Stop 0x000000CE DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
  • STOP 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL
  • Stop 0x000000D5 DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL
  • Stop 0x000000D8 DRIVER_USED_EXCESSIVE_PTES
  • Stop 0x000000DA SYSTEM_PTE_MISUSE
  • STOP 0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER
  • Stop 0x000000ED UNMOUNTABLE_BOOT_VOLUME
  • Stop 0x000000F2 HARDWARE_INTERRUPT_STORM
  • Stop 0x000000F4 CRITICAL_OBJECT_TERMINATION
  • Stop 0x000000FC ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
  • STOP 0x000000FE BUGCODE_USB_DRIVER
  • Stop 0xC0000218 UNKNOWN_HARD_ERROR
  • STOP 0xC000021A STATUS_SYSTEM_PROCESS_TERMINATED
  • Stop 0xC0000221 STATUS_IMAGE_CHECKSUM_MISMATCH
  • STOP 0xC0000244 STATUS_AUDIT_FAILED

  

  This thread is purely an informative thread. If you are experiencing a BSOD error please create a new thread ensure you provide information that questions on this thread.

  While many BSOD errors may be troubleshooting-made the same way, there is an amount of many of them and they should be troubleshoot-carried out on their own.

  If you have anything else you want to add or general BSOD issues then you can post them here, but if you ask about anything that requires real troubleshooting it should be in its own thread.

• XP Home BSOD after return from standby (Standby).

  Here is the data from the Minidump:
  

  Debug version of Microsoft Windows (R) 6.11.0001.404 X 86
  Copyright (c) Microsoft Corporation. All rights reserved.

  Loading dump file [C:\WINDOWS\Minidump\Mini010510-12.dmp]
  The mini kernel dump file: only registers and the trace of the stack are available

  Symbol search path is: SRV * c:\symbols* http://msdl.microsoft.com/download/symbols
  Executable search path is:
  Windows XP Kernel Version 2600 (Service Pack 3) MP (2 processors) free x 86 compatible
  Product: WinNt, suite: TerminalServer personal TerminalServer
  Built by: 2600.xpsp_sp3_gdr. 090804 1435
  Computer name:
  Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
  The debugging session: 21:51:44.500 Mar 5 Jan 2010 (GMT-5)
  System Uptime: 0 days 0:02:15.234
  Loading the kernel symbols
  ...............................................................
  ...................................................
  Loading user symbols
  Loading unloaded module list
  ..........
  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  Use! analyze - v to obtain detailed debugging information.

  Bugcheck F4, {3, 8a 105524, 8060567e, 8a1053b0}

  Unable to get nt! KiCurrentEtwBufferOffset
  Unable to get nt! KiCurrentEtwBufferBase
  Probably caused by: hardware_disk (+ fc)

  Follow-up: MachineOwner
  ---------

  1: kd >! analyze - v
  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  CRITICAL_OBJECT_TERMINATION (f4)
  A process or thread crucial to system operation has unexpectedly left or been
  terminated.
  Several processes and threads are necessary to the functioning of the
  System; When they are finished (for some reason any), the system may not
  function longer.
  Arguments:
  Arg1: 00000003, process
  Arg2: 8a1053b0, object of ends
  Arg3: 8A 105524, name of the process image file
  Arg4: 8060567e, explanatory message (ascii)

  Debugging information:
  ------------------

  Unable to get nt! KiCurrentEtwBufferOffset
  Unable to get nt! KiCurrentEtwBufferBase

  PROCESS_OBJECT: 8a1053b0

  Nom_image: hardware_disk

  DEBUG_FLR_IMAGE_TIMESTAMP: 0

  FAULTING_MODULE: 00000000

  Nom_processus: csrss.exe

  EXCEPTION_RECORD: b730f9d8-(.exr 0xffffffffb730f9d8)
  ExceptionAddress: 75b7b3b9
  ExceptionCode: c0000006 (in page i/o error)
  ExceptionFlags: 00000000
  NumberParameters: 3
  Parameter [0]: 00000000
  Parameter [1]: 75b7b3b9
  Parameter [2]: c000000e
  A paging operation is not to 75b7b3b9, because I/O error c000000e

  EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - the instruction at "0 x % lx 08" referenced memory at "0 x % 08 lx. The required data were not placed in memory due to a State of error / "0 x % 08 lx.

  CUSTOMER_CRASH_COUNT: 12

  DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

  Error_code: (NTSTATUS) 0xc0000006 - the instruction at "0 x % lx 08" referenced memory at "0 x % 08 lx. The required data were not placed in memory due to a State of error / "0 x % 08 lx.

  EXCEPTION_PARAMETER1: 00000000

  EXCEPTION_PARAMETER2: 75b7b3b9

  EXCEPTION_PARAMETER3: c000000e

  IO_ERROR: (NTSTATUS) 0xc000000e - a device which does not exist was specified.

  EXCEPTION_STR: 0xc0000006_c000000e

  FAULTING_IP:
  + fc
  75b7b3b9?              ???

  BUGCHECK_STR: 0xF4_IOERR_C000000E

  FOLLOWUP_IP:
  + fc
  75b7b3b9?              ???

  FOLLOWUP_NAME: MachineOwner

  MODULE_NAME: hardware_disk

  SYMBOL_NAME: + fc

  STACK_COMMAND: kb

  FAILURE_BUCKET_ID: 0xF4_IOERR_C000000E_ + cf

  BUCKET_ID: 0xF4_IOERR_C000000E_ + cf

  Follow-up: MachineOwner
  ---------

  I tried; disconnect all usb drives, updating the drivers of Intel 82801FB/FMB, update drivers from Nvidia 9800GT chipset, disable the write cache on the SATA drive, update the network drivers.

  System works perfectly otherwise. Its own BSOD during the return of the mode standby.

  I solved this problem just: my setup had 2 cd discs using the primary IDE channel and a Sata drive on the 2nd Sata channel.

  I bought the computer used and it was how it has been implemented (and it worked fine in this config without using sleep).

  It turns out that the HD (with the top OS) must be connected on the first channel of Sata (Sata (0) on my Dell) so he can wake up correctly the mode standby.
   
  I just disconnected the Sata round cable and moved to first, then changed the BIOS to reflect this change, and everything's fine.

• A process or thread crucial to system operation has unexpectedly left or came to an end.

  So, if you look at the other question, I asked, you will see that I had a few problems under Windows 7. Now, I'm having almost exactly the same problem after return to windows Vista.

  Twice now, after that immediately turned on the computer and the starting windows, I got the system slows down suddenly and freeze. Previously, in windows 7, this has led to many problems, and ultimately the system was unresponsive and unusable until I reinstalled the operating system. Under vista, the computer actually seems to try to solve the problem, and I am fairing slightly better.

  Earlier, I got a blue screen with the 0x00000F4 error code (I couldn't have the correct amount of 0) and the message that is indicated in the title. Once the computer is restarted, it works very well, and I found it in under the window newspapers/system event viewer:

  The structure of the file system on the volume C: has now been repaired.

  Event ID: 130 Source: Ntfs
  The event data:

  VolumeIdLength 2

  VolumeId C:

  RepairDetail 25008: Startup Repair on 13/04/2010 at 17:45:14:941 26084: remove an entry from index to index the file 0x2c000000004b8a 0x12000000007fa7. 27094: an index entry in the index to the file 0x12000000007fa7 point unused 0x2c000000004b8a. 25009: repair end on 13/04/2010 at 17:45:14:941

  RepairDataLength 136

  RepairData 8A4B000000002C00BB00170006000000000000000000000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

  There is also another warning of the same nature, which seems to be a repair on a different part of the C: drive.
  In addition to this, I see warnings that the following packages (which appear to be updates security) do not apply to my system. The only thing I installed in this time was windbg, so these errors can be that, but I do not. The packages are:
  
  KB979309 and KB978601 (there are four separate warnings for this package)
  In addition, I tried to analyze the minidump created by crushing with windbg. Here's what I got, but I don't know if I was doing it right or not.
  CRITICAL_OBJECT_TERMINATION (f4)

  A process or thread crucial to system operation has unexpectedly left or been

  terminated.

  Several processes and threads are necessary to the functioning of the

  System; When they are finished (for some reason any), the system may not

  function longer.

  Arguments:

  Arg1: 0000000000000003, process

  Arg2: fffffa8007998c10, object of ends

  Arg3: fffffa8007998e48, name of the process image file

  Arg4: fffff80001ee1af0, explanatory message (ascii)

  Debugging information:

  ------------------

  PROCESS_OBJECT: fffffa8007998c10

  Nom_image: csrss.exe

  DEBUG_FLR_IMAGE_TIMESTAMP: 0

  MODULE_NAME: csrss

  FAULTING_MODULE: 0000000000000000

  Nom_processus: csrss.exe

  EXCEPTION_CODE: (Win32) 0x875b7f0 (141932528).

  BUGCHECK_STR: 0xF4_875B7F0

  CUSTOMER_CRASH_COUNT: 1

  DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

  CURRENT_IRQL: 0

  STACK_TEXT:

  "fffffa60 '043351-8 fffff800' 01f5d1e3: 00000000' 00000000'00000003 fffffa80 ' 07998 000000f4 c 10 fffffa80 ' 07998e48: nt! KeBugCheckEx

  "fffffa60 '043351b 0 fffff800' 01e762c8: fffffa80 '0875b7f0 fffffa80' 0875b7f0 fffffa60 ' 04335 c 20 fffffa60 ' 04335a 40: nt! PspCatchCriticalBreak + 0 x 93

  fffffa60 '043351f0 fffff800' 01eaa190: fffffa80 '0875b7f0 00000000' 00000008 fffffa60'04335 c 20 00000000'00000008: nt! : NNGAKEGL: 'string' + 0x110f6

  "fffffa60 ' 04335240 fffff800' 01c5def3: fffffa80 ' 07998 c 10 fffffa80 ' 0875b7f0 fffffa60 '04335320 fffffa60' 04335c 20: nt! NtTerminateProcess + 0xd8

  fffffa60 '043352-0 fffff800' 01c5e400: fffff800' fffffa60 '04335b 78 fffffa60' 01cbe2ed fffffa60'04335 04335ca 0 c 20: nt! KiSystemServiceCopyEnd + 0x13

  fffffa60 ' 04335438 fffff800' 01cbe2ed: fffffa60 '04335 b 78 fffffa60' fffffa60'04335 04335 ca 0 c 20 00000000'003913 0 d: nt! KiServiceLinkage

  fffffa60 ' 04335440 fffff800' 01c5e2a9: fffffa60'04335 b 78 00000000' 0001cb88 fffffa60'04335 20 00000000'003919 d 8 c: nt! : FNODOBFM: 'string' + 0x2935c

  fffffa60 '04335-40 fffff800' 01c5d0a5: 00000000'00000000 00000000' 003cf8a0 00000000'00000001 00000000' 0001cb88: nt! KiExceptionDispatch + 0xa9

  fffffa60'04335 c 20 00000000' 77ba347e: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: nt! KiPageFault + 0x1e5

  00000000' 003912f0 00000000'00000000: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: 0x77ba347e

  STACK_COMMAND: kb

  FOLLOWUP_NAME: MachineOwner

  FAILURE_BUCKET_ID: X64_0xF4_875B7F0_IMAGE_csrss.exe

  BUCKET_ID: X64_0xF4_875B7F0_IMAGE_csrss.exe

  Follow-up: MachineOwner
  Thanks for any help!

  Good job!  I am pleased that chkdsk option included in my post the primary problem solved oiriginal (if only temporarily).  It doesn't sound like your hard drive may be dying (or close very dead).  We should do a complete diagnostic of her test to see what it shows.

  To test your hard drive, check the manufacturer and then get the diagnostic utility of:http://www.techsupportforum.com/hardware-support/hard-drive-support/302602-hard-drive-diagnostic-utilities.html.  If she failed the test, replace it.  If she passes the test, there's probably nothing wrong with it that can't hold off for a while (but the corruption on the hard disk is a sign that there is something wrong with the hard drive, even if she meets this criterion).

  Csrss.exe crash almost certainly has not caused the problems of corruption on your hard drive - what is much more likely a hardware problem (but the above will be)- and it is more likely that corruption caused the crash.

  I see no harm in installing the fix - although I do not know it will not solve the problem (especially if you aren't really using console applications or it occurs not only when you close).  Yes, it seems to apply to your situation in a certain way and can solve this problem, but I really think that the underlying issue is the hard drive itself.

  I hope this helps.

  Good luck!

  Lorien - MCSA/MCSE/network + / has + - if this post solves your problem, please click the 'Mark as answer' or 'Useful' button at the top of this message. Marking a post as answer, or relatively useful, you help others find the answer more quickly.

• Blue error screen when indexing the files on Vista computer

  Original title: Problem Event Name:_BlueScreen__ OS Version:_6.0.6002.2.2.0.768.3__ Locale ID:_1033__

  BCCode: f4

  BCP1: 00000003

  BCP2: 872E2D90

  BCP3: 872E2EDC

  BCP4: 81E33710

  OS version: 6_0_6002

  Service Pack: 2_0

  Product: 768_1

  Before I tear off my hard drive and throw it out the window, please tell me I can recover from this error. The above error when I try to rebuild my Index. I regularly get messages "index has stopped working". I select the indexer rebuild to the original configuration. He tried to do, but stopped after the indexing of files about 1700, restarted, and then returned with the above event. I had several problems with my OS for a few days. I have run chkdsk and chkdsk/r several times. I use Norton 360, analysis tell me that all files are up to date, Windows update is performed regularly and is up to date. I was initially received an error "parameter has exceeded its normal range" train SMART. I disabled this option considered, but service to have problems with my system. Everything seems to work okay in safe mode, where I am now. I am at a loss. I have a recovery partition on my drive, but did not know what options to use. I have the installation CD Vista too, but avoided to reinstall, have done this before for another question. For any help or suggestion will be greatly appreciated. Please see my other post earlier this week, I was only partially successful with this process. Thank you very much!

  Hello

  If a PC remove all power to the system:

  Check and replace the cards, memory and cables (at both ends) actually remove and replace
  -do not just tight. Memory could be the problem, so if you have more than 1 stick swap
  in and out to see if the problem follows a stick or try the new memory. How to test
  memory in the next message.

  -------------------------------------------------------------------------------------------------------

  Pick up the pieces after a computer crash - includes "what to do if Windows doesn't.
  start correctly'.
  http://Windows.Microsoft.com/en-us/Windows-Vista/picking-up-the-pieces-after-a-computer-crash

  Check this thread for more information using BlueScreenView, MyEventViewer and other methods
  to troubleshoot the BlueScreens - top 3 responses (+ 1 other).

  http://social.answers.Microsoft.com/forums/en-us/vistarepair/thread/3deab2fa-4000-4136-8c78-a3d22b1db009

  We can analyze the minidumps if make you it available to the SkyDrive or another file
  sharing sites (such as MediaFire). If you have problems to download the copy of minidumps
  for the office or in the Documents folder and download them from there.

  ZIP or download the content of the C:\Windows\minidump

  Use SkyDrive to upload collected files.
  http://social.technet.Microsoft.com/forums/en-us/w7itproui/thread/4fc10639-02dB-4665-993a-08d865088d65

  ================================================================

  BCCode: F4 0x000000F4

  Check and reinstall the cards memory and cables (at both ends where possible) actually remove and
  replace - do not just tight. On a laptop computer on all you can do is reinstall the memory and possibly check
  the contacts/connection to the hard drive. Memory could be the problem, so if you have more than 1
  stick swap them in and out to see if the problem follows a stick or try the new memory. Antivirus/anti-
  spyware/security programs have been known to cause or have a role in this matter.

  More general patch updates day and low level chipset BIOS drivers and other software to control.
  Also check wiring for hard drive.

  ======================================================

  Bug Check 0xF4: CRITICAL_OBJECT_TERMINATION

  CRITICAL_OBJECT_TERMINATION bug control has a value of 0x000000F4. This indicates that a process or thread crucial to system operation has unexpectedly is released or ended.

  Important info if you received a STOP Code

  If you received a blue error screen, or a stop code, the computer stopped abruptly to protect against data loss. A hardware device, its driver or software might have caused this error. If your copy of Windows is shipped with your computer, contact your computer manufacturer. If you purchased Windows separately from your computer, Microsoft provides support. To find contact information for Microsoft or the manufacturer of your computer, Contact Support.

  If you have experience with computers and try to recover from this error, follow the steps in the Microsoft article solution STOP (blue screen) errors in Windows.

  These actions could prevent a mistake like this does not happen:

  1. Download and install updates for your computer from Windows Update device drivers.
  2. Scan your computer for computer viruses.
  3. Check your hard drive for errors.

  CRITICAL_OBJECT_TERMINATION parameters

  The following settings are displayed on the blue screen.

  Parameter	Description
  1	The Terminal object type: 0 x 3 : Process of 0 x 6 : Thread
  2	The endpoint object
  3	The name of the process image file
  4	Pointer to a string ASCII containing an explanatory message

  Cause

  Several processes and threads are necessary to the functioning of the system. As they are completed for some reason, the system can no longer function.

  BCCode: F4 0x000000F4<-- read="" this="">
  * 1241.html http://www.faultwire.com/solutions-fatal_error/A-process-or-thread-crucial-to-System-Operation-has-0x000000F4-

  -----------------------------------------------------------------------------

  Look in the Event Viewer to see if something is reported on those.
  http://www.computerperformance.co.UK/Vista/vista_event_viewer.htm

  MyEventViewer - free - a simple alternative in the standard event viewer
  Windows. TIP - Options - Advanced filter allows you to see a time rather
  of the entire file.
  http://www.NirSoft.NET/utils/my_event_viewer.html

  Here are a few ways to possibly fix the blue screen issue. If you could give the blue screen
  info that would help. Such as ITC and 4 others entered at the bottom left. And all others
  error information such as codes of STOP and info like IRQL_NOT_LESS_OR_EQUAL or PAGE_FAULT_IN_NONPAGED_AREA and similar messages.

  As examples:

  BCCode: 116
  BCP1: 87BC9510
  BCP2: 8C013D80
  BCP3: 00000000
  BCP4: 00000002

  or in this format:

  Stop: 0 x 00000000 (oxoooooooo oxoooooooo oxoooooooo oxooooooooo)
  Tcpip.sys - address blocking 0 x 0 00000000 000000000 DateStamp 0 x 000000000

  It is an excellent tool for displaying the blue screen error information

  BlueScreenView scans all your minidump files created during ' blue screen of the.
  death ' crashes and displays information about all accidents of a table.
  Free
  http://www.NirSoft.NET/utils/blue_screen_view.html

  BlueScreens many are caused by drivers of old or damaged, in particular the video drivers
  However, there are other causes.

  You can do mode if necessary safe or the Vista DVD command prompt or
  Options recovery if your system is installed by the manufacturer.

  This tells you how to access the System Recovery Options and/or a Vista DVD
  http://windowshelp.Microsoft.com/Windows/en-us/help/326b756b-1601-435e-99D0-1585439470351033.mspx

  You can try a system restore to a point before the problem started when one exists.

  How to make a Vista system restore
  http://www.Vistax64.com/tutorials/76905-System-Restore-how.html

  -------------------------------------------------------------------------

  Start - type this into the search-> find COMMAND to top box and RIGHT CLICK-
  RUN AS ADMIN

  Enter this at the command prompt - sfc/scannow

  How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe)
  program generates in Windows Vista cbs.log
  http://support.Microsoft.com/kb/928228

  The log can give you the answer if there is a corrupted driver. (Does not work
  tell all possible driver issues).

  Also run CheckDisk, so we cannot exclude as much as possible of the corruption.

  How to run the check disk at startup in Vista
  http://www.Vistax64.com/tutorials/67612-check-disk-Chkdsk.html

  -------------------------------------------------------------------------

  Often drivers up-to-date will help, usually video, sound, network card (NIC), WiFi, part 3
  keyboard and mouse, as well as of other major device drivers.

  Look at the sites of the manufacturer for drivers - and the manufacturer of the device manually.
  http://pcsupport.about.com/od/driverssupport/HT/driverdlmfgr.htm

  How to install a device driver in Vista Device Manager
  http://www.Vistax64.com/tutorials/193584-Device-Manager-install-driver.html

  How to disable automatic driver Installation in Windows Vista - drivers
  http://www.AddictiveTips.com/Windows-Tips/how-to-disable-automatic-driver-installation-in-Windows-Vista/
  http://TechNet.Microsoft.com/en-us/library/cc730606 (WS.10) .aspx

  -------------------------------------------------------------------------

  How to fix BlueScreen (STOP) errors that cause Windows Vista to shut down or restart
  quit unexpectedly
  http://support.Microsoft.com/kb/958233

  Troubleshooting, STOP error blue screen Vista
  http://www.chicagotech.NET/Vista/vistabluescreen.htm

  Understanding and decoding BSOD (blue screen of death) Messages
  http://www.Taranfx.com/blog/?p=692

  Windows - troubleshooting blue screen errors
  http://KB.wisc.edu/page.php?id=7033

  -------------------------------------------------------------------------

  In some cases, it may be necessary.

  The Options or Vista recovery disk Startup Repair

  How to do a startup repair
  http://www.Vistax64.com/tutorials/91467-startup-repair.html

  This tells you how to access the System Recovery Options and/or a Vista DVD
  http://windowshelp.Microsoft.com/Windows/en-us/help/326b756b-1601-435e-99D0-1585439470351033.mspx

  I hope this helps.

  Rob Brown - Microsoft MVP<- profile="" -="" windows="" expert="" -="" consumer="" :="" bicycle="" -="" mark="" twain="" said="" it="">

• At the start of some games, I get a BSOD 0x000000f4

  Hi every 1

  Was the first time that I had this problem with Call of duty: modern warfare, now all of a sudden, I got it on testdrive unlimeted!

  I never used to have any problem! But anyway, the problem in detail.

  I have updated all drivers and all the stuff, reinstalled the games and every thing. So, when I start the game, it goes black and then comes up with the blue screen of death (BSOD). It is said that as a critical process or thread system was completed or something like that. The error code is 0x000000f4 (0 x 00000003, varies, varies, varies)

  Here are the things to dump:

  version.txt:

  Windows NT Version 6.0 Build: 6002 SP2

  Product (0 x 2): Windows Vista (TM) Home Basic

  Edition: HomeBasic

  BuildString: 6002.18209.x86fre.vistasp2_gdr.100218 - 0019

  Flavor: Multiprocessor Free

  Architecture: X 86

  LCID: 1033

  SysData.XML:

  http://www.mediafire.com/?75sez5eg61uzos3

  Mini072210 - 01.dmp:
  http://www.mediafire.com/?8sn3yec7jkaesj8
  Thanks for any help provided!
  Jon

  Hi Jon,

  you get the following verification of bug: 0xF4 - CRITICAL_OBJECT_TERMINATION: This indicates that a process or thread crucial to system operation has unexpectedly left or came to an end.

  The debugger says, wininit.exe led by gamexl.exe . What I see, it's spyware.

  Run this tool and scan your PC for spyware:

  http://www.Malwarebytes.org/MBAM.php

  André

  "A programmer is just a tool that converts the caffeine in code" Deputy CLIP - http://www.winvistaside.de/

• T500 - BSOD - Win XP

  Hello

  I have a T500 (1 month), he has Win XP on it. He began to give the BSOD. Please fnd below the minidump, suggestions are welcome. Thank you!

  Debug version of Microsoft Windows (R) 6.11.0001.404 X 86
  Copyright (c) Microsoft Corporation. All rights reserved.

  Loading dump file [C:\WINDOWS\Minidump\Mini051609-01.dmp]
  The mini kernel dump file: only registers and the trace of the stack are available

  Symbol search path is: C:\WINDOWS\Symbols
  Executable search path is: C:\WINDOWS\ServicePackFiles\i386
  Windows XP Kernel Version 2600 (Service Pack 3) MP (2 processors) free x 86 compatible
  Product: WinNt, suite: TerminalServer SingleUserTS
  By: 2600.xpsp.080413 - 2111
  Computer name:
  Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
  The debugging session: 01:40:38.703 sat May 16, 2009 (GMT-7)
  System Uptime: 0 days 0:43:41.295
  Loading the kernel symbols
  ...............................................................
  ................................................................
  .......................................................
  Loading user symbols
  Loading unloaded module list
  ..................
  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  Use! analyze - v to obtain detailed debugging information.

  Bugcheck F4, {3, 8a4f2b30, 8a4f2ca4, 805d 2970}

  Unable to get nt! KiCurrentEtwBufferOffset
  Unable to get nt! KiCurrentEtwBufferBase
  Probably caused by: hardware_disk (+ fc)

  Follow-up: MachineOwner
  ---------

  0: kd >! analyze - v
  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  CRITICAL_OBJECT_TERMINATION (f4)
  A process or thread crucial to system operation has unexpectedly left or been
  terminated.
  Several processes and threads are necessary to the functioning of the
  System; When they are finished (for some reason any), the system may not
  function longer.
  Arguments:
  Arg1: 00000003, process
  Arg2: 8a4f2b30, object of ends
  Arg3: 8a4f2ca4, name of the process image file
  Arg4: 805d 2970, explanatory message (ascii)

  Debugging information:
  ------------------

  Unable to get nt! KiCurrentEtwBufferOffset
  Unable to get nt! KiCurrentEtwBufferBase

  PROCESS_OBJECT: 8a4f2b30

  Nom_image: hardware_disk

  DEBUG_FLR_IMAGE_TIMESTAMP: 0

  FAULTING_MODULE: 00000000

  Nom_processus: csrss.exe

  EXCEPTION_RECORD: 9d6209d8-(.exr 0xffffffff9d6209d8)
  ExceptionAddress: 75b900d1
  ExceptionCode: c0000006 (in page i/o error)
  ExceptionFlags: 00000000
  NumberParameters: 3
  Parameter [0]: 00000008
  Parameter [1]: 75b900d1
  Parameter [2]: c0000056
  A paging operation is not to 75b900d1, because I/O error c0000056

  EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - the instruction at "0 x % lx 08" referenced memory at "0 x % 08 lx. The required data were not placed in memory due to a State of error / "0 x % 08 lx.

  CUSTOMER_CRASH_COUNT: 1

  DEFAULT_BUCKET_ID: DRIVER_FAULT

  Error_code: (NTSTATUS) 0xc0000006 - the instruction at "0 x % lx 08" referenced memory at "0 x % 08 lx. The required data were not placed in memory due to a State of error / "0 x % 08 lx.

  EXCEPTION_PARAMETER1: 00000008

  EXCEPTION_PARAMETER2: 75b900d1

  EXCEPTION_PARAMETER3: c0000056

  IO_ERROR: A non close operation (NTSTATUS) 0xc0000056 - was requested of an object file with a suspended deletion.

  EXCEPTION_STR: 0xc0000006_c0000056

  FAULTING_IP:
  + fc
  75b900d1?              ???

  BUGCHECK_STR: 0xF4_IOERR_C0000056

  FOLLOWUP_IP:
  + fc
  75b900d1?              ???

  FOLLOWUP_NAME: MachineOwner

  MODULE_NAME: hardware_disk

  SYMBOL_NAME: + fc

  STACK_COMMAND: kb

  FAILURE_BUCKET_ID: 0xF4_IOERR_C0000056_ + cf

  BUCKET_ID: 0xF4_IOERR_C0000056_ + cf

  Follow-up: MachineOwner
  ---------

  0: kd > lmvm hardware_disk
  start end module name
  0: kd >! ffffffff8a4f2b30 process 3
  GetPointerFromAddress: unable to read from 80562134
  PROCESS 8a4f2b30 SessionId: no Cid: 05b 8 Peb: 7ffdb000 ParentCid: 056c
  DirBase: 0b 380060 ObjectTable: e1a1b928 HandleCount:
  Image: csrss.exe
  VadRoot 83ac0a60 Vads Clone 0 403 private 185. Updated the 4878. locked 0.
  DeviceMap e1009200
  Token e1cd9030
  ReadMemory error: could not get nt! KeMaximumIncrement value.
  ffdf0000: cannot get shared data
  ElapsedTime 00:00:00.000
  Get_user_time 00:00:00.000
  KernelTime 00:00:00.000
  QuotaPoolUsage [PagedPool] 103900
  QuotaPoolUsage [NonPagedPool] 8560
  Working Set sizes (now, min, max) (1107, 50, 345) (4428KB, 200 KB, 1380KB)
  PeakWorkingSetSize 1209
  VirtualSize 30 MB
  PeakVirtualSize 53 Mb
  PageFaultCount 9915
  MemoryPriority BACKGROUND
  BasePriority 13
  493 dedicated

  Error in reading nt! _ETHREAD @ 89b35c88

  0: kd > .exr 0xffffffff9d6209d8
  ExceptionAddress: 75b900d1
  ExceptionCode: c0000006 (in page i/o error)
  ExceptionFlags: 00000000
  NumberParameters: 3
  Parameter [0]: 00000008
  Parameter [1]: 75b900d1
  Parameter [2]: c0000056
  A paging operation is not to 75b900d1, because I/O error c0000056
  0: kd > lmvm hardware_disk
  start end module name

  Update - my computer came with Sp2, I applied all updates to windows. He lied to me. I uninstalled Sp3. It has been a week since my last BSOD. Is tested, if all goes well, will restore the factory settings and disable the updates of Windows (at least for IE8 and SP3).

  my configuration:

  T500

  Intel Core 2 Duo - 2.53 GHz

  4 GB of Ram (XP 32 bit sees only 3)

  250 GB

  fingerprint reader

  chip card reader

  ATI Radeon 3650

  WSXGA +.

  Nano Logitech Wireless mouse