cluberti

I would say that it would be "safer" to download the hotfix from the Microsoft hotfix server after contacting PSS regarding your issue, but those hotfixes at least look like they match up pretty well to the privates you get from MS. I don't know if I'd trust a hotfix from a source other than the vendor's site (even if it was from the vendor, you still can't know for sure if it's been tampered with, etc), but people do all the time.

Isn't that the job of the BestBuy staff? I mean, I know that (with few exceptions) they probably can't, but still - they're supposedly all "Vista trained" (or whatever the heck that means). As to your hardware failures, this was also the case going from NT4 to Windows 2000 or 2003 - the OS is more stringent about hardware issues, and does tax hardware further than XP does. But, that said, most "hardware" bugchecks are still caused by crappy drivers, not the actual hardware itself. Bad hardware generally causes more chaos and freezing/pausing/stuttering than bugchecks.

Note that he said RD-RAM - that's RAMBUS, and not cheap at all. Not to mention that with the symptoms he's describing, he could probably get a new motherboard, processor, and same amount of RAM for the cost of a decent RIMM upgrade .

Can you telnet to his machine on port 3389, or have you tried configuring RDP to use a different port for testing?

And the error is a STOP 0xD1, or DRIVER_IRQL_NOT_LESS_OR_EQUAL in that ar1124.sys driver. That means that the driver specified (don't know what the ar1124.sys driver is, but it's probably an HP system driver) attempted to access pageable memory using a kernel process IRQL that was too high - this causes a scheduler event, but anything IRQL2 or lower cannot initiate scheduler events or a bugcheck occurs (as we see). Generally, this is the driver's fault listed in the bugcheck, although I have seen it caused by bad RAM before. As with any OS, it's only as good (or, in this case, as BAD) as the drivers you load onto it. Note that almost all bugchecks are not caused by Windows - they're driver or hardware errors!.

Windows XP had built-in support for wireless networking, but Windows 2000 did not. You will need the utility that came with your wireless adapter to make it work properly on Windows 2000.

That would depend on whether or not it came preloaded on a new computer. If it did, then no, you cannot transfer that license (product key and COA) to another machine. However, if it's a retail copy (purchased either retail OEM or retail packaging, and not with a new PC), then yes it can be transfered. The old user must uninstall Windows and replace it with another OS before you install and activate it though, as it can only (legally) be installed and activated on one machine at a time.

What are the steps you are taking to reproduce the problem, and what have you tried (at least to this point) to resolve it? Also, have you tried formatting the disks in another machine capable of formatting the RW disks to make sure they work in another machine?

Well, that is not entirely true. I doubt the netopia network device can do it, but you can (and the smoothwall could likely be modded to do it) have the same IP address on a LAN and WAN interface - it's called proxy arp. @Herbalist - you might want to contact the ISP to see what they suggest - I am not sure how the netopia works with regard to LAN and WAN links, and since I do not believe it supports proxy arp, you'll likely need more than one public IP address from your ISP to do what you want to do.

You would call the vbscript as the first runonce item - and if it doesn't work, you'll get a popup dialog box, and if it does work you won't. Either way, runonce will continue on to the second item in the list.

You really need to see what msinfo32 reports, as it's probably going to be close to 4GB of RAM. If that ends up being the case, you may have to disable features in the BIOS or remove some of your add-in cards to get some of that RAM back.

As I mentioned in your other posting of this question in the Introduce yourself forum, we frown on double-posting here, and you've posted this question in both places. Look to the thread here in the Windows XP forums for assistance, and please don't double-post going forward. Again, welcome .

If you're sure all of your .dll's are registered (and it sounds like they are), you might want to check the filename again, and make sure you've included the full path to it (or at least are checking the path when you start up). Unless you are actually trying to launch a COM object that no longer exists or isn't registered, it's going to be the filename tripping you up.

The reason for this is the .bud file a PCL print queue uses - PS print queues do not need/use .bud files to store config information, and therefore don't have the issue. There aren't any really easy ways to accomplish this short of using the 2k3 R2 PMC. I'm sure this can be scripted, but I don't currently have the time to look into it (sorry, screamiing child ).

If you can prove you have the COA sticker (which, if you have the serial, it sounds like you do), you can contact Microsoft to send you a replacement. You'll likely pay for shipping, but otherwise media should be easy to acquire.

