Memory increses over time, Leak? New Game 6.0

Ask here if you experience technical problems with X4: Foundations.

Moderator: Moderators for English X Forum

Captain-Spaulding
Posts: 1
Joined: Wed, 21. Jun 23, 13:13
x4

Re: Memory increses over time, Leak? New Game 6.0

Post by Captain-Spaulding »

I hope this (shortened) DxDiag is helpful.
At least it mentions a potential memory leak, if I interpret that correct.
Spoiler
Show
------------------
System Information
------------------
Time of this report: 6/28/2023, 14:54:33
Machine name: RALLE-PC
Machine Id: {74E86EAC-01B7-4FF4-9CE0-7905A878FF98}
Operating System: Windows 11 Home 64-bit (10.0, Build 22621) (22621.ni_release.220506-1250)
Language: German (Regional Setting: German)
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: Z690 UD DDR4
BIOS: F7a (type: UEFI)
Processor: 12th Gen Intel(R) Core(TM) i7-12700K (20 CPUs), ~3.6GHz
Memory: 32768MB RAM
Available OS Memory: 32610MB RAM
Page File: 7671MB used, 29801MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 12
DX Setup Parameters: Not found
User DPI Setting: 96 DPI (100 percent)
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
Miracast: Available, no HDCP
Microsoft Graphics Hybrid: Not Supported
DirectX Database Version: 1.4.6
DxDiag Version: 10.00.22621.0001 64bit Unicode

------------
DxDiag Notes
------------
Display Tab 1: No problems found.
Sound Tab 1: No problems found.
Sound Tab 2: No problems found.
Sound Tab 3: No problems found.
Input Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D: 0/4 (retail)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)

---------------
Display Devices
---------------
Card name: NVIDIA GeForce RTX 3070
Manufacturer: NVIDIA
Chip type: NVIDIA GeForce RTX 3070
DAC type: Integrated RAMDAC
Device Type: Full Device (POST)
Device Key: Enum\PCI\VEN_10DE&DEV_2488&SUBSYS_F2801569&REV_A1
Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]
Device Problem Code: No Problem
Driver Problem Code: Unknown
Display Memory: 24336 MB
Dedicated Memory: 8032 MB
Shared Memory: 16304 MB
Current Mode: 2560 x 1440 (32 bit) (59Hz)
HDR Support: Supported
Display Topology: Internal
Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709
Color Primaries: Red(0.669922,0.311523), Green(0.278320,0.660156), Blue(0.155273,0.064453), White Point(0.313477,0.329102)
Display Luminance: Min Luminance = 0.123900, Max Luminance = 436.208008, MaxFullFrameLuminance = 436.208008
Monitor Name: Generic PnP Monitor
Monitor Model: G32QC A
Monitor Id: GBT3206
Native Mode: 2560 x 1440(p) (59.940Hz)
Output Type: Displayport External
Monitor Capabilities: HDR Supported (BT2020RGB BT2020YCC Eotf2084Supported )
Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP
Advanced Color: AdvancedColorSupported
Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvldumdx.dll
Driver File Version: 31.00.0015.3179 (English)
Driver Version: 31.0.15.3179
DDI Version: 12
Feature Levels: 12_2,12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1
Driver Model: WDDM 3.1
Hardware Scheduling: DriverSupportState:Stable Enabled:True
Displayable: Not Supported
Graphics Preemption: Pixel
Compute Preemption: Dispatch
Miracast: Not Supported
Detachable GPU: No
Hybrid Graphics GPU: Discrete
Power P-states: Not Supported
Virtualization: Paravirtualization
Block List: No Blocks
Catalog Attributes: Universal:False Declarative:True
Driver Attributes: Final Retail
Driver Date/Size: 25.04.2023 02:00:00, 770664 bytes
WHQL Logo'd: Yes
WHQL Date Stamp: Unknown
Device Identifier: {D7B71E3E-67C8-11CF-B27A-8FD20EC2D235}
Vendor ID: 0x10DE
Device ID: 0x2488
SubSys ID: 0xF2801569
Revision ID: 0x00A1
Driver Strong Name: oem90.inf:0f066de31a1a610b:Section072:31.0.15.3179:pci\ven_10de&dev_2488
Rank Of Driver: 00CF2001
Video Accel:
DXVA2 Modes: {86695F12-340E-4F04-9FD3-9253DD327460} DXVA2_ModeMPEG2_VLD {6F3EC719-3735-42CC-8063-65CC3CB36616} DXVA2_ModeVC1_D2010 DXVA2_ModeVC1_VLD {32FCFE3F-DE46-4A49-861B-AC71110649D5} DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT DXVA2_ModeH264_VLD_Stereo_NoFGT DXVA2_ModeH264_VLD_NoFGT DXVA2_ModeHEVC_VLD_Main DXVA2_ModeHEVC_VLD_Main10 {20BB8B0A-97AA-4571-8E99-64E60606C1A6} {15DF9B21-06C4-47F1-841E-A67C97D7F312} DXVA2_ModeMPEG4pt2_VLD_Simple DXVA2_ModeMPEG4pt2_VLD_AdvSimple_NoGMC {9947EC6F-689B-11DC-A320-0019DBBC4184} {33FCFE41-DE46-4A49-861B-AC71110649D5} DXVA2_ModeVP9_VLD_Profile0 DXVA2_ModeVP9_VLD_10bit_Profile2 {DDA19DC7-93B5-49F5-A9B3-2BDA28A2CE6E} {B8BE4CCB-CF53-46BA-8D59-D6B8A6DA5D2A} {6AFFD11E-1D96-42B1-A215-93A31F09A53D} {914C84A3-4078-4FA9-984C-E2F262CB5C9C} {8A1A1031-29BC-46D0-A007-E9B092CA6767}
Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
D3D9 Overlay: Not Supported
DXVA-HD: Supported
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
MPO MaxPlanes: 4
MPO Caps: RGB,YUV,BILINEAR,HIGH_FILTER,STRETCH_YUV,STRETCH_RGB,IMMEDIATE,HDR (MPO3)
MPO Stretch: 10.000X - 0.500X
MPO Media Hints: resizing, colorspace Conversion
MPO Formats: NV12,P010,YUY2,R16G16B16A16_FLOAT,R10G10B10A2_UNORM,R8G8B8A8_UNORM,B8G8R8A8_UNORM
PanelFitter Caps: RGB,YUV,BILINEAR,HIGH_FILTER,STRETCH_YUV,STRETCH_RGB,IMMEDIATE,HDR (MPO3)
PanelFitter Stretch: 10.000X - 0.500X

-------------
Sound Devices
-------------
Description: G32QC A (NVIDIA High Definition Audio)
Default Sound Playback: No
Default Voice Playback: No
Hardware ID: HDAUDIO\FUNC_01&VEN_10DE&DEV_009E&SUBSYS_1569F280&REV_1001
Manufacturer ID: N/A
Product ID: N/A
Type: N/A
Driver Name: nvhda64v.sys
Driver Version: 1.3.40.14 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 19.01.2023 02:00:00, 121880 bytes
Other Files:
Driver Provider: NVIDIA Corporation
HW Accel Level: Emulation Only
Cap Flags: 0xF1F
Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

Description: Lautsprecher (Realtek(R) Audio)
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0897&SUBSYS_1458A194&REV_1004
Manufacturer ID: N/A
Product ID: N/A
Type: N/A
Driver Name: RTKVHD64.sys
Driver Version: 6.0.9225.1 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 17.08.2021 02:00:00, 6505000 bytes
Other Files:
Driver Provider: Realtek Semiconductor Corp.
HW Accel Level: Emulation Only
Cap Flags: 0xF1F
Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

Description: Realtek Digital Output (Realtek(R) Audio)
Default Sound Playback: No
Default Voice Playback: No
Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0897&SUBSYS_1458A194&REV_1004
Manufacturer ID: N/A
Product ID: N/A
Type: N/A
Driver Name: RTKVHD64.sys
Driver Version: 6.0.9225.1 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 17.08.2021 02:00:00, 6505000 bytes
Other Files:
Driver Provider: Realtek Semiconductor Corp.
HW Accel Level: Emulation Only
Cap Flags: 0xF1F
Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

---------------------
Sound Capture Devices
---------------------
---------------------
Video Capture Devices
Number of Devices: 0
---------------------
-------------------
DirectInput Devices
-------------------
Device Name: Maus
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a

Device Name: Tastatur
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a

Device Name: Logitech G710 Keyboard
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC24D
FF Driver: n/a

Device Name: Intel(R) HID Event Filter
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x8087, 0x0A1E
FF Driver: n/a

Device Name: Intel(R) HID Event Filter
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x8087, 0x0A1E
FF Driver: n/a

Device Name: Konvertiertes PDC (Portable Device Control)-Gerät
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x045E, 0x0000
FF Driver: n/a

Device Name: Intel(R) HID Event Filter
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x8087, 0x0A1E
FF Driver: n/a

Device Name: Intel(R) HID Event Filter
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x8087, 0x0A1E
FF Driver: n/a

Device Name: Intel(R) HID Event Filter
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x8087, 0x0A1E
FF Driver: n/a

Device Name: Konvertiertes PDC (Portable Device Control)-Gerät
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x045E, 0x0000
FF Driver: n/a

Device Name: Intel(R) HID Event Filter
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x8087, 0x0A1E
FF Driver: n/a

Device Name: Intel(R) HID Event Filter
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x8087, 0x0A1E
FF Driver: n/a

Device Name: Intel(R) HID Event Filter
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x8087, 0x0A1E
FF Driver: n/a

Device Name: Intel(R) HID Event Filter
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x8087, 0x0A1E
FF Driver: n/a

Device Name: MX518 Gaming Mouse
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC08E
FF Driver: n/a

Device Name: MX518 Gaming Mouse
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC08E
FF Driver: n/a

Device Name: Intel(R) HID Event Filter
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x8087, 0x0A1E
FF Driver: n/a

Device Name: MX518 Gaming Mouse
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC08E
FF Driver: n/a

Device Name: Intel(R) HID Event Filter
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x8087, 0x0A1E
FF Driver: n/a

Device Name: MX518 Gaming Mouse
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC08E
FF Driver: n/a

