TR Forums

I've got a reproducible error that I get a BSOD when I quit out of Bastion. It's happened on Windows 8.1 Update and the Windows 10 Tech Preview. It's occurred with numerous driver revisions including the current hotfix 350(?) ones. Has anyone else encountered this. The CPU/mobo are a Core i5 4690K and ASUS Z97-A. Kingston DDR3-1600. Nothing's overclocked and everything is otherwise running fine.

Anyone else with a 970 seen the same or have a fix? I finished the game the last time I played it, but it's pretty annoying if I want to go back to it.

I have the game in my steam library from a Humble bundle. Never played it before. My system: i5 3570K, 16GB memory, Gigabyte Z77-DS3H, GTX 970. Running 347.88 on Win 8.1 Pro + MCE totally updated. Played for about 15 minutes and then quit out of the game. Went to the desktop, no errors, no BSOD. Sorry, man.

Unfortunately, Internal Memory Error is a rather vague BSOD name in comparison to others. The bug check code reference to which I just linked had no mention of a Internal Memory Error BSOD, but the reference is mainly for developers who won't have most BSODs caused by their software/drivers.

It's an NVDA feature...don't be ungrateful

Are you overclocking anything in the system? Is the 970 running a little toasty?

I would check that before moving onto software related issues.