dsound.dll strikes back

Jyuki

Prima Undine
Guildcard
42008882
Hey, it's me again on this problem ! Already asked in the past but since it wasn't properly fixed, I figured I'd ask again, maybe someone got a clue now.

PSO just randomly crash to desktop and the issue is caused by DirectSound.

OS: Windows 10 LTSC 64bit (Fresh install)
CPU: Ryzen 5 1600
GPU: MSI GTX 1050ti 4gb OC
RAM: 2x8GB DDR4
MB: MSI Tomahawk B350
Drivers: Everything is freshly up to date
AV: Eset Nod32 (PSO is added to the exclusions)

Baguette error:
JZOxNJB.jpg


DE(r)P:
RxbMHvn.jpg


If someone have a clue on how to prevent that, you'll be my savior. <3
 
did you install nvidia audio (would try uninstalling or switching to it if you did)
 
Last edited:
did you install nvidia audio (would try uninstalling or switching to it if you did)

I did let the Nvidia's driver install all of its things, I'll try reinstalling only the display drivers.

Edit: Haven't crashed since the change, it might be the fix. I'll wait & see after playing more.
 
Last edited:
Worked fine since the change but I crashed again today, same error. I really wonder what causes this.
 
Could be Windows 10 not liking something you're changing and rolling it back on reboot? If I remember right, windows 10 updates everything through windows updates, even non MS related things, so maybe turn off windows update? It could be continually trying to update a driver its seeing as out of data but that isn't and its causing conflicts.
 
I can turn off updates for 35 days on LTSC but, there's nothing about any changes/updates in the logs. I can give it a try though. :D
 
Isn't that impossible on Windows 10?

I mean technically yeah, Microsoft can probably always just get new update servers or w/e the fuck they do xD most of the publicly known stuff is blockable either manually through cmd or by running that one exe that does it for you.
 
I seem to remember using this thing, which you used to be able to download from Microsoft directly:
https://ln2.sync.com/dl/572a29a70/ymyhm698-9pckg4ve-tw2irsxg-hxe2ixwb

To selectively disable W10 updates (by name) indefinitely. But I don't know if this even still works with more modern W10 installs, or if they stopped this utility from functioning. You don't want to use it too liberally, as you can bork your OS unless you know what you are doing with it (e.g: you block an undesirable W10 update, which later becomes a dependency of another update, and that future update breaks your OS in some / many ways). I found it handy but handle with care... not even sure if it still does anything

If Windows keeps altering files in certain folders, take permission of those folders away from Windows using something like:
https://ln2.sync.com/dl/7ad025ce0/pexcqhiu-bzcq6m89-3gzkcvkn-prgnxxw6

This is a registry entry that restores the old "take ownership" entry in the context menu. You can force take-over folders, then alter their permissions as you like. If a certain file keeps being deleted, take ownership of it and set it to read only or something

These utilities can be a bit OP if you don't know wtf you are doing so again, unless you are pretty confident probably don't bother
 
I think, even without Nvidia's audio (while, even with the box unchecked at install, the driver seems to hook up with my monitor https://i.imgur.com/aa1SpAD.jpg ), Windows 10 have default HDMI audio drivers:

T1a8D92.jpg


That being said, I've reinstalled PSO and it didn't crashed since then. But, it's too soon to say anything so, I'll keep playing and see if I get any crashes.
 
I just crashed so I investigated a little bit further and saw that Nvidia was, somehow, installed again:

upload_2019-10-16_15-33-24.png

Aswell as some generic Win10 drivers, I just deactivated both (uninstalling will just cause Win10 to reinstall anyway). I'll report again if I crash. :mad:
 
LTSC is an enterprise edition that only receive "stable updates" and give a lot more control on the OS/update schedule.

Everything else just work like any other Windows 10 versions.
 
Last edited:
Windows will install the update for Nvidia unless you turn off automatic driver installation. HDMI audio and Nvidia audio drivers aren't the same, though they have never caused issues for me either.

I doubt Windows 10 automatic updates are to blame. At least for dsound.dll and PSO. Honestly, access violations can be a huge pain in the ass. If you can't trace, it could be a lot of things. Do/have you...
  • Downloaded a new installer from Homepage and did a fresh install of PSO itself?
  • Tried running PSO outside of C:\?
  • Run any customized ogg or sound effects? Tried going without them?
  • (non-SSD only) Ran chkdsk?
  • Does disabling music or sound effects (not both) in the original options make a difference?
  • Ensured that you do use a Page File? (a lot of people will tell you not to use this if you have a lot of RAM. This is wrong.)
 
Downloaded a new installer from Homepage and did a fresh install of PSO itself?

Yes

Tried running PSO outside of C:\?

Nope, always using the C: drive. That's something I can test if it crash again.

Run any customized ogg or sound effects? Tried going without them?

Nope, it's a clean install (except for my custom HUD & addons)

(non-SSD only) Ran chkdsk?

Using a nvme ssd

Does disabling music or sound effects (not both) in the original options make a difference?

I have BGM volume to 0 but it's not disabled in the options. That's another thing to try if it crash again.

Ensured that you do use a Page File? (a lot of people will tell you not to use this if you have a lot of RAM. This is wrong.)

I do use Page File, Windows would freak out without one as it's hardcoded to use it (aswell as some softwares).
 
Windows 7, at least, works without a page file, but it's still a good idea to have one of a few MB, because it allows Windows to save bugcheck dumps. Without a pagefile, you'll have no record of what caused a BSOD.
 
You can still disable the Page file in Windows 10 (unless they added a new hidden one, its pretty much exactly how it is done in 7.) But just like in Windows 7, there are more reasons to keep it around than to disable it.

But I'm out of ideas after that. WinDbg it!?
 
Little update: I got a new Power Supply, a new CPU (Ryzen 2600) and even a new GPU (GTX 980) and still had crashes. I also did a few memtest and everything was fine.

Then I realized the only thing that didn't change between all the crashes was my antivirus, ESET Nod32. So I uninstalled it and started using Windows Defender. So far, no crash. I'll update if it happen again.

Nod32 is using some host intrusion protection for softwares, I suspect it could've been unstable for PSO, not sure yet. I could've tweaked around the options but I was too lazy/annoyed and went straight for an uninstall. :D
 
I would completely ditch modern nod32 tbh. For various reasons, but a lot of those being it simply didnt stop shit and it caused more headaches with whitelists than it helped anyways.
 
I would completely ditch modern nod32 tbh. For various reasons, but a lot of those being it simply didnt stop shit and it caused more headaches with whitelists than it helped anyways.

To be honest, I've used nod32 since 5 years now and didn't encounter much issues. But I don't really visit or download shady stuff in general so, I always trusted it (I can't remember the last time I actually had a virus).

I was skeptical about Defender at first, it was the reason I was using nod32 but seeing that it hold well, even compared to the most expensive solutions (not counting internet security, which Defender lacks), I'll give it a try and probably never install nod32 again, as I loved MSE.
 
Defender presents its own set of issues sometimes, but its all depending on what you're doing and what you're playing. So if its working good for you here, more power to it. Though, As it's been said in the past in troubleshooting, if you know what you're doing and where you're going its sometimes better to not even bother with an AV. Just turn it on around w/e porn sites you're visiting lol.
 
Back
Top