Device Name: Intel(R) HID Event Filter
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x8087, 0x0A1E
FF Driver: n/a

Device Name: Intel(R) HID Event Filter
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x8087, 0x0A1E
FF Driver: n/a

Device Name: Intel(R) HID Event Filter
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x8087, 0x0A1E
FF Driver: n/a

Device Name: Intel(R) HID Event Filter
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x8087, 0x0A1E
FF Driver: n/a

Device Name: ITE Device
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x048D, 0x5702
FF Driver: n/a

Device Name: ITE Device
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x048D, 0x5702
FF Driver: n/a

Device Name: Intel(R) HID Event Filter
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x8087, 0x0A1E
FF Driver: n/a

Device Name: Logitech G710 Keyboard
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC24D
FF Driver: n/a

Device Name: Intel(R) HID Event Filter
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x8087, 0x0A1E
FF Driver: n/a

Poll w/ Interrupt: No

-----------
USB Devices
-----------
+ USB-Root-Hub (USB 3.0)
| Vendor/Product ID: 0x8086, 0x7AE0
| Matching Device ID: USB\ROOT_HUB30
| Service: USBHUB3
| Driver: USBHUB3.SYS, 5/10/2023 09:58:34, 722240 bytes
|
+-+ USB-Verbundgerät
| | Vendor/Product ID: 0x046D, 0xC08E
| | Location: Port_#0007.Hub_#0001
| | Matching Device ID: USB\COMPOSITE
| | Service: usbccgp
| | Driver: usbccgp.sys, 2/14/2023 21:17:04, 226640 bytes
| |
| +-+ USB-Eingabegerät
| | | Vendor/Product ID: 0x046D, 0xC08E
| | | Location: 0000.0014.0000.007.000.000.000.000.000
| | | Matching Device ID: USB\Class_03&SubClass_01
| | | Service: HidUsb
| | | Driver: hidusb.sys, 11/9/2022 12:43:53, 77824 bytes
| | | Driver: hidclass.sys, 11/9/2022 12:43:53, 278528 bytes
| | | Driver: hidparse.sys, 11/9/2022 12:43:53, 90112 bytes
| | |
| | +-+ HID-konforme Maus
| | | | Vendor/Product ID: 0x046D, 0xC08E
| | | | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE
| | | | Service: mouhid
| | | | Driver: mouhid.sys, 5/7/2022 07:19:25, 69632 bytes
| | | | Driver: mouclass.sys, 5/7/2022 07:19:25, 95592 bytes
| | |
| +-+ USB-Eingabegerät
| | | Vendor/Product ID: 0x046D, 0xC08E
| | | Location: 0000.0014.0000.007.000.000.000.000.000
| | | Matching Device ID: USB\Class_03
| | | Service: HidUsb
| | | Driver: hidusb.sys, 11/9/2022 12:43:53, 77824 bytes
| | | Driver: hidclass.sys, 11/9/2022 12:43:53, 278528 bytes
| | | Driver: hidparse.sys, 11/9/2022 12:43:53, 90112 bytes
| | |
| | +-+ HID-Tastatur
| | | | Vendor/Product ID: 0x046D, 0xC08E
| | | | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD
| | | | Service: kbdhid
| | | | Driver: kbdhid.sys, 5/7/2022 07:19:25, 73728 bytes
| | | | Driver: kbdclass.sys, 5/7/2022 07:19:25, 95576 bytes
| |
+-+ Generischer USB-Hub
| | Vendor/Product ID: 0x05E3, 0x0608
| | Location: Port_#0006.Hub_#0001
| | Matching Device ID: USB\USB20_HUB
| | Service: USBHUB3
| | Driver: USBHUB3.SYS, 5/10/2023 09:58:34, 722240 bytes
| |
| +-+ USB-Verbundgerät
| | | Vendor/Product ID: 0x046D, 0xC24D
| | | Location: Port_#0001.Hub_#0002
| | | Matching Device ID: USB\COMPOSITE
| | | Service: usbccgp
| | | Driver: usbccgp.sys, 2/14/2023 21:17:04, 226640 bytes
| | |
| | +-+ USB-Eingabegerät
| | | | Vendor/Product ID: 0x046D, 0xC24D
| | | | Location: 0000.0014.0000.006.001.000.000.000.000
| | | | Matching Device ID: USB\Class_03&SubClass_01
| | | | Service: HidUsb
| | | | Driver: hidusb.sys, 11/9/2022 12:43:53, 77824 bytes
| | | | Driver: hidclass.sys, 11/9/2022 12:43:53, 278528 bytes
| | | | Driver: hidparse.sys, 11/9/2022 12:43:53, 90112 bytes
| | | |
| | | +-+ HID-Tastatur
| | | | | Vendor/Product ID: 0x046D, 0xC24D
| | | | | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD
| | | | | Service: kbdhid
| | | | | Driver: kbdhid.sys, 5/7/2022 07:19:25, 73728 bytes
| | | | | Driver: kbdclass.sys, 5/7/2022 07:19:25, 95576 bytes
| | | |
| | +-+ USB-Eingabegerät
| | | | Vendor/Product ID: 0x046D, 0xC24D
| | | | Location: 0000.0014.0000.006.001.000.000.000.000
| | | | Matching Device ID: USB\Class_03
| | | | Service: HidUsb
| | | | Driver: hidusb.sys, 11/9/2022 12:43:53, 77824 bytes
| | | | Driver: hidclass.sys, 11/9/2022 12:43:53, 278528 bytes
| | | | Driver: hidparse.sys, 11/9/2022 12:43:53, 90112 bytes
| | | |
| | | +-+ HID-Tastatur
| | | | | Vendor/Product ID: 0x046D, 0xC24D
| | | | | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD
| | | | | Service: kbdhid
| | | | | Driver: kbdhid.sys, 5/7/2022 07:19:25, 73728 bytes
| | | | | Driver: kbdclass.sys, 5/7/2022 07:19:25, 95576 bytes

----------------
Gameport Devices
----------------

------------
PS/2 Devices
------------
+ HID-Tastatur
| Vendor/Product ID: 0x045E, 0x0000
| Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD
| Service: kbdhid
| Driver: kbdhid.sys, 5/7/2022 07:19:25, 73728 bytes
| Driver: kbdclass.sys, 5/7/2022 07:19:25, 95576 bytes
|
+ HID-Tastatur
| Vendor/Product ID: 0x8087, 0x0000
| Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD
| Service: kbdhid
| Driver: kbdhid.sys, 5/7/2022 07:19:25, 73728 bytes
| Driver: kbdclass.sys, 5/7/2022 07:19:25, 95576 bytes

------------------------
Disk & DVD/CD-ROM Drives
------------------------
Drive: C:
Free Space: 1071.2 GB
Total Space: 1906.8 GB
File System: NTFS
Model: Samsung SSD 980 PRO 2TB

--------------
System Devices
--------------
Name: Intel(R) PEG10 - 460D
Device ID: PCI\VEN_8086&DEV_460D&SUBSYS_50001458&REV_02\3&11583659&0&08
Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.22621.1635 (German), 5/10/2023 09:58:26, 570736 bytes

Name: Standardmäßiger NVM Express-Controller
Device ID: PCI\VEN_144D&DEV_A80A&SUBSYS_A801144D&REV_00\4&97A1985&0&0030
Driver: C:\WINDOWS\system32\DRIVERS\stornvme.sys, 10.00.22621.1635 (English), 5/10/2023 09:58:26, 251200 bytes

Name: Intel(R) Host Bridge/DRAM Registers - 4668
Device ID: PCI\VEN_8086&DEV_4668&SUBSYS_50001458&REV_02\3&11583659&0&00
Driver: n/a

Name: Intel(R) Management Engine Interface #1
Device ID: PCI\VEN_8086&DEV_7AE8&SUBSYS_1C3A1458&REV_11\3&11583659&0&B0
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\heci.inf_amd64_c22251d5ea82b3c3\x64\TeeDriverW10x64.sys, 2131.01.0004.0000 (English), 8/19/2021 05:30:18, 309384 bytes

Name: Intel(R) Serial IO I2C Host Controller - 7ACE
Device ID: PCI\VEN_8086&DEV_7ACE&SUBSYS_00000000&REV_11\3&11583659&0&AA
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ialpss2_i2c_adl.inf_amd64_778b19a5f4d49cba\iaLPSS2_I2C_ADL.sys, 30.100.2131.0026 (English), 7/29/2021 05:04:10, 202896 bytes

Name: Intel(R) USB 3.20 eXtensible-Hostcontroller – 1.20 (Microsoft)
Device ID: PCI\VEN_8086&DEV_7AE0&SUBSYS_50071458&REV_11\3&11583659&0&A0
Driver: C:\WINDOWS\system32\DRIVERS\USBXHCI.SYS, 10.00.22621.1635 (German), 5/10/2023 09:58:34, 677232 bytes
Driver: C:\WINDOWS\system32\DRIVERS\UMDF\UsbXhciCompanion.dll, 10.00.22621.1635 (English), 5/10/2023 09:58:34, 170824 bytes

Name: Intel(R) Serial IO I2C Host Controller - 7AFC
Device ID: PCI\VEN_8086&DEV_7AFC&SUBSYS_00000000&REV_11\3&11583659&0&C8
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ialpss2_i2c_adl.inf_amd64_778b19a5f4d49cba\iaLPSS2_I2C_ADL.sys, 30.100.2131.0026 (English), 7/29/2021 05:04:10, 202896 bytes

Name: Intel(R) SMBus - 7AA3
Device ID: PCI\VEN_8086&DEV_7AA3&SUBSYS_50011458&REV_11\3&11583659&0&FC
Driver: n/a

Name: Intel(R) LPC Controller/eSPI Controller (Z690) - 7A84
Device ID: PCI\VEN_8086&DEV_7A84&SUBSYS_50011458&REV_11\3&11583659&0&F8
Driver: C:\WINDOWS\system32\DRIVERS\msisadrv.sys, 10.00.22621.0001 (English), 5/7/2022 07:19:04, 54608 bytes

Name: Intel(R) Serial IO I2C Host Controller - 7ACC
Device ID: PCI\VEN_8086&DEV_7ACC&SUBSYS_00000000&REV_11\3&11583659&0&A8
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ialpss2_i2c_adl.inf_amd64_778b19a5f4d49cba\iaLPSS2_I2C_ADL.sys, 30.100.2131.0026 (English), 7/29/2021 05:04:10, 202896 bytes

