Game boots up, displays white screen, only has sound and invisible UI

@VaanDiablo 

---

VaanDiablo wrote:

All are stable and run 200(±~35)+ FPS. My GPU is OC'd slightly and I've since deactivated my OC settings because of instability during the summer heat and forgot to turn them back on. My CPU is OC'd for an extra 100MHz Boost Clock.

---

I would ask you to end all overclocking for the time we troubleshot.

---

VaanDiablo wrote:

I do, but that strikes me as slightly more effort than it's worth considering my friends are all in excess of 20 miles away, and my missus is an Alienware Laptop user. So not really an option I'd take easily.

---

Considering your description, it really is. Still there are several LiveKernelEvent 141 Hardware error in your DxDiag. (VIDEO_ENGINE_TIMEOUT_DETECTED)
So that might be something to consider if everything else fails.
Not being able to use DDU in such a case is a real problem as well.

---

VaanDiablo wrote:

I only tried Shut Down > DC > Start with my main monitor, as it's a normal aspect ratio and resolution. I did try both of them unplugged normally, however.

---

Please try with the other monitor as well. (As only monitor connected, and The Sims resolution set to 1080P.)

---

@VaanDiablo wrote:

I can't, my 144hz is VGA, my widescreen is HDMI 2.0. I don't have a converter either, I'm afraid.

---

You surely mean DVI? That's what your DxDiag says.

---

@VaanDiablo wrote:

The board bios being old makes sense, considering. I'll give that a crack. Same thing as PCIe, though. Updating the entire board makes it less likely to be that, right?

---

Yes it does makes it less likely to be that, but lets make sure.

Furthermore, I would normally ask you to preform a clean boot, (Not a save boot) and to disable Afterburner and Rivatuner or any other overclocking tool you might have, and test the Game in clean boot mode.

But I can't say if your Pin would work on a non active Windows in clean boot state, and that provides us with another problem here.

May I suggest to recover your Password? There are useful tools at the nirsoft site.  

• I would ask you to end all overclocking for the time we troubleshot.

Went and looked, turns out I'd never applied my CPU OC. There was never an OC of any type applied to my system. Which raises other questions for me, but none for the EA forums.

• The LiveKernelEvent 141 Hardware error in myDxDiag

Did more digging. Most likely cause of this I could find is that my luck continues to be poor (it's a running joke across my entire life that anything revolving around luck is never going to go my way) and I lost on the silicon lottery for my 1080ti. Makes sense, because it's OC capabilities were poor when I was faffing with them last year some time.

• Please try with the other monitor as well. (As only monitor connected, and The Sims resolution set to 1080P.)

No luck.

• You surely mean DVI? That's what your DxDiag says.

Point still stands. I've got no connector.

• Yes it does makes it less likely to be that, but lets make sure.

So I was reticent to do this due to prior experience bricking a mobo due to a bad bios update. Thankfully they replaced it for free as it was their own new bios, but still.

In the meantime I did a completely fresh install of Sims 4 and Origin again. This time I removed the entire EA folder from my Documents, rather than just the settings, Mods, and Saves. It worked. I thought a fully fresh install was the saviour and was ready to come on here and tell you guys that life could go on but I needed to pop out. I came back, turned on my PC and tried to boot Sims 4 and it was white screening again.

This time I just removed the EA folder from my Documents. Lo' and behold, Sims 4 boots up. I move my Saves back and it still boots. I load a game, play a bit, make a new save, change the music settings down, and then turn off my PC to test. On a fresh boot the game will no longer load up properly. It appears the game, on closing, is putting something into my EA folder along with my saves that makes the game break. I use no mods, nothing in my game is different to the average users'. I now have a repeatable way of breaking and fixing my game. It's a ball ache, but at least I can play. Now I'm just curious as to what the F is happening with my game that is causing it to commit settings-based suicide. Any of you have an idea?

Thanks to everyone that aided in the process of debugging my game and offering help!

@VaanDiablo  Holger is the hardware expert, not me, so I defer to him in that category.  But as far as game files go, are you saying that messing with options.ini is the way to break the game?  Can you play as long as you change no game settings at all?  If so, once you get to a white screen, delete options.ini and nothing else, and relaunch.

@VaanDiablo  That's so strange.  I mean, it makes perfect sense that the files might not work properly if they were compressed and the game couldn't read them.  But I'd think the problem would be more widespread.

In any event, I'm glad to hear you figured it out, and thanks so much for sharing that info.  I'll be sure to keep it in mind for other people with the same symptoms.

@VaanDiablo 

---

@VaanDiablo wrote:

I had the sudden idea to stop windows from doing it's auto compression on those files once they'd been created and had started giving me whitescreen. This solved it. I can now turn my PC off and on and get back into the game without whitescreening it each time. I have no single idea why nor how, and I was under the impression it's only slight compression to aid with space saving and that any file in use is uncompressed, so nothing should be happening. However, that doesn't change the fact that it's no longer breaking once it's deactivated.

---

This behavior is not really automatic, at least not most of the time.

Auto compression is not set by default in Windows 10, it is however enable if a feature update of Windows finds a hard drive that is low on space during the update. 

You should make sure that you have at least 20GB of space on your system drive before you run a Windows feature update.

---

@VaanDiablo wrote:
Did more digging. Most likely cause of this I could find is that my luck continues to be poor (it's a running joke across my entire life that anything revolving around luck is never going to go my way) and I lost on the silicon lottery for my 1080ti. Makes sense, because it's OC capabilities were poor when I was faffing with them last year some time.

---

The LiveKernelEvent 141 error can have many reasons, a real hardware defect of the GPU is one of them.
But it can also (among other things) be memory or driver related. So a clean installation of the driver with DDU and a Memory check would be a good idea.