Stuntz

Nothing noticeable, though there's zero reason for it locking to 59 in the nvidia control panel.

It won't be refresh rate related, at least it shouldn't be. What monitor is it that sets to 59 out of interest?

Still looks like a picmip setting is screwed. Are both your in-game resolution and rendering resolutions set to the same?

I believe it was rocket that posted some time ago that there wouldn't be a way to currently disable mouse accel, due to arma being a simulation (the way you can't turn near objects and whatnot). I don't have the exact post on hand, but I believe it said something along the lines of fixing the acceleration problem so that it's more user-friendly is not as simple as toggling it off (it'd harm the "feel" of the game as it were). Instead, they would have to redesign the entire input system, something which i think(??) he mentioned was in its initial stages. So I'm afraid for now you'll have to live with it sadly. But try turn down sensitivity ingame to extremely low, and smoothing all the way down. There's also: http://donewmouseaccel.blogspot.com.au/2010/03/markc-windows-7-mouse-acceleration-fix.html Some follks have felt an improvement with that. Might be worth a try.

Hey, In alpha, getting stuck in the occasional rock/wall/room happens. Best way to fix it is to get to the nearest wall, press your vault key (default: V), and as the animation moves forward, log out of the server. Log back in and repeat a few times until you get through the wall, the timing is rather tough. You should eventually get out that way. Frustrating I know.

What driver version are you running? An older driver (311.06) had an issue with lod/picmip in some games, forcing them extremely low.

Ok, 1st things 1st, in your nvidia control panel, is there a setup/profile specific for dayz? If so, delete it. If not, can you tell me what your 3d settings are at in there?

60c for your gpu under load is absolutely fine. Not the source of the issue. What driver version are you on?

Getting to the source of a bluescreen requires a few things: System specs (including psu) Overclock (frequencies and voltages!) Driver versions/OS A copy of the .dmp file created by the BSOD would be nice too.

It's the rabbits, the rabbits I tell you! (I swear I'm not crazy, I've seen things, man...) I sh*t you not. For some reason the rabbits you see in between the grass and outside houses make zombie/eating/drinking sounds. Reloading noises are made when someone with a weapon joins a server, dead giveaway.

On my side it's all wired, no wireless nonsense. Router/firmware is well up to date. As for multiple refresh, it wouldn't happen so much if there was a way to show what time of day the server was before you joined. Joining 4-5 night servers in a row will invariably result in multiple near back-to-back refreshes (you don't want to join a server with 20-30 people to try and gear up just because it says 24/7 day time after all).

Happens to me too! I've seen a couple of threads on this. Once the server list stops refreshing, my net drops entirely, like my router has been ddos'd/flooded lol. For the sake of reference I'm on fibre optic cable, 200mb down/20up.

I should mention that I'm on a fibre optic cable 200mb down/20mb up.

It happens to me too, after refreshing the server list and moving to a new server, my net completely drops, takes a few mins for it to come back following whatever the game does.

I get (what I'd consider to be) awful fps in the SA too. 25-30 in cities, 35-40 in forests. Specs: i7-4930k @ 5.1GHz (all cores), Watercooled 32GB ddr3 2133MHz r9 290x @ 1100/5800 Corsair force GT 240GB for windows/steam Win 7 ultimate x64 Out of game settings: cfg- GPU_MaxFramesAhead=1;GPU_DetectedFramesAhead=1;shadowZDistance=200;preferredObjectViewDistance=1000; Launch options--CpuCount=6 -ExThread=11 -maxVRAM=4095 -maxMem=32768 Ingame settings- 1080p res Vsync Disabled Texture Detail: Very high Texture Filtering: High Objects/Terrain/Clouds: Very high Shadows: Low AA/Alpha to coverage: Disabled Edge Smoothing: Disabled HDR: Very Low Ambient Occlusion: Enabled Post processing: High Bloom/Radial blur: Minimum Some options up higher for sure, but the more demanding ones (aa/edge smoothing/shadows/hdr etc) turned down. Cpu temp tops out @ ~70c, gpu about the same, so no chance of thermal throttling. No unnecessary background crap running.

It very much depends on the nature of the bluescreen. If it remains as a 0x116 error, like the one you posted, then it is still down to the vid card drivers *or* slightly low pch voltage. (also a chance that the lower quality psu is not feeding the correct voltage, even the top psu's tend to be off by a few thousandths of of a volt, lower quality ones I've seen be as far off as a tenth of a volt output the vCore, and in such a case that'd kill your overclocking potential.

1.29 is fine, On the haswell's I'd be wary about going over 1.35v even on a decent closed loop watercooler. Depending on your sample luck, you might be able to hit 4.2GHz @ 1.25v, some can even do it at stock if really lucky. @ 1.3v some would even be able to get 4.4 or 4.5 from it, but that's pushing it. Regardless, that seems fine. There's plenty of voltage headroom in modern boards/cpus, just make sure everything you do is incremental, no big jumps. A few blue screens are nothing to be concerned about when trying to get an OC right. I've got my 4930k running @ 5.1GHz watercooled, 1.45V. Took a lot of fiddling to get everything stable, I needed a 1.2v PCH for that, and a 1.88v QPI/PLL.

The basics of it is: IOH stands for Input/Output Hub, something akin to the older style of northbridge. Though someone correct me if I'm wrong - i believe from sandybridge chipsets onwards its PCH (Platform Controller Hub) now, not IOH. Functionality remains the same regardless, in essence. I'm guessing your issue was there if a bios reset fixed the issue. If you get further bsod's, consider the drivers to be at fault. Either way, a pre-OC'd pc should have been burn/stress tested to ensure the voltages were correct. No 2 chips/boards are identical, voltages that work for one won't necessarily work for another board/chip of the same model (only need to look at the massive variance in results of people's haswell overclocking to see that). The issue would have been readily apparent. The pch 1.05v should be (estimating) ~1.08-1.085v, and the PCH 1.5v should be no higher than 1.525. Given that your BSOD's were only occuring under heavy stress (dayz in this case), I'd guess a small tweak would have done it.

I'm guessing they only upped the vCore voltage and nothing else. Left the IOH @ stock, causing the issue.

0x116 indicates either a low IOH voltage, or an overclocked GPU failure. Is that 7770 oc'd? VIDEO TDR ERROR suggests a display driver crash that windows couldn't recover from. Try uninstall your graphics driver, reinstall the newest ones. Make sure your directX runtime is as up to date as possible. Should your current drivers be the most up to date ones, try rollback to catalyst 13.10, they were quite stable on the 7000 series cards.

http://www.resplendence.com/download/whocrashedSetup.exe download that, install, click analyze, and copy/paste what the crash dump analysis says :P Works too ^^ Edit: specifically the bugcheck code line!

C:\Windows\Minidump any of the recent ones in there will do.

Aye odds are its a low qual psu, but if you wanna post any of the dump logs/files, might be able to narrow down further, especially on an asus board, they're very specific in their blue screens compared to most. Can narrow down to the voltage giving the issue on them.

Can you post the full bsod message, error code included? Or just upload the dmp file so I can get a look at it? Might be able to narrow down the source of your crashes. Would also help knowing what mobo you're on.

My specs: i7-4930k @ 5.1GHz (watercooled) 32GB ddr3 @ 2133MHz r9 290x @ 1140MHz core / 6000MHz memory Dayz/OS installed on a 240GB Corsair Force GT SSD. Settings: 1080p Vsync: Off Tex Details/Filering: Very High Objects/Terrain/Clouds: Very High Shadows: Low Antialiasing: Disabled Alpha to Coverage: Disabled Edge Smoothing: Disabled HDR Quality: Very Low Ambient Occlusion: Enabled Post Process Quality: High Bloom: Minimum Rotation Blur: Minimum CFG specific Changes: preferredObjectViewDistance=1000 GPU_MaxFramesAhead=1; GPU_DetectedFramesAhead=1; Launch Options: -CpuCount=6 -ExThread=11 -maxVRAM=4095 -maxMem=32768 Top out @ 45fps in the wilderness, 30ish in cities, in the 20's with weapon out running around with other people. I Know dropping shadows to off and disabling ambient occlusion nets me another ~10 fps, but the loss in detail is simply not worth it - and the pc should be more than capable of handing the game with most of the intensive settings low/disabled. And I realize that some people would consider that (more than) playable, but I fear for mid range pc performance as more features are implemented (player crafting, wildlife, increased Z spawns, vehicles, more loot spawns, potentially enhanced weather effects etc). These will all have negative impacts on performance. Without some serious optimizations, I'm unsure if dayz will be playable for the majority.