I was requested to post this here due to on going issues. I will post the original post page here and you can read what I have done. It is detailed. "Pa Bear" has continued to follow me from post to post (cyber stalker style) insisting the computer has been "hijacked" and has done nothing but harass me. As you read through what I have done you will see this is not the case. Here is the link http://social.answers.microsoft.com/Forums/en-US/w7network/thread/ee250dfa-0a15-416a-9423-72a083665d13 Thanks for your time

Hi, thank you for posting here. After reviewing the old thread, I found the problem related with the Norton software. Did your problem solved when you uninstall Norton? Regards, Leo HuangPlease 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.

NO as listed in that thread. I will say it again, it's not Nortons, it is the OS. So fed up with no help or resolutions I contacted Newegg (whom I purchased Ultimate through) and they RMA'd that copy and will be sending me a new copy. In the mean time since Robear has tainted everybody into believeing it must be me or a virus, I figured I would post this update. I have installed in the same mannor as listed in the other thread, a family members copy of win7 64 pro and have been using it without issue for close to 2.5 weeks. So I rest my case in stating it was the OS as the problem and thanks to Robear no one will get a solution and this dragged out far more than it should have.

Well, I guess that wasnt the answer. The Pro too finally sucummed to the same issue. I reinstalled the os for the umpteenth time as described in the above with one differance. I this time disabled the network adaptor on the board and installed the Intel Pro mt1000 then installed the os (Ultimate version, mine). Worked for approximatly 2.5 weeks then got the same message. After hours of research it appears throughout the internet with multipule "help" sites that this is clearly an issue with the OS. I need this issue solved or the computer is practically useless. I cant get to any networked computer or "share" my media with anything attached to the network. As I stated before I will help in anyway I can to get this resolved. Newegg sent me back my copy of the Ultimate too btw. Oh, I forgot, the install was 2 differances, I did not install any 3rd party firewalls and did not update or add the MS Security stuff. I still have the same issue. So its not the firewalls either.

Hi, I will escalate your question. Other senior support engineer would help you to find the solution. Regards, Leo HuangPlease 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.

Thank you very much I do appreciate it. FYI...I installed Win7 32 on my older P4 system with an Intel pro mt server adapter with all my programs including Nortons and have had none of the issues listed above. However, it is doing somthing funky with Outlook 2007 which will not allow it to function properly where as it did in 64. This has been posted in another thread. Thanks again

I got the Outlook issue handled. I have been now running the Win7 64 Ultimate after reinstall (same mannor as listed) and for some reason it has worked with the intel pro mt pci nic adaptor and after reading the all the other posts am wondering if it has something to do with the broadcom nics install on the mb. Then again it happens quite freaquently with the wireless too in many of those posts. So I am officially out of ideas, but at least its working for now.

As of this morning I discovered my system restarted due to a blue screen. It restarted yesterday too due to a bluescreen. Upon startup the system didn't load Nortons even though it showed it as started. So I cheked the Windows firewall to see if it was running and it was. I stopped the service and restarted the system and now have the same issue again. I am fed up with the reinstalling of all my programs and the emails to have my install keys reactivated on all my programs. I noticed in the "users" folder thatt a lock icon appears over all the profiles including 2 named "Mcx1-CENTURION" and "Mcx2-CENTURION" (Centurion is computer name). This is not on the 32 bit system and still have yet to get these issues on that system (which is GREAT). This still needs to be solved, so someone ot MS please look into this and tell me what info you need. Thanks

Hi, Please follow these steps to collect dump file: Collect Minidump Files ================= 1. Click "Start", input "SYSDM.CPL" (without quotation marks) in the “Search” bar and press “Enter”. 2. Switch to the "Advanced" tab and click the "Settings" button under "Startup and Recovery". 3. Under "Write debugging information" section, make sure the "Small memory dump (128KB)" option is selected. 4. Make sure "%SystemRoot%\Minidump" is in the "Small dump directory" open box and click “OK”. If the Blue Screen appears again, please refer to the following steps to collect memory dump files: 1. Click “Start”, type “%SystemRoot%\Minidump" (without quotation marks) in “Search” bar and press “Enter”. 2. Go to your Desktop, right-click on it and create a new folder named "Dump". 3. Copy all the memory dump files (looks like [Mini092008-01.dmp]) in Minidump to this folder. 4. Right-click on the Dump folder, click "Send To", and click "Compressed (zipped) Folder". 5. Share the dump file to we, you can use Windows Live SkyDrive (http://www.skydrive.live.com/)to upload the file and share its URL with me. You can also analyze them with Debugging Tools by yourself. You can install it and it’s Symbol Packages from the following link: http://www.microsoft.com/whdc/Devtools/Debugging/default.mspx WinDbg will tell you the possible cause. For more information, please read Microsoft KB Article: How to read the small memory dump files that Windows creates for debugging. If no clue can be found, you may contact Microsoft Customer Support Service (CSS) via telephone so that a dedicated Support Professional can assist with your request. To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. Please be advised that contacting phone support will be a charged call. Regards, Leo HuangPlease 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.

Hello Leo, Its been awhile. I have fought with this for a while now. I have not done as you requested due to lack of faith in "everyones" ideas on what the problem may be. Well, I believe I have figured it out. For some reason on this paticular machine when the ms updates are installed and the system is restarted it apparently only will connect wirelessly, even though there HAS never been any wireless device attached or installed on this machine. So there for it shows "no connections avalible" even though you are connected through the wired lan. After reinstalling the os for the umpteenth time I decided not to install anything with 2008 server in it and did not have an issue. Well I started thinking and decided to to disable through the "services" "WLAN AutoConfig" (due to the sp1 update going to install what i didnt anyway). It worked. I then to further my suspicions I re-enabled the on board nic and removed the nic card (due to it always giving me the "no connections avlible") and it too, worked. After the install and multipul restarts it has worked well. I then installed the sp 1 update yesterday, and it to went well. I turned on the machine today and it remained on the "network", however it wouldn't reconnect to my server/mapped drives. So I checked the "services" and discovered that "LanmanWorkstation" was properly set to "automatic" but the service was stopped. I started it and all is well. The issue now, is it has to be restarted everytime the computer is booted up. Once started it runs as expected. I am sure this can be corrected, just not sure how. Thanks