Fresh Install, Lets play

Ever since last week when the game started acting up and performance was cut in half.
I tried everything to get it back. I even reworked hours upon hours of using windows performance analyzer, cross referencing signal affinity interrupt, working out any remaining latency hiccups to try and make up for the performance loss in the game.
Anyway long story short, i wasn’t happy (was happy with every other game though)
So i decided, i was going to do a fresh install and retweak the entire system. Almost like gearing your guy up in the early stages of unique’s. You find one in the world and it helps your build and you start to build around it. That is kind of what i do on installs.
I try to find a new angle and go with it.
I have my usual drive with vital drivers for components and system, but i must be missing something…
Fired up diablo 4 and it wont even launch…
This is something that NEVER happened on my old install.
Then again, i had tweaked that system insanely…
I have all the information, maybe i spend all night tweaking the registry again…
If anyone of you have any ideas maybe as to a driver check or a fix for the not launching debacle i am all ears.

UPDATE

So an update to working on this all night.
I got it running after adjusting my system with many registry entries and de-bloating of windows. It was a fresh install without custom iso.
It was running like a champ.
Standing in nehantu at a steady 140fps with great framepacing.
The ping was atrocious though. Low 100’s
I went into undercity to try it out.
Great frames.
And then a 2 second freeze. (First time i have EVER experienced that)
Then another freeze like 20 seconds later.
Game closed out with no error.
Here is the weird part though and this did happen back in the beta days into early release. When i click my mouse, i can see my desktop for a nano second.
I remember back then if you went into task manager and force closed explorer. exe it would restart itself. But long enough to register that the game was in “full screen” and the desktop showing when you click would stop.
That didnt work now. So essentially an old bug is back.
Also i was reading fenris up to the point where i entered through the portal into under city. The issues of freezing started then, but fenris gives some indication of what is happening. I will post what it says from the time i go into under city to the time it closes with no error. Keep in mind, i am clicking and the desktop is showing in nanoseconds behind the screen. So its outputting that in the file as the following :
[WarpManager] Portal completed
I 2024.12.16 15:33:20.943700 104023 [Game] Initializing client world X1_Undercity_SnakeTemple_02…
I 2024.12.16 15:33:20.943771 104023 [Game] Client world initialized X1_Undercity_SnakeTemple_02 (1048577)…
I 2024.12.16 15:33:21.792374 104130 [Game] VideoPrefs: texture quality limited to High (VRAM: 8059MB)
I 2024.12.16 15:33:21.792383 104130 [Game] VideoPrefs: texture quality limited to High (VRAM: 8059MB)
I 2024.12.16 15:33:21.792385 104130 [Game] == Resetting Sound Prefs to Default… ==
I 2024.12.16 15:33:21.792388 104130 [Game] == Sound Prefs Reset to Default ==
I 2024.12.16 15:33:22.467023 104215 [Game] VideoPrefs: texture quality limited to High (VRAM: 8059MB)
I 2024.12.16 15:33:22.467031 104215 [Game] VideoPrefs: texture quality limited to High (VRAM: 8059MB)
I 2024.12.16 15:33:22.467034 104215 [Game] == Resetting Sound Prefs to Default… ==
I 2024.12.16 15:33:22.467043 104215 [Game] == Sound Prefs Reset to Default ==
E 2024.12.16 15:33:27.932105 104885 [Game] Tried to use shader Shader ‘vfx_decal_parallax_normalAO_emissiveColor’ with 2 passes on particle system Particle ‘NPC_Mercenary_shieldBearer_groundSlam_crackDecal_Parallax’. Particles only support single-pass shaders!
I 2024.12.16 15:33:28.366679 104929 [Game] VideoPrefs: texture quality limited to High (VRAM: 8059MB)
I 2024.12.16 15:33:28.366687 104929 [Game] VideoPrefs: texture quality limited to High (VRAM: 8059MB)
I 2024.12.16 15:33:28.366690 104929 [Game] == Resetting Sound Prefs to Default… ==
I 2024.12.16 15:33:28.366692 104929 [Game] == Sound Prefs Reset to Default ==
I 2024.12.16 15:33:32.179254 105374 [Game] VideoPrefs: texture quality limited to High (VRAM: 8059MB)
I 2024.12.16 15:33:32.179263 105374 [Game] VideoPrefs: texture quality limited to High (VRAM: 8059MB)
I 2024.12.16 15:33:32.179266 105374 [Game] == Resetting Sound Prefs to Default… ==
I 2024.12.16 15:33:32.179269 105374 [Game] == Sound Prefs Reset to Default ==
I 2024.12.16 15:33:33.098064 105492 [Game] VideoPrefs: texture quality limited to High (VRAM: 8059MB)
I 2024.12.16 15:33:33.098072 105492 [Game] VideoPrefs: texture quality limited to High (VRAM: 8059MB)
I 2024.12.16 15:33:33.098074 105492 [Game] == Resetting Sound Prefs to Default… ==
I 2024.12.16 15:33:33.098077 105492 [Game] == Sound Prefs Reset to Default ==
I 2024.12.16 15:33:34.155581 105617 [Game] VideoPrefs: texture quality limited to High (VRAM: 8059MB)
I 2024.12.16 15:33:34.155589 105617 [Game] VideoPrefs: texture quality limited to High (VRAM: 8059MB)
I 2024.12.16 15:33:34.155591 105617 [Game] == Resetting Sound Prefs to Default… ==
I 2024.12.16 15:33:34.155594 105617 [Game] == Sound Prefs Reset to Default ==
I 2024.12.16 15:33:40.840011 106423 [Game.Powers.PhasedPowers] Primary power desync: The client and server disagree on the current phase. | ClientPower: Spiritborn_Eagle_Basic | ClientFrame: 7945 | ClientPhase: 0X1FD3A | ServerPower: Spiritborn_Eagle_Basic | ServerFrame: 7945 | ServerPhase: 124610
I 2024.12.16 15:33:41.703091 106536 [Game] VideoPrefs: texture quality limited to High (VRAM: 8059MB)
I 2024.12.16 15:33:41.703100 106536 [Game] VideoPrefs: texture quality limited to High (VRAM: 8059MB)
I 2024.12.16 15:33:41.703102 106536 [Game] == Resetting Sound Prefs to Default… ==
I 2024.12.16 15:33:41.703105 106536 [Game] == Sound Prefs Reset to Default ==
E 2024.12.16 15:33:41.940796 106566 [Game] Tried to use shader Shader ‘vfx_decal_parallax_normalAO_emissiveColor’ with 2 passes on particle system Particle ‘NPC_Mercenary_shieldBearer_groundSlam_crackDecal_Parallax’. Particles only support single-pass shaders!
I 2024.12.16 15:33:47.870461 107327 [Game] VideoPrefs: texture quality limited to High (VRAM: 8059MB)
I 2024.12.16 15:33:47.870469 107327 [Game] VideoPrefs: texture quality limited to High (VRAM: 8059MB)
I 2024.12.16 15:33:47.870472 107327 [Game] == Resetting Sound Prefs to Default… ==
I 2024.12.16 15:33:47.870474 107327 [Game] == Sound Prefs Reset to Default ==
I 2024.12.16 15:33:53.531306 108108 [Game] VideoPrefs: texture quality limited to High (VRAM: 8059MB)
I 2024.12.16 15:33:53.531317 108108 [Game] VideoPrefs: texture quality limited to High (VRAM: 8059MB)
I 2024.12.16 15:33:53.531320 108108 [Game] == Resetting Sound Prefs to Default… ==
I 2024.12.16 15:33:53.531323 108108 [Game] == Sound Prefs Reset to Default ==
E 2024.12.16 15:33:57.490370 108162 [Game] Tried to use shader Shader ‘vfx_decal_parallax_normalAO_emissiveColor’ with 2 passes on particle system Particle ‘NPC_Mercenary_shieldBearer_groundSlam_crackDecal_Parallax’. Particles only support single-pass shaders!
I 2024.12.16 15:33:57.497616 108162 [Game] VideoPrefs: texture quality limited to High (VRAM: 8059MB)
I 2024.12.16 15:33:57.497624 108162 [Game] VideoPrefs: texture quality limited to High (VRAM: 8059MB)
I 2024.12.16 15:33:57.497627 108162 [Game] == Resetting Sound Prefs to Default… ==
I 2024.12.16 15:33:57.497630 108162 [Game] == Sound Prefs Reset to Default ==
I 2024.12.16 15:34:08.372816 109656 [Game] VideoPrefs: texture quality limited to High (VRAM: 8059MB)
I 2024.12.16 15:34:08.372825 109656 [Game] VideoPrefs: texture quality limited to High (VRAM: 8059MB)
I 2024.12.16 15:34:08.372828 109656 [Game] == Resetting Sound Prefs to Default… ==
I 2024.12.16 15:34:08.372831 109656 [Game] == Sound Prefs Reset to Default ==
E 2024.12.16 15:34:16.224542 110637 [Game] Tried to use shader Shader ‘vfx_decal_parallax_normalAO_emissiveColor’ with 2 passes on particle system Particle ‘NPC_Mercenary_shieldBearer_groundSlam_crackDecal_Parallax’. Particles only support single-pass shaders!
I 2024.12.16 15:34:18.074415 110846 [Game] VideoPrefs: texture quality limited to High (VRAM: 8059MB)
I 2024.12.16 15:34:18.074424 110846 [Game] VideoPrefs: texture quality limited to High (VRAM: 8059MB)
I 2024.12.16 15:34:18.074427 110846 [Game] == Resetting Sound Prefs to Default… ==
I 2024.12.16 15:34:18.074431 110846 [Game] == Sound Prefs Reset to Default ==
I 2024.12.16 15:34:27.000295 111981 [Game] VideoPrefs: texture quality limited to High (VRAM: 8059MB)
I 2024.12.16 15:34:27.000303 111981 [Game] VideoPrefs: texture quality limited to High (VRAM: 8059MB)
I 2024.12.16 15:34:27.000305 111981 [Game] == Resetting Sound Prefs to Default… ==
I 2024.12.16 15:34:27.000308 111981 [Game] == Sound Prefs Reset to Default ==

