BSOD, random, error 0x1A

  1. Posts : 1
    Windows 7 64 bit

    BSOD, random, error 0x1A


    I have a computer that gets a BSOD. It appears to be random. The only thing that I can think of that we did different at the time this started happening was plug in and install a Western Digital external hard drive. I have uploaded the dump files and system information for you to view.

    Thank you,

    Joshua Davis
      My Computer

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

    Welcome to the forum acog,

    I've checked 3 of your dumps generally and the bugchecks are the same in each of them.

    BugCheck 1A, {41790, fffffa80067fb6c0, ffff, 0} MEMORY_MANAGEMENT (1a)

    Please carry out the steps below:

    Reduce items at start-up. Nothing except anti-virus is required plus improves the time for logging in windows.


    Perform a clean boot:

    Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:
    • Click on the
    • Type CMD on Search
    • Left click and Run as Administrator
    • Type SFC /scannow

    Full tutorial here:

    Then 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.
    Errors are sometimes found after 8 passes.

    Memtest should be done overnight.

    Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Users\Yusra\Downloads\Compressed\debug-USLTEN03-Tue_07_01_2014_160701_03\070114-8829-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    Symbol search path is: SRV*c:\symbols*
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Machine Name:
    Kernel base = 0xfffff800`02206000 PsLoadedModuleList = 0xfffff800`02449890
    Debug session time: Tue Jul  1 21:00:01.271 2014 (UTC + 6:00)
    System Uptime: 0 days 2:33:48.494
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    Use !analyze -v to get detailed debugging information.
    BugCheck 1A, {41790, fffffa80067fb6c0, ffff, 0}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )
    Followup: MachineOwner
    4: kd> !analyze -v
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
        # Any other values for parameter 1 must be individually examined.
    Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
    	contains the address of the PFN for the corrupted page table page.
    	On a 32 bit OS, parameter 2 contains a pointer to the number of used
    	PTEs, and parameter 3 contains the number of used PTEs.
    Arg2: fffffa80067fb6c0
    Arg3: 000000000000ffff
    Arg4: 0000000000000000
    Debugging Details:
    BUGCHECK_STR:  0x1a_41790
    LAST_CONTROL_TRANSFER:  from fffff800022ecd50 to fffff8000227bbc0
    fffff880`24e736e8 fffff800`022ecd50 : 00000000`0000001a 00000000`00041790 fffffa80`067fb6c0 00000000`0000ffff : nt!KeBugCheckEx
    fffff880`24e736f0 fffff800`022ae7d9 : fffffa80`00000000 00000000`684effff fffffa80`00000000 fffff800`00000000 : nt! ?? ::FNODOBFM::`string'+0x35084
    fffff880`24e738b0 fffff800`025950f1 : fffffa80`10240bf0 00000000`00000000 fffffa80`0a90e340 fffffa80`0a90e340 : nt!MiRemoveMappedView+0xd9
    fffff880`24e739d0 fffff800`025954f3 : 00000000`00000000 00000000`67f70000 fffffa80`00000001 00000000`00001501 : nt!MiUnmapViewOfSection+0x1b1
    fffff880`24e73a90 fffff800`0227ae53 : fffffa80`131ce060 fffff880`24e73b60 fffffa80`12539640 00000000`5cbce610 : nt!NtUnmapViewOfSection+0x5f
    fffff880`24e73ae0 00000000`76da155a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`5cbce698 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76da155a
    nt! ?? ::FNODOBFM::`string'+35084
    fffff800`022ecd50 cc              int     3
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+35084
    FOLLOWUP_NAME:  MachineOwner
    IMAGE_NAME:  ntkrnlmp.exe
    FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35084
    BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35084
    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 21:10.
Find Us