Hello theklondike.
Do you mean that you were unable to look around upon pressing the alt key? Or just by using the num keys? Also, have you experienced this issue on the 0.62 version or the 063 version?
Regards,
Geez

Hello Lafayett3 and thank you for the report.
We have confirmed the issue and it has been scheduled for a fix.
Regards,
Geez

Hello michael.schalzl and thank you for the report.
Just to be sure, this issue has occurred on the 0.63 experimental version? And do you remember on which server/s by any chance and the approximate time of the occurrence?
Regards,
Geez

Hello Behemian and thank you for the report.
We have been testing this issue thoroughly but so far we were unable to reproduce it, though we are aware of some situations during which magazines may become stuck in weapons. The next time you experience this issue, can you try to take note of the specific actions/details you have done prior to the issue occurring (Such as the weapon placement ((hands slot / back slot)), the placement of the magazines, the way you have loaded the magazine ((through quickbar / drag and drop)) etc.) and let us know under this ticket?
Regards,
Geez

Thank you for the update.
We are aware that such issue can occur and it is being worked on internally.
Regards,
Geez

Hello again.
If you are still experiencing this issue frequently, can you try to re-install the game and let us know if you are still experience the issue even upon doing so?
Regards,
Geez

Thank you for the update.
Please let us know under this ticket in case the issue re-appears in the near future.
Regards,
Geez

hello emrsmrsli.
We have restarted the servers, do you still experience the issue?
Regards,
Geez

Hello mhouri22.
We have moved the character for you and it should not be stuck any more. In case there are any issues with the character still, please let us know under this ticket.
Regards,
Geez

Hello Zaxus.
We have moved the character for you and it should not be stuck any more. In case there are any issues with the character still, please let us know under this ticket.
Regards,
Geez

Hello e_xil and thank you for the report.
The issue with being unable to raise weapon/arms at walls is known to us and is currently being worked on.
Regards,
Geez

Hello mysuccess and thank you for the report.
We have confirmed the issue and it has been scheduled for a fix.
Regards,
Geez

Hello worthlesstediousaccount and thank you for the report.
Do you still have an issue with being unable to connect to this particular server? We have tested this internally but so far we have been able to connect to the server.
Regards,
Geez

Hello everyone.
This specific crash has been fixed and should no longer occur on the 0.63 version. However, keep in mind that crashes with similar error messages may still occur.
Regards,
Geez

Hello TikTactical.
This particular crash has been fixed for the 0.63 version and should no longer occur. However, keep in mind that crashes with similar error messages may still appear.
Regards,
Geez

Hello TomZ and thank you for the report.
Have you been experiencing this issue always on the 0.63 version or has it started to occur from specific date/update? Were there any software changes on your computer since the issue has started to occur? Have you tried re-installing your video drivers to see if it has any effect on the issue? And is your hardware running at optimal temperature when this issue occurs?
Regards,
Geez

Hello TeamDeer and thank you for the report.
This is an issue we are aware of it, it has been fixed internally and should be fixed on Steam in the future.
Regards,
Geez

Hello makija89 and thank you for the report.
This is an issue we are aware of and it is scheduled for a fix.
Regards,
Geez

Hello TeamDeer.
The issue has been fixed internally and should be fixed on Steam in the future.
Regards,
Geez

Hello molsHot.
Both of the issues were fixed internally and should be fixed on Steam in the future.
Regards,
Geez

Hello again.
Do you still experience this issue on the latest experimental version?
Regards,
Geez

Hello Uncuepa.
Have you experienced this issue on the current versions as well?
Regards,
Geez

Hello Vespi.
Are you still experiencing this issue on the current experimental version?
Regards,
Geez

Hello Checkpoint and thank you for the report.
Were you able to load any magazines into the weapon prior to experiencing this issue, or have you found the Mp5 in this state already? (With magazine attached but unable to remove it or replace it)
Regards,
Geez

Hello RipTideHoS and thank you for the report.
Have you experienced this issue on the 0.62 version or the 0.63 version? And can you please provide us with the IP of the server where you have experienced the issue?
Regards,
Geez

