BSOD When typing, searching or going other websites with Google Chrome


  1. Posts : 2
    Windows 7 Ultimate 64 bit
       #1

    BSOD When typing, searching or going other websites with Google Chrome


    Hi guys, i have BSOD problem when i typing, searching or going to otherwebsites to read articles or images and

    then instantly BlueScreen came up even in facebook page too, i dont know what is the problem the problem

    start like maybe 4-5 months ago that i changed my Graphics Card before didnt happening this all i remember is

    that after i changed my Graphic Card then 2-3 weeks problem starts, if u guys gave any suggestion to this

    problem please post, here my details below:

    Here is my SevenForums Diagnostic folder about BSOD:

    Before my Graphic Card: NVIDIA GeForce 9300Ge (256MB i think i can't remember)

    Now my graphic card: AMD Radeon HD 6570 (2048Mb memory DDR3)

    Regards...
      My Computer


  2. Posts : 3,056
    Windows 10
       #2

    Hello and welcome to SF zuzuu96 :).

    The bugchecks seem to fair well with your observation with regards
    to the GPU (graphics card) upgrade.

    Code:
    VIDEO_SCHEDULER_INTERNAL_ERROR (119)
    The video scheduler has detected that fatal violation has occurred. This resulted
    in a condition that video scheduler can no longer progress. Any other values after
    parameter 1 must be individually examined according to the subtype.
    Arguments:
    Arg1: 0000000000000001, The driver has reported an invalid fence ID.
    Arg2: 00000000ff000000
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    
    Debugging Details:
    ------------------
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x119
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  a
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    DPC_STACK_BASE:  FFFFF80000BA2FB0
    
    LAST_CONTROL_TRANSFER:  from fffff88003bd722f to fffff80002c94bc0
    
    STACK_TEXT:  
    fffff800`00b9c118 fffff880`03bd722f : 00000000`00000119 00000000`00000001 00000000`ff000000 00000000`00000000 : nt!KeBugCheckEx
    fffff800`00b9c120 fffff880`0fd46ec5 : 00000000`000043ba 00000000`ff000000 00000000`00000000 00000000`00000000 : watchdog!WdLogEvent5+0x11b
    fffff800`00b9c170 fffff880`0fd471cf : fffffa80`05a77000 fffff800`00b9c2b0 fffffa80`000011ac fffff800`00b9c2b0 : dxgmms1!VidSchiVerifyDriverReportedFenceId+0xad
    fffff800`00b9c1a0 fffff880`0fd46f82 : fffff800`000043ba fffffa80`0444e000 fffffa80`05a77000 00000000`00000000 : dxgmms1!VidSchDdiNotifyInterruptWorker+0x23b
    fffff800`00b9c1f0 fffff880`042cc13f : fffffa80`04f67480 fffff800`00b9c220 fffff800`00b9c2d0 fffff880`03e1156a : dxgmms1!VidSchDdiNotifyInterrupt+0x9e
    fffff800`00b9c220 fffff880`0426eb36 : fffffa80`04474dc0 00000000`00000002 fffff800`00b9c2d9 fffff880`03e025c2 : dxgkrnl!DxgNotifyInterruptCB+0x83
    fffff800`00b9c250 fffffa80`04474dc0 : 00000000`00000002 fffff800`00b9c2d9 fffff880`03e025c2 00000000`00000000 : atikmpag+0x45b36
    fffff800`00b9c258 00000000`00000002 : fffff800`00b9c2d9 fffff880`03e025c2 00000000`00000000 00000000`00000008 : 0xfffffa80`04474dc0
    fffff800`00b9c260 fffff800`00b9c2d9 : fffff880`03e025c2 00000000`00000000 00000000`00000008 fffffa80`04e1c050 : 0x2
    fffff800`00b9c268 fffff880`03e025c2 : 00000000`00000000 00000000`00000008 fffffa80`04e1c050 fffff880`03e12aed : 0xfffff800`00b9c2d9
    fffff800`00b9c270 fffff880`03e02783 : fffffa80`04e1cd28 00000000`00000001 00000000`00000002 000043ba`ff000000 : USBPORT!USBPORT_Xdpc_iSetState+0x2a
    fffff800`00b9c2a0 fffff880`03e1156a : fffffa80`04d2c1a0 fffff880`03e12960 fffffa80`05a82c00 fffff880`0fd4b0a1 : USBPORT!USBPORT_Xdpc_iSignal+0xcb
    fffff800`00b9c2d0 fffffa80`00000000 : 00000000`ff000000 00000000`00000210 00000000`00000000 fffffa80`05995e50 : USBPORT!GetHcFdoExt+0x1a
    fffff800`00b9c300 00000000`ff000000 : 00000000`00000210 00000000`00000000 fffffa80`05995e50 fffffa80`039d2160 : 0xfffffa80`00000000
    fffff800`00b9c308 00000000`00000210 : 00000000`00000000 fffffa80`05995e50 fffffa80`039d2160 fffffa80`039d2000 : 0xff000000
    fffff800`00b9c310 00000000`00000000 : fffffa80`05995e50 fffffa80`039d2160 fffffa80`039d2000 00000000`00000004 : 0x210
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    atikmpag+45b36
    fffff880`0426eb36 ??              ???
    
    SYMBOL_STACK_INDEX:  6
    
    SYMBOL_NAME:  atikmpag+45b36
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmpag
    
    IMAGE_NAME:  atikmpag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  52a231d9
    
    FAILURE_BUCKET_ID:  X64_0x119_1_DRIVER_REPORTED_INVALID_FENCE_ID_atikmpag+45b36
    
    BUCKET_ID:  X64_0x119_1_DRIVER_REPORTED_INVALID_FENCE_ID_atikmpag+45b36
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x119_1_driver_reported_invalid_fence_id_atikmpag+45b36
    
    FAILURE_ID_HASH:  {1d656d04-b896-4c50-1a4b-ca7fd5789058}
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm atikmpag
    Browse full module list
    start             end                 module name
    fffff880`04229000 fffff880`042c9000   atikmpag T (no symbols)           
        Loaded symbol image file: atikmpag.sys
        Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
        Image name: atikmpag.sys
        Browse all global symbols  functions  data
        Timestamp:        Fri Dec 06 22:21:45 2013 (52A231D9)
        CheckSum:         0009FEFF
        ImageSize:        000A0000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    My guess would be that it is due to lack of power / incompatibility (BIOS).
    I wasn't able to find an update to the BIOS on HP's webpage.
    Code:
    !sysinfo machineid
    Machine ID Information [From Smbios 2.5, DMIVersion 37, Size=2013]
    BiosMajorRelease = 5
    BiosMinorRelease = 5
    BiosVendor = Phoenix Technologies, LTD
    BiosVersion = 5.20
    BiosReleaseDate = 10/28/2008
    SystemManufacturer = HP-Pavilion
    SystemProductName = FT966AA-ABG s3780a
    SystemFamily = 103C_53316J
    SystemVersion =  
    SystemSKU = FT966AA#ABG
    BaseBoardManufacturer = FOXCONN
    BaseBoardProduct = Irvine
    BaseBoardVersion = HP P/N
    The best way to test is to try the GPU on a more powerful / modern (stable!) system
    and observe the situation.
    If it still crashes then it is the GPU which is at fault and you should RMA it, it is if stable
    then it is the above mentioned given the system truly was stable with the older GPU.

    You can also test the GPU using Furmark.
    Test for thermals and stability:

    • Download HWinfo and post a Screenshot of the sensors window, one at idle and another while putting load on the Furmark for the GPU.


    //Let us know the results.
      My Computer


  3. Posts : 2
    Windows 7 Ultimate 64 bit
    Thread Starter
       #3

    Here is the results:
    I test funcmark with 1980x1080 in 10 min my GPU got 80 degrees at 99% Load and 4FPS
      My Computer


  4. Posts : 3,056
    Windows 10
       #4

    The screenshots show no GPU utilization.
    Did the GPU continue to heatup or did you stop the test?
    Did you check for a newer BIOS?
    Did you test the GPU separately as mentioned in my previous post?
    Give out as much information as you can or I won't be able to help you.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 03:24.
Find Us