Please give me a hammer!

[MarkW]

I am not sure if this is the root cause but our friend NickN cautions against over clocking before you finish installing everything and ensure you have a stable system. He claims that most software errors occur because people over clock first then install. Hopefully you will find the cause and be able to fix it.Mark

[Guest jahman]

Smart advice, but you can do both: OC your PC before installing the software to see how fast it will go, disable OC to install the software and check functionality. If all OK, re-enable OC.Cheers,- jahman.

[ryanbatc]

It appeared stable before all this happened. 12+ hrs P95 and a few hours of OCCT @ 4GHz should be enough. When it wasn't stable at 4.5GHz it let me know with those specific error codes regarding not enough vcore etc etc.Looking over the MS support article it's likely something became corrupted in Windows. I did a fresh install and will put it through some tests and my friend's going to look at it too.

[MarkW]

Smart advice, but you can do both: OC your PC before installing the software to see how fast it will go, disable OC to install the software and check functionality. If all OK, re-enable OC.Cheers,- jahman.

Good to know.

[Guest Kosta]

Seriously, I think that non-ocing before install is a non-sense. If you have a stable machine (I am doing my tests with Linx), you will have no troubles installing programs.Though finding a "stable" point is really really hard, and I doubt that everyone is doing it correctly. Not even sure if I'm doing it right, but I do my best. My final test is Linx 4GB, 300 runs (that gives it about 9 hours of hardcore testing). Then I run couple of hours Prime95. That and then check if I have any boot problems (memory, usually IMC playing tricks).Given that: when I buy a new machine and doing a complete OS reinstall, then I don't have patience to leave tests for nights long. I want to have a running machine. Then I do it on stock as I can't check the OC. But my last, I didn't reinstall Windows, and I OCed it right away.

It appeared stable before all this happened. 12+ hrs P95 and a few hours of OCCT @ 4GHz should be enough. When it wasn't stable at 4.5GHz it let me know with those specific error codes regarding not enough vcore etc etc.Looking over the MS support article it's likely something became corrupted in Windows. I did a fresh install and will put it through some tests and my friend's going to look at it too.

Try what I wrote in previous post. In my experience, if Linx doesn't crash, nothing else will. I had Linx crash after 6 hours btw... not even sure if 10 hours is enough.

[Guest jahman]

Seriously, I think that non-ocing before install is a non-sense.

Seriously, NickN knows a lot more about PCs than you do. :Party: Cheers,- jahman.

[Guest Kosta]

Seriously, NickN knows a lot more about PCs than you do. :Party: Cheers,- jahman.

So he does. Doesn't mean everyone else knows jackshit, pardon my expression.

[fghdgdfdfgfgf]

ROFL

[cmeeks]

Regardless of what NickN says, I think it makes much more sense to find a stable OC before installing FSX. BSOD can sometimes corrupt your windows installation, so I think that takes precedence.