Name: High Definition Audio-Controller
Device ID: PCI\VEN_8086&DEV_7AD0&SUBSYS_A1941458&REV_11\3&11583659&0&FB
Driver: C:\WINDOWS\system32\DRIVERS\hdaudbus.sys, 10.00.22621.1635 (English), 5/10/2023 09:58:24, 192512 bytes
Driver: C:\WINDOWS\system32\DRIVERS\drmk.sys, 10.00.22621.1344 (English), 3/15/2023 12:00:31, 143360 bytes
Driver: C:\WINDOWS\system32\DRIVERS\portcls.sys, 10.00.22621.1344 (English), 3/15/2023 12:00:31, 475136 bytes

Name: Realtek Gaming 2.5GbE Family Controller
Device ID: PCI\VEN_10EC&DEV_8125&SUBSYS_E0001458&REV_05\01000000684CE00000
Driver: C:\WINDOWS\system32\DRIVERS\rt640x64.sys, 10.50.0511.2021 (German), 8/12/2021 21:19:54, 1151992 bytes

Name: Intel(R) Serial IO I2C Host Controller - 7ACF
Device ID: PCI\VEN_8086&DEV_7ACF&SUBSYS_00000000&REV_11\3&11583659&0&AB
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ialpss2_i2c_adl.inf_amd64_778b19a5f4d49cba\iaLPSS2_I2C_ADL.sys, 30.100.2131.0026 (English), 7/29/2021 05:04:10, 202896 bytes

Name: Intel(R) Serial IO I2C Host Controller - 7AFD
Device ID: PCI\VEN_8086&DEV_7AFD&SUBSYS_00000000&REV_11\3&11583659&0&C9
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ialpss2_i2c_adl.inf_amd64_778b19a5f4d49cba\iaLPSS2_I2C_ADL.sys, 30.100.2131.0026 (English), 7/29/2021 05:04:10, 202896 bytes

Name: Intel(R) PEG60 - 464D
Device ID: PCI\VEN_8086&DEV_464D&SUBSYS_00000000&REV_02\3&11583659&0&30
Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.22621.1635 (German), 5/10/2023 09:58:26, 570736 bytes

