Semi-daily BLACK screens (BSOD without the BS) on NTOSKRNL.EXE

Page 1 of 2 12 LastLast

  1. Posts : 76
    XP, Vista, W7, all flavors
       #1

    Semi-daily BLACK screens (BSOD without the BS) on NTOSKRNL.EXE


    This is an ongoing issue...

    I installed this from a Retail Windows Ultimate disk a few months ago, with 8GB of RAM. At the time I installed, I was getting crashes 80% of the way into the install. When I moved the RAM around, I was able to complete the installation. memtest fsails; Checking BIOS, I saw thet the guys at the PC store had overclocked the board slightly. I reset the board to default and reinstalled, no problem.

    Flash forward a couple weeks. I get BSODs on ntoskrnl.exe. I run memtest and get no errors, but decide to swap out the memory anyway.

    (I also had a weird problem where RDesktop and Windows file sharing FROM this PC were extremely slow (16kB/sec) but other transfers were fine. Fixed by adding a new NIC.)

    It's worse now. Daily crashes. Two this morning. Can you guys tell from this if it's the MB or did I get two bum sets of RAM in a row? Some other hardware?

    MB: ASUS M5A88-M

    Attachment 183115
    Attachment 183116
      My Computer


  2. Posts : 5,405
    Windows 7 Ultimate 64bit SP1
       #2

    Hi.


    Update
    the software\driver for Asus ATK0110 ACPI Utility (a known BSOD maker in Win7). Also a part of the Asus PCProbe and AISuite Utilities


    Yours is too old from 28-Mar-05 no way to be compatible with windows 7


    ASUSTeK Computer Inc. -Support- Drivers and Download


    Update
    your ASUS NX1101 Gigabit Ethernet Adapter


    ASUSTeK Computer Inc. -Support- Drivers and Download



    Finish
    and post back.
      My Computer


  3. Posts : 76
    XP, Vista, W7, all flavors
    Thread Starter
       #3

    Thank you for that info. I updated the NX1101 driver and the ATK0110 ACPI utility (at least, I think I did. The download descriptions at ASUS were not too helpful).

    (Also note that I have disabled the NX1101 for unrelated reasons, and the crash still occurred).

    All was well for 4 days, and I was about to write back that you had fixed my issue when I got a crash this morning, and it was ntoskrnl.sys again.

    Attached is the minidump info.
    Attachment 183654
      My Computer


  4. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #4

    A system process was terminated by an external program, that includes antivirus software, defect in hardware, malware and system utilities.
    Run a scan of Malwarebytes
    Reset your BIOS options to thier default values and stop any overclocking.
    Run the Memtes86+ again with your RAM at default voltages and timings
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    CRITICAL_OBJECT_TERMINATION (f4)
    A process or thread crucial to system operation has unexpectedly exited or been
    terminated.
    Several processes and threads are necessary for the operation of the
    system; when they are terminated (for any reason), the system can no
    longer function.
    Arguments:
    Arg1: 0000000000000003, Process
    Arg2: fffffa80079a69e0, Terminating object
    Arg3: fffffa80079a6cc0, Process image file name
    Arg4: fffff800035e38b0, Explanatory message (ascii)
    
    Debugging Details:
    ------------------
    
    
    PROCESS_OBJECT: fffffa80079a69e0
    
    IMAGE_NAME:  csrss.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MODULE_NAME: csrss
    
    FAULTING_MODULE: 0000000000000000 
    
    PROCESS_NAME:  csrss.exe
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
    
    BUGCHECK_STR:  0xF4_IOERR
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`021b80e8 fffff800`0366a5e2 : 00000000`000000f4 00000000`00000003 fffffa80`079a69e0 fffffa80`079a6cc0 : nt!KeBugCheckEx
    fffff880`021b80f0 fffff800`0361799b : ffffffff`ffffffff fffffa80`07c84060 fffffa80`079a69e0 fffffa80`079a69e0 : nt!PspCatchCriticalBreak+0x92
    fffff880`021b8130 fffff800`03597448 : ffffffff`ffffffff 00000000`00000001 fffffa80`079a69e0 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6
    fffff880`021b8180 fffff800`032deed3 : fffffa80`079a69e0 fffff800`c0000006 fffffa80`07c84060 00000000`01f80ea0 : nt!NtTerminateProcess+0xf4
    fffff880`021b8200 fffff800`032db470 : fffff800`0332b67f fffff880`021b8b78 fffff880`021b88d0 fffff880`021b8c20 : nt!KiSystemServiceCopyEnd+0x13
    fffff880`021b8398 fffff800`0332b67f : fffff880`021b8b78 fffff880`021b88d0 fffff880`021b8c20 00000000`01f81a40 : nt!KiServiceLinkage
    fffff880`021b83a0 fffff800`032df2c2 : fffff880`021b8b78 00000000`00013510 fffff880`021b8c20 00000000`01f81518 : nt! ?? ::FNODOBFM::`string'+0x49874
    fffff880`021b8a40 fffff800`032dde3a : 00000000`00000000 000007fe`fdd3d8b4 00000000`01f91501 00000000`00013510 : nt!KiExceptionDispatch+0xc2
    fffff880`021b8c20 00000000`778c9c12 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
    00000000`01f81460 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778c9c12
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe
    
    BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe
    
    Followup: MachineOwner
    ---------
      My Computer


  5. Posts : 76
    XP, Vista, W7, all flavors
    Thread Starter
       #5

    I am pretty sure I did that back when I was first having trouble, but I went ahead and defaulted it again, and ran the RAM test. No problems.

    I'll let it chug on for a while and see. But from what you said, the only common problem I have had is the MB.
      My Computer


  6. Posts : 76
    XP, Vista, W7, all flavors
    Thread Starter
       #6

    Update: I still had problems, after double-checking that nothing was overclocked, updating the BIOS, etc. Still had a crash after a few days.

    I swapped out the MB with a duplicate (that was fun). That was Friday evening. so I got three days out of it until it crashed again.

    So now the ONLY common component is the CPU. Just as a reminder...

    When I first installed this system, I could not get thru the windows installation with the original memory sticks A and B in slots 1 and 3. In fact, that produced a memtest error. BUT if I moved the sicks to 2 and 4, or reversed A and B, there was no problem. I replaced the memory and there was no problem. So I installed and now I am having these crashes.

    Is there anyway of finding out what the "External" is in the memory ntoskrnl error? Can it be a USB device? There is nothing new on this system (usb) Vs the previous incarnation.

    It might be the CPU (AMD 970). I do have a 965 that I could swap in, but this would take digging out the MB again (I may as well, so I can return it, I guess). Is that error consistent with a bad CPU?

    Could it be heating up? I have done some things to keep the box cool, and I did not notice any difference in crashing when it was running hot Vs cold.

    Thanks again.
      My Computer


  7. Posts : 76
    XP, Vista, W7, all flavors
    Thread Starter
       #7

    I ran a WinDbg analysis, seems that there is an error reading memory in CSRSS.exe.

    Is there a way to determine if that address is on the HDD or in RAM? Could it be a disk problem? I ran CHKDSK /R /F and there were no problems.

    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\121311-34367-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 (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Machine Name:
    Kernel base = 0xfffff800`03c09000 PsLoadedModuleList = 0xfffff800`03e4e670
    Debug session time: Tue Dec 13 05:38:37.838 2011 (UTC - 8:00)
    System Uptime: 3 days 7:09:28.010
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..............................................
    Loading User Symbols
    Loading unloaded module list
    .........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck F4, {3, fffffa8008e54b30, fffffa8008e54e10, fffff80003f898b0}

    Probably caused by : csrss.exe

    Followup: MachineOwner
    ---------

    1: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    CRITICAL_OBJECT_TERMINATION (f4)
    A process or thread crucial to system operation has unexpectedly exited or been
    terminated.
    Several processes and threads are necessary for the operation of the
    system; when they are terminated (for any reason), the system can no
    longer function.
    Arguments:
    Arg1: 0000000000000003, Process
    Arg2: fffffa8008e54b30, Terminating object
    Arg3: fffffa8008e54e10, Process image file name
    Arg4: fffff80003f898b0, Explanatory message (ascii)

    Debugging Details:
    ------------------


    PROCESS_OBJECT: fffffa8008e54b30

    IMAGE_NAME: csrss.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    MODULE_NAME: csrss

    FAULTING_MODULE: 0000000000000000

    PROCESS_NAME: csrss.exe

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

    BUGCHECK_STR: 0xF4_C0000005

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    CURRENT_IRQL: 0

    STACK_TEXT:
    fffff880`07a970e8 fffff800`040105e2 : 00000000`000000f4 00000000`00000003 fffffa80`08e54b30 fffffa80`08e54e10 : nt!KeBugCheckEx
    fffff880`07a970f0 fffff800`03fbd99b : ffffffff`ffffffff fffffa80`08cde060 fffffa80`08e54b30 fffffa80`08e54b30 : nt!PspCatchCriticalBreak+0x92
    fffff880`07a97130 fffff800`03f3d448 : ffffffff`ffffffff 00000000`00000001 fffffa80`08e54b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6
    fffff880`07a97180 fffff800`03c84ed3 : fffffa80`08e54b30 fffff800`c0000005 fffffa80`08cde060 00000000`02a308c0 : nt!NtTerminateProcess+0xf4
    fffff880`07a97200 fffff800`03c81470 : fffff800`03cd167f fffff880`07a97b78 fffff880`07a978d0 fffff880`07a97c20 : nt!KiSystemServiceCopyEnd+0x13
    fffff880`07a97398 fffff800`03cd167f : fffff880`07a97b78 fffff880`07a978d0 fffff880`07a97c20 00000000`02a32100 : nt!KiServiceLinkage
    fffff880`07a973a0 fffff800`03c852c2 : fffff880`07a97b78 00000000`00011a44 fffff880`07a97c20 00000000`02a31bd8 : nt! ?? ::FNODOBFM::`string'+0x49874
    fffff880`07a97a40 fffff800`03c83e3a : 00000000`00000001 00000000`02a30e78 00000000`00000001 00000000`00011a44 : nt!KiExceptionDispatch+0xc2
    fffff880`07a97c20 00000000`776e8e3d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
    00000000`02a30e80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x776e8e3d


    STACK_COMMAND: kb

    FOLLOWUP_NAME: MachineOwner

    FAILURE_BUCKET_ID: X64_0xF4_C0000005_IMAGE_csrss.exe

    BUCKET_ID: X64_0xF4_C0000005_IMAGE_csrss.exe

    Followup: MachineOwner
    ---------

    1: kd> !process fffffa8008e54b30 3
    GetPointerFromAddress: unable to read from fffff80003eb8000
    PROCESS fffffa8008e54b30
    SessionId: none Cid: 01fc Peb: 7fffffdf000 ParentCid: 016c
    DirBase: 1d3d9e000 ObjectTable: fffff8a00141a0a0 HandleCount: <Data Not Accessible>
    Image: csrss.exe
    VadRoot fffffa800a7f7a80 Vads 95 Clone 0 Private 788. Modified 4218. Locked 0.
    DeviceMap fffff8a000008bb0
    Token fffff8a0014adb40
    ReadMemory error: Cannot get nt!KeMaximumIncrement value.
    fffff78000000000: Unable to get shared data
    ElapsedTime 00:00:00.000
    UserTime 00:00:00.000
    KernelTime 00:00:00.000
    QuotaPoolUsage[PagedPool] 0
    QuotaPoolUsage[NonPagedPool] 0
    Working Set Sizes (now,min,max) (1622, 50, 345) (6488KB, 200KB, 1380KB)
    PeakWorkingSetSize 1622
    VirtualSize 49 Mb
    PeakVirtualSize 57 Mb
    PageFaultCount 5956
    MemoryPriority BACKGROUND
    BasePriority 13
    CommitCharge 1105

    *** Error in reading nt!_ETHREAD @ fffffa80091ca060
      My Computer


  8. Posts : 76
    XP, Vista, W7, all flavors
    Thread Starter
       #8

    OK. This time I swapped out my main HDD (SSD) for a spare standard HDD (Clonezilla). Running for 5 days without a crash (nine without BSOD is the best). Chkdsk had found no errors on it.

    This may be the wrong place, but is there a more rigorous disk checking program for an SSD?
      My Computer


  9. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #9

    ultralame said:
    OK. This time I swapped out my main HDD (SSD) for a spare standard HDD (Clonezilla). Running for 5 days without a crash (nine without BSOD is the best). Chkdsk had found no errors on it.

    This may be the wrong place, but is there a more rigorous disk checking program for an SSD?
    Try HD Tune and do the Error Check test
      My Computer


  10. Posts : 76
    XP, Vista, W7, all flavors
    Thread Starter
       #10

    Well, it's been 16 days without a crash, a new record. I am running off an old 250GB standard HDD and all is well. This leads me to believe it was the SSD.

    I have run every test I could find on the SSD, no errors. This jives with the fact that it would chug on for 3-7 days without error.

    I am going to find another place to post questions about the HDD, but this is the last, Big Question:

    Is this a hardware error or a software error? My drivers were all up to date, or so I believe. Is there a specific driver that could be faulting with the SSD and not the non-SSD? I didn't think I needed anything special for it.

    The drive is a Corsair FORCE Sata3 120GB drive (CSSD-F120GB3)
      My Computer


 
Page 1 of 2 12 LastLast

  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 15:14.
Find Us