BSOD every other start up ntoskrnl.exe issue (I believe)


  1. Posts : 3
    Windows 7 Ultimate x64
       #1

    BSOD every other start up ntoskrnl.exe issue (I believe)


    First off I would like to apologize in advance for my ignorance on the subject of computers, I'm still sorta new to this stuff.

    About a week ago an error occurred when I opened my browser(chrome). A notification said there was an issue with my Kernal.DLL files or something of that matter. I tried using my back up browser(internet explorer) and it worked. I read somewhere that sometimes these errors are flukes and to just reboot my PC, I did so and my issues where resolved, or so I thought. about two days past and while I was browsing the web while running a game in the background, My first BSOD appeared. My initial thoughts were that it might have been Malware due to some sketchy software that I have previously downloaded that suppose to help detect drivers in need of updating. I uninstalled the software and found a potential "virus" called "Content Explorer". Still the BSOD's persisted to pop up after every boot up but as soon as I tried again it would allow the computer to run normally. Windows prompted me to restore my computer to a previous time I did but still no luck. I did some research and I downloaded Blue screen viewer to see if i can locate where the root of the error maybe. I logged all the errors and posted them on the bottom. Again I apologize for my ignorance in advance so please keep explanations simple. I thank everyone for taking the time to read this and helping me with this issue. :)




    Error(1)

    ==================================================
    Dump File : 062014-19609-01.dmp
    Crash Time : 6/20/2014 3:11:46 PM
    Bug Check String : BAD_POOL_HEADER
    Bug Check Code : 0x00000019
    Parameter 1 : 00000000`00000003
    Parameter 2 : fffff800`0340eac0
    Parameter 3 : fffffa80`09c9d010
    Parameter 4 : fffffa80`09c9d010
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+75bc0
    File Description : NT Kernel & System
    Product Name : Microsoftฎ Windowsฎ Operating System
    Company : Microsoft Corporation
    File Version : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
    Processor : x64
    Crash Address : ntoskrnl.exe+75bc0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\062014-19609-01.dmp
    Processors Count : 8
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 276,088
    Dump File Time : 6/20/2014 3:21:31 PM
    ==================================================

    Error(2)

    ==================================================
    Dump File : 062314-27050-01.dmp
    Crash Time : 6/23/2014 7:40:57 PM
    Bug Check String : SESSION3_INITIALIZATION_FAILED
    Bug Check Code : 0x0000006f
    Parameter 1 : ffffffff`c0000005
    Parameter 2 : 00000000`00000000
    Parameter 3 : 00000000`00000000
    Parameter 4 : 00000000`00000000
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+75bc0
    File Description : NT Kernel & System
    Product Name : Microsoftฎ Windowsฎ Operating System
    Company : Microsoft Corporation
    File Version : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
    Processor : x64
    Crash Address : ntoskrnl.exe+75bc0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\062314-27050-01.dmp
    Processors Count : 8
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 269,216
    Dump File Time : 6/23/2014 7:46:46 PM
    ==================================================

    Error (3)

    ==================================================
    Dump File : 062414-16692-01.dmp
    Crash Time : 6/24/2014 8:36:23 PM
    Bug Check String : IRQL_NOT_LESS_OR_EQUAL
    Bug Check Code : 0x0000000a
    Parameter 1 : 00000000`090aab68
    Parameter 2 : 00000000`00000002
    Parameter 3 : 00000000`00000000
    Parameter 4 : fffff800`032dbf42
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+75bc0
    File Description : NT Kernel & System
    Product Name : Microsoftฎ Windowsฎ Operating System
    Company : Microsoft Corporation
    File Version : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
    Processor : x64
    Crash Address : ntoskrnl.exe+75bc0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\062414-16692-01.dmp
    Processors Count : 8
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 276,088
    Dump File Time : 6/24/2014 8:56:20 PM
    ==================================================

    Error (4)

    ==================================================
    Dump File : 062414-17596-01.dmp
    Crash Time : 6/24/2014 8:58:38 PM
    Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
    Bug Check Code : 0x00000050
    Parameter 1 : ffffffff`90fbec14
    Parameter 2 : 00000000`00000001
    Parameter 3 : fffff880`012f29ba
    Parameter 4 : 00000000`00000005
    Caused By Driver : Ntfs.sys
    Caused By Address : Ntfs.sys+d1c5
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : x64
    Crash Address : ntoskrnl.exe+75bc0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\062414-17596-01.dmp
    Processors Count : 8
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 262,144
    Dump File Time : 6/24/2014 9:01:20 PM
    ==================================================

    Error (5)

    ==================================================
    Dump File : 062514-50684-01.dmp
    Crash Time : 6/25/2014 2:19:23 PM
    Bug Check String : SYSTEM_SERVICE_EXCEPTION
    Bug Check Code : 0x0000003b
    Parameter 1 : 00000000`c0000005
    Parameter 2 : fffff800`0358cb93
    Parameter 3 : fffff880`08ae5d70
    Parameter 4 : 00000000`00000000
    Caused By Driver : ataport.SYS
    Caused By Address : ataport.SYS+5fd8
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : x64
    Crash Address : ntoskrnl.exe+75bc0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\062514-50684-01.dmp
    Processors Count : 8
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 276,032
    Dump File Time : 6/25/2014 4:44:29 PM
    ==================================================


    Error (6)

    ==================================================
    Dump File : 062714-23415-01.dmp
    Crash Time : 6/27/2014 2:13:45 AM
    Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
    Bug Check Code : 0x000000d1
    Parameter 1 : 00000000`00000012
    Parameter 2 : 00000000`00000002
    Parameter 3 : 00000000`00000000
    Parameter 4 : fffff880`01914ee4
    Caused By Driver : tcpip.sys
    Caused By Address : tcpip.sys+114ee4
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : x64
    Crash Address : ntoskrnl.exe+75bc0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\062714-23415-01.dmp
    Processors Count : 8
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 276,088
    Dump File Time : 6/27/2014 2:20:00 AM
    ==================================================
    Last edited by thebigcheese77; 27 Jun 2014 at 08:11.
      My Computer


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

    You need to follow the Blue Screen of Death (BSOD) Posting Instructions and upload the zip for us.
      My Computer


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

    which is better option 1 or option 2?
      My Computer


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

    Got it, sorry i thought blue screen viewer was acceptable.
      My Computer


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

    Reduce items at start-up:

    Perform a clean boot:

    Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable!:-

    NTIOLib_X64.sys Thu Oct 25 16:27:58 2012 (5089142E)
    MSI Afterburner driver (known BSOD issues with Windows) Also found to be a part of MSI Live Update 5
    Driver Reference Table - NTIOLib_X64.sys

    dtscsibus.sys Mon Oct 29 15:28:48 2012 (508E4C50)
    DAEMON Tools Virtual SCSI Bus Driver[br]Likely BSOD cause in Windows systems (first seen in Win8)
    Driver Reference Table - dtscsibus.sys

    RTCore64.sys Mon Mar 11 11:32:06 2013 (513D6C56)
    RivaTuner/EVGA Precision/MSI Afterburner (known BSOD issues w/Win7)
    Driver Reference Table - RTCore64.sys

    AODDriver2.sys Thu Sep 12 09:36:40 2013 (523136C8)
    AMD Overdrive; also in EasyTune6 for Gigabyte motherboard [br] Known BSOD issues in Win7[br][br]Part of AMD Fuel[br][br]Location: C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys
    Driver Reference Table - AODDriver2.sys

    To perform a clean install of a driver, follow this tutorial:

    Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows you to remove leftover registry:-

    Code:
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Debug session time: Fri Jun 27 12:13:45.222 2014 (UTC + 6:00)
    System Uptime: 0 days 0:02:37.236
    BugCheck D1, {12, 2, 0, fffff88001914ee4}
    Probably caused by : tcpip.sys ( tcpip!IppSendUnsolicitedNeighborAdvertisement+14 )
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  svchost.exe
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Debug session time: Thu Jun 26 00:19:23.037 2014 (UTC + 6:00)
    System Uptime: 0 days 17:18:23.066
    BugCheck 3B, {c0000005, fffff8000358cb93, fffff88008ae5d70, 0}
    Probably caused by : ntkrnlmp.exe ( nt!IoCsqInsertIrpEx+93 )
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  MsMpEng.exe
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Debug session time: Wed Jun 25 06:58:38.948 2014 (UTC + 6:00)
    System Uptime: 0 days 0:02:40.072
    BugCheck 50, {ffffffff90fbec14, 1, fffff880012f29ba, 5}
    Probably caused by : hardware ( Ntfs!BinarySearchIndex+34a )
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  services.exe
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Debug session time: Wed Jun 25 06:36:23.399 2014 (UTC + 6:00)
    System Uptime: 0 days 0:01:10.523
    BugCheck A, {90aab68, 2, 0, fffff800032dbf42}
    Probably caused by : ntkrnlmp.exe ( nt!KiDeferredReadyThread+32 )
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  System
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Debug session time: Tue Jun 24 05:40:57.522 2014 (UTC + 6:00)
    System Uptime: 0 days 0:00:37.082
    BugCheck 6F, {ffffffffc0000005, 0, 0, 0}
    Probably caused by : ntkrnlmp.exe ( nt!StartFirstUserProcess+20e )
    BUGCHECK_STR:  0x6F_c0000005
    PROCESS_NAME:  System
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Debug session time: Sat Jun 21 01:11:46.155 2014 (UTC + 6:00)
    System Uptime: 0 days 0:01:14.279
    BugCheck 19, {3, fffff8000340eac0, fffffa8009c9d010, fffffa8009c9d010}
    Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a53 )
    BUGCHECK_STR:  0x19_3
    PROCESS_NAME:  System
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    
    Daemon Tools/Alchohol is known to cause Blue Screens. Please remove it:

    Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

    Post a screenshot of your Hard Drive(s) using Crystal Disk Info software:

    Run a Hard Drive test:

    Check for heating issues using Speccy or HWmonitor

    Upload a screen shot:

    Run Disk Check on your hard disk for file system errors and bad sectors on it:

    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


 

  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 22:31.
Find Us