Name: NVIDIA GeForce RTX 3070
Device ID: PCI\VEN_10DE&DEV_2488&SUBSYS_F2801569&REV_A1\4&AA66160&0&0008
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\NVWMI\nvPerfProvider.man, 4/26/2023 01:34:15, 14175 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\NVWMI\nvWmi.mof, 4/26/2023 01:34:15, 148921 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\NVWMI\nvWmi64.exe, 2.36.0000.0000 (English), 4/26/2023 18:48:14, 4513304 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\Display.NvContainer\MessageBus.dll, 1.22.2758.1620 (English), 4/26/2023 18:47:16, 7542560 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\Display.NvContainer\NVDisplay.Container.exe, 1.37.3103.4323 (English), 4/26/2023 18:47:18, 1014768 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\Display.NvContainer\NvContainerRecovery.bat, 4/26/2023 01:34:15, 1951 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\Display.NvContainer\dlsargs.xml, 4/26/2023 01:34:15, 544 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\Display.NvContainer\dlsnetparams.csv, 4/26/2023 01:34:15, 341661 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\Display.NvContainer\messagebus_client.conf, 4/26/2023 01:34:15, 57 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\Display.NvContainer\nvgwls.exe, 4/26/2023 18:47:20, 3940848 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\Display.NvContainer\nvtopps.db3, 4/26/2023 01:34:15, 126976 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\Display.NvContainer\plugins\LocalSystem\NvXDCore.dll, 31.00.0015.3179 (English), 4/26/2023 18:47:30, 1819632 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\Display.NvContainer\plugins\LocalSystem\NvcDispCorePlugin.dll, 31.00.0015.3179 (English), 4/26/2023 18:47:24, 523264 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\Display.NvContainer\plugins\LocalSystem\NvcDispWatchdog.dll, 1.37.3103.4323 (English), 4/26/2023 18:47:26, 738816 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\Display.NvContainer\plugins\LocalSystem\_DisplayDriverRAS.dll, 1.10.0000.0000 (English), 4/26/2023 18:47:32, 2713112 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\Display.NvContainer\plugins\LocalSystem\_NvMsgBusBroadcast.dll, 1.34.3030.7627 (English), 4/26/2023 18:47:34, 3192304 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\Display.NvContainer\plugins\LocalSystem\messagebus.conf, 4/26/2023 01:34:15, 57 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\Display.NvContainer\plugins\LocalSystem\wksServicePluginZ.dll, 31.00.0015.3179 (English), 4/26/2023 18:47:32, 267248 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\Display.NvContainer\plugins\Session\_NvGSTPlugin.dll, 31.00.0015.3179 (English), 4/26/2023 18:47:42, 2653680 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\Display.NvContainer\plugins\Session\_nvtopps.dll, 31.00.0015.3179 (English), 4/26/2023 18:47:44, 11941872 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\Display.NvContainer\plugins\Session\nvprofileupdaterplugin.dll, 31.00.0015.3179 (English), 4/26/2023 18:47:34, 2230296 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\Display.NvContainer\plugins\Session\nvxdsyncplugin.dll, 8.17.0015.3179 (English), 4/26/2023 18:47:38, 1830400 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\Display.NvContainer\plugins\Session\wksServicePlugin.dll, 31.00.0015.3179 (English), 4/26/2023 18:47:40, 309232 bytes
Driver: C:\WINDOWS\system32\DRIVERS\NVIDIA Corporation\Drs\dbInstaller.exe, 31.00.0015.3179 (English), 4/26/2023 18:40:38, 732656 bytes
Driver: C:\WINDOWS\system32\DRIVERS\NVIDIA Corporation\Drs\nvdrsdb.bin, 4/26/2023 01:34:15, 1901716 bytes
Driver: C:\WINDOWS\system32\nvcpl.dll, 8.17.0015.3179 (English), 4/26/2023 18:41:20, 5835288 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nv3dappshext.dll, 6.14.0015.3179 (English), 4/26/2023 18:40:52, 1004568 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nv3dappshextr.dll, 6.14.0015.3179 (German), 4/26/2023 18:40:54, 97816 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvcoproc.bin, 4/26/2023 01:34:15, 10355057 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvcpl.dll, 8.17.0015.3179 (English), 4/26/2023 18:41:20, 5835288 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvdevtools.dll, 31.00.0015.3179 (English), 4/26/2023 18:41:58, 4586008 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvdevtoolsr.dll, 31.00.0015.3179 (German), 4/26/2023 18:42:02, 245808 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvdisps.dll, 31.00.0015.3179 (English), 4/26/2023 18:42:04, 11649560 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvdispsr.dll, 31.00.0015.3179 (German), 4/26/2023 18:42:06, 11551256 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvgames.dll, 31.00.0015.3179 (English), 4/26/2023 18:42:32, 12479464 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvgamesr.dll, 31.00.0015.3179 (German), 4/26/2023 18:42:34, 13252144 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvlicensings.dll, 6.14.0015.3179 (English), 4/26/2023 18:43:20, 4551664 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvlicensingsr.dll, 6.14.0015.3179 (German), 4/26/2023 18:43:22, 307248 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvshext.dll, 1.02.0000.0001 (English), 4/26/2023 18:45:24, 133632 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvsmartmax.dll, 6.14.0010.10003 (English), 4/26/2023 18:45:28, 201200 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvsmartmax64.dll, 6.14.0010.10003 (English), 4/26/2023 18:45:30, 239600 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvsmartmaxapp.exe, 6.14.0010.10003 (English), 4/26/2023 18:45:32, 274416 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvsmartmaxapp64.exe, 6.14.0010.10003 (English), 4/26/2023 18:45:32, 285168 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvsvc64.dll, 31.00.0015.3179 (German), 4/26/2023 18:45:40, 2667056 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvsvcr.dll, 31.00.0015.3179 (German), 4/26/2023 18:45:42, 1801728 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvsvs.dll, 31.00.0015.3179 (English), 4/26/2023 18:45:44, 5096432 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvsvsr.dll, 31.00.0015.3179 (English), 4/26/2023 18:45:46, 2013720 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvui.dll, 8.17.0015.3179 (English), 4/26/2023 18:45:48, 6629400 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvuir.dll, 8.17.0015.3179 (German), 4/26/2023 18:45:52, 2648600 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvvitvs.dll, 31.00.0015.3179 (English), 4/26/2023 18:45:56, 7451184 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvvitvsr.dll, 31.00.0015.3179 (German), 4/26/2023 18:45:58, 4227096 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvwss.dll, 31.00.0015.3179 (English), 4/26/2023 18:46:34, 12259864 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvwssr.dll, 31.00.0015.3179 (German), 4/26/2023 18:46:34, 9527320 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvxdapix.dll, 8.17.0015.3179 (English), 4/26/2023 18:46:38, 9272816 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvxdbat.dll, 8.17.0015.3179 (English), 4/26/2023 18:46:44, 1645032 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvxdplcy.dll, 8.17.0015.3179 (English), 4/26/2023 18:46:46, 1889264 bytes
Driver: C:\WINDOWS\system32\lxss\lib\libcuda.so, 4/26/2023 01:34:15, 154096 bytes
Driver: C:\WINDOWS\system32\lxss\lib\libcuda.so.1, 4/26/2023 01:34:15, 154096 bytes
Driver: C:\WINDOWS\system32\lxss\lib\libcuda.so.1.1, 4/26/2023 01:34:15, 154096 bytes
Driver: C:\WINDOWS\system32\lxss\lib\libnvcuvid.so, 4/26/2023 01:34:15, 10411192 bytes
Driver: C:\WINDOWS\system32\lxss\lib\libnvcuvid.so.1, 4/26/2023 01:34:15, 10411192 bytes
Driver: C:\WINDOWS\system32\lxss\lib\libnvdxdlkernels.so, 4/26/2023 01:34:15, 36576952 bytes
Driver: C:\WINDOWS\system32\lxss\lib\libnvidia-encode.so, 4/26/2023 01:34:15, 547432 bytes
Driver: C:\WINDOWS\system32\lxss\lib\libnvidia-encode.so.1, 4/26/2023 01:34:15, 547432 bytes
Driver: C:\WINDOWS\system32\lxss\lib\libnvidia-ml.so.1, 4/26/2023 01:34:15, 223048 bytes
Driver: C:\WINDOWS\system32\lxss\lib\libnvidia-opticalflow.so, 4/26/2023 01:34:15, 362960 bytes
Driver: C:\WINDOWS\system32\lxss\lib\libnvidia-opticalflow.so.1, 4/26/2023 01:34:15, 362960 bytes
Driver: C:\WINDOWS\system32\lxss\lib\libnvoptix.so.1, 4/26/2023 01:34:15, 68560 bytes
Driver: C:\WINDOWS\system32\lxss\lib\libnvwgf2umx.so, 4/26/2023 01:34:15, 71873376 bytes
Driver: C:\WINDOWS\system32\lxss\lib\nvidia-smi, 4/26/2023 01:34:15, 634504 bytes
Driver: C:\WINDOWS\system32\DRIVERS\NVIDIA Corporation\license.txt, 6/7/2022 06:08:38, 28827 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\_nvngx.dll, 31.00.0015.3179 (English), 4/26/2023 18:47:12, 1529840 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\cudnn_infer64_7.dll, 4/26/2023 18:40:30, 22774224 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvngx.dll, 30.00.0014.9516 (English), 4/26/2023 18:43:28, 488648 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvngx_update.exe, 31.00.0015.3179 (English), 4/26/2023 18:43:32, 1189912 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvngxdlss.dll, 4/26/2023 18:43:30, 27328 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\NvCamera\FreqTransfer32.exe, 4/26/2023 18:47:48, 3707440 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\NvCamera\FreqTransfer64.exe, 4/26/2023 18:47:52, 4007984 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\NvCamera\GreenScreenBG01.jpg, 4/26/2023 01:34:15, 281528 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\NvCamera\GreenScreenBG02.jpg, 4/26/2023 01:34:15, 499736 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\NvCamera\HighresBlender32.exe, 4/26/2023 18:47:52, 3814912 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\NvCamera\HighresBlender64.exe, 4/26/2023 18:47:56, 4110384 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\NvCamera\NvCamera32.dll, 7.01.0817.0000 (English), 4/26/2023 18:47:56, 8062488 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\NvCamera\NvCamera64.dll, 7.01.0817.0000 (English), 4/26/2023 18:48:00, 8556016 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\NvCamera\NvCameraAllowlisting32.dll, 7.01.0817.0000 (English), 4/26/2023 18:48:02, 562160 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\NvCamera\NvCameraAllowlisting64.dll, 7.01.0817.0000 (English), 4/26/2023 18:48:04, 706072 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\NvCamera\NvCameraEnable.exe, 4/26/2023 18:48:04, 375344 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\NvCamera\NvImageConvert32.exe, 4/26/2023 18:48:06, 3711488 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\NvCamera\NvImageConvert64.exe, 4/26/2023 18:48:08, 3989016 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\NvCamera\ReShadeFXC32.exe, 2.00.0000.0000 (English), 4/26/2023 18:48:10, 776728 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\NvCamera\ReShadeFXC64.exe, 2.00.0000.0000 (English), 4/26/2023 18:48:10, 891416 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\NvCamera\ShotWithGeforce518x32.rgba, 4/26/2023 01:34:15, 66304 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\NvCamera\SphericalEquirect32.exe, 4/26/2023 18:48:12, 3660312 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\NvCamera\SphericalEquirect64.exe, 4/26/2023 18:48:14, 3914264 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\NvCamera\Sticker01.png, 4/26/2023 01:34:15, 49695 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\NvCamera\Sticker02.png, 4/26/2023 01:34:15, 474002 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\NvCamera\Sticker03.png, 4/26/2023 01:34:15, 380006 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\NvCamera\Sticker04.png, 4/26/2023 01:34:15, 86881 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\NvCamera\Sticker05.png, 4/26/2023 01:34:15, 59304 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\NvCamera\Sticker06.png, 4/26/2023 01:34:15, 13547 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\NvCamera\Sticker07.png, 4/26/2023 01:34:15, 6342 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\NvCamera\Sticker08.png, 4/26/2023 01:34:15, 96493 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\NvCamera\d3dcompiler_47_32.dll, 6.03.9600.16384 (English), 4/26/2023 18:47:46, 3471360 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\NvCamera\d3dcompiler_47_64.dll, 6.03.9600.16384 (English), 4/26/2023 18:47:46, 4178432 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\NvCamera\scratches.jpg, 4/26/2023 01:34:15, 346354 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\NvCamera\tools_licenses.txt, 4/26/2023 01:34:15, 15970 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\NvCamera\ui.tga, 4/26/2023 01:34:15, 120236 bytes
Driver: C:\WINDOWS\system32\MCU.exe, 1.01.5204.20580 (German), 4/26/2023 18:40:50, 853016 bytes
Driver: C:\WINDOWS\system32\nvdebugdump.exe, 6.14.0015.3179 (English), 4/26/2023 18:41:52, 457712 bytes
Driver: C:\WINDOWS\system32\nvidia-smi.exe, 8.17.0015.3179 (English), 4/26/2023 18:42:44, 741400 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvopencl32.dll, 31.00.0015.3179 (English), 4/26/2023 18:44:06, 18390552 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvopencl64.dll, 31.00.0015.3179 (English), 4/26/2023 18:44:12, 10605616 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvcompiler32.dll, 31.00.0015.3179 (English), 4/26/2023 18:40:58, 41544752 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvcompiler64.dll, 31.00.0015.3179 (English), 4/26/2023 18:41:08, 46333976 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvlddmkm.sys, 31.00.0015.3179 (English), 4/26/2023 18:43:08, 58251248 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvvm32.dll, 31.00.0015.3179 (English), 4/26/2023 18:46:02, 60341736 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvvm64.dll, 31.00.0015.3179 (English), 4/26/2023 18:46:16, 68047384 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\libcuda.so.1.1, 4/26/2023 01:34:15, 29653704 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\libcuda_loader.so, 4/26/2023 01:34:15, 154096 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\libnvcuvid.so.1, 4/26/2023 01:34:15, 10411192 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\libnvdxdlkernels.so, 4/26/2023 01:34:15, 36576952 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\libnvidia-encode.so.1, 4/26/2023 01:34:15, 547432 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\libnvidia-ml.so.1, 4/26/2023 01:34:15, 1556224 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\libnvidia-ml_loader.so, 4/26/2023 01:34:15, 223048 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\libnvidia-nvvm.so.4, 4/26/2023 01:34:15, 27511416 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\libnvidia-opticalflow.so.1, 4/26/2023 01:34:15, 362960 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\libnvidia-ptxjitcompiler.so.1, 4/26/2023 01:34:15, 21669384 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\libnvoptix_loader.so.1, 4/26/2023 01:34:15, 68560 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\libnvwgf2umx.so, 4/26/2023 01:34:15, 71873376 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nv-vk64.json, 4/26/2023 01:34:15, 671 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvDecMFTMjpeg.dll, 31.00.0015.3179 (English), 4/26/2023 18:41:54, 502808 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvDecMFTMjpegx.dll, 31.00.0015.3179 (English), 4/26/2023 18:41:56, 653824 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvEncMFTH264.dll, 31.00.0015.3179 (English), 4/26/2023 18:42:16, 890392 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvEncMFTH264x.dll, 31.00.0015.3179 (English), 4/26/2023 18:42:18, 1140264 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvEncMFThevc.dll, 31.00.0015.3179 (English), 4/26/2023 18:42:20, 896048 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvEncMFThevcx.dll, 31.00.0015.3179 (English), 4/26/2023 18:42:22, 1147952 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvcubins.bin, 4/26/2023 01:34:15, 26345360 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvcuda32.dll, 31.00.0015.3179 (English), 4/26/2023 18:41:24, 22597656 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvcuda64.dll, 31.00.0015.3179 (English), 4/26/2023 18:41:30, 9923096 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvd3dumx.dll, 31.00.0015.3179 (English), 4/26/2023 18:40:00, 49681184 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvdlistx.dll, 31.00.0015.3179 (English), 4/26/2023 18:40:14, 225648 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvdxdlkernels.dll, 4/26/2023 18:42:12, 80346648 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvidia-smi, 4/26/2023 01:34:15, 634504 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvldumdx.dll, 31.00.0015.3179 (English), 4/26/2023 18:40:18, 770664 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvml.dll, 8.17.0015.3179 (English), 4/26/2023 18:43:24, 1254376 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvoglv64.dll, 31.00.0015.3179 (English), 4/26/2023 18:43:52, 62551024 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvoptix.bin, 4/26/2023 01:34:15, 143085908 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvoptix.dll, 7.07.0000.0000 (English), 4/26/2023 18:44:20, 53352984 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvptxJitCompiler32.dll, 31.00.0015.3179 (English), 4/26/2023 18:44:42, 13664768 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvptxJitCompiler64.dll, 31.00.0015.3179 (English), 4/26/2023 18:44:46, 16423424 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvrtum64.dll, 31.00.0015.3179 (English), 4/26/2023 18:44:54, 105561600 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvwgf2umx.dll, 31.00.0015.3179 (English), 4/26/2023 18:40:38, 89310728 bytes
Driver: C:\WINDOWS\system32\NvFBC64.dll, 6.14.0015.3179 (English), 4/26/2023 18:42:30, 2166296 bytes
Driver: C:\WINDOWS\system32\NvIFR64.dll, 6.14.0015.3179 (English), 4/26/2023 18:43:02, 1536512 bytes
Driver: C:\WINDOWS\system32\OpenCL.dll, 3.00.0003.0000 (English), 4/26/2023 18:46:56, 1487872 bytes
Driver: C:\WINDOWS\system32\nvEncodeAPI64.dll, 31.00.0015.3179 (English), 4/26/2023 18:42:26, 979456 bytes
Driver: C:\WINDOWS\system32\nvapi64.dll, 31.00.0015.3179 (English), 4/26/2023 18:39:42, 7935568 bytes
Driver: C:\WINDOWS\system32\nvcuda.dll, 31.00.0015.3179 (English), 4/26/2023 18:41:40, 3430448 bytes
Driver: C:\WINDOWS\system32\nvcudadebugger.dll, 0.00.0000.0000 (English), 4/26/2023 18:41:34, 5911024 bytes
Driver: C:\WINDOWS\system32\nvcuvid.dll, 7.17.0015.3179 (English), 4/26/2023 18:41:48, 11650048 bytes
Driver: C:\WINDOWS\system32\nvinfo.pb, 4/26/2023 01:34:15, 104369 bytes
Driver: C:\WINDOWS\system32\nvml.dll, 8.17.0015.3179 (English), 4/26/2023 18:43:26, 851968 bytes
Driver: C:\WINDOWS\system32\nvofapi64.dll, 4/26/2023 18:43:36, 671256 bytes
Driver: C:\WINDOWS\system32\vulkan-1-999-0-0-0.dll, 1.03.0236.0000 (English), 4/26/2023 18:47:00, 1479216 bytes
Driver: C:\WINDOWS\system32\vulkan-1.dll, 1.03.0236.0000 (English), 4/26/2023 18:47:00, 1479216 bytes
Driver: C:\WINDOWS\system32\vulkaninfo-1-999-0-0-0.exe, 1.03.0236.0000 (English), 4/26/2023 18:47:06, 2172472 bytes
Driver: C:\WINDOWS\system32\vulkaninfo.exe, 1.03.0236.0000 (English), 4/26/2023 18:47:06, 2172472 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nv-vk32.json, 4/26/2023 01:34:15, 671 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvIccAdvancedColorIdentity.icm, 4/26/2023 01:34:15, 3288 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvd3dum.dll, 31.00.0015.3179 (English), 4/26/2023 18:39:48, 45956832 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvdispco64.exe, 1.00.0016.0000 (English), 4/26/2023 18:42:04, 1578472 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvdlist.dll, 31.00.0015.3179 (English), 4/26/2023 18:40:12, 188696 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvldumd.dll, 31.00.0015.3179 (English), 4/26/2023 18:40:16, 616192 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvoglv32.dll, 31.00.0015.3179 (English), 4/26/2023 18:43:40, 44152816 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvwgf2um.dll, 31.00.0015.3179 (English), 4/26/2023 18:40:22, 59617096 bytes
Driver: C:\WINDOWS\SysWow64\NvFBC.dll, 6.14.0015.3179 (English), 4/26/2023 18:42:28, 1621016 bytes
Driver: C:\WINDOWS\SysWow64\NvIFR.dll, 6.14.0015.3179 (English), 4/26/2023 18:43:00, 1194480 bytes
Driver: C:\WINDOWS\SysWow64\OpenCL.dll, 3.00.0003.0000 (English), 4/26/2023 18:46:54, 1226736 bytes
Driver: C:\WINDOWS\SysWow64\nvEncodeAPI.dll, 31.00.0015.3179 (English), 4/26/2023 18:42:24, 758768 bytes
Driver: C:\WINDOWS\SysWow64\nvapi.dll, 31.00.0015.3179 (English), 4/26/2023 18:39:38, 6798792 bytes
Driver: C:\WINDOWS\SysWow64\nvcuda.dll, 31.00.0015.3179 (English), 4/26/2023 18:41:38, 6083568 bytes
Driver: C:\WINDOWS\SysWow64\nvcuvid.dll, 7.17.0015.3179 (English), 4/26/2023 18:41:44, 13769216 bytes
Driver: C:\WINDOWS\SysWow64\nvofapi.dll, 4/26/2023 18:43:34, 506352 bytes
Driver: C:\WINDOWS\SysWow64\vulkan-1-999-0-0-0.dll, 1.03.0236.0000 (English), 4/26/2023 18:47:04, 1211448 bytes
Driver: C:\WINDOWS\SysWow64\vulkan-1.dll, 1.03.0236.0000 (English), 4/26/2023 18:47:04, 1211448 bytes
Driver: C:\WINDOWS\SysWow64\vulkaninfo-1-999-0-0-0.exe, 1.03.0236.0000 (English), 4/26/2023 18:47:10, 1607736 bytes
Driver: C:\WINDOWS\SysWow64\vulkaninfo.exe, 1.03.0236.0000 (English), 4/26/2023 18:47:10, 1607736 bytes
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\NvTelemetry64.dll, 14.03.0060.0000 (English), 4/26/2023 18:45:48, 4466136 bytes

