New
#21
Yes reran it before I posted the newest V2 - run it again?
Yes reran it before I posted the newest V2 - run it again?
Yes please. If/when you get a BSOD, run V2 as soon as possible. Also, take a picture of the BSOD screen if there is any information on it that may be useful. Make sure Automatic restart on system failure is disabled:
You can turn off automatic restart so you can read BSOD information:
Right click on This PC and select Properties.
Click Advanced system settings then Startup and Recovery Settings.
Uncheck box for Automatically restart.
OWNER981841-PC-(2020-07-26_10-39-36).zip - Google Drive
.062620-25890-01.zip - Google Drive
Hope these worked - had to safe boot to run it
Did you take pictures of any of the BSOD screens when Driver Verifier was active?
Have you disabled Automatic Restart yet?
None of the dumps in the zip have Driver Verifier enabled.
Sorry Rich I am not sure I know what I did wrong. Will go back to square one from your original post and repeat it all. I could not take pix of BSOD but the message stated Corrupted PFN - I will write down any following messages and report in. Thanks for your patient assistance.
I'm asking for the pic of the BSOD screen in case there is information on the screen indicating what driver cause it. Sometimes it gets overlooked.
When you use DV this time, start with 5 drivers. After a half hour or hour, if no BSOD, add 5 more and repeat.
OK will try that. I will try to get a pic for you next crash
I ran with verifier two days without any BSOD excepting the PFN LIST CORRUPT that occurs at shutdown. I went back through all steps and here are the logfiles. Log Collector stopped when msinfo.exe timed out. I reran this manually and it got hung at OLE Registration step.
072920-12640-01.zip - Google Drive
OWNER981841-PC-(2020-07-30_09-53-22).zip - Google Drive
- - - Updated - - -
msinfo32.nfo - Google Drive
Last edited by bam12b; 30 Jul 2020 at 09:55. Reason: typo
Run the older DM log collector and upload it's zip file.
Run Verifier again, following this tutorial: Enable and Disable Driver Verifier in Windows 10
Especially Part Two Step 4.
Also make sure these are checked:
[X] 0x00000200 Force pending I/O requests.
[X] 0x00000400 IRP logging.
[X] 0x00200000 NDIS/WIFI verification.
[X] 0x02000000 Code integrity checks.
Zbook just pointed out to me there was a driver problem in a dump from 7/26 : 062620-25890-01.dmp
Code:PFN_LIST_CORRUPT (4e) Typically caused by drivers passing bad memory descriptor lists (ie: calling MmUnlockPages twice with the same list, etc). If a kernel debugger is available get the stack trace. Arguments: Arg1: 0000000000000007, A driver has unlocked a page more times than it locked it Arg2: 00000000000033cb, page frame number Arg3: 0000000000000001, current share count Arg4: 0000000000000000, 0 Debugging Details: ------------------ *** WARNING: Unable to verify timestamp for LHidEqd.SysName LEqdUsb.Sys Date: 6/9/2015 3:25:30 PMCode:fffff58d`1e3c46b0 fffff803`135a0000Unable to load image LEqdUsb.Sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for LEqdUsb.Sys LEqdUsb
Info Logitech SetPoint Unifying KMDF USB Filter
Source SetPoint – Logitech Support + Download
Driver is pretty old. See if you can find an update for it or uninstall it if it's not needed.