Random Numerous BSOD majority are 133 errors

Page 2 of 4 FirstFirst 1234 LastLast

  1. Posts : 38,356
    windows 10 professional version 1607 build 14393.969 64 bit
       #11

    Open administrative command prompt and type or copy and paste:
    1) sfc /scannow
    2) dism /online /cleanup-image /restorehealth
    3) chkdsk /scan
    When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    4) msconfig (in the pop up system configuration > move the dot from normal startup to selective startup > uncheck load startup items > click service tab > in left lower corner check hide all Microsoft services > in the lower right side click disable all > click apply or ok > do not reboot)

    5) taskmgr (in the pop up task manager > click on the start up tab > click on status so that the column sorts with enable rising to the top > right click on each row with enable and change to disable)

    https://support.microsoft.com/en-us/...oot-in-windows

    How to perform a Clean Boot in Windows 10 - TechNet Articles - United States (English) - TechNet Wiki

    6) shutdown /r (you will reboot the computer so that it is in clean boot)

    7) Attempt the DM log collector when in clean boot and post the zip into the thread:
    BSOD - Posting Instructions - Windows 10 Forums
      My Computer


  2. Posts : 20
    wundows 10 pro
    Thread Starter
       #12
      My Computer


  3. Posts : 20
    wundows 10 pro
    Thread Starter
       #13

    I finally have a log file that is not empty, can someone take a look at it.

    Thanks
      My Computer

  4. philc43's Avatar
    Posts : 4,973
    64bit Win 10 Pro ver 20H2 Build 19042.868 and W10 Insider Preview Build 21343
       #14

    There are a range of different BSOD errors as you pointed out, these tend to suggest that you may have a hardware issue.

    Some of the possible causes identified by WinDbg are shown below:

    Code:
    BugCheck 7F, {8, ffff8400885c8bf0, ffff840088c38000, fffff802d7f78d6d}
    
    *** WARNING: Unable to verify checksum for win32k.sys
    Probably caused by : memory_corruption
    
    BugCheck 3B, {c0000005, fffff80250f47fd9, ffffaa001f7eb6e0, 0}
    
    Probably caused by : hardware ( nt!PfpPfnPrioRequest+2c9 )
    
    BugCheck 7F, {8, ffffd40095e4fbf0, ffffd4009b8c7ec0, fffff80227a3496c}
    
    Probably caused by : memory_corruption
    Please test your RAM: Note: this will probably take more than a day to complete the testing.



    Diagnostic Test

     RAM TEST


    Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

    Note   Note


    MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.


    Make a photo of the result and post it.

    Addition:
    If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
    If errors show up and you see them a lot later, no problem, the errors don't affect the test.
    Last edited by philc43; 13 Sep 2017 at 11:07. Reason: added additional info
      My Computers


  5. Posts : 38,356
    windows 10 professional version 1607 build 14393.969 64 bit
       #15

    When available please post the results of the steps in post #11.
    When you were able to generate the DM log was it after all of the steps?
    Had you tried it after steps 1 -3 and before clean boot or only after clean boot?
      My Computer


  6. Posts : 20
    wundows 10 pro
    Thread Starter
       #16

    I never could get the DM log to create a suitable file. I copied the TPfile into the DM log folder.

    I am going to start the mem test right now.

    Thanks for your patience.

    leo
      My Computer


  7. Posts : 38,356
    windows 10 professional version 1607 build 14393.969 64 bit
       #17

    LeoH said:
    I never could get the DM log to create a suitable file. I copied the TPfile into the DM log folder.
    We would like to have the DM log collector work smoother.
    Please describe where the DM log collector got stuck or appeared to malfunction.
    Was it not apparent until you viewed the end result or were you able to see a problem before the attempted viewing?
    Please describe the steps in as much detail as possible what you did to be able to post a working log.
      My Computer


  8. Posts : 20
    wundows 10 pro
    Thread Starter
       #18

    I followed the instructions as best I could and every seemed to work fine, no error messages, hangs or anything. But if you use file explorer to check the properties is says it 22 bytes long and the size on the disk is 0. I seen where someone asked what to do with the TPfile and they said that it was the source of the DMLog folder. So I copied the contents to the DMLog folder. It was then 11 MB long, so I deleted the larger files until I got down to 1,i73 MB. I thought I see where the "Zip" had a maximum size of 2 MB.
      My Computer


  9. Posts : 38,356
    windows 10 professional version 1607 build 14393.969 64 bit
       #19

    Which is the TP file?
    Which files did you delete?
    Is your impression that it was a compression issue?
      My Computer


  10. Posts : 20
    wundows 10 pro
    Thread Starter
       #20

    The file that I copied the dmp files is named TFDebugFiles.

    The mem test ran for 19 cycles and 20 hours. No errors.
      My Computer


 
Page 2 of 4 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 20:09.
Find Us




Windows 10 Forums