Name: Intel(R) Platform Monitoring Technology-Treiber
Device ID: PCI\VEN_8086&DEV_467D&SUBSYS_00000000&REV_01\3&11583659&0&50
Driver: C:\WINDOWS\system32\DRIVERS\IntelPMT.sys, 10.00.22621.1485 (English), 3/28/2023 22:14:03, 91688 bytes

Name: Intel(R) SPI (flash) Controller - 7AA4
Device ID: PCI\VEN_8086&DEV_7AA4&SUBSYS_00000000&REV_11\3&11583659&0&FD
Driver: n/a

Name: Intel(R) PCI Express Root Port #1 - 7AB8
Device ID: PCI\VEN_8086&DEV_7AB8&SUBSYS_00000000&REV_11\3&11583659&0&E0
Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.22621.1635 (German), 5/10/2023 09:58:26, 570736 bytes

Name: Intel(R) Serial IO I2C Host Controller - 7ACD
Device ID: PCI\VEN_8086&DEV_7ACD&SUBSYS_00000000&REV_11\3&11583659&0&A9
Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ialpss2_i2c_adl.inf_amd64_778b19a5f4d49cba\iaLPSS2_I2C_ADL.sys, 30.100.2131.0026 (English), 7/29/2021 05:04:10, 202896 bytes

Name: Intel(R) Shared SRAM - 7AA7
Device ID: PCI\VEN_8086&DEV_7AA7&SUBSYS_00000000&REV_11\3&11583659&0&A2
Driver: n/a

Name: High Definition Audio-Controller
Device ID: PCI\VEN_10DE&DEV_228B&SUBSYS_F2801569&REV_A1\4&AA66160&0&0108
Driver: C:\WINDOWS\system32\DRIVERS\hdaudbus.sys, 10.00.22621.1635 (English), 5/10/2023 09:58:24, 192512 bytes
Driver: C:\WINDOWS\system32\DRIVERS\drmk.sys, 10.00.22621.1344 (English), 3/15/2023 12:00:31, 143360 bytes
Driver: C:\WINDOWS\system32\DRIVERS\portcls.sys, 10.00.22621.1344 (English), 3/15/2023 12:00:31, 475136 bytes

Name: Standardmäßiger SATA AHCI- Controller
Device ID: PCI\VEN_8086&DEV_7AE2&SUBSYS_B0051458&REV_11\3&11583659&0&B8
Driver: C:\WINDOWS\system32\DRIVERS\storahci.sys, 10.00.22621.0608 (English), 10/12/2022 09:29:54, 214352 bytes

Name: Intel(R) PCI Express Root Port #3 - 7ABA
Device ID: PCI\VEN_8086&DEV_7ABA&SUBSYS_50011458&REV_11\3&11583659&0&E2
Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.22621.1635 (German), 5/10/2023 09:58:26, 570736 bytes

------------------

EVR Power Information
---------------
Current Setting: {5C67A112-A4C9-483F-B4A7-1D473BECAFDC} (Quality)
Quality Flags: 2576
Enabled:
Force throttling
Allow half deinterlace
Allow scaling
Decode Power Usage: 100
Balanced Flags: 1424
Enabled:
Force throttling
Allow batching
Force half deinterlace
Force scaling
Decode Power Usage: 50
PowerFlags: 1424
Enabled:
Force throttling
Allow batching
Force half deinterlace
Force scaling
Decode Power Usage: 0

---------------
Diagnostics
---------------

Windows Error Reporting:
+++ WER0 +++:
Fehlerbucket 2108523322540578791, Typ 5
Ereignisname: RADAR_PRE_LEAK_64
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: X4.exe
P2: 6.10.0.0
P3: 10.0.22621.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Angefügte Dateien:
\\?\C:\Users\Laube\AppData\Local\Temp\RDR9BFF.tmp\empty.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.55435b9d-4453-497e-96f2-293a7931f523.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.7b86853f-2b27-4bea-aca9-472350cc0043.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.9100e35d-ef5a-4535-99cc-9516a5d50ef5.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.4ccbb1dc-7c72-481a-b475-64b323ef1aa0.tmp.xml

Diese Dateien befinden sich möglicherweise hier:
NULL

Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: fef073b9-3a56-402e-871d-c3b2406c1eaa
Berichtstatus: 268435456
Bucket mit Hash: 61c4357adf8746d5bd42faca58a857e7
CAB-Datei-Guid: 0
+++ WER1 +++:
Fehlerbucket 1182370049893755862, Typ 5
Ereignisname: RADAR_PRE_LEAK_64
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: steamwebhelper.exe
P2: 8.13.34.93
P3: 10.0.22621.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Angefügte Dateien:
\\?\C:\Users\Laube\AppData\Local\Temp\RDRBA9A.tmp\empty.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.2431aa60-db0f-4daf-a87b-ad4fd39cd1ff.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d8fad470-afaa-4c1d-bec0-a64f99f1127d.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.5ffcd8f4-728e-4d2c-943a-95bb1c6190de.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.69db903a-17b7-4168-936a-171709899699.tmp.xml

Diese Dateien befinden sich möglicherweise hier:
NULL

Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: 3bfdf5eb-f714-4f4c-b095-f37756c92f00
Berichtstatus: 268435456
Bucket mit Hash: e7503343733a07e430689f4bc0fa6bd6
CAB-Datei-Guid: 0
+++ WER2 +++:
Fehlerbucket 2157759659630986059, Typ 5
Ereignisname: RADAR_PRE_LEAK_64
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: TaleWorlds.MountAndBlade.Launcher.exe
P2: 1.0.0.0
P3: 10.0.22621.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Angefügte Dateien:
\\?\C:\Users\Laube\AppData\Local\Temp\RDRBFE9.tmp\empty.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.91edb6f6-c25a-44bd-b4d3-a7bc7dd16b82.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.079d9368-f68c-45e1-868e-3729c016f881.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.673321e8-0132-4cf7-afdc-04f37c0078b4.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.8dca8472-ffcb-426e-a3ca-846e6b5e41af.tmp.xml

