Windows 8 and 8.1 Forums


Another Asus desktop crashing

  1. #1

    Another Asus desktop crashing


    This is new box with Win8.1 installed about a month ago & all updates to that date. Box is connected to a lan w/o web access. Had some problems from the start. Thought orig it might be sleeping WD green drives using port multiplier since was getting crashes when doing TeraCopy copies or PowerDVD viewing. Have run crystal on hdd & win (native) mem test - no probs reported.

    Then started getting occasional video driver failure/restart messages. Video driver is native Win8.1 as there is none listed for Asus FM2A85-V Pro. Using Richland A10-6800K apu. Updated sata AHCI & nic drivers a couple of days ago.

    Now crashes are happening more frequently, sometime with watchdog msg, sometimes just a straight reboot with no warning. I have seen video driver listed during watchdog "collection", but it's not consistant. Have seen other tags like IRQL_... too. Often watchdog prep-reboot screen lists no cause.

    Edit1: Should mention that I'm seeing "misplaced" video randomly on the screen during copy/video viewing. Like a partial file name or white bars. Don't remember seeing this before today. Have not been noticing problems when I working on spreadsheets - no hdd activity related?

    Edit2: Had hdmi splitter between computer & monitor (65" hdtv) which seemed to prevent resizing open windows and rearranging desktop when monitor (only) turned off; removed this & most "misplaced" video eliminated. Watched video for 90 min then watchdog kernal_security_check_error. Don't know whether to update my SF data attachment.

    Edit3: (+60 min) "misplaced" video back even without splitter, but not as much.
    Last edited by dianedebuda; 14 Oct 2014 at 19:45.

      My System SpecsSystem Spec

  2. #2


    Posts : 5,139
    Win8.1Pro - Finally!!!


    A couple of months ago I bought a laptop for my wife. When connecting it (via HDMI) to her 32" monitor it showed video artifacts.
    After much testing I found that the brand new HDMI cable was faulty.
    Do you have another monitor and a different set of cables that you can test with?

    You have 4 hard drives. What is the make/model/wattage and age of your Power Supply?

    Many, many Windows Update failures in the WER section of MSINFO32. If you continue to have problems with it, please post over in the Windows Updates & Activation - Windows 8 Forums

    I've gotta wonder if MS Office 97 is compatible w/Win8 or 8.1
    If not, please uninstall it.

    Out of 13 memory dumps there were 7 different BSOD error codes. The differing error codes are usually symptomatic of a lower level problem within the system. They are usually caused by one of these things:
    - borked (broken) hardware (several different procedures used to isolate the problem device)
    - BIOS issues (check for updates at the motherboard manufacturer's website)
    - overclocking/overheating - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
    - dirt/dust/hair/fur/crud inside the case. Blow out the case/vents with canned air (DO NOT use an air compressor or vacuum as they can cause damage to the system)
    - missing Windows Updates
    - compatibility issues (3rd party hardware/drivers), older systems, or even pirated systems
    - low-level driver problems
    - or even malware (scanned for when we ask for hardware diagnostics from Initial Hardware Diagnostics or Hardware Diagnostics ).

    You can get a head start on the hardware diagnostics if you'd like - they are located here: Hardware Diagnostics

    AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Windows systems.
    NOTE: these symptoms were from the previous release of OverDrive. The new release uses the same driver name, but is dated from 4 November 2013.
    Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program
    Then, download (but DO NOT install) a fresh copy of the ATI drivers from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD (in the upper right corner of the page)
    Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure - Sysnative Forums

    If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
    Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
    Locate the AODDriver entry, right click on it and select "Un-install". Reboot for changes to take affect.
    Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

    If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.
    Your Silicone Image storage controller drivers (SiWinAcc.sys, SiRemFil.sys, and SI3132.sys) date from 2007 and likely aren't compatible w/Win8 or 8.1
    Please update them. If unable to update them, please remove the device that they are associated with (and uninstall the software/drivers that they use).

    Please uninstall Asus PCProbe as it's driver (AsIO.sys) dates from 2010

    I wonder if there are 2 separate problems here (a video problem and a storage controller problem).


    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Tue Oct 14 13:41:31.055 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\101414-19765-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 0:15:55.759
    *** 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+bd84 )
    BugCheck 116, {ffffe0004e40d4d0, fffff801456e1d84, 0, d}
    BugCheck Info: VIDEO_TDR_FAILURE (116)
    Arguments: 
    Arg1: ffffe0004e40d4d0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff801456e1d84, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 000000000000000d, Optional internal context dependent data.
    BUGCHECK_STR:  0x116
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x116_IMAGE_atikmpag.sys
      BIOS Version                  6002
      BIOS Release Date             03/15/2013
      Manufacturer                  System manufacturer
      Product Name                  System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Oct 12 11:23:00.926 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\101214-18484-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 1:56:24.621
    Probably caused by :ntkrnlmp.exe ( nt!KiFastFailDispatch+d0 )
    BugCheck 139, {3, ffffd00164d22050, ffffd00164d21fa8, 0}
    BugCheck Info: KERNEL_SECURITY_CHECK_FAILURE (139)
    Arguments: 
    Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
    Arg2: ffffd00164d22050, Address of the trap frame for the exception that caused the bugcheck
    Arg3: ffffd00164d21fa8, Address of the exception record for the exception that caused the bugcheck
    Arg4: 0000000000000000, Reserved
    BUGCHECK_STR:  0x139
    DEFAULT_BUCKET_ID:  LIST_ENTRY_CORRUPT
    PROCESS_NAME:  audiodg.exe
    FAILURE_BUCKET_ID: 0x139_3_nt!KiFastFailDispatch
      BIOS Version                  6002
      BIOS Release Date             03/15/2013
      Manufacturer                  System manufacturer
      Product Name                  System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Oct 12 00:06:52.731 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\101114-18656-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 0:22:47.437
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1607f )
    BugCheck 1A, {41284, 20594000, 26be, fffff58010804000}
    BugCheck Info: MEMORY_MANAGEMENT (1a)
    Arguments: 
    Arg1: 0000000000041284, A PTE or the working set list is corrupt.
    Arg2: 0000000020594000
    Arg3: 00000000000026be
    Arg4: fffff58010804000
    BUGCHECK_STR:  0x1a_41284
    PROCESS_NAME:  PowerDVD.exe
    FAILURE_BUCKET_ID: 0x1a_41284_nt!_??_::FNODOBFM::_string_
      BIOS Version                  6002
      BIOS Release Date             03/15/2013
      Manufacturer                  System manufacturer
      Product Name                  System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Oct 11 23:43:21.128 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\101114-18578-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 23:35:31.831
    *** WARNING: Unable to verify timestamp for SiWinAcc.sys
    *** ERROR: Module load completed but symbols could not be loaded for SiWinAcc.sys
    Probably caused by :SiWinAcc.sys ( SiWinAcc+102e )
    BugCheck 24, {b500190637, ffffd00024f9ef78, ffffd00024f9e780, fffff8017850d866}
    BugCheck Info: NTFS_FILE_SYSTEM (24)
    Arguments: 
    Arg1: 000000b500190637
    Arg2: ffffd00024f9ef78
    Arg3: ffffd00024f9e780
    Arg4: fffff8017850d866
    PROCESS_NAME:  PowerDVD.exe
    BUGCHECK_STR:  0x24
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    FAILURE_BUCKET_ID: 0x24_SiWinAcc+102e
      BIOS Version                  6002
      BIOS Release Date             03/15/2013
      Manufacturer                  System manufacturer
      Product Name                  System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Oct 10 23:54:42.070 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\101014-16609-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 0:07:33.765
    *** WARNING: Unable to verify timestamp for SI3132.sys
    *** ERROR: Module load completed but symbols could not be loaded for SI3132.sys
    Probably caused by :SI3132.sys ( SI3132+a50a )
    BugCheck 133, {0, 501, 500, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
        component can usually be identified with a stack trace.
    Arg2: 0000000000000501, The DPC time count (in ticks).
    Arg3: 0000000000000500, The DPC time allotment (in ticks).
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_DPC_SI3132+a50a
      BIOS Version                  6002
      BIOS Release Date             03/15/2013
      Manufacturer                  System manufacturer
      Product Name                  System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Oct 10 23:46:20.829 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\101014-29125-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:2 days 16:52:34.532
    *** WARNING: Unable to verify timestamp for SI3132.sys
    *** ERROR: Module load completed but symbols could not be loaded for SI3132.sys
    Probably caused by :SI3132.sys ( SI3132+a4f9 )
    BugCheck 133, {0, 501, 500, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
        component can usually be identified with a stack trace.
    Arg2: 0000000000000501, The DPC time count (in ticks).
    Arg3: 0000000000000500, The DPC time allotment (in ticks).
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_DPC_SI3132+a4f9
      BIOS Version                  6002
      BIOS Release Date             03/15/2013
      Manufacturer                  System manufacturer
      Product Name                  System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Oct  6 17:04:00.964 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\100614-17968-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 0:19:21.658
    *** WARNING: Unable to verify timestamp for SiWinAcc.sys
    *** ERROR: Module load completed but symbols could not be loaded for SiWinAcc.sys
    Probably caused by :SiWinAcc.sys ( SiWinAcc+102e )
    BugCheck 1000007E, {ffffffffc0000005, fffff8002418e075, ffffd0017f1e5598, ffffd0017f1e4da0}
    BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    Arguments: 
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff8002418e075, The address that the exception occurred at
    Arg3: ffffd0017f1e5598, Exception Record Address
    Arg4: ffffd0017f1e4da0, Context Record Address
    PROCESS_NAME:  System
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    FAILURE_BUCKET_ID: AV_SiWinAcc+102e
      BIOS Version                  6002
      BIOS Release Date             03/15/2013
      Manufacturer                  System manufacturer
      Product Name                  System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Oct  6 16:43:50.731 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\100614-19281-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 22:15:33.425
    *** 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+112180 )
    BugCheck D1, {10, 2, 0, fffff801f89cf180}
    BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    Arguments: 
    Arg1: 0000000000000010, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff801f89cf180, address which referenced memory
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: AV_atikmdag+112180
      BIOS Version                  6002
      BIOS Release Date             03/15/2013
      Manufacturer                  System manufacturer
      Product Name                  System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Oct  5 18:20:39.756 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\100514-16703-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 18:55:03.460
    *** WARNING: Unable to verify timestamp for SI3132.sys
    *** ERROR: Module load completed but symbols could not be loaded for SI3132.sys
    Probably caused by :SI3132.sys ( SI3132+a50a )
    BugCheck 133, {0, 501, 500, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
        component can usually be identified with a stack trace.
    Arg2: 0000000000000501, The DPC time count (in ticks).
    Arg3: 0000000000000500, The DPC time allotment (in ticks).
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_DPC_SI3132+a50a
      BIOS Version                  6002
      BIOS Release Date             03/15/2013
      Manufacturer                  System manufacturer
      Product Name                  System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Oct  1 12:04:25.134 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\100114-35578-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 0:12:41.828
    *** WARNING: Unable to verify timestamp for SI3132.sys
    *** ERROR: Module load completed but symbols could not be loaded for SI3132.sys
    Probably caused by :SI3132.sys ( SI3132+a50a )
    BugCheck 133, {0, 501, 500, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
        component can usually be identified with a stack trace.
    Arg2: 0000000000000501, The DPC time count (in ticks).
    Arg3: 0000000000000500, The DPC time allotment (in ticks).
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_DPC_SI3132+a50a
      BIOS Version                  6002
      BIOS Release Date             03/15/2013
      Manufacturer                  System manufacturer
      Product Name                  System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Oct  1 11:38:58.385 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\100114-47171-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 0:06:33.079
    *** WARNING: Unable to verify timestamp for SI3132.sys
    *** ERROR: Module load completed but symbols could not be loaded for SI3132.sys
    Probably caused by :SI3132.sys ( SI3132+a50a )
    BugCheck 133, {0, 501, 500, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
        component can usually be identified with a stack trace.
    Arg2: 0000000000000501, The DPC time count (in ticks).
    Arg3: 0000000000000500, The DPC time allotment (in ticks).
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_DPC_SI3132+a50a
      BIOS Version                  6002
      BIOS Release Date             03/15/2013
      Manufacturer                  System manufacturer
      Product Name                  System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu Sep 25 17:14:53.758 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\092514-27750-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 0:12:59.450
    *** WARNING: Unable to verify timestamp for SI3132.sys
    *** ERROR: Module load completed but symbols could not be loaded for SI3132.sys
    Probably caused by :SI3132.sys ( SI3132+a50a )
    BugCheck 133, {0, 501, 500, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
        component can usually be identified with a stack trace.
    Arg2: 0000000000000501, The DPC time count (in ticks).
    Arg3: 0000000000000500, The DPC time allotment (in ticks).
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_DPC_SI3132+a50a
      BIOS Version                  6002
      BIOS Release Date             03/15/2013
      Manufacturer                  System manufacturer
      Product Name                  System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu Sep 25 17:01:01.855 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\092514-37843-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 22:22:09.549
    *** WARNING: Unable to verify timestamp for SI3132.sys
    *** ERROR: Module load completed but symbols could not be loaded for SI3132.sys
    Probably caused by :SI3132.sys ( SI3132+a50a )
    BugCheck 133, {0, 501, 500, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
        component can usually be identified with a stack trace.
    Arg2: 0000000000000501, The DPC time count (in ticks).
    Arg3: 0000000000000500, The DPC time allotment (in ticks).
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_DPC_SI3132+a50a
      BIOS Version                  6002
      BIOS Release Date             03/15/2013
      Manufacturer                  System manufacturer
      Product Name                  System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    3rd Party Drivers:
    The following is for information purposes only.
    Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
    Code:
    **************************Tue Oct 14 13:41:31.055 2014 (UTC - 4:00)**************************
    SiWinAcc.sys                Thu Jun 14 20:02:02 2007 (4671D6FA)
    SiRemFil.sys                Wed Jun 20 15:42:10 2007 (46798312)
    SI3132.sys                  Wed Oct  3 14:39:29 2007 (4703E1E1)
    AsIO.sys                    Mon Aug 23 21:53:02 2010 (4C7325FE)
    usbfilter.sys               Tue Aug 28 21:27:12 2012 (503D6FF0)
    AtihdW86.sys                Fri Jul  5 14:10:40 2013 (51D70C20)
    amd_sata.sys                Tue Jul 23 04:06:27 2013 (51EE3983)
    amd_xata.sys                Tue Jul 23 04:06:39 2013 (51EE398F)
    Rt630x64.sys                Fri Jul 26 03:01:35 2013 (51F21ECF)
    AODDriver2.sys              Wed Sep 11 23:36:40 2013 (523136C8)
    000.fcl                     Fri Oct 18 03:16:31 2013 (5260E04F)
    RTKVHD64.sys                Tue Oct 22 08:31:34 2013 (52667026)
    avgrkx64.sys                Wed Jun 18 15:03:17 2014 (53A1E275)
    avgdiska.sys                Wed Jun 18 15:03:29 2014 (53A1E281)
    avgidsha.sys                Wed Jun 18 15:03:31 2014 (53A1E283)
    atikmpag.sys                Fri Jul  4 21:26:52 2014 (53B7545C)
    atikmdag.sys                Fri Jul  4 21:39:13 2014 (53B75741)
    avgwfpa.sys                 Fri Jul 18 09:52:05 2014 (53C92685)
    avgloga.sys                 Fri Jul 18 09:53:20 2014 (53C926D0)
    avgidsdrivera.sys           Thu Jul 24 08:06:31 2014 (53D0F6C7)
    avgmfx64.sys                Wed Aug  6 15:39:48 2014 (53E28484)
    avgldx64.sys                Wed Aug 20 15:45:05 2014 (53F4FAC1)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Oct 12 00:06:52.731 2014 (UTC - 4:00)**************************
    au630x64.sys                Thu Mar 14 05:44:07 2013 (51419BE7)
    amd_sata.sys                Fri Jun 28 00:45:40 2013 (51CD14F4)
    amd_xata.sys                Fri Jun 28 00:45:43 2013 (51CD14F7)
    
    http://www.carrona.org/drivers/driver.php?id=SiWinAcc.sys
    http://www.carrona.org/drivers/driver.php?id=SiRemFil.sys
    http://www.carrona.org/drivers/driver.php?id=SI3132.sys
    http://www.carrona.org/drivers/driver.php?id=AsIO.sys
    http://www.carrona.org/drivers/driver.php?id=usbfilter.sys
    http://www.carrona.org/drivers/driver.php?id=AtihdW86.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=Rt630x64.sys
    http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
    http://www.carrona.org/drivers/driver.php?id=000.fcl
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=avgrkx64.sys
    http://www.carrona.org/drivers/driver.php?id=avgdiska.sys
    http://www.carrona.org/drivers/driver.php?id=avgidsha.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=avgwfpa.sys
    http://www.carrona.org/drivers/driver.php?id=avgloga.sys
    http://www.carrona.org/drivers/driver.php?id=avgidsdrivera.sys
    http://www.carrona.org/drivers/driver.php?id=avgmfx64.sys
    http://www.carrona.org/drivers/driver.php?id=avgldx64.sys
    http://www.carrona.org/drivers/driver.php?id=au630x64.sys
    http://www.carrona.org/drivers/driver.php?id=amd_sata.sys
    http://www.carrona.org/drivers/driver.php?id=amd_xata.sys
      My System SpecsSystem Spec

  3. #3


    So kind of you to take a look. I do appreciate it.

    Do you have another monitor and a different set of cables that you can test with
    Yes. Can do.
    Power Supply
    current: hec HP585DB 585W ATX12V- new. Used a different (size & brand) p/s a couple of weeks ago.
    You have 4 hard drives.
    # drives vary significantly. Always present: 1 ssd (2 partitions), 1 2.5 hdd, 1 3.5 hdd. # of eSata drives vary from 0 to 14.
    Many, many Windows Update failures
    Of course - box is not connected to web. Should turn off update.
    I've gotta wonder if MS Office 97 is compatible w/Windows 8 or 8.1
    Unlikely that this is problem. Used ok with Win7 64 for years. So far with Win8, never seems to have crash problems when only using Word/Excel/Access 97. Have newer versions of Office, but don't like as well plus have XL/Office 97 boxes (non-web) that xfer data. No Office 97 with Win8 would be a deal breaker of using Win 8 for me.
    Out of 13 memory dumps there were 7 different BSOD error codes.
    Good to know; kind of expected that.
    BIOS issues
    Bios 6002 2013.04.11 as purchased. There are several updates, but since Asus bios updater will not let you revert to earlier bios, would prefer to delay change unless no other reasonable option.
    overclocking/overheating
    Not overclocked. Temps seem reasonable: cpu 35 C, mb 26 C
    AMD OverDrive (AODDriver2.sys)...
    Assumed Win Update or Asus support would have had latest. Stupid me. Have to change mindset that although this box has an APU and not a separate graphics card/chip, video drivers should be treated separately, just like when I had ATI cards. Installed latest catalyst, 14.9. Will try that with existing cable/monitor today & see what happens.
    Your Silicone Image storage controller drivers (SiWinAcc.sys, SiRemFil.sys, and SI3132.sys) date from 2007 and likely aren't compatible w/Windows 8 or 8.1
    There were auto-installed by Win8, so I assume they're compatible. I have numerous Sans Digital TR4M JBOD boxes which are pretty fussy about compatible (multiport) controllers. The SI controller cards worked well with Win7 64; I've heard worrysome things about the RocketRAID (cards natively used by Sans Digital) like conflicts and limits on number of disks in use. The use of the TR4M (multiport) JBOD is a requirement for this box. If there's a better adapter(s) for 6 eSata ports to support them, I'm game.

    FWIW, nothing was connected to the SI controller cards when the last several crashes occurred. There is no driver listed by the manufacturer for Win8, so wondering if it'd be worth trying the Win7 64 driver?
    Please uninstall Asus PCProbe as it's driver (AsIO.sys) dates from 2010
    Added/ran Asus hardware diagnostic (no probs found) a couple of days ago and assume this was installed then. It's listed as Win8 compatible. Can uninstall the diagnostic.

    I wonder if there are 2 separate problems here (a video problem and a storage controller problem).
    I agree. Hopefully the new catalyst will take care of the video headache. As for the storage, that's a real problem. I need multiport support. I was using the native Win8 AHCI drivers until a couple of days ago. Installed update from Asus, but problem still exists. Looks like Asus is only suppporting hot swap & multiport on their 1 native eSata port - and that's not nearly enough for me. Know of any alternative drivers?

    Ok, so here's the plan. Will locate where (old) mini-dumps are and delete. Will try newly installed Catalyst for a couple of days. If video artifacts, change hdmi cable. If still artifacts, test on another monitor. If I get a crash, will use autoruns to disable AODDriver2.sys. Try again. If crash, uninstall Asus Hardware Diagnostic. Try again. If crash, remove Silicon Image cards & disable driver with autoruns. Try Again. If crash, restore from a point a couple of weeks ago before testing new AHCI drivers, then install with new Catalyst. Cross fingers, toes, knees & elbows - and try again... Will start visit of Hardware Diagnostics.

    Thanks.
      My System SpecsSystem Spec

  4. #4


    Posts : 5,139
    Win8.1Pro - Finally!!!


    I have to wonder if the PSU is powerful enough when you connect all of those eSATA drives?

    Sorry, I forgot that you stated it wasn't connected to the web. BUT, it still needs the Windows Updates.

    Office 97 is not compatible w/Win8.1: Windows Compatibility Center: office 97
    As this is a non-negotiable item, I'd suggest reverting to Win7 or earlier.

    I've recently seen UEFI's dated in 2014 that need updates - it never hurts to update (as long as you do it properly).

    Windows doesn't always know if something is compatible. I had problems with my RocketRAID card when running the beta versions of Win8. I ripped it out and didn't have any problems afterwards (I gave the system away w/Win7 on it). The driver loads in the beginning (when booting Windows) - so it doesn't matter if you're using it or not, it's still loaded into memory (there's less chance of it malfunctioning - but it's not a zero chance).

    The rest of your plan sounds fine to me - good luck!
    One other thing tho' - the system seems to work fine w/Win7, so why not just downgrade and see how things work?
      My System SpecsSystem Spec

  5. #5


    I have to wonder if the PSU is powerful enough when you connect all of those eSATA drives?
    They're all externally powered.
    Sorry, I forgot that you stated it wasn't connected to the web. BUT, it still needs the Windows Updates.
    These days, not being connected to web is abnormal. The work on this box is pretty much repetitive, so it's pretty much "get it stable" & then "if it ain't broke, don't fix it". Have other boxes for web work.
    Office 97 is not compatible w/Windows 8.1
    According to MS, Office 97 was not compatible with Win7 either, but it works fine for what I do. So I'll wait & see.
    it never hurts to update (as long as you do it properly).
    Sorry, but I've been bit a number of times by updates, so I'm a bit more conservative = less trusting.

    As for unused drivers fouling up things, that's why I opt to disable them with autoruns - it lot easier than uninstalling.

    Found a loose hdmi connection, so that may be the cause of my spurious display problems. Sadly have already gotten a video driver failure/restart (no crash), so looks like I'll have to try disabling that AODDriver2.sys tomorrow.

    As for downgrading to Win7, it is an option I'm considering. Have tweaked Win8 to my liking now, so want to give it a good shot. Actually already have a Win7 setup with same mb but with a Trinity APU. The Win8 box has a Richland APU. Wish it didn't take so long for me to install, update & tweak per o/s. Don't do enough to justify automating the process though.
      My System SpecsSystem Spec

  6. #6


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Compatibility isn't a hard and fast thing. An incompatible program can work just fine with some systems - but then, as updates are applied, the incompatibilities may be exposed.

    In your case the system is less "dynamic" than most systems - due to the lack of internet, which leads to the lack of Windows Updates. As such it'll stay stable for longer (and is less exposed to external threats). But as the system still has some dynamic properties, things (like incompatibilities) can pop up seemingly out of the blue. This is because there are so many possible different combinations of things running that you may not experience all possibilities during the life of a system.

    IMO updates are essential. Nearly all problems that I've seen with updates are due to other updates being missing (which is also an issue with compatibility, as they won't release updates to keep it compatible). So, if an update causes problems, the first thing to look for is other missing updates.

    I suggest making a "clean" image of each system just after installing/updating/tweaking the OS.
    That way you have a stable platform to go back to - or to install on another system.

    Good luck!
      My System SpecsSystem Spec

  7. #7


    updates are essential.
    On a dynamic system, as you call it, I'd agree 100%; not so much on a closed system like this one. Problems I've had with updates are either 1) bug in the update or, more often 2) an o/s fix that exposes poor programming somewhere else. With the closed system, trick is getting it stable in the first place - my holy grail right now
    I suggest making a "clean" image of each system just after installing/updating/tweaking the OS.
    Exactly what I do.

    Still ogetting problems with file copies, so it's going to be restore back to the "initial" setup state and selectively move forward. Going to start some hardware tests. I'd used the Win mem tester, but I understand it's fallen out of favor. Like to use memtest86+, but getting confused about which version to use. I have a UEFI bios & 16 GB mem.

    Going to rebuild the Win7 box and, once it's up and running again, bite the bullet and update the bios on this sucker since it sure seems there's low level problems. Looking at the sparse Asus docs for the bios, betting this 2006 version was the first for the Richland APU...
      My System SpecsSystem Spec

  8. #8


    Posts : 5,139
    Win8.1Pro - Finally!!!


    I've used v5.01 of MemTest86+ at work without problems.
      My System SpecsSystem Spec

Another Asus desktop crashing
Related Threads
Asus Desktop Crashes Randomly in BSOD Crashes and Debugging
OK. New to the forum so thanks in advance for any help I can get. I've run sfc /scannow and collected logs as requested. Not sure what's wrong. Only solution offered by Asus support was to do a O/S reinstall. I'd like to avoid that for obvious reasons. HD integrity check is good. I have all...
INITIAL ISSUE: Could not boot Last week, I tried to dual-boot install Fedora Linux onto my Windows 8.1 PC (Asus CM1435 Desktop). I resized the Data Partition (not OS partition) by 100GB. I then restarted the PC, and Fedora seemed to work okay, however, I could not got Windows to start anymore. I...
Hello, When I try to go PC settings then PC and devices and then PC info it crashes. Please help! Here are my specs. OS:Windows 8.1 CPU: Intel Core i7-4500U 1.8GHz with Turbo Boost up to 3.0GHz GPU:Intel HD 4400 RAM/Memory: 8 GB DDR3 L Memory.
Windows 8, Asus PC, keeping crashing with BSOD in BSOD Crashes and Debugging
I have a Asus pc, that has been crashing all the time due to unknown reasons. I have experienced that as soon as it hangs due to some process that is taking some time, it usually ends with a BSOD. I can let the computer alone and when I come back it has crashed, apparently for no reason, since...
Hello! I got quite annoying problem with modern apps. Whenever i launch one, they start but when i want to do anything further im beeing kicked to desktop. App dont crash. If i hower app list from left top corner its still there, i can go to it. But trying any action again kicks me to destkop....
I had this computer for a hour when it started to crash. It has windows 8 and has been getting constant memory_management crashes whenever i try to use it and sometimes just from idling. I have tried doing a reset through the recovery options and have done a full reinstall of windows 8. I really...
Ths system crashed 4 times, during the last hour. Unclear why.. even SF is crashing while collecting windows update information. Attached info collected earlier today. Info from SF crashing: ************* Exception Text **************
Eight Forums Android App Eight Forums IOS App Follow us on Facebook