Host freeze using virtual box

Hi, there I have windows 7 installed on VirtualBox version 6.1
it was working perfectly for a few days but suddenly it start crashing(don’t remember if updated anything) it is like after running my windows virtual machine ( not VB itself) my host machine froze and the mouse or keyboard doesn’t work, I can’t even enter TTY.
the point is it just happens sometimes and not always, like once it’s good and working nice, next time it doesn’t, I tried both Wayland, X11, Nvidia, and AMD GPU but have no effect.

inxi -Fzx     
  Kernel: 5.17.12-300.fc36.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.37-27.fc36 Desktop: GNOME v: 42.2
    Distro: Fedora release 36 (Thirty Six)
  Type: Laptop System: ASUSTeK product: ZenBook UX434IQ_UM433IQ v: 1.0
    serial: <superuser required>
  Mobo: ASUSTeK model: UX434IQ v: 1.0 serial: <superuser required>
    UEFI: American Megatrends v: UX434IQ_UM433IQ.302 date: 07/10/2020
  ID-1: BAT0 charge: 32.1 Wh (70.9%) condition: 45.3/50.0 Wh (90.7%)
    volts: 11.9 min: 11.9 model: ASUSTeK ASUS Battery status: discharging
  Info: 8-core model: AMD Ryzen 7 4700U with Radeon Graphics bits: 64
    type: MCP arch: Zen 2 rev: 1 cache: L1: 512 KiB L2: 4 MiB L3: 8 MiB
  Speed (MHz): avg: 1395 high: 1398 min/max: 1400/2000 boost: enabled
    cores: 1: 1396 2: 1396 3: 1388 4: 1397 5: 1398 6: 1396 7: 1396 8: 1396
    bogomips: 31939
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Device-1: NVIDIA GP107M [GeForce MX350] vendor: ASUSTeK driver: nvidia
    v: 510.68.02 arch: Pascal bus-ID: 01:00.0
  Device-2: AMD Renoir vendor: ASUSTeK driver: amdgpu v: kernel
    bus-ID: 04:00.0
  Device-3: IMC Networks USB2.0 HD IR UVC WebCam type: USB driver: uvcvideo
    bus-ID: 3-2:2
  Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 22.1.2 driver: X:
    loaded: amdgpu,nvidia unloaded: fbdev,modesetting,nouveau,vesa gpu: amdgpu
    resolution: 1: 1920x1080~60Hz 2: N/A
  OpenGL: renderer: NVIDIA GeForce MX350/PCIe/SSE2
    v: 4.6.0 NVIDIA 510.68.02 direct render: Yes
  Device-1: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel
    v: kernel bus-ID: 04:00.1
  Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: ASUSTeK
    driver: N/A bus-ID: 04:00.5
  Device-3: AMD Family 17h/19h HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel bus-ID: 04:00.6
  Sound Server-1: ALSA v: k5.17.12-300.fc36.x86_64 running: yes
  Sound Server-2: PulseAudio v: 15.0 running: no
  Sound Server-3: PipeWire v: 0.3.51 running: yes
  Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus-ID: 02:00.0
  IF: wlp2s0 state: up mac: <filter>
  IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
  Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8
    bus-ID: 1-4:4
  Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: see --recommends
  Local Storage: total: 953.87 GiB used: 39.49 GiB (4.1%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLB1T0HALR-00000
    size: 953.87 GiB temp: 46.9 C
  ID-1: / size: 952.37 GiB used: 39.21 GiB (4.1%) fs: btrfs
    dev: /dev/nvme0n1p3
  ID-2: /boot size: 973.4 MiB used: 268.9 MiB (27.6%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 511 MiB used: 13.9 MiB (2.7%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 952.37 GiB used: 39.21 GiB (4.1%) fs: btrfs
    dev: /dev/nvme0n1p3
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) dev: /dev/zram0
  System Temperatures: cpu: 50.0 C mobo: N/A
  Fan Speeds (RPM): cpu: 3100
  GPU: device: nvidia screen: :0.0 temp: 56 C device: amdgpu temp: 56.0 C
  Processes: 352 Uptime: 7m Memory: 15.11 GiB used: 1.89 GiB (12.5%)
  Init: systemd runlevel: 5 Compilers: gcc: 12.1.1 clang: 14.0.0 Packages: 6
  note: see --pkg Shell: Zsh v: 5.8.1 inxi: 3.3.16

Is there any relevant info with journalctl -b -1 ? The most obvious thing I can think of is if it’s getting killed by an OOM (Out of Memory) situation.

I don’t think that’s the case cuz there’s 16 GB ram on this laptop and I think that should be enough to prevent OOM kill.
don’t know if there is any information here:

journalctl --since "2022-6-8 10:13:00" | grep -i virtualbox
Jun 08 10:13:33 zen systemd[1957]: Started app-glib-virtualbox-6507.scope - Application launched by gnome-shell.
Jun 08 10:13:33 zen systemd[1957]: Started app-gnome-virtualbox-6507.scope - Application launched by gnome-shell.
Jun 08 10:15:08 zen systemd[1]: Starting vboxdrv.service - VirtualBox Linux kernel module...
Jun 08 10:15:08 zen systemd[1]: vboxservice.service - VirtualBox guest services was skipped because all trigger condition checks failed.
Jun 08 10:15:08 zen[923]: Starting VirtualBox services.
Jun 08 10:15:08 zen[1083]: Starting VirtualBox services.
Jun 08 10:15:08 zen[1204]: VirtualBox services started.
Jun 08 10:15:08 zen systemd[1]: Started vboxdrv.service - VirtualBox Linux kernel module.
Jun 08 10:16:26 zen systemd[1961]: Started app-glib-virtualbox-4297.scope - Application launched by gnome-shell.
Jun 08 10:16:26 zen systemd[1961]: Started app-gnome-virtualbox-4297.scope - Application launched by gnome-shell.
Jun 08 10:16:58 zen systemd[1961]: app-gnome-virtualbox-4297.scope: Consumed 3.874s CPU time.