Error: Invalid read from address 0x6a2f000

Forums / NoMachine for Windows / Error: Invalid read from address 0x6a2f000

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #38728
    chrys
    Participant

    Dear Support,

    very recently, after some Windows 11 updates, NoMachine clashes when try to connect to the remote Ubuntu PC.

    I attached the nxtrace.log file here.

    Hope can hear your possible suggestion soon.

    Regards,

    Chrys

    Edited and added on by admin:

    Can you describe the steps to reproduce the crash so I can add them to the topic?
    – I click one of the remote PCs, key in Username and Password, and click “Login”, then the nomachine window is closed immediately.

    What updates (version) have you applied to the Windows 11 client?
    – The update applied on the day when crash happened is “Security Intelligence Update for Microsoft Defender Antivirus – KB2267602 (Version 1.367.491.0) ” and “Security Intelligence Update for Microsoft Defender Antivirus – KB2267602 (Version 1.367.600.0)”

    What Ubuntu version are you connecting to?
    – Both Ubuntu 18.04 and Ubuntu 20.04

    Are you able to connect from another client?
    – Yes, I have another laptop running Windows 10. From that laptop, I have no issue connecting to remote PCs.

    Also, the logs did not attach so please send them in reply to this email.
    – please see the attachment including .NX folder and nxtrace.log file.

    #38768
    Britgirl
    Keymaster

    Please try disabling hardware decoding on the Windows client.
    You can disable it completely in the player.cfg. Please edit the file $HOME/.nx/config/player.cfgand set the configuration key “Enable hardware accelerated decoding” to “disabled”.

    #38771
    Britgirl
    Keymaster

    We took a second look at the stack dump.
    Confirmed it fails exactly in the video decoder device initialization and this initialization doesn’t require any special parameter. At a glance this seems to be a device bug and, indeed, we found this same problem reported for Outlook:

    https://answers.microsoft.com/en-us/outlook_com/forum/all/outlook-2016-appcrash-outlookexe-igd10iumd32dll/13e118ae-64e8-4cb5-9d59-038d6052285c?auth=1

    You didn’t say what exact driver version you are using. The first step, we’d say, is to update your video drivers.

    #38781
    chrys
    Participant

    Thanks Britgirl,

    Here is the update about my issue:

    1, after I disable hardware decoding on windows client, the problem is still persisted.

    2, in my laptop, I’ve two graphics cards, both of them are with up-to-date driver version. after I read the outlook post (which you refer me to), I decided to do the down grade of graphics card driver version. Then the problem is solved.

    Thanks again Britgirl.

    #38787
    Britgirl
    Keymaster

    I decided to do the down grade of graphics card driver version. Then the problem is solved.

    Ok Chrys, thanks for letting us know. We suspected as much that the drivers were causing the problem.

     

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.