Windows 8 and 8.1 Forums


BSOD on boot, different reason each time

  1. #1


    Posts : 5
    Windows 8.1

    BSOD on boot, different reason each time


    Hi,

    After my PC has been shutdown for a while (5 hours?), when I turn it back on again I get a BSOD.

    If it is turned off for a couple of hours then I don't, everything is fine.

    It normally boots up ok to the windows login wall paper, as soon as I click to select a user to login as it crashes.

    A reboot normally cures it and I'm and running.

    The messages I've been getting include:

    Windows 8.1 64-bit


    DRIVER_POWER_STATE_FAILURE
    PFN_LIST_CORRUPT
    Driver IRQL not less or equal

    (I've attached my SF Diagnostics Dump File)

    Thanks for any pointers.

      My System SpecsSystem Spec

  2. #2


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Hi Achy & Welcome to the forums ^_^,

    I have analyzed your dump files and below is a summary provided of the dump files just for informative purposes :-
    Code:
    **************************Fri Jul 25 02:03:46.771 2014 (UTC + 5:30)**************************
    Probably caused by : memory_corruption
     
    BugCheck 109, {a3a01f5a3fbe79dc, b3b72be0923bbc6f, fffff80345a4768c, 1}
    BugCheck Info: CRITICAL_STRUCTURE_CORRUPTION (109)
     
    BUGCHECK_STR:  0x109
     
    DEFAULT_BUCKET_ID:  CODE_CORRUPTION
     
    PROCESS_NAME:  csrss.exe
     
    FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
     
      BIOS Version                  F3
     
      BIOS Release Date             01/18/2013
     
      Manufacturer                  Gigabyte Technology Co., Ltd.
     
      Product Name                  To be filled by O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Jul 25 00:58:05.763 2014 (UTC + 5:30)**************************
    Probably caused by : memory_corruption ( nt!MiBadShareCount+4b )
     
    BugCheck 4E, {99, 1223bc, 1, a000000000025bc}
    BugCheck Info: PFN_LIST_CORRUPT (4e)
     
    BUGCHECK_STR:  0x4E_99
     
    PROCESS_NAME:  System
     
    FAILURE_BUCKET_ID:  0x4E_99_nt!MiBadShareCount
     
      BIOS Version                  F3
     
      BIOS Release Date             01/18/2013
     
      Manufacturer                  Gigabyte Technology Co., Ltd.
     
      Product Name                  To be filled by O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Jul 23 23:47:01.176 2014 (UTC + 5:30)**************************
    Probably caused by : ntkrnlmp.exe ( nt!_report_gsfailure+25 )
     
    BugCheck F7, {d68, 21769bab52e8, ffffde896454ad17, 0}
    BugCheck Info: DRIVER_OVERRAN_STACK_BUFFER (f7)
     
    BUGCHECK_STR:  0xF7
     
    DEFAULT_BUCKET_ID:  GS_FALSE_POSITIVE_MISSING_GSFRAME
     
    PROCESS_NAME:  System
     
    FAILURE_BUCKET_ID:  0xF7_MISSING_GSFRAME_nt!_report_gsfailure
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Jul 23 00:54:24.380 2014 (UTC + 5:30)**************************
    *** WARNING: Unable to verify checksum for win32k.sys
     
    Probably caused by : memory_corruption
     
    BugCheck 24, {b500190637, ffffd000281f14d8, ffffd000281f0ce0, fffff800c790bd0f}
    BugCheck Info: NTFS_FILE_SYSTEM (24)
     
    BUGCHECK_STR:  0x24
     
    DEFAULT_BUCKET_ID:  CODE_CORRUPTION
     
    PROCESS_NAME:  svchost.exe
     
    FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
     
      BIOS Version                  F3
     
      BIOS Release Date             01/18/2013
     
      Manufacturer                  Gigabyte Technology Co., Ltd.
     
      Product Name                  To be filled by O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Jul 22 01:43:58.517 2014 (UTC + 5:30)**************************
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
     
    BugCheck 109, {a3a01f5a00a8b739, 0, 0, 108}
    BugCheck Info: CRITICAL_STRUCTURE_CORRUPTION (109)
     
    BUGCHECK_STR:  0x109
     
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
     
    PROCESS_NAME:  System
     
    FAILURE_BUCKET_ID:  BAD_STACK
     
      BIOS Version                  F3
     
      BIOS Release Date             01/18/2013
     
      Manufacturer                  Gigabyte Technology Co., Ltd.
     
      Product Name                  To be filled by O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Jul 21 14:03:33.876 2014 (UTC + 5:30)**************************
    Probably caused by : memory_corruption ( nt!MiBadShareCount+4b )
     
    BugCheck 4E, {99, 35d20, 2, 40001200012ad05}
    BugCheck Info: PFN_LIST_CORRUPT (4e)
     
    BUGCHECK_STR:  0x4E_99
     
    PROCESS_NAME:  System
     
    FAILURE_BUCKET_ID:  0x4E_99_nt!MiBadShareCount
     
      BIOS Version                  F3
     
      BIOS Release Date             01/18/2013
     
      Manufacturer                  Gigabyte Technology Co., Ltd.
     
      Product Name                  To be filled by O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Jul 20 01:52:36.606 2014 (UTC + 5:30)**************************
    *** WARNING: Unable to verify timestamp for win32k.sys
     
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
     
    Probably caused by : memory_corruption
     
    BugCheck 1000007E, {ffffffffc0000005, fffff802e470bd0f, ffffd001639bb8d8, ffffd001639bb0e0}
    BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
     
    PROCESS_NAME:  System
     
    BUGCHECK_STR:  AV
     
    DEFAULT_BUCKET_ID:  CODE_CORRUPTION
     
    FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
     
      BIOS Version                  F3
     
      BIOS Release Date             01/18/2013
     
      Manufacturer                  Gigabyte Technology Co., Ltd.
     
      Product Name                  To be filled by O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Jul 19 10:42:31.871 2014 (UTC + 5:30)**************************
    Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+170 )
     
    BugCheck A, {10, 2, 1, fffff802622c6830}
    BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
     
    BUGCHECK_STR:  AV
     
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
     
    PROCESS_NAME:  svchost.exe
     
    FAILURE_BUCKET_ID:  AV_nt!MiReplenishPageSlist
     
      BIOS Version                  F3
     
      BIOS Release Date             01/18/2013
     
      Manufacturer                  Gigabyte Technology Co., Ltd.
     
      Product Name                  To be filled by O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Jul 18 17:46:06.272 2014 (UTC + 5:30)**************************
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::OKHAJAOM::`string'+b69 )
     
    BugCheck C000021A, {ffffc0009b56e560, ffffffffc0000428, 0, e6e8a10460}
    BugCheck Info: WINLOGON_FATAL_ERROR (c000021a)
     
    Arg2: ffffffffc0000428, Error Code.
     
    BUGCHECK_STR:  0xc000021a_Session_c0000428_Terminated
     
    PROCESS_NAME:  smss.exe
     
    FAILURE_BUCKET_ID:  0xc000021a_Session_c0000428_Terminated_nt!_??_::OKHAJAOM::_string_
     
      BIOS Version                  F3
     
      BIOS Release Date             01/18/2013
     
      Manufacturer                  Gigabyte Technology Co., Ltd.
     
      Product Name                  To be filled by O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Jul 18 13:53:24.897 2014 (UTC + 5:30)**************************
    Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+114a )
     
    BugCheck C2, {7, 1200, 0, ffffc000ca555f10}
    BugCheck Info: BAD_POOL_CALLER (c2)
     
    BUGCHECK_STR:  0xc2_7
     
    PROCESS_NAME:  System
     
    FAILURE_BUCKET_ID:  0xc2_7_nt!ExFreePoolWithTag
     
      BIOS Version                  F3
     
      BIOS Release Date             01/18/2013
     
      Manufacturer                  Gigabyte Technology Co., Ltd.
     
      Product Name                  To be filled by O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Jul 18 11:01:23.341 2014 (UTC + 5:30)**************************
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2f67c )
     
    BugCheck 133, {1, 1e00, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
     
    BUGCHECK_STR:  0x133
     
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
     
    PROCESS_NAME:  System
     
    FAILURE_BUCKET_ID:  0x133_ISR_nt!_??_::FNODOBFM::_string_
     
      BIOS Version                  F3
     
      BIOS Release Date             01/18/2013
     
      Manufacturer                  Gigabyte Technology Co., Ltd.
     
      Product Name                  To be filled by O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Below is a list of 3rd party drivers present on the system :-
    Code:
    **************************Fri Jul 25 02:03:46.771 2014 (UTC + 5:30)**************************
    Rt630x64.sys                Tue Jun 12 19:07:53 2012 (4FD74631)
    usbfilter.sys               Wed Aug 29 06:57:12 2012 (503D6FF0)
    AppleCharger.sys            Thu Oct 25 06:21:02 2012 (50888CF6)
    RTKVHD64.sys                Tue Oct 30 15:21:36 2012 (508FA328)
    amd_sata.sys                Fri Nov 30 14:30:42 2012 (50B875BA)
    amd_xata.sys                Fri Nov 30 14:30:46 2012 (50B875BE)
    point64.sys                 Thu Dec 12 18:46:17 2013 (52A9B721)
    NuidFltr.sys                Thu Dec 12 18:46:25 2013 (52A9B729)
    dc3d.sys                    Thu Dec 12 18:46:35 2013 (52A9B733)
    AMDACPKSL.SYS               Wed Mar 12 05:19:44 2014 (531FA118)
    AtihdWB6.sys                Wed Mar 12 05:20:02 2014 (531FA12A)
    atikmpag.sys                Fri Apr 18 06:37:07 2014 (53507ABB)
    atikmdag.sys                Fri Apr 18 07:43:16 2014 (53508A3C)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Jul 20 01:52:36.606 2014 (UTC + 5:30)**************************
    gdrv.sys                    Fri Mar 13 08:52:29 2009 (49B9D175)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Jul 19 10:42:31.871 2014 (UTC + 5:30)**************************
    Rt630x64.sys                Fri May 10 15:29:08 2013 (518CC4EC)
    dump_storahci.sys           Thu Aug 22 17:10:39 2013 (5215F8B7)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Jul 18 17:46:06.272 2014 (UTC + 5:30)**************************
    atikmdag.sys                Wed Apr 23 14:36:07 2014 (5357827F)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Jul 18 13:53:24.897 2014 (UTC + 5:30)**************************
    atikmpag.sys                Wed Apr 23 13:40:03 2014 (5357755B)
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
    http://www.carrona.org/drivers/driver.php?id=usbfilter.sys
    http://www.carrona.org/drivers/driver.php?id=AppleCharger.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=amd_sata.sys
    http://www.carrona.org/drivers/driver.php?id=amd_xata.sys
    http://www.carrona.org/drivers/driver.php?id=point64.sys
    http://www.carrona.org/drivers/driver.php?id=NuidFltr.sys
    http://www.carrona.org/drivers/driver.php?id=dc3d.sys
    http://www.carrona.org/drivers/driver.php?id=AMDACPKSL.SYS
    http://www.carrona.org/drivers/driver.php?id=AtihdWB6.sys
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
    hiber_amd_sata.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=gdrv.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
    http://www.carrona.org/drivers/driver.php?id=dump_storahci.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys

    I have highlighted a driver in RED. The driver is associated with Gigabyte Software and known to cause BSOD problems. Please remove this software.

    Furthermore, since most of the dump files indicate Memory_Corruption as the possible cause, there is a chance that the RAM module is bad. But, before we can be sure please MAKE SURE you do the below steps :-

    1. Remove the Gigabyte Software.

    2. Update your Chipset Drivers first that is the AMD SATA and AMD XATA drivers as this may be an issue caused by the Chipset drivers being outdated.

    3. Update the rest of the 3rd party highlighted drivers.

    4. Open up your PC, make sure you clean it up so that there is no dust inside it. Take out the RAM modules and plug them again after blowing in some static free air in the RAM Slots. Also, make sure there are no lose connections inside them.

    In case the problem is still there, please feel free to post back and I would be happy to help ^_^.
      My System SpecsSystem Spec

  3. #3


    Posts : 5
    Windows 8.1


    Thank you for coming back to me so quickly.

    BSOD is getting worse.. I get about 5 minutes then a crash... and it is pretty much 5 minutes to the second!
    The network drops then the screen goes black then boom.

    I removed the only Gigabyte Software installed by the gdrv.sys file is still there.

    I've updated the chipset drivers from AMD site.

    I've blown the dust out, removed ram and reseated it.

    I've attached another dump file.
      My System SpecsSystem Spec

  4. #4


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Hi Achy,

    I have analyzed your dump files and below is a summary of them (All of them blame the atikmdag.sys) :-
    Code:
    **************************Sat Jul 26 00:56:51.987 2014 (UTC + 5:30)**************************
    *** WARNING: Unable to verify timestamp for atikmdag.sys
     
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
     
    Probably caused by : atikmdag.sys ( atikmdag+c7dbb )
     
    BugCheck D5, {ffffcf805dff6fe8, 0, fffff801823a0dbb, 0}
    BugCheck Info: DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL (d5)
     
    BUGCHECK_STR:  0xD5
     
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
     
    PROCESS_NAME:  explorer.exe
     
    FAILURE_BUCKET_ID:  0xD5_VRF_atikmdag+c7dbb
     
      BIOS Version                  F3
     
      BIOS Release Date             01/18/2013
     
      Manufacturer                  Gigabyte Technology Co., Ltd.
     
      Product Name                  To be filled by O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Jul 26 00:35:31.872 2014 (UTC + 5:30)**************************
    *** WARNING: Unable to verify timestamp for atikmdag.sys
     
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
     
    Probably caused by : atikmdag.sys ( atikmdag+c7dbb )
     
    BugCheck D5, {ffffcf80b9f7afe8, 0, fffff800d1740dbb, 0}
    BugCheck Info: DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL (d5)
     
    BUGCHECK_STR:  0xD5
     
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
     
    PROCESS_NAME:  dwm.exe
     
    FAILURE_BUCKET_ID:  0xD5_VRF_atikmdag+c7dbb
     
      BIOS Version                  F3
     
      BIOS Release Date             01/18/2013
     
      Manufacturer                  Gigabyte Technology Co., Ltd.
     
      Product Name                  To be filled by O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Jul 26 00:14:32.981 2014 (UTC + 5:30)**************************
    *** WARNING: Unable to verify timestamp for atikmdag.sys
     
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
     
    Probably caused by : atikmdag.sys ( atikmdag+9d3606 )
     
    BugCheck 1000007E, {ffffffffc0000005, fffff800a5e37606, ffffd00027186188, ffffd00027185990}
    BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
     
    PROCESS_NAME:  System
     
    BUGCHECK_STR:  AV
     
    DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
     
    FAILURE_BUCKET_ID:  AV_VRF_atikmdag+9d3606
     
      BIOS Version                  F3
     
      BIOS Release Date             01/18/2013
     
      Manufacturer                  Gigabyte Technology Co., Ltd.
     
      Product Name                  To be filled by O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Jul 26 00:05:13.044 2014 (UTC + 5:30)**************************
    *** WARNING: Unable to verify timestamp for atikmdag.sys
     
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
     
    Probably caused by : atikmdag.sys ( atikmdag+9d3606 )
     
    BugCheck 1000007E, {ffffffffc0000005, fffff80151256606, ffffd00027738188, ffffd00027737990}
    BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
     
    PROCESS_NAME:  System
     
    BUGCHECK_STR:  AV
     
    DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
     
    FAILURE_BUCKET_ID:  AV_VRF_atikmdag+9d3606
     
      BIOS Version                  F3
     
      BIOS Release Date             01/18/2013
     
      Manufacturer                  Gigabyte Technology Co., Ltd.
     
      Product Name                  To be filled by O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Jul 25 23:55:53.323 2014 (UTC + 5:30)**************************
    *** WARNING: Unable to verify timestamp for atikmdag.sys
     
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
     
    Probably caused by : atikmdag.sys ( atikmdag+9d3606 )
     
    BugCheck 1000007E, {ffffffffc0000005, fffff801d801e606, ffffd00023ae6188, ffffd00023ae5990}
    BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
     
    PROCESS_NAME:  System
     
    BUGCHECK_STR:  AV
     
    DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
     
    FAILURE_BUCKET_ID:  AV_VRF_atikmdag+9d3606
     
      BIOS Version                  F3
     
      BIOS Release Date             01/18/2013
     
      Manufacturer                  Gigabyte Technology Co., Ltd.
     
      Product Name                  To be filled by O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Jul 25 23:46:34.204 2014 (UTC + 5:30)**************************
    *** WARNING: Unable to verify timestamp for atikmdag.sys
     
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
     
    Probably caused by : atikmdag.sys ( atikmdag+9d3606 )
     
    BugCheck 1000007E, {ffffffffc0000005, fffff80024e9a606, ffffd00024bb0188, ffffd00024baf990}
    BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
     
    PROCESS_NAME:  System
     
    BUGCHECK_STR:  AV
     
    DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
     
    FAILURE_BUCKET_ID:  AV_VRF_atikmdag+9d3606
     
      BIOS Version                  F3
     
      BIOS Release Date             01/18/2013
     
      Manufacturer                  Gigabyte Technology Co., Ltd.
     
      Product Name                  To be filled by O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Jul 25 23:37:13.438 2014 (UTC + 5:30)**************************
    *** WARNING: Unable to verify timestamp for atikmdag.sys
     
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
     
    Probably caused by : atikmdag.sys ( atikmdag+9d3606 )
     
    BugCheck 1000007E, {ffffffffc0000005, fffff801ea6d1606, ffffd00026d77188, ffffd00026d76990}
    BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
     
    PROCESS_NAME:  System
     
    BUGCHECK_STR:  AV
     
    DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
     
    FAILURE_BUCKET_ID:  AV_VRF_atikmdag+9d3606
     
      BIOS Version                  F3
     
      BIOS Release Date             01/18/2013
     
      Manufacturer                  Gigabyte Technology Co., Ltd.
     
      Product Name                  To be filled by O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Jul 25 23:27:47.294 2014 (UTC + 5:30)**************************
    *** WARNING: Unable to verify timestamp for atikmdag.sys
     
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
     
    Probably caused by : atikmdag.sys ( atikmdag+9d3606 )
     
    BugCheck 1000007E, {ffffffffc0000005, fffff8000b48d606, ffffd00021cc6188, ffffd00021cc5990}
    BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
     
    PROCESS_NAME:  System
     
    BUGCHECK_STR:  AV
     
    DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
     
    FAILURE_BUCKET_ID:  AV_VRF_atikmdag+9d3606
     
      BIOS Version                  F3
     
      BIOS Release Date             01/18/2013
     
      Manufacturer                  Gigabyte Technology Co., Ltd.
     
      Product Name                  To be filled by O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Jul 25 23:18:26.637 2014 (UTC + 5:30)**************************
    *** WARNING: Unable to verify timestamp for atikmdag.sys
     
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
     
    Probably caused by : atikmdag.sys ( atikmdag+9d3606 )
     
    BugCheck 1000007E, {ffffffffc0000005, fffff800082c3606, ffffd000251a9188, ffffd000251a8990}
    BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
     
    PROCESS_NAME:  System
     
    BUGCHECK_STR:  AV
     
    DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
     
    FAILURE_BUCKET_ID:  AV_VRF_atikmdag+9d3606
     
      BIOS Version                  F3
     
      BIOS Release Date             01/18/2013
     
      Manufacturer                  Gigabyte Technology Co., Ltd.
     
      Product Name                  To be filled by O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Jul 25 23:09:06.742 2014 (UTC + 5:30)**************************
    *** WARNING: Unable to verify timestamp for atikmdag.sys
     
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
     
    Probably caused by : atikmdag.sys ( atikmdag+9d3606 )
     
    BugCheck 1000007E, {ffffffffc0000005, fffff800f63fe606, ffffd00020f82188, ffffd00020f81990}
    BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
     
    PROCESS_NAME:  System
     
    BUGCHECK_STR:  AV
     
    DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
     
    FAILURE_BUCKET_ID:  AV_VRF_atikmdag+9d3606
     
      BIOS Version                  F3
     
      BIOS Release Date             01/18/2013
     
      Manufacturer                  Gigabyte Technology Co., Ltd.
     
      Product Name                  To be filled by O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Below is a list of the 3rd party drivers found on your system :-
    Code:
    **************************Sat Jul 26 00:56:51.987 2014 (UTC + 5:30)**************************
    Rt630x64.sys                Tue Jun 12 19:07:53 2012 (4FD74631)
    usbfilter.sys               Wed Aug 29 06:57:12 2012 (503D6FF0)
    RTKVHD64.sys                Tue Oct 30 15:21:36 2012 (508FA328)
    amd_sata.sys                Fri Nov 30 14:30:42 2012 (50B875BA)
    amd_xata.sys                Fri Nov 30 14:30:46 2012 (50B875BE)
    point64.sys                 Thu Dec 12 18:46:17 2013 (52A9B721)
    NuidFltr.sys                Thu Dec 12 18:46:25 2013 (52A9B729)
    dc3d.sys                    Thu Dec 12 18:46:35 2013 (52A9B733)
    AMDACPKSL.SYS               Wed Mar 12 05:19:44 2014 (531FA118)
    AtihdWB6.sys                Wed Mar 12 05:20:02 2014 (531FA12A)
    atikmpag.sys                Fri Apr 18 06:37:07 2014 (53507ABB)
    atikmdag.sys                Fri Apr 18 07:43:16 2014 (53508A3C)
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
    http://www.carrona.org/drivers/driver.php?id=usbfilter.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=amd_sata.sys
    http://www.carrona.org/drivers/driver.php?id=amd_xata.sys
    http://www.carrona.org/drivers/driver.php?id=point64.sys
    http://www.carrona.org/drivers/driver.php?id=NuidFltr.sys
    http://www.carrona.org/drivers/driver.php?id=dc3d.sys
    http://www.carrona.org/drivers/driver.php?id=AMDACPKSL.SYS
    http://www.carrona.org/drivers/driver.php?id=AtihdWB6.sys
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys

    I see that the old chipset drivers are still present. Please update them. Now, since you have removed the Gigabyte Software, it seems the Dump files started saying that the ATI Drivers are responsible instead of the Memory Corruption.
    Please uninstall your Display Drivers using this **TOOL**. Once you have removed the drivers, see if you are still getting the BSOD's or not. Once you are sure that the problem is gone, install the Display drivers which you would have received with your Graphics Card.

    In case you still face problems, please start with the Hardware Diagnostics over here :-
    Diagnostics

    Perform the Memory Diagnostics, Prime 95 Stress Test & Furmark Video Stress Test and report back the results.
      My System SpecsSystem Spec

  5. #5


    Posts : 5
    Windows 8.1


    Hmmm.. I'm confused. I installed the latst chipset drivers (at least I think I did)

    AMD Chipset Driver (include chipset \ sata raid \ VGA driver) 12.102 327.88 MB 2013/06/05
    From the gigabyte site.....

    Since this last posting I have reinstalled windows 8 from scratch.

    All seemed stable, then I installed the RealTek LAN drivers, and then the AMD A45 FCH Chipset drivers... and during the chipset install I got a BSOD - SYSTEM_SEARCH_THREAD_NOT_HANDLED

    I recovered windows back to the restore point and it seems stable again... for at least 8 hours

    So now I'm not sure what to do... install the latest drivers for everything or leave them with Microsoft default drivers (on which it appears stable)
      My System SpecsSystem Spec

  6. #6


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Quote Originally Posted by Achy View Post
    Hmmm.. I'm confused. I installed the latst chipset drivers (at least I think I did)

    AMD Chipset Driver (include chipset \ sata raid \ VGA driver) 12.102 327.88 MB 2013/06/05
    From the gigabyte site.....

    Since this last posting I have reinstalled windows 8 from scratch.

    All seemed stable, then I installed the RealTek LAN drivers, and then the AMD A45 FCH Chipset drivers... and during the chipset install I got a BSOD - SYSTEM_SEARCH_THREAD_NOT_HANDLED

    I recovered windows back to the restore point and it seems stable again... for at least 8 hours

    So now I'm not sure what to do... install the latest drivers for everything or leave them with Microsoft default drivers (on which it appears stable)
    The dump files did not reflect that you updated the Chipset drivers (Most of them date to the year 2012). If you are running stable on Windows drivers then leave them as it is. But, please make sure that your system is stable. Sometimes, you might get a BSOD some time later which would indicate that the root problem is still there.

    Just make sure that your machine is stable and in case not, please feel free to post back ^_^.
      My System SpecsSystem Spec

  7. #7


    Posts : 5
    Windows 8.1


    Ha Ha, you were right!

    Started getting BSOD's again.

    I *think* I have updated the chipset drivers (I can't find any mention of them in the attached files).

    Can you confirm if I have updated them all now?
      My System SpecsSystem Spec

  8. #8


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Hi Achy,

    Don't worry I am still here :P
    Below has been provided an analysis of your most recent SF Diagnostic ZIP File :-
    Code:
    **************************Mon Jul 28 16:06:45.353 2014 (UTC + 5:30)**************************
    *** WARNING: Unable to verify timestamp for atikmdag.sys
     
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
     
    Probably caused by : atikmdag.sys ( atikmdag+7e4621 )
     
    BugCheck 3B, {c0000005, fffff8010a0b0621, ffffd000faf4e560, 0}
    BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
     
    BUGCHECK_STR:  0x3B
     
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
     
    PROCESS_NAME:  csrss.exe
     
    FAILURE_BUCKET_ID:  0x3B_atikmdag+7e4621
     
      BIOS Version                  F3
     
      BIOS Release Date             01/18/2013
     
      Manufacturer                  Gigabyte Technology Co., Ltd.
     
      Product Name                  To be filled by O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Jul 28 15:30:03.624 2014 (UTC + 5:30)**************************
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2f67c )
     
    BugCheck 133, {1, 1e00, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
     
    BUGCHECK_STR:  0x133
     
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
     
    PROCESS_NAME:  System
     
    FAILURE_BUCKET_ID:  0x133_ISR_nt!_??_::FNODOBFM::_string_
     
      BIOS Version                  F3
     
      BIOS Release Date             01/18/2013
     
      Manufacturer                  Gigabyte Technology Co., Ltd.
     
      Product Name                  To be filled by O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Jul 27 16:10:54.211 2014 (UTC + 5:30)**************************
    Probably caused by : memory_corruption
     
    BugCheck A, {ffffd0012ae7ea0e, f, 0, fffff80029f43d10}
    BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
     
    BUGCHECK_STR:  AV
     
    DEFAULT_BUCKET_ID:  CODE_CORRUPTION
     
    FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Jul 27 15:10:23.317 2014 (UTC + 5:30)**************************
    *** WARNING: Unable to verify timestamp for win32k.sys
     
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
     
    Probably caused by : memory_corruption
     
    BugCheck 24, {b500190637, ffffd00051608508, ffffd00051607d10, fffff80143847f53}
    BugCheck Info: NTFS_FILE_SYSTEM (24)
     
    PROCESS_NAME:  MsMpEng.exe
     
    BUGCHECK_STR:  0x24
     
    DEFAULT_BUCKET_ID:  CODE_CORRUPTION
     
    FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
     
      BIOS Version                  F3
     
      BIOS Release Date             01/18/2013
     
      Manufacturer                  Gigabyte Technology Co., Ltd.
     
      Product Name                  To be filled by O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Jul 26 13:18:38.408 2014 (UTC + 5:30)**************************
    *** WARNING: Unable to verify timestamp for atikmdag.sys
     
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
     
    Probably caused by : atikmdag.sys ( atikmdag+7e4624 )
     
    BugCheck 3B, {c0000002, fffff803af754bf4, ffffd00023dfea80, 0}
    BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
     
    BUGCHECK_STR:  0x3B
     
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
     
    PROCESS_NAME:  csrss.exe
     
    FAILURE_BUCKET_ID:  0x3B_atikmdag+7e4624
     
      BIOS Version                  F3
     
      BIOS Release Date             01/18/2013
     
      Manufacturer                  Gigabyte Technology Co., Ltd.
     
      Product Name                  To be filled by O.E.M.
     
    иииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Below is a list of 3rd party drivers which were present on your system :-
    Code:
    **************************Mon Jul 28 16:06:45.353 2014 (UTC + 5:30)**************************
    Rt630x64.sys                Tue Jun 12 19:07:53 2012 (4FD74631)
    amd_sata.sys                Fri Nov 30 14:30:42 2012 (50B875BA)
    amd_xata.sys                Fri Nov 30 14:30:46 2012 (50B875BE)
    AtihdW86.sys                Fri Feb 15 03:41:12 2013 (511D6100)
    atikmpag.sys                Fri Mar  8 07:41:09 2013 (513948BD)
    atikmdag.sys                Fri Mar  8 08:55:16 2013 (51395A1C)
    point64.sys                 Thu Dec 12 18:46:17 2013 (52A9B721)
    NuidFltr.sys                Thu Dec 12 18:46:25 2013 (52A9B729)
    dc3d.sys                    Thu Dec 12 18:46:35 2013 (52A9B733)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Jul 28 15:30:03.624 2014 (UTC + 5:30)**************************
    Rt630x64.sys                Fri May 10 15:29:08 2013 (518CC4EC)
    dump_storahci.sys           Thu Aug 22 17:10:39 2013 (5215F8B7)
    atikmpag.sys                Sat Jul  5 06:56:52 2014 (53B7545C)
    atikmdag.sys                Sat Jul  5 07:09:13 2014 (53B75741)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Jul 27 16:10:54.211 2014 (UTC + 5:30)**************************
    hiber_storport.sys          Thu Aug 22 17:10:18 2013 (5215F8A2)
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
    http://www.carrona.org/drivers/driver.php?id=amd_sata.sys
    http://www.carrona.org/drivers/driver.php?id=amd_xata.sys
    http://www.carrona.org/drivers/driver.php?id=AtihdW86.sys
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
    http://www.carrona.org/drivers/driver.php?id=point64.sys
    http://www.carrona.org/drivers/driver.php?id=NuidFltr.sys
    http://www.carrona.org/drivers/driver.php?id=dc3d.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
    http://www.carrona.org/drivers/driver.php?id=dump_storahci.sys
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
    http://www.carrona.org/drivers/driver.php?id=hiber_storport.sys

    The highlighted drivers are your old chipset drivers which are still present. Do one thing, goto the support page for your Gigabyte Motherboard and see if you are able to find any updates for them or not.

    In the newest dump files the prominent causes are the ATI Driver (atikmdag.sys) and Memory Corruption. Please follow this guide and run Memtest to ensure your memory is not at fault :-
    RAM - Test with Memtest86+ - Windows 7 Help Forums

    Let me know how it goes ^_^.
      My System SpecsSystem Spec

  9. #9


    Posts : 5
    Windows 8.1


    Hi,

    Running memtest... 3 errors so far up to pass 5.

    Does this conclusively point to ram issue then?

    I bought Kingston because I heard it was the best :-(
      My System SpecsSystem Spec

  10. #10


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Quote Originally Posted by Achy View Post
    Hi,

    Running memtest... 3 errors so far up to pass 5.

    Does this conclusively point to ram issue then?

    I bought Kingston because I heard it was the best :-(
    I would say YES to a RAM issue because there is no proper conclusion of what might be causing the issue here. Even I bought the Kingston RAM for my desktop and apparently after 2 years it died <_< . I am still waiting for free time to get it replaced. Anyways if you are having multiple RAM sticks then test each stick one by one and see if it produces an error. If you are using a single stick then buy a RAM module from some shop which accepts returns and test your system.

    Even my desktop would have varied stability with the bad RAM. When I tested it a few days ago, within 2 minutes I got 100 errors :P . So, it would be only getting worse each day in your case.

    Let me know how it goes ^_^.
      My System SpecsSystem Spec

BSOD on boot, different reason each time
Related Threads
Okay, so everytime I run Chkdsk it always finds errors on the disk. I am unsure why, but if I run chkdsk back to back, it will keep constantly find new errors every time. Also, the Chkdsk takes about 2 and a half hours to complete, and always gets stuck at 10% for most of that time. This is...
BSOD without any reason in BSOD Crashes and Debugging
Every 2-3 weeks I have BSOD always when I'm away from my PC. It never generated dump file and nothing is in the event log. Today it finally happened in front of my eyes and it says "dpc watchdog violation" and it also created dump file. In the dump file I saw only the reason as Уntoskrnl.exe...
BSOD for no apparent reason in BSOD Crashes and Debugging
Hi everyone, I have an issue with my Windows 8 PC, as it keeps crashing (Page Fault in non-paged area). Not everyday and not while doing anything special. I can play games without any issue - and then be editing a document and it shuts down. I replaced my HD for a SD back in May but since...
BSOD: different errors (no special reason) in BSOD Crashes and Debugging
Hey guys, I am experiencing many different errors these days. It happens all the time, even when not using the computer. I do have to notice that the Google Chrome browser is always running in the background. I did have a problem with DRIVER_IRQL_NOT_LESS_OR_EQUAL (which was not resolved and...
BSOD crash, unknown reason in BSOD Crashes and Debugging
I have had some trouble with BSOD's lately, but I don't know why. They have happened during different "doings" on my computer (surfing/gaming on Facebook, wathing Youtube-clips, writing in Word etc). Restarting is extremely slow too... 40164 Can anyone find out what is happening please?
Greetings all Recently my laptop started giving me the BSOD "DPC_WATCHDOG_VIOLATION", crashing / freezing the entire time and I even can't login anymore to Windows. I actually can't boot anymore at all at the moment. It's just stuck on this screen the entire time: 34642 This is the normal...
Hello all, I bought a new gaming laptop from Maingear a few months ago and since the day it arrived, it has been giving me BSOD's on almost every single cold boot, either immediately after I get to the desktop, or very shortly after the boot is complete and everything is loaded. I've read the...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook