[atmarkham]

Sometimes the new launcher will crash producing two errors... the first is...



Followed by this afterwards...



Yes I am running it as administrator...

[atmarkham]

Bumping this because it's almost 5 months later and still have not figured this out....

I would really love to know where this comes from. My game can run for days by itself but for past several months I get a memory error crash randomly whether it be live or beta version of minion. It can be 5 mins after login or it can be 5 hours after login. Sometimes It happens enough that I spend more time logging in then I do actually in. It's not my memory because I've replaced that. It's not my driver and/or card because I can switch from my Nvidia to an ATI and I still get it. Upgraded to an SSD and did a fresh install of Windows, the game, and minion. It ran great for about a day I think. No memory issue and then it reared it's head again (was probably just a patch of luck). No other software was installed. Reverted to a system restore point taken the day of installation (before it ran fine for almost 24 hours) with no luck. I had a PSU go out about a month ago so I decided to buy a new tower/PSU... The machine is practically completely different then the one when I first started this thread. The only things not replaced are the motherboard and CPU. FFXIV w/ Minion attached is the only time I get this error. No other game/application produces it. If there is some type of advanced debugging or something I can help with I'd be more than happy to cooperate whether that means allowing teamviewer access or whatnot. All I know is I'm tired of paying each month and bashing my head against the wall on this one.

---

Before it started I had been running Minion almost since release without any issues at all.

[Ace]

What is C,D,E,F? Are these all separate hardware hard drives or partitions on the SSD? The first thing I would check is the amount of virtual memory the operating system is using, and where it is located. For best performance/reliability, the amount of virtual memory should be (total amount of ram * 1.5) and the paging file should be located on the SSD, usually disk C.

[atmarkham]

At the time of the screenshot C D E & F were all separate physical HDDs. Now C is a 512GB SSD. The pagefile I believe has always been off the main drive . I changed it to min of 8gb and max of 12gb for my 8GB of ram and moved it back to C. I then ran the GUI launcher. This is what it's showing there....

[Ace]

I'd have to ask Powder what that error means specifically, but if you haven't the computer since you made that change, that would be my first task for you.

[atmarkham]

Haven't what since I made the change? Reboot? I did that when it said to.

[atmarkham]

This is probably the worst it has been.,, This is what my night looked like....

Code:

01:56:15 [V] ==> Lauching new FFXIV instance for character *removed* on server *removed*.
01:56:19 [D] ==> Finished startup sequence for character *removed* on server *removed*, received PID 7232.
02:37:18 [C] ==> Unkwn Error
02:37:18 [W] ==> Killing PID: 7232, time of day: 02:37:18.0487271
02:37:20 [V] ==> Lauching new FFXIV instance for character *removed* on server *removed*.
02:37:23 [D] ==> Finished startup sequence for character *removed* on server *removed*, received PID 3276.
03:16:06 [C] ==> Unkwn Error
03:16:06 [W] ==> Killing PID: 3276, time of day: 03:16:06.6200730
03:16:08 [V] ==> Lauching new FFXIV instance for character *removed* on server *removed*.
03:16:12 [D] ==> Finished startup sequence for character *removed* on server *removed*, received PID 2868.
03:32:35 [C] ==> Unkwn Error
03:32:35 [W] ==> Killing PID: 2868, time of day: 03:32:35.6737121
03:32:37 [V] ==> Lauching new FFXIV instance for character *removed* on server *removed*.
03:32:40 [D] ==> Finished startup sequence for character *removed* on server *removed*, received PID 7384.
04:21:06 [C] ==> Unkwn Error
04:21:06 [W] ==> Killing PID: 7384, time of day: 04:21:06.6324144
04:21:08 [V] ==> Lauching new FFXIV instance for character *removed* on server *removed*.
04:21:11 [D] ==> Finished startup sequence for character *removed* on server *removed*, received PID 7968.
04:57:20 [C] ==> Unkwn Error
04:57:20 [W] ==> Killing PID: 7968, time of day: 04:57:20.0448773
04:57:22 [V] ==> Lauching new FFXIV instance for character *removed* on server *removed*.
04:57:25 [D] ==> Finished startup sequence for character *removed* on server *removed*, received PID 6196.
05:00:25 [C] ==> Unkwn Error
05:00:25 [W] ==> Killing PID: 6196, time of day: 05:00:25.6435058
05:00:27 [V] ==> Lauching new FFXIV instance for character *removed* on server *removed*.
05:00:30 [D] ==> Finished startup sequence for character *removed* on server *removed*, received PID 7936.
05:13:47 [C] ==> Unkwn Error
05:13:47 [W] ==> Killing PID: 7936, time of day: 05:13:47.6104314
05:13:49 [V] ==> Lauching new FFXIV instance for character *removed* on server *removed*.
05:13:52 [D] ==> Finished startup sequence for character *removed* on server *removed*, received PID 3564.
05:35:01 [C] ==> Unkwn Error
05:35:01 [W] ==> Killing PID: 3564, time of day: 05:35:01.5243859
05:35:03 [V] ==> Lauching new FFXIV instance for character *removed* on server *removed*.
05:35:06 [D] ==> Finished startup sequence for character *removed* on server *removed*, received PID 4652.
05:54:44 [C] ==> Unkwn Error
05:54:44 [W] ==> Killing PID: 4652, time of day: 05:54:44.9951581
05:54:46 [V] ==> Lauching new FFXIV instance for character *removed* on server *removed*.
05:54:50 [D] ==> Finished startup sequence for character *removed* on server *removed*, received PID 8144.
07:05:46 [C] ==> Unkwn Error
07:05:46 [W] ==> Killing PID: 8144, time of day: 07:05:46.7822642
07:05:48 [V] ==> Lauching new FFXIV instance for character *removed* on server *removed*.
07:05:51 [D] ==> Finished startup sequence for character *removed* on server *removed*, received PID 3448.
07:26:06 [C] ==> Unkwn Error
07:26:06 [W] ==> Killing PID: 3448, time of day: 07:26:06.5971192
07:26:08 [V] ==> Lauching new FFXIV instance for character *removed* on server *removed*.
07:26:11 [D] ==> Finished startup sequence for character *removed* on server *removed*, received PID 6552.
07:43:45 [C] ==> Unkwn Error
07:43:45 [W] ==> Killing PID: 6552, time of day: 07:43:45.5089508
07:43:47 [V] ==> Lauching new FFXIV instance for character *removed* on server *removed*.
07:43:50 [D] ==> Finished startup sequence for character *removed* on server *removed*, received PID 7408.
08:38:35 [I] ==> Waiting 2 Minutes to relaunch *removed* .
08:40:24 [V] ==> Lauching new FFXIV instance for character *removed* on server *removed*.
08:40:27 [D] ==> Finished startup sequence for character *removed* on server *removed*, received PID 6620.