Diese Dateien befinden sich möglicherweise hier:
NULL

Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: f24ecba5-95ea-4033-b4ab-9b6d19df01b4
Berichtstatus: 268435456
Bucket mit Hash: 3144dcf9ae0bca29adf1e6fa66f9034b
CAB-Datei-Guid: 0
+++ WER3 +++:
Fehlerbucket 2033612157341214627, Typ 4
Ereignisname: APPCRASH
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: TaleWorlds.MountAndBlade.Launcher.exe
P2: 1.0.0.0
P3: 6454eff2
P4: TaleWorlds.Native.dll
P5: 0.0.0.0
P6: 6454efef
P7: c0000005
P8: 00000000001e91b5
P9:
P10:

Angefügte Dateien:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.8fbe670e-b9e3-45d3-9968-5350027973e8.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.c2b81d7a-0af9-4e8e-b11d-991fa4cd0c90.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.8cd924d3-dab8-4d6c-91c1-1519786e0e3a.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.4754a767-d93b-4cc8-aca8-f33e4b47bef1.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.0d124b8a-b355-4b59-ba27-f56cf332a021.tmp.xml

Diese Dateien befinden sich möglicherweise hier:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_TaleWorlds.Mount_c6304bd6d8f66546e910daa575959d82f244_a2d79c73_432ea62d-5afa-49b7-8b93-32e496f736ff

Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: 48fa171f-2a12-4568-953f-5b6838dea28e
Berichtstatus: 268435456
Bucket mit Hash: 590a3971b6ff3d3e3c38d77b893d27a3
CAB-Datei-Guid: 0
+++ WER4 +++:
Fehlerbucket 1809038555669185253, Typ 5
Ereignisname: BEX64
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: svchost.exe_AppXSvc
P2: 10.0.22621.1
P3: 6dc5c2a5
P4: ntdll.dll
P5: 10.0.22621.1485
P6: b7f0154a
P7: 00000000000a3c90
P8: c0000409
P9: 000000000000000a
P10:

Angefügte Dateien:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.60feabfc-81da-4e5d-83c8-539b8f649d5e.tmp.WERInternalMetadata.xml

Diese Dateien befinden sich möglicherweise hier:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_svchost.exe_AppX_6435f14d0166fcfb4565be868a465346855c38_dbb11454_a08ff43d-c40c-4142-a73f-46a8ab861d9a

Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: e8725840-8362-4a90-bc6f-b013a78c9e6e
Berichtstatus: 268435456
Bucket mit Hash: 6c89320489431dd8791afefb4fa5c2e5
CAB-Datei-Guid: 0
+++ WER5 +++:
Fehlerbucket , Typ 0
Ereignisname: BEX64
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: svchost.exe_AppXSvc
P2: 10.0.22621.1
P3: 6dc5c2a5
P4: ntdll.dll
P5: 10.0.22621.1485
P6: b7f0154a
P7: 00000000000a3c90
P8: c0000409
P9: 000000000000000a
P10:

Angefügte Dateien:

Diese Dateien befinden sich möglicherweise hier:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_svchost.exe_AppX_6435f14d0166fcfb4565be868a465346855c38_dbb11454_a08ff43d-c40c-4142-a73f-46a8ab861d9a

Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: e8725840-8362-4a90-bc6f-b013a78c9e6e
Berichtstatus: 4
Bucket mit Hash:
CAB-Datei-Guid: 0
+++ WER6 +++:
Fehlerbucket , Typ 0
Ereignisname: crashpad_log
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: MicrosoftEdgeUpdate.exe
P2: 1.3.175.27
P3: InstallError
P4: 0x8004080f
P5:
P6:
P7:
P8:
P9:
P10:

Angefügte Dateien:
\\?\C:\ProgramData\Microsoft\EdgeUpdate\Log\MicrosoftEdgeUpdate.log
\\?\C:\Windows\Temp\msedge_installer.log

Diese Dateien befinden sich möglicherweise hier:
NULL

Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: dae31a06-401e-4d67-8623-13226a0eee50
Berichtstatus: 268697600
Bucket mit Hash:
CAB-Datei-Guid: 0
+++ WER7 +++:
Fehlerbucket 1570375870418103188, Typ 5
Ereignisname: crashpad_log
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: MicrosoftEdgeUpdate.exe
P2: 1.3.175.27
P3: InstallError
P4: 0x8004080f
P5:
P6:
P7:
P8:
P9:
P10:

Angefügte Dateien:
\\?\C:\ProgramData\Microsoft\EdgeUpdate\Log\MicrosoftEdgeUpdate.log
\\?\C:\Windows\Temp\msedge_installer.log
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.0284cfb0-9b42-403a-9a4f-ad2afc3b6feb.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.e679b5e9-05ca-4789-b7d1-f90f8bd96452.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ce61aa96-841c-421d-8fd3-3c77efe2d894.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.214ea0dc-97c2-4e38-af2b-e9c35e4920c1.tmp.xml

Diese Dateien befinden sich möglicherweise hier:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_MicrosoftEdgeUpd_7b16be7bdf552bdc43e24804272db49eab32bbd_00000000_dae31a06-401e-4d67-8623-13226a0eee50

Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: dae31a06-401e-4d67-8623-13226a0eee50
Berichtstatus: 268435456
Bucket mit Hash: 2c048445d3ee598f65cb1888b01dab94
CAB-Datei-Guid: 0
+++ WER8 +++:
Fehlerbucket 2191732388549419553, Typ 5
Ereignisname: RADAR_PRE_LEAK_64
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: msedge.exe
P2: 114.0.1823.43
P3: 10.0.22621.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Angefügte Dateien:
\\?\C:\Users\Laube\AppData\Local\Temp\RDRD9A4.tmp\empty.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f4ca7763-c1a2-426a-b276-2d7d92db11af.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.171b1af2-3b81-4ad3-9a16-b2cf2f16dd08.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.7c2136d0-04ca-48e9-905e-c7ccdc46a7a9.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.1e4c5dbc-1474-43da-bb38-f50054e8eef8.tmp.xml

Diese Dateien befinden sich möglicherweise hier:
NULL

Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: 4f91808b-6d56-46a8-be2e-cb5a2b7d5e21
Berichtstatus: 268435456
Bucket mit Hash: f110af1dda3c16f9de6a98febe34e221
CAB-Datei-Guid: 0
+++ WER9 +++:
Fehlerbucket 1432263838080912380, Typ 5
Ereignisname: AppHangB1
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: dllhost.exe
P2: 10.0.22621.1
P3: 05e70ed3
P4: 32f2
P5: 0
P6:
P7:
P8:
P9:
P10:

Angefügte Dateien:
\\?\C:\Users\Laube\AppData\Local\Temp\WER.92e7f9f4-07ef-41d7-bb76-b3cec7762695.tmp.appcompat.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.8a363942-7905-4a37-81f1-4c0bffe55573.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.65484579-b7ee-4027-bb73-617e37e98b85.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.62b5f602-7a66-4321-ab97-8ee8edf24bb9.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.a2eeb812-ee4b-4085-b386-8c2bdd1552ad.tmp.xml

Diese Dateien befinden sich möglicherweise hier:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppHang_dllhost.exe_9c9e4f4d3eca3271189e74edc52329e431fa816_e7c336b8_2b94fcf6-d8a2-4c7b-8ddd-17e80fc220e6

Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: 92dc0ef6-8db0-4b4b-8fed-62140fc47edc
Berichtstatus: 268435456
Bucket mit Hash: 6f54dbfccdba6d3073e06c5f4d734bfc
CAB-Datei-Guid: 0
Alan Phipps
Moderator (English)
Moderator (English)
Posts: 31812
Joined: Fri, 16. Apr 04, 19:21
x4

Re: Memory increses over time, Leak? New Game 6.0

Post by Alan Phipps »

@ Captain-Spaulding: If you mean the RADAR_PRE_LEAK_64 errors then those are non-critical and may routinely happen to lots of players/systems/apps. In your own DxDiag you will see several reported with quite a range of different applications.
A dog has a master; a cat has domestic staff.
badbane
Posts: 127
Joined: Tue, 29. Oct 13, 07:27
x4

Re: Memory increses over time, Leak? New Game 6.0

Post by badbane »

Just updating as I emailed priority support about the issue. I have sent them a save file dxdiag and vulcan info.
If anyone knows of a known way to crash the system to get a bug report. The problem is x4 has taken all of the memory so the debugger has no system memory left to run in so it ends up crashing and there is no debug report in my profile even if I start the game with the switches listed for the exit code 1113.
User avatar
Liupen
Posts: 53
Joined: Wed, 15. Sep 04, 20:59
x4

Re: Memory increses over time, Leak? New Game 6.0

Post by Liupen »

Hello, I too have this problem, i.e. the growth of the RAM occupation (about 13-14 GB out of 32) after playing for a while.
My game is modded (modified) though.
I don't know if this is connected to the occupation of a lot of ram, but it also happens to me that after almost 30 minutes of playing, the NPC characters start not loading, and I often have difficulty closing the game (steam) which remains blocked until when I close from the steam stop button or from the windows task manager.
From the task manager I see many instances from the game, maybe too many to freeze(?).
Also reinstalled Windows 11 and recently changed video card (RTX 4070).
Available to learn more, waiting for a solution.
Thank you.
David.
"Esistono due possibilità:
o siamo soli nell'universo, oppure non lo siamo.
Entrambe sono ugualmente terrificanti."
Arthur C. Clarke​
CBJ
EGOSOFT
EGOSOFT
Posts: 54300
Joined: Tue, 29. Apr 03, 00:56
x4

Re: Memory increses over time, Leak? New Game 6.0

Post by CBJ »

If your game is modified then there's a good chance that the problem you're seeing is unrelated to the one reported by other posters in this thread, especially if it happens a lot more quickly.

The good news is that we've been able to track down the more general problem. For those who are interested, it actually turned out to be related to the new Jolt physics system. Many thanks to those who have been so persistent in providing information, observations and savegames; it has really helped a lot. :)

