cluberti

Follow the link. You first need to install the tools, then follow the directions on making an application hang dump (get the app hung, then run the commands for creating said hang dump). If you do it correctly, they'll be in the adplus folder you created as per the instructions.

Create a hang dump.

The one runs calc.exe, as an example. The code there is harmless, but obviously the exploit is not.

Well, to be honest, most OEM vendors put out crap installs of Windows (not just Vista). It might be better to wipe the stock OEM install and reinstall it clean with the Vista disc you should have with your machine. Always a good idea if you can do it.

Also being an engineer and 20 years in the business, I know how it works as well. And yes, you can get more than 5 years out of most good equipment, but we've all had hardware (sometimes even from "good" companies) that flakes out within 12 months.

Jaclaz, it's called MTBF, or mean time before failure, and all computer parts have a rating for this. Basically, you can expect most destkop-grade consumer parts to last for 3 - 5 years before they start to fail. Some parts fail before this, and some fail LONG after this. However, the expected useful life of most desktop consumer-grade computer parts (including parts ON the motherboard, for instance) is between ~5,000 and ~10,000 hours, depending on the vendor, the quality of the components, and how many subcomponents a part has (each of those would factor into the MTBF equation of the overall device as well). I've seen vendors claim 50,000, 100,000, even 1,000,000 MTBF hours for a component, but in reality about 8,000 hours is as long as most computer equipment (especially ones on for longer than 8 hours a day) should be expected to last. Again, MTBF doesn't guarantee a part will last as long as it's MTBF number, and it also doesn't guarantee it'll fail anywhere near it if it lasts longer either (remember, it's an average, not a hard line in the sand). I choose to replace my main machines every 2 - 3 years or so, and yes I have some machines that are on year 5 or 6 of running, but I don't rely on these machines for anything critical because they are technically running longer than the manufacturer likely envisioned, and are out of warranty on pretty much everything as well. Buying good quality components usually assures you of a long life (5 years+), but it's not a guarantee. Also, buying cheaper components (or getting components from a vendor that barely met QC) is usually a recipie for failure on or before a device's MTBF.

Well, that machine will run fine for you. However, I'd make sure to bump up the memory and get rid of that god-awful hard drive they put in there with something faster (as crahak mentioned - it's really, REALLY slow).

Honestly? Windows. It's easier to repair, has FAR better logging functions, and is easier to back up and restore if the options leave you with no other choice.

