Multiple BSOD errors, Unknown Cause

Page 2 of 6 FirstFirst 1234 ... LastLast

  1. Posts : 32
    Windows 7 Ultimate x64
    Thread Starter
       #11

    so I don't know if these contain the newest minidmp files. I just went into the folder through ubuntu and copied them over.

    As for the bad slot theory, I tried running on a single stick but kept getting errors, no matter which stick I used or what slot I used...

    If I can get back into windows I will update the GeForce Driver.

    Again, thanks for the help.
      My Computer


  2. Posts : 32
    Windows 7 Ultimate x64
    Thread Starter
       #12

    okay, I got windows to boot again. In bios I have the options of AHCI or compatability mode for the sata controller. I swear its always been the AHCI setting, but changing it to compatability mode allowed windows to start.

    Would you suggest staying away from the newer bios, or should I reflash it and try with the new sata settings?
      My Computer


  3. Posts : 3,056
    Windows 10
       #13

    Flashing the BIOS is like heart surgery and its best to avoid when possible.
    I am away from my computer at the moment so I will look more into it when I can.
      My Computer


  4. Posts : 32
    Windows 7 Ultimate x64
    Thread Starter
       #14

    I am down to a single stick of RAM that I know is good in a single slot. Just had a crash in which the MOBO stopped recognizing that slot. I have now switched the ram over to the other slot and am waiting to see what will happen. The crash data went to the full memory dump, which I am not sure how to upload due to its size (66mb compressed).

    Let me know how, and I will attach it.
      My Computer


  5. Posts : 3,056
    Windows 10
       #15

    jeffpkamp said:
    I am down to a single stick of RAM that I know is good in a single slot. Just had a crash in which the MOBO stopped recognizing that slot. I have now switched the ram over to the other slot and am waiting to see what will happen. The crash data went to the full memory dump, which I am not sure how to upload due to its size (66mb compressed).

    Let me know how, and I will attach it.
    How did you determine that RAM module is good?
    How many passes did you run it?
    When was the last time you've checked it?
    You can attach it to your skydrive or something similar
    Last edited by YoYo155; 05 Aug 2013 at 16:44.
      My Computer


  6. Posts : 32
    Windows 7 Ultimate x64
    Thread Starter
       #16

    This is a stick from a laptop that has never given me trouble in 2+ years. I also tested it 10+ cycles with Memtest86+, no errors were found.

    here is the link for the memory dump. So far no crash using slot #2.

    https://skydrive.live.com/redir?resi...HJqkOa5qCE3zjs
      My Computer


  7. Posts : 3,056
    Windows 10
       #17

    The MEMORY.DMP:
    Code:
    **************************************************************************
    THIS DUMP FILE IS PARTIALLY CORRUPT.
    KdDebuggerDataBlock is not present or unreadable.
    **************************************************************************
    Unable to read PsLoadedModuleList
    **************************************************************************
    THIS DUMP FILE IS PARTIALLY CORRUPT.
    KdDebuggerDataBlock is not present or unreadable.
    **************************************************************************
    KdDebuggerData.KernBase < SystemRangeStart
    Windows 7 Kernel Version 7601 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0x00000000`00000000 PsLoadedModuleList = 0xfffff800`032a5670
    Debug session time: Mon Aug  5 23:16:56.499 2013 (UTC + 3:00)
    System Uptime: 0 days 0:53:48.919
    **************************************************************************
    THIS DUMP FILE IS PARTIALLY CORRUPT.
    KdDebuggerDataBlock is not present or unreadable.
    **************************************************************************
    Unable to read PsLoadedModuleList
    **************************************************************************
    THIS DUMP FILE IS PARTIALLY CORRUPT.
    KdDebuggerDataBlock is not present or unreadable.
    **************************************************************************
    KdDebuggerData.KernBase < SystemRangeStart
    Loading Kernel Symbols
    Unable to read PsLoadedModuleList
    GetContextState failed, 0xD0000147
    CS descriptor lookup failed
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    Unable to get program counter
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    Code:
     !error 0xC0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    Unable to get program counter
    Error code: (NTSTATUS) 0xc0000147 (3221225799) - {No Paging File Specified}  No paging file was specified in the system configuration.
    Make sure of this | Dump Files - Configure Windows to Create on BSOD

    Reset your Page File:

    1. Start Menu> Run >type control.exe system
    and press the Enter key.
    A windows will open and on the Left hand side you will see Advanced system settings, click it.



    2.
    Next click on the Advanced tab and Settings which correspond to the Performance section;



    3. Then the Advanced tab once more and click on the Change button;



    4. Untick the checkbox next to Automatically manage paging file size for all drives;



    5. Select No paging file and Click on the Set button;


    6. Confirm all the windows.

    7.
    Restart the PC.

    8. Reverse the procedure, by following steps 1-3, only this time select System managed size
    and click the Set button;



    9. Recheck the box next to Automatically manage paging file size for all drives
    and exit the windows by clicking the OK button;



    10. Confirm all of the remaining windows by click the OK button
    and restart once again to take affect.
    Last edited by YoYo155; 28 Sep 2013 at 13:58.
      My Computer


  8. Posts : 32
    Windows 7 Ultimate x64
    Thread Starter
       #18

    okay, I reset the page file. Also have a symptom that might suggest that this is actually a mother board issue. Sometmes when I start up the computer, it will get past bios and post "No Operating System Detected". If I reset it, it goes away, but that makes me think that it's more than memory or drivers causing this problem.
      My Computer


  9. Posts : 3,056
    Windows 10
       #19

    jeffpkamp said:
    okay, I reset the page file. Also have a symptom that might suggest that this is actually a mother board issue. Sometmes when I start up the computer, it will get past bios and post "No Operating System Detected". If I reset it, it goes away, but that makes me think that it's more than memory or drivers causing this problem.
    Have you had any issues since switching to one RAM slot?

    P.S. after resetting the page file, activating it the 2nd time don't forget to restart the PC again to take affect!
      My Computer


  10. Posts : 32
    Windows 7 Ultimate x64
    Thread Starter
       #20

    i might have... I started my computer this morning after turning off the paging, and when I came back it was off (or at least the power was on, but the computer was not, much like it does after a BSOD sometimes), but Paging was off, so if it did, it left no record of it, and since I didn't catch it in the act, I can't say for sure .

    I"ll let you know if it does it again now that I turned paging on and reset the computer.
      My Computer


 
Page 2 of 6 FirstFirst 1234 ... 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 16:43.
Find Us