Emulator

Game Name? Super Smash Brothers Brawl (NTSC)

Game ID? RSBE01

What's the problem? Describe what went wrong in few words.
Dolphin (not just the game) freezes before starting if cheats are enabled, only way to close Dolphin is to kill it from the task manager.

What did you expect to happen instead?
The game to start, and Dolphin not to require Windows to mercy kill it.

What steps will reproduce the problem?
[Don't assume we have ever played the game and know any level names. Be as
specific as possible.]
1.Get Brawl ISO in working directory
2.Enable cheats if not already
3.Wait for Dolphin to freeze

Dolphin 3.5 and 3.5-367 are old versions of Dolphin that have
known issues and bugs, so don't report issues about them and test the
latest Dolphin version first.
Which versions of Dolphin did you test on?
4.0-2472 (thoroughly)
4.0-2306 (not as thorough)
4.0-2246 (not as thorough, earliest development version I have)

Does using an older version of Dolphin solve your issue? If yes, which
versions of Dolphin used to work? 4.0.2 works to where the emulator can run, but some cheats cause the freeze such as the CSS edit code modified for a new character slot. I remember these codes working at one point, but it's not letting me do them now.

What are your PC specifications? (including, but not limited to: Operating
System, CPU and GPU) Windows 8.1, Intel Core i7 3770, AMD 7500 series Graphics card (I forgot the exact card I am using and this is what the operating system and drivers state I have), 8 gigabytes of ddr3 ram.

Is there any other relevant information? (e.g. logs, screenshots,
configuration files)
I have tried on both Direct3d and OpenGL backends. My other settings are having the DSP LLE on separate thread (turning it off did not help on either), EFB to Texture, 2x Internal resolution, OpenMP Texture Decoder, fast depth correction turned off, and on 4.0.2 caching the display lists. Windowed and Fullscreen were tested, and other games checked for this issue are Shadow The Hedgehog and Metroid: Other M.

I would like to note that on the latest developer, having full screen enabled can make it to where the only way to stop is to do a hard reset.