I think we must understand - assuming that all 3 OSes are on "level" playing fields with 33.3% of the computing population, that means that the share of the 90%+ computer users using Windows that *would* get infected by wanting to install the 45 toolbars and games and "shiny virus but plays games app 2009 Pro Ultimate Virus version" (which you KNOW they're gonna install somehow) will now be using (at least 66.6% of them) Mac OS X and Linux, at relatively equal share. You move the sheeple to these platforms, and they'll be targeted. Period. No amount of kernel security short of not allowing people to have root, ever, for anything will keep the base OS secure. And, technically, simply infecting user-level apps is good enough to spread malware and viruses anyway - they don't always need kernel or root access.

The same - you are supposed to copy that text into an empty .html file, save it, then run it (that's the code that should exploit the vulnerability). Like I said links to the code, but nothing direct (not even the links to the scripts themselves) for obvious reasons.

And I said it yesterday at 5PM. You're all LATE! to the party lol . Seriously though, hopefully the OP will be able to get a motherboard in that will work, and get back to using his machine.

I can only see first chance exceptions, and seeing this detour in GdiPlus causing this A/V is actually expected behavior when the debugger is attached. 0:000> k ChildEBP RetAddr 0006ebd0 4ed991de GdiPlus!LZWDecompressor::FHandleNext+0x10a 0006f2a4 4ed99fc1 GdiPlus!GpGifCodec::ProcessImageChunk+0x935 0006f34c 4ed9a0e7 GdiPlus!GpGifCodec::DoDecode+0x1d6 0006f380 4eca846a GdiPlus!GpGifCodec::Decode+0x91 0006f394 4eca8425 GdiPlus!GpDecodedImage::InternalPushIntoSink+0x2e 0006f3ac 4ec94b74 GdiPlus!GpDecodedImage::PushIntoSink+0x2e 0006f414 4ec94ac8 GdiPlus!GpMemoryBitmap::InitImageBitmap+0xcc 0006f440 4eca87ba GdiPlus!GpMemoryBitmap::CreateFromImage+0x49 0006f478 4ec68040 GdiPlus!CopyOnWriteBitmap::LoadIntoMemory+0x9e 0006f51c 4ec67d48 GdiPlus!CopyOnWriteBitmap::LockBits+0xd7 0006f548 4eca684e GdiPlus!GpBitmap::LockBits+0x6d 0006f578 0047bc58 GdiPlus!GdipBitmapLockBits+0x7f 0006f598 0047bbab msnmsgr!Gdiplus::Bitmap::LockBits+0x1c 0006fa14 0047b6d1 msnmsgr!ATL::CMSGRImage::CreateFromGdiplusBitmap+0x1d3 0006fab4 0047b9ac msnmsgr!ATL::CMSGRImage::Load+0x1c5 0006fadc 006e1654 msnmsgr!ATL::CMSGRImage::Load+0x36 0006fb0c 006e198a msnmsgr!CCustomEmoticons::HrGetCImageFromObjectStoreData+0x30 0006fb50 0047ff1e msnmsgr!CCustomEmoticon::OnObjectGot+0x86 0006fb6c 00436967 msnmsgr!CEventHandler1<CEventingNode<CObjectStoreEventSinkGot,CObjectStoreRequestResultWithObject,Unused,Unused,Unused,Unused>,CObjectStoreRequestResultWithObject>::operator()+0x2c 0006fb78 0048009a msnmsgr!CEventingNode<CMainWnd,enum EOmRecvErr,CRefCountedPtr<COfflineMessage>,Unused,Unused,Unused>::RaiseEvent+0x34 0006fbb8 00480058 msnmsgr!CEventingNode<CObjectStoreEventSinkGot,CObjectStoreRequestResultWithObject,Unused,Unused,Unused,Unused>::Invoke+0x3d 0006fbf4 0047ffdd msnmsgr!CEventSinkList<CObjectStoreRequestResultWithObject,Unused,Unused,Unused,Unused>::InvokeHandlersInternal+0x45 0006fc2c 0047f83b msnmsgr!CEventSinkList<CObjectStoreRequestResultWithObject,Unused,Unused,Unused,Unused>::InvokeHandlers+0x2c 0006fc78 0052b25b msnmsgr!CRetrieveRequest::OnComplete+0xc6 0006fca0 0051f7f0 msnmsgr!CP2PRetrieveRequest::OnReceived+0x84 0006fccc 0051b463 msnmsgr!CSlaveNotifier::OnReceive+0x103 0006fd44 0051eb33 msnmsgr!CP2PTransport::OnReceived+0x8b6 0006fd98 0051dcd7 msnmsgr!CTCPTransportBridge::OnSocketRead+0x284 0006fdb4 00419934 msnmsgr!CTCPTransportBridge::OnMessage+0x17b 0006fdc8 7e418734 msnmsgr!CMsgrWndBase::WndProc+0x5f 0006fdf4 7e418816 user32!InternalCallWinProc+0x28 0006fe5c 7e4189cd user32!UserCallWinProcCheckWow+0x150 0006febc 7e418a10 user32!DispatchMessageWorker+0x306 0006fecc 004032cb user32!DispatchMessageW+0xf 0006fef8 004af31a msnmsgr!CMessengerModule::RunMessageLoop+0x65 0006ff08 004b8dba msnmsgr!ATL::CAtlExeModuleT<CMessengerModule>::Run+0x1e 0006ff10 004b8d32 msnmsgr!RunMessageLoop+0xc 0006ff24 004bd41a msnmsgr!CMSBLApp::main+0xfa 0006ff30 004bd458 msnmsgr!WinMain+0x12 0006ffc0 7c817067 msnmsgr!__tmainCRTStartup+0x140 0006fff0 00000000 kernel32!BaseProcessStart+0x23 Please post back when you have a SECOND CHANCE exception.

Depends on which versions of Windows, Mac, etc. Windows gets viruses because it's the biggest target (ask Mozilla and Apple what happens when you start to get marketshare... it's just that simple, people will not waste time writing viruses/malware that will infect 5% of the internet population when they can instead bother to waste the time to infect the other 95%). I smell a troll....

What text did you see? Was it HTML code?

Guys, ole32db doesn't have a flaw, per se. It's the application calling ole32db that is doing the use-after-free that causes the exploit to be possible. Hence why mshtml.dll was patched in IE, rather than ole32db.dll. The vulnerability is in HOW the APIs that are called are used, not the APIs exported by ole32db itself.

The link I posted above has 2 links (the first two, I think) that contain HTML pages that will repro.

Yes, merry Christmas. This was quite amusing.

Do not double post. [Closed].

There's no crash dump file here. Try again please.

Can you use ping, nslookup, etc to resolve names and IP addresses from this machine? What does ipconfig /all say it's IP address is, and is it a valid IP address on the friend's network? Also, if it is a valid IP, what DNS servers are configured?

Because redistributing Microsoft binaries, even free ones, is against the terms of the EULA, and thus in most countries, illegal. Since nuhi (and MSFN) try to abide by software vendors/developers/manufacturers' wishes with regards to redistribution, vLite no longer contains the portions of the WAIK it needs and directs you to download them from the vendor as per the vendor's EULA for the binaries. Also, since we do not allow redistribution of binaries if the vendor does not allow it, and which Microsoft forbids for the WAIK binaries, you will have to download the WAIK and copy the files out of it you need. Once you have them, there is no need to re-download the WAIK if you have to reinstall, just keep the files from the WAIK you need someplace safe. While you are correct that this would work, I would recommend against advising people to do so. Doing this does technically violate the EULA for the WAIK, and thus would go against forum rules.[Closed].

If the files are hosted in public domain on the site, then yes. If the files are not public domain, I would advise against it. A lot of times the freeware sites host "free" applications but are still owned/maintained (for free, of course) by people and do control distribution (free in use, but not in ownership) If that is the case, you should get their permission first.

The color scheme and font seems to indicate Windows 2000...

If I remember correctly, most AWARD post beep codes were video or RAM related. Anything that was 1 beep then another set of beeps was keyboard, video, etc - long beep codes were always motherboard or RAM issues. If you've swapped out video cards and used known-good RAM in here and it still won't POST, the motherboard is probably bad (specifically the memory controller is suspect).

XP was an abberation - it's the only version of modern Windows not to have a new version released 3 - 4 years after it's release (due to the Vista "reboot" back in 2004/2005). Win95 had Win98, 98 had SE and WinME (and technically W2K), NT4 had W2K (4 years instead of 3), but XP had the better part of 6 years (2001 - 2006), almost 7, before Vista. So, Win7 gets Microsoft back on the "3 year" release schedule they state they want to get back to.