BSOD Possibly due to Dual Monitor


  1. Posts : 3
    windows 7 home premium 64
       #1

    BSOD Possibly due to Dual Monitor


    Hi All,

    I was wondering whether anyone can give me some advice. I have recently been experiencing the BSOD with my windows 7 64 bit home premium. I have recently added a second monitor to my desktop and initially everything worked fine, it has just seemed to happen more and more.

    I have conducted a GPU check and it came back ok, I also believe I have enough power to run the graphics card, so im at a bit of a loss.

    My graphics card is a Radeon 4850 and all drivers are up to date.

    Could anyone have a look at my dump file and let me know whether it is the card, or whether I need to replace anything else.

    Thanks very much in advance

    Matt
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Hi mattygg.

    It seems to be a grapgics/display related issue on a very old branded laptop.

    Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

    Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
    eXtreme Power Supply Calculator
    Also let us know the wattage of the PSU.

    Update the display driver. But not to the latest one. Install version 13.9 WHQL only.


    And at last, Stress test the Graphics Card using Furmark.
    Video Card - Stress Test with Furmark

    Let us know the results.
    __________________________
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa8003f2b2d0, fffff88003cedefc, 0, 2}
    
    Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
    *** 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+8efc )
    
    Followup: MachineOwner
    ---------
    
    4: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa8003f2b2d0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88003cedefc, 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+8efc
    fffff880`03cedefc 4055            push    rbp
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    STACK_TEXT:  
    fffff880`051159c8 fffff880`03f1e140 : 00000000`00000116 fffffa80`03f2b2d0 fffff880`03cedefc 00000000`00000000 : nt!KeBugCheckEx
    fffff880`051159d0 fffff880`03f1de4a : fffff880`03cedefc fffffa80`03f2b2d0 fffffa80`04fd7c00 fffffa80`04fb4410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`05115a10 fffff880`03fc4f13 : fffffa80`03f2b2d0 00000000`00000000 fffffa80`04fd7c00 fffffa80`04fb4410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
    fffff880`05115a40 fffff880`03feecf1 : 00000000`ffffffff 00000000`000120cc 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`05115b20 fffff880`03fed437 : 00000000`00000102 00000000`00000000 00000000`000120cc 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
    fffff880`05115b50 fffff880`03fc02d2 : ffffffff`ff676980 fffffa80`04fb4410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
    fffff880`05115bf0 fffff880`03fecff6 : 00000000`00000000 fffffa80`05098010 00000000`00000080 fffffa80`04fb4410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
    fffff880`05115d00 fffff800`02d2e2ea : 00000000`fffffc32 fffffa80`04d28b50 fffffa80`03c6c9e0 fffffa80`04d28b50 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`05115d40 fffff800`02a828e6 : fffff800`02c0ce80 fffffa80`04d28b50 fffff800`02c1acc0 3078302c`3078302c : nt!PspSystemThreadStartup+0x5a
    fffff880`05115d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    atikmpag+8efc
    fffff880`03cedefc 4055            push    rbp
    
    SYMBOL_NAME:  atikmpag+8efc
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmpag
    
    IMAGE_NAME:  atikmpag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  517f30ef
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x116_image_atikmpag.sys
    
    FAILURE_ID_HASH:  {83e844bc-fe68-2042-4230-7f5d3e90b48a}
    
    Followup: MachineOwner
    ---------
    
    4: kd> lmvm atikmpag
    start             end                 module name
    fffff880`03ce5000 fffff880`03d44000   atikmpag T (no symbols)           
        Loaded symbol image file: atikmpag.sys
        Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
        Image name: atikmpag.sys
        Timestamp:        Tue Apr 30 08:18:15 2013 (517F30EF)
        CheckSum:         000613E7
        ImageSize:        0005F000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  3. Posts : 3
    windows 7 home premium 64
    Thread Starter
       #3

    Hiya,

    Thanks for the reply.

    I have attached a copy of the speccy report, and also another one, as Speccy gave my motherboard temp as 127C as soon as I turned it on, which is extremely high. I had a look and apparently this is an error with the new version of speccy. The other program shows it at 22C which seems more reasonable.

    I have also been onto the CPU wattage site and it shows that I need 316w but they recommend 369w. My power supply is 750w so I think I should be fine with that.

    I have run the stress test and the temperature reached 99C before levelling out. I ran it for 15 mins.

    Lastly, my computer is a desktop, rather than a laptop. This is also a fresh install of windows 7, I had the same errors with windows 8 when I tested on there too.

    I hope this helps.

    http://speccy.piriform.com/results/P...KXBevX4cxerYnV
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    Laptops dont have PSUs.

    The PSU wattage is enough!

    The GPU temperature seems to be a bit high. Try cleaning the air vents and fan grills. Also see that if the GPU fans are working properly.

    Also, have you changed the driver version?
      My Computer


  5. Posts : 3
    windows 7 home premium 64
    Thread Starter
       #5

    Thanks for the quick reply.

    I have tried cleaning all the fans and vents but I think the card has had it.

    I am currently using 13.9 drivers for the card. Do you think it would be worth going back to an older version?

    Cheers
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #6

    Older than 13.9? No need. It is a very good and stable one.
      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:58.
Find Us