S Saiber77 Well-known member Joined Jul 15, 2015 Posts 86 Location Redwoods California Jul 28, 2015 #1 Keep getting a persistent NDIS BSOD which when researched on the web tells me it is related to the Atheros NIC driver, it's not... Even with no NIC drivers installed it will still BSOD and restart. Acer Aspire 7750, Atheros AR8151 PCI-E Gigabit Ethernet Controller (NDIS 6.20), View attachment 14841View attachment BlueScreenView.txt Attaching the BSOD Dump zip and a Bluescreenview dump, can't attach a perfmon report as I keep getting a "The Data Collector Set or one of its dependencies is already in use." error message and consequent searches on the net about this error are obscure at best and generally in reference to a server... needless to say it is ineffectual and irrelevant to my particular issue. Any help with that and I'll gladly generate and post that report... TIA! :grin1:
Keep getting a persistent NDIS BSOD which when researched on the web tells me it is related to the Atheros NIC driver, it's not... Even with no NIC drivers installed it will still BSOD and restart. Acer Aspire 7750, Atheros AR8151 PCI-E Gigabit Ethernet Controller (NDIS 6.20), View attachment 14841View attachment BlueScreenView.txt Attaching the BSOD Dump zip and a Bluescreenview dump, can't attach a perfmon report as I keep getting a "The Data Collector Set or one of its dependencies is already in use." error message and consequent searches on the net about this error are obscure at best and generally in reference to a server... needless to say it is ineffectual and irrelevant to my particular issue. Any help with that and I'll gladly generate and post that report... TIA! :grin1:
jcgriff2 Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.) Staff member Joined Feb 19, 2012 Posts 21,541 Location New Jersey Shore Jul 30, 2015 #2 Hi. . . Both dumps had the same bugcheck - 0x109 - kernel corruption Failing instruction line: fffff8800171fdca - ndis!ndisGetMiniportOffloadCapabilty+66a Click to expand... No idea what it's trying to do there, but ndis.sys is a Microsoft Windows driver and is not the cause here; it's merely listed as a default. http://www.sysnative.com/drivers/driver.php?id=ndis.sys See if Driver Verifier flags any 3rd party drivers - https://www.sysnative.com/forums/bs...er-bsod-related-windows-10-8-1-8-7-vista.html Don't worry about PERFMON at this time. Regards. . . jcgriff2
Hi. . . Both dumps had the same bugcheck - 0x109 - kernel corruption Failing instruction line: fffff8800171fdca - ndis!ndisGetMiniportOffloadCapabilty+66a Click to expand... No idea what it's trying to do there, but ndis.sys is a Microsoft Windows driver and is not the cause here; it's merely listed as a default. http://www.sysnative.com/drivers/driver.php?id=ndis.sys See if Driver Verifier flags any 3rd party drivers - https://www.sysnative.com/forums/bs...er-bsod-related-windows-10-8-1-8-7-vista.html Don't worry about PERFMON at this time. Regards. . . jcgriff2
Jared Sysnative Staff, BSOD Kernel Dump Expert Joined Feb 3, 2014 Posts 1,591 Jul 30, 2015 #3 Code: 0: kd> .bugcheck Bugcheck code 00000109 Arguments a3a039d8`96ea8aa6 b3b7465e`e9686884 fffff880`0171f760 00000000`00000001 0: kd> !chkimg -lo 50 -d !ndis fffff8800171fdca - ndis!ndisGetMiniportOffloadCapabilty+66a [ 00:80 ] 1 error : !ndis (fffff8800171fdca) ndis!ndisGetMiniportOffloadCapability I believe will take a look at how much of the stack it can unload to the network controller, which I presume will send the network packets via the NIC. What appears to have happened is as NDIS checked the stack, data corruption appear, which results in a 0x109 bugcheck. A data structure has most likely been corrupted by a 3rd party driver. Driver Verifier, as linked by jcgriff2 would be the best shot, then testing RAM for any errors.
Code: 0: kd> .bugcheck Bugcheck code 00000109 Arguments a3a039d8`96ea8aa6 b3b7465e`e9686884 fffff880`0171f760 00000000`00000001 0: kd> !chkimg -lo 50 -d !ndis fffff8800171fdca - ndis!ndisGetMiniportOffloadCapabilty+66a [ 00:80 ] 1 error : !ndis (fffff8800171fdca) ndis!ndisGetMiniportOffloadCapability I believe will take a look at how much of the stack it can unload to the network controller, which I presume will send the network packets via the NIC. What appears to have happened is as NDIS checked the stack, data corruption appear, which results in a 0x109 bugcheck. A data structure has most likely been corrupted by a 3rd party driver. Driver Verifier, as linked by jcgriff2 would be the best shot, then testing RAM for any errors.
S Saiber77 Well-known member Joined Jul 15, 2015 Posts 86 Location Redwoods California Jul 30, 2015 #4 Thanks guys, I will get on that ASAP and let you know.
S Saiber77 Well-known member Joined Jul 15, 2015 Posts 86 Location Redwoods California Aug 4, 2015 #5 So here are the zipped results from the sysnative file collection app... hope they yield some results, I'm off to run a memtest. TIAView attachment 15079
So here are the zipped results from the sysnative file collection app... hope they yield some results, I'm off to run a memtest. TIAView attachment 15079
Jared Sysnative Staff, BSOD Kernel Dump Expert Joined Feb 3, 2014 Posts 1,591 Aug 4, 2015 #6 These are old dumps, with the latest one from the 30th of July. Check in C:\Windows\MEMORY.dmp to see if there's a file, if there is, check its timestamp.
These are old dumps, with the latest one from the 30th of July. Check in C:\Windows\MEMORY.dmp to see if there's a file, if there is, check its timestamp.
S Saiber77 Well-known member Joined Jul 15, 2015 Posts 86 Location Redwoods California Aug 4, 2015 #7 Ok, well... not sure if there is a need anymore as I took your advice. I ran Hiren's BCD 15.2 and ran memtest86+, showing RAM errors... I'll replace the RAM and let you know if it resolves the issue. Still want the memory.dmp file?
Ok, well... not sure if there is a need anymore as I took your advice. I ran Hiren's BCD 15.2 and ran memtest86+, showing RAM errors... I'll replace the RAM and let you know if it resolves the issue. Still want the memory.dmp file?
Jared Sysnative Staff, BSOD Kernel Dump Expert Joined Feb 3, 2014 Posts 1,591 Aug 4, 2015 #8 I'll take a look anyway, but that would have been the next step anyway, good work.
S Saiber77 Well-known member Joined Jul 15, 2015 Posts 86 Location Redwoods California Aug 5, 2015 #9 Sorry for taking so long, here is the memory dump. Thanks! Saiber77
jcgriff2 Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.) Staff member Joined Feb 19, 2012 Posts 21,541 Location New Jersey Shore Aug 5, 2015 #10 Did you replace the RAM? Any new BSODs since removing the bad RAM stick?
S Saiber77 Well-known member Joined Jul 15, 2015 Posts 86 Location Redwoods California Aug 5, 2015 #11 Yeah the RAM is replaced, ran memtest on the new ram to determine if it was a motherboard issue or indeed the RAM module, test is clean. Computer runs normally and have not experienced any BSOD's since but still 'bench testing" it... Did you find anything of note in the dump file ? TIA
Yeah the RAM is replaced, ran memtest on the new ram to determine if it was a motherboard issue or indeed the RAM module, test is clean. Computer runs normally and have not experienced any BSOD's since but still 'bench testing" it... Did you find anything of note in the dump file ? TIA
S Saiber77 Well-known member Joined Jul 15, 2015 Posts 86 Location Redwoods California Aug 7, 2015 #12 I guess I'll just mark this as Solved, I haven't had any problems since I replaced the RAM. Thanks for the help guys! :grin1:
I guess I'll just mark this as Solved, I haven't had any problems since I replaced the RAM. Thanks for the help guys! :grin1: