BSOD: ntoskrnl.exe and more

axe0 · 21 Feb 2016

What is the procedure to fix / check the issue? It was again caused by the driver ntoskrnl.exe. Caused by address: ntoskrnl.exe+142480. Maybe you can trace back the root of this problem with this informatio

Unfortunately that information is pretty much useless.
The ntoskrnl.exe file is a Windows kernel file, the Windows kernel files are simply never the cause. I haven't seen a situation where there were enough problems to point the cause to the ntoskrnl.exe file, you need a lot of serious (more then BSOD's) problems to point to the kernel.
You'll need to provide another upload to provide the right information.

I don't want to complaint, but this is the 3rd time I'm asking for system specs, they're very valuable for troubleshooting.
Is there a reason why you don't give them?

Please fill in your system specs

Please follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely.

How to fill in your system specs:

EUWDIAMOND · 21 Feb 2016

I apologize, whener you posted this the issues seemed to have vanished but it returned later. The tutorial is outdated, it redirects me to windows seven forums. I will try to copy everything manually.

CPU:
Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
GenuineIntel
64bit
l2 cache: 1024kb
l3 cache: 6144kb
max clock speed 3192hz
cores 4
logical processors 4

mainboard:
asrock z170pro4s

bios:
American Megatrends Inc.
BIOS Date: 08/13/15 18:07:39 Ver: 05.0000B
serial number: To Be Filled By O.E.M.
P1.40
release: 13.08.2015

memory:
total 16gb
bank 1: 8gb
DIMM

ssd
Crucial_CT250MX200SSD1
3 partitions

graphic card:
AMD Radeon (TM) R9 380 Series
1920 x 1080 x 32 bits (4294967296 colors) @ 60 Hz (my monitor is 144hz, do I need to change any settings or is this fine?
driveR: 15.201.1151.1008
date; 04.11.2015

windows
Microsoft Windows 10 Home 64-Bit
build: 10586 Multiprocessor Free
boot device: \Device\HarddiskVolume1
sys device: \Device\HarddiskVolume2
directory: C:\WINDOWS
system directory: C:\WINDOWS\system32
usable memory: 15.95gb

it says: hdd --> (1) Crucial_CT250MX200SSD1 (2) ST1000DM003-1SB10C

is this fine as of right now? Any further information required?

axe0 · 22 Feb 2016

I posted it a few times, I don't believe that happened every time.

The tutorial isn't outdated, it is from that site, you have to fill in your system specs manually.

EUWDIAMOND · 22 Feb 2016

I am very grateful for your help, don't worry. I might have overlooked it twice. Look, I am actively trying to figure out a solution and I tried to follow each and every step when possible. The issue is that when I select the manual option and then "edit system specs", it redirects me to a site called sevenforums and not tenforums. But I will fill the out directly on the website here.

axe0 · 22 Feb 2016

That tool is written for sevenforums (a sister forum) which is why you're redirected to it.
I have filled in my system specs (better) using it, but I had to manually fill in everything. It is been a while but I believe I couldn't copy/paste anything.

EUWDIAMOND · 25 Mar 2016

Hello,

A small update: The BSOD's have gotten better recently, but there are still a few each week (roughly 3-5) which is very annoying. I filled in manually my system specs, as you wished :) Now, I think we need to recheck everything, software, hardware, installed programs etc. Can you give me a list of steps / checks which I should apply? Where shall we start?

axe0 · 26 Mar 2016

Depends mainly on what types the crashes are, there are several memory related crashes, some are also pretty specific to components.

If you can provide another log, or at least dumps we can find out where to start :)

EUWDIAMOND · 26 Mar 2016

I attached a few logs. Is the language correct? Let me know if not, I am not sure because I have an English windows but the German Keyboard layout. I remember having installed drivers from drivertalent a while ago, we surely need to check whether I have wrong drivers installed / whether correct drivers are lacking. What I noticed is also, that the two most recent bluescreens happened exact at the same time (21:55h) but four days apart. Thanks for your help so far :)

axe0 · 27 Mar 2016

The language is not correct.

All the crashes, except for 1, are 0x1A which are all memory related crashes.
Run driver verifier again, but this time after 48h disable it and some time later enable it again.

What I noticed is also, that the two most recent bluescreens happened exact at the same time (21:55h) but four days apart.

Check your scheduled tasks to see if anything is active in that period.

Diagnostic Test

DRIVER VERIFIER

Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

EUWDIAMOND · 27 Mar 2016

Here is the updated log, I hope the language is correct. If not, inform me. If yes, tell me if you could gather any particular information. I will run driver verifier tomorrow. I have an extern hard disk and I was thinking about copying my important documents there and then installing everything completely from scratch, how should I approach then? I might need>

A new windows or download the newest win 10 usb compatible boot media

A way to remove all currently installed drivers and start again by installing my drivers from the graphic & mainboard card cd dvd.

What do you think about it? I will keep you updated about the driver verifier.