Freeze/Crash & BSOD issues

[Vili]

Have you tried MSI Afterburner or various other brands versions of the Rivatuner? It's not crashing for me (right now) with it loaded.

Booth EVGA Precision X and MSI AB is made by the same person. So I would be surprised if switching made a difference.

[KisaiTenshi]

Booth EVGA Precision X and MSI AB is made by the same person. So I would be surprised if switching made a difference.

You'd think.

I downloaded AB 3 beta to see if I could cause some crash mayhem. There is a new Intel Quicksync video capture feature that I enabled and... well let me explain something weird....

The first time I enabled it, everything that could go wrong did software-wise. I had to enable the HD4600 by plugging in another monitor, which then threw out my aspect-ratio settings on the video driver. So I fixed that, but then when I ran FFXIV it sat there for at least 5 minutes with a "black screen" before anything happened. I ticked on the video capture, and boom, game freezes. Then I tried to reload the game, not-a-chance, error 2002 which I had never ever seen before, So I reboot

The second time I launched FFXIV first, before MSI AB and before extending to the second monitor. Game loads up instantly. So I go flip the monitor back on and load MSI AB. Game works just fine, turn on capture, works just fine (actually works this time) , at least until I hit the screenshot button while the video was recording. Then it locked up. So I'm now checking to see if I can crash the game by just leaving MSI AB beta running.

So for reference my AMD HD 7770 is the primary monitor, and the Intel HD4600 is powered on and running on the second monitor but is only on to enable Intel Quicksync, nothing is actually on it but the windows background. I reasonably suspect that some crashes might be from it, but as I said in other threads, not all crashes with the same symptoms are caused by the same thing.

[Adament]

Well, I’ve spent about a total of 10 hours researching this topic before I had even stumbled upon this thread. I’ve checked about everything everyone else has on this thread, heat, RAM, Video stability, drivers, DX, etc.

I have come to conclude that this is not a hardware issue, as far as faulty hardware is concerned. There is no commonality between manufacturer, driver versions, or heat.

It does not seem to matter what manufacturer you are using, be it AMD or Intel Cores, ATI or Nvidia Graphics.
After reading all 22 pages of this thread I have found one commonality as far as I have seen.

64 bit systems.

I can’t be sure that everyone posting is running 64 bit systems, but as far as I have seen, everyone who has posted their specs are running 64 bit systems with more than 4 gigs RAM (RAM + Video Memory).

This may be a combination of the 64 architecture, and RAM in excess of 4 gigs (RAM + Video RAM). 32 bit systems will only use 4 gigs of RAM regardless of what you have in it.

Please post a reply if anyone is running 32 bit OS with this problem.

My suspicion may be that FFXIV is writing to the memory address reserved for the drivers. The driver is running fine>>FFXIV writes to the reserved address space >>driver goes back to use it>> Driver says “WTF? “ = CRASH

The only OS I have to test this with is XP, which I am not willing to install to test my hypothesis.

I really feel for the posters that built new rigs for this game, a slick system should not be an Achilles heel.

AMD FX 8120 8 Core
Gigabyte GA-990FXA-UD3
16GB Corsair
ATI HD 7770 X2 Crossfire
Windows 7 X64 Pro

[C-croft]

Well, I’ve spent about a total of 10 hours researching this topic before I had even stumbled upon this thread. I’ve checked about everything everyone else has on this thread, heat, RAM, Video stability, drivers, DX, etc.

I have come to conclude that this is not a hardware issue, as far as faulty hardware is concerned. There is no commonality between manufacturer, driver versions, or heat.

It does not seem to matter what manufacturer you are using, be it AMD or Intel Cores, ATI or Nvidia Graphics.
After reading all 22 pages of this thread I have found one commonality as far as I have seen.

64 bit systems.

I can’t be sure that everyone posting is running 64 bit systems, but as far as I have seen, everyone who has posted their specs are running 64 bit systems with more than 4 gigs RAM (RAM + Video Memory).

This may be a combination of the 64 architecture, and RAM in excess of 4 gigs (RAM + Video RAM). 32 bit systems will only use 4 gigs of RAM regardless of what you have in it.

Please post a reply if anyone is running 32 bit OS with this problem.

My suspicion may be that FFXIV is writing to the memory address reserved for the drivers. The driver is running fine>>FFXIV writes to the reserved address space >>driver goes back to use it>> Driver says “WTF? “ = CRASH

The only OS I have to test this with is XP, which I am not willing to install to test my hypothesis.

I really feel for the posters that built new rigs for this game, a slick system should not be an Achilles heel.

