ppgrainbow

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.

Thanks for telling me. It looks like that this might be a bug that broke 64-bit compatibility in Windows 7 RTM and below. As far as I know, the 64-bit version of Stella 4.0 uses Advanced Vector Extensions (AVX) that only exist in Windows 7 SP1 and later. I'm wondering if there is a way to patch the 64-bit version of MSVCRT120.DLL without vpsrlq and AVX support on Windows Vista or not. Otherwise, I will have to use the 32-bit version of Stella 4.0 as it is built using MSVC2013. As far as I know, the next major release of Stella or the next major version of Visual Studio, will neither support Windows XP nor Windows Vista. The AMD FX-4300 CPU does have AVX support, but I'm disappointed to hear that the latest 64-bit release of Stella would not work in Windows Vista, even if the OS is still supported until April 2017.

Okay, what I did was to fix the symbols from the C:\Symbols directory by typing this command: !symfix *C:\Symbols*http://msdl.microsoft.com/download/symbols Next when I ran the !analyze -v command, here's the output of what I received: ******************************************************************************** ** Exception Analysis ** ************************************************************************************* OS 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 ****** ****************************************************************************FAULTING_IP:MSVCR120!log+2d3000007fe`f2ea2bc3 c5e173d034 vpsrlq xmm3,xmm0,34hEXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff)ExceptionAddress: 000007fef2ea2bc3 (MSVCR120!log+0x00000000000002d3) ExceptionCode: c000001d (Illegal instruction) ExceptionFlags: 00000000NumberParameters: 0FAULTING_THREAD: 0000000000001260DEFAULT_BUCKET_ID: WRONG_SYMBOLSPROCESS_NAME: image00000001`40000000ADDITIONAL_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: 0000000076ff0000 ntdllDEBUG_FLR_IMAGE_TIMESTAMP: 524f83ffERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.MOD_LIST: <ANALYSIS/>PRIMARY_PROBLEM_CLASS: WRONG_SYMBOLSBUGCHECK_STR: APPLICATION_FAULT_WRONG_SYMBOLSLAST_CONTROL_TRANSFER: from 00000001400568cc to 000007fef2ea2bc3STACK_TEXT: 00000000`0012f960 00000001`400568cc : 00000000`0012fa10 00000001`40221da0 00000001`40221da0 00000000`00000000 : MSVCR120!log+0x2d300000000`0012f9c0 00000001`4008c44e : 00000000`002ea730 00000001`40221da0 00000000`0012fcf0 00000000`0012fbb8 : image00000001_40000000+0x568cc00000000`0012fb70 00000001`40154cca : 00000000`00000001 00000000`00000001 00000000`001b0010 00000000`00000000 : image00000001_40000000+0x8c44e00000000`0012fd90 00000001`40001020 : 00000000`001f3474 00000000`0000000a 00000000`001f3474 00000000`0000000a : image00000001_40000000+0x154cca00000000`0012fe90 00000001`400010f2 : 00000000`00000001 00000000`001b0010 00000000`000002f4 000007fe`f2e3276b : image00000001_40000000+0x102000000000`0012fed0 00000001`4015419d : 00000001`40000000 00000000`00000000 00000000`001f3474 01cf9d1f`0000000a : image00000001_40000000+0x10f200000000`0012ff20 00000000`76eda54d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : image00000001_40000000+0x15419d00000000`0012ff60 00000000`77016861 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0xd00000000`0012ff90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21FAILED_INSTRUCTION_ADDRESS:MSVCR120!log+2d3000007fe`f2ea2bc3 c5e173d034 vpsrlq xmm3,xmm0,34hFOLLOWUP_IP:MSVCR120!log+2d3000007fe`f2ea2bc3 c5e173d034 vpsrlq xmm3,xmm0,34hSYMBOL_STACK_INDEX: 0SYMBOL_NAME: msvcr120!log+2d3FOLLOWUP_NAME: MachineOwnerMODULE_NAME: MSVCR120IMAGE_NAME: MSVCR120.dllSTACK_COMMAND: ~0s ; kbBUCKET_ID: WRONG_SYMBOLSFAILURE_BUCKET_ID: WRONG_SYMBOLS_c000001d_MSVCR120.dll!logFollowup: MachineOwner---------For some reason, the analyst is telling me that I'm *not* using the correct symbols despite the fact that I set the symbol path to the C:\Symbols directory. Is there a way to make the WinDbg use the correct symbols? Regardless of the fact that I'm not using the correct symbols, it seems that I'm trying to make some progress here and determine what could be causing the 64-bit version of Stella, built with the 64-bit version of VS2013 to crash.

