0x000000f4 Upon Boot Up After Re-Imaging SSD

Hello,

System Specs:
Windows 7 Ultimate x64
OCZ Vertex 4 SSD (Windows installation that was being re-imaged)
OCZ Agility 3 SSD (windows installation that still functions)
Seagate 2TB drive as storage

Story:
OCZ just came out with there linux bootable firmware flash tool, so I made an image using Acronis True Image Home 2011 at normal compression and stored it on my storage drive. I then popped in the linux bootable firmware disc and securely erased the vertex 4 and used the bootable acronis tool to re-image the drive. Upon passing the Windows loading screen, I get the error.

STOP: 0x000000f4 CRITICAL_OBJECT_TERMINATION

Steps taken to attempt recovery:
Use the windows repair disc to repair the installation
Boot into windows on my Agility and run chkdsk /f /r and sfc /scannow on the vertex. Chkdsk found some errors on its run through, but when trying to log onto the vertex, I get the same error.
I securely erased again (Such a waste of writes) and made sure to go into Windows and set the offset and format the drive and attempt another reimage, but no luck.

Using BlueScreenView the following items are highlighted in red:

ntoskrnl.exe ntoskrnl.exe+406882 fffff800`03002000 fffff800`035ea000 0x005e8000 0x4f76721c 3/30/2012 9:55:24 PM Microsoft® Windows® Operating System NT Kernel & System 6.1.7601.17803 (win7sp1_gdr.120330-1504) Microsoft Corporation B:\Windows\system32\ntoskrnl.exe

serial.sys serial.sys+2406a78 fffff880`035e2000 fffff883`035ff000 0x000000030001d000 0x4a5bcaa8 7/13/2009 7:00:40 PM Microsoft® Windows® Operating System Brotehr Serial I/F Driver (WDM) 1.0.1.6 (vbl_wcp_d2_drivers.060801-2007) Brother Industries Ltd. B:\Windows\system32\drivers\serial.sys

and the dump file listing is:

060912-21340-01.dmp 6/9/2012 2:55:49 AM CRITICAL_OBJECT_TERMINATION 0x000000f4 00000000`00000003 fffffa80`0ee85b30 fffffa80`0ee85e10 fffff800`03380510 serial.sys serial.sys+2406a78 Brotehr Serial I/F Driver (WDM) Microsoft® Windows® Operating System Brother Industries Ltd. 1.0.1.6 (vbl_wcp_d2_drivers.060801-2007) x64 ntoskrnl.exe+7f1c0 B:\Windows\Minidump\060912-21340-01.dmp 8 15 7601 299,769

In my Windows on the agility, I am able to access the vertex drive just fine, read/write, etc.

Any assistance on this would be greatly appreciated.

Using Windows on the agility, can you upload the .dmp files to us? They would be in the [drive_letter]:\Windows\Minidump folder. You will need to copy and paste them somewhere else since they are protected by Windows permissions for security reasons: Dump Files - Upload to SevenForums


Also, have you tried doing a power cycle of the SSD? The following steps should be carried out and take ~1 hour to complete.

1. Power off the system.
2. Remove all power supplies (ac adapter then battery for laptop, ac adapter for desktop)
3. Hold down the power button for 30 seconds to close the circuit and drain all components of power.
4. Reconnect all power supplies (battery then ac adapter for laptop, ac adapter for desktop)
5. Turn on the system and enter the BIOS (see your manual for the steps to enter the BIOS)
6. Let the computer remain in the BIOS for 20 minutes.
7. Follow steps 1-3 and physically remove the SSD from the system by disconnecting the cables for a desktop or disconnecting the drive from the junction for a laptop.
8. Leave the drive disconnected for 30 seconds to let all power drain from it.
9. Replace the drive connection(s) and then do steps 4-8 again.
10. Repeat steps 1-4.
11. Start your computer normally and run Windows.

The above steps were a result of: Why did my SSD "disappear" from my system? - Crucial Community

While that may not be your drive, a power cycle should be the same on all SSD drives. See how the system responds after the SSD power cycle.

I will try those steps. In the mean time, here is the minidump.

Thank you

No luck on the power cycling, unfortunately.

The .dmp file primarily indicates hard disk problems. This could mean hard disk corruption, bad sectors, a failing hard disk, Windows files or registry corruption, viruses, or memory problems.

• If you are overclocking any hardware, please stop.
  
  
• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log (you may need to search for wininit instead of chkdsk).
  For any drives that do not give the message:
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.
  
  
• Run the short and long tests with SeaTools for HDDs.
  SeaTools for Windows
  
  SeaTools for DOS
  
  
• 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.
  
  
  
• Check Windows for corruption. Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of SFC /SCANNOW Command - System File Checker to provide us with the sfcdetails.txt file if errors occur.
  
  
• Download and install Malwarebytes, update it, do not start the free trial, and then run a full scan. Also run a full scan with your antivirus software installed on your system. If you do not have antivirus software installed, see the Good and Free system security combination. for better security steps and scanning tools. Make sure to update the security software before running the full scan.
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
     Warning

  Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.

Thank you for the steps to try. I have reduced the memory clock on my gpu back to stock and will try to boot into that installation. I'll try the other steps and knock each one out.

Good work on removing the overclocks. Let us know what you find with the diagnostics.