So everytime i click its throwing a texture and sound prefs change.
Im convinced those are occurring when i click because the game is registering the desktop for a nano second.

The good news is, if i can get it stable and bypass the bugs, the framepacing and FPS are screaming good like they were before blizzard bricked the game.
But there is only so much i can do on my end.
Here’s to hoping blizzard had every able body crunching since last patch.
My thoughts are if anything, they are OVER thinking the issues and compounding them due to intelligence. I say that because i KNOW they have seasoned talent at blizzard.
I just hope those are the people addressing this next patch.

Does it give any kind of error when attempting to launch the game? Or you hit the Play button on the Bnet launcher, the play button greys out and nothing happens?

1 Like

No error, just closes out on splash
I just put a different driver on to see if that would change.
Assigned to core 6/7
Assigned the pci bridge to core 6/7
Those cores lower dpc and give good through put.
I have got to be missing something required.
Ran the all in one for runtimes first thing after chipset drivers and gpu.
Set power setting with Powersettingsexplorer properly.
Maybe im missing dotnets…Will check.
Gotta be another driver i am missing, unless its utilizing something i disabled in device manager. Alot of those device/trees i do not use or have my system setup differently, but the only one that is new adding to the list of disabled was device composite enumerator. Going to also mess with memory compression a bit.

