<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Topic &#x27;Re: ndis.sys crash on Server 2008 R2&#x27; in forum &#x27;No, I Will Not Fix Your #@$!! Computer&#x27; - dslreports.com</title>
<link>http://www.dslreports.com/forum/Re-ndissys-crash-on-Server-2008-R2-27721788</link>
<description></description>
<language>en</language>
<pubDate>Sun, 19 May 2013 11:55:34 EDT</pubDate>
<lastBuildDate>Sun, 19 May 2013 11:55:34 EDT</lastBuildDate>

<item>
<title>Re: ndis.sys crash on Server 2008 R2</title>
<link>http://www.dslreports.com/forum/Re-ndissys-crash-on-Server-2008-R2-27725835</link>
<description><![CDATA[exocet_cm posted : The firmware upgrade fixed the NDIS problems but still BSODs. She got nuked this morning.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-ndissys-crash-on-Server-2008-R2-27725835</guid>
<pubDate>Wed, 14 Nov 2012 08:36:24 EDT</pubDate>
</item>

<item>
<title>Re: ndis.sys crash on Server 2008 R2</title>
<link>http://www.dslreports.com/forum/Re-ndissys-crash-on-Server-2008-R2-27723876</link>
<description><![CDATA[exocet_cm posted : Holy sh*t firmware upgrade. Seems to be working fine now. I still don't know why it stopped after having been in use for a time now. The firmware route I pulled out of my a$$. Not sure why I thought of it but at 2:00 AM I thought "hmmm, firmware, I'll try it when I get up in a few hours". That was my last uphill charge with bayonets locked before I nuked it. <br><br>@JoelC707, this is one of two physical DCs. We virtualized a DC (the VM DC makes three). I have in the plans to demote this one and set up a second virtual DC (still three, one physical, two virtual), but my plans weren't meant to be put in place so soon.  :huh:<br><br>I think this firmware upgrade fixed it though. The gigabit NIC team had firmware 3.x.x and the upgrade was at 7.x.x.<br><br>Edit: Broadcom 5722 with driver version 15.4.0.17, firmware version 7.4.8. The connectivity was dying once BACS 4 was fully loaded and removing BACS 4 didn't fix it. Guess firmware was the route. <br><small>--<br>"I have measured out my life with coffee spoons..." - T.S Eliot<br> "I have often regretted my speech, never my silence." - Publilius Syrus<b><br> <b>Ma blog: &raquo;<A HREF="http://www.johndball.com" >www.johndball.com</A></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-ndissys-crash-on-Server-2008-R2-27723876</guid>
<pubDate>Tue, 13 Nov 2012 15:51:11 EDT</pubDate>
</item>

<item>
<title>Re: ndis.sys crash on Server 2008 R2</title>
<link>http://www.dslreports.com/forum/Re-ndissys-crash-on-Server-2008-R2-27723854</link>
<description><![CDATA[JoelC707 posted : This is one of three DCs? What else does it do? Unless this is a remote DC, needed for some HIGH load or something like that, do you really need a 3rd DC? If this is just a DC and you don't have a special need for it, I say dcpromo it and kill it. Easy way out  :D :p]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-ndissys-crash-on-Server-2008-R2-27723854</guid>
<pubDate>Tue, 13 Nov 2012 15:46:30 EDT</pubDate>
</item>

<item>
<title>Re: ndis.sys crash on Server 2008 R2</title>
<link>http://www.dslreports.com/forum/Re-ndissys-crash-on-Server-2008-R2-27723729</link>
<description><![CDATA[exocet_cm posted : <div class="bquote"><said>said by <a href="/profile/1349705" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1349705');">jimk</a>:</said><p>Do you have any software firewalls other than the native one that comes with Windows? If so, try removing them. I have seen this exact behavior in multiple occasions. The same thing applies to anything else that installs as a NDIS filter. I know you said nothing has been installed recently, but I have seen this kind of issue occur suddenly for no apparent reason.<br><br>If it is not an onboard NIC, do you have a spare you could try? Hardware issues are always a possibility.<br> </p></div>Yeah, both on-board. ESET threw an error in the event logs and I removed the AV but it didn't fix anything. I'll try the spare mobo but I have neither the time nor the patience to really troubleshoot it. I'm seriously contemplating making one of the connections active and removing the DC role the blowing it away and start with a fresh install. <br><small>--<br>"I have measured out my life with coffee spoons..." - T.S Eliot<br> "I have often regretted my speech, never my silence." - Publilius Syrus<b><br> <b>Ma blog: &raquo;<A HREF="http://www.johndball.com" >www.johndball.com</A></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-ndissys-crash-on-Server-2008-R2-27723729</guid>
<pubDate>Tue, 13 Nov 2012 15:16:49 EDT</pubDate>
</item>

<item>
<title>Re: ndis.sys crash on Server 2008 R2</title>
<link>http://www.dslreports.com/forum/Re-ndissys-crash-on-Server-2008-R2-27723492</link>
<description><![CDATA[jimk posted : Do you have any software firewalls other than the native one that comes with Windows? If so, try removing them. I have seen this exact behavior in multiple occasions. The same thing applies to anything else that installs as a NDIS filter. I know you said nothing has been installed recently, but I have seen this kind of issue occur suddenly for no apparent reason.<br><br>If it is not an onboard NIC, do you have a spare you could try? Hardware issues are always a possibility.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-ndissys-crash-on-Server-2008-R2-27723492</guid>
<pubDate>Tue, 13 Nov 2012 14:12:41 EDT</pubDate>
</item>

<item>
<title>Re: ndis.sys crash on Server 2008 R2</title>
<link>http://www.dslreports.com/forum/Re-ndissys-crash-on-Server-2008-R2-27723095</link>
<description><![CDATA[exocet_cm posted : <div class="bquote"><said>said by <a href="/profile/656685" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=656685');">drew</a>:</said><p>Possible hardware failure?<br><br>Also, are you sure that no patches were installed?<br> </p></div>Yeah, I had yet to approve the Windows updates and the other admin hadn't made any changes. I have a spare mobo for it, I guess I'll swap it and see?<br><small>--<br>"I have measured out my life with coffee spoons..." - T.S Eliot<br> "I have often regretted my speech, never my silence." - Publilius Syrus<b><br> <b>Ma blog: &raquo;<A HREF="http://www.johndball.com" >www.johndball.com</A></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-ndissys-crash-on-Server-2008-R2-27723095</guid>
<pubDate>Tue, 13 Nov 2012 12:30:38 EDT</pubDate>
</item>

<item>
<title>Re: ndis.sys crash on Server 2008 R2</title>
<link>http://www.dslreports.com/forum/Re-ndissys-crash-on-Server-2008-R2-27722444</link>
<description><![CDATA[drew posted : Possible hardware failure?<br><br>Also, are you sure that no patches were installed?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-ndissys-crash-on-Server-2008-R2-27722444</guid>
<pubDate>Tue, 13 Nov 2012 10:30:10 EDT</pubDate>
</item>

<item>
<title>Re: ndis.sys crash on Server 2008 R2</title>
<link>http://www.dslreports.com/forum/Re-ndissys-crash-on-Server-2008-R2-27722389</link>
<description><![CDATA[exocet_cm posted : <div class="bquote"><said>said by <a href="/profile/1197627" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1197627');">Modus</a>:</said><p>How do you know that ndis.sys caused the BSOD? Did you use BlueScreenView?<br> </p></div>Yeah, used it and it pulled the crash dump. Listed ndis.sys and since the crash networking hasn't worked.<br><small>--<br>"I have measured out my life with coffee spoons..." - T.S Eliot<br> "I have often regretted my speech, never my silence." - Publilius Syrus<b><br> <b>Ma blog: &raquo;<A HREF="http://www.johndball.com" >www.johndball.com</A></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-ndissys-crash-on-Server-2008-R2-27722389</guid>
<pubDate>Tue, 13 Nov 2012 10:18:46 EDT</pubDate>
</item>

<item>
<title>Re: ndis.sys crash on Server 2008 R2</title>
<link>http://www.dslreports.com/forum/Re-ndissys-crash-on-Server-2008-R2-27722383</link>
<description><![CDATA[Modus posted : How do you know that ndis.sys caused the BSOD? Did you use BlueScreenView?<br><small>--<br>Think Ahead. Learn More. Solve Now!</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-ndissys-crash-on-Server-2008-R2-27722383</guid>
<pubDate>Tue, 13 Nov 2012 10:16:58 EDT</pubDate>
</item>

<item>
<title>ndis.sys crash on Server 2008 R2</title>
<link>http://www.dslreports.com/forum/ndissys-crash-on-Server-2008-R2-27721788</link>
<description><![CDATA[exocet_cm posted : Ndis.sys caused one of our three DCs to BSOD earlier this evening (for the non-profit, not my regular job). Completely random and out of the blue. No new hardware or software installed. No system configuration changes .<br><br>We have Broadcom NICs with the latest drivers using BACS 4. Doing everything I could with the NICs has still not resolved the problem (remove, reinstall, new drivers, etc). <br><br>I removed the team and one NIC that I have configured will responded to network traffic for about 1 minute after the server reboots then stop responding to traffic. If I manually disable and enable the NIC it'll respond to traffic. Advanced functions with the NICs cause them to not respond to traffic at all.<br><br>Any ideas?<br><small>--<br>"I have measured out my life with coffee spoons..." - T.S Eliot<br> "I have often regretted my speech, never my silence." - Publilius Syrus<b><br> <b>Ma blog: &raquo;<A HREF="http://www.johndball.com" >www.johndball.com</A></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/ndissys-crash-on-Server-2008-R2-27721788</guid>
<pubDate>Tue, 13 Nov 2012 02:36:26 EDT</pubDate>
</item>

</channel>
</rss>
