Menu
I intermittently receive a browser hang with this error in a dump file.
After using !analyze -v on 3 crashes I receive this error and stack
GetUrlPageData2 (WinHttp) failed: 12007.
However, I can never find the URL in my dump file that is failing. Can anyone help?
STACK_TEXT:
0029e8fc 5ffce1fd 74ce1450 00000000 00000000 user32!NtUserWaitMessage+0x15
0029e960 5ffd5f2c 00000001 0070fab0 00000000 ieframe!CBrowserFrame::FrameMessagePump+0x52e
0029e9a8 5ffd64e4 00000000 74ce1450 00708618 ieframe!BrowserThreadProc+0xf8
0029e9c8 5ffd6441 00708618 00000000 00708618 ieframe!BrowserNewThreadProc+0x88
0029fa38 5ffd62b2 00708618 00000000 76655528 ieframe!SHOpenFolderWindow+0x109
0029fa5c 5ffd61b1 006e4188 00000001 00000000 ieframe!IEWinMainEx+0x204
0029fa78 5ffd6120 006e4188 00000001 00000000 ieframe!IEWinMain+0x77
0029fab0 00c32fdb 006e4188 00000001 01000000 ieframe!LCIEStartAsFrame+0x265
0029fc04 00c312a2 00c30000 00000000 006a21cc iexplore!wWinMain+0x3b2
0029fc98 74ce33aa 7efde000 0029fce4 77159ef2 iexplore!_initterm_e+0x1b1
0029fca4 77159ef2 7efde000 77f3a412 00000000 kernel32!BaseThreadInitThunk+0xe
0029fce4 77159ec5 00c31b0a 7efde000 00000000 ntdll!__RtlUserThreadStart+0x70
0029fcfc 00000000 00c31b0a 7efde000 00000000 ntdll!_RtlUserThreadStart+0x1b
How can I find the URL in this stack that is failing?
712
As an alternative to the k command, you can view the call stack in the Calls window. To open the Calls window, choose Call Stack from the View menu.
Launch Notepad and attach WinDbg On the File menu, choose Open Executable. In the Open Executable dialog box, navigate to the folder that contains notepad.exe (typically, C:\Windows\System32). For File name, enter notepad.exe. Select Open.
To get a stack trace, use the methods GetStackTrace and GetContextStackTrace. A stack trace can be printed using OutputStackTrace and OutputContextStackTrace.
Alternatively referred to as Cmd+K, Command+K is a keyboard shortcut that varies depending on the program used. For example, in certain programs, Command+K is used to insert a hyperlink, and in some browsers, Command+K focuses on the search bar. On Windows computers, the most similar keyboard shortcut is Ctrl + K .
The GetUrlPageData2 (WinHttp) failed: 12007 does not have anything to do with the crash.
Windbg tries to pull in Watson data from Microsoft servers and failed to pull it so it is showing the error string it is for information purpose only
the data that is being pulled is the data sent to Microsoft servers by various users worldwide when they say yes to the dialog which asks do you want to send this to Microsoft_xxxx when an application crashes
the data if it existed may aid Windbg to provide a better analysis of the crash when you use !analyze -v
the error code 12007 is ERROR_WINHTTP_NAME_NOT_RESOLVED
you can find a list of Winhttp errors defined in winhttp.h if you have the sdk installed locally or refer winhttp_errorcodes
if you are so bent you can use .dbgdbg to debug the debugger and set a break-point on ext!GetUrlPageData2 and dump the string with da Poi(@esp+4)
GetPageUrlData failed, server returned HTTP status 404
URL requested: http://watson.microsoft.com/StageOne/FoxitReader_exe/7_2_8_1124/56551ff4/FoxitCloud_fpi/3_7_139_918/55fbbee5/c0000005/0006b97a.htm?Retriage=1
This out of the way the stack you posted doesn't appear to hold any details regarding the crash it seems to be waiting on an object
95
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