You’re messing with stuff that shouldn’t really be messed with all for one game. I get you like it, but really?

Does the event viewer say anything when Bnet crashes?

If you’ve done a fresh install - windows, drivers, the works - and D4 still isn’t firing up, then i wouldn’t bother. Clearly a patch has gone screwy and caused a conflict somewhere. Throw it in the too hard basket and hope next patch fixes it.

Blizz won’t care either way. They’ll give you a robotic piece of advice from a proforma and then say “It’s fine on our end…”.

Bnet is not crashing.
The game approaches splash and closes without error.
As far as “Messing with things that shouldnt be messed with”
I am quite familiar with what i am doing.
I have been doing this for over thirty years.
(I just forget things sometimes, thankfully the internet exists lol)
Event viewer throws nothing.
I usually never have any problems with this game.
Since last patch is what has prompted me.
It was time for a clean install again anyway.
I will get it working.
Just thinking i overlooked one of my usual settings in my freshinstall folder.
You are probably right though…Its just me banging my head on the wall, because of this last patch…It destroyed sanctuary.

Its likely something so simple that you’ve overlooked it.

Think back to recently - when the issues started. What changed? Did you update GPU drivers? Tried a rollback?

Did you install some new internet security suite? Install a game that has anti-cheat software at the kernal level?