---

Also that last log was from an install of the live version that was a fresh install. Only alteration to it was I made a skillmgr profile for gathering shards along with a fresh install of EnhanceAssist.

---

Switched to Beta and had no problem setting up a fresh install. Only thing I changed was I added my mining skill profile from live. Configured it for mining and got this crash a minute or so after starting the bot...

Code:

Problem signature:
  Problem Event Name:    APPCRASH
  Application Name:    ffxiv.exe
  Application Version:    1.0.0.0
  Application Timestamp:    53d1d154
  Fault Module Name:    nvd3dum.dll
  Fault Module Version:    9.18.13.3523
  Fault Module Timestamp:    5315b426
  Exception Code:    c0000005
  Exception Offset:    005022f0
  OS Version:    6.3.9600.2.0.0.256.48
  Locale ID:    1033
  Additional Information 1:    5861
  Additional Information 2:    5861822e1919d7c014bbb064c64908b2
  Additional Information 3:    d1d9
  Additional Information 4:    d1d94a13d3609d6b740644c12508f581

[atmarkham]

Removed all Nvidia drivers from my system and installed the latest verison (was running an older version to test). Same nvd3dum.dll error.

[Ace]

The unknown error is usually because of a problem with the injected bot not being able to contact the auth server. What is your modem/router situation/setup? Make sure you don't have Geforce Experience features like optimal driver and shadow play running or anything, GExp is known for causing a lot of issues with minion. Also any third-party video features like EVGA's PrecisionX and the like can cause issues as well.

[atmarkham]

My modem\router is a Motorola SBG6580. My PC is wired directly into it. No other PCs are wired. On wifi there is 2 laptops, 3 smartphones, a tablet, and a chromecast. I doubt thou that the error has anything to do with connection as it's happening at the same interval as the nvd3dum.dll error unless the connection is causing the injected bot to fault the dll. I researched the error a little further and actually found a thread on nvidia's forums pertaining to FFXIV and this dll. While no one seems to know why it happens or a fool proof fix there was several things listed to try. One was to upgrade BIOS. I was already at latest from MSI so I downgraded with no success. Another was changing drivers but I am already sick of that. Another which happens to show promise was to change my TDR delay from 2 to 8.So far the game has been running three hours without a hiccup. Would still like to get to the bottom of it as the TDR delay change is only a temporary fix.