Random and Ongoing BSOD's

Page 2 of 5 FirstFirst 1234 ... LastLast
  1. zebal's Avatar
    Posts : 905
    Windows 10 Pro x64 20H2 (Build: 19042.867)
       #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 10:10.
      My Computer


  2. Posts : 21
    Windows 10
    Thread Starter
       #12

    cwsink said:
    This may apply to your situation. The block wasn't put in place for some time after 1903 was released. Are you still having crashes after updating IRST?
    Thanks for the extra info... since i updated the IRST (last night) no crashes have happened.. i will watch it over the next few days and see if that helped. Sadly the newest version of the driver which applies to my board is the following per Intel:

    Latest version: 14.8.16.1063 Installed Version: 14.8.16.1063
    This download installs the Intel® Rapid Storage Technology (Intel® RST) RAID driver version 14.8.16.1063.
    Release date: May 3, 2017Size: 14 MB

    Anything after Ver 14.8.16.1063 gives an error that "This platform is not supported." So looks like the one i have installed is the newest for my chipset. Hopefully 14.8 solves the problem. If not i just need to limp this thing to April when it will be replaced lol
      My Computer


  3. Posts : 38,371
    windows 10 professional version 1607 build 14393.969 64 bit
       #13

    Depending on how IRST is being used on some computers the software can be removed.
    If this is an option testing can be done to see the impact on instability / stability.
      My Computer


  4. Posts : 207
    Windows 10 Pro
       #14

    Please let us know how it goes. As zbook wrote, IRST is often optional and can be uninstalled unless it was used to build a RAID array. That's the only time it's required, as far as I know.
      My Computer


  5. Posts : 21
    Windows 10
    Thread Starter
       #15

    cwsink said:
    Please let us know how it goes. As zbook wrote, IRST is often optional and can be uninstalled unless it was used to build a RAID array. That's the only time it's required, as far as I know.
    Quick update: Since updating the IRST to the newest available version the system has had 2 BSOD episodes... I have added the updated Dmp, miniDump and V2 Log (in zip format) to the google drive @
    BSOD Files - Google Drive

    And moved the prior crash files to the Prior Crash folder @
    Prior Crash Files - Google Drive

    I guess next i will try and uninstall the IRST and see if that does anything unless something else is showing in the dumps you guys see.

    Thanks again for your help.
      My Computer

  6. zebal's Avatar
    Posts : 905
    Windows 10 Pro x64 20H2 (Build: 19042.867)
       #16

    You failed to answer to my post, can you please at least enable driver verifier as discussed before.
    and possibly check which component is loading performance library.
      My Computer


  7. Posts : 21
    Windows 10
    Thread Starter
       #17

    zebal said:
    You failed to answer to my post, can you please at least enable driver verifier as discussed before.
    and possibly check which component is loading performance library.
    Sorry i missed your suggestion. I will have to run verifier after work later today and let you know the results.
      My Computer


  8. Posts : 207
    Windows 10 Pro
       #18

    The latest memory.dmp file has a bug check code of 12B and the link here describes what causes such crashes. In this case "the Compressed Store Manager due to a failure to decompress a page due to physical memory corruption" according to the documentation.

    Memtest86 is usually pretty reliable when testing DDR3 so I would tend to assume it was okay if it got through 8 full passes without any errors. The system was up for 15 hours before it crashed - was that with frequent use or mostly idle/sleep mode?
      My Computer


  9. Posts : 21
    Windows 10
    Thread Starter
       #19

    zebal said:
    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)?
    Ok so i setup Driver Verifier per the instructions of the page you linked and got stuck in a reboot crash cycle, i had to boot to safe mode to delete the verifier settings to get back into the system.

    Process explorer (from fresh boot with no programs open except Chrome so i can get to the posts) doesn't show any processes currently using Perfts.dll so i guess ill have to keep checking that as i open programs throughout the day.

    The search continues...

    - - - Updated - - -

    cwsink said:
    The latest memory.dmp file has a bug check code of 12B and the link here describes what causes such crashes. In this case "the Compressed Store Manager due to a failure to decompress a page due to physical memory corruption" according to the documentation.

    Memtest86 is usually pretty reliable when testing DDR3 so I would tend to assume it was okay if it got through 8 full passes without any errors. The system was up for 15 hours before it crashed - was that with frequent use or mostly idle/sleep mode?
    The system crashed at 9:21pm on 01/26/2020 (1st crash since updated IRST)

    2nd Crash happened at 12:30pm on 01/28/2020 - the previous 24 hrs of use have been as follows:
    01/27/2020 - in use from 12pm - 4pm >> idle mostly from 4pm - 9pm >>> in use from 9pm - 12am >>> idle mostly 12am - 9am >>> in use from 9am till crash at 12:30pm (occasionally went to sleep/hibernate/whichever one it does) at the time of crash i was actively working with the system. Due to the type of work i do and the amount of research i typically have alot of browser windows open and i was moving between them when the BSOD happened.
      My Computer

  10. zebal's Avatar
    Posts : 905
    Windows 10 Pro x64 20H2 (Build: 19042.867)
       #20

    parham93 said:
    Ok so i setup Driver Verifier per the instructions of the page you linked and got stuck in a reboot crash cycle, i had to boot to safe mode to delete the verifier settings to get back into the system.
    reboot/crash cycle, does that mean bsods? if yes upload them please to find out where is the problem.

    parham93 said:
    Process explorer (from fresh boot with no programs open except Chrome so i can get to the posts) doesn't show any processes currently using Perfts.dll so i guess ill have to keep checking that as i open programs throughout the day.
    Did bsod usually happen while using specific application or operation? (that applies to times before using driver verifier)
      My Computer


 
Page 2 of 5 FirstFirst 1234 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 03:29.
Find Us




Windows 10 Forums