Multiple BSOD issue, 0XF4 was the only culprit caught.

[squish8294]

Squish, if you moved the page file from your SSD to the secondary hard drive, please move it back to the SSD, then shut down and remove both cables from the Momentus, start back up and open a elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

Also, if you are overclocking anything, please set everything back to default levels.

Momentus has no Page File. I think I know which drive is causing the issue.

I have part of my Page File on the 2TB drive which will sometimes stop sending data to the MB and needs to have the power reconnected. Would this cause my BSOD issue if it occurred during bootup?

Edit: Does the pagefile get scanned by the SFC procedure?

 

[essenbe]

I may not be much help. sfc scans protected system files. I know that much. Whether a page file is a protected system file, I don't know that, and whether it would find it if it is not in the expected place, I don't know either. However, why don't you put the page file back on the SSD, where it should be. Most of the stuff you read on the internet about moving the page file off the SSD to reduce writes to it is bunk. Most of that stuff was written for 1st and 2nd generation SSDs, which was needed. We are many generations past that and SSDs are not near as fragile as people think. I can give you links to threads where people tried to kill them by writing constantly to them 24 hours a day. Most of them it took petabytes of writes to kill them. More than you and I combined will write in a lifetime. I have an Intel X-25M that is quite old and has endured more than I could ever give it. I also have a Vertex2 which is still running just fine. I own 12 SSDs with another in the mail and have never taken the page file off of any of them and they all are running in some machine here. About 4 years ago, Intel guaranteed that their SSDs could take 5 GB of writes per day every single day for a minimum of 5 years without suffering damage.

Now, as for the 2TB drive stopping sending info to the board. That should never happen, page file or not. I would suggest you change the cable and see if that is the problem or whether you have a dying drive on your hands. I would back up everything on the drive right now until you find out which it is. But, to answer your question. Be sure you know I am just assuming here. If the computer has stored information on the page file, and it needs it now, but cannot get it, I would think it could cause a BSOD. The computer needs constant access to the files necessary for it to run. If, for whatever reason, it cannot have the data it needs to run, it will quit functioning. A common thing with BSODs is that something happens and the computer will shut itself down to prevent damage from occurring (BSOD). Just my 2 cents.

 

[squish8294]

Now, as for the 2TB drive stopping sending info to the board. That should never happen, page file or not. I would suggest you change the cable and see if that is the problem or whether you have a dying drive on your hands. I would back up everything on the drive right now until you find out which it is. But, to answer your question. Be sure you know I am just assuming here. If the computer has stored information on the page file, and it needs it now, but cannot get it, I would think it could cause a BSOD. The computer needs constant access to the files necessary for it to run. If, for whatever reason, it cannot have the data it needs to run, it will quit functioning. A common thing with BSODs is that something happens and the computer will shut itself down to prevent damage from occurring (BSOD). Just my 2 cents.

I have changed the data cable. I have PSU Cable routing done in my case so changing the power cable isn't really the best solution, on top of the fact that my drives are all on one cable, so if it was just the cable going bad, all of em would be having that issue. Leads me to believe the drive is going.

 

[essenbe]

Well, honestly that's what I think too. I was just trying to think of some other possibility before I pronounced that it had a terminal disease and no further medication would be useful.
I think I would be getting all my Data off now.

 

[squish8294]

Okay, reviving this one. Continuation - playing Battlefield Bad Company 2 causes my system to BSOD reliably. I've run Memtest86 and it's given me all sorts of errors. I've reverted from an overclock (relatively mild), and am now running my CPU @ stock, and RAM @ 1333 MHz 9-9-9-24.

Still BSOD while playing the game.

Here's the dealio with memtest - There's only 2 cores of 0 to 3 throwing errors to the memory, Core 1 and 2.

Does this mean my memory is going bad, or is half of my processor die going bad? Any ideas? Multiple tests threw errors, I don't remember if they were all at the same address, but it was that I saw, all CPU 1 and 2.

Also, another possible thing;

With multiple drives and different ports having disappeared from windows (More than once being my OS SSD, heh), I'm wondering if maybe my MoBo isn't going bad?

 

[essenbe]

No, if you have changed the timings, frequency or voltage to the ram, run memtest again. If you get errors, run 1 good stick only in every slot and keep track of which sticks and which slots give errors.