Varios BSOD errors - Crash at any point Solved

Page 1 of 5 123 ... LastLast

  1. Posts : 26
    Microsoft Windows 10 Pro N 64-bit (17134 Multiprocessor Free)
       #1

    Varios BSOD errors - Crash at any point


    Hi everyone

    I have had various BSOD errors over the past few weeks, occurring multiple times a day, I've just about had enough of it.

    I believe these BSOD errors started occurring when I updated to the August Windows 10 patch. I tried to complete a system restore, but had no success. Either a BSOD or an error would appear.

    I have tried running each stick of RAM individually, still had BSOD's. Also used Windows Memory Diagnostic, all ok. I have also checked my SSD, which has my OS on, using SanDisk software, and it shows it's health as normal. I have also tried various command prompts; SFC Scan, Health check, are there any others that you would advise doing?

    As I had my files backed up, I decided to do a clean reboot of Windows 10 OS - Pro N. So right now I still have these BSOD's at sporadic times (I haven't noticed a pattern).

    Have uploaded a zip, post reboot.

    Any help would be greatly appreciated, so I can get back to gaming!

    Thanks,

    Wild Fires
      My ComputerSystem Spec

  2. Ztruker's Avatar
    Posts : 8,473
    Windows 10 Pro X64 1903 189362.439
       #2

    Hi Wild Fires, welcome to tenforums.

    First thing I see is you have a G19s Gaming Keyboard but the drivers for it are not installed. Don't know if that matters yet but something to think about.

    Also see your BIOS is down level, version 2.70 dated 06/11/2014 is available. You have version 2.00 dated 15/10/2012.

    Your Nvidia driver is also down level. You have version 388.13 dated 27/10/2017. Version 399.07 dated 27/08/2018 is available.

    The eventlog.txt file has thousands of these:
    Code:
    Event[821]:
      Log Name: System
      Source: Ntfs
      Date: 2018-08-28T17:59:30.889
      Event ID: 134
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-0TAR8SA
      Description: 
    The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
    This post from 2014 should still apply, even though it was for Windows 7 as the file system is the same.

    Karthik Vengaloor - This issue occurs if the Windows file system transaction log is corrupted. The Windows file system uses the transaction log to recover system transactions when a file error occurs.The Common Log File System (CLFS) transaction logs may be left in an inconsistent state. When the CLFS transaction logs are in an inconsistent state.
    To resolve this problem, delete the .blf files and the .regtrans-ms files from the %Windir%\System32\SMI\Store\Machine folder.

    After you restart the computer, the registry regenerates the deleted files. These regenerated files are in a consistent state.

    a. Press Windows key+X and select Command prompt(Admin).
    b. At command prompt, type the following command, and then press ENTER:

    fsutil resource setautoreset true c:\

    Note
    These steps assume that Windows is installed in the default location, on drive C. If this is not the case, adjust the drive letter of the folder path to match your configuration.
    c. Restart the computer.
    Above posted here: https://answers.microsoft.com/en-us/...d-89730e593710
      My ComputersSystem Spec


  3. Posts : 26
    Microsoft Windows 10 Pro N 64-bit (17134 Multiprocessor Free)
    Thread Starter
       #3

    Hi Ztruker,

    Thanks for the help! I'll try all of this later, and let you know how I get on.

    Wild Fires
      My ComputerSystem Spec


  4. Posts : 26
    Microsoft Windows 10 Pro N 64-bit (17134 Multiprocessor Free)
    Thread Starter
       #4

    Hi Ztruker,

    Everything is up to date, and I have gone through that process. But unfortunately I'm still receiving the BSOD's.

    I have had to replace my keyboard is. It has a separate issue, not through anger fortunately!

    I have attached my zip.

    Thanks again,

    Wild Fires
      My ComputerSystem Spec

  5. Ztruker's Avatar
    Posts : 8,473
    Windows 10 Pro X64 1903 189362.439
       #5

    I don't see any new resource manager problems, so that's good. Nvidia driver looks good and up to date as does the BIOS.

    You had 16 BSODs on the 30th, here is a list of most of them:
    Code:
    2018-08-30T17:03:53.476  0x0000001e
    2018-08-30T17:15:24.470  0x0000001e
    2018-08-30T17:39:47.561  0x000000da
    2018-08-30T17:58:32.843  0x0000000a
    2018-08-30T18:25:11.003  0x00000101
    2018-08-30T18:42:23.866  0x0000003b
    2018-08-30T19:00:38.736  0x0000003b
    2018-08-30T19:37:04.656  0x000000d1
    2018-08-30T19:48:08.001  0x000000f7
    2018-08-30T20:03:33.371  0x0000000a
    2018-08-30T20:09:32.677  0x0000000a
    2018-08-30T20:20:36.922  0x0000000a
    As you can see there are 6 different crash codes. The dumps I looked at all point to Windows drivers which doesn't help as they are not at all likely to be the cause. Something else if triggering this.

    Let's start by doing a Clean Boot, see if that gets rid of the BSODs. If yes then that is pretty conclusive that it's a non-Microsoft device driver problem and the way to resolve it is to enable them a few at a time until the BSODs start occurring again. Once we know what driver/device is the cause we can see how to fix it.

    See here: How to Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts

    If that doesn't identify the cause the next step is to enable Driver Verifier to try and force a device driver error, as follows:
    ===================================================
    Driver Verifier
    is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
    Machines exposed to Driver Verifier may run very sluggishly due to the stress being applied to the drivers.

    Driver Verifier - Enable and Disable in Windows 10

    Pay close attention to PART TWO and make sure the correct boxes are checked.

    Warning:
    It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

    Always create a Restore Point prior to enabling Driver Verifier so you have a way to recover if it goes haywire. Seldom does but it can happen.

    What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the log collector and upload the resulting zip file.

    One other thing I'd like you to do is use the v2-Beta12 collector listed at the bottom of the BSOD posting instructions link. It collects additional info that may be helpful in figuring this problem out. Run it now and upload the zip then use it from now on instead of the dm_log_collector.exe.
      My ComputersSystem Spec


  6. Posts : 26
    Microsoft Windows 10 Pro N 64-bit (17134 Multiprocessor Free)
    Thread Starter
       #6

    Ok I've created a new zip using the V2-Beta log.

    Attached below :)
      My ComputerSystem Spec



  7. Posts : 26
    Microsoft Windows 10 Pro N 64-bit (17134 Multiprocessor Free)
    Thread Starter
       #7

    I completed the Clean Boot, removed any non-Microsoft processes. But I'm still receiving BSOD's.

    I am currently using driver verifier, will post zip when I receive next BSOD.
      My ComputerSystem Spec


  8. Posts : 26
    Microsoft Windows 10 Pro N 64-bit (17134 Multiprocessor Free)
    Thread Starter
       #8

    Here's the latest zip.
      My ComputerSystem Spec

  9. Ztruker's Avatar
    Posts : 8,473
    Windows 10 Pro X64 1903 189362.439
       #9

    Not too hopeful of Driver Verifier showing anything then as Clean Boot didn't improve things. Time will tell.
      My ComputersSystem Spec


  10. Posts : 26
    Microsoft Windows 10 Pro N 64-bit (17134 Multiprocessor Free)
    Thread Starter
       #10

    Ok, so should i continue to use clean boot for the time being?
      My ComputerSystem Spec


 
