Random BSODs nolonger generating dump files

Page 1 of 2 12 LastLast

  1. Posts : 17
    windows 7 home premium 64bit
       #1

    Random BSODs nolonger generating dump files


    Computer stopped generating minidumps but have had numerous BSODs. I have followed the instructions on this site to make sure that PC is configured for minidumps. I have also run chkdsk command with repair and SFC /scannow. I have also run Kaperskys and malwarebytes rootkit virus detectors. Both came back clean. Most pressing need is to be able to generate dump files so that someone help to determine what is causing BSODs. I have attached the file from the dmg collector and also the results from a SFC /scannow. Any help would be appreciated.
      My Computer


  2. Posts : 7,050
    Windows 10 Pro
       #2

    Please make sure your pc is configured for small dump files How to configure minidump | Windows 7 tutorial

    We need at least a picture of the BSOD to see what kind we're dealing with, please make sure you get some pictures of the BSODs and post them.
      My Computer


  3. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #3

    The 16 GB Micron RAM ... was it there from the beginning, or you added it latter?

    Test your RAM modules for possible errors. Run memtest86+ for at least 8 consecutive passes.

    If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

    Let us see a camera snap of the Memtest86+ screen before closing the program.
      My Computer


  4. Posts : 17
    windows 7 home premium 64bit
    Thread Starter
       #4

    Minidump settings


    I have attached screenshot of minidump settings. I believe these have always been the settings on my PC.Attachment 386189
      My Computer


  5. Posts : 17
    windows 7 home premium 64bit
    Thread Starter
       #5

    My PC originally had 8GB of memory. I added the additional memory about 2 years ago. I will run the memtest86+ tonight. Thanks.
      My Computer


  6. Posts : 7,050
    Windows 10 Pro
       #6

    Until the problem of no dump is solved, please uncheck 'Automatically restart' so you have enough time to get a photo and see if any problem occurs while the dump is being created + saved.
      My Computer


  7. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #7

    Dump is not being recorded, most probably because of it.
    2/24/2016 2:20 PM
    Windows Error Reporting Fault bucket BAD_DUMPFILE,
    type 0

    Event Name: BlueScreen
    But when the last known BSODs are

    • 2/24/2016 2:20 PM Windows Error Reporting Fault bucket X64_0x3B
    • 2/24/2016 2:19 PM Windows Error Reporting Fault bucket X64_0x24

    I see no good reason to not perform the RAM test.
      My Computer


  8. Posts : 17
    windows 7 home premium 64bit
    Thread Starter
       #8

    Attachment 386277
    Here is a camera shot of the memtest86 that I ran last night. Clearly some type of RAM problem. Not sure of what to do next. I do have the original RAM sticks that came with the PC.
      My Computer


  9. Posts : 7,050
    Windows 10 Pro
       #9

    Here is what to do.
    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.
      My Computer


  10. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #10

    Now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

    Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

    How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
    How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:
    No code has to be inserted here.
    It is a RAM, a bad RAM.

    But if you have got a result like that:
    No code has to be inserted here.
    It is a motherboard issue. The particular slot is bad.

    If it is a bad RAM, you need to change the RAM. Take the other existing (good) RAM to the shop and get one of the exactly same specification. The best is, get a totally new RAM KIT.

    If it is a bad slot, it is a motherboard issue. But changing the motherboard needs a preparation for most of us; so dont populate that slot for the time being.
      My Computer


 
Page 1 of 2 12 LastLast

  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 18:19.
Find Us