locked
Multiple BSOD stops referencing ntoskrnl.exe RRS feed

  • Question

  • I have been encountering numerous BSOD stops.   The Bug Check String is different almost every time:

    UNEXPECTED_KERNEL_MODE_TRAP
    MEMORY_MANAGEMENT
    SYSTEM_SERVICE_EXCEPTION
    IRQL_NOT_LESS_OR_EQUAL
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
    ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY

    ETC.

    The only similarity in BlueScreenView is the reference to ntoskrnl.exe

    The crashes occur seemingly at random and  I cannot reproduce a BSOD voluntarily. Nor can I point to any one particular thing I'm doing when it happens.

    System Specs:

    Intel Core i7-3770K Ivy Bridge 3.5GHz LGA 1155 77W Quad-Core Desktop Processor
    ASUS SABERTOOTH Z77 LGA 1155 Intel Z77 Motherboard
    GeForce GTX 660 Graphics Card
    OCZ 512GB Vertex 4 SSD
    Windows 8

    I'm running the latest Mobo Bios and nVidia drivers.  I've tested my RAM with memtest, and removed a stick had some issues- still getting BSODs.

    minidump files:

    https://skydrive.live.com/redir?resid=84236C19C114AF53!127&authkey=!AIMnA7rbLOU7AL8

    https://skydrive.live.com/redir?resid=84236C19C114AF53!125&authkey=!AHpEbIa0kpvL0Us

    https://skydrive.live.com/redir?resid=84236C19C114AF53!128&authkey=!AF7KtBQPbC1WaCc

    https://skydrive.live.com/redir?resid=84236C19C114AF53!124&authkey=!ANV9qw5OngK9ICY

    BlueScreenView Screenshot:

    https://skydrive.live.com/redir?resid=84236C19C114AF53!126&authkey=!AE4Fcj_PrjI1_Tg

    Thanks in advance

    Monday, July 29, 2013 6:07 PM

Answers

  • ok, you use a XPM profile which can cause issues. Use the 800MHz RAM speed. Go into the BIOS/UEFI and change the speed there.

    "A programmer is just a tool which converts caffeine into code"

    • Proposed as answer by Cloud_TS Wednesday, July 31, 2013 7:38 AM
    • Marked as answer by Cloud_TS Monday, August 5, 2013 1:45 PM
    Tuesday, July 30, 2013 5:31 AM
    Answerer

All replies

  • it still looks like a RAM related issue:

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    CRITICAL_STRUCTURE_CORRUPTION (109)
    This bugcheck is generated when the kernel detects that critical kernel code or
    data have been corrupted. There are generally three causes for a corruption:
    1) A driver has inadvertently or deliberately modified critical kernel code
     or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
    2) A developer attempted to set a normal kernel breakpoint using a kernel
     debugger that was not attached when the system was booted. Normal breakpoints,
     "bp", can only be set if the debugger is attached at boot time. Hardware
     breakpoints, "ba", can be set at any time.
    3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
    Arguments:
    Arg1: a3a039d8a4be37bc, Reserved
    Arg2: b3b7465ef73b37a4, Reserved
    Arg3: fffff8038715c041, Failure type dependent information
    Arg4: 0000000000000001, Type of corrupted region, can be
    	0 : A generic data region
    	1 : Modification of a function or .pdata
    	2 : A processor IDT
    	3 : A processor GDT
    	4 : Type 1 process list corruption
    	5 : Type 2 process list corruption
    	6 : Debug routine modification
    	7 : Critical MSR modification
    
    Debugging Details:
    ------------------
    
    
    PG_MISMATCH:  10000000
    
    MEMORY_CORRUPTOR:  ONE_BIT
    
    FAULTING_IP: 
    nt! ?? ::FNODOBFM::`string'+2bfd4
    fffff803`8715c041 ba01000000      mov     edx,1
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    BUGCHECK_STR:  0x109
    
    PROCESS_NAME:  csrss.exe
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 6.3.9431.0 (debuggers(dbg).130615-1214) amd64fre
    
    STACK_TEXT:  
    nt!KeBugCheckEx
    
    
    FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
    
    BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:memory_corruption_one_bit
    

    If the memtest tells no error, please download CPU-Z [1], look in the memory and SPD tab and verify that the current RAM Speed and the Timings match to the values that you see in the SPD tab. If your RAM run at CR (Command Rate) 1T, change the value into 2T in the BIOS/UEFI.

    André


    [1] http://www.cpuid.com/softwares/cpu-z.html


    "A programmer is just a tool which converts caffeine into code"

    Monday, July 29, 2013 7:01 PM
    Answerer
  • André,

    Thank you so much for your help.

    I installed CPU-Z, here are the memory specs. (Screen Shots)

    If you wouldn't mind helping me decode this info...

    Memory:

    https://skydrive.live.com/redir?resid=84236C19C114AF53!129&authkey=!ALi_IVoRChZ8Xfk

    SPD:

    https://skydrive.live.com/redir?resid=84236C19C114AF53!130&authkey=!ACXU636mk0CSOrc

    Monday, July 29, 2013 7:24 PM
  • ok, you use a XPM profile which can cause issues. Use the 800MHz RAM speed. Go into the BIOS/UEFI and change the speed there.

    "A programmer is just a tool which converts caffeine into code"

    • Proposed as answer by Cloud_TS Wednesday, July 31, 2013 7:38 AM
    • Marked as answer by Cloud_TS Monday, August 5, 2013 1:45 PM
    Tuesday, July 30, 2013 5:31 AM
    Answerer