could someone give me a hand my hashcat is acting funny

[mptito]

hi, im not new to hashcat but i do have a brand new laptop and when i try to to run hashcat -I or hashcat -b i just get that yelllow text(on windows)
Benchmarking uses hand-optimized kernel code by default.
You can use it in your cracking session by setting the -O option.
Note: Using optimized kernel code limits the maximum supported password length.
To disable the optimized kernel code in benchmark mode, use the -w option.

and then it stops. 

if i run it with -D1 i get this 
CUDA API (CUDA 12.6)
====================
* Device #1: NVIDIA GeForce RTX 4070 Laptop GPU, skipped

OpenCL API (OpenCL 3.0 CUDA 12.6.65) - Platform #1 [NVIDIA Corporation]
=======================================================================
* Device #2: NVIDIA GeForce RTX 4070 Laptop GPU, skipped

OpenCL API (OpenCL 3.0 ) - Platform #2 [Intel(R) Corporation]
=============================================================
* Device #3: Intel(R) Iris(R) Xe Graphics, skipped

OpenCL API (OpenCL 3.0 D3D12 Implementation) - Platform #3 [Microsoft]
======================================================================
* Device #4: NVIDIA GeForce RTX 4070 Laptop GPU, skipped
* Device #5: Intel(R) Iris(R) Xe Graphics, skipped
* Device #6: Microsoft Basic Render Driver, 16271/32607 MB (512 MB allocatable), 1MCU

OpenCL API (OpenCL 3.0 WINDOWS) - Platform #4 [Intel(R) Corporation]
====================================================================
* Device #7: 13th Gen Intel(R) Core(TM) i7-13700H, 32575/65215 MB (16303 MB allocatable), 20MCU

Benchmark relevant options:
===========================
* --opencl-device-types=1
* --optimized-kernel-enable

-------------------
* Hash-Mode 0 (MD5)

then it stops again. what seems to be the issue?

[Snoopy]

hi, im not new to hashcat but i do have a brand new laptop and when i try to to run hashcat -I or hashcat -b i just get that yelllow text(on windows)
Benchmarking uses hand-optimized kernel code by default.
You can use it in your cracking session by setting the -O option.
Note: Using optimized kernel code limits the maximum supported password length.
To disable the optimized kernel code in benchmark mode, use the -w option.

and then it stops. 

if i run it with -D1 i get this 
CUDA API (CUDA 12.6)
====================
* Device #1: NVIDIA GeForce RTX 4070 Laptop GPU, skipped

OpenCL API (OpenCL 3.0 CUDA 12.6.65) - Platform #1 [NVIDIA Corporation]
=======================================================================
* Device #2: NVIDIA GeForce RTX 4070 Laptop GPU, skipped

OpenCL API (OpenCL 3.0 ) - Platform #2 [Intel(R) Corporation]
=============================================================
* Device #3: Intel(R) Iris(R) Xe Graphics, skipped

OpenCL API (OpenCL 3.0 D3D12 Implementation) - Platform #3 [Microsoft]
======================================================================
* Device #4: NVIDIA GeForce RTX 4070 Laptop GPU, skipped
* Device #5: Intel(R) Iris(R) Xe Graphics, skipped
* Device #6: Microsoft Basic Render Driver, 16271/32607 MB (512 MB allocatable), 1MCU

OpenCL API (OpenCL 3.0 WINDOWS) - Platform #4 [Intel(R) Corporation]
====================================================================
* Device #7: 13th Gen Intel(R) Core(TM) i7-13700H, 32575/65215 MB (16303 MB allocatable), 20MCU

Benchmark relevant options:
===========================
* --opencl-device-types=1
* --optimized-kernel-enable

-------------------
* Hash-Mode 0 (MD5)

then it stops again. what seems to be the issue?

combined Intel CPU/GPU tend to produce errors (opencl is broken), for your GTX, seems a driver problem, you need the CUDA SDK and corresponding driverversions.