Windows 10: Random BSOD's, ntoskrnl.exe / driver related? Solved

Page 1 of 2 12 LastLast
  1.    24 Sep 2016 #1

    Random BSOD's, ntoskrnl.exe / driver related?


    Greetings all,

    I usually find my way around PC issues, but I'm about to lose hope with this one..

    The laptop in question is a brand new Vaio Z Flip. Have it for less than a week.
    Model is i7 6567U, 8GB RAM, 256 SSD.

    Some history (long post, might not be relevant.. skip to file below itc):

    When I turned it on, Win10 began updating immediately, so I can't tell if BSOD's were there before.
    The installs failed mid-way (don't remember if it was a BSOD or a freeze). Ever since, I started noticing random BSOD's, usually of the types:
    IRQL_NOT_LESS_OR_EQUAL
    MEMORY_MANAGEMENT
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
    PFN_LIST_CORRUPT

    ...and some others which I can't recall (wiped PC since).
    99% of the errors listed ntoskrnl.exe as the problem when examining with BlueScreenView.

    I did a reset, which also failed mid-way, so the PC won't boot. I re-installed Win10 using a USB (with Media Creation Tool), and then performed a reset inside Windows. It succeeded, but BSOD's were still there. I re-installed again. I then noticed same BSOD's, despite no 3rd party drivers being installed (except ones fetched automatically by Windows - I turned that off then). I installed all 3rd party manually as given by Vaio here.
    BSOD's were still there at random, maybe less frequent.

    Also tried:
    1. Ran memtest a whole night for 9 passes - no errors.

    2. Performed built-in diagnostics (sfc, chkdisk etc.). sfc returned this:
    Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log... ... For example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not supported in offline servicing scenarios.
    CBS.log is attached below.

    3. I used to get a BSOD when touching the PC after it'd been idle - I noticed it stops happening when I turned off "Save me power when my device knows I'm away" in settings.

    4. Driver Verifier. When I ran it the way instructed in MS forums (checking all tests except two), I would get a DRIVER_VERIFIER_DETECTED_VIOLATION on boot, with no dump generated. I tested this with all non-MS drivers, and also some individual drivers - most of them generated this error.
    After that, I ran the test as explained in this forum, PC booted normally & left running during the night. The following morning I noticed it had a SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, with ntoskrnl.exe / storport.sys.

    All in all, can't tell if it's a HW problem (haven't crashed in safe mode.. yet). Laptop is under warranty, but Vaio have no reps in my country. So I must make sure I'm dealing with HW issues before shipping internationally.

    Thanks in advance!
      My ComputerSystem Spec


  2. Posts : 11,515
    Windows 10 Pro
       25 Sep 2016 #2

    Hi rstysnake,

    Welcome to the 10forums

    I then noticed same BSOD's, despite no 3rd party drivers being installed (except ones fetched automatically by Windows - I turned that off then)
    This is a good indication that you have a hardware problem, no system should crash with default drivers.
    Recommendation is to use the warranty.
      My ComputersSystem Spec


  3. Posts : 133
    Windows 10 Pro (14393) / 7 Pro
       25 Sep 2016 #3

    I have a similar error with one of my many computers as well. What build are you running?
      My ComputerSystem Spec

  4.    25 Sep 2016 #4

    Hi, and thanks.

    Small update: I was about to post that I'd run BSOD-free ever since doing a clean boot (with all non-MS services removed). I even did some stress-testing (HD videos, constant searching my SSD, etc..).
    Unfortunately, I had a BSOD just now.. strangely enough, while doing nothing at all.

    This one came with no error name, and win32kfull.sys being the process at fault. DMP is attached

    axe0 said: View Post
    Hi rstysnake,

    Welcome to the 10forums


    This is a good indication that you have a hardware problem, no system should crash with default drivers.
    Recommendation is to use the warranty.
    That I fear as well, yes. Despite all HW diagnostics returning no errors, I guess I can't rule that out.
    There is some strange behavior, even with default drivers. For example, Windows keeps reinstalling the WiFi card driver, even though I turned off the auto-install drivers option. I also had to remove an auto-installed "Intel Driver Package". This one didn't come back, though.

    I understand warranty is my safest bet. But as I mentioned, that'll involve some costly international shipping, so I must be sure it is indeed hardware.

    Michaelvas17 said: View Post
    I have a similar error with one of my many computers as well. What build are you running?
    I added the specs to my profile. It's a Vaio Z Flip laptop. It is the exact same spec as reviewed here.
      My ComputerSystem Spec


  5. Posts : 133
    Windows 10 Pro (14393) / 7 Pro
       25 Sep 2016 #5

    This crash dump actually has nothing to do with ntoskrnl.exe. In fact, the fault has to do with win32kfull.sys.
    I can't provide much other insight.

    The question I'm asking to you @rstysnake is what build of Windows 10 are you running. If you're not sure, do the following:
    - Press the Windows Key + R. The Run Dialog should come up.
    - Type 'winver' in the box, press enter.
    - A window like this should come up:
    Attachment 103187

    The information that is highlighted is what I'm asking for.
      My ComputerSystem Spec

  6.    25 Sep 2016 #6

    Michaelvas17 said: View Post
    This crash dump actually has nothing to do with ntoskrnl.exe. In fact, the fault has to do with win32kfull.sys.
    I can't provide much other insight.

    The question I'm asking to you @rstysnake is what build of Windows 10 are you running. If you're not sure, do the following:
    - Press the Windows Key + R. The Run Dialog should come up.
    - Type 'winver' in the box, press enter.
    - A window like this should come up:
    Attachment 103187

    The information that is highlighted is what I'm asking for.
    Ah, I see. The build I'm running is the same as in the picture - 1607 14393.187.

    I actually had 2 BSOD's (PFN corrupt & IRQL not less) while attempting to write this post... it seems they're much more frequent when I'm not clean-booting.

    And yes, I realize most of the time, the driver reported by WhoCrashed/BlueScreenView as faulty may not actually be the problem. The last DMP listed both ntoskrnl.exe and FLTMGR.sys.

    If anyone can provide further analysis, I'll be grateful. My next step is trying to install Win7/8.1 and see if I'm still crashing.
      My ComputerSystem Spec


  7. Posts : 11,515
    Windows 10 Pro
       26 Sep 2016 #7

    Microsoft drivers aren't the cause, when they are blamed it is either something else corrupted something earlier / made an illegal action or there is a hardware problem.

    The dump isn't very insightful for me.

    As you already ran Driver Verifier I would like to have some more information about the tests performed.

    1. Ran memtest a whole night for 9 passes - no errors.
    Which memtest did you ran? MemTest86/MemTest86+/Other?

    2. Performed built-in diagnostics (sfc, chkdisk etc.).
    Which other built-in diagnostics did you run exactly?
    Please upload the chkdsk log Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums
      My ComputersSystem Spec

  8.    26 Sep 2016 #8

    axe0 said: View Post
    Microsoft drivers aren't the cause, when they are blamed it is either something else corrupted something earlier / made an illegal action or there is a hardware problem.

    The dump isn't very insightful for me.

    As you already ran Driver Verifier I would like to have some more information about the tests performed.


    Which memtest did you ran? MemTest86/MemTest86+/Other?


    Which other built-in diagnostics did you run exactly?
    Please upload the chkdsk log Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums
    I used MemTest86+. Booted with a USB.

    Regarding other diagnostics, they were just Windows' own memory tester, disk error checker, startup repair & a full scan with Windows Defender.

    I uploaded the required log. Anything in particular I should be looking for in the event viewer?

    (p.s I just noticed my local date is 28/9 instead of 26/9. Sorry if it makes the logs a little confusing.)
      My ComputerSystem Spec


  9. Posts : 11,515
    Windows 10 Pro
       26 Sep 2016 #9

    It looks like your file system has been very corrupted.

    Please try following command in an admin command prompt and post a screenshot of the result.
    Code:
    DISM /Online /Cleanup-Image /RestoreHealth
    If there are problems with RestoreHealth, please follow step 6 or 7 (depending on the file you have from the download) from the tutorial DISM - Repair Windows 10 Image - Tutorial.





    Random BSOD's, ntoskrnl.exe / driver related? Diagnostics Test Random BSOD's, ntoskrnl.exe / driver related?
     HDD TEST

    Note   Note
    Please run HDTune first, in the order posted!

    Run HDTune to
    • check the health,
    • scan for errors, no quick scan but full scan
    • run a benchmark.

    It may take some time, but please take the time you need to perform it properly.
    When above is done please make screenshots of the following
    • the health,
    • the error scan,
    • the benchmark incl. following
      • transfer rate,
      • access time,
      • burst rate,
      • cpu usage.


    Run SeaTools DOS to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
    Run the long test.
    Note   Note
    Do not run SeaTools on an SSD as the results will be invalid.

    Make a photo of the result and post it.
      My ComputersSystem Spec

  10.    26 Sep 2016 #10

    Hi axe0,

    DISM doesn't seem to work. I've tried your command, as well as the one in the guide (using install.esd).
    Both commands result in the following message:


    I also tried it in safe mode. The RPC service is on, so I'm not sure what's wrong.

    Here are the results from HDTune:

    Attachment 103314

    Everything seems in order, besides the S.M.A.R.T info not showing up in health.

    Regarding SeaTools - I am indeed using an SSD, so according to the note I shouldn't be running this test?
    Last edited by rstysnake; 02 Oct 2016 at 11:33.
      My ComputerSystem Spec


 
Page 1 of 2 12 LastLast

Related Threads
Hi, new member here, I thought this looks like the place to try and get over a annoying problem. Every 1 or 2 days intermittently I am getting a BSOD, it usually happens when my PC wakes up from sleep, but I can't repeat it. (I have tried manually...
Good day, I've been using my Dell XPS 8700 for some time now and ever since I've gotten it it randomy blue screens with multiple different errors, as the title implies. When I open up BlueScreenView, the errors seem to be commonly related to...
Random BSOD always related to ntoskrnl.exe in BSOD Crashes and Debugging
Hi, Having these BSOD happen almost once a week. It never happens when gaming or doing anything demanding. It seems to happen alot when either watching Twitch or Netflix. I have already ran a memtest with 7 passes with no errors. Could...
Hi there Since I updated my CPU, mainboard and RAM to the new Skylake plattform, I'm getting mostly ntoskrnl.exe related BSOD. Memtest didn't show anything after 7 hours but the Windows integrated memory analysis tool did, so I sent my RAM to...
Hello, I've been having a BSOD problem with my computer ever since I updated to windows 10 and it seems to be related to ntoskrnl.exe. I've tired my very best to fix it with driver updates/ uninstall reinstall and part swapping but I was unable to...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 04:17.
Find Us