The game seems to lock up with a "Fez has stopped working correctly" error in Win7 64 after spending more than a couple of minutes in this room (see attachment). I know this isn't the best place to report bugs - just throwing it out there in case anyone else has the same problem.

I have that exact problem with Win7 64bit

True. It crashed for me too. Was afraid it's problem with my low spec CPU. There is hope it is not. But yea, it is bugged.

Mine crashed too

!
(14:30:56.955) [OpenAL] 32-bit OpenAL-Soft will be used
(14:30:57.066) [OpenAL] Available mono sources : 255
(14:31:00.134) [Version] INFORMATİON : 1.0, Build Date : 30.04.2013 04:17
(14:31:00.527) [MonoGame] INFORMATİON : OpenGL version 3.3.11653 Compatibility Profile Context
(14:31:01.525) [Unhandled Exception] ERROR : Microsoft.Xna.Framework.Content.ContentLoadException: Could not load Other Textures\keyboard_glyphs\P_I asset as a non-content file! ---> Microsoft.Xna.Framework.Content.ContentLoadException: Can't find asset named : Other Textures\keyboard_glyphs\P_I
konum: FezEngine.Tools.MemoryContentManager.OpenStream(String assetName)
konum: Microsoft.Xna.Framework.Content.ContentManager.ReadAsset[T](String assetName, Action`1 recordDisposableObject)
--- İç özel durum yığını izlemesinin sonu ---
konum: Microsoft.Xna.Framework.Content.ContentManager.ReadAsset[T](String assetName, Action`1 recordDisposableObject)
konum: FezEngine.Tools.SharedContentManager.CommonContentManager.ReadAsset[T](String assetName)
konum: FezEngine.Tools.SharedContentManager.CommonContentManager.Load[T](String name, String assetName)
konum: FezEngine.Tools.SharedContentManager.Load[T](String assetName)
konum: FezEngine.Components.GlyphTextRenderer..ctor(Game game)
konum: FezGame.Components.SpeechBubble.Initialize()
konum: Microsoft.Xna.Framework.Game.InitializeExistingComponents()
konum: Microsoft.Xna.Framework.Game.Initialize()
konum: FezGame.Fez.Initialize()
konum: Microsoft.Xna.Framework.Game.DoInitialize()
konum: Microsoft.Xna.Framework.Game.Run(GameRunBehavior runBehavior)
konum: FezGame.Program.MainInternal()
konum: Common.Logger.Try(Action action)

I reported it here: https://getsatisfaction.com/polytron

I am on the same boat :/

Vista 64 bit, nvidia 560ti.

Edit: my post was not edited..arg...

Seems that those cubes(disposable item) are still referenced to XNA which got ripped out from the game.
This could happen in other areas were those cubes are used :/

Version 1.1 incoming soon i guess.

As I posted elsewhere, same thing. Also happens in another room with a similar four-block puzzle (one on a pedestal, two on a lower level, one on the lowest level). Both of those rooms have the same music, and those are the only rooms I've seen those blocks in. No crashes anywhere else, including the similar-styled purple rooms with different music.

I just read the readme, i add 2 more problems.

I have the exact same problem in the exact same room. I hope this gets resolved as soon as possible... :(

Comment from developer: getsatisfaction.com/polytron/topics/crash_in_tetris_block_secret_puzzle_room#reply_11941677

For lazy people:
"Hi,

This problem has been found last night and was fixed in the Steam build that will come out later today.
Unfortunately the GOG build is two days old by now, and will only get updated tomorrow at the earliest.

The version that corrects this problem is v1.02. I'll update this thread when the patch comes live on GOG! "

Well..that is...i dont know...at least we too get the patch...as usual.

They found it last night and still uploaded the bugged version here on GOG? A warning or some information would have been nice, I guess... :(
Feeling a bit like a second rate customer here.

From what i read the GOG version was send/given to GoG 2 days ago, since they found the bug last night, they couldn't stop it...but an early patch would have been nice, or do they have to rebuild the game with those fixes?

It also seems that more gamers bought the game on steam and it is more critical to get the best version there :/

No matter...i stopped playing already...waiting for the patch to arrive. At least they act fast and respond to those issues. It's bad when such things happen...but they happen. I would still choose the GOG version just for beeing without DRM.