Multiple BSOD, Different Error Each Time


  1. Posts : 1
    Windows 7 Home Premium 64bit
       #1

    Multiple BSOD, Different Error Each Time


    I've been experiencing BSOD for a while now they seem to frequent when I play certain video games (mainly League of Legends & Guild Wars 2) and sometimes when I'm viewing YouTube. Its gotten to the point where my computer is bound to blue screen whenever I start one of these games.

    I'll upload the dump files using the recommended SF Diagnostic Tool.
      My Computer


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

    Welcome to the forum.

    Code:
    
    Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\admin\Downloads\pokemn7\SF_29-10-2014\102914-48609-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 7601 (Service Pack 1) MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Machine Name:
    Kernel base = 0xfffff800`02c54000 PsLoadedModuleList = 0xfffff800`02e97890
    Debug session time: Wed Oct 29 04:51:24.749 2014 (UTC + 6:00)
    System Uptime: 0 days 0:08:04.450
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .............................................
    Loading User Symbols
    Loading unloaded module list
    ........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1A, {5001, fffff70001080000, 3ad00, fffff6800006a009}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2924c )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000005001, The subtype of the bugcheck.
    Arg2: fffff70001080000
    Arg3: 000000000003ad00
    Arg4: fffff6800006a009
    
    Debugging Details:
    ------------------
    
    
    OVERLAPPED_MODULE: Address regions for 'nwifi' and 'WinUsb.sys' overlap
    
    BUGCHECK_STR:  0x1a_5001
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  Gw2.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff80002d31f2a to fffff80002cc9bc0
    
    STACK_TEXT:  
    fffff880`07ad2888 fffff800`02d31f2a : 00000000`0000001a 00000000`00005001 fffff700`01080000 00000000`0003ad00 : nt!KeBugCheckEx
    fffff880`07ad2890 fffff800`02ce79df : 50500000`a5d87025 00000000`a5d72121 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x2924c
    fffff880`07ad2920 fffff800`02ce64f3 : 00000000`000a69a1 00000000`76dd9770 fffff680`003b6ec8 fffffa80`06aa0ec8 : nt!MiResolveProtoPteFault+0x1cf
    fffff880`07ad29b0 fffff800`02cd6179 : 00000000`00000000 00000000`76dd9770 fffffa80`0670f060 00000000`00000000 : nt!MiDispatchFault+0x1c3
    fffff880`07ad2ac0 fffff800`02cc7cee : 00000000`00000008 00000000`76dd9770 00000000`00000401 00000000`063fdc50 : nt!MmAccessFault+0x359
    fffff880`07ad2c20 00000000`76dd9770 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
    00000000`063fd778 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76dd9770
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+2924c
    fffff800`02d31f2a cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+2924c
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  531590fb
    
    FAILURE_BUCKET_ID:  X64_0x1a_5001_nt!_??_::FNODOBFM::_string_+2924c
    
    BUCKET_ID:  X64_0x1a_5001_nt!_??_::FNODOBFM::_string_+2924c
    
    Followup: MachineOwner
    ---------
    
    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
    Memtest should be done overnight.
      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 16:35.
Find Us