BSOD - Please Insert Boot Drive or Restart the System

Thanks zigzag

I shall await for another BSOD, hopefully it doesn't occur, but shall post it straight away if it does.

I have re-checked all drivers are up to date as well.

Also, I did include a bsod from late nov last year in a post above that one, all of which occur randomly while I'm on chrome and itunes, and all of which result in the same insert boot disk message.

Cheers :)

Hey happened again,

I know you asked for multiple BSODS but this is the 5th time this has happened

Here it is,

Hope that this one can shed some light on wth is causing these issues.

Cheers~

Bump :)

Code:

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


Loading Dump File [F:\BSODDmpFiles\Sangdrax\021312-21356-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.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0300c000 PsLoadedModuleList = 0xfffff800`03251670
Debug session time: Sun Feb 12 19:40:54.387 2012 (GMT-7)
System Uptime: 0 days 0:24:01.199
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa801071d200, fffffa801071d4e0, fffff8000338c8b0}

Probably caused by : wininit.exe

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

4: 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: fffffa801071d200, Terminating object
Arg3: fffffa801071d4e0, Process image file name
Arg4: fffff8000338c8b0, Explanatory message (ascii)

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


PROCESS_OBJECT: fffffa801071d200

IMAGE_NAME:  wininit.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: wininit

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  wininit.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

BUGCHECK_STR:  0xF4_IOERR

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`09d779c8 fffff800`034135e2 : 00000000`000000f4 00000000`00000003 fffffa80`1071d200 fffffa80`1071d4e0 : nt!KeBugCheckEx
fffff880`09d779d0 fffff800`033c099b : ffffffff`ffffffff fffffa80`10884950 fffffa80`1071d200 fffffa80`1071d200 : nt!PspCatchCriticalBreak+0x92
fffff880`09d77a10 fffff800`03340448 : ffffffff`ffffffff 00000000`00000001 fffffa80`1071d200 0000007f`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6
fffff880`09d77a60 fffff800`03087ed3 : fffffa80`1071d200 00000000`c0000006 fffffa80`10884950 00000000`00000026 : nt!NtTerminateProcess+0xf4
fffff880`09d77ae0 00000000`76f715da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`004af828 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f715da


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_wininit.exe

BUCKET_ID:  X64_0xF4_IOERR_IMAGE_wininit.exe

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

A windows system process was terminated unexpectedly. Possible causes are hard disk errors... System file corruption... Viruses... Lack of Windows updates... Drivers...

Go through the following list, and if your stability is not improved after a step, post the crash reports and proceed to the next step.

• 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
  
  
  
• Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.
  
  
  
• Scan for viruses with a full scan using the free version (do not start the trial) of Malwarebytes : Free anti-malware, anti-virus and spyware removal download and see the Good and Free system security combination. for better security steps and scanning tools.
  
  
  
• Install all Windows Updates.
  
  
  
• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. Run Driver Verifier
  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.
  
  Thanks to zigzag3143 for contributing to the Verifier steps.
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.

Woah woah woah big error now!

Have just run the SFC command just now when I got an I/O memory error:
Explorer.exe - the instruction at ... Referenced memory at ...
The instruction was not placed into memory because of an IO error status 0xc000000e

And

IAStorIcon.exe
Has generated an exception that could not be handled
Process ID 0x9dc (2524) thread ID 0xb98 (2968)

The SFC scan came back with no integrity violations or errors.

Do not know why these errors occurred ;_;

Yea
Came back clean with no errors or corrupt uhh segments? detected.
(Forgot the right term :P)
If you want I took photos of the two error messages that came up so I can be more accurate with the code etc if that'll help?

Ohhhhhhhh just read that post in the quote
So would it be a good idea to test a hdd drive in place of the SSD?
And I know this may sound like a stupid question but how do I check the SSD's firmware is up to date etc?
It's a WD SSD "Black" vertex 3 I believe :)

Yes! Sorry I have no idea why I always say its WD
Yes it is OCZ my bad!
So how do I check to see if the firmware needs updating?
I thought I had and it was correct before, however now I am not so sure I did it correctly :S
Is there a guide or set of steps I can check to make sure I was right first time round? Or should I update the firmware from the OCZ link you supplied anyways?