Windows 8 and 8.1 Forums


ntoskrnl.exe BSOD Before and After Fresh Windows Install

  1. #1


    Posts : 8
    Windows 8.1 64 bit

    ntoskrnl.exe BSOD Before and After Fresh Windows Install


    I built a computer about a year ago and its run fine until about a month ago when my displays started shutting off and not coming back on. The only way I could get my displays to come back on would be to disconnect both monitors and only plug in the monitor that connects with DVI. Connecting the second monitor would cause both to cut out and sometimes BSOD. It seems the same thing was happening with the on-board video. I finally decided to do a fresh Windows 8.1 install and see if the problem persisted. As soon as the I got up and running again I got a BSOD (before installing any drivers). I then did the following tests.

    - Ran memtest for 2 passes (no errors)
    - Tried my GPU on a different PCI-E slot (Still BSOD)
    - Tried unplugging the power from the GPU (Still connected to the PCI-E slot, still BSOD)

    I was thinking of trying with the video card out completely but it seems the crash is random and I can't reproduce it. Any ideas?

      My System SpecsSystem Spec

  2. #2


    Posts : 5,139
    Win8.1Pro - Finally!!!


    I noticed that you don't have Secure Boot and/or UEFI enabled. If you were having problems with it and changed it, please let us know.
    It's not necessary to enable it now. But, should you reinstall Windows at some point in the future, please enable it first.

    I mention this because it may happen that (one day) the system won't boot. This can be caused by a program changing your UEFI settings, or an update of the UEFI resetting it to default values.

    To test and see if this is the cause, boot into the UEFI and see if the settings have been changed. If uncertain, try with Secure Boot both on and off (and the UEFI on UEFI or Legacy (CSM))

    If it still doesn't boot after trying this, then move on to other troubleshooting tools as it's not likely to be due to this.
    I have seen problems with the Killer Network Manager - but mostly on MSI systems. I'd suggest checking out the following:
    [QUOTE]At times the Killer Network Manager may cause BSOD prolems:
    NOTE: See this link first: BSOD while playing on msi gt70 dragon edition 2 (thanks to kaelaan) It appears that the Killer Service problem was solved with the latest release of the Qualcomm versions of the drivers (so try updating to a version dated from later in 2014).[quote]
    The Qualcomm Atheros Killer Service/KillerNetManager is known to cause BSOD's. Please follow the workaround instructions here:
    First, open the Run dialog (Win + R keys) and type in "services.msc" (without the quotes) and press Enter
    Scroll down and locate the "Qualcomm Atheros Killer Service" and right click on it. Select "Stop"
    Right click on it again and this time select "Properties"
    In the dropdown box for "Startup type", select "Disabled", then click on the "OK" button at the bottom of the window

    Next, open Task Manager (right click on TaskBar and select "Task Manager")
    Click on the "More details" dropdown (if present)
    Click on the "Startup" tab
    Scroll down and locate the "KillerNetManager" entry, right click on it and select "Disable"
    There may also be an Install Shield (with the Killer gaming K next to it), if so Right click on it and select "Disable"
    Finally, restart the system in order for the changes to take affect.
    At times the Killer Network Manager will continue to load. If so, it's usually listed in the MSINFO32...Software Environment...Startup Programs section. If it is, please try this:
    It may be that the instructions aren't stopping everything.
    In some cases, there's a program running out of the Program Files/Program Files (x86) directory.
    "c:\program files\qualcomm atheros\killer network manager\killer~1.exe" (NOTE: killer~1.exe is most likely killernetmanager.exe)
    In other cases, there's a program running out of c:\windows\installer\{Long string of letters, numbers, and dashes}\networkmanager.exe_130c27d738f34c89bddf21bcfd74b56d.exe (the long string of letters and numbers may change)

    Here's some things to try
    1) Please see if there are any entries in the Startup tab of Task Manager that are related to Qualcomm/Atheros/Killer Network Manager (and NOT the card itself) and disable them (please let us know what you find) Be careful as the wrong selection can disable the network card.
    2) Check in "msconfig" for any entries that aren't in the Startup tab of Task Manager. Let us know if you find any Qualcomm/Atheros/Killer entries there (we'll disable them differently if they are there).
    3) Locate the "c:\program files\qualcomm atheros\killer network manager\killer~1.exe" and rename the .exe to .BAD (the killer~1 is actually a filename that starts with killer and ends with .exe) There will be an error in event viewer, but it'll stop the bugger from loading.
    4) Locate the "c:\windows\installer\{Long string of letters, numbers, and dashes}\networkmanager.exe_130c27d738f34c89bddf21bcfd74b56d.exe" entry and rename the last .exe to .BAD (the long string of letters and numbers may change)

    Just FYI - here are the MSI workaround instructions: MSI USA
    Although there's only 3 memory dumps, I'm wondering about a hardware problem here. Please run these free diagnostics: Hardware Diagnostics

    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Tue May  6 23:08:18.668 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\050614-3671-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
    System Uptime:0 days 0:02:17.302
    *** WARNING: Unable to verify timestamp for Ntfs.sys
    *** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
    Probably caused by :ntkrnlmp.exe ( nt!ExFreePoolWithTag+d1d )
    BugCheck 19, {3, ffffc00019a9a7d0, ffffc02019a9a7d0, ffffc00019a9a7d0}
    BugCheck Info: BAD_POOL_HEADER (19)
    Arguments: 
    Arg1: 0000000000000003, the pool freelist is corrupt.
    Arg2: ffffc00019a9a7d0, the pool entry being checked.
    Arg3: ffffc02019a9a7d0, the read back flink freelist value (should be the same as 2).
    Arg4: ffffc00019a9a7d0, the read back blink freelist value (should be the same as 2).
    BUGCHECK_STR:  0x19_3
    PROCESS_NAME:  TiWorker.exe
    FAILURE_BUCKET_ID: 0x19_3_nt!ExFreePoolWithTag
    CPUID:        "Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3392
      BIOS Version                  F9
      BIOS Release Date             04/24/2014
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  G1.Sniper M5
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon May  5 21:54:17.904 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\050514-4796-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
    System Uptime:0 days 0:02:38.537
    Probably caused by :memory_corruption ( ONE_BIT )
    BugCheck 1A, {41792, fffff6bfff141ba8, 2000000000, 0}
    BugCheck Info: MEMORY_MANAGEMENT (1a)
    Arguments: 
    Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
        the PTE. Parameters 3/4 contain the low/high parts of the PTE.
    Arg2: fffff6bfff141ba8
    Arg3: 0000002000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x1a_41792
    PROCESS_NAME:  CCC.exe
    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
    CPUID:        "Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3392
      BIOS Version                  F9
      BIOS Release Date             04/24/2014
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  G1.Sniper M5
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun May  4 22:56:28.716 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\050414-3218-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.16384.amd64fre.winblue_rtm.130821-1623
    System Uptime:0 days 0:13:20.340
    Probably caused by :memory_corruption ( ONE_BIT )
    BugCheck 1A, {41792, fffff68000003828, 2000000000, 0}
    BugCheck Info: MEMORY_MANAGEMENT (1a)
    Arguments: 
    Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
        the PTE. Parameters 3/4 contain the low/high parts of the PTE.
    Arg2: fffff68000003828
    Arg3: 0000002000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x1a_41792
    PROCESS_NAME:  BWCFilter11AC_
    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
    CPUID:        "Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3392
      BIOS Version                  F3
      BIOS Release Date             04/24/2013
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  G1.Sniper M5
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    3rd Party Drivers:
    The following is for information purposes only.
    Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
    Code:
    **************************Tue May  6 23:08:18.668 2014 (UTC - 4:00)**************************
    bwcW8x64.sys                Wed Feb 13 12:25:48 2013 (511BCC9C)
    e22w8x64.sys                Wed Mar 20 17:24:01 2013 (514A28F1)
    cthda.sys                   Mon Aug 19 22:48:10 2013 (5212D8EA)
    intelppm.sys                Thu Aug 22 04:46:35 2013 (5215CFEB)
    dump_storahci.sys           Thu Aug 22 07:40:39 2013 (5215F8B7)
    TeeDriverx64.sys            Thu Sep  5 14:02:18 2013 (5228C72A)
    iwdbus.sys                  Tue Dec 17 17:47:38 2013 (52B0D48A)
    igdkmd64.sys                Wed Jan 22 17:42:16 2014 (52E04948)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon May  5 21:54:17.904 2014 (UTC - 4:00)**************************
    AMDACPKSL.SYS               Tue Mar 11 19:49:44 2014 (531FA118)
    AtihdWB6.sys                Tue Mar 11 19:50:02 2014 (531FA12A)
    atikmpag.sys                Thu Apr 17 21:07:07 2014 (53507ABB)
    atikmdag.sys                Thu Apr 17 22:13:16 2014 (53508A3C)
    
    http://www.carrona.org/drivers/driver.php?id=bwcW8x64.sys
    http://www.carrona.org/drivers/driver.php?id=e22w8x64.sys
    http://www.carrona.org/drivers/driver.php?id=cthda.sys
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=dump_storahci.sys
    http://www.carrona.org/drivers/driver.php?id=TeeDriverx64.sys
    http://www.carrona.org/drivers/driver.php?id=iwdbus.sys
    http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
    http://www.carrona.org/drivers/driver.php?id=AMDACPKSL.SYS
    http://www.carrona.org/drivers/driver.php?id=AtihdWB6.sys
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
      My System SpecsSystem Spec

  3. #3


    Posts : 8
    Windows 8.1 64 bit


    I noticed that you don't have Secure Boot and/or UEFI enabled. If you were having problems with it and changed it, please let us know.
    Around four days ago, when I reinstalled windows, I also updated my BIOS to the latest version and reset all motherboard defaults. It would seem those options are turned off by default. Should I go ahead and enable them or only if I plan to do another clean install?

    I have seen problems with the Killer Network Manager...At times the Killer Network Manager may cause BSOD prolems...
    It appears that the Killer Service problem was solved with the latest release of the Qualcomm versions of the drivers (so try updating to a version dated from later in 2014).
    The version I have installed is the latest from my motherboard manufacturers website. Is there a way to get a more updated version than that? I would like to download the latest version but I wouldn't know which one to get if it's not listed on the motherboard manufacturers website. I'll try following the steps you've listed to disable it on startup.

    I'll reply once I've followed all of the steps listed above (Probably late tonight / tomorrow)
      My System SpecsSystem Spec

  4. #4


    Posts : 660
    windows 8.1


    On the qualcomm downloadpage here Driver Downloads | Qualcomm Atheros, Inc. you can find Killer E2200 version 1.1.38.1281. Sadly did not put up any timestamp of the driver.
    So check in device manager your version number.
      My System SpecsSystem Spec

  5. #5


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Don't reset UEFI or Secure Boot until you're ready to reload the OS.

    I'm not certain that there is a problem with the Killer Network Manager. It's just that there were problems with it in the past (which seem to have been fixed) and I haven't seen many of them until recently (I've seen 2 of them over the last couple of days).

    I'd suggest keeping an eye on it for now. If it keeps showing up in subsequent BSOD's - then we might have to do something about it.

    If the hardware diagnostics don't show anything, then try running Driver Verifier according to these instructions: Driver Verifier Settings
      My System SpecsSystem Spec

  6. #6


    Posts : 8
    Windows 8.1 64 bit


    I'm back with a few updates. Since my first post I have:
    - Updated my ethernet drivers to the latest version
    -- Disabled Killer ethernet crap in startup and services
    - Checked the SMART data on my SSD for any errors

    I'm still getting BSOD and random restarts without any BSOD. I've attached more dump info and the SMART data from the SSD.
      My System SpecsSystem Spec

  7. #7


    Posts : 5,139
    Win8.1Pro - Finally!!!


    SMART data is predictive - so it really isn't useful (IMO) as a diagnostic tool.
    It does give hints tho' - which then can be confirmed by running hardware diagnostics
    Please run these hardware diagnostics: Hardware Diagnostics

    Please also run Driver Verifier according to these instructions: Driver Verifier Settings

    Killer Network Manager is still listed in your startups, Please disable it from starting.
    Killer Network Manager c:\windows\installer\{7411487a-ff21-481e-ab53-bf27ff30e042}\networkmanager.exe_130c27d738f34c89bddf21bcfd74b56d.exe -minimize Public Common Startup
    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Fri May  9 19:41:38.513 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\050914-4015-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
    System Uptime:0 days 0:25:17.148
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+6327 )
    BugCheck 1A, {5003, fffff58010804000, 2681, 626a009}
    BugCheck Info: MEMORY_MANAGEMENT (1a)
    Arguments: 
    Arg1: 0000000000005003, The subtype of the bugcheck.
    Arg2: fffff58010804000
    Arg3: 0000000000002681
    Arg4: 000000000626a009
    BUGCHECK_STR:  0x1a_5003
    PROCESS_NAME:  chrome.exe
    FAILURE_BUCKET_ID: 0x1a_5003_nt!_??_::FNODOBFM::_string_
    CPUID:        "Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3392
      BIOS Version                  F9
      BIOS Release Date             04/24/2014
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  G1.Sniper M5
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    3rd Party Drivers:
    The following is for information purposes only.
    Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
    Code:
    **************************Fri May  9 19:41:38.513 2014 (UTC - 4:00)**************************
    e22w8x64.sys                Wed Mar 20 17:24:01 2013 (514A28F1)
    cthda.sys                   Mon Aug 19 22:48:10 2013 (5212D8EA)
    intelppm.sys                Thu Aug 22 04:46:35 2013 (5215CFEB)
    dump_storahci.sys           Thu Aug 22 07:40:39 2013 (5215F8B7)
    TeeDriverx64.sys            Thu Sep  5 14:02:18 2013 (5228C72A)
    bwcW8x64.sys                Fri Nov  8 10:31:59 2013 (527D03EF)
    iwdbus.sys                  Tue Dec 17 17:47:38 2013 (52B0D48A)
    igdkmd64.sys                Wed Jan 22 17:42:16 2014 (52E04948)
    
    http://www.carrona.org/drivers/driver.php?id=e22w8x64.sys
    http://www.carrona.org/drivers/driver.php?id=cthda.sys
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=dump_storahci.sys
    http://www.carrona.org/drivers/driver.php?id=TeeDriverx64.sys
    http://www.carrona.org/drivers/driver.php?id=bwcW8x64.sys
    http://www.carrona.org/drivers/driver.php?id=iwdbus.sys
    http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
      My System SpecsSystem Spec

  8. #8


    Posts : 8
    Windows 8.1 64 bit


    SMART data is predictive - so it really isn't useful (IMO) as a diagnostic tool.
    Not sure what to download to test this with. My SSD manufacturer doesn't have software to test with so I downloaded the seagate SeaTools. I won't be able to run the bootable version because I don't have a CD-ROM drive. I'll be testing with the windows version with the Long Generic test option.

    Other test that I could run:

    - Video Card: Not plugged in right now so we can factor that out as being the problem (although it is still plugged into the pci-e slot I unplugged the power from it)
    - CPU: Haven't gotten around to it yet. (I'll do this later today)
    - RAM: I need to do MEMTEST overnight (I'll do that tonight)
    - Driver Verifier: As long as it doesn't require using a CD I'll try this today also.

    Killer Network Manager is still listed in your startups, Please disable it from starting.
    There are no more items related to killer network manager in my startups. I just went to c:\windows\installer\{7411487a-ff21-481e-ab53-bf27ff30e042} and added .BAD extension to the end.

    Thanks for you help so far!
      My System SpecsSystem Spec

  9. #9


    Posts : 5,139
    Win8.1Pro - Finally!!!


    You can test SSD's w/CrystalMark. It's actually a benchmarking utility, but its the only thing that I know you can do.

    As for the video card - you must have one or you won't be able to see anything on the screen.
    What is the monitor plugged into?
    The video card that has no power going to it can cause problems simply because it has no power. Please remove it from the system in order to see if that helps (if it's what the monitor is plugged into - post back and we'll discuss it a bit).

    Driver Verifier doesn't require a CD - but the recovery sometimes does (although you can use a recovery USB drive in the same way).
      My System SpecsSystem Spec

  10. #10


    Posts : 8
    Windows 8.1 64 bit


    Alright I'm back with an update and I'm even more confused than ever. Since last time I've:

    - Removed GPU completely
    - Run MEMTEST with the following results:
    -- (Chip 1 - Slot 1) 1.5 hours - No errors
    -- (Chip 2 - Slot 1) 1.5 hours - No errors
    -- (Chip 1 - Slot 2) 1.5 hours - No errors
    -- (Chip 2 - Slot 2) 1.5 hours - 30000 errors
    -- (Chip 2 - Slot 2) 1.5 hours - NO ERRORS (same chip and slot)
    -- (Chip 1 & 2 - Slots 3 & 4) 11 hours - NO ERRORS
    -
    Run PRIME for 5 hours with no errors.
    - Monitored temps with HWMonitor while PRIME was running. All sub 50 celcius.
    - Ran seagate drive checker software - No errors - Not sure if this software works the same with SSDs?

    Onboard GPU and dedicated GPU are still not recognizing more than 1 monitor even though the latest drivers are installed. Starting the computer with both monitors plugged in causes both screens to stop displaying. I'm starting to think it's a MB or PSU problem. Next step is to run driver verifier.

    - Also tried using a different HDMI cable to see if it was just a bad cable causing the display to not be recognized. It didn't help.
      My System SpecsSystem Spec

Page 1 of 2 12 LastLast
ntoskrnl.exe BSOD Before and After Fresh Windows Install
Related Threads
Hi, This is my 1st BSOD after I did a Bios update on my laptop, followed by a fresh install of Windows 8 Pro. It occurred during my installation of drivers. The BSOD Error message was: Driver Power State Failure. The dump file is attached if anyone can help take a look at it, as its got me...
Hey guys , I just did a fresh install of windows 8.1 pro on my new rig, all updates done and drivers correct , but every now and then I am getting BSOD Windows 8.1 Kernel Security Check Failure on Windows Your Help would be much appreciated ;) I followed these instructions "Blue Screen of...
I'm sorry but I'm new at this but I'm at a loss at what I'm suppose to do. Just got in the mail 2 ssd's and the HD7870 video card along with a copy of windows 8.1 complete (retail). My boot ssd (one I'm trying to install on) is a 60gb Mushkin and the other is the one I was going to put games on...
Hello, I recently re installed Windows 8 then upgraded to Windows 8.1 because I was having BSOD. Now on the fresh install, which is 4 days or so old, my computer BSOD on start up like before. My guess hardware failure or Norton.... Thank you for your help.
Solved Windows 8.1 BSOD Fresh Install - igdkmd64.sys in BSOD Crashes and Debugging
Edit: Issue solved as of Intel HD Graphics Driver 10.18.10.3345 I get a BSOD with message DRIVER_IRQL_NOT_LESS_OR_EQUAL (igdkmd64.sys) shortly after launching any game. The driver is linked to Intel's Integrated Graphics which I have updated with 'Windows 8.1 Ready' drivers. My laptop has a...
BSOD on Windows 8 fresh install in BSOD Crashes and Debugging
I just got three 320GB Seagate drives setup in RAID 0 for Linux, and I decided to also reinstall Windows 8 on my SSD since it started lagging and running slower than normal. While trying to install Win8, right after selecting a disk/partition to install to, I got a BSOD about an error in a nonpaged...
Windows 8 BSOD after fresh install in BSOD Crashes and Debugging
I have been getting a random BSOD on a fresh Windows 8 install. It doesn't seem to happen at any given time. Sometimes its right after startup and sometimes in the middle of the night when nothing is happening. I have attached my dumps if anyone can help read them. I have tried to look at them...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook