Trying to install the latest version of TweetDeck for Windows XP.. During the installation phase there's this BSOD.. I'll attach the minidump files for the experts here to analyze..Things I have already tried:Updating drivers to the very latest from Dell official website. (I own a Dell Inspiron 1420, BTW)Tried installing the application after putting the computer in CLEAN boot.. No joy! Encountered the same error yet again!!Thanks for any help!RIP!Minidump here: http://dl.dropbox.com/u/6898779/Minidump.rar1 person needs an answerI do too

TweetDeck should be a user-mode app; user-mode apps don't cause bluescreens (kernel-mode components and hardware can). So, the TweetDeck installation may be triggering some behavior that is causing the bluescreen/bugcheck, but is not directly responsible for it.Both bugchecks were KERNEL_MODE_EXCEPTION_NOT_HANDLED_M - caused by unhandled access violations. In each case, the driver windrvNT.sys was implicated in the dump. Check for an update to this driver, or uninstall it or the software that it came with.For dealing with Blue Screens, general guidance follows:Consider running chkdsk on all partitions. Let chkdsk complete on each partition and see if that helps.Also consider running SFC /SCANNOW.It can be helpful to use Driver Verifier. To enable Driver Verifier... start->verifier.exe->OK->Create standard settings- >Next->select driver names from a list->Next->sort by Provider->select all non-Microsoft drivers->Finish, and OK your way out of the dialog.Then, reboot and use the system as you normally would, and wait for a problem. In the event that the system does not boot completely after enabling driver verifier, boot into Safe Mode and run driver verifier, and tell it to delete the changes.Wait for a bugcheck to occur after enabling verifier as described, and then upload it to your SkyDrive, and provide a link.If you boot into safe mode, do you still experience bugchecks? What about if you do a clean boot, or device clean boot?Consider testing memory with Windows Memory Diagnostic or memtest86. Note that memory that passes tests is not necessarily good memory - it just hasn't failed a test. Consider systematically eliminating RAM from the system - run with a couple of modules for a while, and see how things go. Then try the other modules.Other common suggestions include ensuring drivers are up to date (including video drivers), as well as ensuring that you're using the latest BIOS.

^^Thanks No.Compromise. It's actually a friend of mine who has the issue.. I'll refer her this thread link and keep you updated if it fixes the issue.

Very well! Good luck!