PSU worked fine on 110V, crashes on 220V???

[psucrash]

My primary gaming PC crashes consistently during game play (tested in CSGO and Borderlands2). I have done extensive troubleshooting ruled out most major components (it's probably NOT: RAM, GPU, motherboard, drivers/OS). I am leaning towards it being a PSU issue, but I'm not sure.

I moved to Europe from the U.S. recently. The system was 100% fine before it was shipped to Europe. Is it even possible for a PSU to not work on 220V power but work fine on 110V? Are there different "rails" or whatever that handle these different voltages in the PSU?

It is a Cooler Master Silent Pro Gold 1000W. US Type.

System boots fine, everything seems to work. I can launch into a game and it runs as normal, but after some time (no longer than 15 minutes) the system crashes. The screen goes blank and I have to do a full power cycle before I can get video displayed again.

I have put the video card in another system and it was 100% stable. I have changed out the motherboard entirely and the issue persists. I have tried different RAM and it makes no difference.

 

[user14]

I think that PSU as most ones are autorange input VAC so shouldn't matter, does the problem occur even you leave computer unattended/light use?
Would be a good idea, if you haven't yet, install some kind of monitoring SW that can read out temperatures and voltages.
Try this one and report back what you see..
http://openhardwaremonitor.org/
BTW do you feel like the exhaust air from the PSU fan smells kind of "hot" or fried?

 

[psucrash]

I swapped to another PSU entirely and the issue still happened.

I am starting to think it is the CPU, because that is the only thing I haven't swapped out at this point for testing.

Definitely not the motherboard. Definitely not the graphics. Definitely not the PSU. Definitely not the RAM.

CPU is an Intel Core i7-3770K Ivy Bridge 3.5GHz (3.9GHz Turbo) LGA 1155. Makes me wonder if I needed to change the motherboard at all. Although that motherboard's PCI-E slots stopped working. Maybe it damaged the CPU while it was at it...