What does msinfo32 display for system memory? http://blogs.technet.com/askperf/archive/2...e-s-my-ram.aspx

ffdshow.ax codec is causing it - not sure why, but it's causing it while doing a load or unload of a .dll in support of the codec when the issue occurred: 0:002> ~*kvn 0 Id: e40.e18 Suspend: 1 Teb: 7ffde000 Unfrozen # ChildEBP RetAddr Args to Child 00 0013fec0 77d491ce 77d49201 0018f868 00000000 ntdll!KiFastSystemCallRet (FPO: [0,0,0]) 01 0013fee0 0060ecf5 0018f868 00000000 00000000 user32!NtUserGetMessage+0xc WARNING: Stack unwind information not available. Following frames may be wrong. 02 00000000 00000000 00000000 00000000 00000000 mplayerc+0x20ecf5 1 Id: e40.eb0 Suspend: 1 Teb: 7ffdd000 Unfrozen # ChildEBP RetAddr Args to Child 00 0186fe14 7c90e399 77e765d3 000001c4 0186ff74 ntdll!KiFastSystemCallRet (FPO: [0,0,0]) 01 0186fe18 77e765d3 000001c4 0186ff74 00000000 ntdll!NtReplyWaitReceivePortEx+0xc (FPO: [5,0,0]) 02 0186ff80 77e76c9f 0186ffa8 77e76ac1 001a4f38 rpcrt4!LRPC_ADDRESS::ReceiveLotsaCalls+0x12a (FPO: [Non-Fpo]) 03 0186ff88 77e76ac1 001a4f38 00000000 0013eec8 rpcrt4!RecvLotsaCallsWrapper+0xd (FPO: [Non-Fpo]) 04 0186ffa8 77e76c87 001a51e0 0186ffec 7c80b683 rpcrt4!BaseCachedThreadRoutine+0x79 (FPO: [Non-Fpo]) 05 0186ffb4 7c80b683 001a9458 00000000 0013eec8 rpcrt4!ThreadStartRoutine+0x1a (FPO: [Non-Fpo]) 06 0186ffec 00000000 77e76c6d 001a9458 00000000 kernel32!BaseThreadStart+0x37 (FPO: [Non-Fpo]) # 2 Id: e40.cac Suspend: 1 Teb: 7ffdb000 Unfrozen # ChildEBP RetAddr Args to Child WARNING: Frame IP not in any known module. Following frames may be wrong. 00 01a6f07c 0298ee46 00000004 01238920 0123892c 0x0 01 01a6f0a0 029969d9 01231044 0129312c 01a6f120 ffdshow!DllUnregisterServer+0x47426 02 01a6f0c8 02a5fecf 00000008 02929dcb 01280f38 ffdshow!DllUnregisterServer+0x4efb9 03 01a6f0e8 02a5cdbb 00000000 029272f1 01238920 ffdshow!DllCanUnloadNow+0x9e2f 04 01a6f164 02a58540 00000000 01a6f188 01234ee4 ffdshow!DllCanUnloadNow+0x6d1b 05 01a6f220 004c1a28 01233c70 00000001 01a6f24c ffdshow!DllCanUnloadNow+0x24a0 06 01a6f260 00421843 00ec4dfc 01234ee4 00ec4e24 mplayerc+0xc1a28 07 01a6f39c 00423045 00ec4dfc 01234ee4 00000000 mplayerc+0x21843 08 01a6f40c 00421c16 00ec4dfc 01230f8c 00000000 mplayerc+0x23045 09 01a6f554 00423045 00ec4dfc 0122e40c 00000000 mplayerc+0x21c16 0a 01a6f5c4 00421c16 00ec4dfc 0122bffc 00000000 mplayerc+0x23045 0b 01a6f70c 00423045 00ec4dfc 012288b4 00000000 mplayerc+0x21c16 0c 01a6f77c 00422281 00ec4dfc 0122879c 00000000 mplayerc+0x23045 0d 01a6f808 0044af5b 00ec4dfc 00ed2b58 00000000 mplayerc+0x22281 0e 01a6fab8 0044ee37 00ecb0f8 00ed30e8 0000c000 mplayerc+0x4af5b 0f 01a6fe70 004561ea 00ed30e8 00000000 01a6ff68 mplayerc+0x4ee37 10 01a6fe88 0060ea6b 00000000 00ed30e8 001b6048 mplayerc+0x561ea 11 01a6ff74 0063d1d8 0013f428 e9228f30 00000000 mplayerc+0x20ea6b 12 01a6ffac 0063d27d 00608e78 7c80b683 00ed6c78 mplayerc+0x23d1d8 13 01a6ffdc 7c839a0f 7c80b690 00000000 00000000 mplayerc+0x23d27d 3 Id: e40.b9c Suspend: 1 Teb: 7ffda000 Unfrozen # ChildEBP RetAddr Args to Child 00 01b7ff54 77d491ce 77d49201 01b7ff98 00000000 ntdll!KiFastSystemCallRet (FPO: [0,0,0]) 01 01b7ff74 7486ea96 01b7ff98 00000000 00000000 user32!NtUserGetMessage+0xc 02 01b7ffb4 7c80b683 00000000 7c913288 00000000 quartz!ObjectThread+0x47 (FPO: [Non-Fpo]) 03 01b7ffec 00000000 7486ea4f 000000b8 00000000 kernel32!BaseThreadStart+0x37 (FPO: [Non-Fpo]) 4 Id: e40.280 Suspend: 1 Teb: 7ffd9000 Unfrozen # ChildEBP RetAddr Args to Child 00 01cefecc 7c90e9ab 7c8094e2 00000002 01cefef8 ntdll!KiFastSystemCallRet (FPO: [0,0,0]) 01 01cefed0 7c8094e2 00000002 01cefef8 00000001 ntdll!ZwWaitForMultipleObjects+0xc (FPO: [5,0,0]) 02 01ceff6c 7c80a075 00000002 01ceffa4 00000000 kernel32!WaitForMultipleObjectsEx+0x12c (FPO: [Non-Fpo]) 03 01ceff88 72d2312a 00000002 01ceffa4 00000000 kernel32!WaitForMultipleObjects+0x18 (FPO: [Non-Fpo]) 04 01ceffb4 7c80b683 00000000 00000000 020a0014 wdmaud!MixerCallbackThread+0x42 (FPO: [Non-Fpo]) 05 01ceffec 00000000 72d230e8 00000000 00000000 kernel32!BaseThreadStart+0x37 (FPO: [Non-Fpo]) 5 Id: e40.f2c Suspend: 1 Teb: 7ffd8000 Unfrozen # ChildEBP RetAddr Args to Child 00 0291ff04 7c90e9c0 7c8025cb 00000354 00000000 ntdll!KiFastSystemCallRet (FPO: [0,0,0]) 01 0291ff08 7c8025cb 00000354 00000000 00000000 ntdll!ZwWaitForSingleObject+0xc (FPO: [3,0,0]) 02 0291ff6c 7c802532 00000354 ffffffff 00000000 kernel32!WaitForSingleObjectEx+0xa8 (FPO: [Non-Fpo]) 03 0291ff80 74827d84 00000354 ffffffff 0291ffb4 kernel32!WaitForSingleObject+0x12 (FPO: [Non-Fpo]) 04 0291ff90 7482a183 ffffffff 0122e94c 7482a154 quartz!CAMEvent::Wait+0x10 (FPO: [Non-Fpo]) 05 0291ff9c 7482a154 00000000 7482a12f 0122c0d0 quartz!CAMThread::GetRequest+0xf (FPO: [0,0,0]) 06 0291ffa4 7482a12f 0122c0d0 01a6e774 0291ffec quartz!CImplReader_1Worker::ThreadProc+0xc (FPO: [0,0,0]) 07 0291ffb4 7c80b683 0122e94c 0122c0d0 01a6e774 quartz!CAMThread::InitialThreadProc+0x15 (FPO: [Non-Fpo]) 08 0291ffec 00000000 7482a11a 0122e94c 00000000 kernel32!BaseThreadStart+0x37 (FPO: [Non-Fpo]) 6 Id: e40.988 Suspend: 1 Teb: 7ffd7000 Unfrozen # ChildEBP RetAddr Args to Child 00 02bcfe14 7c90e399 77e765d3 000001c4 02bcff74 ntdll!KiFastSystemCallRet (FPO: [0,0,0]) 01 02bcfe18 77e765d3 000001c4 02bcff74 00000000 ntdll!NtReplyWaitReceivePortEx+0xc (FPO: [5,0,0]) 02 02bcff80 77e76c9f 02bcffa8 77e76ac1 001a4f38 rpcrt4!LRPC_ADDRESS::ReceiveLotsaCalls+0x12a (FPO: [Non-Fpo]) 03 02bcff88 77e76ac1 001a4f38 00110010 7c808f8e rpcrt4!RecvLotsaCallsWrapper+0xd (FPO: [Non-Fpo]) 04 02bcffa8 77e76c87 001a51e0 02bcffec 7c80b683 rpcrt4!BaseCachedThreadRoutine+0x79 (FPO: [Non-Fpo]) 05 02bcffb4 7c80b683 001e8880 00110010 7c808f8e rpcrt4!ThreadStartRoutine+0x1a (FPO: [Non-Fpo]) 06 02bcffec 00000000 77e76c6d 001e8880 00000000 kernel32!BaseThreadStart+0x37 (FPO: [Non-Fpo]) 0:002> ~2s eax=01238920 ebx=00000000 ecx=01228670 edx=01236fa0 esi=01280f38 edi=0129312c eip=00000000 esp=01a6f080 ebp=012930a8 iopl=0 nv up ei pl nz na po nc cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00200202 00000000 ?? ??? 0:002> kvn # ChildEBP RetAddr Args to Child WARNING: Frame IP not in any known module. Following frames may be wrong. 00 01a6f07c 0298ee46 00000004 01238920 0123892c 0x0 01 01a6f0a0 029969d9 01231044 0129312c 01a6f120 ffdshow!DllUnregisterServer+0x47426 02 01a6f0c8 02a5fecf 00000008 02929dcb 01280f38 ffdshow!DllUnregisterServer+0x4efb9 03 01a6f0e8 02a5cdbb 00000000 029272f1 01238920 ffdshow!DllCanUnloadNow+0x9e2f 04 01a6f164 02a58540 00000000 01a6f188 01234ee4 ffdshow!DllCanUnloadNow+0x6d1b 05 01a6f220 004c1a28 01233c70 00000001 01a6f24c ffdshow!DllCanUnloadNow+0x24a0 06 01a6f260 00421843 00ec4dfc 01234ee4 00ec4e24 mplayerc+0xc1a28 07 01a6f39c 00423045 00ec4dfc 01234ee4 00000000 mplayerc+0x21843 08 01a6f40c 00421c16 00ec4dfc 01230f8c 00000000 mplayerc+0x23045 09 01a6f554 00423045 00ec4dfc 0122e40c 00000000 mplayerc+0x21c16 0a 01a6f5c4 00421c16 00ec4dfc 0122bffc 00000000 mplayerc+0x23045 0b 01a6f70c 00423045 00ec4dfc 012288b4 00000000 mplayerc+0x21c16 0c 01a6f77c 00422281 00ec4dfc 0122879c 00000000 mplayerc+0x23045 0d 01a6f808 0044af5b 00ec4dfc 00ed2b58 00000000 mplayerc+0x22281 0e 01a6fab8 0044ee37 00ecb0f8 00ed30e8 0000c000 mplayerc+0x4af5b 0f 01a6fe70 004561ea 00ed30e8 00000000 01a6ff68 mplayerc+0x4ee37 10 01a6fe88 0060ea6b 00000000 00ed30e8 001b6048 mplayerc+0x561ea 11 01a6ff74 0063d1d8 0013f428 e9228f30 00000000 mplayerc+0x20ea6b 12 01a6ffac 0063d27d 00608e78 7c80b683 00ed6c78 mplayerc+0x23d1d8 13 01a6ffdc 7c839a0f 7c80b690 00000000 00000000 mplayerc+0x23d27d 0:002> dc 01231044 01231044 02a67fa8 00004501 ff800001 00000000 .....E.......... 01231054 00000000 00000000 00000000 00000000 ................ 01231064 00000000 00000000 00000000 00000000 ................ 01231074 00000000 5c3a4500 6e776f44 64616f6c .....E:\Download 01231084 6c415c73 65657a69 206e6520 636e6f63 s\Alizee en conc 01231094 5c747265 69766f6d 76612e65 00000069 ert\movie.avi... 012310a4 000044d0 00004540 33797437 00000000 .D..@E..7ty3.... 012310b4 000044d0 00005300 73647561 00100000 .D...S..auds.... 0:002> dps 01a6f07c 01a6f07c 00000000 01a6f080 0298ee46 ffdshow!DllUnregisterServer+0x47426 01a6f084 00000004 01a6f088 01238920 01a6f08c 0123892c 01a6f090 00000000 01a6f094 01280f38 01a6f098 01a6f0c8 01a6f09c 02a5f658 ffdshow!DllCanUnloadNow+0x95b8 01a6f0a0 00000008 01a6f0a4 029969d9 ffdshow!DllUnregisterServer+0x4efb9 01a6f0a8 01231044 01a6f0ac 0129312c 01a6f0b0 01a6f120 01a6f0b4 01231540 01a6f0b8 01230f80 01a6f0bc 01a6f124 01a6f0c0 01a6f0d0 01a6f0c4 01238920 01a6f0c8 01a6f0e8 01a6f0cc 02a5fecf ffdshow!DllCanUnloadNow+0x9e2f 01a6f0d0 00000008 01a6f0d4 02929dcb ffdshow+0x9dcb 01a6f0d8 01280f38 01a6f0dc 01234ee4 01a6f0e0 00000000 01a6f0e4 00000001 01a6f0e8 01a6f15c 01a6f0ec 02a5cdbb ffdshow!DllCanUnloadNow+0x6d1b 01a6f0f0 00000000 01a6f0f4 029272f1 ffdshow+0x72f1 01a6f0f8 01238920

