[SOLVED] [10v1909] DPC/ISR high latency unknown cause. FIX: I updated the BIOS to new version 7B86vH6

IncrociatoreX

IncrociatoreX

Member
Joined
Mar 28, 2020
Posts
24
Hi all, i'm trying to fix this problem from ages.

I have updated all drivers/bios, tried all possible fixes on internet (Hpet, MSI mode, tricks on audio devices ecc ecc).

I'm on a fresh win1909 installation from media creation tool. Bios default settings (xmp enabled and tried without).

I can reproduce pops the moment when i run a program (whatsapp, steam and others), but they can appear randomly when i listen music or other simple things.
Many games are fluent but some stutter every 1-2 min for less than a second. It's a "total" stutter, not only audio.

From my experience i can say that there are some "good" boot-ups with no issues at start, but they can appear after some hours. No fast start or hybernation by the way.

LatencyMon is not very helpful, some random wdf, ntoskrnl e dxgkrnl latency. If I disable the video card driver, latency reduce by a lot (tried both gtx1060 and 5600XT same result).
So the main culprit appears to be dxgkrnl but i can't isolate the problem, tried to disable every single driver from devices manager.
Stressed out ram and cpu with all classic tests, no problems.

Last thing, i've done a trace during a couple of pops when i run whatsapp (two times) GD link --> DESKTOP-PTCT7LR.03-22-2020.22-05-51.etl

Thank you in advance, sorry for my english
____________________________________________________________________________________________________________________________
Operating System
Windows 10 Pro 64-bit
CPU
AMD Ryzen 5 3600X
RAM
16,0GB (CORSAIR Memoria Dimm Vengeance LPX 16GB (2 x 8GB) DDR4 3200 MHz CL16)
Motherboard
Micro-Star International Co. Ltd B450 GAMING PLUS MAX (MS-7B86) (AM4) 27 °C
Graphics
MX259 (1920x1080@60Hz)
6128MB ATI AMD Radeon RX 5600 XT (Unknown)
Storage
3726GB Seagate ST4000DM004-2CV104 (SATA ) 24 °C
465GB Crucial CT500MX500SSD1 (SATA (SSD))
465GB Seagate ST3500418AS (SATA ) 26 °C
232GB Western Digital WDS250G3X0C-00SJG0 (Unknown (SSD))
Optical Drives
No optical disk drives detected
Audio
Realtek High Definition Audio
PSU
CORSAIR Alimentatore 650 Watt Serie TX-M Semi-Modulare Certificazione 80 Plus Gold
 

Attachments

  • drivers.PNG
    drivers.PNG
    45 KB · Views: 8
  • cpus.PNG
    cpus.PNG
    24 KB · Views: 6
Hi, @IncrociatoreX , Welcome to Sysnative!

Please give them 48-72 hours to respond as they may be busy with other threads or simply taking care of Family during these trying times.

I would help but this is not my area of expertise.

We thank you for your patience.
 
On your motherboard webpage:
Realtek HD Universal Driver - 6.0.8911.1 - 2020-04-10 (10 Apr 2020) - 40.62 MB
Note: Must update Nahimic 3 in Microsoft store after updating Realtek HD Universal Driver. Recommend installing this driver for Windows 10 RS3 or later versions.
Click to expand...
 
