New
#11
Hello, there are 2 ways to track down the problem.
1. one thing looks obvious, unless I'm wrong ofc:
A. these bsods are happening due to buffer overrun, thus corrupting memory by writing outside of range.
B. the dll that is reporting too small buffer is perfts.dll which is a performance counters library
now we need a way to figure out which drivers or applications are loading this dll, this will help to test out these drivers
or applications, ie. by removing them.
For this you will need Process explorer:
https://docs.microsoft.com/en-us/sys...ocess-explorer
and here is tutorial how to tell which programs are loading which dlls.
Getting a list of DLLs currently loaded in a process
the above tutorial also tells how to save report to file, so you may want to share this file.
however you will need to first select process that loads before mentioned dll and save to file, and so on select each process that loads this dll and save to separete file, then zip up all files and send here.
NOTE: you must run process explorer as administrator.
2. another way could be easier by just enabling driver verifier.
see bellow tutorial on how to do this: (just make sure you have a restore point!)
https://answers.microsoft.com/en-us/...3-c48669e4c983
driver verif. will test drivers and produce bsod, which will tell us which driver is causing this.
so you need to upload new dumps generated by driver verif.
note it may not be needed to upload full memory dumps once driver verifier is enabled.
edit:
2nd mehtod, driver verifier will identify a driver,
1st method will identify a process.
which ever turns out to be helpful.
Additional information that could help:
Does this problem happen while using specific application(s)?
Last edited by zebal; 25 Jan 2020 at 11:10.