Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Windows 8.1 BSOD ntoskrn.exe


  • Please log in to reply
11 replies to this topic

#1 54M33R

54M33R

  • Members
  • 18 posts
  • OFFLINE
  •  
  • Local time:03:47 AM

Posted 08 March 2017 - 10:45 PM

Been getting some odd BSOD's lately it has been bugging me, turns out ntoskrn.exe is causing this mess, now to save time I will kindly post everything that should be needed to find the very source of this mess if anything else is needed I will also be glad to hand it over.

 

Specs:

 

  • Windows 8.1
  • 64 bit
  • original install was Windows 8.1
  • OS was pre-installed on system although it came from a retailer which I believe might be BestBuy...
  • Unsure but for an estimate ~ 2 - 4 years
  • OS age is also ~ 2 - 4 years and It has never been reinstalled
  • CPU Intel core i7 3632QM 2.20Ghz
  • Manufacturer is HP
  • Model number I am unsure as apparently, the label is not on this laptop
  • And Yes it's a laptop.

 

Now here is an SysnativeFileCollectionApp.zip file for perhaps useful information

Attached File  SysnativeFileCollectionApp.zip   2.64MB   3 downloads

 

Now if more system information is needed I am also kindly to give a Speccy report

http://speccy.piriform.com/results/eUiDPa5eJBXI4ylf7KAg5Pc

 

I will be hoping to see someone to come along and perhaps help with this situation.



BC AdBot (Login to Remove)

 


#2 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 2,990 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:04:47 AM

Posted 08 March 2017 - 10:56 PM

4: kd> .bugcheck
Bugcheck code 0000007F
Arguments 00000000`00000008 ffffd000`94a88230 ffffd000`255a6000 fffff803`a73109d2
ffffd000`255a62f8  fffff801`22c16f2cUnable to load image \SystemRoot\system32\drivers\aswbidsdrivera.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswbidsdrivera.sys
*** ERROR: Module load completed but symbols could not be loaded for aswbidsdrivera.sys
 aswbidsdrivera+0x16f2c
4: kd> lmvm aswbidsdrivera
start             end                 module name
fffff801`22c00000 fffff801`22c50000   aswbidsdrivera T (no symbols)           
    Loaded symbol image file: aswbidsdrivera.sys
    Image path: \SystemRoot\system32\drivers\aswbidsdrivera.sys
    Image name: aswbidsdrivera.sys
    Timestamp:        Tue Feb 21 11:35:49 2017 (58AC6C65)
    CheckSum:         00057DEE
    ImageSize:        00050000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

STOP 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP bugcheck with an avast! driver listed in the raw stack. Uninstall avast!, run their cleaning tool, and use Windows Defender for protection temporarily. Then go to HP's website and update ALL your networking drivers.

 

Let me know how everything goes. :)


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#3 54M33R

54M33R
  • Topic Starter

  • Members
  • 18 posts
  • OFFLINE
  •  
  • Local time:03:47 AM

Posted 08 March 2017 - 11:51 PM

So pretty much there is no other choice but to remove avast. Well might as well switch to Kaspersky. Also be more exact do you mean install all 9 networking drivers for HP?


Edited by 54M33R, 09 March 2017 - 12:00 AM.


#4 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 2,990 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:04:47 AM

Posted 09 March 2017 - 09:52 AM

Really what is happening is that Avast's drivers are conflicting with your networking drivers, as we see tcpip called several times in the stack:

