https://x.com/t3dotgg/status/1727978052238655952?s=46&t=vbktiL2gXRFBJ3M2LN2O8A
chrome or edge… which will have a dick pill ad on the new tab page first
3 Likes
Thanks! I’d forgotten, uh, Event Viewer was a thing. I’ll keep an eye on Event Viewer and see what I can find out.
2 Likes
It’s very easy to forget about for some reason! It often contains invaluable information though. At an old workplace of mine one of my co-workers put a grainy black-and-white printout of the Log Lady from Twin Peaks up on the wall with “ASK THE LOG” written in black Sharpie as a reminder, after we were talking about how much it helps if you remember to start the troubleshooting process that way. 
4 Likes
I did this, it seemed fine. I didn’t run into any issue traceable to cruft and my user directories were created on Windows 7 (or maybe even XP, I can’t remember).
But I mean yeah Windows is very complicated so I don’t think it can be ruled out that something in there might cause a weird glitch. But nowadays the risk is at least limited and you can troubleshoot your way out of any issue you run into after the upgrade.
Only the kind of obvious problem that pre-installing Windows 11 on the old computer is not an available option (since it doesn’t have the TPM)
So even if you’re planning to switch to a new boot drive, you’ll need to get the Windows 10 drive connected on the new computer, or make a perfect copy of it onto your new drive. For me that was a hassle because my new ITX build doesn’t have a lot of SATA ports and I use Bitlocker encryption.
1 Like
this is pretty sick
3 Likes
unsure about choco but winget does this
1 Like
i need your help hardware people.
I’ve been having this very strange problem with my computer. Here are the symptoms:
- Sometimes I get BSOD crashes - this is very rare, but maybe informative. I believe the error code is “DPC_WATCHDOG_VIOLATION”
- Most of the time I just get a hard crash - screen freezes and I have to force a restart.
- Before the crash, there are usually 1-2 second long intervals where all my sound is staticky, my mouse doesn’t work right, and sometimes my controller disconnects. This happens whether or not the devices in question are wireless. These intervals will occur 10-30 times before a crash. Sometimes there is no crash.
- If I restart when I notice the sound/kbm issues, about half the time they’ll go away and I won’t get a crash
Crashes tend to occur when I’m doing something fairly intensive, like playing Fortnite or streaming. However, it can happen with any game, there’s not a strong correlation between the game being intensive and there being crackling sound/kbm issues/eventual crash. On the other hand, I never notice it with fairly unintensive things like Retroarch. My gut says that this only happens when a game is fullscreen as well.
Things I have done to try and solve this:
- I thought this must be the audio drivers, and in fact uninstalling the special software for my headphones seems to have reduced crashing. But not completely eradicated it.
- I ran MemTest86 and got a clean bill of health
- I’m running GPU-Z to get logs before crashes. To me, none of it looks that remarkable, but I’m not sure. Here’s a log that occurred right before a crash:
Log
2023-04-02 22:03:50 , 315.0 , 625.2 , 44.3 , 53.1 , 56.0 , 0 , 0 , 0 , 0 , 3722 , 37 , 13 , 0 , 0 , 51.3 , 11.1 , 40.2 , 12.1 , 1.9 , 12.1 , 41.2 , 12.1 , 8.2 , 12.1 , 16.6 , 16 , 0.6620 , 51.0 , 6986 ,
2023-04-02 22:03:51 , 315.0 , 625.2 , 44.4 , 53.5 , 56.0 , 0 , 0 , 0 , 0 , 3722 , 37 , 13 , 0 , 0 , 52.1 , 11.7 , 40.4 , 12.1 , 2.1 , 12.1 , 41.6 , 12.1 , 8.4 , 12.1 , 16.8 , 16 , 0.6620 , 53.0 , 6986 ,
2023-04-02 22:03:52 , 315.0 , 625.2 , 44.4 , 53.1 , 56.0 , 0 , 0 , 0 , 0 , 3722 , 37 , 13 , 0 , 0 , 51.8 , 11.5 , 40.3 , 12.1 , 2.0 , 12.1 , 41.6 , 12.1 , 8.2 , 12.1 , 16.7 , 16 , 0.6620 , 49.0 , 6986 ,
2023-04-02 22:03:53 , 300.0 , 625.2 , 44.4 , 53.4 , 56.0 , 0 , 0 , 0 , 0 , 3722 , 36 , 13 , 0 , 0 , 51.5 , 11.1 , 40.4 , 12.1 , 2.0 , 12.1 , 41.3 , 12.1 , 8.2 , 12.2 , 16.6 , 16 , 0.6620 , 53.0 , 6986 ,
2023-04-02 22:03:54 , 300.0 , 625.2 , 44.5 , 53.4 , 56.0 , 0 , 0 , 0 , 0 , 3722 , 37 , 12 , 0 , 0 , 51.4 , 11.2 , 40.2 , 12.1 , 2.0 , 12.1 , 41.3 , 12.1 , 8.1 , 12.1 , 16.6 , 16 , 0.6620 , 54.0 , 6986 ,
2023-04-02 22:03:55 , 315.0 , 625.2 , 44.6 , 53.7 , 56.0 , 0 , 0 , 0 , 0 , 3722 , 38 , 13 , 0 , 0 , 52.2 , 11.7 , 40.5 , 12.1 , 2.2 , 12.1 , 41.6 , 12.1 , 8.4 , 12.1 , 16.8 , 16 , 0.6620 , 51.0 , 6981 ,
2023-04-02 22:03:56 , 315.0 , 625.2 , 44.6 , 53.6 , 56.0 , 0 , 0 , 0 , 0 , 3722 , 38 , 12 , 0 , 0 , 51.4 , 11.1 , 40.2 , 12.1 , 2.0 , 12.1 , 41.2 , 12.1 , 8.1 , 12.1 , 16.6 , 16 , 0.6620 , 51.0 , 6986 ,
2023-04-02 22:03:57 , 315.0 , 625.2 , 44.6 , 53.6 , 56.0 , 0 , 0 , 0 , 0 , 3722 , 37 , 12 , 0 , 0 , 51.3 , 11.1 , 40.2 , 12.1 , 2.0 , 12.1 , 41.1 , 12.1 , 8.1 , 12.1 , 16.5 , 16 , 0.6620 , 51.0 , 6985 ,
2023-04-02 22:03:58 , 315.0 , 625.2 , 44.6 , 53.6 , 56.0 , 0 , 0 , 0 , 0 , 3722 , 38 , 12 , 0 , 0 , 51.2 , 11.1 , 40.0 , 12.1 , 2.0 , 12.1 , 41.1 , 12.1 , 8.1 , 12.1 , 16.5 , 16 , 0.6620 , 51.0 , 6985 ,
2023-04-02 22:03:59 , 315.0 , 625.2 , 44.8 , 53.6 , 56.0 , 0 , 0 , 0 , 0 , 3722 , 40 , 13 , 0 , 0 , 51.4 , 11.3 , 40.1 , 12.1 , 2.0 , 12.1 , 41.2 , 12.1 , 8.2 , 12.1 , 16.6 , 16 , 0.6620 , 51.0 , 6986 ,
2023-04-02 22:04:00 , 315.0 , 625.2 , 44.8 , 53.6 , 56.0 , 0 , 0 , 0 , 0 , 3722 , 40 , 13 , 0 , 0 , 52.4 , 12.2 , 40.2 , 12.1 , 2.2 , 12.1 , 41.4 , 12.1 , 8.7 , 12.1 , 16.9 , 16 , 0.6620 , 52.0 , 6985 ,
2023-04-02 22:04:01 , 315.0 , 625.2 , 44.8 , 53.7 , 56.0 , 0 , 0 , 0 , 0 , 3722 , 38 , 12 , 0 , 0 , 51.8 , 11.7 , 40.1 , 12.1 , 2.1 , 12.1 , 41.3 , 12.1 , 8.4 , 12.1 , 16.7 , 16 , 0.6620 , 53.0 , 6984 ,
2023-04-02 22:04:02 , 300.0 , 625.2 , 44.8 , 53.5 , 56.0 , 0 , 0 , 0 , 0 , 3722 , 35 , 11 , 0 , 0 , 51.1 , 11.4 , 39.7 , 12.1 , 2.0 , 12.1 , 40.9 , 12.1 , 8.2 , 12.1 , 16.5 , 16 , 0.6620 , 53.0 , 6985 ,
Date , GPU Clock [MHz] , Memory Clock [MHz] , GPU Temperature [°C] , Hot Spot [°C] , Memory Temperature [°C] , Fan 1 Speed (%) [%] , Fan 1 Speed (RPM) [RPM] , Fan 2 Speed (%) [%] , Fan 2 Speed (RPM) [RPM] , Memory Used [MB] , GPU Load [%] , Memory Controller Load [%] , Video Engine Load [%] , Bus Interface Load [%] , Board Power Draw [W] , GPU Chip Power Draw [W] , PWR_SRC Power Draw [W] , PWR_SRC Voltage [V] , PCIe Slot Power [W] , PCIe Slot Voltage [V] , 8-Pin #1 Power [W] , 8-Pin #1 Voltage [V] , 8-Pin #2 Power [W] , 8-Pin #2 Voltage [V] , Power Consumption (%) [% TDP] , PerfCap Reason [] , GPU Voltage [V] , CPU Temperature [°C] , System Memory Used [MB] ,
- I’ve uninstalled anything I wasn’t actively using, and tried to keep background processes to a minimum
Questions that I have that might be helpful:
- I have an old hard drive attached to this machine. I don’t use it for anything but randomly pulling stuff off of it, but could it be causing issues?
- Is it possibly a power issue? Like, my CPU is not getting enough power sometimes? I have no idea how I would even check that.
- What further tests can I do to narrow this down?
So uh
yeah i need help!!! I’ve been half-assedly troubleshooting this for like 9 months now and I’m just sick of it. Any direction y’all can point me in is gonna be extremely helpful!
EDIT: probably unrelated but my clock keeps getting out of sync. it seems like it won’t actually contact the server automatically, even though i changed the server. and when i tested the Sync Now button just now it actually worked!! so what the fuck!! anyway like i said i don’t think it’s related but sometimes this shit is related because computers are the worst.
3 Likes
what GPU do you have and why is it an AMD (sounds like sketchy chipset drivers)
1 Like
oh good call here’s a whole dxdiag dump
Summary
------------------
System Information
------------------
Time of this report: 11/9/2023, 12:03:36
Machine name: DESKTOP-FDCN9HE
Machine Id: {7D7824C1-93B8-4B69-A21D-8BE7F761DAC0}
Operating System: Windows 10 Home 64-bit (10.0, Build 19045) (19041.vb_release.191206-1406)
Language: English (Regional Setting: English)
System Manufacturer: ASUS
System Model: System Product Name
BIOS: 1203 (type: UEFI)
Processor: 12th Gen Intel(R) Core(TM) i7-12700K (20 CPUs), ~3.6GHz
Memory: 16384MB RAM
Available OS Memory: 16126MB RAM
Page File: 7223MB used, 24773MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 12
DX Setup Parameters: Not found
User DPI Setting: 144 DPI (150 percent)
System DPI Setting: 144 DPI (150 percent)
DWM DPI Scaling: UnKnown
Miracast: Available, no HDCP
Microsoft Graphics Hybrid: Not Supported
DirectX Database Version: 1.0.8
DxDiag Version: 10.00.19041.3570 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.
Sound Tab 4: No problems found.
Sound Tab 5: 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 Ti
Manufacturer: NVIDIA
Chip type: NVIDIA GeForce RTX 3070 Ti
DAC type: Integrated RAMDAC
Device Type: Full Device (POST)
Device Key: Enum\PCI\VEN_10DE&DEV_2482&SUBSYS_50521462&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: 16093 MB
Dedicated Memory: 8031 MB
Shared Memory: 8062 MB
Current Mode: 3840 x 2160 (32 bit) (60Hz)
HDR Support: Supported
Display Topology: Internal
Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709
Color Primaries: Red(0.679688,0.315430), Green(0.280273,0.673828), Blue(0.152344,0.049805), White Point(0.312500,0.329102)
Display Luminance: Min Luminance = 0.010000, Max Luminance = 1499.000000, MaxFullFrameLuminance = 799.000000
Monitor Name: Generic PnP Monitor
Monitor Model: LG HDR 4K
Monitor Id: GSM7707
Native Mode: 3840 x 2160(p) (59.997Hz)
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_675be35f1ba2315e\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_675be35f1ba2315e\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_675be35f1ba2315e\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_675be35f1ba2315e\nvldumdx.dll
Driver File Version: 31.00.0015.3623 (English)
Driver Version: 31.0.15.3623
DDI Version: 12
Feature Levels: 12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1
Driver Model: WDDM 2.7
Hardware Scheduling: Supported:True Enabled:False
Graphics Preemption: Pixel
Compute Preemption: Dispatch
Miracast: Not Supported
Detachable GPU: No
Hybrid Graphics GPU: Not Supported
Power P-states: Not Supported
Virtualization: Paravirtualization
Block List: No Blocks
Catalog Attributes: Universal:False Declarative:True
Driver Attributes: Final Retail
Driver Date/Size: 6/7/2023 6:00:00 PM, 773720 bytes
WHQL Logo'd: Yes
WHQL Date Stamp: Unknown
Device Identifier: {D7B71E3E-67C2-11CF-F579-5D700EC2D235}
Vendor ID: 0x10DE
Device ID: 0x2482
SubSys ID: 0x50521462
Revision ID: 0x00A1
Driver Strong Name: oem24.inf:0f066de31a145f91:Section070:31.0.15.3623:pci\ven_10de&dev_2482
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,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: Digital Audio (S/PDIF) (High Definition Audio Device)
Default Sound Playback: No
Default Voice Playback: No
Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0897&SUBSYS_10438814&REV_1004
Manufacturer ID: N/A
Product ID: N/A
Type: N/A
Driver Name: HdAudio.sys
Driver Version: 10.0.19041.3570 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 9/28/2023 6:00:00 PM, 430080 bytes
Other Files:
Driver Provider: Microsoft
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: Headphones (3- Arctis Nova Pro Wireless)
Default Sound Playback: Yes
Default Voice Playback: No
Hardware ID: USB\VID_1038&PID_12E0&REV_0113&MI_00
Manufacturer ID: N/A
Product ID: N/A
Type: N/A
Driver Name: USBAUDIO.sys
Driver Version: 10.0.19041.3570 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 9/28/2023 6:00:00 PM, 205824 bytes
Other Files:
Driver Provider: Microsoft
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: LG HDR 4K (NVIDIA High Definition Audio)
Default Sound Playback: No
Default Voice Playback: Yes
Hardware ID: HDAUDIO\FUNC_01&VEN_10DE&DEV_009E&SUBSYS_14625052&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: 1/18/2023 6:00:00 PM, 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: Speakers (Steam Streaming Microphone)
Default Sound Playback: No
Default Voice Playback: No
Hardware ID: ROOT\SteamStreamingMicrophone
Manufacturer ID: N/A
Product ID: N/A
Type: N/A
Driver Name: SteamStreamingMicrophone.sys
Driver Version: 8.33.15.17 ()
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 7/27/2017 6:00:00 PM, 40736 bytes
Other Files:
Driver Provider: Valve 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: Speakers (Steam Streaming Speakers)
Default Sound Playback: No
Default Voice Playback: No
Hardware ID: ROOT\SteamStreamingSpeakers
Manufacturer ID: N/A
Product ID: N/A
Type: N/A
Driver Name: SteamStreamingSpeakers.sys
Driver Version: 17.56.13.764 ()
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 7/19/2017 6:00:00 PM, 40736 bytes
Other Files:
Driver Provider: Valve 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
---------------------
Sound Capture Devices
---------------------
Description: Microphone (3- Arctis Nova Pro Wireless)
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: USBAUDIO.sys
Driver Version: 10.0.19041.3570 (English)
Driver Attributes: Final Retail
Date and Size: 9/28/2023 6:00:00 PM, 205824 bytes
Cap Flags: 0x1
Format Flags: 0xFFFFF
Description: Microphone (Steam Streaming Microphone)
Default Sound Capture: No
Default Voice Capture: No
Driver Name: SteamStreamingMicrophone.sys
Driver Version: 8.33.15.17 ()
Driver Attributes: Final Retail
Date and Size: 7/27/2017 6:00:00 PM, 40736 bytes
Cap Flags: 0x1
Format Flags: 0xFFFFF
Description: Microphone (USB Live Camera audio)
Default Sound Capture: No
Default Voice Capture: No
Driver Name: USBAUDIO.sys
Driver Version: 10.0.19041.3570 (English)
Driver Attributes: Final Retail
Date and Size: 9/28/2023 6:00:00 PM, 205824 bytes
Cap Flags: 0x1
Format Flags: 0xFFFFF
Description: Microphone (Virtual Desktop Audio)
Default Sound Capture: No
Default Voice Capture: No
Driver Name: vdvad.sys
Driver Version: 1.6.1.0 (English)
Driver Attributes: Final Retail
Date and Size: 1/27/2022 6:00:00 PM, 44936 bytes
Cap Flags: 0x1
Format Flags: 0xFFFFF
---------------------
Video Capture Devices
Number of Devices: 1
---------------------
FriendlyName: USB Live camera
Category: Camera
SymbolicLink: \\?\usb#vid_0c45&pid_636b&mi_00#7&315a9f63&0&0000#{e5323777-f976-4f5b-9b55-b94699c46e44}\global
Location: n/a
Rotation: n/a
Manufacturer: Microsoft
HardwareID: USB\VID_0C45&PID_636B&REV_0100&MI_00,USB\VID_0C45&PID_636B&MI_00
DriverDesc: USB Video Device
DriverProvider: Microsoft
DriverVersion: 10.0.19041.3570
DriverDateEnglish: 6/21/2006 00:00:00
DriverDateLocalized: 6/21/2006 12:00:00 AM
Service: usbvideo
Class: Camera
DevNodeStatus: 180200A[DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]
ContainerId: {6390D0D1-881C-5BB2-9E49-DE293F40E0B5}
ProblemCode: No Problem
BusReportedDeviceDesc: USB Live camera
Parent: USB\VID_0C45&PID_636B\SN0001
DriverProblemDesc: n/a
UpperFilters: n/a
LowerFilters: WdmCompanionFilter
Stack: \Driver\ksthunk,\Driver\usbvideo,\Driver\usbccgp
ContainerCategory: n/a
SensorGroupID: n/a
MFT0: n/a
DMFT: n/a
CustomCaptureSource: n/a
DependentStillCapture: n/a
EnablePlatformDMFT: n/a
DMFTChain: n/a
EnableDshowRedirection: n/a
FrameServerEnabled: n/a
AnalogProviders: n/a
ProfileIDs: n/a
-------------------
DirectInput Devices
-------------------
Device Name: Mouse
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a
Device Name: Keyboard
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a
Device Name: ITE BillBoard
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x048D, 0x5212
FF Driver: n/a
Device Name: MIDI Mix
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x09E8, 0x0031
FF Driver: n/a
Device Name: AURA LED Controller
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x0B05, 0x19AF
FF Driver: n/a
Device Name: Ultimate Wireless Controller
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x2DC8, 0x3109
FF Driver: n/a
Device Name: Arctis Nova Pro Wireless
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x1038, 0x12E0
FF Driver: n/a
Device Name: Arctis Nova Pro Wireless
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x1038, 0x12E0
FF Driver: n/a
Device Name: NZXT USB Device
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x1E71, 0x200F
FF Driver: n/a
Device Name: Stream Deck MK.2
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x0FD9, 0x0080
FF Driver: n/a
Device Name: Keychron K10 Pro
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x3434, 0x02A0
FF Driver: n/a
Device Name: Keychron K10 Pro
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x3434, 0x02A0
FF Driver: n/a
Device Name: Keychron K10 Pro
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x3434, 0x02A0
FF Driver: n/a
Device Name: Keychron Link
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x3434, 0xD030
FF Driver: n/a
Device Name: Arctis Nova Pro Wireless
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x1038, 0x12E0
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, 10/11/2023 16:32:59, 648680 bytes
|
+-+ Generic USB Hub
| | Vendor/Product ID: 0x2109, 0x2817
| | Location: Port_#0004.Hub_#0001
| | Matching Device ID: USB\USB20_HUB
| | Service: USBHUB3
| | Driver: USBHUB3.SYS, 10/11/2023 16:32:59, 648680 bytes
| |
| +-+ Generic USB Hub
| | | Vendor/Product ID: 0x14CD, 0x8601
| | | Location: Port_#0002.Hub_#0003
| | | Matching Device ID: USB\USB20_HUB
| | | Service: USBHUB3
| | | Driver: USBHUB3.SYS, 10/11/2023 16:32:59, 648680 bytes
| | |
| | +-+ USB Composite Device
| | | | Vendor/Product ID: 0x3434, 0xD030
| | | | Location: Port_#0003.Hub_#0006
| | | | Matching Device ID: USB\COMPOSITE
| | | | Service: usbccgp
| | | | Driver: usbccgp.sys, 10/11/2023 16:32:59, 190320 bytes
| | | |
| | | +-+ USB Input Device
| | | | | Vendor/Product ID: 0x3434, 0xD030
| | | | | Location: 0000.0014.0000.004.002.003.000.000.000
| | | | | Matching Device ID: USB\Class_03&SubClass_01
| | | | | Service: HidUsb
| | | | | Driver: hidusb.sys, 10/11/2023 16:32:59, 44032 bytes
| | | | | Driver: hidclass.sys, 10/11/2023 16:32:59, 233472 bytes
| | | | | Driver: hidparse.sys, 10/11/2023 16:32:59, 46080 bytes
| | | | |
| | | | +-+ HID-compliant mouse
| | | | | | Vendor/Product ID: 0x3434, 0xD030
| | | | | | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE
| | | | | | Service: mouhid
| | | | | | Driver: mouhid.sys, 12/7/2019 03:07:56, 35328 bytes
| | | | | | Driver: mouclass.sys, 12/7/2019 03:07:56, 67600 bytes
| | | | |
| | | +-+ USB Input Device
| | | | | Vendor/Product ID: 0x3434, 0xD030
| | | | | Location: 0000.0014.0000.004.002.003.000.000.000
| | | | | Matching Device ID: USB\Class_03&SubClass_01
| | | | | Service: HidUsb
| | | | | Driver: hidusb.sys, 10/11/2023 16:32:59, 44032 bytes
| | | | | Driver: hidclass.sys, 10/11/2023 16:32:59, 233472 bytes
| | | | | Driver: hidparse.sys, 10/11/2023 16:32:59, 46080 bytes
| | | | |
| | | | +-+ HID Keyboard Device
| | | | | | Vendor/Product ID: 0x3434, 0xD030
| | | | | | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD
| | | | | | Service: kbdhid
| | | | | | Driver: kbdhid.sys, 12/7/2019 03:07:56, 46592 bytes
| | | | | | Driver: kbdclass.sys, 12/7/2019 03:07:56, 71480 bytes
| | | | | |
| | | | +-+ HID Keyboard Device
| | | | | | Vendor/Product ID: 0x3434, 0xD030
| | | | | | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD
| | | | | | Service: kbdhid
| | | | | | Driver: kbdhid.sys, 12/7/2019 03:07:56, 46592 bytes
| | | | | | Driver: kbdclass.sys, 12/7/2019 03:07:56, 71480 bytes
| |
+-+ Generic USB Hub
| | Vendor/Product ID: 0x1A40, 0x0101
| | Location: Port_#0003.Hub_#0001
| | Matching Device ID: USB\USB20_HUB
| | Service: USBHUB3
| | Driver: USBHUB3.SYS, 10/11/2023 16:32:59, 648680 bytes
| |
| +-+ USB Composite Device
| | | Vendor/Product ID: 0x3434, 0x02A0
| | | Location: Port_#0001.Hub_#0005
| | | Matching Device ID: USB\COMPOSITE
| | | Service: usbccgp
| | | Driver: usbccgp.sys, 10/11/2023 16:32:59, 190320 bytes
| | |
| | +-+ USB Input Device
| | | | Vendor/Product ID: 0x3434, 0x02A0
| | | | Location: 0000.0014.0000.003.001.000.000.000.000
| | | | Matching Device ID: USB\Class_03&SubClass_01
| | | | Service: HidUsb
| | | | Driver: hidusb.sys, 10/11/2023 16:32:59, 44032 bytes
| | | | Driver: hidclass.sys, 10/11/2023 16:32:59, 233472 bytes
| | | | Driver: hidparse.sys, 10/11/2023 16:32:59, 46080 bytes
| | | |
| | | +-+ HID Keyboard Device
| | | | | Vendor/Product ID: 0x3434, 0x02A0
| | | | | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD
| | | | | Service: kbdhid
| | | | | Driver: kbdhid.sys, 12/7/2019 03:07:56, 46592 bytes
| | | | | Driver: kbdclass.sys, 12/7/2019 03:07:56, 71480 bytes
| | | |
| | +-+ USB Input Device
| | | | Vendor/Product ID: 0x3434, 0x02A0
| | | | Location: 0000.0014.0000.003.001.000.000.000.000
| | | | Matching Device ID: USB\Class_03
| | | | Service: HidUsb
| | | | Driver: hidusb.sys, 10/11/2023 16:32:59, 44032 bytes
| | | | Driver: hidclass.sys, 10/11/2023 16:32:59, 233472 bytes
| | | | Driver: hidparse.sys, 10/11/2023 16:32:59, 46080 bytes
| | | |
| | | +-+ HID-compliant mouse
| | | | | Vendor/Product ID: 0x3434, 0x02A0
| | | | | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE
| | | | | Service: mouhid
| | | | | Driver: mouhid.sys, 12/7/2019 03:07:56, 35328 bytes
| | | | | Driver: mouclass.sys, 12/7/2019 03:07:56, 67600 bytes
| | | | |
| | | +-+ HID Keyboard Device
| | | | | Vendor/Product ID: 0x3434, 0x02A0
| | | | | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD
| | | | | Service: kbdhid
| | | | | Driver: kbdhid.sys, 12/7/2019 03:07:56, 46592 bytes
| | | | | Driver: kbdclass.sys, 12/7/2019 03:07:56, 71480 bytes
----------------
Gameport Devices
----------------
------------
PS/2 Devices
------------
------------------------
Disk & DVD/CD-ROM Drives
------------------------
Drive: C:
Free Space: 747.1 GB
Total Space: 1907.1 GB
File System: NTFS
Model: Samsung SSD 970 EVO Plus 2TB
Drive: D:
Free Space: 7662.5 GB
Total Space: 9537.5 GB
File System: NTFS
Model: WDC WD101EFBX-68B0AN0
Drive: E:
Free Space: 706.8 GB
Total Space: 2800.5 GB
File System: NTFS
Model: TOSHIBA DT01ACA300
Drive: F:
Free Space: 1.7 GB
Total Space: 60.0 GB
File System: NTFS
Model: TOSHIBA DT01ACA300
--------------
System Devices
--------------
Name: Standard NVM Express Controller
Device ID: PCI\VEN_144D&DEV_A808&SUBSYS_A801144D&REV_00\4&3A1B80A7&0&0030
Driver: C:\Windows\system32\DRIVERS\stornvme.sys, 10.00.19041.3570 (English), 10/11/2023 16:32:59, 165232 bytes
Name: PCI Express Root Port
Device ID: PCI\VEN_8086&DEV_7AC0&SUBSYS_86941043&REV_11\3&11583659&0&D8
Driver: C:\Windows\system32\DRIVERS\pci.sys, 10.00.19041.3570 (English), 10/11/2023 16:32:59, 478696 bytes
Name: PCI standard ISA bridge
Device ID: PCI\VEN_8086&DEV_7A84&SUBSYS_86941043&REV_11\3&11583659&0&F8
Driver: C:\Windows\system32\DRIVERS\msisadrv.sys, 10.00.19041.3570 (English), 10/11/2023 16:32:59, 21480 bytes
Name: PCI Device
Device ID: PCI\VEN_8086&DEV_7ACC&SUBSYS_86941043&REV_11\3&11583659&0&A8
Driver: n/a
Name: Intel(R) Management Engine Interface #1
Device ID: PCI\VEN_8086&DEV_7AE8&SUBSYS_86941043&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 06:30:18, 309384 bytes
Name: Intel(R) USB 3.20 eXtensible Host Controller - 1.20 (Microsoft)
Device ID: PCI\VEN_8086&DEV_7AE0&SUBSYS_86941043&REV_11\3&11583659&0&A0
Driver: C:\Windows\system32\DRIVERS\USBXHCI.SYS, 10.00.19041.3570 (English), 10/11/2023 16:32:59, 625640 bytes
Driver: C:\Windows\system32\DRIVERS\UMDF\UsbXhciCompanion.dll, 10.00.19041.3570 (English), 10/11/2023 16:32:59, 143144 bytes
Name: PCI Express Root Port
Device ID: PCI\VEN_8086&DEV_464D&SUBSYS_86941043&REV_02\3&11583659&0&30
Driver: C:\Windows\system32\DRIVERS\pci.sys, 10.00.19041.3570 (English), 10/11/2023 16:32:59, 478696 bytes
Name: Performance Monitor
Device ID: PCI\VEN_8086&DEV_467D&SUBSYS_86941043&REV_01\3&11583659&0&50
Driver: n/a
Name: PCI Device
Device ID: PCI\VEN_8086&DEV_7AA4&SUBSYS_86941043&REV_11\3&11583659&0&FD
Driver: n/a
Name: RAID Controller
Device ID: PCI\VEN_8086&DEV_467F&SUBSYS_86941043&REV_00\3&11583659&0&70
Driver: n/a
Name: PCI Express Root Port
Device ID: PCI\VEN_8086&DEV_7AB8&SUBSYS_86941043&REV_11\3&11583659&0&E0
Driver: C:\Windows\system32\DRIVERS\pci.sys, 10.00.19041.3570 (English), 10/11/2023 16:32:59, 478696 bytes
Name: PCI Device
Device ID: PCI\VEN_8086&DEV_7ACD&SUBSYS_86941043&REV_11\3&11583659&0&A9
Driver: n/a
Name: PCI Express Root Port
Device ID: PCI\VEN_8086&DEV_7AB0&SUBSYS_86941043&REV_11\3&11583659&0&E8
Driver: C:\Windows\system32\DRIVERS\pci.sys, 10.00.19041.3570 (English), 10/11/2023 16:32:59, 478696 bytes
Name: PCI standard RAM Controller
Device ID: PCI\VEN_8086&DEV_7AA7&SUBSYS_86941043&REV_11\3&11583659&0&A2
Driver: n/a
Name: Realtek PCIe 2.5GbE Family Controller
Device ID: PCI\VEN_10EC&DEV_8125&SUBSYS_87D71043&REV_05\01000000684CE00000
Driver: C:\Windows\system32\DRIVERS\rt640x64.sys, 9.01.0410.2015 (English), 12/7/2019 03:07:54, 694272 bytes
Name: NVIDIA GeForce RTX 3070 Ti
Device ID: PCI\VEN_10DE&DEV_2482&SUBSYS_50521462&REV_A1\4&22F77229&0&0008
Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_675be35f1ba2315e\NVWMI\nvPerfProvider.man, 6/8/2023 22:38:35, 14175 bytes
[trimmed for length]
the card i have is an NVIDIA GeForce RTX 3070 Ti and i keep the drivers pretty much up to date
1 Like
this is always a hardware / driver problem and usually it is with hardware / drivers that are either failing or no longer supported and it can be really annoying to isolate and often it’s a problem with a part of a Windows machine that may not be replaceable.
some food for thought:
- is it possible it’s your network card?
- can you find a different driver for that hardware than windows update wants to give you?
2 Likes
explanation in the event I turn out to be right:
the only devices that can cause a timeout crash like that are the ones that need very low latency interrupts, and on a modern machine that has basically no PCI slots, that pretty much just means southbridge and m2-attached devices like a network card. if your machine ever has unusual stutters at any other time despite the CPU and GPU appearing otherwise totally capable of full performance, it’s almost certainly this.
if it happens in a way that feels vaguely related to Bluetooth audio, that’s also handled by the network hardware rather than (at all) by the onboard sound hardware, so that supports this hypothesis
3 Likes
the good news if it turns out to be the network card is that most onboard network hardware on modern motherboards is socketed m.2 cards and is easily replaceable even though very few people replace it
2 Likes
nearly this exact thing happened to me and I fixed it. it was the sound card. For whatever reason my PC came with an audigy soundblaster and uninstalling it fixed these intermittant and random crashes. I found it by reading crash logs but also combing through Event Viewer to try to find the culprit. If you BSOD wait for it to complete and read the crash logs using Bluescreen view
Here’s some additional info I read up when trying to dx the issue.
6 Likes
thanks y’all, i’ll do some more testing with drivers and see if i can narrow it down. my gut says it’s the drivers for my wireless headphones but we’ll see
1 Like
I had very similar latency crackling and crashes because I tried to use my 10 year old DVD drive on windows 10. Took a few days of research before I realized the problem. Drivers never got 10 support. Instantly fixed when I removed the DVD drive.
2 Likes
I, um, I think if you follow this series of steps, the name of the offending driver is all but guaranteed to materialze. I hope. 
A lot of Windows troubleshooting stuff came back to me while I was writing this…I think maybe the discussion about the Event Viewer the other day kind of stimulated my instincts in that regard or something. 
For starters, as hellojed mentioned, every time that BSoD occurs it should create entries in the Event Viewer. You can type “Event” into the start menu search bar and it should show up, or failing that Start → Programs → Administrative Tools → Event Viewer. Once it’s open, you would look for the errors in, on the left, Windows Logs → System. Most of what will appear here is low-priority messages of no interest…in order to hone in on the messages the blue screen may have left behind, we can open “Filter Current View” on the right and check “Critical” and “Error”. You could try entering 0x133 or DPC_WATCHDOG_VIOLATION in the “Keywords” field as well maybe.
If anything turns up this way, there’s a “Copy” button on the right that you could use to paste the error message(s) into this thread. One or more of them might well name the malfunctioning driver.
That may solve the mystery right out. However, sometimes the Event Viewer fails to deliver. In that case, there is a more aggressive troubleshooting strategy you could employ.
I’m basing this on this passage from Windows Internals, Part 2, 7th ed., pg. 136:
Windows doesn’t just expect users to manually look into latency issues caused by DPCs; it also includes built-in mechanisms to address a few common scenarios that can cause significant problems. The first is the DPC Watchdog and DPC Timeout mechanism, which can be configured through certain registry values in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Kernelsuch asDPCTimeout,DpcWatchdogPeriod, andDpcWatchdogProfileOffset.The DPC Watchdog is responsible for monitoring all execution of code at
DISPATCH_LEVELor above, where a drop in IRQL has not been registered for quite some time. The DPC Timeout, on the other hand, monitors the execution time of a specific DPC. By default, a specific DPC times out after 20 seconds, and allDISPATCH_LEVEL(and above) execution times out after 2 minutes. Both limits are configurable with the registry values mentioned earlier (DPCTimeoutcontrols a specific DPC time limit, whereas theDpcWatchdogPeriodcontrols the combined execution of all the code running at high IRQL). When these thresholds are hit, the system will either bugcheck withDPC_WATCHDOG_VIOLATION(indicating which of the situations was encountered), or, if a kernel debugger is attached, raise an assertion that can be continued.
Based on this, you could try lowering the DpcWatchdogPeriod setting in the registry. This will increase the chances of getting a DPC_WATCHDOG_VIOLATION BSoD. Before doing this, I would recommend enabling crash dumps if you haven’t already—if you’ve done this the blue screen should create a minidump file in the “Small dump directory” in Startup and Recovery as described on that page (if memory serves 
let me know if you try that and you’re still not getting a crash dump post-blue-screen). The crash dump might contain a stack trace naming the malfunctioning driver. If we get this far, you could follow the instructions on this page to get a text description of the crash dump’s contents, which I think you could safely copy and paste in this thread (I don’t think it contains anything sensitive but it wouldn’t hurt to double-check first).
Anyway: DpcWatchdogPeriod.
The reason why that blue screen happens is basically because, like, many devices communicate with the operating system using what are called “interrupts” (I’m kind of assuming nothing, you may already know this, apologies if so). One example of an interrupt is the kind generated when you press your computer’s power button, or close the lid of your laptop if you have a laptop; these kinds of actions cause special electrical signals from the motherboard to be sent to your CPU (oversimplifying a bit). Another kind happens in software; a driver may be able to generate an interrupt using an interface the OS provides.
On the other side, device drivers can register pieces of code they want the OS to run whenever it sees interrupts of one kind or another. In Windows, these pieces of code are called “Interrupt Service Routines” or ISRs (in the *nix world they are called “Interrupt Handlers” ). When an interrupt comes in, Windows looks through its ISRs and runs any of them which have been registered for that specific kind of interrupt. Many varieties of hardware do their moment-to-moment work this way—networking, audio, video, and input devices are all examples of things like that, but any device driver might register one or more ISRs for one reason or another.
ISRs run at a very high priority level, meaning that until they finish, Windows does not allow most other code to run, at least on the CPU core that’s executing the ISR. ISRs are suppose to do the bare minimum of work they need to as quickly as possible and then hand off execution to other code which can run at a lower priority level. Basically, they should just quickly get whatever info the driver needs to handle the interrupt and put it somewhere for other lower-priority code, and maybe send some sort of minimal response to something communicating that the interrupt was received—that sort of thing. If the ISR tries to do too much work in some sense and ends up running for a long time, it will starve out almost any other code that needs to run on that CPU core for an extended period, which, as you can imagine, can cause problems.
One mechanism that Windows provides for ISRs to avoid doing too much work is called “Deferred Procedure Calls” or DPCs. These are other pieces of code that the ISR can tell Windows to run soon after it finishes. They run at a lower priority than an ISR, but still a very high priority, so they’re designed for stuff that needs to happen very soon after the interrupt came in but can afford to wait just a bit (in case there are other ISRs that need to run first).
One way a DPC_WATCHDOG_VIOLATION blue screen can arise is if Windows spends too long at a priority level high enough for an ISR or DPC. DpcWatchdogPeriod specifies exactly how long “too long” is. By default, it’s 2 minutes, and it sounds like that’s too great a period for the specific situation you’re facing; it sounds like the misbehaving driver manages to totally take over the CPU and hardlock your computer much sooner than that most of the time. I think it might work well to lower DpcWatchdogPeriod by half, wait a while to see if you get a blue screen, then lower it by half again, etc., until the blue screen happens.
Just to quickly note again, this setting is in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Kernel. The setting is in milliseconds in hexadecimal; here’s a table:
| Seconds | Hex (ms) |
|---|---|
| 120 | 0x0001d4c0 |
| 60 | 0x0000ea60 |
| 30 | 0x00007530 |
| 15 | 0x00003a98 |
| 7.5 | 0x00001d4c |
| 3.75 | 0x00000ea6 |
| 1.875 | 0x00000753 |
| 0.9375 | 0x000003aa |
| 0.46875 | 0x000001d5 |
| 0.234375 | 0x000000ea |
That’s about as low as you should possibly need to go I would think. I would lower it fairly gradually just because it’s entirely possible you have other drivers that are functioning normally and yet spend far longer than they should in one or more of their ISRs or DPCs, in which case they would generate false positives. Still, this sounds like a dramatic-enough problem that I would guess you would get a relevant blue screen well before that becomes an issue.
I would not at all be surprised if those 1–2 s. hiccups are caused by the exact same problem that’s causing the hardlocks—the 1–2 s. hiccups could just be the less-severe form of the same issue, where it’s seizing up the CPU for short bursts (causing your other devices which need to respond to interrupts to be left out in the cold briefly, like the trouble you’re seeing with your audio and input devices). The exact way it’s seizing up the CPU is kind of hard to say at this distance—it’s possible, I think, that the same buggy interrupt routine is getting run over and over in a short time, so that eventually it is running on all cores and not returning on any of them fast enough, or there’s an ISR or DPC with buggy multithreaded code that is doing the same thing on its own power (either way you can get hardlock, if it never comes back, or brief stuttering, if this problem is happening in short bursts).
Anyway, all that is to say, when you’re getting those hiccups, that might be a good time to play around with DpcWatchdogPeriod. If this hypothesis is correct you may be able to trigger the blue screen easily while that is going on. You might have to restart your computer after changing DpcWatchdogPeriod for it take effect—I’m not sure, maybe not. Of course, once you’re done, I think it’s probably a good idea to put it back to the default of 0x0001d4c0, unless you really like having it lower for some reason.
As one last note…if the crash dump from this still doesn’t reveal which driver is malfunctioning, and you have another Windows machine available, you might be able to start a kernel-mode debugging session when the blue screen would otherwise happen, which will let you look around on the malfunctioning system at the moment of the crash. Then I think we almost certainly could identify the driver. I’ve never tried doing this before but it sounds interesting. I can only guess that the problem would be solved well before this point though.
9 Likes
this is extremely helpful based on skimming it, i am bookmarking it and when i get the energy to do a really deep dive i’ll do it. thank you so much!!!
2 Likes
Sure thing, I’m glad if it helps 
Feel free to ask if you have any questions.
2 Likes
This tool will spit out a report of what dpc calls are taking a long time and what driver created them
6 Likes
I have a copy of windows in an old PC that I want to transfer to almost an entirely new build… how do I do that?
Edit: Can I just take the harddrive and move it over?
1 Like