Give me some time man - just downloading the files now.

Whatever XP sees, make a page file of that size + 64MB or so on the boot volume, and you should be set (obviously a reboot is required, but you should be good to go once you've done that). Once we have a good, working memory dump, you can set everything back to the way it was.

See this post: http://www.msfn.org/board/index.php?showtopic=95980

Since Aero is done in the dwm process, not the explorer.exe process, I think you may be on the wrong track.

From http://www.msfn.org/board/index.php?showtopic=90244: Memory dump of the entire system: 1. Create or set the following registry value: Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters Value: CrashOnCtrlScroll Type: REG_DWORD Data: 1 2. Right-Click on the "My Computer" icon on the desktop and select "Properties", then click the "Advanced tab. On the "Advanced" tab, click "Settings" under the "Performance" header. Click the "Advanced" tab, then click "Change" under "Virtual Memory". Set the pagefile to be located on the partition where the OS is installed, and set it to be equal to Physical RAM + 50 MB. 3. Also in the "System Properties" window on the "Advanced" tab, click the "Settings" buttun under the "Startup and Recovery" header. Make sure "Complete Memory Dump" is selected (see 3a if this is not in the list). You can change the location of the memory dump file to a different local partition if you do not have enough room on the partition where the OS is installed. 3a. If the "Complete Memory Dump" option in step 3 is not available, you will need to manually set this registry value: Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl Value: CrashDumpEnabled Type: REG_DWORD Value: 1 4. You will need to reboot for these changes to take effect. 5. The next time that the system is hanging with a USB device attached, hold down the RIGHT CTRL key and press the SCROLL LOCK key twice to cause the machine to bugcheck and create a memory dump. After the box comes back up, you'll find the resulting memory dump file in %systemroot%\memory.dmp that can be analyzed. I'd like to look at that dump, btw.

Any network sniffer app that can work with your NIC in promiscuous mode is good - wireshark, netmon come to mind, and those are the two I use.

Try restoring to a point previous to the issue using system restore?

Making a registry change shouldn't corrupt your registry, regardless of the value you entered. This would indicate other problems with the registry that existed before the last reboot that worked - changing a registry key should not corrupt your registry, period. If it does, your registry was already corrupted, and it's the reboot that brings it to life (because, of course, you won't be able to boot). Note that registry corruption is usually the fact that your hive has gotten too large, or a handle to the registry wasn't released by an application during shutdown or app closure - Windows won't corrupt your registry directly, only indirectly on boot (when your software or system hive is too large to load into memory).