cluberti

Note that the answer to this question has been stickied here for future reference.

Sounds like you should file a bug

What is the FQDN for the domain that the server or workstation belongs to? I know it's complaining because the name it mentions there has no .tld or .local extension, so it is technically an invalid DNS name. What is the domain and NetBIOS name of the domain the machine belongs to?

Another point to mention - you can indeed use 4GB of RAM with a 32bit OS and use almost all of it, but you generally have to have older hardware (that lacks PCI-E or PCI-X, have an older video card, and make sure the BIOS is fairly generic). Otherwise, yes, you'll need a 64bit OS. Note that the additional memory that Windows "can't see" does actually get used by your devices, and memory shadowing is generally a good thing - you just can't use it with your applications or OS. If you do some research and make sure your hardware has certified drivers for x64, your OS will indeed be stable. If you have apps that won't run on x64, you'll be stuck in 32bit land - but for the resto of us, x64 is the way of the future on the desktop .

The frequency of these posts leads me to believe we need to sticky this topic in a few places. This is getting frustrating.

Please explain what you mean by "not working" - can you browse to websites? Can you ping hosts by name? Can you ping hosts by IP address? If you do a pathping or tracert to IP addresses on the internet that you should be able to get to, do you get any errors? We need more information - "not working" is too vague for us to help at the moment. If you can answer these questions, we might be able to assist.

Take a look over at PlanetAMD64 for answers.

To the user who reported this thread (you know who you are) - the report button is not meant to solicit help or bring posts to the attention of the moderators unless there is some breach of the forum rules. Reporting this does NOT fall under those guidelines, so please use the report button sparingly. Thank you.

At this point, I think it's safe to say that only a live debug is gonna catch this - is it possible to load a second install of Vista, clean, on that machine? If so, let's install Vista clean, then install your applications one at a time and try to reproduce the issue after each install+reboot. I apologize, but I just don't have the time at the moment to help you with a live debug .

No, I'd say uninstall and try to cause the problem again.

Well, actually, it will show disconnected if you did not authenticate to the server hosting the drives (this can happen when a "slow link" is detected, or if you're using a wireless connection and you've logged in with cached credentials). When you first log in if this happens, the drives will show up, but they'll be "disconnected" until you double-click one to browse it (auth happens in the background, and once you get a valid token from a DC or the local server if it's a local account on the server, everything "works" again).

