It says faulting module on my C drive for d3d8.dll. There isn't a file there. When I try to run microsoft's latest DX installer it says my computer already has a more upgraded version.
I do not use DGVoodoo, I also just uninstalled Reshade, but still have the proxy D3D8.dll in my e: drive, the POLviewer directory. Just nothing in the C: drives system32 directory.
Should I put one of the proxy D3D8.dlls in the system32 directory? It seems weird because this just started happening (I didn't change anything beforehand).
Edit: This has been happening (not at the same time) since 9-23-2022, so for 5 days. The other 2-3 times on the 23rd, 24th, and 25th (twice), it's been random times, so I'm not sure if the time for the last 3 days is just a coincidence (pretty amazing coincidence if it is).
Even on 9-23, the first crash, it was the same thing:
At first the error was d3d8.dll in my playonlineviewer folder for the beginning crashes (crashes have been happening a few days now). I started researching it a little bit, and found out about the proxy. I then did the basic proxy (this was 2 days ago) where you just put the d3d8.dll in your playonlineviewer folder, and the error switched to this. I figured maybe I can do reshade because it appears to be a more up to date thing, but it didn't help (last night), and since I was only using it for the proxy, I uninstalled.
I haven't checked tonight if it will crash, it's been working perfectly all day so far.
I'm going to update my first post with correct up to date info.
I guess my main question is, why does it say there is a fault in a module that doesn't exist, but I haven't had it apparently for quite a while. Why is it just starting to say that now?
Of course I do help with anything to get this fixed, but it's just weird.
you definitely need the file, it crashing could be your gpu driver crashing, it could be a multitude of other things, especially if you AREN'T using a proxy of somesort.
As for it listing system32: well that is the windows folder, my guy.
Should I put the d3d8.dll proxy there, or a regular directx8.dll in the system 32 folder? I'm using 64bit windows 10.
Personally I wouldn't mess with it.
If you keep experiencing crashing the fellas over on the windower discord know their stuff, I'd say under #ffxi-support would be the right place to ask if it continues.
Should I put the d3d8.dll proxy there, or a regular directx8.dll in the system 32 folder? I'm using 64bit windows 10.
Personally I wouldn't mess with it.
If you keep experiencing crashing the fellas over on the windower discord know their stuff, I'd say under #ffxi-support would be the right place to ask if it continues.
Thanks guys, that's what I was thinking. It seems like such a weird problem.
Okay, so this is interesting. I was playing last night finishing up Adoulin Survival Skills, and got to Kamihr drifts where you need to load in Vanilla FFXI to get past the cutscene.
Well, I did that, and finished up my survival skills, then just went back to Bastok Markets exit and left my character there (I never reloaded the game with windower so was still in Vanilla FFXI), and then it crashed again (but a different time of night, so time has nothing to do with it I guess) but it caused an interesting fault:
Does the above mean, the offending file is the pol.exe in the playonline viewer folder (which I thought was windower) but it caused the "Vanilla" ffximain.dll to crash?
Is there something wrong with my pol.exe in the playonline viewer folder, and if there is, how do I fix it? (check files has already been done and found no faults)
For what it's worth I also get these every few days at least and have been for quite some time (2+ years). Doesn't seem to matter what I've been running but the error is almost always the one above.
I don't think this has ever happened while I've been actively playing, seems to happen only when I'm afk and sitting in jueno or mog house overnight.
Yes. How interesting. This just started for me earlier this week. I was thinking also researching a bit more about reshade. I seem to remember trying something that was going to alter my pol.exe at some point.
So Yvan, you actually do have a d3d8.dll in your regular old windows/system32 folder, and you're still getting the crash. So that kind of answers my first question of do I need the file there. Is that your "original" install location? Have you ever had corrupted files in that location, re-imaged it, or anything?
The only other thing I can think of is I re-imaged my hard drive (I've done this multiple times in the past and it's always worked perfect), to an SSD of the same size, but that's where my ffxi install was. The game has worked perfectly fine up until earlier this week, once again, so I wasn't thinking it was the image that may have corrupted something, or a registry, or something like that.
I'm REALLY TRYING HARD to not have to reinstall. And just fix this issue.
I reinstalled a maybe a year ago and upgraded to windows 11, but was still getting these errors before then. No idea if the file was present in system32 at that time.
Got it fixed I think. At least it hasn't happened for the last 4 nights or so.
The problem was a reshade installation, and an atomos installation of the d3d8.dll. On the windower discord, they have a dgvoodoo installation that provides very nice instructions, and fixed all my issues.
It says faulting module on my C drive for d3d8.dll. There isn't a file there. When I try to run microsoft's latest DX installer it says my computer already has a more upgraded version.
I do not use DGVoodoo, I also just uninstalled Reshade, but still have the proxy D3D8.dll in my e: drive, the POLviewer directory. Just nothing in the C: drives system32 directory.
Should I put one of the proxy D3D8.dlls in the system32 directory? It seems weird because this just started happening (I didn't change anything beforehand).
Edit: This has been happening (not at the same time) since 9-23-2022, so for 5 days. The other 2-3 times on the 23rd, 24th, and 25th (twice), it's been random times, so I'm not sure if the time for the last 3 days is just a coincidence (pretty amazing coincidence if it is).
Even on 9-23, the first crash, it was the same thing:
