Different BSODs or freezing while gaming or at desktop

Page 1 of 2 12 LastLast

  1. Posts : 8
    Microsoft Windows 10 Home 64-bit 15063 Multiprocessor Free
       #1

    Different BSODs or freezing while gaming or at desktop


    Recently I had been getting BSODs or freezing (no response from input, no pointer movement, screen stuck, last sound looping through speakers) that seemed to start around the time that the Win10 Creator Update hit my windows update. That was roughly a week ago. The frequency of the crashes has varied, with some coming in groups of 2 or 3 within minutes, and others hours or days apart. Usually in between the crashes, which can be infrequent, everything seems to run normally. I haven't found one action or program that can set it off, as it's happened during online gaming, while AFK at the desktop, and everywhere in between. It also doesn't consistently give the same bluescreen error.

    I tried a fresh install of Win10, in case I had gotten a bad creator update, but the BSODs kept coming, both with the fresh Windows 10 install, and after it downloaded the creator update once again. I tried replacing the ram with different sticks earlier today (8/19), but I had another no-BSOD freeze since. I attempted to run Driver Verifier, but that caused a BSOD either on startup, or shortly after, and it didn't give a file name on the bluescreens that it caused. I ended up trying it twice, both times shutting it off after a few restarts.

    Thank you for any help.
      My Computer


  2. Posts : 41,472
    windows 10 professional version 1607 build 14393.969 64 bit
       #2

    Hi JKBNSINH ,

    Welcome to Ten Forums.
    There were 8 bsod mini dump files debugged.
    There were 5 misbehaving drivers.
    There were 2 software misbehaving drivers and 3 hardware misbehaving drivers.
    Windows fast start up failed.

    Open administrative command prompt and type or copy and paste these commands:
    1) sfc /scannow
    2) dism /online /cleanup-image /restorehealth
    3) chkdsk /scan

    4) 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

    5) Run memtest86+ version 5.01 for at least 8 runs.
    This may take many hours so plan to run it overnight.
    http://www.memtest.org/
    When Memtest86+ has completed 8 or more runs use a camera or smart phone camera to take a picture and post an image into the thread.
    Memtest86+ is perform not by time but by passes.
    The more passes the better.
    Fewer than 8 passes has a high incidence of false negatives.
    A false negative is a pass with Malfunctioning RAM.
    There is 16 GB RAM on the computer.
    Memtest 86+ takes approximately 1 - 2 hours / GB RAM.
    Just 1 error is a fail and you can abort testing.
    Then test 1 RAM at a time in the same DIMM for 8 passes each.
    If the RAM testing fails when tested together and passes when tested independently the RAM needs to be tested again in another DIMM to differentiate malfunctioning RAM from malfunctioning DIMM/MB.
    After each test please use a camera or smart phone camera to take pictures and post images into the thread.

    https://answers.microsoft.com/en-us/windows/wiki/windows_10-update/memory-problems/21c3f63f-f570-4522-b2ef-ecc7b7ff6461

    https://www.tenforums.com/tutorials/14201-memtest86-test-ram.html


    7) Turn off Windows fast startup:
    Turn On or Off Fast Startup in Windows 10 Windows 10 Performance Maintenance Tutorials

    8) Make sure that there is no over clocking while troubleshooting.

    Sometimes there are problems in the bios that produce bsod.

    The bios in your computer: BIOS Version/Date American Megatrends Inc. F4, 10/20/2015

    9) Please check to see if this is the most up to date version.

    10) To ensure that there are no improper bios settings please reset the bios.

    Sometimes there can be failure to boot after resetting the bios.

    11) So please make sure your files are backed up.

    12) Please make a backup image with Macrium:
    Macrium Software | Macrium Reflect Free:
    Macrium Software | Your Image is Everything

    13) And please create a restore point.

    How to Clear Your Computers CMOS to Reset BIOS Settings:
    How to Clear Your Computers CMOS to Reset BIOS Settings

    3 Ways to Reset Your BIOS - wikiHow:
    3 Ways to Reset Your BIOS - wikiHow

    14) Uninstall all Trend Microsoftware
    Home and Home Office Support | Trend Micro
    Maximum Security Support - Home and Home Office Support | Trend Micro

    15) Turn on Windows defender

    16) Use device manager to uninstall Killer Bandwidth Control filter driver bwcW10x64.sys
    Reinstall: Support

    17) Use device manager to uninstall Realtek Hi definition Audio driver: MBfilt64.sys
    Reinstall: Realtek

    18) The best way to fix the misbehaving Nvidia driver is to uninstall everything Nvidia using Display driver uninstaller and install new drivers from the computer manufacturer's website or from the Nvidia website.

    The computer manufacturer's web site is preferred.
    Enter the computer's serial or product number and the operating system to view available drivers.

    If you use the Nvidia web site be sure the "clean install" box is checked and only install the graphics driver and the physx driver.

    Official Display Driver Uninstaller DDU Download
    Display Driver Uninstaller Download version 17.0.7.2

    Display Driver Uninstaller: How to use - Windows 7 Help Forums

    NVIDIA

    19) Turn off Windows fast startup:
    Turn On or Off Fast Startup in Windows 10 Windows 10 Performance Maintenance Tutorials


    Code:
    ffff9b81`2eaa49e0  fffff80a`ddd99760Unable to load image \SystemRoot\system32\DRIVERS\tmcomm.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for tmcomm.sys*** ERROR: Module load completed but symbols could not be loaded for tmcomm.sys
    tmcomm.sys Trend Micro Internet Security/ Housecall scanner http://us.trendmicro.com/us/download...nd-homeoffice/


    tmevtmgr.sys Trend Micro Internet Security http://trendmicro.software.net/
    Code:
    ffff9901`057bca38  fffff809`22294c30Unable to load image \SystemRoot\system32\DRIVERS\bwcW10x64.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for bwcW10x64.sys*** ERROR: Module load completed but symbols could not be loaded for bwcW10x64.sys bwcW10x64+0x4c30
    Code:
    BfLwf        Killer Bandwidth Contr Killer Bandwidth Contr Kernel        System     Running    OK         TRUE        FALSE        0                 102,400     0          9/15/2016 12:22:54 PM  C:\WINDOWS\system32\DRIVERS\bwcW10x64.sys        8,192
    Code:
    ffff9901`057bc138  fffff809`21ca4909Unable to load image \SystemRoot\system32\DRIVERS\tmeevw.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for tmeevw.sys*** ERROR: Module load completed but symbols could not be loaded for tmeevw.sys tmeevw+0x4909
    Code:
    BugCheck C4, {2000, fffff80c620f4b94, 0, 774e6350}*** WARNING: Unable to verify timestamp for MBfilt64.sys*** ERROR: Module load completed but symbols could not be loaded for MBfilt64.sysProbably caused by : MBfilt64.sys ( MBfilt64+4b94 )
    MBfilt64.sys Realtek HiDefinition Audio driver (file labelled as Creative Audio Driver) - Was found in the latest Win8 version available from Realtek on 07Sep2013 http://www.realtek.com.tw/downloads/...&GetDown=false
    Code:
    MBfilt       MBfilt                 MBfilt                 Kernel        Manual     Running    OK         TRUE        FALSE        4,096             12,288      0          7/30/2009 11:40:32 PM  C:\WINDOWS\system32\drivers\MBfilt64.sys         8,192
    Code:
    ffffbf00`6ddb2d08  fffff807`e328f1a4Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvlddmkm.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for nvlddmkm.sys*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys nvlddmkm+0x15f1a4
    Code:
    nvlddmkm     nvlddmkm               nvlddmkm               Kernel        Manual     Running    OK         TRUE        FALSE        5,820,416         6,438,912   0          5/1/2017 3:55:53 PM    C:\WINDOWS\system32\DriverStore\FileRepository\n 36,864
    nvlddmkm.sys nVidia Video drivers http://www.nvidia.com/Download/index.aspx
    Get from OEM for laptops




    Code:
    Windows failed fast startup with error status 0xC00000D4.
    Last edited by zbook; 20 Aug 2017 at 03:13.
      My Computer


  3. Posts : 8
    Microsoft Windows 10 Home 64-bit 15063 Multiprocessor Free
    Thread Starter
       #3

    Thank you for the welcome and reply! The CMD prompt copy/paste:

    Code:
    Microsoft Windows [Version 10.0.15063]
    (c) 2017 Microsoft Corporation. All rights reserved.
    
    C:\WINDOWS\system32>sfc /scannow
    
    Beginning system scan. This process will take some time.
    
    Beginning verification phase of system scan.
    Verification 100% complete.
    
    Windows Resource Protection did not find any integrity violations.
    
    C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth
    
    Deployment Image Servicing and Management tool
    Version: 10.0.15063.0
    
    Image Version: 10.0.15063.0
    
    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.
    
    C:\WINDOWS\system32>chkdsk /scan
    The type of the file system is NTFS.
    
    Stage 1: Examining basic file system structure ...
    327168 file records processed.
    File verification completed.
    12381 large file records processed.
    0 bad file records processed.
    
    Stage 2: Examining file name linkage ...
    442838 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.
    
    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    57836 data files processed.
    CHKDSK is verifying Usn Journal...
    34952376 USN bytes processed.
    Usn Journal verification completed.
    
    Windows has scanned the file system and found no problems.
    No further action is required.
    
    116343308 KB total disk space.
    70040060 KB in 238735 files.
    179416 KB in 57837 indexes.
    0 KB in bad sectors.
    437252 KB in use by the system.
    65536 KB occupied by the log file.
    45686580 KB available on disk.
    
    4096 bytes in each allocation unit.
    29085827 total allocation units on disk.
    11421645 allocation units available on disk.
    
    C:\WINDOWS\system32>

    Memtest:
    Unfortunately, I ran into an issue here. I started memtest before going to bed, as suggested, and while it had found no errors when I checked, the program itself seemed to have frozen after 4 passes. The little spinning "active" indicator wasn't moving, the test and pass progress had stalled, and the count of how long the test was running for had been stopped for a while when I checked it. I tried C to open config, and then ESC to exit out, but it didn't respond to either and I had to manually power off to get out of it. I can attempt to run it again tonight, or run one of the single DIMM tests, but I'm not sure if it would do the same.

    Fast Start:
    I went into power options and turned Fast Start off.

    BIOS and Overlock:
    I updated from the 10/2015 (F4) BIOS to 06/2017 (F22) and loaded the BIOS default settings. I don't overclock this PC manually, but I'm not positive if there are settings that do an automatic overclock in the BIOS. It's a "Gaming" motherboard, so it's possible, but there are pages of settings that I never touched, all set to "Auto". I'll look into that.

    Drivers:
    - I used the Trend Micro uninstall and remnant remover tools to remove the antivirus and its components. Windows Defender turned itself on automatically.

    - I removed the Killer LAN drivers from Gigabyte and switched to the newer ones on Killer's support site.

    - I removed the Realtek drivers from Gigabyte and switched to the ones on the Realtek site linked.

    - My PC is a home build, so I installed the most recent WHQL drivers from NVIDIA's site (385.28) after a DDU uninstall, only installing the graphics and physX driver.

    I think that's everything on the list that I was able to complete, outside of the memtest issue mentioned above.
    Last edited by Brink; 20 Aug 2017 at 13:23. Reason: code box
      My Computer


  4. Posts : 41,472
    windows 10 professional version 1607 build 14393.969 64 bit
       #4

    Nice progress.
    Many of the mini dump files have indicated probable memory corruption.
    There were many dump files.
    The RAM / DIMM /Motherboard are important parts of the troubleshooting.
    Please repeat the Memtest86+ so that there are at least 8 passes. The more the better.
    The Memtest86+ will then enable you to rule in / rule out hardware (RAM /DIMM /MB) as potential causes of the bsods.
    Please use a camera or smart phone camera to take a picture and post an image into the thread.


    Code:
    Use !analyze -v to get detailed debugging information.BugCheck 3B, {c0000005, fffff801236fbe65, ffff9b812eaa4570, 0}Probably caused by : memory_corruption
    Code:
    BugCheck DA, {504, ffffc24c409c6f40, 0, 138de8}*** WARNING: Unable to verify timestamp for win32k.sys*** ERROR: Module load completed but symbols could not be loaded for win32k.sysProbably caused by : memory_corruption
    Code:
    BugCheck 50, {ffffd78577ad7d40, 0, fffff80350f91750, 2}Could not read faulting driver nameProbably caused by : memory_corruption


    Code:
    BugCheck A, {300001f88, 2, 0, fffff802de0ff047}*** WARNING: Unable to verify timestamp for MBfilt64.sys*** ERROR: Module load completed but symbols could not be loaded for MBfilt64.sys*** WARNING: Unable to verify timestamp for win32k.sys*** ERROR: Module load completed but symbols could not be loaded for win32k.sysProbably caused by : memory_corruption
    Code:
    BugCheck A, {200001f88, 2, 0, fffff8022f47c047}*** WARNING: Unable to verify timestamp for MBfilt64.sys*** ERROR: Module load completed but symbols could not be loaded for MBfilt64.sys*** WARNING: Unable to verify timestamp for win32k.sys*** ERROR: Module load completed but symbols could not be loaded for win32k.sysProbably caused by : memory_corruption
      My Computer


  5. Posts : 8
    Microsoft Windows 10 Home 64-bit 15063 Multiprocessor Free
    Thread Starter
       #5

    I ran Memtest again last night and was able to get through 8 passes this time.
    (Apologies for the swirly bits, camera phone autofocus.)

    Attachment 149862
      My Computer


  6. Posts : 41,472
    windows 10 professional version 1607 build 14393.969 64 bit
       #6

    Now use the computer under typical use for a few days to see if there is anything else of concern.
      My Computer


  7. Posts : 8
    Microsoft Windows 10 Home 64-bit 15063 Multiprocessor Free
    Thread Starter
       #7

    Had another BSOD, unfortunately. (Page fault in nonpaged area)
      My Computer


  8. Posts : 545
    seL4
       #8

    Looks like Killer Networking released a new driver update here:

    Downloads
      My Computer


  9. Posts : 41,472
    windows 10 professional version 1607 build 14393.969 64 bit
       #9

    There was 1 new bsod mini dump file debugged and this did not display a definitive misbehaving driver.
    There was an error in the event viewer from yesterday:

    cannot zero sectors on the disk

    Code:
    Event[3163]:  Log Name: System  Source: VDS Basic Provider  Date: 2017-08-20T16:15:20.444  Event ID: 5  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-0GN41V3  Description: Cannot zero sectors on disk \\?\PhysicalDrive2. Error code: 5@0101000F
    Was that related to a USB drive or using diskpart?

    Please fill out the system specifications:
    How To Fill Out Your System Specs

    How To Fill Out Your System Specs
    System Specs - Fill in at Ten Forums:

    System Specs - Fill in at Ten Forums Windows 10 General Tips Tutorials

    In the left corner below in your post you find 'My System Specs'.

    After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
    System Info - See Your System Specs - Windows 7 Help Forums

    In addition to the information in the links above please post information on: PSU, cooler, case, and peripherals: (mouse, keyboard, joystick, etc.)



    Windows driver verifer is a tool that is used to find misbehaving drivers.
    It will repetitively produce bsod until misbehaving drivers are fixed or until it is turned off.
    Each bsod should create a mini dump that can be debugged to find the misbehaving drivers.
    In order to use this tool you must know how to turn it off after each bsod and be able to return to the desktop to fix the misbehaving drivers.
    There are 3 methods and all of them are done through the windows recovery or advanced troubleshooting menu:
    1) startup options (not startup repair) > #6 safe mode with command prompt > type: verifier /reset
    2) command prompt > Administrator X:\Windows\system32\cmd.exe > type verifier /bootmode resetonbootfail
    3) restore
    The methods to turn off windows driver verifer should be done in the above order and only advance if the prior method fails to turn off the tool. The restore method leads to a loss of the bsod mini dump file and little progress is made in the troubleshooting.
    To practice the methods to turn off windows driver verifier open administrative command prompt by typing or copying and pasting: shutdown /r /o /f //t 00
    For each bsod there will be a stop code, typically driver verifier detected violation, and there may be a displayed misbehaving driver in the form *.sys. If you see the driver displayed please record it and post it into the thread.
    Use the instructions in this link to make sure you have time to view the bsod window by unchecking automatic restart:

    Microsoft Community

    After each bsod you will return to the desktop and run bluescreenview and whocrashed to find the misbehaving driver. Also post a new zip with each bsod so that we can guide you through the process:

    Blue screen of death (STOP error) information in dump files.
    http://www.resplendence.com/whocrashed
    BSOD - Posting Instructions - Windows 10 Forums

    Use the settings in this link to turn on and customize windows driver verifier:

    Microsoft Community

    Review the methods in this link to turn off windows driver verifier:
    Enable and Disable Driver Verifier in Windows 10 Windows 10 Performance Maintenance Tutorials

    Before turning on windows driver verifier make sure you perform the following steps:
    1) create a brand new restore
    2) backup all files
    3) create a backup image using Macrium:
    Macrium Software | Your Image is Everything
    4) save the image to another drive

    Also make sure that you are comfortable with the 3 methods to turn off windows driver verifier.

    Once all misbehaving drivers are fixed windows driver verifier will run for an additional 36 hours of normal computer use. If there are no more bsod then the troubleshooting and preventative maintenance will be completed.
      My Computer


  10. Posts : 8
    Microsoft Windows 10 Home 64-bit 15063 Multiprocessor Free
    Thread Starter
       #10

    "Cannot zero sectors on the disk": Was that related to a USB drive or using diskpart?
    - I did use diskpart to reclaim space on a USB drive. I ran the memtest+ tests using the automatic USB drive maker, and since the first test didn't run to completion, I wanted to try a newer drive for the second run. I tried to get the space back on my first drive, (It was only being recognized as 90MB usable) but I couldn't seem to touch the partitions on a USB with the Win10 Disk Management tool, so I used diskpart.

    System specs:
    I've filled them out with as much accuracy as I can recall, but the first "How To Fill Out Your System Specs" link gave me permission denied, so if there were additional instructions there, I may have missed them.

    Driver Verifier:
    Running verifier caused an immediate BSOD before even the windows login screen:

    IRQL_NOT_LESS_OR_EQUAL - Both bluescreenview and whocrashed point to "ntoskrnl.exe", but caution that it's likely another driver that can't be identified.

    Once I restarted from that, I was able to log into Win10 with verifier running, but after a minute or so it hit another BSOD:

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED - While bluescreenview points again to "ntoskrnl.exe", whocrashed this time blames "hidclass.sys", which it says is another Windows file and likely not the cause.

    Whocrashed also includes a 3rd entry that bluescreenview doesn't have:

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M - This once more points to "ntoskrnl.exe".
      My Computer


 

  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 22:49.
Find Us




Windows 10 Forums