BSOD due to ntoskrnl.exe?


  1. Posts : 17
    Windows 7 64 Professional
       #1

    BSOD due to ntoskrnl.exe?


    I get blue screens at least once a day. Sitill unknown. I ran memtest and prime95 last month with no errors. BlueScreenView shows ntoskrnl on a few of the crashes.

    Any help would be greatly appreciated.

    Thanks.
    Geoffrey
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    gweglarz said:
    I get blue screens at least once a day. Sitill unknown. I ran memtest and prime95 last month with no errors. BlueScreenView shows ntoskrnl on a few of the crashes.

    Any help would be greatly appreciated.

    Thanks.
    Geoffrey
    These are caused by several things all of which pointing to hardware.

    I would re-run memtest for the proscribed 6-7 passes. One stick at a time, and test the mobo slots with known good ram.

    Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.


    Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\102910-31465-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;srv*e:\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.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`03016000 PsLoadedModuleList = 0xfffff800`03253e50
    Debug session time: Fri Oct 29 14:04:30.772 2010 (GMT-4)
    System Uptime: 1 days 0:18:44.739
    Loading Kernel Symbols
    .
    
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    
    ..............................................................
    ................................................................
    .......................................................
    Loading User Symbols
    Loading unloaded module list
    .......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {fffffa7fffffffd8, 2, 1, fffff800030a73a4}
    
    Probably caused by : memory_corruption ( nt!MiUnlinkFreeOrZeroedPage+1ca )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: fffffa7fffffffd8, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff800030a73a4, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032be0e0
     fffffa7fffffffd8 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!MiUnlinkFreeOrZeroedPage+1ca
    fffff800`030a73a4 48893cc2        mov     qword ptr [rdx+rax*8],rdi
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  fffff880009a9a10 -- (.trap 0xfffff880009a9a10)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=9ffffffffffffffa rbx=0000000000000000 rcx=0000000000000006
    rdx=fffffa8000000008 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800030a73a4 rsp=fffff880009a9ba0 rbp=0000000000000028
     r8=0000000000000000  r9=0000000000000000 r10=fffffa8003c01060
    r11=fffff880009a9c08 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz ac po cy
    nt!MiUnlinkFreeOrZeroedPage+0x1ca:
    fffff800`030a73a4 48893cc2        mov     qword ptr [rdx+rax*8],rdi ds:fffffa7f`ffffffd8=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80003085ca9 to fffff80003086740
    
    STACK_TEXT:  
    fffff880`009a98c8 fffff800`03085ca9 : 00000000`0000000a fffffa7f`ffffffd8 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`009a98d0 fffff800`03084920 : ffffffff`ffffffff fffffa80`01174f80 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`009a9a10 fffff800`030a73a4 : 00000000`00000000 00000000`00000000 fffffa80`03cf5040 fffff800`030cd985 : nt!KiPageFault+0x260
    fffff880`009a9ba0 fffff800`030cd4c6 : 00000000`0000003f 00000000`00000028 00000000`0000000f 00000000`00000000 : nt!MiUnlinkFreeOrZeroedPage+0x1ca
    fffff880`009a9c10 fffff800`0332ac06 : fffffa80`03cf5040 00000000`00000080 fffffa80`03c719e0 fffff800`03064c19 : nt!MmZeroPageThread+0x551
    fffff880`009a9d40 fffff800`03064c26 : fffff800`03200e80 fffffa80`03cf5040 fffff800`0320ec40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`009a9d80 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a99b0 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiUnlinkFreeOrZeroedPage+1ca
    fffff800`030a73a4 48893cc2        mov     qword ptr [rdx+rax*8],rdi
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!MiUnlinkFreeOrZeroedPage+1ca
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0xA_nt!MiUnlinkFreeOrZeroedPage+1ca
    
    BUCKET_ID:  X64_0xA_nt!MiUnlinkFreeOrZeroedPage+1ca
    
    Followup: MachineOwner
    ---------
    Old drivers
    Code:
    SiWinAcc.sys        fffff880`015a8000    fffff880`015b1000    0x00009000    0x4671d6fa    6/14/2007 20:02:02                        
    SiRemFil.sys        fffff880`01e53000    fffff880`01e5b000    0x00008000    0x46798312    6/20/2007 15:42:10                        
    SI3124.sys        fffff880`0108d000    fffff880`010a7000    0x0001a000    0x47e40d5d    3/21/2008 15:32:45                        
    spldr.sys        fffff880`01e00000    fffff880`01e08000    0x00008000    0x4a0858bb    5/11/2009 12:56:27                        
    amdxata.sys        fffff880`01306000    fffff880`01311000    0x0000b000    0x4a12f2eb    5/19/2009 13:56:59                        
    nvraid.sys        fffff880`00c71000    fffff880`00c9a000    0x00029000    0x4a13a5ac    5/20/2009 02:39:40                        
    nvstor.sys        fffff880`01000000    fffff880`0102b000    0x0002b000    0x4a13a711    5/20/2009 02:45:37                        
    PxHlpa64.sys        fffff880`015da000    fffff880`015e5e00    0x0000be00    0x4a416253    6/23/2009 19:16:35
    To cover possible OS corruption I would also run a system file check

    SFC /SCANNOW Command - System File Checker

    Ken
      My Computer


  3. Posts : 17
    Windows 7 64 Professional
    Thread Starter
       #3

    Well, I ram memtest and it came back fine. One stick at a time, and a good one in every slot . Blew out dust. Reinstalled memory; DIMMS in different slots. Then it ws rebooting like it had hiccups. Reseated all DIMMs. Still BSODS; these are worse; on restore, startup, and after a few minutes after a boot.

    I have to assume that somewhere is a bad DIMM and I should replace all; I was considering upgrading to 8GB anyway
      My Computer


  4. Posts : 17
    Windows 7 64 Professional
    Thread Starter
       #4

    Well, I installed new memory, and no BSOD since!
      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 00:27.
Find Us