The next update to the 6.20 Public Beta should include a fix for people to try out, and hopefully confirm that it's solved the problem.
User avatar
alt3rn1ty
Posts: 3525
Joined: Thu, 26. Jan 06, 19:45
x4

Re: Memory increses over time, Leak? New Game 6.0

Post by alt3rn1ty »

CBJ wrote: Fri, 30. Jun 23, 12:49 ~ The good news is that we've been able to track down the more general problem. For those who are interested, it actually turned out to be related to the new Jolt physics system. Many thanks to those who have been so persistent in providing information, observations and savegames; it has really helped a lot. :)

The next update to the 6.20 Public Beta should include a fix for people to try out, and hopefully confirm that it's solved the problem.
YEEES!.
I havent participated in this particular topic (I gave up reporting the problem after Ketraar told me "Its not feasible to expect Egosoft to test a problem for over 12 hours").

Very good to see this finally squashed, now I can go back to trying out veeeery long sessions of game play 8) (well when the new beta drops that is).
Spec's@2025-05-17 - Laptop - Acer Predator Helios Neo 16 AI - Win 11 x64
CPU - Intel Core Ultra 9 275HX 2.7-5.4ghz, RAM - 32gb DDR5 6400(OC),
Discrete GPU - NVidia Geforce RTX 5070 Ti, VRAM 12gb GDDR7,
SSD - M.2 PCIe NVME 1Tb
, OLED WQXGA 2560x1600.
:goner: Seeker of Sohnen. Long live Queen Polypheides. :boron:
badbane
Posts: 127
Joined: Tue, 29. Oct 13, 07:27
x4

Re: Memory increses over time, Leak? New Game 6.0

Post by badbane »

Good to hear as gave up and tried the latest 6.20 to see if it was better and the game time to crash was down to 45 minutes. Any Idea when the 6.20 patch will be coming out with the fix?
User avatar
alt3rn1ty
Posts: 3525
Joined: Thu, 26. Jan 06, 19:45
x4

Re: Memory increses over time, Leak? New Game 6.0

Post by alt3rn1ty »

badbane wrote: Tue, 4. Jul 23, 08:20 Good to hear as gave up and tried the latest 6.20 to see if it was better and the game time to crash was down to 45 minutes. Any Idea when the 6.20 patch will be coming out with the fix?
I dont think anyone will be able to answer that one, cant even give a rough guess. The current Beta testing is only at 6.20 Beta 1 HF1, the fix for this problem will probably be in 6.20 Beta 2 (which may be live today, or sometime this week anyway). Each increment of the beta can take anywhere between 1-2 weeks, and how many increments they do depends on what they have ready to go public in their very long list of items to-do. The MTS Beta got up to Beta 8 before it finished, but that was an unusually long testing period due to Egosoft needing it to be thoroughly tested before they went back to the drawing board to redesign some parts of it. A normal beta run can be anywhere between Beta 3 to Beta 5, all depends what they need to achieve and make sure it all works without any unforseen hiccups before it goes out to everyone. Its a complicated process and each one makes a huge amount of changes for the better, which all needs thoroughly testing with good detailled feedback from us (with our own jobs and lives to contend with, hence the long testing period Egosoft gives us all).
So the full release of the 6.20 patch to the general public, somewhere between 2-8 weeks, maybe. Could be next week for all I know if this beta phase only has 2 betas <shrugs>
If anyone wants to participate, read this.
Instructions for participation, read this.
Participants feedback goes here.
Spec's@2025-05-17 - Laptop - Acer Predator Helios Neo 16 AI - Win 11 x64
CPU - Intel Core Ultra 9 275HX 2.7-5.4ghz, RAM - 32gb DDR5 6400(OC),
Discrete GPU - NVidia Geforce RTX 5070 Ti, VRAM 12gb GDDR7,
SSD - M.2 PCIe NVME 1Tb
, OLED WQXGA 2560x1600.
:goner: Seeker of Sohnen. Long live Queen Polypheides. :boron:
CBJ
EGOSOFT
EGOSOFT
Posts: 54300
Joined: Tue, 29. Apr 03, 00:56
x4

Re: Memory increses over time, Leak? New Game 6.0

Post by CBJ »

We've just released 6.20 Beta 2 onto the Public Beta channel. Feel free to give that a go and report back on whether it seems to have solved the memory issue. :)

Please note that some increase in memory usage over time is to be expected, both due to caching of data and a tendency for the amount of universe content to increase as a game progresses, but this update should prevent the specific issue reported in this thread.
badbane
Posts: 127
Joined: Tue, 29. Oct 13, 07:27
x4

Re: Memory increses over time, Leak? New Game 6.0

Post by badbane »

Sweet I am loading the game up now.
User avatar
alt3rn1ty
Posts: 3525
Joined: Thu, 26. Jan 06, 19:45
x4

Re: Memory increses over time, Leak? New Game 6.0

Post by alt3rn1ty »

I started a long play through about six hours ago after downloading, going to run it constantly for 48 hours at least and see how things go.
Spec's@2025-05-17 - Laptop - Acer Predator Helios Neo 16 AI - Win 11 x64
CPU - Intel Core Ultra 9 275HX 2.7-5.4ghz, RAM - 32gb DDR5 6400(OC),
Discrete GPU - NVidia Geforce RTX 5070 Ti, VRAM 12gb GDDR7,
SSD - M.2 PCIe NVME 1Tb
, OLED WQXGA 2560x1600.
:goner: Seeker of Sohnen. Long live Queen Polypheides. :boron:
badbane
Posts: 127
Joined: Tue, 29. Oct 13, 07:27
x4

Re: Memory increses over time, Leak? New Game 6.0

Post by badbane »

Running the latest 6.20 update. It is still happening but the playtime is nearly 6 hours now rather than 1 hour. The update definitely has improved things. Looking to get more details for you guys.

Today was another repeat started around 5:30 pm and at 9:30 it just crashed. I am on the same save I have already submitted.
User avatar
alt3rn1ty
Posts: 3525
Joined: Thu, 26. Jan 06, 19:45
x4

Re: Memory increses over time, Leak? New Game 6.0

Post by alt3rn1ty »

CBJ wrote: Tue, 4. Jul 23, 17:31 We've just released 6.20 Beta 2 onto the Public Beta channel. Feel free to give that a go and report back on whether it seems to have solved the memory issue. :)

Please note that some increase in memory usage over time is to be expected, both due to caching of data and a tendency for the amount of universe content to increase as a game progresses, but this update should prevent the specific issue reported in this thread.
alt3rn1ty wrote: Wed, 5. Jul 23, 00:52 I started a long play through about six hours ago after downloading, going to run it constantly for 48 hours at least and see how things go.
@Devs / @CBJ .. Done that testing using 6.20 Beta 2, as usual for me no mods in use.

Well actually I did a 42 hour constant run, and took a snapshot of X4.exe memory use with VMMap
https://i.imgur.com/ptFrvy3.png

On my machine (see specs in signature below), the game slowly increases memory use for about 3 hours, and then tops out around 9.1gb memory use, and doesn't go higher (well there is a bit of up/down flutter but nothing higher that sticks).
See "Working Set" on the above screenshot.
I did several snapshots with VMMap during the 42 hour period, about every 8 hours. That screenshot is just before I finished the 42 hour period.

For a second (and more visual) opinion to VMMap, I remembered a utility for Skyrim SE, which uses Open Hardware Library (OHL) to access counters a game is affecting such as memory use/VRam/CPU percent/temperatures etcetera, its called Skyrim Performance Monitor 64 .. Which can be setup to launch another games .exe and monitor the same metrics (not guaranteed by the author, but when I asked he said it should be ok, and imho it works well with X4.exe so long as you do not configure anything Skyrim specific like its launcher and a few other things like dont enable In Game counters (it has by default an overlay for in-game in Skyrim SE, so you can see the metrics real time as you play .. Disable them for in-game in X4), and only need to view common game metrics). Oh and run the SPMx64 utility as Admin (Right click the Desktop Icon, choose properties, Compatability Tab, tick "Run as Administrator" and apply).

Its useful because it launches the game exe, and monitors the game metrics you specify for as long as the game is running, then it stops creating graphs when you close the game launched.

I ran it in the background, and got it to launch and monitor X4.exe for just over 4 hours, which gave a graph confirming VMMap findings ..
https://i.imgur.com/5YA6dlt.jpg

Top graph is the Memory and VRAM usage over the 4 hour period, maximum reached 9.1gb (which corroborates VMMap). And you can see between the 3 hour to 4 hour (end of graph) period, memory use does not increase. I could run it for a more extended period but thats good enough for me, I am very familiar with SPM (Once upon a time I made a mod for Skyrim called "Vanilla Reduced Textures", and used SPM extensively to see in every area of the game if I was getting close to maximum VRAM used on an old machine).

No crashes or fps issues during the 42 hour and 4 hour testing periods. During the 42 hour period I engaged with just about everything in the game, a bit of Station building/re-arranging, a thorough flythrough of just about every sector in the game landing at every large station along the way (a chain of fly-to's and dock and wait's with an AI Pilot, and me just standing in the cockpit so that all sectors traversed were High attention) so that just about every texture/resource was loaded, a couple of dogfights and ordering a couple of my fleets to go on coordinated attacks, and during the 4 hour period I did as many sectors fly through as possible plus a bit more management and fighting Kha'ak ..

For me and my laptop, thats a confirmed memory issues fixed :)
Thanks Devs.
Last edited by alt3rn1ty on Fri, 7. Jul 23, 18:31, edited 2 times in total.
Spec's@2025-05-17 - Laptop - Acer Predator Helios Neo 16 AI - Win 11 x64
CPU - Intel Core Ultra 9 275HX 2.7-5.4ghz, RAM - 32gb DDR5 6400(OC),
Discrete GPU - NVidia Geforce RTX 5070 Ti, VRAM 12gb GDDR7,
SSD - M.2 PCIe NVME 1Tb
, OLED WQXGA 2560x1600.
:goner: Seeker of Sohnen. Long live Queen Polypheides. :boron:
badbane
Posts: 127
Joined: Tue, 29. Oct 13, 07:27
x4

Re: Memory increses over time, Leak? New Game 6.0

Post by badbane »