OK - here's the thread that's making the callback into a module that is no longer loaded: 0:044> kn # ChildEBP RetAddr 00 08dff0d4 76060991 kernel32!RaiseException+0x58 01 08dff0ec 76060969 rpcrt4!RpcpRaiseException+0x1e 02 08dff0f8 760ef68f rpcrt4!RpcRaiseException+0x16 03 08dff108 760f1d87 rpcrt4!NdrProxySendReceive+0xa3 04 08dff114 760f1f58 rpcrt4!NdrpProxySendReceive+0xc 05 08dff5fc 760f1d64 rpcrt4!NdrClientCall2+0xbde 06 08dff624 76073763 rpcrt4!ObjectStublessClient+0x6f 07 08dff634 7713c2d1 rpcrt4!ObjectStubless+0xf 08 08dff650 7713c283 ole32!RemoteReleaseRifRefHelper+0x87 09 08dff67c 77141718 ole32!RemoteReleaseRifRef+0x75 0a 08dff700 77140aa2 ole32!CStdMarshal::DisconnectCliIPIDs+0x2da 0b 08dff730 77140c10 ole32!CStdMarshal::Disconnect+0x1a6 0c 08dff74c 77140b7a ole32!CStdIdentity::~CStdIdentity+0x8c 0d 08dff758 77140ccc ole32!CStdIdentity::`scalar deleting destructor'+0xd 0e 08dff76c 763637ca ole32!CStdIdentity::CInternalUnk::Release+0x6d 0f 08dff778 76510983 shell32!IUnknown_SafeReleaseAndNullPtr<CPropertyControlBase>+0x17 10 08dff784 7645a80b shell32!CProgressDialogUI::EndDialog+0x24 11 08dff7a8 763c67c8 shell32!CProgressDialogUI::_HandleTimerMessage+0xe0 12 08dff7c0 763ca53b shell32!CProgressDialogUI::_DialogProc+0x1fe 13 08dff7dc 76e71a10 shell32!CProgressDialogUI::DialogProc+0x51 14 08dff808 76e60e04 user32!InternalCallWinProc+0x23 15 08dff884 76e60c7e user32!UserCallDlgProcCheckWow+0x132 16 08dff8cc 76e6123b user32!DefDlgProcWorker+0xa8 17 08dff8e8 76e71a10 user32!DefDlgProcW+0x22 18 08dff914 76e71ae8 user32!InternalCallWinProc+0x23 19 08dff98c 76e72a47 user32!UserCallWinProcCheckWow+0x14b 1a 08dff9f0 76e72a98 user32!DispatchMessageWorker+0x322 1b 08dffa00 763c7e29 user32!DispatchMessageW+0xf 1c 08dffa38 763c4282 shell32!CProgressDialog::_ThreadProc+0xb4 1d 08dffa40 7628b132 shell32!CProgressDialog::s_ThreadProc+0xd 1e 08dffabc 76153833 shlwapi!WrapperThreadProc+0x10f 1f 08dffac8 777ba9bd kernel32!BaseThreadInitThunk+0xe 20 08dffb08 00000000 ntdll!_RtlUserThreadStart+0x23 The error code can be seen when dumping registers for the stack at frame 12 - we're getting an ntstatus error message of 0x80010012, which means "The callee (server [not server application]) is not available and disappeared; all connections are invalid. The call did not execute.". So shell32 made a call to a function in a previously loaded .dll, but for whatever reason that module is no longer loaded, and all rpc connections between the shell and this process are null and void. From digging deeper, I can see that the actual RPC call was "_RTL_CALLER_ALLOCATED_ACTIVATION_CONTEXT_STACK_FRAME_EXTENDED", which means someone wanted to extend the stack frame to store more information. There are 2 different products on the box that appear to have been involved here, but since they've unloaded I have to make an educated guess - it's very likely that one of these two modules is causing the crash: 0:044> lmvm PhoneBrowser start end module name 07070000 07101000 PhoneBrowser C (export symbols) PhoneBrowser.dll Loaded symbol image file: PhoneBrowser.dll Image path: C:\Program Files\Nokia\Nokia PC Suite 6\PhoneBrowser.dll Image name: PhoneBrowser.dll Timestamp: Wed Mar 28 04:57:04 2007 (460A2DE0) CheckSum: 00000000 ImageSize: 00091000 File version: 6.83.74.9 Product version: 3.0.0.0 File flags: 0 (Mask 3F) File OS: 40004 NT Win32 File type: 2.0 Dll File date: 00000000.00000000 Translations: 0409.04b0 CompanyName: Nokia ProductName: Phone Browser InternalName: Phone Browser 3 OriginalFilename: PhoneBrowser.dll ProductVersion: 3.0 FileVersion: 6, 83, 74, 9 SpecialBuild: Release Unicode FileDescription: Phone Browser LegalCopyright: Copyright © 2006 Nokia. All rights reserved. 0:044> lmvm atsc70 start end module name 0a200000 0a32c000 ATSC70 (export symbols) ATSC70.dll Loaded symbol image file: ATSC70.dll Image path: C:\Windows\System32\ATSC70.dll Image name: ATSC70.dll Timestamp: Mon Nov 20 13:10:55 2006 (4561EFAF) CheckSum: 00127ABC ImageSize: 0012C000 File version: 7.7.0.25 Product version: 7.7.0.25 File flags: 20 (Mask 3F) Special File OS: 40004 NT Win32 File type: 2.0 Dll File date: 00000000.00000000 Translations: 0409.04b0 CompanyName: AuthenTec, Inc. ProductName: AuthenTec Sensor Control DLL InternalName: AuthenTec AT DLL OriginalFilename: ATSC70.DLL ProductVersion: 7, 7, 0, 25 FileVersion: 7, 7, 0, 25 SpecialBuild: BETA Pre-release of 7.7.0.26 FileDescription: AuthenTec AT DLL LegalCopyright: Copyright © 1999 - 2006 AuthenTec, Inc. All rights reserved. Comments: BETA Pre-release of 7.7.0.26