These are the things that can affect games etc.

1 Like

Yeah it sucks cause i cant get Fenris to tell me anything.
Nor event viewer because it doesn’t register as a crash.
Just closes on splash.
Fenris just returns [Crash] User defined symbols path: C:\Diablo IV
when i crtl-f in the text file.

have you tried the ‘Run As Administrator’ option on the .exe ?

Without knowing about your system it is difficult to offer any advice. I have an Intel 14900k, 64GB DDR5 and an Nividia RTX 4080. I had issues with CTD about an hour in game consistently. I reverted back to the 561.09 game ready driver THEN I turned off system managed Virtual Memory by manually allocating 1 TB of VM EACH on 2 separate SSD’s. Since then I have been stable for as long as I want to play. 8-10 hours no CTD. As I did both at the same time I cannot attribute it to one thing. Hope it helps

The game closing at the splash screen might be caused by warden detection of your system behaving abnormally.

I’ll be honest and admit that I did not read the entire thread, but to me this looks on the surface like an over “tweaked” system not operating as it should.

I respect that you have been doing this for a long time, but I have as well. Started on a TRS-80 with a cassette drive :wink:

If you are going to customize your system to the point of manual tweaks to the windows registry, you kind of need to expect things will go wrong from time to time as most applications are built expecting windows to be a bit of a black box i.e. known input yields known output without having to know everything going on inside. When you start editing windows registry settings you are kind of taking on responsibility for ensuring the sum of your changes results in the same black box scenario,

1 Like

i just dont know what i would even do with my time if diablo 4 wasnt working. Maybe id be forced to go play another game, something good possibly, like poe2

This was my thoughts as well. I have very similar experience as the OP. Earlier versions of windows you could do this. The newer versions in the last decade or so it is hit or miss, usually miss. The most I do as far as registry is delete unnecessary entries left behind by uninstalled programs to avoid it getting too bloated. The tweak I posted is about as far as I go anymore as M$ treats everyone as they know nothing and re-enables anything you shut off with the next patch.

I used to love researching and ordering every bit of hardware and hand assembling and overclocking / tweaking for absolute max performance, but these days it’s easy to buy a high-performance machine off the shelf and have it be good enough to run every game on max settings without any extra effort.

Kinda like me wanting to custom everything on the straight six in my '76 Nova when I was 18, and not even wanting to open the hood of my A5 to add wiper fluid now lol

This is the most poorly optimized game I have ever played. Stop wasting your time trying to get it to work. The insanity that is the amount of time, detail, and nuance that went into trying to get the game to work on your system is commendable but even if you managed to prevail, the latency will remain. Forever and always. Atleast it doesnt consistently bring down your entire network like it does for me?

1 Like