BSOD netio, ntoskrnl, ndis i7 7700 GA b250m

Page 1 of 2 12 LastLast

  1. migssie
    Posts : 11
    Windows 10 1809
       New #1

    BSOD netio, ntoskrnl, ndis i7 7700 IRQL_NOT_LESS_OR_EQUAL


    So I've been plagued by blue screen for the past few weeks which happen randomly through out the day, sometimes I get blue screens just when I boot and sometimes I don't for hours.

    I upgraded my computer's mobo and processor then I started getting these BSODs. With that said Im sure nothing else in my computer is wrong cos I don't get any BSODs before. At first thought It might be software, but then I tried doing a fresh install but I still get BSODs no matter what. So I thought maybe it would be the board cos the BSODs keep pointing me to different drivers like netio.sys, ntoskrnl, ndis and etc. But that all changed when I tried my Processor on my friends board. I ran my processor on their system and I had a blue screen and couple of laughs just when the PC booted which led me to think that it might be the processor? I already ran Intel's Diagnostic tool but everything passed.

    It seems that I get blue screens when I download or make use of the internet. But it also happens so randomly so I'm not quite sure if that's it. Atleast I'm still able to use the computer and am able to squeeze out long gaming sessions SOMETIMES without BSODs (I'm typing this on the PC praying that I don't get a BSOD. Lol)

    Some of the troubleshooting I've done.
    1. Ran memtest. All Passed.
    2. Replaced RAM. Still BSOD.
    3. Tried a fresh install. Still get BSODs.
    4. Ran Intel's Diagnostic Tools. PASSED.
    5. Tried repasting just for LOLs. Nothing.
    6. Tried using other DRAM slots. Nothing.
    7. Tried my proc on my friends board. BSOD on netio.sys. TWICE. (A bad proc? )
    8. Tried running a system stability test with AIDA 64 stressing everything except the GPU for an hour but never had BSODs. (Whut?)

    I'm hoping for a second opinion, or hopefully a work around. I wont be able to RMA this proc since I bought it 2nd hand from a company closing down.

    Here are the files made by the tool you guys have. Only realized after posting since this is my first time posting hehe.
    Click here!

    Here are the latest dump files I got this morning (Already scanned by the tool).
    dumps.zip - Google Drive

    My PC specs.
    i7 7700 (running at stock. BIOS is at defaults)
    GA-b250m-HD3
    8gb RAM HyperX 2666 running at 2400
    Samsung 850 EVO 250gb SSD
    WD Black 1tb
    Seasonic G550 Semi Modular PSU 80+ Gold
    Zotac GTX 1060 3GB Mini
    Last edited by migssie; 31 Oct 2018 at 02:31. Reason: more relevant title
      My Computer
    Quote Quote

  3. migssie
    Posts : 11
    Windows 10 1809
    Thread Starter
       New #2

    Heres the data collected by the app. Its already in the link above. They're practically the same thing
      My Computer
    Quote Quote

  4. philc43
    Posts : 5,170
    64bit Win 10 Pro ver 21H2
       New #3

    Hello migssie and welcome to Tenforums!

    The recent crash dumps all suggest that there is a problem with the rt640x64.sys driver. This is for your Realtek Ethernet Adapter.

    The version you have installed is ver 10.31.828.2018

    Until Gigabyte provide a new driver I would go back to the one they provide on their website which is ver 10.026.0521.2018

    Code:
    0: kd> .load pde;!dpx
=========================================================================================
 PDE v11.3 - Copyright 2017 Andrew Richards
=========================================================================================
Start memory scan  : 0xffff9e0724d10ce8 ($csp)
End memory scan    : 0xffff9e0724d13000 (Kernel Stack Base)

               rsp : 0xffff9e0724d10ce8 : 0xfffff8075c270669 : nt!KiBugCheckDispatch+0x69