Page 1 of 5 123 ... LastLast

Related Threads
Hi, I am very tired, afraid and angry. Today I was surfing with Edge and I encouter a web page with a loopy popup that want to make me win an Apple iPhone. Trying to closing that pop-op it will reopen again and my Edge starts with the...
This PC runs fine most of the time, but often, as many as 2 or 3 times a day it can crash. Many times it just powers off, however it sometimes shows a BSOD," MEMORY_MANAGEMENT 0x0000001a 00000000`00000403 ...
Solved chkdsk reparse point errors - repeatedly in Performance & Maintenance
Hello, Does anyone have experience of repeated 'extended attribute set and a reparse point detected in file xxxxx'errors in chkdsk in windows 10? - even though it apparently corrects the errors with 'deleting extended attribute set due to...
Ok . I am getting random system lockups, can happen anytime. Sometimes using when using chrome or just on desktop. Happens most often when windows is on login screen, or sometime right before windows loads. Playing any game I have will cause crash...
Hi Y'all. Ok. I've been having the BSoD with multiple errors causing the crashes. May 31st: NETIO.SYS Jun 2nd: CNG.SYS Jun 3rd: WMILIB.SYS Jun 6th: NTFS.SYS I have dmp files for all 3 crashes if requested.
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 06:18.
Find Us