We all know that it happens: After booting up Gateway / PastCFW on a N3DS, super stable 3D no more works. Temporarily fixing it is just a minor nuisance, as it only requires you to close and open the lid. What I'm interested in is, what is the technical reason behind the SS3D failure? In fact, any information helps! Some more information: For GW, I always saw the SS3D failure as (unavoidable) collateral damage, as GW is closed source and (supposedly) does a lot of stuff in the background. The same can't be said for PastaCFW, though. PastaCFW, only patches two adresses in memory - that should be pretty precise and having the same "collateral damage" as GW just seems strange. With other words: the sig checks are at these two memory adresses, how can SS3D also be controlled from that? So, any ideas?