0xffff9e0724d10ce8 : 0xfffff8075c270669 : nt!KiBugCheckDispatch+0x69
0xffff9e0724d10d10 : 0xfffff804467724d1 : NETIO!KfdClassify2+0xb1
Unable to load image aswStm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswStm.sys
*** ERROR: Module load completed but symbols could not be loaded for aswStm.sys
0xffff9e0724d10e28 : 0xfffff8075c26ca8e : nt!KiPageFault+0x44e
0xffff9e0724d10e30 : 0xffff8801c44f3140 :  Trap @ ffff9e0724d10e30
0xffff9e0724d10f58 : 0xfffff8044525374c : tcpip!TlShimMarshalInTransportFields+0x148
0xffff9e0724d10f98 : 0xfffff804467724d1 : NETIO!KfdClassify2+0xb1
0xffff9e0724d10fc8 : 0xfffff80445208e2f : tcpip!WfpAleInsertEndpoint+0x93
0xffff9e0724d11018 : 0xfffff80445208d83 : tcpip!WfpAleQueryEndpointHandle+0x13
0xffff9e0724d11088 : 0xfffff8044520448c : tcpip!WfpTlShimInspectRecvTcpDatagram+0x7cc
0xffff9e0724d11258 : 0xfffff804451eeba3 : tcpip!TcpTcbReassemblyInsertSegment+0xff
0xffff9e0724d11338 : 0xfffff804451c3dcd : tcpip!InetInspectReceiveTcpDatagram+0x51d
0xffff9e0724d11428 : 0xfffff804451bdab4 : tcpip!ShimIpPacketInV4+0x74
0xffff9e0724d11478 : 0xfffff804451c1b3d : tcpip!TcpTcbReceive+0x10d
0xffff9e0724d116c8 : 0xfffff804451c10d3 : tcpip!TcpMatchReceive+0x213
0xffff9e0724d11840 : 0xfffff804453ac280 : tcpip!Ipv4Global
Unable to load image aswHdsKe.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswHdsKe.sys
*** ERROR: Module load completed but symbols could not be loaded for aswHdsKe.sys
0xffff9e0724d118f8 : 0xfffff804451c0dc7 : tcpip!TcpValidateReceive+0xc7
0xffff9e0724d11998 : 0xfffff804451c0184 : tcpip!TcpReceive+0x304
0xffff9e0724d119d8 : 0xfffff8075c0189f5 : hal!HalpApicRequestInterrupt+0x95
0xffff9e0724d119e8 : 0xfffff8044676219c : NETIO!WfpNblInfoDestroyIfUnused+0xbc
*** WARNING: Unable to verify timestamp for rt640x64.sys
*** ERROR: Module load completed but symbols could not be loaded for rt640x64.sys
0xffff9e0724d11a58 : 0xfffff804453ac280 : tcpip!Ipv4Global
0xffff9e0724d11a78 : 0xfffff804453ac5e8 : tcpip!Ipv4Global+0x368
0xffff9e0724d11a98 : 0xfffff80445217732 : tcpip!TcpNlClientReceiveDatagrams+0x22
0xffff9e0724d11aa8 : 0xfffff8044676829a : NETIO!KfdClassify+0x3ba
0xffff9e0724d11ad8 : 0xfffff804451bdf92 : tcpip!IppDeliverListToProtocol+0x62
0xffff9e0724d11b18 : 0xfffff804456125e9 : Wdf01000!imp_WdfSpinLockRelease+0x79
0xffff9e0724d11b48 : 0xfffff8075c019ae6 : hal!HalPerformEndOfInterrupt+0x16
0xffff9e0724d11ba8 : 0xfffff804451bdb42 : tcpip!IppProcessDeliverList+0x62
0xffff9e0724d11bd8 : 0xfffff804453ac280 : tcpip!Ipv4Global
0xffff9e0724d11bf0 : 0xfffff804453ac280 : tcpip!Ipv4Global
0xffff9e0724d11c18 : 0xfffff804451bce3a : tcpip!IppReceiveHeaderBatch+0x22a
0xffff9e0724d11cb8 : 0xfffff804451fff4f : tcpip!Ipv4pValidateNetBuffer+0xcf
0xffff9e0724d11d00 : 0xfffff804453ac280 : tcpip!Ipv4Global
0xffff9e0724d11d18 : 0xfffff804451be303 : tcpip!IppFlcReceivePacketsCore+0x323
0xffff9e0724d11d20 : 0xfffff804453ac280 : tcpip!Ipv4Global
0xffff9e0724d11d80 : 0xfffff804453ac280 : tcpip!Ipv4Global
0xffff9e0724d11e38 : 0xfffff80445201745 : tcpip!IpFlcReceivePreValidatedPackets+0x965
0xffff9e0724d11e58 : 0xfffff80445219400 : tcpip!IppCopyPacket+0x1e0
0xffff9e0724d11eb8 : 0xfffff8044521c551 : tcpip!FlpValidateNetBufferListChain+0x4b1
0xffff9e0724d11ec8 : 0xfffff804453ac280 : tcpip!Ipv4Global
0xffff9e0724d11f70 : 0xfffff804453b486a : tcpip!AddressFamilyInformation+0x2
0xffff9e0724d12028 : 0xfffff804452031b0 : tcpip!FlpReturnNetBufferListChain
0xffff9e0724d12058 : 0xfffff8044521c037 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0x127
0xffff9e0724d120c0 : 0xfffff804452031b0 : tcpip!FlpReturnNetBufferListChain
0xffff9e0724d120f8 : 0xfffff8075c114a58 : nt!KeQueryCurrentStackInformation+0x68
0xffff9e0724d12128 : 0xfffff8075c113280 : nt!KiExpandKernelStackAndCalloutSwitchStack+0x100
0xffff9e0724d12178 : 0xfffff8044521bf10 : tcpip!FlReceiveNetBufferListChainCalloutRoutine
0xffff9e0724d12198 : 0xfffff8075c113118 : nt!KeExpandKernelStackAndCalloutInternal+0x78
0xffff9e0724d12208 : 0xfffff8075c11308d : nt!KeExpandKernelStackAndCalloutEx+0x1d
0xffff9e0724d12210 : 0xfffff8044521bf10 : tcpip!FlReceiveNetBufferListChainCalloutRoutine
0xffff9e0724d12248 : 0xfffff8044520042e : tcpip!FlReceiveNetBufferListChain+0x2be
0xffff9e0724d12268 : 0xfffff804455181d6 : wfplwfs!L2RefreshFlow+0xaa
0xffff9e0724d12278 : 0xfffff80445515705 : wfplwfs!L2ProcessClassifyOut+0xb5
0xffff9e0724d122a8 : 0xfffff804455193bc : wfplwfs!L2p802_3IsNblPermitted+0x20c
0xffff9e0724d122f8 : 0xfffff804452031b0 : tcpip!FlpReturnNetBufferListChain
0xffff9e0724d123a8 : 0xfffff8044551915d : wfplwfs!L2802_3IsNetBufferListPermitted+0x115
0xffff9e0724d12448 : 0xfffff80445012781 : ndis!ndisMIndicateNetBufferListsToOpen+0x221
0xffff9e0724d12478 : 0xfffff80445017a51 : ndis!NdisFIndicateReceiveNetBufferLists+0x71
0xffff9e0724d12518 : 0xfffff8044501239d : ndis!ndisMTopReceiveNetBufferLists+0x23d
0xffff9e0724d12590 : 0xfffff80445012160 : ndis!ndisMTopReceiveNetBufferLists
0xffff9e0724d125a0 : 0xfffff80445012160 : ndis!ndisMTopReceiveNetBufferLists
0xffff9e0724d125a8 : 0xfffff804450177c3 : ndis!ndisCallReceiveHandler+0x43
0xffff9e0724d125f8 : 0xfffff80445015087 : ndis!NdisMIndicateReceiveNetBufferLists+0x5b7
0xffff9e0724d12618 : 0xfffff8075c19a2a2 : nt!KiUpdateSpeculationControl+0x1e2
0xffff9e0724d126d8 : 0xfffff80445011720 : ndis!ndisMSendCompleteNetBufferListsInternal
0xffff9e0724d126e8 : 0xfffff8075c1bcc79 : nt!KeFlushIoBuffers+0x49
0xffff9e0724d12760 : 0xfffff80445612570 : Wdf01000!imp_WdfSpinLockRelease
0xffff9e0724d12780 : 0xfffff80445612570 : Wdf01000!imp_WdfSpinLockRelease
0xffff9e0724d12840 : 0xfffff804456124c0 : Wdf01000!imp_WdfSpinLockAcquire
0xffff9e0724d12878 : 0xfffff804456125e9 : Wdf01000!imp_WdfSpinLockRelease+0x79
0xffff9e0724d12928 : 0xfffff80445021183 : ndis!ndisQueuedMiniportDpcWorkItem+0x193
0xffff9e0724d12a38 : 0xfffff8044502fd39 : ndis!ndisReceiveWorkerThread+0x189
0xffff9e0724d12a50 : 0xfffff8044502fb00 : ndis!ndisOidPreSupportedList+0x130
0xffff9e0724d12aa8 : 0xfffff8075c19a2a2 : nt!KiUpdateSpeculationControl+0x1e2
0xffff9e0724d12ad8 : 0xfffff8075c226452 : nt!EtwTraceContextSwap+0xb2
0xffff9e0724d12b08 : 0xfffff8075c1cf6c5 : nt!PspSystemThreadStartup+0x55
0xffff9e0724d12b20 : 0xfffff8044502fbb0 : ndis!ndisReceiveWorkerThread
0xffff9e0724d12b50 : 0xfffff8075c58f400 : nt!KiInitialThread
0xffff9e0724d12b58 : 0xfffff8075c26638c : nt!KiStartSystemThread+0x1c
0xffff9e0724d12b70 : 0xfffff8075c1cf670 : nt!PspSystemThreadStartup
      My Computers
    Quote Quote

  6. migssie
    Posts : 11
    Windows 10 1809
    Thread Starter
       New #4

    philc43 said:
    Hello migssie and welcome to Tenforums!

    The recent crash dumps all suggest that there is a problem with the rt640x64.sys driver. This is for your Realtek Ethernet Adapter.

    The version you have installed is ver 10.31.828.2018

    Until Gigabyte provide a new driver I would go back to the one they provide on their website which is ver 10.026.0521.2018

    Code:
    0: kd> .load pde;!dpx
