Jump to content

Search the Community

Showing results for tags 'windbg'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • The General Stuff
    • Announcements
    • Introduce Yourself!
    • General Discussion
  • Microsoft Software Products
    • Windows 11
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Server
    • Older Windows NT-Family OSes
    • Windows 9x/ME
    • Other Microsoft Products
  • Unattended Windows Discussion & Support
    • Unattended Windows
    • Other Unattended Projects
  • Member Contributed Projects
    • Nuhi Utilities
    • Member Projects
    • Other Member Contributed Projects
    • Windows Updates Downloader
  • Software, Hardware, Media and Games
    • Forum Categories
    • Mobile Devices
  • Customizing Windows and Graphics
    • Customizing Windows
    • Customizing Graphics
  • Coding, Scripting and Servers
    • Web Development (HTML, Java, PHP, ASP, XML, etc.)
    • Programming (C++, Delphi, VB/VBS, CMD/batch, etc.)
    • Server - Side Help (IIS, Apache, etc.)

Calendars

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype

Found 1 result

  1. This is a follow-up to my previous post, "Internet Explorer has stopped working..." made a couple of weeks back. Thanks to the help of MagicAndre1981, I've decided to debug Internet Explorer 9 to determine what dependency could be causing IE9 to crash. Here's a complete output to determine what has been constantly causing IE9 to crash all of the time here... Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64Copyright (c) Microsoft Corporation. All rights reserved.CommandLine: "C:\Program Files (x86)\Internet Explorer\iexplore.exe"Symbol search path is: *** Invalid ******************************************************************************** Symbol loading may be unreliable without a symbol search path. ** Use .symfix to have the debugger choose a symbol path. ** After setting your symbol path, use .reload to refresh symbol locations. *****************************************************************************Executable search path is:ModLoad: 00000000`00ce0000 00000000`00d98000 iexplore.exeModLoad: 00000000`76ff0000 00000000`77176000 ntdll.dllModLoad: 00000000`771b0000 00000000`77310000 ntdll32.dllModLoad: 00000000`00050000 00000000`00086000 C:\Windows\system32\verifier.dllPage heap: pid 0xC7C: page heap enabled with flags 0x3.AVRF: iexplore.exe: pid 0xC7C: flags 0x48004: application verifier enabledModLoad: 00000000`743c0000 00000000`74405000 C:\Windows\system32\wow64.dllModLoad: 00000000`74370000 00000000`743be000 C:\Windows\system32\wow64win.dllModLoad: 00000000`74ca0000 00000000`74ca9000 C:\Windows\system32\wow64cpu.dll(c7c.6c0): Break instruction exception - code 80000003 (first chance)*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -ntdll!DbgBreakPoint:00000000`770361f0 cc int 3Hit Debug > Go for the first time around and got this: 0:000> gModLoad: 00000000`76ec0000 00000000`76fed000 WOW64_IMAGE_SECTIONModLoad: 00000000`764e0000 00000000`765f0000 WOW64_IMAGE_SECTIONModLoad: 00000000`76ec0000 00000000`76fed000 NOT_AN_IMAGEModLoad: 00000000`76a90000 00000000`76b5d000 NOT_AN_IMAGEModLoad: 00000000`68e70000 00000000`68ea1000 C:\Windows\syswow64\verifier.dllPage heap: pid 0xC7C: page heap enabled with flags 0x3.AVRF: iexplore.exe: pid 0xC7C: flags 0x48004: application verifier enabledModLoad: 00000000`764e0000 00000000`765f0000 C:\Windows\syswow64\kernel32.dllModLoad: 00000000`74d60000 00000000`74e26000 C:\Windows\syswow64\ADVAPI32.dllModLoad: 00000000`76040000 00000000`76130000 C:\Windows\syswow64\RPCRT4.dllModLoad: 00000000`74cd0000 00000000`74d30000 C:\Windows\syswow64\Secur32.dllModLoad: 00000000`75f70000 00000000`76040000 C:\Windows\syswow64\USER32.dllModLoad: 00000000`75e10000 00000000`75ea0000 C:\Windows\syswow64\GDI32.dllModLoad: 00000000`75ea0000 00000000`75f4a000 C:\Windows\syswow64\msvcrt.dllModLoad: 00000000`75a60000 00000000`75ab9000 C:\Windows\syswow64\SHLWAPI.dllModLoad: 00000000`74ec0000 00000000`759d1000 C:\Windows\syswow64\SHELL32.dllModLoad: 00000000`75c40000 00000000`75d85000 C:\Windows\syswow64\ole32.dllModLoad: 00000000`75ac0000 00000000`75bd2000 C:\Windows\syswow64\urlmon.dllModLoad: 00000000`76810000 00000000`7689d000 C:\Windows\syswow64\OLEAUT32.dllModLoad: 00000000`76130000 00000000`762e9000 C:\Windows\syswow64\iertutil.dllModLoad: 00000000`763c0000 00000000`764db000 C:\Windows\syswow64\WININET.dllModLoad: 00000000`75f50000 00000000`75f53000 C:\Windows\syswow64\Normaliz.dll(c7c.6c0): WOW64 breakpoint - code 4000001f (first chance)First chance exceptions are reported before any exception handling.This exception may be expected and handled.*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll32.dll -ntdll32!DbgBreakPoint:771c0004 cc int 3Hit Debug > Go for a second time around and got this: 0:000:x86> gModLoad: 75be0000 75c40000 C:\Windows\SysWOW64\IMM32.DLLModLoad: 762f0000 763b8000 C:\Windows\syswow64\MSCTF.dll(c7c.6c0): Access violation - code c0000005 (first chance)First chance exceptions are reported before any exception handling.This exception may be expected and handled.ntdll!RtlVirtualUnwind+0x2d9:00000000`77028df9 488b02 mov rax,qword ptr [rdx] ds:fffffa60`1044db70=????????????????Access violation reported (code C0000005) in modules IMM32.DLL and MSCTF.DLL. Ran Debug > Go for the third time and got this output: 0:000> gModLoad: 00000000`75f60000 00000000`75f69000 C:\Windows\syswow64\LPK.DLL(c7c.6c0): Access violation - code c0000005 (first chance)First chance exceptions are reported before any exception handling.This exception may be expected and handled.ntdll!RtlVirtualUnwind+0x2d9:00000000`77028df9 488b02 mov rax,qword ptr [rdx] ds:fffffa60`1044db70=????????????????Another access violation reported in module LPK.DLL. Ran Debug > Go for the last time and got this output: 0:000> gModLoad: 00000000`759e0000 00000000`75a5d000 C:\Windows\syswow64\USP10.dll(c7c.6c0): Access violation - code c0000005 (first chance)First chance exceptions are reported before any exception handling.This exception may be expected and handled.ntdll!RtlVirtualUnwind+0x2d9:00000000`77028df9 488b02 mov rax,qword ptr [rdx] ds:fffffa60`1044db70=????????????????An access violation reported in USP10.DLL which was widely responsible for crashing Internet Explorer 9 while attempting to view Unicode characters on someone's Twitter account. >.< Now to try to isolate the problem I decided to fix the symbols and analyse the output for these issues involving IE9: 0:000> !symfix *C:\Symbols*http://msdl.microsoft.com/download/symbols0:000> !analyze -vThe final result of the output are as follows: ******************************************************************************** ** Exception Analysis ** *********************************************************************************** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\Windows\system32\verifier.dll -*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\Windows\system32\wow64.dll -*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\Windows\system32\wow64cpu.dll -*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\Windows\system32\wow64win.dll -***** OS symbols are WRONG. Please fix symbols to do analysis.*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\Windows\syswow64\kernel32.dll -***** OS (WOW64 kernel32) symbols are WRONG. Please fix symbols to do analysis.**************************************************************************** ****** ****** Your debugger is not using the correct symbols ****** ****** In order for this command to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: ntdll!_PEB ****** ******************************************************************************************************************************************************** ****** ****** Your debugger is not using the correct symbols ****** ****** In order for this command to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!IMAGE_NT_HEADERS32 ****** ******************************************************************************* ERROR: Module load completed but symbols could not be loaded for iexplore.exe*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\Windows\syswow64\ole32.dll -GetPageUrlData failed, server returned HTTP status 404URL requested: http://watson.microsoft.com/StageOne/iexplore_exe/9_0_8112_16561/539247f9/ntdll_dll/6_0_6002_18881/51da3d16/c0000005/00038df9.htm?Retriage=1FAULTING_IP:ntdll!RtlVirtualUnwind+2d900000000`77028df9 488b02 mov rax,qword ptr [rdx]EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff)ExceptionAddress: 0000000077028df9 (ntdll!RtlVirtualUnwind+0x00000000000002d9) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: fffffa601044db70Attempt to read from address fffffa601044db70FAULTING_THREAD: 00000000000006c0PROCESS_NAME: iexplore.exeADDITIONAL_DEBUG_TEXT: Use '!findthebuild' command to search for the target build information.If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.FAULTING_MODULE: 00000000764e0000 kernel32DEBUG_FLR_IMAGE_TIMESTAMP: 51da3d90MODULE_NAME: wow64ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.EXCEPTION_PARAMETER1: 0000000000000000EXCEPTION_PARAMETER2: fffffa601044db70READ_ADDRESS: fffffa601044db70FOLLOWUP_IP:wow64!Wow64EmulateAtlThunk+698200000000`743d1f02 85ed test ebp,ebpMOD_LIST: <ANALYSIS/>BUGCHECK_STR: APPLICATION_FAULT_INVALID_POINTER_READ_WRONG_SYMBOLSPRIMARY_PROBLEM_CLASS: INVALID_POINTER_READDEFAULT_BUCKET_ID: INVALID_POINTER_READLAST_CONTROL_TRANSFER: from 0000000076ff5ef8 to 0000000077028df9STACK_TEXT:00000000`0014d790 00000000`76ff5ef8 : 00000000`00000000 00000000`00000000 fffffa60`1044db10 00000000`00884280 : ntdll!RtlVirtualUnwind+0x2d900000000`0014d7f0 00000000`76ff5dfa : 00000000`00000003 00000000`00000010 00000000`00000000 00000000`759e0000 : ntdll!RtlWalkFrameChain+0x13800000000`0014dd70 00000000`76ff5d7b : 00000000`00000001 00000000`0005d859 00000000`0010000e 00000000`0014de18 : ntdll!RtlWalkFrameChain+0x3a00000000`0014dda0 00000000`000651b4 : 00000000`00880080 00000000`00884280 00000000`000041a0 00000000`00000040 : ntdll!RtlCaptureStackBackTrace+0x4b00000000`0014ddd0 00000000`0005b9a5 : 00000000`00000000 00000000`0014df20 00000000`0014df70 00000000`0005e924 : verifier!VerifierStopMessage+0x67c00000000`0014de10 00000000`743d1f02 : 00000000`7ffeffff 00000000`002ee47c 00000000`0014df70 00000000`7ffeffff : verifier+0xb9a500000000`0014de90 00000000`743ca986 : 00000000`00000000 00000000`002ee328 00000000`002ee374 00000000`7efdd000 : wow64!Wow64EmulateAtlThunk+0x698200000000`0014dfb0 00000000`74ca3688 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`7efdd000 : wow64!Wow64SystemServiceEx+0xca00000000`0014e860 00000000`743cab36 : 00000000`00000000 00000000`0014edf0 fffffa60`005efcc0 fffffa60`1044dc20 : wow64cpu!TurboDispatchJumpAddressEnd+0x2800000000`0014e8f0 00000000`743c621a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : wow64!Wow64SystemServiceEx+0x27a00000000`0014e920 00000000`74390c35 : 00000000`0014eca0 0000002b`0000004c 00000000`00000000 00000000`00000000 : wow64!Wow64KiUserCallbackDispatcher+0x23e00000000`0014ec80 00000000`77036db6 : 00000000`00000000 00000000`00000000 00000000`735b003a 00000000`00000000 : wow64win+0x20c3500000000`0014edf0 00000000`74ca3d09 : 00000000`74ca3cc5 00000023`771f94b2 00000000`00000023 00000000`00000202 : ntdll!KiUserCallbackDispatcher+0x1f00000000`0014ee48 00000000`74ca3cc5 : 00000023`771f94b2 00000000`00000023 00000000`00000202 00000000`002ef540 : wow64cpu!TurboDispatchJumpAddressEnd+0x6a900000000`0014ee50 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : wow64cpu!TurboDispatchJumpAddressEnd+0x665SYMBOL_STACK_INDEX: 6SYMBOL_NAME: wow64!Wow64EmulateAtlThunk+6982FOLLOWUP_NAME: MachineOwnerIMAGE_NAME: wow64.dllSTACK_COMMAND: ~0s ; kbBUCKET_ID: WRONG_SYMBOLSFAILURE_BUCKET_ID: INVALID_POINTER_READ_c0000005_wow64.dll!Wow64EmulateAtlThunkWATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/iexplore_exe/9_0_8112_16561/539247f9/ntdll_dll/6_0_6002_18881/51da3d16/c0000005/00038df9.htm?Retriage=1Followup: MachineOwner---------Something is fishy here. Reinstalling Internet Explorer 9 has had no help. The STACK_TEXT shows a list of dependencies that could be the culprint here and for some reason, it points to wow64.dll, but I don't know if it's true or not. Sorry for the distressful spam here, but can anyone look up the offending dependencies that caused IE9 to stop working properly here? Thanks for your time.
×
×
  • Create New...