BSOD ntoskrnl.exe +75bc0


  1. Posts : 3
    Windows 7 Ultimate x64 SP1
       #1

    BSOD ntoskrnl.exe +75bc0


    My system has been BSOD randomly for 3-4 months.
    Would be grateful if someone can help me. SF diagnostic log attached.
      My Computer


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

    Code:
    Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Usra\Downloads\SF_tompus\SF_24-01-2014\011114-18891-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\SymCache*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
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Machine Name:
    Kernel base = 0xfffff800`0320b000 PsLoadedModuleList = 0xfffff800`0344e6d0
    Debug session time: Sun Jan 12 02:24:40.453 2014 (UTC + 6:00)
    System Uptime: 0 days 9:54:44.857
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .........................
    Loading User Symbols
    Loading unloaded module list
    ............
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {fffff88007c0bd60, 0, fffff8000327fe5b, 0}
    
    
    Could not read faulting driver name
    Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+0 )
    
    Followup: MachineOwner
    ---------
    
    Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Usra\Downloads\SF_tompus\SF_24-01-2014\012414-17331-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\SymCache*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
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Machine Name:
    Kernel base = 0xfffff800`0325d000 PsLoadedModuleList = 0xfffff800`034a06d0
    Debug session time: Sat Jan 25 00:33:40.275 2014 (UTC + 6:00)
    System Uptime: 0 days 7:57:44.680
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ........................
    Loading User Symbols
    Loading unloaded module list
    ........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1A, {8886, fffffa8000d67ca0, fffffa8000581100, 205}
    
    Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+19c )
    
    Followup: MachineOwner
    ---------
    Start by taking Memtest.

    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.
      My Computer


  3. Posts : 3
    Windows 7 Ultimate x64 SP1
    Thread Starter
       #3

    Thanks koolkat77, I'll start memtest and send results.
      My Computer


  4. Posts : 3
    Windows 7 Ultimate x64 SP1
    Thread Starter
       #4

    Memtest86 did not show errors after 8 passes of all combinations of stick-slot, but after testing I changed slots of my RAM sticks, and I dont have BSOD.
    Now, I'm going to wait a few weeks and if I have a BSOD again, I'll answer to you.
    Thank you
      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 01:53.
Find Us