{ "expand": "operations,versionedRepresentations,editmeta,changelog,renderedFields", "id": "554415", "self": "https://bugs.mojang.com/rest/api/2/issue/554415", "key": "BDS-19188", "fields": { "issuetype": "1", "project": "11700", "fixVersions": [], "resolution": "10001", "customfield_10500": { "self": "https://bugs.mojang.com/rest/api/2/customFieldOption/10300", "value": "Unconfirmed", "id": "10300", "disabled": false }, "customfield_12800": null, "customfield_12602": [], "customfield_12601": null, "customfield_12604": null, "customfield_12603": null, "customfield_12606": null, "customfield_12605": null, "customfield_12608": null, "resolutiondate": "2024-06-21T00:01:02.000+0300", "customfield_12607": null, "customfield_12609": null, "workratio": -1, "lastViewed": null, "watches": { "self": "https://bugs.mojang.com/rest/api/2/issue/BDS-19188/watchers", "watchCount": 3, "isWatching": false }, "created": "2024-04-02T10:20:50.000+0300", "customfield_12000": null, "customfield_12201": null, "customfield_12600": null, "labels": [], "customfield_11700": "{}", "versions": [ "22213" ], "issuelinks": [], "assignee": null, "updated": "2024-06-21T00:01:02.000+0300", "status": "5", "description": "Initially I created a bedrock server running 1.20.72 (Ubuntu Linux) and the world was working fine with 2x windows 11 clients, albeit there was the error reported on the server logs (MCPE-179139)\r\n\r\nAfter some time building, the two clients could not connect the next day. Tried the work around by importing the world into the one of the clients, toggling on 1.21 features, which allowed us to play (not using the dedicated server). However, bringing the world back into the server, the two clients would still crash when loading the world at connection time.\r\n\r\nWhat is interesting however, is another computer I have, also with 1.20.73 on Windows 11 is able to connect without issue. The two problematic computers have error events with \"invalid instruction\" in the entry \u2013 I did compare CPU-Z between the older computers and the newer one. The newer one is an Intel N100 which supports AVX2, AVX-VNNI, FMA3 and SHA instructions which the older machines (2nd Gen Intel i5s) do not support (they do support SSE2, 3, 4 and AVX1 however).\r\n\r\nThis issue occurs with 1.20.72 and 1.20.73 clients connecting to either a 1.20.72 or 1.20.73 bedrock dedicated server.\r\n\r\nThe windows version is 21H2 (22000.2538) and 23H2.\r\n\r\nI have attached error logs below.", "customfield_11100": 0.0, "customfield_11300": "Windows 11", "customfield_11500": null, "customfield_12503": null, "customfield_12700": "[Briefly describe the bug here]\r\n\r\n*Steps to Reproduce:*\r\n# [Step 1]\r\n# [Step 2]\r\n# [Step 3]\r\n\r\n*Observed Results:*\r\n[Describe what happens]\r\n\r\n*Expected Results:*\r\n[Describe what should happen]\r\n\r\n*Screenshots/Videos attached:* [please attach an image or short video]\r\n\r\n*Notes:*", "customfield_12502": null, "customfield_12504": null, "attachment": [ "566984", "566983" ], "summary": "Windows Client Crashes (1.20.72 and 1.20.73) when connecting to Bedrock Server", "creator": "JIRAUSER775597", "reporter": "JIRAUSER775597", "customfield_10002": null, "customfield_12501": null, "customfield_12500": null, "customfield_11601": null, "customfield_11600": "0|i2gwpb:", "environment": null, "customfield_11801": null, "customfield_11800": null, "customfield_11602": null, "customfield_11802": null, "comment": { "comments": [ { "self": "https://bugs.mojang.com/rest/api/2/issue/554415/comment/1313382", "id": "1313382", "author": "JIRAUSER775597", "body": "Server Log:\r\n{code:java}\r\n[2024-04-02 19:20:48:124 INFO] Starting Server\r\n[2024-04-02 19:20:48:124 INFO] Version: 1.20.73.01\r\n[2024-04-02 19:20:48:124 INFO] Session ID: 1d493a7d-ea08-4e31-9b47-c220f17001da\r\n[2024-04-02 19:20:48:124 INFO] Build ID: 23303367\r\n[2024-04-02 19:20:48:124 INFO] Branch: r/20_u7\r\n[2024-04-02 19:20:48:124 INFO] Commit ID: 53b6d61fe5d57f85d90c790592412160e3fa5cb0\r\n[2024-04-02 19:20:48:124 INFO] Configuration: Publish\r\n[2024-04-02 19:20:48:125 INFO] Level Name: Bedrock level\r\n[2024-04-02 19:20:48:126 INFO] No CDN config file found for dedicated server\r\n[2024-04-02 19:20:48:126 INFO] Game mode: 1 Creative\r\n[2024-04-02 19:20:48:126 INFO] Difficulty: 1 EASY\r\n[2024-04-02 19:20:48:127 INFO] Content logging to console is enabled.\r\n[2024-04-02 19:20:49:663 INFO] Experiment(s) active: biom, ul23\r\n[2024-04-02 19:20:49:663 INFO] Opening level 'worlds/Bedrock level/db'\r\n[2024-04-02 19:20:50:541 INFO] IPv4 supported, port: 19132: Used for gameplay and LAN discovery\r\n[2024-04-02 19:20:50:541 INFO] IPv6 supported, port: 19133: Used for gameplay\r\n[2024-04-02 19:20:50:552 INFO] Server started.\r\n[2024-04-02 19:20:50:552 INFO] ================ TELEMETRY MESSAGE ===================\r\n[2024-04-02 19:20:50:552 INFO] Server Telemetry is currently not enabled.\r\n[2024-04-02 19:20:50:552 INFO] Enabling this telemetry helps us improve the game.\r\n[2024-04-02 19:20:50:552 INFO]\r\n[2024-04-02 19:20:50:552 INFO] To enable this feature, add the line 'emit-server-telemetry=true'\r\n[2024-04-02 19:20:50:552 INFO] to the server.properties file in the handheld/src-server directory\r\n[2024-04-02 19:20:50:552 INFO] ======================================================\r\n[2024-04-02 19:20:56:050 INFO] Player connected: , xuid: \r\n[2024-04-02 19:21:00:100 INFO] Player Spawned: xuid: , pfid: \r\n[2024-04-02 19:21:09:365 INFO] Player disconnected: , xuid: , pfid: {code}\r\n\u00a0\r\n\r\n\u00a0", "updateAuthor": "JIRAUSER775597", "created": "2024-04-02T11:23:08.380+0300", "updated": "2024-04-02T11:23:08.380+0300" }, { "self": "https://bugs.mojang.com/rest/api/2/issue/554415/comment/1313383", "id": "1313383", "author": "JIRAUSER775597", "body": "Application Error:\r\n{code:java}\r\nFaulting application name: Minecraft.Windows.exe, version: 1.20.73.1, time stamp: 0x6605ffc3\r\nFaulting module name: Minecraft.Windows.exe, version: 1.20.73.1, time stamp: 0x6605ffc3\r\nException code: 0xc000001d\r\nFault offset: 0x0000000004612509\r\nFaulting process id: 0x148c\r\nFaulting application start time: 0x01da84d668c7bb89\r\nFaulting application path: C:\\Program Files\\WindowsApps\\Microsoft.MinecraftUWP_1.20.7301.0_x64__8wekyb3d8bbwe\\Minecraft.Windows.exe\r\nFaulting module path: C:\\Program Files\\WindowsApps\\Microsoft.MinecraftUWP_1.20.7301.0_x64__8wekyb3d8bbwe\\Minecraft.Windows.exe\r\nReport Id: 0275493c-78c2-491c-b7a3-6a0f4ac46178\r\nFaulting package full name: Microsoft.MinecraftUWP_1.20.7301.0_x64__8wekyb3d8bbwe\r\nFaulting package-relative application ID: App {code}\r\n[^Report.wer]", "updateAuthor": "JIRAUSER775597", "created": "2024-04-02T11:24:26.169+0300", "updated": "2024-04-02T11:24:26.169+0300" }, { "self": "https://bugs.mojang.com/rest/api/2/issue/554415/comment/1333040", "id": "1333040", "author": "jarl-penguin", "body": "Seeing as MCPE-179139 has been fixed with 1.21.0, is this still an issue?\r\n\r\n~This issue is being temporarily resolved as {color:#d04437}*Awaiting Response*{color}. Once the requested information has been delivered, the report will be reopened automatically.~\r\n\r\n*Quick Links*:\r\n\ud83d\udcd3 [Bug Tracker Guidelines|https://aka.ms/MCBugTrackerHelp] -- \ud83d\udcac [Community Support|https://discord.com/invite/58Sxm23] -- \ud83d\udce7 [Mojang Support (Technical Issues)|https://aka.ms/Minecraft-Support] -- \ud83d\udce7 [Microsoft Support (Account Issues)|https://support.xbox.com/contact-us/]\r\n\ud83d\udcd3 [Project Summary|https://bugs.mojang.com/projects/BDS/summary] -- \u270d\ufe0f [Feedback and Suggestions|https://aka.ms/MinecraftFeedbackDiscord] -- \ud83d\udcd6 [BDS Wiki|https://minecraft.wiki/w/Bedrock_Dedicated_Server] -- \ud83d\udcd6 [FAQs|https://help.minecraft.net/hc/en-us/articles/360035131651-Dedicated-Servers-for-Minecraft-on-Bedrock-]", "updateAuthor": "jarl-penguin", "created": "2024-06-21T00:01:02.639+0300", "updated": "2024-06-21T00:01:02.639+0300" } ], "maxResults": 3, "total": 3, "startAt": 0 }, "votes": { "self": "https://bugs.mojang.com/rest/api/2/issue/BDS-19188/votes", "votes": 1, "hasVoted": false } }, "changelog": { "startAt": 0, "maxResults": 12, "total": 12, "histories": [ { "id": "2964965", "author": "JIRAUSER775597", "created": "2024-04-02T10:22:35.288+0300", "items": [ { "field": "description", "fieldtype": "jira", "from": null, "fromString": "Initially I created a bedrock server running 1.20.72 (Ubuntu Linux) and the world was working fine with 2x windows 11 clients, albeit there was the error reported on the server logs.\r\n\r\nAfter some time building, the two clients could not connect the next day. Tried the work around by importing the world into the one of the clients, toggling on 1.21 features, which allowed us to play (not using the dedicated server). However, bringing the world back into the server, the two clients would still crash when loading the world at connection time.\r\n\r\nWhat is interesting however, is another computer I have, also with 1.20.73 on Windows 11 is able to connect without issue. The two problematic computers have error events with \"invalid instruction\" in the entry \u2013 I did compare CPU-Z between the older computers and the newer one. The newer one is an Intel N100 which supports AVX2, AVX-VNNI, FMA3 and SHA instructions which the older machines (2nd Gen Intel i5s) do not support (they do support SSE2, 3, 4 and AVX1 however).\r\n\r\nThis issue occurs with 1.20.72 and 1.20.73 clients connecting to either a 1.20.72 or 1.20.73 bedrock dedicated server.\r\n\r\nIf requested, I can attach the world as well as windows error logs.", "to": null, "toString": "Initially I created a bedrock server running 1.20.72 (Ubuntu Linux) and the world was working fine with 2x windows 11 clients, albeit there was the error reported on the server logs ([MCPE-180147] [Structure][error]-[[Jigsaw Structure]] couldn't be constructed, no pool named `minecraft:trial_chambers/chamber/end` - Jira (mojang.com)).\r\n\r\nAfter some time building, the two clients could not connect the next day. Tried the work around by importing the world into the one of the clients, toggling on 1.21 features, which allowed us to play (not using the dedicated server). However, bringing the world back into the server, the two clients would still crash when loading the world at connection time.\r\n\r\nWhat is interesting however, is another computer I have, also with 1.20.73 on Windows 11 is able to connect without issue. The two problematic computers have error events with \"invalid instruction\" in the entry \u2013 I did compare CPU-Z between the older computers and the newer one. The newer one is an Intel N100 which supports AVX2, AVX-VNNI, FMA3 and SHA instructions which the older machines (2nd Gen Intel i5s) do not support (they do support SSE2, 3, 4 and AVX1 however).\r\n\r\nThis issue occurs with 1.20.72 and 1.20.73 clients connecting to either a 1.20.72 or 1.20.73 bedrock dedicated server.\r\n\r\nIf requested, I can attach the world as well as windows error logs." } ] }, { "id": "2964967", "author": "JIRAUSER775597", "created": "2024-04-02T10:23:05.013+0300", "items": [ { "field": "description", "fieldtype": "jira", "from": null, "fromString": "Initially I created a bedrock server running 1.20.72 (Ubuntu Linux) and the world was working fine with 2x windows 11 clients, albeit there was the error reported on the server logs ([MCPE-180147] [Structure][error]-[[Jigsaw Structure]] couldn't be constructed, no pool named `minecraft:trial_chambers/chamber/end` - Jira (mojang.com)).\r\n\r\nAfter some time building, the two clients could not connect the next day. Tried the work around by importing the world into the one of the clients, toggling on 1.21 features, which allowed us to play (not using the dedicated server). However, bringing the world back into the server, the two clients would still crash when loading the world at connection time.\r\n\r\nWhat is interesting however, is another computer I have, also with 1.20.73 on Windows 11 is able to connect without issue. The two problematic computers have error events with \"invalid instruction\" in the entry \u2013 I did compare CPU-Z between the older computers and the newer one. The newer one is an Intel N100 which supports AVX2, AVX-VNNI, FMA3 and SHA instructions which the older machines (2nd Gen Intel i5s) do not support (they do support SSE2, 3, 4 and AVX1 however).\r\n\r\nThis issue occurs with 1.20.72 and 1.20.73 clients connecting to either a 1.20.72 or 1.20.73 bedrock dedicated server.\r\n\r\nIf requested, I can attach the world as well as windows error logs.", "to": null, "toString": "Initially I created a bedrock server running 1.20.72 (Ubuntu Linux) and the world was working fine with 2x windows 11 clients, albeit there was the error reported on the server logs ([MCPE-179139] Content Log error appears \"[Structure][error]-[[Jigsaw Structure]] couldn't be constructed, no pool named `minecraft:trial_chambers/chamber/end`\" when loading up a newly created world - Jira (mojang.com))\r\n\r\nAfter some time building, the two clients could not connect the next day. Tried the work around by importing the world into the one of the clients, toggling on 1.21 features, which allowed us to play (not using the dedicated server). However, bringing the world back into the server, the two clients would still crash when loading the world at connection time.\r\n\r\nWhat is interesting however, is another computer I have, also with 1.20.73 on Windows 11 is able to connect without issue. The two problematic computers have error events with \"invalid instruction\" in the entry \u2013 I did compare CPU-Z between the older computers and the newer one. The newer one is an Intel N100 which supports AVX2, AVX-VNNI, FMA3 and SHA instructions which the older machines (2nd Gen Intel i5s) do not support (they do support SSE2, 3, 4 and AVX1 however).\r\n\r\nThis issue occurs with 1.20.72 and 1.20.73 clients connecting to either a 1.20.72 or 1.20.73 bedrock dedicated server.\r\n\r\nIf requested, I can attach the world as well as windows error logs." } ] }, { "id": "2964968", "author": "JIRAUSER775597", "created": "2024-04-02T10:23:21.655+0300", "items": [ { "field": "description", "fieldtype": "jira", "from": null, "fromString": "Initially I created a bedrock server running 1.20.72 (Ubuntu Linux) and the world was working fine with 2x windows 11 clients, albeit there was the error reported on the server logs ([MCPE-179139] Content Log error appears \"[Structure][error]-[[Jigsaw Structure]] couldn't be constructed, no pool named `minecraft:trial_chambers/chamber/end`\" when loading up a newly created world - Jira (mojang.com))\r\n\r\nAfter some time building, the two clients could not connect the next day. Tried the work around by importing the world into the one of the clients, toggling on 1.21 features, which allowed us to play (not using the dedicated server). However, bringing the world back into the server, the two clients would still crash when loading the world at connection time.\r\n\r\nWhat is interesting however, is another computer I have, also with 1.20.73 on Windows 11 is able to connect without issue. The two problematic computers have error events with \"invalid instruction\" in the entry \u2013 I did compare CPU-Z between the older computers and the newer one. The newer one is an Intel N100 which supports AVX2, AVX-VNNI, FMA3 and SHA instructions which the older machines (2nd Gen Intel i5s) do not support (they do support SSE2, 3, 4 and AVX1 however).\r\n\r\nThis issue occurs with 1.20.72 and 1.20.73 clients connecting to either a 1.20.72 or 1.20.73 bedrock dedicated server.\r\n\r\nIf requested, I can attach the world as well as windows error logs.", "to": null, "toString": "Initially I created a bedrock server running 1.20.72 (Ubuntu Linux) and the world was working fine with 2x windows 11 clients, albeit there was the error reported on the server logs (MCPE-179139)\r\n\r\nAfter some time building, the two clients could not connect the next day. Tried the work around by importing the world into the one of the clients, toggling on 1.21 features, which allowed us to play (not using the dedicated server). However, bringing the world back into the server, the two clients would still crash when loading the world at connection time.\r\n\r\nWhat is interesting however, is another computer I have, also with 1.20.73 on Windows 11 is able to connect without issue. The two problematic computers have error events with \"invalid instruction\" in the entry \u2013 I did compare CPU-Z between the older computers and the newer one. The newer one is an Intel N100 which supports AVX2, AVX-VNNI, FMA3 and SHA instructions which the older machines (2nd Gen Intel i5s) do not support (they do support SSE2, 3, 4 and AVX1 however).\r\n\r\nThis issue occurs with 1.20.72 and 1.20.73 clients connecting to either a 1.20.72 or 1.20.73 bedrock dedicated server.\r\n\r\nIf requested, I can attach the world as well as windows error logs." } ] }, { "id": "2964988", "author": "JIRAUSER775597", "created": "2024-04-02T11:24:22.241+0300", "items": [ { "field": "Attachment", "fieldtype": "jira", "from": null, "fromString": null, "to": "566983", "toString": "Report.wer" } ] }, { "id": "2964989", "author": "JIRAUSER775597", "created": "2024-04-02T11:26:13.486+0300", "items": [ { "field": "description", "fieldtype": "jira", "from": null, "fromString": "Initially I created a bedrock server running 1.20.72 (Ubuntu Linux) and the world was working fine with 2x windows 11 clients, albeit there was the error reported on the server logs (MCPE-179139)\r\n\r\nAfter some time building, the two clients could not connect the next day. Tried the work around by importing the world into the one of the clients, toggling on 1.21 features, which allowed us to play (not using the dedicated server). However, bringing the world back into the server, the two clients would still crash when loading the world at connection time.\r\n\r\nWhat is interesting however, is another computer I have, also with 1.20.73 on Windows 11 is able to connect without issue. The two problematic computers have error events with \"invalid instruction\" in the entry \u2013 I did compare CPU-Z between the older computers and the newer one. The newer one is an Intel N100 which supports AVX2, AVX-VNNI, FMA3 and SHA instructions which the older machines (2nd Gen Intel i5s) do not support (they do support SSE2, 3, 4 and AVX1 however).\r\n\r\nThis issue occurs with 1.20.72 and 1.20.73 clients connecting to either a 1.20.72 or 1.20.73 bedrock dedicated server.\r\n\r\nIf requested, I can attach the world as well as windows error logs.", "to": null, "toString": "Initially I created a bedrock server running 1.20.72 (Ubuntu Linux) and the world was working fine with 2x windows 11 clients, albeit there was the error reported on the server logs (MCPE-179139)\r\n\r\nAfter some time building, the two clients could not connect the next day. Tried the work around by importing the world into the one of the clients, toggling on 1.21 features, which allowed us to play (not using the dedicated server). However, bringing the world back into the server, the two clients would still crash when loading the world at connection time.\r\n\r\nWhat is interesting however, is another computer I have, also with 1.20.73 on Windows 11 is able to connect without issue. The two problematic computers have error events with \"invalid instruction\" in the entry \u2013 I did compare CPU-Z between the older computers and the newer one. The newer one is an Intel N100 which supports AVX2, AVX-VNNI, FMA3 and SHA instructions which the older machines (2nd Gen Intel i5s) do not support (they do support SSE2, 3, 4 and AVX1 however).\r\n\r\nThis issue occurs with 1.20.72 and 1.20.73 clients connecting to either a 1.20.72 or 1.20.73 bedrock dedicated server.\r\n\r\nThe windows version is 21H2.\r\n\r\nIf requested, I can attach the world as well as windows error logs." } ] }, { "id": "2964990", "author": "JIRAUSER775597", "created": "2024-04-02T11:26:25.881+0300", "items": [ { "field": "description", "fieldtype": "jira", "from": null, "fromString": "Initially I created a bedrock server running 1.20.72 (Ubuntu Linux) and the world was working fine with 2x windows 11 clients, albeit there was the error reported on the server logs (MCPE-179139)\r\n\r\nAfter some time building, the two clients could not connect the next day. Tried the work around by importing the world into the one of the clients, toggling on 1.21 features, which allowed us to play (not using the dedicated server). However, bringing the world back into the server, the two clients would still crash when loading the world at connection time.\r\n\r\nWhat is interesting however, is another computer I have, also with 1.20.73 on Windows 11 is able to connect without issue. The two problematic computers have error events with \"invalid instruction\" in the entry \u2013 I did compare CPU-Z between the older computers and the newer one. The newer one is an Intel N100 which supports AVX2, AVX-VNNI, FMA3 and SHA instructions which the older machines (2nd Gen Intel i5s) do not support (they do support SSE2, 3, 4 and AVX1 however).\r\n\r\nThis issue occurs with 1.20.72 and 1.20.73 clients connecting to either a 1.20.72 or 1.20.73 bedrock dedicated server.\r\n\r\nThe windows version is 21H2.\r\n\r\nIf requested, I can attach the world as well as windows error logs.", "to": null, "toString": "Initially I created a bedrock server running 1.20.72 (Ubuntu Linux) and the world was working fine with 2x windows 11 clients, albeit there was the error reported on the server logs (MCPE-179139)\r\n\r\nAfter some time building, the two clients could not connect the next day. Tried the work around by importing the world into the one of the clients, toggling on 1.21 features, which allowed us to play (not using the dedicated server). However, bringing the world back into the server, the two clients would still crash when loading the world at connection time.\r\n\r\nWhat is interesting however, is another computer I have, also with 1.20.73 on Windows 11 is able to connect without issue. The two problematic computers have error events with \"invalid instruction\" in the entry \u2013 I did compare CPU-Z between the older computers and the newer one. The newer one is an Intel N100 which supports AVX2, AVX-VNNI, FMA3 and SHA instructions which the older machines (2nd Gen Intel i5s) do not support (they do support SSE2, 3, 4 and AVX1 however).\r\n\r\nThis issue occurs with 1.20.72 and 1.20.73 clients connecting to either a 1.20.72 or 1.20.73 bedrock dedicated server.\r\n\r\nThe windows version is 21H2 (22000.).\r\n\r\nIf requested, I can attach the world as well as windows error logs." } ] }, { "id": "2964991", "author": "JIRAUSER775597", "created": "2024-04-02T11:26:38.596+0300", "items": [ { "field": "description", "fieldtype": "jira", "from": null, "fromString": "Initially I created a bedrock server running 1.20.72 (Ubuntu Linux) and the world was working fine with 2x windows 11 clients, albeit there was the error reported on the server logs (MCPE-179139)\r\n\r\nAfter some time building, the two clients could not connect the next day. Tried the work around by importing the world into the one of the clients, toggling on 1.21 features, which allowed us to play (not using the dedicated server). However, bringing the world back into the server, the two clients would still crash when loading the world at connection time.\r\n\r\nWhat is interesting however, is another computer I have, also with 1.20.73 on Windows 11 is able to connect without issue. The two problematic computers have error events with \"invalid instruction\" in the entry \u2013 I did compare CPU-Z between the older computers and the newer one. The newer one is an Intel N100 which supports AVX2, AVX-VNNI, FMA3 and SHA instructions which the older machines (2nd Gen Intel i5s) do not support (they do support SSE2, 3, 4 and AVX1 however).\r\n\r\nThis issue occurs with 1.20.72 and 1.20.73 clients connecting to either a 1.20.72 or 1.20.73 bedrock dedicated server.\r\n\r\nThe windows version is 21H2 (22000.).\r\n\r\nIf requested, I can attach the world as well as windows error logs.", "to": null, "toString": "Initially I created a bedrock server running 1.20.72 (Ubuntu Linux) and the world was working fine with 2x windows 11 clients, albeit there was the error reported on the server logs (MCPE-179139)\r\n\r\nAfter some time building, the two clients could not connect the next day. Tried the work around by importing the world into the one of the clients, toggling on 1.21 features, which allowed us to play (not using the dedicated server). However, bringing the world back into the server, the two clients would still crash when loading the world at connection time.\r\n\r\nWhat is interesting however, is another computer I have, also with 1.20.73 on Windows 11 is able to connect without issue. The two problematic computers have error events with \"invalid instruction\" in the entry \u2013 I did compare CPU-Z between the older computers and the newer one. The newer one is an Intel N100 which supports AVX2, AVX-VNNI, FMA3 and SHA instructions which the older machines (2nd Gen Intel i5s) do not support (they do support SSE2, 3, 4 and AVX1 however).\r\n\r\nThis issue occurs with 1.20.72 and 1.20.73 clients connecting to either a 1.20.72 or 1.20.73 bedrock dedicated server.\r\n\r\nThe windows version is 21H2 (22000.2538).\r\n\r\nIf requested, I can attach the world as well as windows error logs." } ] }, { "id": "2964992", "author": "JIRAUSER775597", "created": "2024-04-02T11:26:51.770+0300", "items": [ { "field": "description", "fieldtype": "jira", "from": null, "fromString": "Initially I created a bedrock server running 1.20.72 (Ubuntu Linux) and the world was working fine with 2x windows 11 clients, albeit there was the error reported on the server logs (MCPE-179139)\r\n\r\nAfter some time building, the two clients could not connect the next day. Tried the work around by importing the world into the one of the clients, toggling on 1.21 features, which allowed us to play (not using the dedicated server). However, bringing the world back into the server, the two clients would still crash when loading the world at connection time.\r\n\r\nWhat is interesting however, is another computer I have, also with 1.20.73 on Windows 11 is able to connect without issue. The two problematic computers have error events with \"invalid instruction\" in the entry \u2013 I did compare CPU-Z between the older computers and the newer one. The newer one is an Intel N100 which supports AVX2, AVX-VNNI, FMA3 and SHA instructions which the older machines (2nd Gen Intel i5s) do not support (they do support SSE2, 3, 4 and AVX1 however).\r\n\r\nThis issue occurs with 1.20.72 and 1.20.73 clients connecting to either a 1.20.72 or 1.20.73 bedrock dedicated server.\r\n\r\nThe windows version is 21H2 (22000.2538).\r\n\r\nIf requested, I can attach the world as well as windows error logs.", "to": null, "toString": "Initially I created a bedrock server running 1.20.72 (Ubuntu Linux) and the world was working fine with 2x windows 11 clients, albeit there was the error reported on the server logs (MCPE-179139)\r\n\r\nAfter some time building, the two clients could not connect the next day. Tried the work around by importing the world into the one of the clients, toggling on 1.21 features, which allowed us to play (not using the dedicated server). However, bringing the world back into the server, the two clients would still crash when loading the world at connection time.\r\n\r\nWhat is interesting however, is another computer I have, also with 1.20.73 on Windows 11 is able to connect without issue. The two problematic computers have error events with \"invalid instruction\" in the entry \u2013 I did compare CPU-Z between the older computers and the newer one. The newer one is an Intel N100 which supports AVX2, AVX-VNNI, FMA3 and SHA instructions which the older machines (2nd Gen Intel i5s) do not support (they do support SSE2, 3, 4 and AVX1 however).\r\n\r\nThis issue occurs with 1.20.72 and 1.20.73 clients connecting to either a 1.20.72 or 1.20.73 bedrock dedicated server.\r\n\r\nThe windows version is 21H2 (22000.2538).\r\n\r\nI have attached error logs below." } ] }, { "id": "2964993", "author": "JIRAUSER775597", "created": "2024-04-02T11:28:41.008+0300", "items": [ { "field": "Attachment", "fieldtype": "jira", "from": null, "fromString": null, "to": "566984", "toString": "CPU-Z Report.txt" } ] }, { "id": "2966044", "author": "JIRAUSER775597", "created": "2024-04-03T14:41:03.530+0300", "items": [ { "field": "description", "fieldtype": "jira", "from": null, "fromString": "Initially I created a bedrock server running 1.20.72 (Ubuntu Linux) and the world was working fine with 2x windows 11 clients, albeit there was the error reported on the server logs (MCPE-179139)\r\n\r\nAfter some time building, the two clients could not connect the next day. Tried the work around by importing the world into the one of the clients, toggling on 1.21 features, which allowed us to play (not using the dedicated server). However, bringing the world back into the server, the two clients would still crash when loading the world at connection time.\r\n\r\nWhat is interesting however, is another computer I have, also with 1.20.73 on Windows 11 is able to connect without issue. The two problematic computers have error events with \"invalid instruction\" in the entry \u2013 I did compare CPU-Z between the older computers and the newer one. The newer one is an Intel N100 which supports AVX2, AVX-VNNI, FMA3 and SHA instructions which the older machines (2nd Gen Intel i5s) do not support (they do support SSE2, 3, 4 and AVX1 however).\r\n\r\nThis issue occurs with 1.20.72 and 1.20.73 clients connecting to either a 1.20.72 or 1.20.73 bedrock dedicated server.\r\n\r\nThe windows version is 21H2 (22000.2538).\r\n\r\nI have attached error logs below.", "to": null, "toString": "Initially I created a bedrock server running 1.20.72 (Ubuntu Linux) and the world was working fine with 2x windows 11 clients, albeit there was the error reported on the server logs (MCPE-179139)\r\n\r\nAfter some time building, the two clients could not connect the next day. Tried the work around by importing the world into the one of the clients, toggling on 1.21 features, which allowed us to play (not using the dedicated server). However, bringing the world back into the server, the two clients would still crash when loading the world at connection time.\r\n\r\nWhat is interesting however, is another computer I have, also with 1.20.73 on Windows 11 is able to connect without issue. The two problematic computers have error events with \"invalid instruction\" in the entry \u2013 I did compare CPU-Z between the older computers and the newer one. The newer one is an Intel N100 which supports AVX2, AVX-VNNI, FMA3 and SHA instructions which the older machines (2nd Gen Intel i5s) do not support (they do support SSE2, 3, 4 and AVX1 however).\r\n\r\nThis issue occurs with 1.20.72 and 1.20.73 clients connecting to either a 1.20.72 or 1.20.73 bedrock dedicated server.\r\n\r\nThe windows version is 21H2 (22000.2538) and 23H2.\r\n\r\nI have attached error logs below." } ] }, { "id": "2968393", "author": "umija5895", "created": "2024-04-06T16:21:24.800+0300", "items": [ { "field": "Key", "fieldtype": "jira", "from": null, "fromString": "MCPE-180236", "to": null, "toString": "BDS-19188" }, { "field": "Platform", "fieldtype": "custom", "from": "10901", "fromString": "Windows", "to": null, "toString": "" }, { "field": "Version", "fieldtype": "jira", "from": null, "fromString": null, "to": "22213", "toString": "1.20.73" }, { "field": "Version", "fieldtype": "jira", "from": "22211", "fromString": "1.20.73 Hotfix", "to": null, "toString": null }, { "field": "Version", "fieldtype": "jira", "from": "22202", "fromString": "1.20.72 Hotfix", "to": null, "toString": null }, { "field": "Workflow", "fieldtype": "jira", "from": "727342", "fromString": "MCPE Workflow", "to": "727718", "toString": "Global Mojang Workflow" }, { "field": "project", "fieldtype": "jira", "from": "10200", "fromString": "Minecraft (Bedrock codebase)", "to": "11700", "toString": "Bedrock Dedicated Server" } ] }, { "id": "3021851", "author": "jarl-penguin", "created": "2024-06-21T00:01:02.647+0300", "items": [ { "field": "resolution", "fieldtype": "jira", "from": null, "fromString": null, "to": "10001", "toString": "Awaiting Response" }, { "field": "status", "fieldtype": "jira", "from": "1", "fromString": "Open", "to": "5", "toString": "Resolved" } ] } ] } }