Thank you for the help. I will install the Windows 7 SDK Debugger and report back when I'm done. Note: In order for the Windows 7 SDK Debugger to work, I have to uninstall Visual Studio 2010 and reinstall the Windows 7.1 SDK. I have the System Restore to revert the changes, so once I'm done...I can revert prior to installing the Windows 7.1 SDK. Update: I did some debugging on the 64-bit executable of Stella 4.0 and here are the results: Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64Copyright (c) Microsoft Corporation. All rights reserved.CommandLine: C:\Stella\Stella.exeSymbol 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: 00000001`40000000 00000001`40366000 image00000001`40000000ModLoad: 00000000`779d0000 00000000`77b56000 ntdll.dllModLoad: 00000000`77540000 00000000`7766d000 C:\Windows\system32\kernel32.dllModLoad: 00000000`6c740000 00000000`6c86f000 C:\Stella\SDL2.dllModLoad: 000007fe`fe540000 000007fe`fe5a4000 C:\Windows\system32\GDI32.dllModLoad: 00000000`77310000 00000000`773dd000 C:\Windows\system32\USER32.dllModLoad: 000007fe`fe790000 000007fe`fe898000 C:\Windows\system32\ADVAPI32.dllModLoad: 000007fe`fea80000 000007fe`febc2000 C:\Windows\system32\RPCRT4.dllModLoad: 000007fe`fe400000 000007fe`fe42d000 C:\Windows\system32\IMM32.dllModLoad: 000007fe`febd0000 000007fe`fecd2000 C:\Windows\system32\MSCTF.dllModLoad: 000007fe`ffc50000 000007fe`ffcec000 C:\Windows\system32\msvcrt.dllModLoad: 000007fe`fe8a0000 000007fe`fea78000 C:\Windows\system32\ole32.dllModLoad: 000007fe`fe6b0000 000007fe`fe783000 C:\Windows\system32\OLEAUT32.dllModLoad: 000007fe`fef50000 000007fe`ffba3000 C:\Windows\system32\SHELL32.dllModLoad: 000007fe`feed0000 000007fe`fef43000 C:\Windows\system32\SHLWAPI.dllModLoad: 000007fe`fd820000 000007fe`fd82b000 C:\Windows\system32\VERSION.dllModLoad: 000007fe`fc450000 000007fe`fc489000 C:\Windows\system32\WINMM.dllModLoad: 000007fe`fc3f0000 000007fe`fc445000 C:\Windows\system32\OLEACC.dllModLoad: 000007fe`f0900000 000007fe`f09a6000 C:\Stella\MSVCP120.dllModLoad: 000007fe`f06a0000 000007fe`f078f000 C:\Stella\MSVCR120.dll(4a4.13d8): Break instruction exception - code 80000003 (first chance)*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -ntdll!DbgBreakPoint:00000000`77a161f0 cc int 3Now, when I select Debug > Go in the menu, here's the second output that I received: 0:000> gModLoad: 000007fe`feec0000 000007fe`feecd000 C:\Windows\system32\LPK.DLLModLoad: 000007fe`fe5b0000 000007fe`fe64b000 C:\Windows\system32\USP10.dllModLoad: 000007fe`fcf70000 000007fe`fd169000 C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6002.18305_none_1509f852f40ee5cd\comctl32.dllModLoad: 000007fe`f9260000 000007fe`f9267000 C:\Windows\system32\shfolder.dllModLoad: 000007fe`fe270000 000007fe`fe296000 C:\Windows\system32\USERENV.dllModLoad: 000007fe`fe250000 000007fe`fe26c000 C:\Windows\system32\Secur32.dllModLoad: 000007fe`fca30000 000007fe`fca81000 C:\Windows\system32\uxtheme.dllModLoad: 000007fe`ffbb0000 000007fe`ffc49000 C:\Windows\system32\CLBCatQ.DLLModLoad: 000007fe`f5ff0000 000007fe`f602d000 C:\Windows\System32\dinput8.dllModLoad: 000007fe`fc950000 000007fe`fc95b000 C:\Windows\system32\HID.DLLModLoad: 000007fe`fece0000 000007fe`feebc000 C:\Windows\system32\SETUPAPI.DLLModLoad: 000007fe`fd1b0000 000007fe`fd1e9000 C:\Windows\system32\WINTRUST.dllModLoad: 000007fe`fdb40000 000007fe`fdc7b000 C:\Windows\system32\CRYPT32.dllModLoad: 000007fe`fdcf0000 000007fe`fdd09000 C:\Windows\system32\MSASN1.dllModLoad: 000007fe`fe520000 000007fe`fe538000 C:\Windows\system32\imagehlp.dllModLoad: 00000000`022f0000 00000000`0230e000 C:\Windows\system32\XInput1_3.dllModLoad: 000007fe`f0700000 000007fe`f078b000 C:\Windows\system32\XAudio2_7.dllModLoad: 000007fe`fc0a0000 000007fe`fc0d6000 C:\Windows\System32\MMDevApi.dllModLoad: 000007fe`fbca0000 000007fe`fbcd3000 C:\Windows\system32\AUDIOSES.DLLModLoad: 000007fe`fba20000 000007fe`fba9a000 C:\Windows\system32\audioeng.dllModLoad: 00000000`77b70000 00000000`77b79000 C:\Windows\system32\PSAPI.DLLModLoad: 000007fe`fd2b0000 000007fe`fd2b8000 C:\Windows\system32\AVRT.dll(1198.244): Illegal instruction - code c000001d (first chance)(1198.244): Illegal instruction - code c000001d (!!! second chance !!!)*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\Stella\MSVCR120.dll -MSVCR120!log+0x2d3:000007fe`f0952bc3 c5e173d034 vpsrlq xmm3,xmm0,34hI checked the C:\Symbols directory and I found that the debugger created the msvcrt120.amd.pdb and ntdll.pdb sub-directories containing the respective files? What should I do with the *.pdb files?

