BSOD due to ntoskrnl.exe

[Johngan16]

Hi everyone,

Im posting here as my last resort before doing a fresh install but Im having some issues with my new ryzen computer. Keep getting a BSOD from ntoskrnl.exe.

It did it 3 times in about a week, and I have noticed that everytime that it does it well my bluetooth headset starts to cut sound and when I plug it in and change the audio settings it crashes.I am also having some really REALLY weird bluetooth audio issues I want to clear that bsod first.

I have ran a memtest86 and 0 error...RAM is flawless

Here is the dump file and two screenshot that you may find useful.

https://drive.google.com/file/d/0Bz45zwI7bJhTZk9Jb1dCdHJoX2s/view?usp=sharing

http://imgur.com/a/WDwiq

Thanks for the help

 

[Colif]

Bug Check 0x139 KERNEL_SECURITY_CHECK_FAILURE

parameter 1 value: 3 - A LIST_ENTRY was corrupted (for example, a double remove).

LIST_ENTRY corruption can be difficult to track down and this bug check, indicates that an inconsistency has been introduced into a doubly-linked list (detected when an individual list entry element is added to or removed from the list). Unfortunately, the inconsistency is not necessarily detected at the time when the corruption occurred, so some detective work may be necessary to identify the root cause.

https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check---bug-check-0x139-kernel-security-check-failure

Don't format it yet, someone may read the dump files and solve it for you.

Have a look in device manager and see if any warnings or unknown devices showing

Check you have latest chipset driver & LAN drivers are up to date (I assume blue tooth uses lan - I have it on my PC and looking at drivers, there isn't a separate one for bluetooth on mine)

 

[Johngan16]

Hey Colif! Thanks for the quick reply!

About the device manager there is nothing wrong there!

I am using a non wifi/bluetooth motherboard ; The gigabyte ab350-gaming 3 ( I know its a piece of shit but ryzen has VERY limited choice. even I hate it.)

I've bought an Intel AC PCI wi-fi card with bluetooth (bluetooth also plugs in a USB 2.0 header on-board) Note that I've had ALOT of issues getting the bluetooth to work. This is a also a known card for issues, especially with bluetooth. Ive had to install MANY drivers ( including the up-to-date ) that did not work. This card has two drivers. the Wifi (pro-set wireless) AND the Bluetooth drivers.

I've ended up using a bluetooth driver that works fine (WP-BT-17.1.1531.1764_s64).

I have done (as far as I know) a clean install/un-installation which is the following; Install the driver ( see if it works. If not, reboot see if it works. If not, uninstall, run Ccleaner Registry fix, reboot. repeat until I get a working version.

I would suspect that this card is the source of my problems. (well Possibly the remains of old drivers)

Let me know what you think. .. if you would think that is a possiblity I will explain you the VERY WEIRD issues that I have with my sound devices when I open the Recording/playback devices.

 

[Colif]

Wait and see but if you have a card that is known to cause problems, it seems an obvious good place to start but as I can't read dump files, I shouldn't jump to conclusions yet.

I have noticed add on cards like WIFI cards have been acting up recently so it might be a problem created by MS. Card having AC on it at least makes me think it should have win 10 drivers... the drivers you are using are for win 7. It seems to be many WiFi cards use old chips that don't have win 10 drivers, its tripping up a lot of people who use old cards, as if there isn't a win 10 driver signed by MS, Win 10 won't use it.

Intel(R) PROSet/Wireless SEStub Setup Program is from 2011, https://downloadcenter.intel.com/download/25319/Intel-PROSet-Wireless-Software-for-Bluetooth-technology-for-Windows-7-64-bit

these look like latest bluetooth drivers - https://www.intel.com.au/content/www/au/en/support/network-and-i-o/wireless-networking/000005489.html

 

[gardenman]

Hi, you had the error: [KERNEL_SECURITY_CHECK_FAILURE (139)]

Here is the info I pulled from the dump file: https://pastebin.com/43LumEHK

According the documentation and your dump file, parameter 1 was "3" which means "A LIST_ENTRY was corrupted (for example, a double remove)."

As I read on, part of the documentation says to try Driver Verifier (you should get Colif to help you with this and listen to him first because it may put you in a boot loop). He may not even want to try that.

I'm no expert at reading these dump files. Maybe someone else will come along who knows more. I can't help you with this, wait for Colif or someone else to reply.

 

[Colif]

ITs late here, I will look though pastebin tomorrow unless someone else beats me too it

As for driver verifer, try running driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.

note: sometimes this will put you into a boot loop so it helps to have a win 10 installer handy to get out again. Also helps to run system restore before hand to create a backup to roll back to if necessary. Download the Windows 10 media creation tool and use it to make a win 10 installer on USB
Once it bsod, run Who crashed and see what driver it reveals

The instructions to stop it looping are in the link above I will show u anyway
change boot order so USB is first, hdd second
boot from installer
on screen after languages, choose repair this pc, not install.
choose start up options
hit the restart button
choose a safe mode (it doesn't matter which) by using number associated with it.
Pc will restart and load safe mode
Now open command Prompt
type verifer /reset and press enter
restart PC

thanks Gardenman

 

[Colif]

another fix that might help is run memtest86 on ram, 1 stick at a time. Any errors are too many as only score you want to get is 0. It makes a bootable USB so run it outside windows. Any errors means stick needs to be removed/replaced

Pastebin blames system which isn't right. I found this answer on https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/ntkrnlmpexe-fastfailcorruptlistentry/7ebf85f6-9ec0-47b9-a472-0af2c1cb75ab
as their error is of a similar nature and the 1st answer was driver verifer as above.

 

[Johngan16]

Alright got it!!

Here's Whocrashed report and the Screenshot that confirms it!

http://imgur.com/a/tequE

[strike]https://drive.google.com/file/d/0Bz45zwI7bJhTLW93bXliaG9EaGM/view?usp=sharing
[/strike]

Here's pastebin report of Whocrashed because the url above makes it unreadable

https://pastebin.com/cjJkhscv

 

[Colif]

well, it appears your guess as to cause is correct

On Thu 29/06/2017 03:36:38 your computer crashed
crash dump file: C:\Windows\Minidump\062917-7281-01.dmp
This was probably caused by the following module: ibtusb.sys (ibtusb+0x2040)
Bugcheck code: 0xC4 (0x2000, 0xFFFFF80CB97A2040, 0x0, 0x69706131)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\ibtusb.sys
product: Intel(R) Wireless Bluetooth(R)
company: Intel Corporation
description: Intel(R) Wireless Bluetooth(R) USB Driver
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ibtusb.sys (Intel(R) Wireless Bluetooth(R) USB Driver, Intel Corporation).
Google query: Intel Corporation DRIVER_VERIFIER_DETECTED_VIOLATION

would have been nice if it were something else.

Fresh installing windows to fix a problem caused by an add on card is wrong approach. Sounds like you better off getting new card as this probelm isn't going away unless Intel fix it. I would have thought there be cards that have USB 3 on them by now and that would likely show signs of being more compatible. I feel the problems will continue while you use old drivers.

 

[Johngan16]

Yup..I guess I will return this garbage and buy a TP-LINK PCI card or something like that.. I had originally planned to buy that and a bluetooth dongle but I

was showed that Intel card which was doing both. I mean why not!!

Thanks alot for the help this is unfortunate that the issue cannot be fixed but at least we found it!