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!

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:

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:

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.

Michaelvas17 said:

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.

axe0 said:

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.)