BSOD while using more memory-intensive programs

Page 3 of 3 FirstFirst 123

  1. Posts : 16
    Windows 7 Ultimate 64-bit
    Thread Starter
       #21

    More BSOD's, this time 2 in a row. Windows went to start-up repair, but was unable to fix the problem. Both didn't create a mini-dump file, just a corrupt 'Memory' dump under Windows folder again. Only useful info I found was that the stop was 0x3b. Not sure if using dm log will be useful.
      My Computer


  2. Posts : 25,847
    Windows 10 Pro. 64/ version 1709 Windows 7 Pro/64
       #22

    Anytime you get a BSOD posting the logs can be very useful.

    Your BSOD team need those logs.
      My Computer


  3. Posts : 16
    Windows 7 Ultimate 64-bit
    Thread Starter
       #23

    Layback Bear,

    Thanks for the reply. I apologize for the presumption. As a precaution, I did the elevated command prompts again for WinDBg, to make sure it's associated. I'm including the latest DM log, hopefully it is helpful.

    I don't want to confuse the issue, but there are some things about my RAM concern me. Taking a look at the Asus Qualified Vendor List (see attached), I don't show that CMZ8GX3M2A1600C9B is on there. In addition, even though I have it set to 1600 mHz, and voltage to 1.5v via BIOS (timing is displayed correctly), Speccy lists the DRAM frequency @ 800 mHz. I've included a snapshot text file for Speccy for consideration.

    At this point I'd like to give as much information as possible, since the stop errors aren't consistent. I am theorizing that if it isn't a driver-related crash, then either the RAM, motherboard, or the GTX 560 are hardware issues.
      My Computer


  4. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #24

    The last two logs haven't included any new dumps unfortunately. Can you follow these instructions to check if you are set to record memory dumps:

    1. Open Advanced System Settings
    2. Click on Settings in Startup & Recovery
    3. Make sure both boxes indicated below are checked
    4. In the dropdown box ensure you're set to record Small Memory Dumps

      My Computer


  5. Posts : 16
    Windows 7 Ultimate 64-bit
    Thread Starter
       #25

    Boozad,

    Ok, done. It was not set for small memory dumps for some reason. I don't know why it changed. I assume we need new BSOD's since the log didn't catch these others. Seems if I use more GPU-intensive programs the BSOD's occur, but 'correlation is not causation' as it were. I'll post a new DM log if I get some more recent ones.
      My Computer


  6. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #26

    Excellent, at least we know you're set to catch them now.
      My Computer


  7. Posts : 16
    Windows 7 Ultimate 64-bit
    Thread Starter
       #27

    I was able to get another BSOD, and it looks like it created a viable mini dump. I've attached it below.
      My Computer


  8. Posts : 16
    Windows 7 Ultimate 64-bit
    Thread Starter
       #28

    Well, two in a row while playing games. Note the first one was Star Trek Online, second one was Left 4 Dead 2. I'm going to include a new log with just those two mini-dumps, so ignore that last attachment.
      My Computer


  9. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #29

    I'll get to these tonight after work.
      My Computer


 
Page 3 of 3 FirstFirst 123

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

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