So I was playing Borderlands 2 playing some music in the background when BAM BSOD in my face.
After turning the system back on the boot device (shown in the POST as Samsung 931GB RAID due to being in RST with the SSD) had 'disabled' next to it.
I then turned the machine off, took the sides off, and checked the connections to all of the SATA ports, put the sides back on, and it started up fine and here I am typing this post.
The only other BSOD I have had on this machine was a couple of months ago when I was playing Test Drive Unlimited 2. On restarting the drives were fine though.
Any ideas?
I think it was an unstable overclock on my GPU last time, but this time I have a new GPU, stock clocks, and it is fine in Kombuster etc so it can't be that.
Could it be that one of the SATA cables somehow came loose? And when the system had to read/write back to the HDD it bluescreened?
And could be in any-way related to the F2 and 70 errors that my motherboard shows on the Dr. Debug LCD when I start it up occasionally? (maybe one in every 15 times it halts on a F2 error, restarts itself, then halts on a 70 error. I then have to manually turn it off, and when I turn it back on it is fine. I started a thread about it a while ago)
After turning the system back on the boot device (shown in the POST as Samsung 931GB RAID due to being in RST with the SSD) had 'disabled' next to it.
I then turned the machine off, took the sides off, and checked the connections to all of the SATA ports, put the sides back on, and it started up fine and here I am typing this post.
The only other BSOD I have had on this machine was a couple of months ago when I was playing Test Drive Unlimited 2. On restarting the drives were fine though.
Any ideas?
I think it was an unstable overclock on my GPU last time, but this time I have a new GPU, stock clocks, and it is fine in Kombuster etc so it can't be that.
Could it be that one of the SATA cables somehow came loose? And when the system had to read/write back to the HDD it bluescreened?
And could be in any-way related to the F2 and 70 errors that my motherboard shows on the Dr. Debug LCD when I start it up occasionally? (maybe one in every 15 times it halts on a F2 error, restarts itself, then halts on a 70 error. I then have to manually turn it off, and when I turn it back on it is fine. I started a thread about it a while ago)
Last edited:
