BSOD Ntoskrnl.exe+7efc0 and Ntoskrnl.exe+75c40

Page 1 of 2 12 LastLast

  1. Posts : 7
    Windows 7 Home Premium
       #1

    BSOD Ntoskrnl.exe+7efc0 and Ntoskrnl.exe+75c40


    I keep getting a BSOD (Critical_Object_Termination) but have no idea what is causing the issue. I tried in vain to debug my own minidump files but ended up getting nowhere.

    So far i have run MemTest over the weekend with 107 passes. I also ran Prime95 64-bit for 4 hours on each of the FFT tests without error.

    I have enabled driver verifier (following the guide on this site) and this has not caused anynew BSOD's.

    I also get a random BSOD on startup but it has happened so infrequently i have been unable to boot with disable automatic restart on system failure enabled to capture the stop code.

    I really could do with some expert advice please.

    This is my first post so i apologise if i have missed something important but i have tried to read as much info as possible before posting.
      My Computer


  2. Posts : 2,573
    Win7 Ultimate X64
       #2

    Unusual one you got there think it may be a windows problem please run sf tool and upload all files not just dumps and try running an sfc scan
    SFC /SCANNOW Command - System File Checker option 2

    Check system temperatures also
      My Computer


  3. Posts : 7
    Windows 7 Home Premium
    Thread Starter
       #3

    The rest of the files as requested


    Sorry i thought i'd grabbed all the files but i guess i was impatient.

    I also forgot to mention the max temp was no more than 75 when running a large FFT test with Prime 95.
      My Computer


  4. Posts : 2,573
    Win7 Ultimate X64
       #4

    How about the SFC scan any problems found/fixed
    If any errors were fixed run again
      My Computer


  5. Posts : 7
    Windows 7 Home Premium
    Thread Starter
       #5

    Hi Pauly,

    Sorry i forgot to mention that it came back without any problems. Were the rest of the files i uploaded correct?
      My Computer


  6. Posts : 2,573
    Win7 Ultimate X64
       #6

    Had a look through your files and not getting anything conclusive, quite a rare bugcheck code caused by critical threads or processes misbehaving or ending unexpectedly my initial thought would be a problem windows install, hdd problem or some other hardware failure/problem. All dumps blame wininit.exe which is not a driver so explains why driver verifier didnt cause any more crashes.

    SFC scan has proved windows files so i would recommend completing hardware tests with
    Disk Check
    Hard Drive Diagnostic Procedure
    Video Card - Stress Test with Furmark

    if you have multiple HDDs be sure to check them all with a bootable drive check
      My Computer


  7. Posts : 3
    Windows 7 Ultimate x64
       #7

    I was getting bsods all the time with these two files Ntoskrnl.exe

    i have now no bsods now - been running now for 36 hours ( games or normal )

    ask him to check if usb 3 is enabled in bios.

    i had that enabled - now disabled - no bsod
      My Computer


  8. Posts : 7
    Windows 7 Home Premium
    Thread Starter
       #8

    Ok so i tried Furmark which came back fine although as it's a laptop with Intel HD graphics it didn't exactly display the results i was expecting in terms of not showing me a temperature? Ran it for 20 minutes though without any visual errors.

    Ran check disk on both partitions with a /f command and did this on startup rather than in windows.

    Just wanted to ask about the HDD diagnostic procedure. I use HDD Tune Pro which also shows me the S.M.A.R.T. information as well being able to do a surface scan. This came back clean in both and has proved to be very useful to me in the past.

    Is this better or not as good as using one of the HDD diagnostic tools listed on the link you posted? In the past i've found some of those programs to be less useful which is why i want en expert opinion!

    Finally and just to cover everything i disabled USB3.0 in the BIOS just to be sure.

    So far the system hasn't given me anymore BSOD's but i just know as soon as it goes back to the end user it will start to happen again.

    What else can i try and is there a way i can capture any BSOD's outside of the OS in a file that can be analysed?

    Thanks for the help so far.
      My Computer


  9. Posts : 2,573
    Win7 Ultimate X64
       #9

    I always recommend bootable HDD diagnostic software as its the most thorough, visit your hdd manufacturers www and get their software for your drive, create a bootable cd or usb with it then reboot and run checks on all drives for example if you have seagate drives go here SeaTools | Seagate

    Personally i hate s.m.a.r.t. they are ok to give a rough idea but cannot be relied upon, i have built a few systems (including my own that im on now) that show smart comand failed on bios boot screen from brand new

    Not sure what you mean about capturing bsod, when the os crashes like this it generates a dump file which is hat you have already uploaded and this is the file/s we analyse, heres the basic output of your most recent one (i have trimmed it down a bit)
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck F4, {3, fffffa8006402b30, fffffa8006402e10, fffff8000337d470}
    ----- ETW minidump data unavailable-----
    Probably caused by : wininit.exe
    Followup: MachineOwner
    ---------
    2: 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: fffffa8006402b30, Terminating object
    Arg3: fffffa8006402e10, Process image file name
    Arg4: fffff8000337d470, Explanatory message (ascii)
    Debugging Details:
    ------------------
    ----- ETW minidump data unavailable-----
    PROCESS_OBJECT: fffffa8006402b30
    IMAGE_NAME:  wininit.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    MODULE_NAME: wininit
    FAULTING_MODULE: 0000000000000000 
    PROCESS_NAME:  wininit.exe
    EXCEPTION_CODE: (Win32) 0x5 (5) - Access is denied.
    BUGCHECK_STR:  0xF4_5
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    CURRENT_IRQL:  0
    STACK_TEXT:  
    fffff880`040359c8 fffff800`034055e2 : 00000000`000000f4 00000000`00000003 fffffa80`06402b30 fffffa80`06402e10 : nt!KeBugCheckEx
    fffff880`040359d0 fffff800`033b147b : 00000000`00000001 fffffa80`06405b50 fffffa80`06402b30 fffffa80`0642db30 : nt!PspCatchCriticalBreak+0x92
    fffff880`04035a10 fffff800`033324f4 : 00000000`00000001 00000000`00000001 fffffa80`06402b30 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x174f6
    fffff880`04035a60 fffff800`03074ed3 : fffffa80`06405b50 fffff880`00000005 fffffa80`06405b50 00000000`00000000 : nt!NtTerminateProcess+0xf4
    fffff880`04035ae0 00000000`771915da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0027f868 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x771915da
     
    STACK_COMMAND:  kb
    FOLLOWUP_NAME:  MachineOwner
    FAILURE_BUCKET_ID:  X64_0xF4_5_IMAGE_wininit.exe
    BUCKET_ID:  X64_0xF4_5_IMAGE_wininit.exe
    Followup: MachineOwner
    ---------
    2: kd> lmvm wininit
    start             end                 module name
      My Computer


  10. Posts : 7
    Windows 7 Home Premium
    Thread Starter
       #10

    Hi Pauly,

    I will give the manufacturer test a go and let you know the results.

    All i wanted to know with the S.M.A.R.T. data was how reliable is it? I have posted an image of the S.M.A.R.T. data of a faulty HDD as an example. If i see any reallocated sectors (05) and unstable sectors (C5) i automatically deem the HDD to be faulty and replace. If for example i get an error with Ultra DMA CRC which is put down to a fauly cable i generally ignore these as both my work computer and home computer have these erros and they work just fine.

    Based on this am i doing the wrong thing and should i stop using this program?
      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 06:05.
Find Us