BSOD crashes in random intervals

Page 1 of 2 12 LastLast

  1. Posts : 9
    Windows 10

    BSOD crashes in random intervals

    Throughout the day my computer will BSOD each time it will say a different reason and I will be doing something completely different each time. Sometimes I am gaming, watching live streams, or absolutely nothing. Thanks in advance for any help you guys give me.
    Last edited by brentsky96; 31 May 2016 at 10:37.
      My Computer

  2. Posts : 14,050
    Windows 11 Pro X64 22H2 22621.1848

    The zip file contains only a file called Debug-Brent-PC-05_30_2016.

    Please run DM Log collector again but run it as Administrator this time, see if that gives us better data. To do this right click on dm_log_collector.exe and select Run as Administrator.

    Upload the new zip file here. Check it first, it should contain of 21 files.
      My Computers

  3. Posts : 9
    Windows 10
    Thread Starter

    There we go, that attachment should work now. Also thank you for replying :)
      My Computer

  4. Posts : 14,050
    Windows 11 Pro X64 22H2 22621.1848

    Much better, thanks.

    Dumps indicate Memory corruption. Most often that indicates defective RAM.

    Download Memtest86+ (you want the 2nd one Download - Pre-Compiled Bootable ISO (.zip)). Unzip it then create a CD from the iso file using your CD burning software. There is a good freeware burner called ImgBurn which will do this easily.

    DO NOT burn the .iso file directly to CD. It must be used as input to a program that knows what to do with it, like the one I mentioned above.

    You can do this on any computer that has a working CD Burner.

    You can also use a Flash drive instead of a CD.

    Download - Auto-installer for USB Key (Win 9x/2k/xp/7) *NEW!*.
    Unzip and run Memtest86+ USB Installer.exe.
    It will format the flash drive if you tell it to. I used a small, 16MB flash drive and it had 8.5GB left when done.

    Boot the CD or Flash drive and run Memtest86+ for at least 3 complete passes (unless it shows errors sooner than that. An overnight run is much better.

    A couple of the dumps had this in it:

    *** WARNING: Unable to verify timestamp for avgwfpa.sys
    *** ERROR: Module load completed but symbols could not be loaded for avgwfpa.sys
    Try uninstalling AVG and running with the built-in Windows Defender (that's what I use) for awhile, see if that makes a difference.
      My Computers

  5. Posts : 9
    Windows 10
    Thread Starter

    Yeah I found out about AVG and already uninstalled it. But thank you I will run memtest and post the results when done.
      My Computer

  6. Posts : 9
    Windows 10
    Thread Starter

    Okay so when I woke up this morning, memtest was on Pass: 5 with no errors found.
      My Computer

  7. Posts : 14,050
    Windows 11 Pro X64 22H2 22621.1848

    Have you had a problem since you ubninstalled AVG? If not, wait and see if you get one. If so, run DM Log collector again and post the zip here pleaase.
      My Computers

  8. Posts : 9
    Windows 10
    Thread Starter

    No actually it appears they are getting worse. During one of the blue screens, after my pc restarted, it brought up the windows icon with text at the bottom saying "Preparing PC Diagnosis" after that a blue screen came up saying "Windows did not start correctly" and gave me some options. I chose to restart my pc and after a couple loops of this, I was able to get my computer to start properly and that was right before I am typing this. Here is the latest DM logs.
    Last edited by brentsky96; 02 Jun 2016 at 07:40. Reason: DM Log file was empty
      My Computer

  9. Posts : 9
    Windows 10
    Thread Starter

    Have had a couple more BSODs since my last zip file. Here is an updated one
      My Computer

  10. Posts : 14,050
    Windows 11 Pro X64 22H2 22621.1848

    Nothing new in the dumps, memory corruption or ntkrnlmp, same as previously.

    Time to try Driver Verifier.

    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 will run very sluggishly due to the stress being applied to the drivers.

    Driver Verifier - Enable and Disable in Windows 10

    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.

    Let's see if that kicks out a problem driver.

    Also, please fill in your System Specs:

    How to fill out System Specs for tenforums.

    See here: System Specs - Fill in at Ten Forums
      My Computers


  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 06:48.
Find Us

Windows 10 Forums