Note that you need the WU 3.0 client installed, _and_ 927891 for this to "work".

In this case, IE7 uses functionality in the OS to provide features specific to browsing and security - since it would take a rearchitect of these components on a Windows 2000 machine or a Windows XP RTM or SP1 machine to make IE7 work, IE7 is XPSP2/W2K3SP1 and Vista/Longhorn only. Remember, once a product is out of mainstream support, products generally don't get released for that platform going forward.

You won't be able to redirect a URL via W2K3 DNS, so you'll have to create a default page at the web server in question (http://123.456.789.0/default.htm) that simply does a redirect to the location you want your users to go to. Then, point an A record at http://123.456.789.0 for application.company.com, and all users going to application.company.com should open default.htm by default, and be redirected to the URL you specify.

Almost always, when csrss.exe crashes (and your STOP 0xC21A error says this is the crashed module), you've got one of three problems: 1. A system driver (usually antivirus or backup software, but I've seen remote control, network, and video drivers cause this too) has hooked into the process (either explicitly or a global hook) and excepted, which will cause the subsystem to crash and thus bugcheck the box 2. Mismatched file versions for csrss.exe and it's supporting .dll files can cause it to crash if csrss.exe calls an export that doesn't exist in the .dll it's calling (for whatever reason), or expects a certain response from a call that it doesn't get, etc. - this is bad, and generally reapplying the Service Pack and subsequent hotfixes resolves the issue 3. Bad / Overclocked hardware can cause this if it's a timing issue, and we're exposing flaws in the hardware by pushing it harder than originally intended.

Actually, that reg key location doesn't exist until T-9 during setup, so if you're calling this at T-13 or T-12, you'll get this error.

We know! Have you tried it? How do you create a new file type of your own? You can't. It only shows the extensions that are already present and you can change the program that is called. Yes - and the original question was trying to _change_ what was already there, not add new ones. There isn't a GUI to do this built-in to Vista anymore, but there are two ways to do it. One, if you know how to write decent C# code, you can try this, or, if you aren't a programmer, there's a good freeware tool that can do the job as well. You can always use the right-click menu on a file type that you want to change and choose "Open with...", as well.

Moving to more appropriate forum.

Guys - Control Panel > Default Programs.

I could tell from the previous logs you were doing something like that - I'm downloading it now.

This sounds like a great place for you to create a custom MMC with the snapins necessary to do their jobs, so they don't use their own Computer Management to manage machines with an account other than one they're logged in with (I've seen this happen before).

OK - I think I see what is happening, but I need for you to change the command used to start the debugger to this: cscript adplus.vbs -crash -fullonfirst -pn explorer.exe -o c:\adplus We're only getting first-chance exceptions, so I need to capture those. I think we have a .dll that is missing registry information (the errors are all interface not registered, basically), but without a .dmp file I can't see which. Configure for fullonfirst as above, and we should get more data (at least some .dmp files).

I'm not sure about that specific application, but if the applications you are using require installation of filter drivers of any kind, you cannot install it on x64 (you can't install 32bit filter drivers on x64).

Not that I'm aware of. There are some GPO changes in Longhorn, but nothing for local policies that I'm aware of. The only thing you can do currently is filter a GPO for users or groups.