4: kd> k
Child-SP          RetAddr           Call Site
ffffd000`94a880e8 fffff803`a73cfee9 nt!KeBugCheckEx
ffffd000`94a880f0 fffff803`a73cdff4 nt!KiBugCheckDispatch+0x69
ffffd000`94a88230 fffff803`a73109d2 nt!KiDoubleFaultAbort+0xb4
ffffd000`255a6000 fffff803`a730f2cc nt!SepMandatoryIntegrityCheck+0x2
ffffd000`255a6010 fffff803`a730f0a0 nt!SeAccessCheckWithHint+0x1bc
ffffd000`255a61a0 fffff801`2198b799 nt!SeAccessCheckFromStateEx+0x88
ffffd000`255a6230 fffff801`2198bc04 NETIO!MatchValues+0x1c9
ffffd000`255a62e0 fffff801`219892c7 NETIO!IndexListClassify+0xd8
ffffd000`255a6370 fffff801`21b08d3c NETIO!KfdClassify+0x8a8
ffffd000`255a6830 fffff801`21afa182 tcpip!WfpAleClassify+0x4c
ffffd000`255a6870 fffff801`21afa9c4 tcpip!WfpAlepReauthorizeOutboundConnection+0x7ce
ffffd000`255a69f0 fffff801`21c3a892 tcpip!WfpAleReauthorizeOutboundConnection+0x190
ffffd000`255a6b30 fffff801`21bd6881 tcpip!WfpAlepAuthorizeConnectCompletion+0x136
ffffd000`255a6c30 fffff801`21afa182 tcpip!WfpAleClassify+0xcdb91
ffffd000`255a6c70 fffff801`21afa9c4 tcpip!WfpAlepReauthorizeOutboundConnection+0x7ce
ffffd000`255a6df0 fffff801`21c3a892 tcpip!WfpAleReauthorizeOutboundConnection+0x190
ffffd000`255a6f30 fffff801`21bd6881 tcpip!WfpAlepAuthorizeConnectCompletion+0x136
ffffd000`255a7030 fffff801`21afa182 tcpip!WfpAleClassify+0xcdb91
ffffd000`255a7070 fffff801`21afa9c4 tcpip!WfpAlepReauthorizeOutboundConnection+0x7ce
ffffd000`255a71f0 fffff801`21c3a892 tcpip!WfpAleReauthorizeOutboundConnection+0x190
ffffd000`255a7330 fffff801`21bd6881 tcpip!WfpAlepAuthorizeConnectCompletion+0x136
ffffd000`255a7430 fffff801`21afa182 tcpip!WfpAleClassify+0xcdb91
ffffd000`255a7470 fffff801`21afa9c4 tcpip!WfpAlepReauthorizeOutboundConnection+0x7ce
ffffd000`255a75f0 fffff801`21c3a892 tcpip!WfpAleReauthorizeOutboundConnection+0x190
ffffd000`255a7730 fffff801`21bd6881 tcpip!WfpAlepAuthorizeConnectCompletion+0x136
ffffd000`255a7830 fffff801`21afa182 tcpip!WfpAleClassify+0xcdb91
ffffd000`255a7870 fffff801`21afa9c4 tcpip!WfpAlepReauthorizeOutboundConnection+0x7ce
ffffd000`255a79f0 fffff801`21c3a892 tcpip!WfpAleReauthorizeOutboundConnection+0x190
ffffd000`255a7b30 fffff801`21bd6881 tcpip!WfpAlepAuthorizeConnectCompletion+0x136
ffffd000`255a7c30 fffff801`21afa182 tcpip!WfpAleClassify+0xcdb91
ffffd000`255a7c70 fffff801`21afa9c4 tcpip!WfpAlepReauthorizeOutboundConnection+0x7ce
ffffd000`255a7df0 fffff801`21c3a892 tcpip!WfpAleReauthorizeOutboundConnection+0x190
ffffd000`255a7f30 fffff801`21bd6881 tcpip!WfpAlepAuthorizeConnectCompletion+0x136
ffffd000`255a8030 fffff801`21afa182 tcpip!WfpAleClassify+0xcdb91
ffffd000`255a8070 fffff801`21afa9c4 tcpip!WfpAlepReauthorizeOutboundConnection+0x7ce
ffffd000`255a81f0 fffff801`21c3a892 tcpip!WfpAleReauthorizeOutboundConnection+0x190
ffffd000`255a8330 fffff801`21bd6881 tcpip!WfpAlepAuthorizeConnectCompletion+0x136
ffffd000`255a8430 fffff801`21afa182 tcpip!WfpAleClassify+0xcdb91
ffffd000`255a8470 fffff801`21afa9c4 tcpip!WfpAlepReauthorizeOutboundConnection+0x7ce
ffffd000`255a85f0 fffff801`21c3a892 tcpip!WfpAleReauthorizeOutboundConnection+0x190
ffffd000`255a8730 fffff801`21bd6881 tcpip!WfpAlepAuthorizeConnectCompletion+0x136
ffffd000`255a8830 fffff801`21afa182 tcpip!WfpAleClassify+0xcdb91
ffffd000`255a8870 fffff801`21afa9c4 tcpip!WfpAlepReauthorizeOutboundConnection+0x7ce
ffffd000`255a89f0 fffff801`21c3a892 tcpip!WfpAleReauthorizeOutboundConnection+0x190
ffffd000`255a8b30 fffff801`21bd6881 tcpip!WfpAlepAuthorizeConnectCompletion+0x136
ffffd000`255a8c30 fffff801`21afa182 tcpip!WfpAleClassify+0xcdb91
ffffd000`255a8c70 fffff801`21afa9c4 tcpip!WfpAlepReauthorizeOutboundConnection+0x7ce
ffffd000`255a8df0 fffff801`21c3a892 tcpip!WfpAleReauthorizeOutboundConnection+0x190
ffffd000`255a8f30 fffff801`21bd6881 tcpip!WfpAlepAuthorizeConnectCompletion+0x136
ffffd000`255a9030 fffff801`21afa182 tcpip!WfpAleClassify+0xcdb91
ffffd000`255a9070 fffff801`21afa9c4 tcpip!WfpAlepReauthorizeOutboundConnection+0x7ce
ffffd000`255a91f0 fffff801`21c3a892 tcpip!WfpAleReauthorizeOutboundConnection+0x190
ffffd000`255a9330 fffff801`21bd6881 tcpip!WfpAlepAuthorizeConnectCompletion+0x136
ffffd000`255a9430 fffff801`21afa182 tcpip!WfpAleClassify+0xcdb91
ffffd000`255a9470 fffff801`21afa9c4 tcpip!WfpAlepReauthorizeOutboundConnection+0x7ce
ffffd000`255a95f0 fffff801`21c3a892 tcpip!WfpAleReauthorizeOutboundConnection+0x190
ffffd000`255a9730 fffff801`21bd6881 tcpip!WfpAlepAuthorizeConnectCompletion+0x136
ffffd000`255a9830 fffff801`21afa182 tcpip!WfpAleClassify+0xcdb91
ffffd000`255a9870 fffff801`21afa9c4 tcpip!WfpAlepReauthorizeOutboundConnection+0x7ce
ffffd000`255a99f0 fffff801`21c3a892 tcpip!WfpAleReauthorizeOutboundConnection+0x190
ffffd000`255a9b30 fffff801`21bd6881 tcpip!WfpAlepAuthorizeConnectCompletion+0x136
ffffd000`255a9c30 fffff801`21afa182 tcpip!WfpAleClassify+0xcdb91
ffffd000`255a9c70 fffff801`21afa9c4 tcpip!WfpAlepReauthorizeOutboundConnection+0x7ce
ffffd000`255a9df0 fffff801`21c3a892 tcpip!WfpAleReauthorizeOutboundConnection+0x190
ffffd000`255a9f30 fffff801`21bd6881 tcpip!WfpAlepAuthorizeConnectCompletion+0x136
ffffd000`255aa030 fffff801`21afa182 tcpip!WfpAleClassify+0xcdb91
ffffd000`255aa070 fffff801`21afa9c4 tcpip!WfpAlepReauthorizeOutboundConnection+0x7ce
ffffd000`255aa1f0 fffff801`21c3a892 tcpip!WfpAleReauthorizeOutboundConnection+0x190
ffffd000`255aa330 fffff801`21bd6881 tcpip!WfpAlepAuthorizeConnectCompletion+0x136
ffffd000`255aa430 fffff801`21afa182 tcpip!WfpAleClassify+0xcdb91
ffffd000`255aa470 fffff801`21afa9c4 tcpip!WfpAlepReauthorizeOutboundConnection+0x7ce
ffffd000`255aa5f0 fffff801`21c3a892 tcpip!WfpAleReauthorizeOutboundConnection+0x190
ffffd000`255aa730 fffff801`21bd6881 tcpip!WfpAlepAuthorizeConnectCompletion+0x136
ffffd000`255aa830 fffff801`21afa182 tcpip!WfpAleClassify+0xcdb91
ffffd000`255aa870 fffff801`21afa9c4 tcpip!WfpAlepReauthorizeOutboundConnection+0x7ce
ffffd000`255aa9f0 fffff801`21c3a892 tcpip!WfpAleReauthorizeOutboundConnection+0x190
ffffd000`255aab30 fffff801`21bd7a70 tcpip!WfpAlepAuthorizeConnectCompletion+0x136
ffffd000`255aac30 fffff801`21b45d77 tcpip!WfpAlepAuthorizeConnect+0x91970
ffffd000`255aae00 fffff801`21bbab56 tcpip!WfpAleAuthorizeConnect+0x667
ffffd000`255ab250 fffff801`21c12394 tcpip!InetInspectConnect+0x172
ffffd000`255ab320 fffff801`21b476a2 tcpip!TcpContinueCreateAndConnectEx+0x674
ffffd000`255ab420 fffff801`21b48dc5 tcpip!TcpContinueCreateAndConnect+0x17e
ffffd000`255ab450 fffff801`21b48578 tcpip!TcpCreateAndConnectTcbWorkQueueRoutine+0x341
ffffd000`255ab540 fffff801`22afd7a7 tcpip!TcpCreateAndConnectTcb+0x578
ffffd000`255ab670 fffff801`22af33b6 afd!AfdSuperConnect+0x48f
ffffd000`255ab7e0 fffff803`a7711e03 afd!AfdDispatchDeviceControl+0x66
ffffd000`255ab810 fffff803`a7712d36 nt!IopSynchronousServiceTail+0x32b
ffffd000`255ab8e0 fffff803`a76d89d2 nt!IopXxxControlFile+0xd86
ffffd000`255aba20 fffff803`a73cfbb3 nt!NtDeviceIoControlFile+0x56
ffffd000`255aba90 00007ff8`5ef4072a nt!KiSystemServiceCopyEnd+0x13
00000089`80d8e038 00000000`00000000 0x00007ff8`5ef4072a
We don't know whether if it's a bug in Avast, a bug in your networking drivers, or a combination of both. That's why I asked you to uninstall Avast TEMPORARILY for testing purposes, then update ALL (yes, all nine) networking drivers. If you're BSOD-free after that, you can reinstall Avast and see what happens.

I recommend you keep away from Kaspersky for now — Kaspersky is famous for causing BSODs!!!

If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#5 54M33R

54M33R
  • Topic Starter

  • Members
  • 18 posts
  • OFFLINE
  •  
  • Local time:03:47 AM

Posted 09 March 2017 - 03:30 PM

Now I am having another issue... I have no clue as which network drivers from HP for my laptop to install as some of these I apparently do not even have and may not even be supposed to be installed. Perhaps you could list them if they are in the Attachment somewhere.


Edited by 54M33R, 09 March 2017 - 03:38 PM.


#6 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 2,990 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:04:47 AM

Posted 09 March 2017 - 04:35 PM

Please upload MEMORY.DMP:

 

:step1: Upload MEMORY.DMP

• Press and hold the Windows Key + R on your keyboard at the same time.
• In the Run box, type in %WinDir% and hit Enter on your keyboard.
• Find the file MEMORY.DMP and copy/paste it on to your Desktop.
• Zip up MEMORY.DMP (use .ZIP please!!!) and upload it to a trustworthy file-sharing service.

 

This will allow me to see the potential networking drivers that were conflicting with avast!.


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#7 54M33R

54M33R
  • Topic Starter

  • Members
  • 18 posts
  • OFFLINE
  •  
  • Local time:03:47 AM

Posted 09 March 2017 - 08:02 PM

Alright here it is

https://www.dropbox.com/s/55vsv27rgd4zadw/MEMORY.zip?dl=0



#8 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 2,990 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:04:47 AM

Posted 09 March 2017 - 10:04 PM

I think your Intel® Centrino® Wireless-N 2230 driver is the culprit. **DOWNLOAD LINK**


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#9 54M33R

54M33R
  • Topic Starter

  • Members
  • 18 posts
  • OFFLINE
  •  
  • Local time:03:47 AM

Posted 10 March 2017 - 03:25 PM

I see it seems to be working fine, although any other alternative for Avast perhaps?



#10 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 2,990 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:04:47 AM

Posted 10 March 2017 - 03:31 PM

For the time being, I highly suggest you stick to Windows Defender until the weekend has passed. We need to see whether if the system is truly stable. I've seen a lot of cases in which all was well for a few hours, but in a few days we were back to square one.

 

Let's keep our fingers crossed. :)


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#11 54M33R

54M33R
  • Topic Starter

  • Members
  • 18 posts
  • OFFLINE
  •  
  • Local time:03:47 AM

Posted 10 March 2017 - 06:20 PM

Alrighty, then the Test shall begin. I will also add after updating the driver some time later I did encounter a BSOD and this was before avast was removed.


Edited by 54M33R, 10 March 2017 - 06:34 PM.


#12 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 2,990 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:04:47 AM

Posted 10 March 2017 - 09:17 PM

In the end, I guess it is Avast's fault. A new version of Avast was released fairly recently and has been a bit problematic.

 

Good luck!!


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users