Status: Unconfirmed Owner: [EMAIL PROTECTED] Labels: Type-Bug Pri-2 OS-All Area-Misc
New issue 4775 by chaostya: BSOD on selecting "open link in a new tab" http://code.google.com/p/chromium/issues/detail?id=4775 Chrome Version : 0.4.154.25 URLs (if applicable) : no specific Other browsers tested: Add OK or FAIL after other browsers where you have tested this issue: Safari 3: Not tested Firefox 3: Not tested IE 7: Not tested What steps will reproduce the problem? 1. Open google results page 2. Click "open link in a new tab" 3. Screen goes black, then image returns, you say "hmmm" and "open link a new tab" for next link ... computer goes to BSOD What is the expected result? Open link a new tab What happens instead? BSOD Please provide any additional information below. Attach a screenshot if possible. Attaching 2 minidumps. And WinDbg listing when opened on my machine: Loading Dump File [C:\WINDOWS\Minidump\Mini110708-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: C:\WINDOWS\Symbols Executable search path is: Unable to load image ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x80554040 Debug session time: Thu Nov 6 14:45:58.281 2008 (GMT+2) System Uptime: 3 days 3:48:23.338 Unable to load image ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe Loading Kernel Symbols ...................................................................................................................................... Loading User Symbols Loading unloaded module list .................................................. Unable to load image win32k.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for win32k.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, bf952937, a77bbc00, 0} Probably caused by : win32k.sys ( win32k!NtGdiEngStretchBltROP+13c ) Followup: MachineOwner --------- kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: c0000005, The exception code that was not handled Arg2: bf952937, The address that the exception occurred at Arg3: a77bbc00, Trap Frame Arg4: 00000000 Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". FAULTING_IP: win32k!NtGdiEngStretchBltROP+13c bf952937 8b4004 mov eax,dword ptr [eax+4] TRAP_FRAME: a77bbc00 -- (.trap 0xffffffffa77bbc00) ErrCode = 00000000 eax=00000000 ebx=00000100 ecx=00000000 edx=00000000 esi=e1ee3000 edi=e4d44c00 eip=bf952937 esp=a77bbc74 ebp=a77bbc8c iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 win32k!NtGdiEngStretchBltROP+0x13c: bf952937 8b4004 mov eax,dword ptr [eax+4] ds:0023:00000004=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0x8E PROCESS_NAME: chrome.exe LAST_CONTROL_TRANSFER: from bf949fc4 to bf952937 STACK_TEXT: a77bbc8c bf949fc4 e12e4718 e1ee3200 e1b25530 win32k!NtGdiEngStretchBltROP+0x13c a77bbd28 bf94a040 81012b80 00bcec40 00000100 win32k!GreIcmSetBrushBitmap+0x58 a77bbd48 8053d648 81012b80 00bcec40 00000100 win32k!NtGdiIcmBrushInfo+0x3e a77bbd64 7c90e4f4 badb0d00 00bce954 a8654d98 nt!PopReadShutdownPolicy+0x7c WARNING: Frame IP not in any known module. Following frames may be wrong. a77bbd68 badb0d00 00bce954 a8654d98 a8654dcc 0x7c90e4f4 a77bbd6c 00bce954 a8654d98 a8654dcc 00000000 0xbadb0d00 a77bbd70 a8654d98 a8654dcc 00000000 00000000 0xbce954 a77bbd74 a8654dcc 00000000 00000000 00000000 0xa8654d98 a77bbd78 00000000 00000000 00000000 00000000 0xa8654dcc STACK_COMMAND: kb FOLLOWUP_IP: win32k!NtGdiEngStretchBltROP+13c bf952937 8b4004 mov eax,dword ptr [eax+4] SYMBOL_STACK_INDEX: 0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32k IMAGE_NAME: win32k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 48ce513a SYMBOL_NAME: win32k!NtGdiEngStretchBltROP+13c FAILURE_BUCKET_ID: 0x8E_win32k!NtGdiEngStretchBltROP+13c BUCKET_ID: 0x8E_win32k!NtGdiEngStretchBltROP+13c Followup: MachineOwner --------- Attachments: Mini110708-01.dmp 96.0 KB Mini112508-01.dmp 96.0 KB -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-bugs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
