dublea

PAGE_FAULT_IN_NONPAGED_AREA is pretty generic. You either have malware or faulty hardware. Check your ram, video ram, HDD, and scan for malware.

If you don't know your specs and your computer is a name brand, what is the make and model?

Since last week, I'm guessing when battleye updated to v1.200, I've been experiencing a very odd issue. When I close Dayz, the Program Compatibility Assistant crashes causing 10 other services to fail. It causes me to drop internet and it is only resolved by a reboot. At first I thought my USB wireless adapter was going out. I then grabbed another from work (different brand/interface and all) but the issue was still present. Here are the errors I've found in the order that fail: After this happened, even after I new wireless adapter was installed, I decided to perform a full system diagnostic. That night I ran memtest86 v4.20 till the next morning. It passed 8 times without error. I decided to take my computer to work and run some tests there. All but one of my hardware devices passed daignostic tests. I found that one of my HDDs was failing but this HDD was only a storage drive that had nothing to do with the game or mod. I still removed it from play and pressed on. When the issue was still occuring that night, I had lost my patience with it and performed a fresh install of windows. Re-installed the games and mod, still happened. My motherboard has some SATA III ports by Marvell. I moved my SSD raid off of them onto the SATA II Intel as the Marvell can have issues. Clean install of OS, games, and mod, still happened. I've since found that if I disable the PCA service, it has stopped happening. I'd rather have that service enabled but at this point I'm at a loss. I can not find anyone else who is having such a unique issue. It's puzzling to say the least.

BattlEye v1.201 has resolved this issue and you can now re-enable the PCA service.

If it were an nvidia problem, it would happen with other games too. So that can rule out that. I still suggest that you play around with Arma 2's resolution/refresh rates. As I stated before, wow did this to me while other games played fine. I had to run wow at 720p to make it disapear. But, on my computer LCD, it never did that.

Two hardware tests I would perform. Test the HDD that the game is installed on and your system's memory. As far as your HDD, find the manufacturers diagnostic tools. And, for memory, run memtest86. If you want a easy way of doing either, look for a ISO called hiren's. I think they are at v15.2. Verify that game and mod install too. Depending on where you obtained the game will depend on what options you have with that.

Be sure and set Launch Parameters too so that you utilise all of your available hardware.

Once upon a time when I played wow and tried to play on my TV, I had the exact same issue. Some games just don't play well with TV's. If it is supported, I'd play around with both the resolution & refresh rates.

Yes. I would recommend to have this service always set to automatic. This is only a temporary band-aid fix.

I was informed today:

SSD's do not help with FPS in gaming. They only help in loading times. And, if your setup is like mine, your games are not on your SSD to begin with due to the knowledge that there isn't a performance gain from it.

Good to hear.

? Lowering vram? Set it to the amount you have on your video card. As far as the -maxMem it is locked to 2047mb

You have not disabled the PCA service as indicated. You MUST set the Startup type to Disabled and apply AFTER you stop the service.

Is that the only service that is failing? Check your Application logs too for an error

I got an i7 and get ~65+ on avg. It only drops when there are more zeds/players than norm. Though I don't have antialiasing set that high. You are missing some things I would add to your launch parameters though. Here is mine: -cpuCount=4 -exThreads=7 -nosplash -nopause -maxMem=2047 -maxVRAM=1024 You may not be utilizing all of your cores or threads by not setting it.

See the list of services that fail? Check your Software and Event Log in Windows Event Viewer and see what is failing when you disconnect. Be sure that you actually set it to disabled as the service will start again if it stays set to automatic.

Here ya go

"go to your admin panel and under the map it will say edit database then it will say it on the left hand side" Source found in comments

Solution, one that I posted to your thread also ChatoicFarva. Disable the PCA service and that should resolve it till BattlEye can fix their program from killing it.

When you drop to DX9 from DX10, it doesn't use the same versions of shadders, AA, etc. You will always gain an FPS increase from doing it. Minor SLI load balancing is still there when not forcing it into DX9. I only gained about 3-5fps from doing it.

To my knowledge, the only way to enable SLI is to make sure you have the correct drivers/patch such as the EVGA SLI Patch. But, even when it is working, it only offers minor load ballancing as Arma 2 / OA is not optimized for SLI/CF. '-winxp' enforces DX9 and compatibility with older GPU drivers. That's about as much as that command does. I've only seen one other who suggested it, but when I tried it I never saw a noticable difference as compaired to DX10 while having SLI enabled. I later found this list of commands and what they actually do

I have your solution here. Currently have an open ticket with BattlEye. Possibly true, but it would happen even while playing. As it is happening when he closes the game, it's probably the PCA service being killed by BattlEye.

Have you set any addition launch parameters? That will make a huge difference in FPS. As an SLI users, Arma 2 does not benefit from it in any way. The game is just not optimized for it. So don't think another 680 will help. Here is are my launch parameters I have configured into dayz commander that gave me a 15-20fps increase: I have a core i7 w/ 12GB of ram and 2 GTX 580 SSC cards in SLI. I only get ~45-75fps with high settings with or without SLI. The game just isn't optimized that well but there are ways to improve it.

I agree. It would still cause the BSOD, and some happen so fast people don't see them. To pin-point it, we can look at the error it created. I find it can be easier to get the info from the BSOD msg than having someone look through their Event Viewer. Either would work though. We just need to find out what is being logged, if anything, as the point of failure. I always disable that feature for machines I build due to how fast newer systems reboot after dumping the info. So, I would suggest he do both, provide system specs and disable the auto restart w/ testing to see if he gets a BSOD.