=========================================================================================
 PDE v11.3 - Copyright 2017 Andrew Richards
=========================================================================================
Start memory scan  : 0xffff9e0724d10ce8 ($csp)
End memory scan    : 0xffff9e0724d13000 (Kernel Stack Base)

               rsp : 0xffff9e0724d10ce8 : 0xfffff8075c270669 : nt!KiBugCheckDispatch+0x69
0xffff9e0724d10ce8 : 0xfffff8075c270669 : nt!KiBugCheckDispatch+0x69
0xffff9e0724d10d10 : 0xfffff804467724d1 : NETIO!KfdClassify2+0xb1
Unable to load image aswStm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswStm.sys
*** ERROR: Module load completed but symbols could not be loaded for aswStm.sys
0xffff9e0724d10e28 : 0xfffff8075c26ca8e : nt!KiPageFault+0x44e
0xffff9e0724d10e30 : 0xffff8801c44f3140 :  Trap @ ffff9e0724d10e30
0xffff9e0724d10f58 : 0xfffff8044525374c : tcpip!TlShimMarshalInTransportFields+0x148
0xffff9e0724d10f98 : 0xfffff804467724d1 : NETIO!KfdClassify2+0xb1
0xffff9e0724d10fc8 : 0xfffff80445208e2f : tcpip!WfpAleInsertEndpoint+0x93
0xffff9e0724d11018 : 0xfffff80445208d83 : tcpip!WfpAleQueryEndpointHandle+0x13
0xffff9e0724d11088 : 0xfffff8044520448c : tcpip!WfpTlShimInspectRecvTcpDatagram+0x7cc
0xffff9e0724d11258 : 0xfffff804451eeba3 : tcpip!TcpTcbReassemblyInsertSegment+0xff
0xffff9e0724d11338 : 0xfffff804451c3dcd : tcpip!InetInspectReceiveTcpDatagram+0x51d
0xffff9e0724d11428 : 0xfffff804451bdab4 : tcpip!ShimIpPacketInV4+0x74
0xffff9e0724d11478 : 0xfffff804451c1b3d : tcpip!TcpTcbReceive+0x10d
0xffff9e0724d116c8 : 0xfffff804451c10d3 : tcpip!TcpMatchReceive+0x213
0xffff9e0724d11840 : 0xfffff804453ac280 : tcpip!Ipv4Global
Unable to load image aswHdsKe.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswHdsKe.sys
*** ERROR: Module load completed but symbols could not be loaded for aswHdsKe.sys
0xffff9e0724d118f8 : 0xfffff804451c0dc7 : tcpip!TcpValidateReceive+0xc7
0xffff9e0724d11998 : 0xfffff804451c0184 : tcpip!TcpReceive+0x304
0xffff9e0724d119d8 : 0xfffff8075c0189f5 : hal!HalpApicRequestInterrupt+0x95
0xffff9e0724d119e8 : 0xfffff8044676219c : NETIO!WfpNblInfoDestroyIfUnused+0xbc
*** WARNING: Unable to verify timestamp for rt640x64.sys
*** ERROR: Module load completed but symbols could not be loaded for rt640x64.sys
0xffff9e0724d11a58 : 0xfffff804453ac280 : tcpip!Ipv4Global
0xffff9e0724d11a78 : 0xfffff804453ac5e8 : tcpip!Ipv4Global+0x368
0xffff9e0724d11a98 : 0xfffff80445217732 : tcpip!TcpNlClientReceiveDatagrams+0x22
0xffff9e0724d11aa8 : 0xfffff8044676829a : NETIO!KfdClassify+0x3ba
0xffff9e0724d11ad8 : 0xfffff804451bdf92 : tcpip!IppDeliverListToProtocol+0x62
0xffff9e0724d11b18 : 0xfffff804456125e9 : Wdf01000!imp_WdfSpinLockRelease+0x79
0xffff9e0724d11b48 : 0xfffff8075c019ae6 : hal!HalPerformEndOfInterrupt+0x16
0xffff9e0724d11ba8 : 0xfffff804451bdb42 : tcpip!IppProcessDeliverList+0x62
0xffff9e0724d11bd8 : 0xfffff804453ac280 : tcpip!Ipv4Global
0xffff9e0724d11bf0 : 0xfffff804453ac280 : tcpip!Ipv4Global
0xffff9e0724d11c18 : 0xfffff804451bce3a : tcpip!IppReceiveHeaderBatch+0x22a
0xffff9e0724d11cb8 : 0xfffff804451fff4f : tcpip!Ipv4pValidateNetBuffer+0xcf
0xffff9e0724d11d00 : 0xfffff804453ac280 : tcpip!Ipv4Global
0xffff9e0724d11d18 : 0xfffff804451be303 : tcpip!IppFlcReceivePacketsCore+0x323
0xffff9e0724d11d20 : 0xfffff804453ac280 : tcpip!Ipv4Global
0xffff9e0724d11d80 : 0xfffff804453ac280 : tcpip!Ipv4Global
0xffff9e0724d11e38 : 0xfffff80445201745 : tcpip!IpFlcReceivePreValidatedPackets+0x965
0xffff9e0724d11e58 : 0xfffff80445219400 : tcpip!IppCopyPacket+0x1e0
0xffff9e0724d11eb8 : 0xfffff8044521c551 : tcpip!FlpValidateNetBufferListChain+0x4b1
0xffff9e0724d11ec8 : 0xfffff804453ac280 : tcpip!Ipv4Global
0xffff9e0724d11f70 : 0xfffff804453b486a : tcpip!AddressFamilyInformation+0x2
0xffff9e0724d12028 : 0xfffff804452031b0 : tcpip!FlpReturnNetBufferListChain
0xffff9e0724d12058 : 0xfffff8044521c037 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0x127
0xffff9e0724d120c0 : 0xfffff804452031b0 : tcpip!FlpReturnNetBufferListChain
0xffff9e0724d120f8 : 0xfffff8075c114a58 : nt!KeQueryCurrentStackInformation+0x68
0xffff9e0724d12128 : 0xfffff8075c113280 : nt!KiExpandKernelStackAndCalloutSwitchStack+0x100
0xffff9e0724d12178 : 0xfffff8044521bf10 : tcpip!FlReceiveNetBufferListChainCalloutRoutine
0xffff9e0724d12198 : 0xfffff8075c113118 : nt!KeExpandKernelStackAndCalloutInternal+0x78
0xffff9e0724d12208 : 0xfffff8075c11308d : nt!KeExpandKernelStackAndCalloutEx+0x1d
0xffff9e0724d12210 : 0xfffff8044521bf10 : tcpip!FlReceiveNetBufferListChainCalloutRoutine
0xffff9e0724d12248 : 0xfffff8044520042e : tcpip!FlReceiveNetBufferListChain+0x2be
0xffff9e0724d12268 : 0xfffff804455181d6 : wfplwfs!L2RefreshFlow+0xaa
0xffff9e0724d12278 : 0xfffff80445515705 : wfplwfs!L2ProcessClassifyOut+0xb5
0xffff9e0724d122a8 : 0xfffff804455193bc : wfplwfs!L2p802_3IsNblPermitted+0x20c
0xffff9e0724d122f8 : 0xfffff804452031b0 : tcpip!FlpReturnNetBufferListChain
0xffff9e0724d123a8 : 0xfffff8044551915d : wfplwfs!L2802_3IsNetBufferListPermitted+0x115
0xffff9e0724d12448 : 0xfffff80445012781 : ndis!ndisMIndicateNetBufferListsToOpen+0x221
0xffff9e0724d12478 : 0xfffff80445017a51 : ndis!NdisFIndicateReceiveNetBufferLists+0x71
0xffff9e0724d12518 : 0xfffff8044501239d : ndis!ndisMTopReceiveNetBufferLists+0x23d
0xffff9e0724d12590 : 0xfffff80445012160 : ndis!ndisMTopReceiveNetBufferLists
0xffff9e0724d125a0 : 0xfffff80445012160 : ndis!ndisMTopReceiveNetBufferLists
0xffff9e0724d125a8 : 0xfffff804450177c3 : ndis!ndisCallReceiveHandler+0x43
0xffff9e0724d125f8 : 0xfffff80445015087 : ndis!NdisMIndicateReceiveNetBufferLists+0x5b7
0xffff9e0724d12618 : 0xfffff8075c19a2a2 : nt!KiUpdateSpeculationControl+0x1e2
0xffff9e0724d126d8 : 0xfffff80445011720 : ndis!ndisMSendCompleteNetBufferListsInternal
0xffff9e0724d126e8 : 0xfffff8075c1bcc79 : nt!KeFlushIoBuffers+0x49
0xffff9e0724d12760 : 0xfffff80445612570 : Wdf01000!imp_WdfSpinLockRelease
0xffff9e0724d12780 : 0xfffff80445612570 : Wdf01000!imp_WdfSpinLockRelease
0xffff9e0724d12840 : 0xfffff804456124c0 : Wdf01000!imp_WdfSpinLockAcquire
0xffff9e0724d12878 : 0xfffff804456125e9 : Wdf01000!imp_WdfSpinLockRelease+0x79
0xffff9e0724d12928 : 0xfffff80445021183 : ndis!ndisQueuedMiniportDpcWorkItem+0x193
0xffff9e0724d12a38 : 0xfffff8044502fd39 : ndis!ndisReceiveWorkerThread+0x189
0xffff9e0724d12a50 : 0xfffff8044502fb00 : ndis!ndisOidPreSupportedList+0x130
0xffff9e0724d12aa8 : 0xfffff8075c19a2a2 : nt!KiUpdateSpeculationControl+0x1e2
0xffff9e0724d12ad8 : 0xfffff8075c226452 : nt!EtwTraceContextSwap+0xb2
0xffff9e0724d12b08 : 0xfffff8075c1cf6c5 : nt!PspSystemThreadStartup+0x55
0xffff9e0724d12b20 : 0xfffff8044502fbb0 : ndis!ndisReceiveWorkerThread
0xffff9e0724d12b50 : 0xfffff8075c58f400 : nt!KiInitialThread
0xffff9e0724d12b58 : 0xfffff8075c26638c : nt!KiStartSystemThread+0x1c
0xffff9e0724d12b70 : 0xfffff8075c1cf670 : nt!PspSystemThreadStartup
    Thank you very much for the reply. I'll revert back to the old drivers and post the results. And btw here are some fresh and crispy new minidumps. I got a new BSOD for ntfs.sys btw. I hope these help locate the problem. Thanks again!
      My Computer
    Quote Quote

  7. migssie
    Posts : 11
    Windows 10 1809
    Thread Starter
       New #5

    New BSOD last night. Already reverted my driver.
      My Computer
    Quote Quote

  8. philc43
    Posts : 5,170
    64bit Win 10 Pro ver 21H2
       New #6

    This latest BSOD looks different. I can not tell from the crash dump what might have caused it, all I can see is that it happened while the esrv_svc.exe process was running. This is something to do with an Intel monitoring service I think.

    Could you try the beta log collector provided at the end of the BSOD Posting Instructions and I will see if that gives more information. May be a little while before I can get around to checking it though.
      My Computers
    Quote Quote

  9. migssie
    Posts : 11
    Windows 10 1809
    Thread Starter
       New #7

    Here is the zip made by the beta log collector. And btw I've had two more blue screens a while ago. Thanks again for the reply!
      My Computer
    Quote Quote

  10. zbook
    Posts : 42,120
    windows 10 professional version 1607 build 14393.969 64 bit
       New #8

    In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
    a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery into the thread.
    b) > on the advanced tab under performance > click on settings > under performance options > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory tab into the thread


    Open Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread

    In case there are any problems posting images please use share links (one drive, drop box, or google drive)

    There are settings for BSOD crashes that can be modified.
    The current setting is small memory dump and automatic restart.
    With these settings there were multiple mini dumps but no memory dump.

    After making these changes please post the updated settings:
    Change small memory dump to automatic memory dump.
    Uncheck automatic restart.

    If automatic restart is checked it can be easy to miss BSOD.
    With automatic restart unchecked there should be a bsod windows with bugcheck and : (
    Sometimes a misbehaving driver may be displayed in the form *.sys
    At the beginning of a bsod a % counter may be seen.
    If the % counter is seen please allow it to rise to 100% before rebooting so that there is sufficient time to create the dump files.

    Run HD Tune: (free edition) (on all drives)
    https://www.hdtune.com/
    Post images into the thread for test results on these tabs:
    a) Health (SMART)
    b) Benchmark
    c) Full error scan

    In the mini dump files there was one additional misbehaving driver identified in the debugging.

    Uninstall Avast AV using the applicable uninstall tool:
    Avast Uninstall Utility | Download aswClear for Avast Removal

    After uninstall Avast make sure that Windows defender is on.

    If there are any BSOD:
    a) post a new BETA zip into the thread
    b) open file explorer > this PC > C: > in the right upper corner search for: C:\windows\memory.dmp > if the file size is < 1.5 GB then zip and post a share link into the thread using one drive, drop box, or google drive.
      My Computer
    Quote Quote

  12. migssie
    Posts : 11
    Windows 10 1809
    Thread Starter
       New #9

    Thats a shame. Ive been using Avast for about 9 years. But ok. Uninstalled.
    Also changed to automatic memory dump.

    heres the screenshots you requested.
    Attachment 210802
    Attachment 210803
    Attachment 210804

    hdd tune for my ssd

    Attachment 210805
    Attachment 210806
    Attachment 210807

    hdd tune for my hdd

    Attachment 210808
    Attachment 210809
    Attachment 210810

    Ill keep you guys posted if there are any more bsods. The last one was before your reply @zbook so I havent configured the system with automatic dumps yet. Ill keep you guys posted. Thanks for the Replies!
      My Computer
    Quote Quote

  13. zbook
    Posts : 42,120
    windows 10 professional version 1607 build 14393.969 64 bit
       New #10

    1) Once the computer environment is stable ( no BSOD for one week or more) the Avast AV can be reinstalled.

    2) For startup and recovery system failure:
    a) uncheck automatically restart
    b) change small memory dump to automatic memory dump
    c) reboot to keep settings

    3) For Ccleaner uncheck:
    a) Memory Dumps
    b) Windows log files
      My Computer
    Quote Quote

 

  Related Discussions
