BSOD help needed


  1. Posts : 5,915
    Windows 10 Pro X64
       #1

    BSOD help needed


    Looking at my dads computer. He gets a BSOD pretty much daily.

    Attachment 321972
      My Computer


  2. Posts : 3,904
    Windows 7 Ultimate 64-bit
       #2

    Im not a pro but looking at the dumps i found this?

    Possibly graphics related or graphics driver?

    Event[7]:
    Log Name: Application
    Source: Windows Error Reporting
    Date: 2013-08-01T08:32:11.000
    Event ID: 1001
    Task: N/A
    Level: Information
    Opcode: Info
    Keyword: Classic
    User: N/A
    User Name: N/A
    Computer: 37L4247D28-05
    Description:
    Fault bucket , type 0
    Event Name: PnPGenericDriverFound
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: x86
    P2: PCI\VEN_1002&DEV_9904&SUBSYS_85261043&REV_00
    P3:
    P4:
    P5:
    P6:
    P7:
    P8:
    P9:
    P10:

    Attached files:

    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_x86_2abaaa1240b1c14d76438c373d083e88be1 681_cab_0750b49e

    Analysis symbol:
    Rechecking for solution: 0
    Report Id: 62f32353-faa6-11e2-b308-d29c12173334
    Report Status: 6
      My Computer


  3. Posts : 17,322
    Win 10 Pro x64
       #3

    That event above is from August last year, that's not in the dump file it's in the eventapp.txt.

    Looking in the msinfo32 file I see the driver is dated 2-14-2013 which looks to be the 13.1 version so you may want to try a newer one, like 13.9.

    Previous AMD Catalyst? Display Drivers

    I tried opening a bunch of those dumps Doug, they just hang for me so I can't even get the bugcheck, sorry about that.

    Maybe they will load for someone else.
      My Computer


  4. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #4

    EDIT: Derek beat me to it.

    Hey Doug,

    I've just looked through the first three logs and they're all 0xA0000001, these are considered a custom bugcheck coded into ATI drivers. And checking the logs the AMD drivers show up time and again.

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A0000001, {5, 0, 0, 0}
    
    *** WARNING: Unable to verify timestamp for atikmpag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
    Probably caused by : atikmdag.sys ( atikmdag+18755 )
    
    Followup: MachineOwner
    Code:
    a7277934 9063ed69 60000100 a7277950 9064ba17 atikmdag+0x18755
    a7277940 9064ba17 86835000 a72779c4 a72779a0 atikmdag+0x19d69
    a7277950 9067f51b 857df000 a7277960 00000040 atikmdag+0x26a17
    a72779a0 9068054b 86837000 9063ed52 86835000 atikmdag+0x5a51b
    a72779fc 90680671 86837000 86840650 00000000 atikmdag+0x5b54b
    a7277a18 9068071c 86837000 86840650 00000000 atikmdag+0x5b671
    a7277ab8 906807f1 86837000 86840650 00000000 atikmdag+0x5b71c
    a7277ae0 90686bc4 86837000 86840650 a7277b00 atikmdag+0x5b7f1
    a7277ba4 9067e20f 86837000 858d1040 858d1040 atikmdag+0x61bc4
    a7277bbc 9063e9b0 86837000 8542ffd0 a7277be4 atikmdag+0x5920f
    a7277bcc 8fc41c12 858d1040 00000000 858cc000 atikmdag+0x199b0
    a7277be4 8fcb1b14 858d1040 00000000 a7277c08 atikmpag+0x5c12
    a7277bf4 82cd4f9e 858cc000 85791920 00000000 dxgkrnl!DpiFdoMessageInterruptRoutine+0x17 (FPO: [Non-Fpo])
    a7277c08 82c84e1d 858cc000 85791920 a7277c34 nt!KiInterruptMessageDispatch+0x12
    a7277c08 5b5d1bd8 858cc000 85791920 a7277c34 nt!KiInterruptDispatch+0x6d (FPO: [0,2] TrapFrame @ a7277c34)
    02b54ae0 00000000 00000000 00000000 00000000 0x5b5d1bd8
    They're pretty old mate and could do with updating.

    Code:
    2: kd> lmvm atikmdag
    start    end        module name
    90625000 90ffa000   atikmdag T (no symbols)           
        Loaded symbol image file: atikmdag.sys
        Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
        Image name: atikmdag.sys
        Timestamp:        Thu Feb 14 22:36:39 2013 (511D66F7)
        CheckSum:         0098F232
        ImageSize:        009D5000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  5. Posts : 3,904
    Windows 7 Ultimate 64-bit
       #5

    Well atleast i was on the right scent! :)
      My Computer


  6. Posts : 5,915
    Windows 10 Pro X64
    Thread Starter
       #6

    Thanks guys, updating drivers now
      My Computer


  7. Posts : 17,322
    Win 10 Pro x64
       #7

    HLPTech said:
    Well atleast i was on the right scent! :)
    That you were, good sniffing.
      My Computer


  8. Posts : 5,915
    Windows 10 Pro X64
    Thread Starter
       #8

    Updated his drivers and the chipset drivers from ASUS for his motherboard. He is good now, thanks again.
      My Computer


  9. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #9

    Glad you got it sorted Doug.
      My Computer


  10. Posts : 3,904
    Windows 7 Ultimate 64-bit
       #10

    Glad its sorted :)
      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 14:49.
Find Us