BSOD when using Google Chrome

Welcome to the forum.

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

adfs.SYS Fri Jun 27 02:52:37 2008 (48640195)
Adobe File System Driver
Driver Reference Table - adfs.SYS

btwl2cap.sys Sat Apr 4 06:28:45 2009 (49D6A9BD)
Broadcom Bluetooth L2CAP Servicen
Driver Reference Table - btwl2cap.sys

CtClsFlt.sys Mon Jun 15 11:06:41 2009 (4A35D6E1)
Creative Camera Class Upper Filter Driver
Driver Reference Table - CtClsFlt.sys

• To perform a clean install of a driver, follow this tutorial:
  
  • How to Clean Left Over Driver Files with Driver Sweeper

If no updates are available, please uninstall the software.

• Revo Uninstaller "Free"
  
  • Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling. This allows you to remove leftover registry entries of the software.
    
    • Link to download: Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Update the ATI drivers to their latest.

atikmpag.sys Wed May 23 07:08:40 2012 (4FBC3898)
ATI Video driver (remove the Catalyst Control Center and only install the Display Driver)
Driver Reference Table - atikmpag.sys

atikmdag.sys Wed May 23 07:45:20 2012 (4FBC4130)
ATI Video driver (remove the Catalyst Control Center and only install the Display Driver)
Driver Reference Table - atikmdag.sys

• To perform a clean install of a driver, follow this tutorial:
  
  • How to Clean Left Over Driver Files with Driver Sweeper

• System File Checker
  
  • The SFC /SCANNOW Command - System File Checker scans the integrity of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible. If you have modified your system files as in theming explorer/system files, running sfc /scannow will revert the system files to it's default state.
    
    • Link to full tutorial: SFC /SCANNOW Command - System File Checker
• Run Disk Check in Windows 7
  
  • Run this on your Hard Drive(s). This will show you how to run Check Disk or chkdsk in Windows 7 to check a selected hard disk for file system errors and bad sectors on it. With both boxes checked for all HDDs and with Automatically fix file system errors. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log
    
    • Link to full tutorial: Disk Check

• Virus Check:
  
  • Make scans with these tools below:
    
    • TDSSKiller Rootkit Removal Utility Free Download | Kaspersky Lab US
    • Online Virus Scanner Eset
• Application conflict:
  
  • Reduce the start-up items. This will help avoid software conflicts:
    
    • Remove Startup Programs in Windows 7
    • Clean Startup in Windows 7

Code:

BugCheck 119, {1, cb5, 10a0, 109f}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiVerifyDriverReportedFenceId+ad )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 119, {1, 1596, 1598, 1597}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiVerifyDriverReportedFenceId+ad )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 119, {1, f495, f497, f496}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiVerifyDriverReportedFenceId+ad )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 119, {1, 61ed, 63d9, 63d8}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiVerifyDriverReportedFenceId+ad )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 119, {1, 3841, 3aa6, 3aa5}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiVerifyDriverReportedFenceId+ad )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 116, {fffffa80040024e0, fffff8800403bf94, 0, 2}
Probably caused by : atikmpag.sys ( atikmpag+6f94 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

I had done the steps u suggested
-Update ATI driver
-Reinstall Bluetooth
-Uninstall Camera Driver
-System File Checker done and don't have any violation
-Disk Check ok

but i don't know which Adobe File System Driver I need to install.
The bluescreen error still occur..now even my built-in card reader (Removable Disk) also missing in My Computer..

May i ask for few questions ?
the ATI Driver cannot install only driver, I just only can install the package together with Catalyst Center is it ok?
How to check the driver is updated?
Is it possible is the hardware problem?

this is the report again..can help me check for it? Koolkat, Thanks for helping..and sorry for disturb again..

According to the crash dump that you posted, the display driver is not updated. May be it is earlier than updating the driver?

Let us know for any further issue.

Code:

fffff880`04000000 fffff880`0404b000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Sat Jan 29 04:12:18 2011 (4D43464A)
    CheckSum:         00052309
    ImageSize:        0004B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

What you have installed? The old driver again!

Code:

    Image name: atikmpag.sys
    Timestamp:        Sat Jan 29 04:12:18 2011 (4D43464A)

Then how it would be any better?

Update your ATI/AMD display driver.
You can get it from the link in our forum, Latest AMD Catalyst Video Driver for Windows 7, or you may go to AMD Graphics Driver and Software and opt for Automatically Detect and Install the appropriate driver for your card.


During installation, you may opt for advanced installation, and install the display driver only, not the Catalyst Control Center.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8005dbb4e0, fffff88002c84f94, 0, 2}

*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+6f94 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8005dbb4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88002c84f94, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP: 
atikmpag+6f94
fffff880`02c84f94 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`03dc99c8 fffff880`02d26000 : 00000000`00000116 fffffa80`05dbb4e0 fffff880`02c84f94 00000000`00000000 : nt!KeBugCheckEx
fffff880`03dc99d0 fffff880`02d25d0a : fffff880`02c84f94 fffffa80`05dbb4e0 fffffa80`04409980 fffffa80`058e9410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`03dc9a10 fffff880`02c0ff07 : fffffa80`05dbb4e0 00000000`00000000 fffffa80`04409980 fffffa80`058e9410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`03dc9a40 fffff880`02c39b75 : 00000000`ffffffff 00000000`0000b83d 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`03dc9b20 fffff880`02c382bb : 00000000`00000102 00000000`00000000 00000000`0000b83d 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`03dc9b50 fffff880`02c0b2c6 : ffffffff`ff676980 fffffa80`058e9410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`03dc9bf0 fffff880`02c37e7a : 00000000`00000000 fffffa80`04409980 00000000`00000080 fffffa80`058e9410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`03dc9d00 fffff800`02f7ecce : 00000000`fffffc32 fffffa80`05810b60 fffffa80`03b94400 fffffa80`05810b60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`03dc9d40 fffff800`02cd2fe6 : fffff880`02f63180 fffffa80`05810b60 fffff880`02f6dfc0 fffff880`01218384 : nt!PspSystemThreadStartup+0x5a
fffff880`03dc9d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+6f94
fffff880`02c84f94 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+6f94

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d43464a

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

Followup: MachineOwner
---------

2: kd> lmvm atikmpag
start             end                 module name
fffff880`02c7e000 fffff880`02cc9000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Sat Jan 29 04:12:18 2011 (4D43464A)
    CheckSum:         00052309
    ImageSize:        0004B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Who told you to do autodetect? And who cares what auto detect says when we can detect that your driver is historically old?

Either do what is suggested or you are at your own.

icekingdom said:

I think there is a misunderstanding...after i used the auto detect, i still remove my ATI driver with Driver Sweeper, and i install the beta 13.0 ATI which is given by u..but it now seldom BSOD , but still lagging..suddnly whole screen lag and mouse cant move..but no more BSOD..

I havent given beta 13.0. You need to install WHQL 13.9.