Over the past month or so I've been getting freezes for about 15-30 seconds, it happens relatively randomly. Specs: 32GB RAM Ryzen 5 2600 ASUS B450 Strix F I had ESET installed, which seems to have replaced the ndis.sys BSOD or with...
NETIO.SYS/ntoskrnl.exe BSOD error
in BSOD Crashes and Debugging

~4 users at my company experience seemingly random BSODs. Windows Event Logs show that a bugcheck is causing the unexpected shutdowns: 0x0000003B (0x00000000c0000005, 0xfffff801c2770bc0, 0xffffd480a493df40, 0x0000000000000000). I have ran Windows...
BSOD caused by ntoskrnl.exe and ndis.sys
in BSOD Crashes and Debugging

Hi, I just moved, this weekend from a HDD to a SSD and installed a watercooling for my CPU. After cloning my disk, I had multiple BSOD, so I decided to use the MediaCreationTool.exe to do a new clean install. But I'm still getting BSOD. It...
Hello, A friend of mine has been having some trouble with BSODs recently, I have been attempting to assist them with their issue. Recently we have used Windows 10's "Reset" feature selecting all options to remove all files from both the boot SSD...
Windows 10 Pro x64, browsing Facebook in Chrome when I got a BSOD for system service exception netio.sys Following next login I ran BlueScreenView and it seems to think ntoskrnl.exe is related. Googling leads me to solutions mentioning ASUS ROG...
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 11:09.
Find Us




Windows 10 Forums