1
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?
UPDATE:
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.
UPDATE 2:
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.
UPDATE 3:
My computer is now stable again, the problem that lead to this was the 5200 hour bug in crucial m4 drives.
Lars Næss Evensen
Posted 2012-08-06T20:24:28.397
Reputation: 11
1Could be power problems. Have you tried a new power supply? What BSoD STOP code do you get? – Ƭᴇcʜιᴇ007 – 2012-08-06T20:34:36.647
I did replace my power supply within the last 6 months, so it should be ok, but still that might be the issue. Since the BSOD happens at random intervals I have not yet managed to figure out what stop code I am getting. – Lars Næss Evensen – 2012-08-06T20:37:15.430
1You may want to disable automatic reboot on Blue Screen then, that way you'll be able to read it the next time it happens. It should also report the bug check in the Event Logs as well.. Anything obvious in those? Never assume any part is good just because it was replaced "recently". Really though, we'll need much more info to help you with this, most coming from you trying general troubleshooting and asking specific questions about specific problems. Otherwise it's going to just be guesses... – Ƭᴇcʜιᴇ007 – 2012-08-06T20:41:27.770
Thanks, I was not aware I could turn off the automatic reboot, but that will be really helpful :) I will also check the event logs. – Lars Næss Evensen – 2012-08-06T20:43:44.153
From the event log I am getting an Event 3 - Session "Microsoft Security Client OOBE" stopped due to the following error 0xC000000D in between the Critical Kernel-Power (because the machine reboots without shutting down properly). – Lars Næss Evensen – 2012-08-06T21:06:19.470
There are some suggestions on how to solve this issue on msdn technet, so I will give that a try. – Lars Næss Evensen – 2012-08-06T21:09:39.063
None of the suggestions in that thread worked for me. I also managed to get some info from the BSOD: 0X000000F4(0X0000000000000003, 0xFFFFFA800481EB30, 0XFFFFFA800481EE10, 0XFFFFF8000318F720) But no dumpfile was created, which might be related to the missing SATA drives? – Lars Næss Evensen – 2012-08-07T16:29:50.377
Yup, F4 errors are often (most commonly, from my experience) caused by a hard drive or hard drive controller error. – Ƭᴇcʜιᴇ007 – 2012-08-07T19:37:57.290
Ok, that was not what I hoped for, but thank you so much for the help :) I have brought a harddrive from work to verify if it is the controller or the drive. The warranty should still be valid on both my motherboard and harddrive. – Lars Næss Evensen – 2012-08-08T18:03:54.370