Window crash at 3:57:59 everytime

Everytime windower has been running for 3 hours 57 minutes and 59 seconds it crashes, every single time, that is the exact time it crashes at. It has been doing this for almsot a full year now, i was using asheeta as a replacement but now asheeta also doesnt work the way id like it to so im stuck between a rock and a hard place.  Restarting my game everytime before a delve or whatever just so i dont time out midway through is more annoying then d/cing midway through. 

I beg whoever knows how to fix this to fix it please. 

It doesnt matter if i running addons, or not running addons, it doesnt matter if im completely afk or active, every 3:57:59 it crashes. no console text pops up, nothing. just crashes. 

That is very strange. Can you provide us with a crash dump?

This is the link to my dmp file

https://kodytehnolog...5ni83zjb95esdsg

I'm currently unable to look into this further, but it's definitely crashing in Hook, and the dump looks useful. With any luck we'll be able to sort this out soon.

Unfortunately not too useful... it's a crash in the IPC handler, but I cannot see why it's crashing.

Well at least you know it's in IPC. Add that to the list of IPC problems to fix

ah, so there is nothing i can do for this?

OMG so i have this same problem!!! 

There is no fix?

I have tried uninstalling windower and final fantasy then re-installing but didn't work...

Updated all my drivers, windows updates, cleaned up junk...

I'm about to resort to a full clean wipe of my laptop to maybe try and get it working like it used to...

PLEASE HALP!

ok i have a few questions for thoes with these issues

1. are you using any other apps when this crashes

2. what plugins/addons are you using

3. are you playing on the live ffxi servers not a private ffxi servers

i ask because i do not have this issue but the above could be involved

What program or way do you use to look at the windower crash dumps?

Since we have the source code, we can match the crashing code location to the source code (we just use Visual Studio for that). Unfortunately it's not always helpful, since crashes may not be in our code, but SE's code (even if it's something caused by us). Hence crash dumps are not always very telling of the underlying problem.

Well I meant how do I look at them so I can post/show you guys it, to see if there is a solution for my issue.

You need WinDbg (which comes with the Windows SDK) or Visual Studio to open .dmp files. However, without the debug symbols for Windower (they're not publicly available, sorry), you won't be able to do much with them. Instead of trying to open them yourself, you should upload them somewhere, and give us a link so we can download them.

I posted my crash dump in my topic if you guys want to take a look at it. curious if you guys can do something about it or not.