Quote:
Originally Posted by spida_singh
Guys, set off another encode, but, for some reason, i got BSOD?? Only did a fresh install about 2 weeks back, any ideas what could be causing it? The same happened with my Family guy rips when using automkv, i got BSOD after the audio encode, is x264.exe causing a crash (as this was used when converting to a .mp4)? Strange as it worked with my hellboy encode overnight??
|
A BSOD will usually mean an unstale overclock on your system (FSB\CPU\RAM), not enough volts or overheating. Just because one encode worked doesn't mean that it isn't the problem as you could be on the upper threshold and if the ambient temp is slightly warmer one day it could push a component over the edge in terms of heat etc.
Hard to say, but you should run Prim95 (latest version that tests all cores) for a couple of hours to check. Also run memtest to check the memory for a couple of hours afterwards.