DPC Latency problem

[zClown]

Uninstall intel RST.

What is intel RST?

EDIT: I don't have rapid storage technology installed

Can I do something else to help you finding out the cause of high latency

 

[xilolee]

Nonetheless, its drivers iaStorAV and iaStorA appear in your logs.
Also arcsas, nvraid, sisraid2, sisraid4, vsmraid, vstxraid.
Even if it seems all of them are not currently started and used.

I'll admit I have all of them too...

And at this point I'm not sure if they are remnants of previous installations or if they came with windows installation.

 

[zClown]

Nonetheless, its drivers iaStorAV and iaStorA appear in your logs.
Also arcsas, nvraid, sisraid2, sisraid4, vsmraid, vstxraid.

I'll admit I have all of them too...

And at this point I'm not sure if they are remnants of previous installations or if they came with windows installation.

Maybe they came with INF driver or windows update, this is the picture of all my drivers, take a look
Imgur: The most awesome images on the Internet

 

[xilolee]

Did you already update your mouse software? This seems to be the newer software version for it: 8.91.48.

 

[zClown]

Did you already update your mouse software? This seems to be the newer software version for it: 8.91.48.

Yes, in my previous post of all installed software it's written 8.91.48.

 

[xilolee]

You could try to run driver verifier; please read CAREFULLY the following instructions:

• Only for windows 8, 8.1, 10 users (Win7 users, WinVista users, XP users, shouldn't have this problem):
  • change the bcdedit {bootmgr} displaybootmenu setting from No to Yes
  • change the bcdedit {bootmgr} timeout setting to 30 seconds
  • change the bcdedit bootmenupolicy setting from standard to legacy
  • restart your PC and see if the boot menu appears and if it allows you to select windows advanced boot options (SAFE MODE included!) with the good old F8 key.
  See the hidden instructions if you don't know how to do it.
  Read More:

  From an elevated command prompt, launch these commands:

  bcdedit
  bcdedit /set {bootmgr} displaybootmenu yes
  bcdedit /set {bootmgr} timeout 30
  bcdedit /set {current} bootmenupolicy legacy
  bcdedit

  You should get something like (see bold strings):

  Read More:

  c:\>bcdedit
  
  Windows Boot Manager
  --------------------
  identificatore {bootmgr}
  device partition=\Device\HarddiskVolume2
  path \EFI\Microsoft\Boot\bootmgfw.efi
  description Windows Boot Manager
  locale it-IT
  inherit {globalsettings}
  integrityservices Enable
  default {current}
  resumeobject {5d5a201e-d643-11e4-a71c-9001aae18364}
  displayorder {current}
  toolsdisplayorder {memdiag}
  timeout 30
  displaybootmenu No
  
  Caricatore di avvio di Windows
  -------------------
  identificatore {current}
  device partition=C:
  path \WINDOWS\system32\winload.efi
  description Windows 10 home x64
  locale it-IT
  inherit {bootloadersettings}
  recoverysequence {4a081ca8-71be-11e6-80cd-eca86b8ec766}
  integrityservices Enable
  recoveryenabled Yes
  isolatedcontext Yes
  allowedinmemorysettings 0x15000075
  osdevice partition=C:
  systemroot \WINDOWS
  resumeobject {5d5a201e-d643-11e4-a71c-9001aae18364}
  nx AlwaysOn
  bootmenupolicy Standard
  quietboot No
  
  C:\>bcdedit /set {bootmgr} displaybootmenu yes
  The operation completed successfully.
  
  C:\>bcdedit /set {bootmgr} timeout 30
  The operation completed successfully.
  
  C:\>bcdedit /set {current} bootmenupolicy legacy
  The operation completed successfully.
  
  c:\>bcdedit
  
  Windows Boot Manager
  --------------------
  identificatore {bootmgr}
  device partition=\Device\HarddiskVolume2
  path \EFI\Microsoft\Boot\bootmgfw.efi
  description Windows Boot Manager
  locale it-IT
  inherit {globalsettings}
  integrityservices Enable
  default {current}
  resumeobject {5d5a201e-d643-11e4-a71c-9001aae18364}
  displayorder {current}
  toolsdisplayorder {memdiag}
  timeout 30
  displaybootmenu Yes
  
  Caricatore di avvio di Windows
  -------------------
  identificatore {current}
  device partition=C:
  path \WINDOWS\system32\winload.efi
  description Windows 10 home x64
  locale it-IT
  inherit {bootloadersettings}
  recoverysequence {4a081ca8-71be-11e6-80cd-eca86b8ec766}
  integrityservices Enable
  recoveryenabled Yes
  isolatedcontext Yes
  allowedinmemorysettings 0x15000075
  osdevice partition=C:
  systemroot \WINDOWS
  resumeobject {5d5a201e-d643-11e4-a71c-9001aae18364}
  nx AlwaysOn
  bootmenupolicy Legacy
  quietboot No

• Create a restore point
• Create a system image
• 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.
• Enable verifier
  You can use either the standard method, or the EXPERIMENTAL instructions at the end of this post.
  No need to use them both.
  By the way, in the experimental instructions I modified some verifier settings: I've added the parameter /bootmode resetonbootfail.
  This should reset driver verifier if it should cause the pc to go in BSOD loop state (see next point).
  This option is incompatible with windows 7 and windows vista (it should be skipped by them).
• If you'll get a very fast BSOD after you logged into windows, you'll need to go to safe mode to reset verifier settings.
  From an elevated command prompt:

  verifier /reset

• Post here the new verifier dump

---

Danger

I created the following method to speed up things a bit, to enable verifier settings like written in Jcgriff's verifier thread, using only third party drivers (hence excluding microsoft drivers).
This was tested only on Windows 10 home x64 (and partially on windows 7)

• download nirsoft driverview and decompress its folder (leaving its default name) on your desktop, i.e. on the desktop there should be the driverview folder (with its files in it):
  • nirsoft driverview x64 (for 64bit versions)
  • nirsoft driverview (x86) (for 32bit versions)
• open notepad, copy the following text and save the file on your desktop as EnableVerifier.ps1:
  
  Note:

  Code for 64bit windows versions
  
  
  Read More:

  
  $extdrivers="$env:userprofile\desktop\extdrivers.txt"
  $extdrivers2="$env:userprofile\desktop\extdrivers2.txt"
  $tempfile="$env:userprofile\desktop\temp.txt"
  $output="$env:userprofile\desktop\Non-ms-drivers.txt"
  $command = {c:\windows\system32\cmd.exe /c '%userprofile%\Desktop\driverview-x64\driverview.exe' /sort 1 /stext %userprofile%\desktop\extdrivers.txt}
  Invoke-Command -scriptblock $command
  type $extdrivers | find /i "driver name" | out-file $extdrivers2
  $drivers = Get-Content $extdrivers2
  FOR ($i=1; $i -lt $drivers.Length; $i++) {
  NV -Name "linea$i"
  SV -name "linea$i" -value ($drivers.GetValue($i))
  $tmp = GV -name linea$i -valueonly
  $tmp = ( $tmp.TrimStart("Driver Name : ") + " , " )
  $tmp | out-file $tempfile -append
  RV -Name "linea$i"
  }
  $tmp = get-content $tempfile | sort
  $tmp = $tmp -join ""
  $tmp = $tmp.TrimEnd(" , ")
  $tmp = $tmp.Replace(" , ", ",")
  $tmp | out-file $output
  verifier /flags 0x2892B /bootmode resetonbootfail /driver $tmp
  del $output, $extdrivers, $tempfile, $extdrivers2
  rv tmp, tempfile, output, i, extdrivers2, drivers
  
  Note:

  Code for 32bit windows versions
  
  
  Read More:

  
  $extdrivers="$env:userprofile\desktop\extdrivers.txt"
  $extdrivers2="$env:userprofile\desktop\extdrivers2.txt"
  $tempfile="$env:userprofile\desktop\temp.txt"
  $output="$env:userprofile\desktop\Non-ms-drivers.txt"
  $command = {c:\windows\system32\cmd.exe /c '%userprofile%\Desktop\driverview\driverview.exe' /sort 1 /stext %userprofile%\desktop\extdrivers.txt}
  Invoke-Command -scriptblock $command
  type $extdrivers | find /i "driver name" | out-file $extdrivers2
  $drivers = Get-Content $extdrivers2
  FOR ($i=1; $i -lt $drivers.Length; $i++) {
  NV -Name "linea$i"
  SV -name "linea$i" -value ($drivers.GetValue($i))
  $tmp = GV -name linea$i -valueonly
  $tmp = ( $tmp.TrimStart("Driver Name : ") + " , " )
  $tmp | out-file $tempfile -append
  RV -Name "linea$i"
  }
  $tmp = get-content $tempfile | sort
  $tmp = $tmp -join ""
  $tmp = $tmp.TrimEnd(" , ")
  $tmp = $tmp.Replace(" , ", ",")
  $tmp | out-file $output
  verifier /flags 0x2892B /bootmode resetonbootfail /driver $tmp
  del $output, $extdrivers, $tempfile, $extdrivers2
  rv tmp, tempfile, output, i, extdrivers2, drivers
  
• From an elevated command prompt, run:

  powershell -executionpolicy unrestricted "%userprofile%\desktop\EnableVerifier.ps1"

• It should appear something like:
  Read More:

  Verifier Flags: 0x0002892b
    Standard Flags:
      [X] 0x00000001 Special pool.
      [X] 0x00000002 Force IRQL checking.
      [X] 0x00000008 Pool tracking.
      [ ] 0x00000010 I/O verification.
      [X] 0x00000020 Deadlock detection.
      [ ] 0x00000080 DMA checking.
      [X] 0x00000100 Security checks.
      [X] 0x00000800 Miscellaneous checks.
      [X] 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.
      [X] 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.
    Boot Mode:
      Resetonbootfail
    Rules:
      All rules are using default settings
    Extensions:
      wdm: rules.default
      ndis: rules.default
    Verified Drivers:
  More data is available.
  The system reboot is required for the changes to take effect.

• Reboot your machine and wait the verifier dump (i.e., verifier should force a new BSOD, identifying the problem).

 

[zClown]

Thank you xilolee, I decided not to pay attention at this problem anymore, because it's not possible to solve it and in the end it will bring even more problems.

 

[xilolee]

Ok, your choice.

Another (simple) thing you could try is to exclude from Win10 Defender the game folders, only if you are sure you (or the program) won't download and run anything inside that folder, obviously (I don't use steam, hence I'm not sure about that):
D:\Programos\Steam\steamapps\Common\Half-Life\
D:\Programos\Steam\steamapps\Common\Counter-Strike Global Offensive\