AMD FX 8120 8 Core
Gigabyte GA-990FXA-UD3
16GB Corsair
ATI HD 7770 X2 Crossfire
Windows 7 X64 Pro

Should this even be happening as it is running in WoW mode. I would think Windows would handle that. Not sure myself, just asking.

[KisaiTenshi]

Should this even be happening as it is running in WoW mode. I would think Windows would handle that. Not sure myself, just asking.

64bit OS turns on DEP by default, but only for the OS. I have DEP enabled for all applications and the only program that has a fit about it is recent versions Hackshield used by Nexon.

[Adament]

Should this even be happening as it is running in WoW mode. I would think Windows would handle that. Not sure myself, just asking.

I quite honestly couldn’t find a straight answer for that one. I checked the MSDN dev site and all I found were some bland explanations of memory usage, just dirty. Dirty memory switching (sad face)

I’m no Dev, but I am a fairly good trouble shooter, this one is beyond me, unless I want to spend several years switching from Net Admin to Programmer. They will fix it in time, or I’ll just get tired of it and stop playing, then I won’t care anymore.

I wish I had something more, but darn near everyone who has posted here has tried about all there is that a non Dev can do.

Talk around in game within your free companies; ask people if they are using a 32bit OS and if they have problems with the BSOD/Black Screen/AppCrash problem. This will at least narrow the possibilities. Devs don’t have the time or resources to test every theory.
I did look into limiting my RAM to 4 GB or less on a 64 bit OS that is using an excess, but I haven’t found anything yet. I know how to hack a 32bit to use more, but not a 64 to use less.

I still think it’s an issue with the conversion of 32-64bit memory addressing, this is completely conjecture on my part.

I was just trying to throw the FFXIV Devs a biscuit if they didn’t know already, chances are they already know about whatever it is and are working on it, but these things take time.

If we can narrow it down to what we know it is not, they will have more to go on.

[Vodomir]

In the majority of cases, it seems people experiencing this specific issue, exclusive to FFXIV, have high end CPUs and GPUs.

I can’t be sure that everyone posting is running 64 bit systems, but as far as I have seen, everyone who has posted their specs are running 64 bit systems with more than 4 gigs RAM (RAM + Video Memory).

This may be a combination of the 64 architecture, and RAM in excess of 4 gigs (RAM + Video RAM).

I guess I can safely discard both theories as a myth, as my gf suffers from the same gfx driver reset, bacl screen and BSOD issues and is actually running a mediocre system (an old Athlon II X4 with an ATI Radeon HD4650 gfx card) with no more than 4 GB of RAM. She does however run Win 7 64-though, but that's what I run, too, without any of those issues.

[Blaez19]

Frustrating. I definitely don't have the technical know-how to solve this mystery...but I'm sure as heck hoping those at Square-Enix can tackle it eventually. :-/

I've had the best luck running Nvidia's 326.80 drivers. With those, I just get a crash to desktop. With the latest Nvidia drivers that changes to a BSOD. The change in behaviour suggests that it could be driver related but I really know zilch about this stuff. At this point I'm with most others here in thinking that it's an issue that will take some adjustment on SE's end to fix.

[Adament]

I guess I can safely discard both theories as a myth, as my gf suffers from the same gfx driver reset, bacl screen and BSOD issues and is actually running a mediocre system (an old Athlon II X4 with an ATI Radeon HD4650 gfx card) with no more than 4 GB of RAM. She does however run Win 7 64-though, but that's what I run, too, without any of those issues.

Windows calculates RAM @ RAM + Video RAM, so, you GF maybe running more than 4 Gigs (depending upon the MB/Graphics Card {dedicated or no}, some laptops share and some don't ).

I did talk to some people in my free company, and 1 person out of 6 (I think) that ran 64 bit did not have a problem. I would have questioned further on the specifics of his system, but I'd rather be playing. You can check your total RAM by doing a dxdaig, just type dxdiag in the search bar of your OS, then ad your system memory to your display memory= total RAM; as far as windows is concerned.

That would be interesting though if the RAM was 4Gb or less on a 64 bit system, that's something I'm unable to do. I guess I'm just looking something in common with this particular problem. The wild card seems to be, who doesn't have this problem, that also uses similar equipment/software as everyone else.

Sometimes its crunchy sometimes its slimy, but its always Fresh!~

[Adament]

Oh, another thought I had almost missed. DDR3.

The FC people I talked to were all using DDR3, but it maybe nothing. Anyone using DDR2 for RAM on your MB's with issues?

This is just a fart in the wind, but it was brought up.