BSOD at random


  1. Posts : 1
    Windows 7 Ultimate x64
       #1

    BSOD at random


    I have been getting BSOD at random times at night and sometimes during gaming. I haven't had BSODs on this PC for a long time until about a month or two ago.

    Help will be greatly appreciated!

    Here is what comes up:

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.256.1
    Locale ID: 1033

    Additional information about the problem:
    BCCode: 4e
    BCP1: 0000000000000099
    BCP2: 000000000004463E
    BCP3: 0000000000000002
    BCP4: 0000000000044638
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 256_1

    Files that help describe the problem:
    C:\Windows\Minidump\120713-19687-01.dmp
    C:\Users\Jason\AppData\Local\Temp\WER-5423031-0.sysdata.xml
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

    The goal is to test all the RAM sticks and all the motherboard slots.

    Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

    If you get errors, stop the test and continue with the next step.

    1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
    *Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
    If this stick passes the test then go to step #3.

    2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
    *If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
    *If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
    3. Test the next stick of RAM (stick #2) in the next motherboard slot.
    *If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
    *If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
    4. If you find a stick that passes the test, test it in all the other motherboard slots.

    If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

    In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.
       Information
    Errors are sometimes found after 8 passes.

       Tip
    Do this test overnight, before going to bed.

    Code:
    Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\USER\Downloads\SF_07-12-2013 (1)\SF_07-12-2013\120713-19687-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
    Machine Name:
    Kernel base = 0xfffff800`03a51000 PsLoadedModuleList = 0xfffff800`03c8ee50
    Debug session time: Sun Dec  8 07:04:51.176 2013 (UTC + 6:00)
    System Uptime: 2 days 7:51:53.612
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...............................
    Loading User Symbols
    Loading unloaded module list
    ........................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 4E, {99, 4463e, 2, 44638}
    
    Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    PFN_LIST_CORRUPT (4e)
    Typically caused by drivers passing bad memory descriptor lists (ie: calling
    MmUnlockPages twice with the same list, etc).  If a kernel debugger is
    available get the stack trace.
    Arguments:
    Arg1: 0000000000000099, A PTE or PFN is corrupt
    Arg2: 000000000004463e, page frame number
    Arg3: 0000000000000002, current page state
    Arg4: 0000000000044638, 0
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x4E_99
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  dwm.exe
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff80003b5133c to fffff80003ac1700
    
    STACK_TEXT:  
    fffff880`07fef778 fffff800`03b5133c : 00000000`0000004e 00000000`00000099 00000000`0004463e 00000000`00000002 : nt!KeBugCheckEx
    fffff880`07fef780 fffff800`03b337b9 : 00000000`00000000 fffff680`000871c0 00000000`00000000 fffff700`010ddff8 : nt!MiBadShareCount+0x4c
    fffff880`07fef7c0 fffff800`03af2401 : 00000000`00000000 fffff680`00087ff8 fffffa80`0404bb30 00000000`000d3aba : nt! ?? ::FNODOBFM::`string'+0x31e93
    fffff880`07fef970 fffff800`03b0316a : 00000000`00000000 00000000`12c45fff fffffa80`00000000 fffffa80`0404bb30 : nt!MiDeleteVirtualAddresses+0x408
    fffff880`07fefb30 fffff800`03ac0953 : ffffffff`ffffffff 00000000`023ef120 00000000`023ef0e8 00000000`00008000 : nt!NtFreeVirtualMemory+0x5ca
    fffff880`07fefc20 00000000`76d5f89a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`023ef058 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d5f89a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiBadShareCount+4c
    fffff800`03b5133c cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!MiBadShareCount+4c
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd34
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
    
    BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
    
    Followup: MachineOwner
    ---------
      My Computer


 

  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 03:36.
Find Us