You could try to run driver verifier; please read CAREFULLY the following instructions:
  • Create a restore point
  • Create a system image (macrium reflect free is a good program, if you don't already have one)
  • Backup your important files (the files you don't want to lose)
  • Read the guide about Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 & Vista (click).
  • Read some other tutorials/guides and WARNINGS on internet.
  • Unzip on your desktop the file I attached: verifier.zipand then:
    1. Open an elevated command prompt (right-click on windows start button, click command prompt (admin)
    2. Type (copy/paste) in it:
      Code: 
      powershell -executionpolicy unrestricted "%userprofile%\desktop\EnableVerifier.ps1
    3. Press enter
    4. The previous command will modify your bcdedit settings and it will set the necessary driver verifier settings.
      It will (more precisely):
      Read More:
    5. If you'll get a very fast BSOD after you logged into windows, or after some dozens (tenths?) of minutes, the option resetonbootfail should reset driver verifier settings (and should allow you to boot your machine in a normal state)... But if this won't happen, you'll need to go to safe mode to reset verifier settings. Once safe mode is available, from an elevated command prompt you'll type:
      Code: 
      verifier /reset
      Sometimes it is necessary to use a system restore point (or a system image).
  • Post here the new verifier dump; from an elevated command prompt, launch this command:
    Code: 
    md "%userprofile%\desktop\minidump" && copy c:\windows\minidump "%userprofile%\desktop\minidump"
 

Attachments

Last edited:
Your ram CMK16GX4M2B3200C16 doesn't seem to be (officially) compatible with your cpu and motherboard combination.
The same is valid for your graphic card AMD Radeon RX 5600 XT and your HDDs: Seagate SATA ST4000DM004-2CV104, Crucial SSD CT500MX500SSD1, Seagate SATA ST3500418AS.
Your WD SSD M.2 WDS250G3X0C HDD instead appears in the compatibility list.
BIOS seems to be the last version: 7B86vH5, 2019-11-07 (7 Nov 2019)
In the dump: BIOS Version H.50, BIOS Release Date 11/07/2019 (7 Nov 2019)
The dump blames on atikmpag.sys, but that's already the last driver version:
Read More:
CMK16GX4M2B3200C16 kit is: VENGEANCE LPX 16GB (2 x 8GB) DDR4 DRAM 3200MHz C16 Memory Kit - Black.
I checked it on your motherboard webpage "Memory by RX-3X00", i.e. for "Zen 2"-"Matisse" architecture.
If you should be able to change that kit, these are the compatible ones:
Read More:



What you can try:
- set the ram speed to its SPD value: 2133 (currently it's 3200); if this won't work, try next point.
- clean reinstall AMD drivers in safe mode; if this won't work, try next point.
- disable atikmpag.sys; if this won't work, try next point.
- try another graphics card (given that you wrote you already own another one); if this won't work, try next point.
- try to use compatible hardware only; if this won't work, try next point.
- ask AMD and MSI to provide the software and drivers for enhancing the compatibility.
 
Last edited:
Hi IncrociatoreX,

While there's a 0x116 crash, it's not caused by driver verifier. In fact, driver verifier's not configured.
Code: 
11: kd> !verifier

Verify Flags Level 0x00000000

  STANDARD FLAGS:
    [X] (0x00000000) Automatic Checks
    [ ] (0x00000001) Special pool
    [ ] (0x00000002) Force IRQL checking
    [ ] (0x00000008) Pool tracking
    [ ] (0x00000010) I/O verification
    [ ] (0x00000020) Deadlock detection
    [ ] (0x00000080) DMA checking
    [ ] (0x00000100) Security checks
    [ ] (0x00000800) Miscellaneous checks
    [ ] (0x00020000) DDI compliance checking

  ADDITIONAL FLAGS:
    [ ] (0x00000004) Randomized low resources simulation
    [ ] (0x00000200) Force pending I/O requests
    [ ] (0x00000400) IRP logging
    [ ] (0x00002000) Invariant MDL checking for stack
    [ ] (0x00004000) Invariant MDL checking for driver
    [ ] (0x00008000) Power framework delay fuzzing
    [ ] (0x00010000) Port/miniport interface checking
    [ ] (0x00040000) Systematic low resources simulation
    [ ] (0x00080000) DDI compliance checking (additional)
    [ ] (0x00200000) NDIS/WIFI verification
    [ ] (0x00800000) Kernel synchronization delay fuzzing
    [ ] (0x01000000) VM switch verification
    [ ] (0x02000000) Code integrity checks

    [X] Indicates flag is enabled


Summary of All Verifier Statistics

  RaiseIrqls           0x0
  AcquireSpinLocks     0x0
  Synch Executions     0x0
  Trims                0x0

  Pool Allocations Attempted             0x0
  Pool Allocations Succeeded             0x0
  Pool Allocations Succeeded SpecialPool 0x0
  Pool Allocations With NO TAG           0x0
  Pool Allocations Failed                0x0

  Current paged pool allocations         0x0 for 00000000 bytes
  Peak paged pool allocations            0x0 for 00000000 bytes
  Current nonpaged pool allocations      0x0 for 00000000 bytes
  Peak nonpaged pool allocations         0x0 for 00000000 bytes

Please configure driver verifier according to the tutorial.
Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 + Vista

Please also confirm driver verifier is enabled, you can do that by opening driver verifier again, select 'display existing settings' and the below screen will show. In the marked area if there's a 'yes' it means driver verifier is enabled.
1586806169547.png
 
Re-open an elevated command prompt, type verifier, press enter, and from verifier GUI:

1. Click the second radio button: Create custom settings (for code developers); click the next button
2. Under Select individual settings from a full list, check (tick) almost all the standard settings, except "DMA checking" and "I/O verification", and "Power framework delay fuzzing" as additional setting; click the next button
Read More:
3. Select the fourth radio button Select driver names from a list; click the next button
4. Click on the Provider column (that sorts the list), check (tick) ALL boxes where "Microsoft" IS NOT the Provider
5. Click on Finish and reboot the machine


This time, if a BSOD will appear, you will have to enter safe mode and type verifier /reset (from an elevated command prompt) to reset verifier settings.
 
Last edited:
xilolee said:
It seems you had one last week: Mon 6 Apr 2020 12:40:40.842; the one I checked in post #10.
I thought it was the one got with verifier...
Click to expand...
It was a failed driver installation for gpu, but it was an isolated issue. Sorry, i did not checked the dump, i'm not an expert.
thank you for the very specific help.
 
Try to update the logitech gaming software to 9.02.65 for windows x64 (2018-10-08).
Currently it seems you are using 9.00.42 (2018-05-10).

If that won't work, try to uninstall it completely.
 
xilolee said:
Try to update the logitech gaming software to 9.02.65 for windows x64 (2018-10-08).
Currently it seems you are using 9.00.42 (2018-05-10).

If that won't work, try to uninstall it completely.
Click to expand...
Tried already with and without that software no luck.


IncrociatoreX said:
From my experience i can say that there are some "good" boot-ups with no issues at start, but they can appear after some hours. No fast start or hybernation by the way.
Click to expand...
It could be a usefull info? Something could "trigger" the issue and then it will not disappear anymore. Then if I perform a reboot, it's very common that i "fix" the problem for some time.
 
Try to run verifier again, without Logitech software this time.

I've fixed the script:
  • Unzip on your desktop the file I attached, verifier.zip, and then:
    1. Open an elevated command prompt (right-click on windows start button, click command prompt (admin)
    2. Type (copy/paste) in it:
      Code: 
      powershell -executionpolicy unrestricted "%userprofile%\desktop\EnableVerifier.ps1
    3. Press enter
      It will reboot your machine in one second, modify your bcdedit settings and set the necessary driver verifier settings.
    4. If you'll get a very fast BSOD after you logged into windows, or after some dozens (tenths?) of minutes, the option resetonbootfail should reset driver verifier settings (and should allow you to boot your machine in a normal state)... But if this won't happen, you'll need to go to safe mode to reset verifier settings. Once safe mode is available, from an elevated command prompt you'll type:
      Code: 
      verifier /reset
      Sometimes it is necessary to use a system restore point (or a system image).
  • Post here the new verifier dump; from an elevated command prompt, launch this command:
    Code: 
    md "%userprofile%\desktop\minidump" && copy c:\windows\minidump "%userprofile%\desktop\minidump"
    And you'll find the minidump file in the minidump folder on your desktop.
 

Attachments

Last edited:
xilolee said:
Try to run verifier again, without Logitech software this time.
Click to expand...
checked again all the settings in post #12, enabled verifier and bsod caused by webcam driver (lvuvc64.sys)
It's an hardware that i use last days for quarantine, it's not the culprit.
Rebooted without webcam, enabled again driver verified, rebooted, no bsod at start but after few minutes i got them x2 times. all 3 dumps attached.

I have red post #10, tried all your points. I have not another set of Ram to test.
I have tested the machine with M.2 ssd only, no luck.
 

Attachments

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top