Yea it is still ongoing for me. I can get much longer out of it. it climbs a lot slower for me but it still gets to 24 GB of total memory which fills my ram and vram. It seems to me that it starts climbing on the first autosave. Ten minutes in I see commited ram holding steady. Then after an autosave I see committed memory drop a bit however after that it starts to climb. Probly a Gig or more per hour. Previously it was four gigs per hour. Still the same thing the more I fly around or teleport the faster the memory grows.
CBJ
EGOSOFT
EGOSOFT
Posts: 54300
Joined: Tue, 29. Apr 03, 00:56
x4

Re: Memory increses over time, Leak? New Game 6.0

Post by CBJ »

Something else must be happening in your case, because we have tested with your file for quite some time and the problem is not happening for us with 6.20 Beta 2. We're getting the same sort of behaviour profile that alt3rn1ty observed: an initial increase for a while, after which it steadies off with occasional fluctuations. Please check that you are actually using the latest beta version and that you're not using any third party mods or tools.
Scoob
Posts: 11197
Joined: Thu, 27. Feb 03, 22:28
x4

Re: Memory increses over time, Leak? New Game 6.0

Post by Scoob »

One thing that's guaranteed to increase the memory used for me seems to be teleporting around a lot. If I'm just sitting on one station / pottering around one sector, remotely doing stuff the memory footprint remains under 10GB. If however, I'm teleporting around constantly to get personally involved in battles, or just to watch things go down, then memory usage increases notably. It's not uncommon to see 20GB+ allocated to the game in those situations. I've not experimented with using the Live Feed instead of going there myself, as I like to be in control of my viewpoint. The streaming view is cool, but when the camera cuts to a different angle just as something happens, well, that's not what I want in those instances.

Note: I have 32GB, so even over 26GB - about as high as I've noticed it go - wasn't a problem.
User avatar
alt3rn1ty
Posts: 3525
Joined: Thu, 26. Jan 06, 19:45
x4

Re: Memory increses over time, Leak? New Game 6.0

Post by alt3rn1ty »

A bit off topic but the thing that really pleased me in my performance test above was the game always seems to leave circa 20% of my 6gb VRAM free, which is a good thing, it leaves space for buffering textures in and out and also keeps the temperature of the Dedicated GPU down.

I have seen people modding their games in the past with more/better/bigger High Res textures who didn't realise it was because they were hitting the roof of the available VRAM constantly with too many high res textures, that their graphics cards were seriously overheating threatening to melt the chips solder (or at least in time form cracks in the solder due to excessive beyond manufacturer specs heat changes causing expansion/contraction, which would eventually stop the GPU from working, or at least cause strange graphics problems).

Good to see X4.exe is being careful in this regard leaving circa 20% VRAM free.
Spec's@2025-05-17 - Laptop - Acer Predator Helios Neo 16 AI - Win 11 x64
CPU - Intel Core Ultra 9 275HX 2.7-5.4ghz, RAM - 32gb DDR5 6400(OC),
Discrete GPU - NVidia Geforce RTX 5070 Ti, VRAM 12gb GDDR7,
SSD - M.2 PCIe NVME 1Tb
, OLED WQXGA 2560x1600.
:goner: Seeker of Sohnen. Long live Queen Polypheides. :boron:
badbane
Posts: 127
Joined: Tue, 29. Oct 13, 07:27
x4

Re: Memory increses over time, Leak? New Game 6.0

Post by badbane »

No mods or tools I even killed the steam overlay for the game.

I have continued to play so my probly has a ton more ships flying around. Literally the Min of Finance probly has 500 s class ships flying around in a sector. If i play x4 statically. IE X4 empire simulator the game seems to be okay. The moment I physically interact and start moving around and such like teleporting to my asgard and taking out a station. then Jumping to the base to talk to Boso. then building a ship s ship to unlock the Shield research. Thats when things are jumping up. I am on the latest build. I can leave the game unattended for some time now. I actively avoid being in the hq sector because There's probly 400 or more ships in that sector at any given time and my HQ is massive.

Verified that I am on 6.20. I can pot my latest save. I also spend time in SETA a lot as well. So I usually jump in a ship start guidance. Point to the gate. Hit Seta watch a video with X4 in the background. Go through the gate point at the next gate and hit SETA. If things get hairy I Teleport to a fleet protecting Hatikvas choice.

My station is spamming out ships for TEL, ARGON, and PARANID non stop. Jumping to a s ship and going to do the shield boost research. Now I am building four stations in several sectors. I'll upload the latest save.
User avatar
alt3rn1ty
Posts: 3525
Joined: Thu, 26. Jan 06, 19:45
x4

Re: Memory increses over time, Leak? New Game 6.0

Post by alt3rn1ty »

badbane wrote: Fri, 7. Jul 23, 19:56 ~ I also spend time in SETA a lot as well. So I usually jump in a ship start guidance. Point to the gate. Hit Seta watch a video with X4 in the background. Go through the gate point at the next gate and hit SETA. ~
I did most of the things you and Scoob said (Teleporting around and doing just about all I normally do in game, even had a miner on a long list of repeat orders mining and selling Nividium to my PHQ, which can occasionally cause problems if it gets into loops it cant resolve, I'm still investigating those problems) ..

But one thing I rarely do (never did it during my testing sessions) is use SETA.
Its notorious for breaking things you expect to happen. A huuuge amount of scripts are running in X4, but when everything is running at 6 x normal speed some things get skipped/lost because the game then has to cull some things to fit it all in the same slice of real time, trades are often not working well, ships get lost OOS when normally they would survive no problem .. I cant remember all the things affected but I found since the X4 game was released that SETA is generally bad if you dont want unexpected events to happen.
It used to be good in older games where you could set a slower speed (like only 2x normal game speed instead of 6x), but Egosoft will not be changing it (I think I get the vibe its technically a very difficult thing for them to do with X4).

Another thing I never do .. Watching videos with X4 running in the background.
If I am doing a long testing period, I have been guilty of alt tabbing out to make a post on Egosoft forums, and then closing the browser afterwards before returning to the game. Browsers these days can take a lot of CPU time and take up memory, variations of Chrome (Google/Edge/Chromium/Brave etc) with its sandboxed tabs can have multiple big wedges of system resources assigned to them, especially if you are streaming/buffering video.

So when playing X4 I tend to devote as much system resources to the game, the X series has always been heavy on CPU usage, but X4 is a game I consider we do not have the machine specs available for purchase yet to play it without any hitches and be able to simultaneously and comfortably multitask other forms of entertainment.

I dont even have GOG Galaxy running, I run the X4.exe directly.

I cant say those habits are causing your problems, but they certainly will not help the smooth running of this game, even people on this forum with the best of desktop rigs have issues with this games performance, to the extent they seriously cut back on things like how many advanced satellites are deployed and active. Really we need a future machine, X series usually does push the envelope a bit regardless of the specified minimum system setup, but I think personally X4 is a fair bit more ambitious/demanding than previous X games, so we need to either just run the game with the system as lean as possible for now, or wait until we have machines which can comfortably handle the game plus anything else we want to multitask at the same time.
If you haven't read it yet, have a look at viewtopic.php?f=180&t=420952&sid=8dc069 ... de723b6191
Imperial Good did quite an amazing job on that topic.
Spec's@2025-05-17 - Laptop - Acer Predator Helios Neo 16 AI - Win 11 x64
CPU - Intel Core Ultra 9 275HX 2.7-5.4ghz, RAM - 32gb DDR5 6400(OC),
Discrete GPU - NVidia Geforce RTX 5070 Ti, VRAM 12gb GDDR7,
SSD - M.2 PCIe NVME 1Tb
, OLED WQXGA 2560x1600.
:goner: Seeker of Sohnen. Long live Queen Polypheides. :boron:
badbane
Posts: 127
Joined: Tue, 29. Oct 13, 07:27
x4

Re: Memory increses over time, Leak? New Game 6.0

Post by badbane »

What you need to understand is Actual memory use is only 5 to 6 gb. Committed memory is memory that the game has allocated to it but may not be using. It is normal for the game to read and write to ram constantly. The game is saying I want more memory to put stuff and indeed I see over time the memory committed go down from time to time. The game is releasing the memory back to the OS however over time the game is grabbing more and more memory but isn't giving it back. At no time does the game actually use more that 8 gb of memory and most of the time the actual memory usage is around 4 GB.

In a perfect world the games committed memory should be around 8 gb of memory. If everything was perfect but realistically the game needs to have some extra memory. However, if the issue lies in the physics engine then flying around in busy systems where the OS has to calculate the physics for all the ships in a sector. Then it makes sense that whatever the cause it likely to be triggered when the engine is having to do a ton of physics calculations.

If the game is only using 6 GB consistently then at some point the Commited memory should top out or at the very least grow in small amounts.

I would bet that if you are OOS or even out of render range then egine isn't doing nearly as many physics calculations. My last play through only lasted an hour. Things seemed to be going well but I found myself in busy systems. Grand Exchange 1 where the PHQ is right now usually hast 50 to 100 ships landing and taking off from the station and I was in render range of that station a lot this last play through. I am currently hunting for ships to shoot me for the shield missions Tech tree and was flying around a lot this play through I never used SETA.

I am running a 8 core Ryzen 2700X and 16 GB of memory with an SSD The graphics card is a rtx 6700 with 12 GB GDDR.

I have played this game since its initial release and have archived Save games from 2018, 2019, and 2020 where i was hundreds of hours in, with multiple fleets, where I am to the point where I am clearing out the whole map. I would leave the game running for DAYS at a time without memory issues running in the background SETA ETC. This was even running on inferior hardware at the time.

I am playing the game just as I was then in 2018. This is definitely a new phenomenon as I am picking the game backup after the latest dlc release. Its a terran start and I have completed the terran story missions. What I can say is that initially after loading the game on the latest beta the issue was better. However several tens of hours of more play and the playtime is back to around an hour, if I am travelling around a lot. Teleporting does not seem to be the worst trigger problem. I did zero Seta this last playthrough and the latest play through only lasted an hour before the committed memory was at 19 GB.

Copy of the latest updates save below.
https://drive.google.com/drive/folders/ ... sp=sharing

Return to “X4: Foundations - Technical Support”