Windows 7: BSOD - Please Insert Boot Drive or Restart the System

Hi, I have just built a new computer (about 3 months ago now).



It has been working fine since then, however about a month ago I had a BSOD and it restarted on its own and works again.

I had another two days ago now as well.

The unusual thing is after it restarts I get a white error message saying "Please insert the boot drive or restart the system", and after restarting, it works perfectly again.

I am unsure what would be the cause of this, and believe that my mem, hdd's and gfx card are all working fine following a memtest.

Drivers are up to date, checked again yesterday.

My system specs are:

Windows 7 Professional 64 Bit
P8z68-V Pro Asus Mobo
Quad Core i7
GTX580 Matrix Graphics Card
WD 1tb HDD
120MB SSD
16gb (4x4x4x4) Ram - 2133mhz (G Skill Rip-Saw)

This is the only OS ever installed on this system.

Although it appears to be a system for OCing, I have not done any of this, and do not believe it to be an issue with power supply/Voltage.

I have tried unsuccessfully to replicate the BSOD situation.

Please see attached .dmp file compressed .rar.

Many thanks and hopefully someone will be able to shed some light on this.
(PS: I am on my computer right now and it is working so I am unsure what could be the issue).

This was related to an I/O (input/output) error. Please run a chkdsk to verify the HD's condition

A- CHKDSK /R /F:

Quote:

Run CHKDSK /R /F from an elevated (Run as administrator) Command Prompt.

Do this for each hard drive on your system.

When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter.

Then reboot and let the test run.

It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors.

See "CHKDSK LogFile" below in order to check the results of the test.

B- Elevated Command Prompt:

Quote:

Go to Start and type in "cmd.exe" (without the quotes)

At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

C-CHKDSK LogFile:

Quote:

Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter

Expand the Windows logs heading, then select the Application log file entry.

Double click on the Source column header.

Scroll down the list until you find the Chkdsk entry (wininit for Windows 7) (winlogon for XP).

Copy/paste the results into your next post.

Here are the results of the Chkdsk scan.

I hope I did it all correctly however one issue arose when trying to run the chkdsk on my e: drive (which is a SSD) - the cmd prompts would say that drive must be disconnected or something along those lines in order to run the dskchk.

Anyways, on that drive is not much, its simply for storage (just anime and music).
The main drive is C: which has on it windows operating system and ALL program files.

Here are the results:

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
130304 file records processed. File verification completed.
193 large file records processed. 0 bad file records processed. 2 EA records processed. 76 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
179468 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
130304 file SDs/SIDs processed. Cleaning up 300 unused index entries from index $SII of file 0x9.
Cleaning up 300 unused index entries from index $SDH of file 0x9.
Cleaning up 300 unused security descriptors.
Security descriptor verification completed.
24583 data files processed. CHKDSK is verifying Usn Journal...
37367208 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
130288 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
10812466 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.

117115903 KB total disk space.
73566268 KB in 103658 files.
63136 KB in 24584 indexes.
0 KB in bad sectors.
236631 KB in use by the system.
65536 KB occupied by the log file.
43249868 KB available on disk.

4096 bytes in each allocation unit.
29278975 total allocation units on disk.
10812467 allocation units available on disk.

Internal Info:
00 fd 01 00 fc f4 01 00 d8 a0 03 00 00 00 00 00 ................
6d 01 00 00 4c 00 00 00 00 00 00 00 00 00 00 00 m...L...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

Bump

CHKDSK appears to be ok. Have you had another BSOD? if so please upload it

Sorry for the late reply, Christmas means work is busy busy!

Anyhow here is another dmp file from a month earlier that may be able to make it easier to pinpoint the I/O error?

I have since both of these crashes updated the BIOS drivers and have had no issues so far but it could also be something else, couldn't it?

Anyways thanks so much for the help and Merry Christmas

Bump

Hello once more,

I just had another crash about 5 mins ago, and have compiled the dmp data and shall attach that here.

I have no idea why that happened again.

I have not changed anything since the last one, no new programs no updates anything.

Was on itunes and Chrome at the time..?
Also got same message on start up about boot disk.

Please if you can help it would be greatly appreciated.

Thanks~

I've let zigzag3143 know you have returned. You may find http://www.sevenforums.com/crashes-d...moval-ssd.html interesting since you both are having similar problems with your SSD drives.

Many thanks writhziden
Shall await the reply

The most recent crash is inconclusive. It points to an I/O error but which process is not named. The uptime (time since booting) is abt 3 hours so it doesnt seem to feel like something loading at startup.

It is much easier to find patterns, etc, when there are more than one crash.

We prefer you wait until you have at least two so that if one is corrupt the other probably wont be.