That's what I've been thinking. The 64-bit version of Stella 4.0 tries to call an API that neither exists on Windows XP x64 nor Windows Vista x64. How can I use the Windbg feature with Stella 4.0 to investigate the issue on Vista? Would I have to download the Windows Debugging Tools from the Windows 7 SDK?

I have a problem here. When I try to run the 64-bit version of a application such as Stella 4.0 that was built with the 64-bit version of Visual Studio 2013, the application crashes. The problem details are as follows: Other applications built using the 64-bit version of Visual Studio 2013 such as Media Player Classic do work under Vista x64. Is there a way to fix or debug this issue? I know that this issue might have been resolved under Windows 7 SP1, but what about Windows Vista SP2 users?

Okay, I'm starting to get someone here. I took the measure by temporary disabling all add-ons in Internet Explorer 9. After I reboot, I will enable one add-on at a time until I determine which add-on could be causing IE9 to crash. If disabling the add-ons doesn't help, then I will do a scan to determine what malware could be causing IE9 to crash as well.

I already have Firefox and other browsers installed. For some odd reason, something may have corrupted the files that is required for IE9 to work on various websites. Everytime IE9 crashes, all of the dumps are starting to pile up. I'm hoping to know what could be causing IE9 to crash.

In case a direct download link may help, here is it: IE8-WindowsVista-x64-ENU.exe When I managed to test Internet Explorer 8 and versions of IE all the way down to Internet Explorer 5.5, it does not do that. [...] I might have to try running in Safe Mode or creating a new account to see if this fixes the issue and if it still doesn't then, I might be at a impasse here. Yes. Well... Considering IE8 works OK and it's available for you, please do enlighten me: why is it downgrading to (much more solid) IE8, and calling it a day, is not an option at all? More and more websites are dropping IE8 support like they did with IE7 which means that certain parts of the website aren't going to work correctly under IE8 and below.

In case a direct download link may help, here is it: IE8-WindowsVista-x64-ENU.exe Not really... But it sounds like a good idea. Okay, I managed to do some limited tested on the family computer running Windows Vista Home Premium 32-bit. I managed to access Livestream on that computer running IE9 (32-bit) and all of the functions work fine. I managed to open an IE window running Internet Explorer 9 using IETester and when I did, IETester crashed, referencing to mshtml.dll. Here are the details: When I managed to test Internet Explorer 8 and versions of IE all the way down to Internet Explorer 5.5, it does not do that. So with that said, something could be causing IE9 to crash. Either it's the malware, a update to my EVGA 8400GS graphics driver or a botched security updates that crippled some of the functionality of Internet Explorer 9. I might have to try running in Safe Mode or creating a new account to see if this fixes the issue and if it still doesn't then, I might be at a impasse here.

When I reverted back to Internet Explorer 7, I was re-directed to the mobile version of the Twitter website, instead of the regular version. If I were to access Livestream via IE7, I'd received a notice that the browser is no longer supported. As for Internet Explorer 8 (which is the last to support Windows XP/Server 2003), I'm unable to test it. If I have time, I'm gonna at least test websites on other computers with Internet Explorer 9 to see if the same issue comes up or not. Have you heard about IETester? If I get a chance, I'll be able to test Livestream and Twitter webpages to see if it works with Internet Explorer 8.

I have MalwareBytes Anti-Malware (MBAM) installed. I don't know if Windows Defender is the issue here or not...so, I turned off all of the features in Windows Defender. And yes, I already have Windows Vista SP2 installed.

Okie. I did uninstall IE9 and reinstalled IE9 again and it didn't solve things. When I went to someone's Twitter account, Internet Explorer 9 crashed again: When I went to Livestream to try to access the chat features, Internet Explorer 9 crashed too: It appears that there maybe some HTML coding inside webpages that causes Internet Explorer 9 to crash, but works on other browsers. I have yet to test this issue on other computers to see if the problem occurs on other computers or not.

Thank you so much for the clarification. I'll do the procedure and remove IE9 now to see if it will get rid of the errors that I have been experiencing. If the problems persist, I'll get back to you. Update: Internet Explorer 9 has been removed and has been reverted back to Internet Explorer 7, the browser that came with Windows Vista RTM. I will re-install IE9 and re-install the updates to see if the problem persists or not.

I don't know if I can fully remove IE9 as it has all of the updates installed since it may leave my PC with functionality issues. Recently, IE9 crashed again while trying to access certain Livestream functions.

Adjusting the cache size doesn't stop Internet Explorer 9 from crashing due to USP10.DLL.

Yes. After I reset Internet Explorer 9 to its default settings, I have modified the Temporary Internet File settings by raising the limit on the size of the disk cache to 1 GB. There are 2,886 files in 31 folders taking up close to 94 MB. I'm wondering if reducing the size of the disk cache will do the trick or not. I'm not sure if I'm correct here, but for some reason, the ScrpitCheckCache dependency in USP10.DLL might have caused IE9 to crash.

Thanks for telling me. I don't think that you use 4shared at all. I guess that I'll need ti use OneDrive then. When I'm done, I'll PM you. Sorry for the trouble, but I was tired. Edit: Private message has been sent. I sure hope that you look over the dump file and investigate what has been causing IE9 to crash.

I actually reset the Internet Explorer 9 to the default settings and it didn't help. Attempting to reinstall IE9 gives the error message: Plus, I have all of the updates applied to IE9. I'm currently uploading the iexplore.exe.5872.dmp right now on my 4shared account and privately note when it's all done.

As the browser keeps crashing over and over and it finally generated a 293 MB dump iexplore.exe.dmp found in the C:\LocalDumps directory. I managed to upload it to my 4Shared account and I will send you a link in a private message when it's all finished.

Thanks for the help. It seems that Microsoft might have released a bad security update that affected Windows Vista users. Edit: I had to back out of the KB2957509 update and hide the update. I'm gonna be contacting Twitter via e-mail to see what was up with it right now.

I'm cross-posting this from the deviantART forums and I've decided to post this here to see if you can help solve the Internet Explorer issue involving the USP10.DLL file. I have a problem with running Internet Explorer 9 under Windows Vista x64 and it has to do with the USP10.DLL (Uniscribe) file. Every time I try to view someone's Twitter's account using Internet Explorer 9, the browser crashes! Here's the error from the Event Viewer that I received: The Event ID is 1000. I'm wondering if this error is reproduced with Internet Explorer 9 under Windows 7 or Windows Server 2008. Could this issue also have to do with a defective security update KB2957509 that was released earlier this month? I should scan this computer for malware to see if this might be the cause or not? Just curious.

I already did install Windows 2000 in VirtualBox. However, I hadn't had the time to test it with UURollup at this time.

Has anyone tested Firefox 29 and Firefox 30 on Windows 2000 with the latest version of UURollup? As far as I know, I recently switched to a new computer a few months back and as a result of this, I can no longer test new versions of Firefox on Windows 2000. Also, in Firefox 30, developers removed the dead OS/2 support code due to lack of contribution and the newer code that hasn't been able to work properly on OS/2.

Has anyone run Windows NT 3.51, Windows NT 4.0 or Windows 2000 under Bochs with networking support successfully? Well, the latest SVN revision is 2014-01-05 and according to therock247uk from the Vogons DOSBox forums, Bochs has working Slirp support on Windows. So far, in the official release of Bochs 2.6.2, there is no networking support. Even with WinPcap installed, networking hasn't been working correctly for years, niclist.exe network detection remains broken and Slirp doesn't work in the official Windows release. Furthermore, if I try to enable Slirp support in the Windows NT 4.0 test VM on Bochs in the settings.bxrc config file, this log with error messages get displayed: Has anyone compiled Bochs 2.6.2 with Slirp support using the SVN 2014-01-05 revision? If so, I would like to grab a copy of the complied version and try to get networking working. Also, the lowest processor that Bochs will be able to emulate is a Pentium MMX. I would also love to see Bochs compiled to run either on a 80386, 80486 or original Pentium. Windows NT 3.51 and Windows NT 4.0 ran on these processors very well. If you would like more information on this, please let me know.