BSOD - ndiswan.sys
Keep getting a BSOD which reports DRIVER IRQL NOT LESS OR EQUAL and ndiswan.sys Address 93A4CDDCHave identified ndiswan as MS PPP Framing Driver (Strong Encryption) version 6.1.7000.0It is not a regular occurance but iritatingly intermittant.Any ideas???
February 17th, 2009 5:02pm

Good Morning Wolfrace,Are you running a Virtual Machine on this computer? I want to advise you to update the Drivers for your Network Adapater, but I am not sure that would take care of the issue. Have you recently installed anything or updated anything? Please follow up with me at your earliest convenience.Thank you,Aaron GriffinMicrosoft Support
Free Windows Admin Tool Kit Click here and download it now
February 17th, 2009 7:28pm

Not a virtual machine.Nothing installed just automatic updates running. It does not happen at specific times, its happened when idling, on the web, on games, using Office or watching videos. Irritating.
February 18th, 2009 4:04pm

This is likely being caused by an interop problem between the ndiswan driver and a third party filter driver. I see a few bugs on this that we've fixed or worked around with the vendors. If you'd like me to confirm and tell you the driver, I will need your BUCKET ID information that is logged for the crash. You should see it in the Reliability Monitor for your crash (start -> search bar -> reliability monitor -> find one of these crashes -> copy/paste the whole page of data, especially the bucket ID. I can confirm with a debugger, then give you some advise on the probable driver cuplrit.If you do not see the crash there, you will need to open the memory dump being created in a debugger, align symbols, run a !analyze -v, and paste in the output here. Download here: http://www.microsoft.com/whdc/devtools/debugging/default.mspxSymbols here: http://www.microsoft.com/whdc/devtools/debugging/debugstart.mspx#aNed Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team
Free Windows Admin Tool Kit Click here and download it now
February 19th, 2009 10:52pm

HiYou can try solving this issue by disabling power management for NIC.Also make sure PCI-E clock is set to 100 in bios
February 19th, 2009 11:08pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics