[Lenovo legion y530] Latency problems

[Vezovi]

Yes, checked 2 different places.
Laptop has already been sent to lenovo service, they found nothing wrong with hardware.
But im worried its more complicated hardware problem, so there is nothing i can do...
wdf01000.sys spikes only when moving mouse/touchpad
acpi.sys randomly every few seconds and extremely when pressing fn+ smth

 

[xilolee]

Did you set the raid option in the bios on purpose?

 

[Vezovi]

Yes, it fixed similar problem for someone, but not for me. Im not sure if i did it right, because i changed it without reinstalling OS. Default is AHCI

 

[xilolee]

If it's present an RST option, try that one.

 

[Vezovi]

Done, set RST in bios and irst driver installed, but problem is still there

 

[xilolee]

Perform the operations described in the following link and post their results: Basic clean-up, check-up and repair of Windows (W10, W8/8.1, W7)

 

[Vezovi]

Everything is ok.
Windows has scanned the file system and found no problems.
No further action is required.
No component store corruption detected.
Minimal boot also shows same ISR and DPC count on wdf01000 and acpi
Disabling acpi battery in device manager, gtx etc. doesn't fix it.
Friend of mine doesn't have this kind of latency problems on his ACER nitro 5. His setup is similar to mine, but he doesn't have SSD.
The only thing comes to my mind is to try fresh install of windows on HDD, leaving ssd empty. But i really don't want to do reinstall once again...

 

[xilolee]

Did you run defrag?

 

[Vezovi]

Not needed

 

[xilolee]

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:

     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:

     
     - export/save your current bcdedit system store content in c:\DEFAULT-BCDedit-SystemStoreContent
     - show the current bcdedit content in "BCDoriginal.txt" (on your desktop)
     - 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
     - show the modified bcdedit content in "BCDmodified.txt" (on your desktop)
     - find non-microsoft drivers and set the necessary driver verifier settings
     - restart your PC after two minutes (you can abort this with "shutdown -a" in an elevated command prompt)
     - the boot menu should appear at every restart and it should allow you to select windows advanced boot options (SAFE MODE included).
     I've added the parameter /bootmode resetonbootfail.
     This should reset driver verifier if it should cause a BSOD.
     It should appear something like:

     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.

  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:

     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:

  md "%userprofile%\desktop\minidump" && copy c:\windows\minidump "%userprofile%\desktop\minidump"

 

[Vezovi]

How long will it take and how do i know that it has ended, if BSOD wont happen?

 

[xilolee]

Wait from 24 hours to 72.
If a BSOD won't happen in 72 hours, you'll reset verifier settings.
It usually causes a BSOD in less time, if there is a problematic driver.

 

[Vezovi]

Is there a possibility to check actual progress?
command query shows this:

Spoiler: screen

 

[xilolee]

Maybe you can check some statistics in the driver verifier GUI, but I'm not sure of it.
Or in Event Viewer...
Anyway It seems it's working.

 

[xilolee]

Yesterday, you have restarted the machine, right?

 

[Vezovi]

Yes, it restarted automatically
it looks like it's not working

Spoiler: spoiler

 

[xilolee]

I found the script doesn't work correctly and cut some drivers names.
Sorry...

Open an elevated command prompt, type verifier /reset , press enter, restart.
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:

I.e., these boxes should be checked:

• DDI compliance checking (standard)
• Deadlock Detection (standard)
• Force IRQL checking (standard)
• Miscellaneous Checks (standard)
• Pool Tracking (standard)
• Security Checks (standard)
• Special Pool (standard)
• Power framework delay fuzzing (Additional)

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

 

[Vezovi]

Done, it's working now :)

 

[xilolee]

This time, if a BSOD Will appear, you have to enter safe mode and type verifier /reset (from an elevated command prompt) to reset verifier settings.

 

[Vezovi]

After 30+ hours nothing happened, so i turned it off, because i couldn't play anything. I can't find any statistics, command query only shows tons of numbers, 0 failures, so i don't think it's driver related.