I needed a 64 bit machine for a firewall and I happened to have an older AMD machine that I wasn't using so I decided to use it. I installed 2K8R2 and everything seemed fine. I even installed Forefront Threat Management Gateway on it and it was fine. However, if I open Windows Explorer, it will blue screen anywhere from a few seconds after starting explorer to a few minutes after starting it. If I don't start explorer, it will hum along nicely without a complaint. Any suggestions as to what I should be looking at to address this? I would like this box to be my FTMG box but if I can't rely on it, I won't be able to use it. Thanks Bert

Any memory dumpfile is generated ? I have seen the problem when you have other Antiviruses and software firewall running along with FTMG. Please remove Symantec End POint if you have or other Av and firewalls.

There probably is a dumpfile, I have to admit that I didn't look. No, there is nothing else on theis computer aside from Windows 2K8R2 and FTMG. For that matter, the problem existed prior to the installation of FTMG. I installed FTMG as a test to see if I could install a piece of software on this system since it kept blue screening. The installation went very well and everything works fine as long as I don't open explorer. Bert

Check the dump file using Windbg tool.

hi penney, its difficult to say which caused the issue without analyzing the dump file. There are 2 things you should consider a) configuring the dump b) analyzing the dump file. To be precise you should have expertise to anlayze the dump file , which is impossible if you are not from debugging background ( avoiod wasting time ), rather you could open a case with microsoft and the experts would assist you analzying the dump and tell you the RCA of the issue. If you have the expertise , then you should analzye the "relevant dump" , with the exception code into consideration along with the BSOD parameter, download theh windbg utiliity or you can use the cmd line tools such as ntsd or cdb.exe to analyze the same. After which you should understand which module has caused ( .sys file ) and to identify the root cause you should check which thread caused the excception, and analzying the thread stack with appropriate symbol file loaded would be viable. As a over all view. make sure a) you have the compatible drivers loaded for windows 2008 R2 and meet the HCL b) replace the RAM ( if relevant only ) @vinay : " have seen the problem when you have other Antiviruses and software firewall running along with FTMG. Please remove Symantec End POint if you have or other Av and firewalls." make sure you provide suggestions after analyzing , or else customer might land into larger problem. Also be specific what customer has to perform. Analyze with windbg ? , it would be tough to understand what to understand , what to see , where to see etc.. , no offenses but its the way all engineers in the forum assist customers.

OK, I'll have a look at the dump. Bert

Please use Skydrive to upload the zipped dump files. Once done, post a link to the uploaded file here. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration