TechSpot

  1. TechSpot is dedicated to computer enthusiasts and power users. Ask a question and give support. Join the community here.
    Ask a Question
    See Latest Posts
    TechSpot is dedicated to computer enthusiasts and power users.
    Ask a question and give support.
    Join the community here, it only takes a minute.
    Dismiss Notice

BSoD - On Windows Startup (0x00000F4)

JIME108
By JIME108
Jan 28, 2010
  1. The other night I went to turn my computer on and after the loading screen for Windows Vista it had the BSoD..

    The error is 0x00000F4 (I don't know the other parameters)

    I cant get to the Minidumps or access any files or programs because my computer does not even load into the OS.

    I have tried to repair Windows using the disc and trying a system restore but said it could not repair this problem nor do the system restore.
    The repair says it is a driver or update that is stopping Windows from starting correctly.

    I have moved the HDD to another PC and still does not work so I know that it is Windows that is playing up not any hardware.

    I ran the Memory Diagnostics Test as well and that also says that a driver or update that is stopping Windows from starting correctly.

    I also have no Viruses/Worms/Trojans on my computer at all.

    Before I shut it down last was an update waiting to restart my PC, so I think this update has screwed up a driver or something and will not let Windows start.

    As I said I cannot access any files due to it does not run into the OS so I am stuck and really do not want to format and reinstall Windows.
     
    Jan 28, 2010
    #1
  2. Route44

    Route44 TechSpot Ambassador Posts: 11,979   +71

    0x000000F4: CRITICAL_OBJECT_TERMINATION
    One of the many processes or threads crucial to system operation has unexpectedly exited or been terminated. As a result, the system can no longer function. Specific causes are many, and often best resolved by a careful history of the problem and the circumstances of the error message. One user, who experienced this on return from Standby mode on Win XP SP2, found the cause was that Windows was installed on a slave drive.

    You may need to do a reformat but before doing so slave this harddrive in another system (you said you put the harddrive in another system but I din't read anything about slaving it).

    From the PCs main drive access this harddrive and back up all important items. Then run a harddrive diagnostics because even though this error points to drives there may still be issues with the disk itself.
     
    Jan 28, 2010
    #2
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...