BSOD - New Desktop PC - No discernable pattern


  1. Posts : 3
    windows 7
       #1

    BSOD - New Desktop PC - No discernable pattern


    Hi,

    I have a new Windows 7 PC and am getting BSOD several times per day.
    I cannot detect a patter and a doing nothing except using Office / IE 11 / IE Chrome when the problems occur.

    I have attached the files as per your thread instructions.

    Any help that you can provide would be great.

    Thanks Paul
      My Computer


  2. Posts : 4,772
    Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
       #2

    mrpaulgill said:
    Hi,

    I have a new Windows 7 PC and am getting BSOD several times per day.
    I cannot detect a patter and a doing nothing except using Office / IE 11 / IE Chrome when the problems occur.

    I have attached the files as per your thread instructions.

    Any help that you can provide would be great.

    Thanks Paul
    Hello there Paul!

    Just looked at your dump files seems like the crashes are pointing to atikmdag.sys which is your display card. I would recommend to completely reinstall it.

    You could use this for complete removal Display Driver Uninstaller Download version 12.9.4.0 and make sure you download the latest version from ATI's website.

    Also found some suspicious looking device / drivers :

    Code:
    MpKsl789ff9ef    ROOT\LEGACY_MPKSL789FF9EF\0000    This device is not present, is not working properly, or does not have all its drivers installed.
    Run Malwarebytes and do a complete scan.

    Code:
    Debug session time: Fri Jul  4 19:38:25.401 2014 (UTC + 5:30)
    Loading Dump File [C:\Users\Shyam\SysnativeBSODApps\070414-13462-01.dmp]
    Built by: 7601.18409.x86fre.win7sp1_gdr.140303-2144
    System Uptime: 0 days 1:54:19.868
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    *** 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+1d630 )
    BugCheck A0000001, {5, 0, 0, 0}
    BugCheck Info: Unknown bugcheck code (a0000001)
    Bugcheck code a0000001
    Arguments: 
    Arg1: 00000005
    Arg2: 00000000
    Arg3: 00000000
    Arg4: 00000000
    BUGCHECK_STR:  0xA0000001
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  0xA0000001_atikmdag+1d630
    BiosVersion = 1102
    BiosReleaseDate = 01/20/2014
    SystemManufacturer = System manufacturer
    SystemProductName = System Product Name
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Debug session time: Thu Jul  3 11:14:22.737 2014 (UTC + 5:30)
    Loading Dump File [C:\Users\Shyam\SysnativeBSODApps\070314-26192-01.dmp]
    Built by: 7601.18409.x86fre.win7sp1_gdr.140303-2144
    System Uptime: 0 days 0:26:08.814
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    *** 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+1d630 )
    BugCheck A0000001, {5, 0, 0, 0}
    BugCheck Info: Unknown bugcheck code (a0000001)
    Bugcheck code a0000001
    Arguments: 
    Arg1: 00000005
    Arg2: 00000000
    Arg3: 00000000
    Arg4: 00000000
    BUGCHECK_STR:  0xA0000001
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  0xA0000001_atikmdag+1d630
    BiosVersion = 1102
    BiosReleaseDate = 01/20/2014
    SystemManufacturer = System manufacturer
    SystemProductName = System Product Name
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Debug session time: Thu Jul  3 03:07:53.062 2014 (UTC + 5:30)
    Loading Dump File [C:\Users\Shyam\SysnativeBSODApps\070214-17300-01.dmp]
    Built by: 7601.18409.x86fre.win7sp1_gdr.140303-2144
    System Uptime: 0 days 1:20:17.529
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    *** 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+1d630 )
    BugCheck A0000001, {5, 0, 0, 0}
    BugCheck Info: Unknown bugcheck code (a0000001)
    Bugcheck code a0000001
    Arguments: 
    Arg1: 00000005
    Arg2: 00000000
    Arg3: 00000000
    Arg4: 00000000
    BUGCHECK_STR:  0xA0000001
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  0xA0000001_atikmdag+1d630
    BiosVersion = 1102
    BiosReleaseDate = 01/20/2014
    SystemManufacturer = System manufacturer
    SystemProductName = System Product Name
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Debug session time: Tue Jul  1 14:36:25.939 2014 (UTC + 5:30)
    Loading Dump File [C:\Users\Shyam\SysnativeBSODApps\070114-16302-01.dmp]
    Built by: 7601.18409.x86fre.win7sp1_gdr.140303-2144
    System Uptime: 0 days 1:32:08.017
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    *** 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+1d630 )
    BugCheck A0000001, {5, 0, 0, 0}
    BugCheck Info: Unknown bugcheck code (a0000001)
    Bugcheck code a0000001
    Arguments: 
    Arg1: 00000005
    Arg2: 00000000
    Arg3: 00000000
    Arg4: 00000000
    BUGCHECK_STR:  0xA0000001
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  0xA0000001_atikmdag+1d630
    BiosVersion = 1102
    BiosReleaseDate = 01/20/2014
    SystemManufacturer = System manufacturer
    SystemProductName = System Product Name
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
      My Computer


  3. Posts : 3
    windows 7
    Thread Starter
       #3

    Thank you.


    I will follow your advice and see where that gets me.
    Many thanks for taking the time to look at this.

    Paul
      My Computer


  4. Posts : 3
    windows 7
    Thread Starter
       #4

    Hello Captain Jack.

    So far so good, I have had no BSOD for a couple of days since I updated the display drivers.

    Thank you very much for your help.

    Paul
      My Computer


  5. Posts : 4,772
    Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
       #5

    mrpaulgill said:
    Hello Captain Jack.

    So far so good, I have had no BSOD for a couple of days since I updated the display drivers.

    Thank you very much for your help.

    Paul
    No problem. Glad I could help :)
      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 06:45.
Find Us