@InfiniteVerve The bloom effect edits should be okay, at least assuming the guide you're looking at describes them correctly. But you can always undo the changes if you don't like them. And if you run into real trouble, just put the original graphicsrules back, or at least a copy of what you had before the bloom effect edits.
By the way, you didn't mention it, but in deviceconfig.log, a few lines below the found and matched values for your graphics card, you should see the texture memory value. If you still have a 32 MB override, that means the game isn't recognizing your card's VRAM and has set it to the minimum. You can fix it by editing a few lines near the top of graphicsrules. This:
if ($textureMemory == 0)
seti textureMemory 32
setb textureMemorySizeOK false
becomes this:
if ($textureMemory == 0)
seti textureMemory 5967
# setb textureMemorySizeOK false
So you're changing the 32 to the (dxdiag reported) dedicated memory of your card, and adding a # and a space in front of setb. Sims 3 is programmed to only use 800 MB of VRAM anyway, and anything over 1 GB is extraneous, so you can set that value to whatever you want.
Since you're not seeing more crashes, it's entirely possible that enabling vertical sync was the solution. Having an unrecognized card only makes a marginal difference, if that, not enough to cause crashes unless someone butchers graphicsrules to the point that the game can't use part of it at all, and you clearly didn't do that. There's nothing else in your dxdiag that would directly explain or even describe the crashing, although a dxdiag will only list the last ten Windows errors, so if you've had more since then, the Sims 3 errors will be pushed off the list.
The Windows errors that are in your dxdiag list eight identical crashes:
Fault bucket 2083440491699377558, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0
Problem signature:
P1: MSI.CentralServer.exe
P2: 1.0.0.46
P3: 5ef2cfce
P4: MSI.CentralServer
P5: 1.0.0.46
P6: 5ef2cfce
P7: c
P8: 3c
P9: System.NullReferenceException
P10:
MSI.CentralServer.exe is a component of MSI Dragon Center, which is control software that MSI wants all its customers to use. It's not necessary though, and it does take up a more than trivial amount of resources, so if you don't have a specific purpose for it, you may want to just uninstall Dragon Center entirely.
The errors also reference .NET Framework 4.x (that's the CLR20r3 at the top), so it's a good idea to run the system file checker. While the error might be entirely due to Dragon Center and not a problem with .NET, it's worth being thorough.
Here's how:
- Hit Windows key-X
- Choose either “PowerShell (Administrator)” or “Command prompt (Administrator),” whichever option is offered
- Inside the window, copy and paste “sfc /scannow” without quotes into the window, and enter
- If sfc reports it found corrupt files and was unable to repair some of them, restart your computer
- Then repeat the above, except with the command "DISM.exe /Online /Cleanup-image /RestoreHealth" (no quotes)
- Then run sfc again
I'm not saying you'll find anything, just that it's a few minutes of your time well spent. And any time you have errors with no clear-cut cause and solution, DISM and sfc are a good place to start.
The one Sims 3 error is a memory leak, but Sims 3 has memory leaks; this doesn't mean there's anything wrong with your system.
If you do get more crashes, or want to find out more about the earlier ones, you can look at the Reliability Monitor. Hit Windows key-R and enter "perfmon /rel" without quotes. The chart of errors and updates goes back 30 days, although it resets with a Windows feature update. For any given error, you can click "View technical details" and get a bit more information.
The advantage of this approach is that the entries have timestamps, although the times reported on the initial chart can be off by a bit, and the chart doesn't always update right away. The ones in the technical details are accurate though. So even if Sims 3 isn't listed, you'll be able to see what happened at the time when the game crashed and go from there. For example, if the component of Dragon Center listed above crashed every time the game did, you'd know to poke at it more, but if the crashes are happening at other times, you'd know they were unrelated.
Other notes: Your BIOS is a bit old, and you could update it if you wanted. It's not necessary to stay fully updated unless you want a new feature, or perhaps some fix or improvement. But it's not critical to stay fully up to date for its own sake.
It looks like you also removed a large chunk of the dxdiag, one which contains information about sound drivers and various devices. There's no indication in your dxdiag that any of that was relevant to the crashing, but if the Windows errors had referenced audio software or a component of an application used by a peripheral device, I'd have wanted to see that information to check driver versions and look for other reports of similar errors. It's also useful in general to check whether someone has all the latest drivers, especially when it's not immediately clear why an application is crashing.
——————————————————————————————————————————
I don't work for EA. I'm just trying to help fellow players with their games.
