The problem I'm having seems related to the problem at http://social.technet.microsoft.com/Forums/en-US/w7itproappcompat/thread/53a5d149-0258-4853-a153-cf53c5681110/. The only thing is I'm running Win 7 Ultimate SP1 x86, so the patch doesn't apply. I was running NOD ESET, now I'm running MS Security Essentials. In both cases I'm getting lots of BSOD, especially when accessing my Synology Diskstation. I've tried running verifier.exe and it reported the following: ndis.sys 0x85c78787 base 0x85c07000 date 0x4ce78937 STOP 0x000000c9 (0x00000226, 0x85c78787, 0xb98f4f68, 0x00000000) I have memory.dmp files being generated all the time, but don't know where to upload them to help me get a solution. I submit every error to Microsoft as Windows' request, but there is always no solution found. Does anyone have any suggestions here? Ironically my Vista machine has never had this problem. BTW this is a clean install on to an SSD from a machine that was shipped with Vista.

Hi, Based on the stop code, this is the bug check code for all Driver Verifier I/O Verification violations: Bug Check 0xC9: DRIVER_VERIFIER_IOMANAGER_VIOLATION It would be caused by a corrupted driver; to find the root cause, please upload the dump file and post the link here: Use SkyDrive to upload collected files Alex ZhaoPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I posted the file here: http://adservium.com/MEMORY.7z I believe it is related to Windows 7 accessing my Synology Diskstation. Once I stopped accessing my Synology NAS the comptuer stopped blue screening. My Vista machine can access the Synology with no problem. I originally had the default NIC drivers that came with Windows 7. After my machine started blue screening I installed the latest drivers from Intel for my 82566DM-2 adapter. The blue screening didn't go away. Thanks for your help.

Hi, This is mostly happens in Windows 7 64-bit Edition after UN-installing Anti-virus & Installing other Anti-virus... ndis.sys BSOD is caused due to TCP functionality problem, if WiFi driver crash, thr are several mini-ports in Device manager with yellow exclamation marks. This can be resolved by restoring system hive, located @ C:\Windows\System32\config\RegBack You have to boot PC offline & take a backup of System file from C:\Windows\System32\config then copy System from C:\Windows\System32\config\RegBack Paste it to C:\Windows\System32\config Turn off WiFi reboot. Once PC boots properly, update wireless card driver. --Harjit

That sounds like a very well thought-out solution, the only problem is this is a desktop with no WiFi running on Win7 32-bit. Does it still apply in this case?

yes indeed if you remembered to take back-up, it will not harm anything & it will still work

I don't see any devices in my Device Manager with yellow exclamation marks. I've even shown hidden devices. Additionally when I try to browse to c:\windows\system32\config I get a permission error.

I posted the file here: http://adservium.com/MEMORY.7z I believe it is related to Windows 7 accessing my Synology Diskstation. Once I stopped accessing my Synology NAS the comptuer stopped blue screening. My Vista machine can access the Synology with no problem. I originally had the default NIC drivers that came with Windows 7. After my machine started blue screening I installed the latest drivers from Intel for my 82566DM-2 adapter. The blue screening didn't go away. Thanks for your help. the Intel driver is the cause: Loaded symbol image file: e1e6232.sys Image path: \SystemRoot\system32\DRIVERS\e1e6232.sys Image name: e1e6232.sys Timestamp: Fri Mar 26 09:13:32 2010 ChildEBP RetAddr 82b2a414 82a6db85 nt!MiPfnReferenceCountIsZero+0x24 82b2a46c 82a7aad8 nt!MmUnlockPages+0x557 82b2a4a8 8b9e188d nt!IopfCompleteRequest+0x2cd 82b2a4c0 8c088444 tdx!TdxSendConnectionTlRequestComplete+0xbd 82b2a4e0 8c0b9d3a tcpip!TcpCompleteTcbSend+0x2e 82b2a53c 8c09d2d8 tcpip!TcpTcbReceive+0x2c4 82b2a5a4 8c09db0a tcpip!TcpMatchReceive+0x237 82b2a5f4 8c09db4b tcpip!TcpPreValidatedReceive+0x293 82b2a610 8c097e77 tcpip!TcpReceive+0x2d 82b2a620 8c0a00ab tcpip!TcpNlClientReceiveDatagrams+0x12 82b2a64c 8c09f9f6 tcpip!IppDeliverListToProtocol+0x49 82b2a66c 8c09ddb8 tcpip!IppProcessDeliverList+0x2a 82b2a6c4 8c09f89f tcpip!IppReceiveHeaderBatch+0x1fb 82b2a758 8c0adccc tcpip!IpFlcReceivePackets+0xbe5 82b2a7d4 8c0a82fe tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x746 82b2a808 82a8b654 tcpip!FlReceiveNetBufferListChainCalloutRoutine+0x11e 82b2a870 8c0a846c nt!KeExpandKernelStackAndCalloutEx+0x132 82b2a8ac 8bea318d tcpip!FlReceiveNetBufferListChain+0x7c 82b2a8e4 8be915be ndis!ndisMIndicateNetBufferListsToOpen+0x188 82b2a90c 8be914b2 ndis!ndisIndicateSortedNetBufferLists+0x4a 82b2aa88 8be3cc1d ndis!ndisMDispatchReceiveNetBufferLists+0x129 82b2aaa4 8be6d56a ndis!ndisMTopReceiveNetBufferLists+0x2d 82b2aac0 8be6d504 ndis!ndisFilterIndicateReceiveNetBufferLists+0x46 82b2aadc 91af2426 ndis!NdisFIndicateReceiveNetBufferLists+0x2f 82b2ab1c 8be91553 vpcnfltr!FilterReceiveNetBufferLists+0x45e 82b2ab44 8be3cc78 ndis!ndisMIndicateReceiveNetBufferListsInternal+0x62 82b2ab6c 921bf256 ndis!NdisMIndicateReceiveNetBufferLists+0x52 WARNING: Stack unwind information not available. Following frames may be wrong. 82b2abb4 921b982d e1e6232+0x7256 82b2abe8 921b9acf e1e6232+0x182d 82b2abf8 921b9b6a e1e6232+0x1acf 82b2ac10 8be91892 e1e6232+0x1b6a 82b2ac50 8be3ca0f ndis!ndisMiniportDpc+0xda 82b2ac78 82a7a1b5 ndis!ndisInterruptDpc+0xaf 82b2acd4 82a7a018 nt!KiExecuteAllDpcs+0xf9 82b2ad20 82a79e38 nt!KiRetireDpcList+0xd5"A programmer is just a tool which converts caffeine into code" Want to install RSAT on Windows 7 Sp1? Check my HowTo: http://www.msfn.org/board/index.php?showtopic=150221

Thanks. I've uninstalled that driver and started using the Microsoft provided driver again. I'm sure this will happen more, when it does, may I ask, how did you get that information from the memory.dmp file?

how did you get that information from the memory.dmp file? I opened the dmp file with Debugging tools for Windows: http://support.microsoft.com/kb/315263"A programmer is just a tool which converts caffeine into code" Want to install RSAT on Windows 7 Sp1? Check my HowTo: http://www.msfn.org/board/index.php?showtopic=150221