Hello bby and thank you for the report.
Do you have some kind of controller connected to your computer by any chance?
Regards,
Geez

Also, can you please add a -dologs launch parameter to the game (right click on the game in Steam library, go into preferences and under general tab select "SET LAUNCH OPTIONS", then type in -dologs), launch the game and wait until the error appears and then send us the .RPT file from your C:\Users\*username*\AppData\Local\DayZ folder? (Make sure to remove all contents of the folder prior to launching the game so the logs are as accurate as possible).
Regards,
Geez

Hello Screw77.
Do you experience this issue on both 62 and 63 versions?
Regards,
Geez

Hello Sealgaire and thank you for the report.
This is a known issue and it is scheduled for a fix.
Regards,
Geez

Hello mysuccess and thank you for the report.
Does the issue persist even upon removing the launch parameters you have set up and using the lowest possible configuration in video options (while leaving the configuration files as default)? Also, do you experience this issue on both v62 and v63? Have you checked if your hardware temperature is optimal while the game is running? And is the game being ran on correct GPU, considering you have two according to your dxdiag file?
Regards,
Geez

Hello Brizzle0705 and thank you for the report.
This is a known issue, it has been fixed internally and will be fixed on Steam in the future.
Regards,
Geez

Thank you for the update.
I am going to set this ticket as Resolved, but feel free to let us know here in case the issue occurs again.
Regards,
Geez

Hello Uncuepa and thank you for the report.
Do you also experience this issue on the most recent versions?
Regards,
Geez

Hello srgtmalarki and thank you for the report.
The issue with the blue screen crashing should be fixed as it has been caused by issues with the battleye client. In case you are still experiencing the issue, please let us know under this ticket.
Regards,
Geez

Hello GenS and thank you for the report.
This is a known issue, it has been fixed internally and will be fixed on Steam in the future.
Regards,
Geez

Hello mysuccess and thank you for the report .
This is an issue we are aware of and it is scheduled for a fix.
Regards,
Geez

Hello mysuccess and thank you for the report.
This is an issue we are aware of and it is scheduled for a fix - the primary ticket can be followed here https://feedback.bistudio.com/T128680. In case your active character is still stuck and you need us to move it from the bus, please post the link to your Steam profile in here and also the server IP.
Regards,
Geez

Hello AdrianX and thank you for the report.
This is an issue we are aware of and it is scheduled for a fix.
Regards,
Geez

Hello ethanms08 and thank you for the report.
On which specific day has this issue occurred? And do you remember the approximate time of the occurrence? Also, have you experienced the issue again since writing this report?
Regards,
Geez

Hello Screw77 and thank you for the report.
If you navigate into your C:\Program Files (x86)\Steam\steamapps\common\DayZ\Addons folder, delete the gear_optics.pbo file + gear_optics.pbo.dayz,bisign file and verify the game cache in Steam, does the issue still persist?
Regards,
Geez

Thank you AussieCleetus.
The issue with the vehicles respawning upon restart should be resolved now. Have you experienced the issue again over the weekend?
Regards,
Geez

Hello nzmat and thank you for the report.
The inventory and swapping system is still WIP and subject to changes. We are working internally to improve the system and to address the issue you have mentioned for the future stages of development.
Regards,
Geez

Hello ScrewYouThatsWhy and thank you for the report.
This is an issue we are aware of and it is scheduled for a fix.
Regards,
Geez

Hello michael.schmalzl.
This issue was possibly caused by the BattlEye client. A Patch has been released for the 0.62 stable and 0.63 experimental versions today to possibly resolve this issue. Please let us know in case the issue still occurs even upon these updates.
Regards,
Geez

hello e_xil and thank you for the report.
Has this occurred on the 0.62 or 0.63 version? And in case you experience such issue in the future, would it be possible for you to capture it on the video? Also, do you remember what was the server population at the time and if there was possibly some kind of desynchronisation occurring at the moment?
Regards,
Geez

Hello DerFallenBaker and thank you for the report.
As cloud37400 mentioned, the custom keybind menu is currently work in progress and does not work correctly.
Regards,
Geez

Hello AussieCleetus and thank you for the report.
We are aware of this issue and it is being worked on.
Regards,
Geez

Hello Vasamard.
It appears that the issue has been caused by the BattlEye client and a fix has been released for the 0.62 stable and 0.63 experimental versions just now. Please let us know in case you experience this issue even after these updates.
Regards,
Geez

Hello everyone.
BattlEye has confirmed that their client is source of the issue and a fix has been released for the 0.62 stable and 0.63 experimental versions just now. Please let us know in case you experience this issue still even after these updates.
Regards,
Geez

Hello buttons.
It appears that this issue has been caused by the BattlEye client. There has been an update for the 0.62 stable and 0.63 experimental released just now. Please let us know in case you still experience this issue even after these updates.
Regards,
Geez

Hello pe3pa.
The BattlEye has confirmed that this has indeed been issue on their side and a patch has been released for the 0.62 stable and 0.63 experimental versions just now. Please let us know in case you experience this issue even upon these updates.
Regards,
Geez

Hello pole_fan and thank you for the report.
Do you experience this issue only on the experimental version or does this issue occur on the stable / stress test versions as well? Have you always experienced this issue with the 0.63 version or has it started to occur from a specific date? Are there any .mdmp files being generated in your C:\Users\*username*\AppData\Local\DayZ folder when this issue occurs? If so, please upload them to this ticket. Also, have you tried to re-install your video drivers to see if it has any effect on the issue?
Regards,
Geez

Hello moeb1us.
Unfortunately, there are no updates on the issue so far. As I have mentioned in the previous post, TrackIR support is not a priority for the 0.63 version and it is going to be possibly addressed in the later stages of development.
Regards,
Geez

Hello cs_wolf.
The issue has been fixed in the 0.63 version.
Regards,
Geez

Hello ThePandaPuncher.
The issue has been fixed for the 0.63 version.
Regards,
Geez

Hello WeirdXone and thank you for the report.
We have confirmed the issue and it has been scheduled for afix.
Regards,
Geez

Hello -Anarchy- and thank you for the report.
This issue has been fixed internally and it is going to be fixed on Steam in the future.
Regards,
Geez

Hello thisusernameisnotallowed1337 and thank you for the report.
This issue has been fixed internally and it is going to be fixed on Steam in the future.
Regards,
Geez

Thank you.
We are also actively looking into the BSOD issues on our side and will let you know under this ticket in case there is any new information.
Regards,
Geez

Hello again and thank you for the updates.
Please contact BattlEye support at https://www.battleye.com/support/ and provide them with as much information as possible, as they would like to take a look at the issues you both are are experiencing.
Regards,
Geez

In T131040#1725045, @CallMeRive wrote:

OK, it's fixed the issue for me - but I've only tried 0.62 yet.

But before reinstalling I ran Uninstall_BattleEye.bat file from ../DayZ/BattleEye folder, then I unstalled DayZ via Steam, then I checked Documents and AppData for any DayZ files and folders, then I checked Common Files folder in Program Files (x86) for any remnants of BattleEye and only after that I rebooted the PC and installed DayZ via Steam.

It works now, but for some reason it runs 32 bit version by default (not a big problem).

In T131040#1724876, @theyowi wrote:

yes still experiencing this error patch didnt fix

Hello Solopopo and thank you for the report.
Is there some kind of error message when the blue screen appears (such as mentioned by hubba747: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED)? And if so, can you please write it down and post it in here?
Regards,
Geez

Hello pe3pa and thank you for the report.
Since this issue might be related to the BattlEye file you have mentioned, please contact BattlEye support directly at https://www.battleye.com/support/ and provide them with all the information you have provided us with.
In case the BattlEye team determines this issue is not on their side, please let us know under this ticket.
Regards,
Geez

Hello Vasamard and thank you for the report.
Were you able to take a note of the error message that appeared with the blue screen (if there was one)?
Regards,
Geez