Huge log file and BSOD problem

**gabyu** · April 22, 2012, 10:09 AM

Hi everyone. I've been playing BC 2.3.2.2 for half an hour as Kingdom of Jerusalem. I loved it but..... I got the Blue Screen of Death problem. Then, after the PC restarted, I defragged the hard disk and found that the bc_log.txt file was HUGE (653 MB, I deleted it to free HDD space). Why did I get the BSOD problem and why was that log file so huge?

PC specs (they may help) :
CPU: AMD Sempron LE-1250 2.2 Ghz, overclocked at 2.74 Ghz
GeForce 7025/nForce 630a (128 MB shared memory)
1GB RAM (of which 128 MB are shared with the GPU)
All the drivers are up to date (checked them yesterday)

**Harith** · April 22, 2012, 10:24 AM

Originally Posted by gabyu

Hi everyone. I've been playing BC 2.3.2.2 for half an hour as Kingdom of Jerusalem. I loved it but..... I got the Blue Screen of Death problem. Then, after the PC restarted, I defragged the hard disk and found that the bc_log.txt file was HUGE (653 MB, I deleted it to free HDD space). Why did I get the BSOD problem and why was that log file so huge?

PC specs (they may help) :
CPU: AMD Sempron LE-1250 2.2 Ghz, overclocked at 2.74 Ghz
GeForce 7025/nForce 630a (128 MB shared memory)
1GB RAM (of which 128 MB are shared with the GPU)
All the drivers are up to date (checked them yesterday)

prolly ur system didnt handle the game... I personally never had this problem... My specs are 4gb ram, 0.5gb video memory and 2.2 ghz core duo.

**gabyu** · April 22, 2012, 10:28 AM

Maybe, but I was on the campaign map when I got the Black Screen of Death.

**wudang_clown** · April 22, 2012, 05:14 PM

I've never heard about such a problem before. The log file should never be that huge - I've never seen 653MB-big log, especially not after half an hour of playing. 100-150MB happens sometimes, but 653MB? Never heard before...

I suspect the overlocking. Or maybe your video card is too weak? Although few years ago I was playing M2TW and Broken Crescent 1.05 on Athlon 1.8GHz and a GForce card with 128MB of dedicated memory, plus 512MB of RAM. Yep! Video settings were lowest possible, iirc, but it was sufficient to play normally.

Can you revert the processor overlocking to default settings and then try to play?