Windows 7 BSOD and missing SATA drives at reboot


I get random BSOD, then when my computer reboots my SATA drives are gone and it gets stuck at "verifying DMI pool data". By rebooting they sometimes re-appear.

Before this my computer has been running without any issues for two years.

At first I thought this was related to my hard-drives, but after disconnecting all except one and retrying nothing changed.

I ran memtest for 24 hours in addition to running with one ram piece at a time replacing it if I got the BSOD again.

Any suggestions to what might be causing this?


I am getting the following error in my event log: "Microsoft Security Client OOBE" stopped due to the following error 0xC000000D

I tried removing a file related to Microsoft Security client as suggested on microsoft technet, but this did not solve my problem.

BSOD info: 0X000000F4(0X0000000000000003, 0xFFFFFA800481EB30, 0XFFFFFA800481EE10, 0XFFFFF8000318F720)

No dump file is created even though I did check the box for that in advanced settings.


After @techie007 suggested it was most likely the hard-drive or the controller, I have left it on at home testing a drive from work. I have also checked online for possible issues with my SSD drive (Crucial m4), and it seems that these have a bug that makes it unstable after 5200 hours. A new firmware has been released solving this issue, so I will attempt that later today.


My computer is now stable again, the problem that lead to this was the 5200 hour bug in crucial m4 drives.

asked on Super User Aug 6, 2012 by Lars Næss Evensen • edited Aug 10, 2012 by Lars Næss Evensen

2 Answers


Go into your BIOS and make sure that the hard drive with the Windows installed is correctly set as the primary boot device. Choose the HDD as primary boot device, followed by CD-ROM/Floppy. Also make sure that the HDD is set to auto-detect within the BIOS utility.

If you have any discs or diskettes in the CD-ROM or floppy drive(s) then please remove these and try and boot up again, this is to make sure the system is not trying to boot from the said device.

Make sure ALL cables are 100% connected to the system and are not loose at any scale. If any of the above does not work then try and reset the CMOS using the CMOS jumper.

If still nothing above fixes the issue then you may have to replace/fix the master boot record on the hard drive as this may be the cause. Or here is a similar instructions website:

answered on Super User Aug 6, 2012 by George

My issue was caused by the 5200 hour bug in crucial m4 harddrive firmware. Hopefully this can help someone else having the same issues that I had.

answered on Super User Aug 10, 2012 by Lars Næss Evensen

User contributions licensed under CC BY-SA 3.0