Jump to content

LuckMan212

Member
  • Posts

    9
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by LuckMan212

  1. thanks cluberti, for your time- this is amazing! Of course I have some questions- 1) how do you know the main/UI thread is 'thread 3' - is thread 3 always the UI thread when debugging x86 on x64? 2) how did you figure out from the entry "03fef62c 774adcea ntdll_77af0000!NtWaitForMultipleObjects+0x15" that it means it is waiting for thread 4? 3) do multithreaded apps always pass control in a linear fashion? (i.e. if thread 3 is waiting, then it means thread 4 is executing??) 4) how do you know thread 4 is a `worker thread`? 5) when I open the dump files in x86 WinDbg on my system, the 'k' command yields the following: 0:000> k Child-SP RetAddr Call Site 00000000`000ceb08 00000000`75c4ab46 wow64cpu!WaitForMultipleObjects32+0x3a 00000000`000cebb0 00000000`75c4a14c wow64!RunCpuSimulation+0xa 00000000`000cebe0 00000000`779852d3 wow64!Wow64LdrpInitialize+0x4b4 00000000`000cf140 00000000`77985363 ntdll!LdrpInitializeProcess+0x14ac 00000000`000cf3f0 00000000`779785ce ntdll! ?? ::FNODOBFM::`string'+0x1ff19 00000000`000cf4a0 00000000`00000000 ntdll!LdrInitializeThunk+0xe What do you think the ntdll ?? ::FNODOBFM:: line is? That line doesn't appear when debugging in the x64 version. sorry for so many questions, I am just trying to understand how you were able to figure this out!
  2. alright, i've uploaded the correct dump files now: hang_mode__date_01-16-2009__time_17-24-09pm.zip download from: http://drop.io/4avkcl0 By the way, I installed the 32bit version of Windbg but when I opened the dump files they basically looked the same. In the docs for the x64 edition, it states "When to Use 64-bit Debugging Tools The 64-bit versions of Debugging Tools for Windows allow you to debug both 32-bit and 64-bit user-mode applications running on 64-bit processors. Use this package to debug both the application and the WOW64 emulator." So are you sure I cannot debug 32bit apps in the 64bit Windbg? Anyway, I really appreciate any sort of help sifting through these dumps, because I think I have the right tools but not the know-how.
  3. whoops-- I've gone and uploaded the wrong dump file. please dont download that one. I'm sending the correct one now.
  4. ok, I've zipped up the dump folder and uploaded it: http://drop.io/4avkcl0 I got your PM about trying to debug a 32bit app with a 64-bit debugger doh! I am downloading the 32bit WinDbg now, let me give it another go...
  5. hi cluberti i've got similar situation to mike above- I'm getting some hangs in iexplore.exe and am trying to debug it using WinDbg as you've laid out above. I've gotten about 70% through the process but I am kind of stuck on knowing how to make heads or tails of the call stacks. I sent you a PM, do you think you might be able to take a look at my .DMP file if I posted it for you?
  6. I doubt it-- All of these parts are working perfectly- what I think happened is that putting on the OEM version somehow altered or damaged an entry in my registry so that during this Upgrade install, setup thinks I need certain version (OEM?) of these files which apparently is not on the "retail" disc. Anyway just in case, here are some MD5/SHA1/CRC-32 hashes of the first file in my list. Can someone please check their XP SP2 install disc and verify that they get the same hash values? if you need a great (free) tool to check File hashes, I recommend HashTab shell extension: http://www.beeblebrox.org/hashtab/index.php Thanks. MIGREGDB.EX_ MD5: F0FAF54886068E84670442C8AB6C3A9C SHA1: F9253FCD04D30898FDC4B3960A53DECFA247C630 CRC32: EAA8E872
  7. OK I installed XP OEM version on top (in-place upgrade) of my normal retail version by accident (that's a whole other story). Of course I couldn't activate, so I did a re-install of my original XP over the OEM version. During the re-install, I got errors from Setup saying it needed XYZ file, for about 30 different files. I had to click "Cancel" for all of them, even though they were sitting right there on the CD (I clicked Browse... and the files were all right there!) -- for some reason Setup didn't "like" those versions, maybe it was looking for an OEM version or something? Anyway here's the list of files it asked for, in the order they were asked for.: MIGREGDB.EX_ ICWCONN1.EX_ ICWCONN2.EX_ INETWIZ.EX_ ICWHELP.DL_ ICWCONN.DL_ ICWUTIL.DL_ ICWRMIND.EX_ ICWDL.DL_ ICWX25A.DU_ ICWX25B.DU_ ICWX25C.DU_ ICWIP.DU_ PHONE.IC_ PHONE.VE_ STATE.IC_ MSICW.IS_ MSN.IS_ SUPPORT.IC_ MSOBSHEL.HT_ ISIGNUP.EX_ ICWTUTOR.EX_ ICWRES.DL_ TRIALOC.DL_ OOBEINFO.IN_ OEMLOGO.GI_ MOUSE.HT_ ISP.HT_ OEMPRIV.HT_ Does anyone know what these are or if they are important? My XP seems to be OK but it sure is annoying to have to click "cancel" 100 times during a setup of XP and I would like to fix the problem somehow. thanks!!
  8. ok I am sort of a newb but I have done lots of reading-- I read as much of the MSFN guide (beginner/intermediate section) as i could and I couldnt find really any references to my issue. it seems like a real simple thing: I want to create a semi-automated (i.e. options are pre-filled out like CD-KEY and Admin name + pwd etc, and OEM drivers are available during setup) but I still want to be able to override the settings during install if I want (example: choose partition to install to, and change Time Zone if I need to etc) without re-burning the CD each time. Apparently you can do this by editing the WINNT.SIF file created by SetupMgr.exe and making sure the UnattendMode under [unattended] is set to "ProvideDefault". I have done this, in fact my whole WINNT.SIF is below. Question is: no matter what I do when Text setup (blue screen part) gets to the part where you choose what partition to install to, it does not allow me to do an IN PLACE UPGRADE. It just shows my HD and I am afraid to continue because I don't want it to delete my WINDOWS or documents folders. Usually it will show something like Choose a windows installation to repair: C:\WINDOWS -- Windows XP Professionaland then you press "R" to do the Upgrade install which preserves your settings. I dont want to install a whole fresh version of windows in this case, I just want to do the in place upgrade but not have to type in all my info again and get asked for drivers, etc. Is this possible?? please you gurus, thanks!! ;SetupMgrTag [Data] AutoPartition=0 MsDosInitiated="0" UnattendedInstall="Yes" AutomaticUpdates=yes [Unattended] UnattendMode=ProvideDefault OemSkipEula=Yes OemPreinstall=Yes TargetPath=\WINDOWS FileSystem=LeaveAlone Repartition=No WaitForReboot="No" OemPnPDriversPath="Drivers\000_chipset;Drivers\001_storage\3ware_9500; Drivers\001_storage\nvraid;Drivers\002_network;Drivers\003_graphics; Drivers\004_monitor;Drivers\005_audio;Drivers\007_pci; Drivers\008_usb\pl2303;Drivers\008_usb\triax" DriverSigningPolicy=Ignore NTUpgrade=Yes AutoActivate=Yes [GuiUnattended] AdminPassword=xxxxxx EncryptedAdminPassword=Yes OEMSkipRegional=1 TimeZone=35 OemSkipWelcome=1 [UserData] ProductKey=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX FullName="Luke Hamburg" OrgName="MyCorp" ComputerName=BLACK-BOX [Display] BitsPerPel=32 Xresolution=1280 YResolution=1024 AutoConfirm=1 [TapiLocation] CountryCode=1 Dialing=Tone AreaCode=212 [Identification] JoinWorkgroup=WORKGROUP [Networking] InstallDefaultComponents=Yes [Components] msmsgs=off msnexplr=off [Shell] DefaultStartPanelOff=Yes [IEPopupBlocker] BlockPopups=No [WindowsFirewall] Profiles=WindowsFirewall.TurnOffFirewall [WindowsFirewall.TurnOffFirewall] Mode=0
×
×
  • Create New...