Once I have mapped drives, I get Blue Screen of Death in fairly short order. After system reboots, BSOD occurs again within 5 to 10 minutes. If I disconnect the mappings, I can run Win 7 for hours with no problems.My attempted mappings are (1) 3 mappings to admin shares for drives C, D, and E on a Windows 2003 Server with all the latest updates and (2) one mapping to a LAN-attached LaCie 2Big storage device.This phenomenon occurs with both the 32-bit version and the 64-bit version.

I know my setup is not the same as yours but I have a home network where I use a PC running XP Pro SP3 as my file server. I was able to map the internal data drive on the file server and an external USB HD I use for backups. So far no BSOD's for me after about an hour and several reboots of the Win7 machine. Sounds like a Server 2003/Win 7 issue.

The problem is probably with your LaCie NAS. More than likely, it runs Linux and to communicate with Windows, Linux uses SAMBA for CIFS. Windows 7 will BSOD with references to tdx.sys when using mappings to anything SAMBA (ie. Linux). I had this issue when connecting to several Linux servers and a Linux-based NAS. I also have connections to several Windows Server 2003 machines and these do not cause me any problems.

I have a Samba server (Ubuntu Server 8.10 w/Samba 3.2.3) and can map drives easily without any BSOD (in fact I have not seen a single BSOD since installing Windows 7). In addition I have all my DVDs on a samba share, and can easily see and play them in Windows 7 media center. I can't join the samba domain from Windows 7, but that's a different story. I'm not saying it's not related to the NAS, but to say anything Linux/Samba will cause a BSOD is simply not true. My guess would be a driver problem. Take a look at these links, although Vista related they seem similar to your problem: http://support.microsoft.com/kb/934611 http://www.vistax64.com/vista-general/81749-vista-blue-screen-death.html I would try to narrow down the problem. First of all make sure you have the latest firmware for your NAS. Secondly try adding the mappings one by one and see which one causes the problem. You could also try disabling your anti-virus for a short period to see if that may bethe cause.

Same here I have map drive to samba server I didn't have any problem ?

I get the same thing when copying data to a newly installed NAS (Synology DS107). I don't map to the drive but when I copy data to the drive from Win7 it gives BSOD and reboots. WinXP machine works fine.I don't remember seeing the BSOD referencing tdx.sys but I can try to install that Vista patch if anyone thinks that is worthy a try. The NAS is up to date with firmware and s/w.

I wouldn't necessarily install the Vista patch as it is intended for Vista and not Windows 7.The knowledge base article does mention legacy network drivers, so I would focus on that. I assume you didn't install any drivers for your NAS (at least you shouldn't have to), but it could be your network card drivers. There is also a number of applications that install drivers that may be incompatible.You can run the verifier tool (search for verifier.exe from the start menu) to search for possible issues:http://support.microsoft.com/kb/244617

That is correct, no drivers were necessary for the NAS, the shares are just seen on the network and available. TheNIC drivers were just the ones installed from Microsoft during the installation, if I try to update them I get a message saying that they are the best available. It is an Intel PRO 100 VE so I even tried installing Intel drivers and get the same thing happening. I looked into the verifier.exe but when I tried to run it I was forced to reboot and the system would not boot back up again, I was forced to do a system restore to get it back functional again, so I doubt that I'll be playing with that one again.

Did you update with the latest firmware? I see there are some firmware updates from January 19 for your model:http://www.synology.com/enu/support/download.php?m=DS107

Thanks, i did check their support page and have installed the latest firmware version.

Not sure if you mean you already have the latest firmware installed, or if you downloaded and installed it. If the latter, did it make a difference? I was playing around with verifier as well, and I could not restart either (got a BSOD during loading). This is actually normal behavior if the verifier loads and it finds a problem driver. The fix was easy enough for me; start in safe mode and disable the driver verifier (I know I have an unsafe driver or two on my system). If you feel adventorous and want to try again, I suggest reading the following article, it may just help you track down your problem: http://www.edbott.com/weblog/archives/000576.html The article is originally written for XP, but the tool is more or less the same. Update: A lot of users seems to have the same problem, and several reports that the problem goes away after removing their anti-virus software - not necessarily what you want to do, but it may be worth a shot. I found at least one post on this forum, as well as this one from the Norton community: http://community.norton.com/norton/board/message?board.id=Win7Beta&message.id=208

thanks, I meant to say that the latestfirmware wasalready installed, i normally don't attempt to use the firmware that comes with hardware and will normally go straight to the support website for the latest. I looked at the website for the verifier info and that makes more sense now than trying to hack through it. It says that I don't have any unsigned drivers installed.

I suggest you take a look at this thread here:http://social.technet.microsoft.com/Forums/en-US/w7itpronetworking/thread/35e5fd42-120b-4240-a22b-1c550fbba44aIt may be what you are looking for.

To save the read and summarize...From what I've both read/seen and experienced now... the simple fact is that once the AV's get uninstalled there are some reg entries that might still not have been trashed/removed. If you've uninstalled say AVG (was the one I had dealt with) and still get BSOD's with tdx.sys on em the easiest fix is to run regedit and find and delete all AVG entries - searching through for AVG worked fine for me doing this. Also creds go to pj29 on here for the post of the fix of this.

I had a very similar problem and found that KIS was causing the BSOD, once it was uninstalled off one system I had no more blue screens.

I am running Windows 7 from a dual-boot setup with XP on 2 Dell PC's. One of the Dells is an Inspiron 600m laptop; the other is a Dimension 9200 tower. On either one, when I map a drive to a share on my Maxtor Shared Storage Drive I get the BSOD within 10 minutes.

Update to my previous post. Same BSoD behavior occurs if I browse to the Maxtor Shared Drive through Network even with no mapped drive to it. BTW, I am running AVG anti-virus.

UNC Path (\\servername\share) to the Maxtor Shared Storage Drive also results in a blue screen with the tdx.sys error after a few minutes. I know that removing the installed anti-virus software (AVG)is a band aid fix but I am very reluctant to run withoutany anti-virus product.

This is a known problem with Antivirus software. If you are experiencing a BSOD when mapping to a UNC, uninstall your antivirus software, reboot and try to remap. You will find that your BSOD will go away. I had the same problem and I am now using Antivir and it works for me.

rl4u,What devices are you connecting to with UNC? I can connect fine with no BSOD to network shares on devicesas long as those devices are running Windows OS's (for example a Windows XP file server). I only have the problem when connecting tomy Maxtor Shared Drive which is Linux-based.

You will only have the issue connecting to Samba shares (which your maxtor drive undoubtedly is using). We are currently investigating this with a number of AV vendors, our SMB team, and Samba. The problem is that the AV vendor software being installed is leading to a crash in TDX.SYS, a driver we provide for legacy network IO filtering (and no, it may not be the AV vendorsissue here - could beSamba's or MS - again, still investigating). If you uninstall your AV software, or do not connect to Samba shares, you will not have an issue. We've had some indications that the problem was more prevelant in wireless than wired scenarios, but that may be heresay.Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team

Any news since Feb '09? I'm having this problem now. Latest version of Samba, latest patches on Windows 7. Neither running with no AV software or not accessing my file server are options for me. What was the fix? Thanks!