chrome.exe was blocked from making system calls to Win32k.sys.
Reported by
artins...@gmail.com,
Aug 2
|
|||||
Issue description
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.75 Safari/537.36
Steps to reproduce the problem:
1. Open the Windows Event Viewer > Applications and Services logs > Microsoft > Windows > Security Mitigations
2. Open a new tab in Chrome.
3. Refresh the Event Viewer, a new entry will appear in the log every time you open a new tab.
Details:
System
- Provider
[ Name] Microsoft-Windows-Security-Mitigations
[ Guid] {FAE10392-F0AF-4AC0-B8FF-9F4D920C3CDF}
EventID 10
Version 0
Level 3
Task 5
Opcode 0
Keywords 0x8000000000000000
- TimeCreated
[ SystemTime] 2018-08-02T01:48:12.068325600Z
EventRecordID 160968
Correlation
- Execution
[ ProcessID] 6792
[ ThreadID] 768
Channel Microsoft-Windows-Security-Mitigations/KernelMode
Computer MSI-X299
- Security
[ UserID] S-1-5-21-3993003903-249957610-1136822349-1001
- EventData
ProcessPathLength 80
ProcessPath \Device\HarddiskVolume4\Program Files (x86)\Google\Chrome\Application\chrome.exe
ProcessCommandLineLength 512
ProcessCommandLine "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --type=renderer --field-trial-handle=1376,18167319134038153551,7205435922304296171,131072 --enable-features=DrawOcclusion,FontCacheScaling,NewAudioRenderingMixingStrategy,ParallelDownloading,PictureInPicture --disable-features=SoundContentSetting --service-pipe-token=721C8C37E8FA9AF34713D8B8CB055E8D --lang=en-US --user-data-dir="D:\Chrome\User\Artins" --disable-client-side-phishing-detection --enable-offline-auto-reload --enable-offline-auto-relo
CallingProcessId 6792
CallingProcessCreateTime 2018-08-02T01:48:12.054908600Z
CallingProcessStartKey 66428094503717043
CallingProcessSignatureLevel 0
CallingProcessSectionSignatureLevel 0
CallingProcessProtection 0
CallingThreadId 768
CallingThreadCreateTime 2018-08-02T01:48:12.054909500Z
What is the expected behavior?
What went wrong?
Opening a new tab causes Windows security mitigations to trigger. It's flooding the event log.
Did this work before? N/A
Chrome version: 68.0.3440.75 Channel: stable
OS Version: 10.0
Flash Version:
,
Aug 9
Tried testing the issue on reported version #68.0.3440.75 using Windows10, by following below steps. Steps: ===== 1.Launched chrome. 2.Opened Event Viewer > Applications and Services logs > Microsoft > Windows > Security Mitigations 3.Opened new tab but unable to observe a new log in log summary. Attached screencast for reference. @Reporter: Could you please review the attached screen-cast and confirm if anything being missed here and request you to retry this issue with fresh profile without any extensions/apps or reset all the flags and let us know if issue still persists. Thanks.!
,
Aug 9
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 5
Tried testing the issue as per comment#3 on reported chrome version#68.0.3440.75 and latest chrome version #71.0.3543.0 using Windows 10 by following below steps. Steps: ===== 1.Launched chrome. 2.Opened Event Viewer > Applications and Services logs > Microsoft > Windows > Security Mitigations 3.Expanded Security Mitigations further to see event logs. 4.Opened new tab and navigated to "google.com", observed entry in event log. 5.Opened multiple new tabs but unable to see a new entry in event log, on each and every new tab opening. Attached screencast for reference. @reporter: Could you please review the attached screencast and let us know if anything is being missed here.Please check if the issue is seen on recent chrome version #69.0.3947.81, as recently the stable has been rolled out to M-69.You can download the latest chrome builds from the link "https://www.chromium.org/getting-involved/dev-channel" and let us know the expected behaviour so that it would be really helpful for better triaging of the issue. Thanks.!
,
Nov 16
**UI mass Triage** We were unable to reproduce this bug. If this bug still reproduces for you, please reopen or file a new issue. Thanks! |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by krajshree@chromium.org
, Aug 2