Windows 8 and 8.1 Forums


  1. #21

    Posts : 148
    Windows 8.1 Pro


    Thanks for your response,

    Apart from the eror regarding the memory card reader, are the logs showing everything else as okay?

    Thanks for your help.

      My System SpecsSystem Spec

  2. #22

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

    We don't know for sure that it's the incompatibility of the Media Card Reader that's causing the errors - or if it's causing your problems. I'd suggest disconnecting the Media Card Reader from the motherboard and see if that stops your problems.
      My System SpecsSystem Spec

  3. #23

    Posts : 148
    Windows 8.1 Pro

    Thanks for your response,

    I experienced a BSOD the other day whilst using the PC. U have attached the logs along with a dump file and would be grateful if you could please take a look and advise was the likely cause was of the BSOD?

    Many thanks,
    Last edited by wizkid; 16 Feb 2013 at 12:15.
      My System SpecsSystem Spec

  4. #24

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

    The uploaded reports aren't complete. Please rerun the collection tool and let it run for 15 minutes (or until the tool itself tells you that it's complete.

    Your BIOS dates from 2011. Please check at the manufacturer's website to see if there are any BIOS updates available for your system. Also check the readme file to see if they apply to the problems that you are having. Please be advised that flashing the BIOS is a very unforgiving process - and one mistake can physically damage your motherboard.

    We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:
    There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

    Here's some suggestions:
    - Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
    - Update the motherboard controllers drivers to the latest available version from the controller manufacturer (NOT the mobo manufacturer unless you can't find any on the controller manufacturer's website)
    - Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
    - Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
    - Update chipset and storage controller drivers to the latest available from the manufacturer of the device (not the manufacturer of the motherboard). Be sure to update ALL controllers on the motherboard!
    ....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.
    - Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
    It's my opinion that SSD's aren't reliable enough (with current hardware) to be used on a system that needs to work reliably. Until I see reliability I will not recommend, nor will I use, SSD's for critical applications.
    06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum
    29 May 2012 - The frequency of BSOD's with SSD's seems to have been decreasing over the last several months. It may be approaching time to re-evaluate my stand on their suitability for use in production systems.
    10 Nov 2012 - I'm seeing an upswing in SSD errors - but most appear due to older storage controller drivers. I strongly suggest NOT using storage controller drivers that don't date from 2012 (if none are available, don't connect an SSD to that controller)
    05 Jan 2013 - very interesting post about difficulties with the Marvell controllers even when not connected to the SSD drives:
    This device is disabled. Was it deliberately disabled? If so, why?
    AMD High Definition Audio Device HDAUDIO\FUNC_01&VEN_1002&DEV_AA01&SUBSYS_00AA0100&REV_1002\5&2384851E&0&0001 This device is disabled.
    Please enable it and update it. Feel free to disable it again if that's how you want it.

    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 Win7 systems.
    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

    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.

    Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

    ctac32k.sys Wed Jul 2 04:38:22 2008 (486B3E7E)
    Creative Audio Driver

    LGPBTDD.sys Wed Jul 1 14:47:52 2009 (4A4BAF58)
    Logitech GamePanel Software

    LGVirHid.sys Mon Nov 23 20:36:48 2009 (4B0B38B0)
    Logitech Gamepanel Virtual HID Device Driver

    LGBusEnum.sys Mon Nov 23 20:36:48 2009 (4B0B38B0)
    Logitech Keyboard

    psi_mf.sys Wed Sep 1 03:53:14 2010 (4C7E066A)
    Secunia PSI (Personal Software Inspector) driver

    SASKUTIL64.SYS Tue Jul 12 17:00:01 2011 (4E1CB5D1)

    SASDIFSV64.SYS Thu Jul 21 19:03:00 2011 (4E28B024)

    emupia2k.sys Mon Aug 22 01:55:54 2011 (4E51EF6A)
    Creative E-mu Plug-in Architecture Driver

    ctsfm2k.sys Mon Aug 22 01:56:00 2011 (4E51EF70)
    Creative SoundFont Management Device Driver

    ctoss2k.sys Mon Aug 22 01:56:11 2011 (4E51EF7B)
    Creative OS Services Driver

    ha20x2k.sys Mon Aug 22 01:57:35 2011 (4E51EFCF)
    Creative 20X HAL (WDM)

    ctaud2k.sys Mon Aug 22 01:58:28 2011 (4E51F004)
    Creative Audio Driver (WDM)

    ctprxy2k.sys Mon Aug 22 01:58:30 2011 (4E51F006)
    Creative Audio Driver (WDM)

    CTEXFIFX.SYS Mon Aug 22 01:59:38 2011 (4E51F04A)
    Creative sound card driver

    CT20XUT.SYS Mon Aug 22 01:59:44 2011 (4E51F050)
    Creative sound card driver

    CTHWIUT.SYS Mon Aug 22 01:59:47 2011 (4E51F053)
    Creative sound card driver

    The following is for informational purposes only.
    **************************Fri Feb  8 16:27:29.398 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\020813-8174-01.dmp]
    Windows 8 Kernel Version 9200 MP (6 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:0 days 0:55:50.088
    *** WARNING: Unable to verify timestamp for amd_sata.sys
    *** ERROR: Module load completed but symbols could not be loaded for amd_sata.sys
    Probably caused by :amd_sata.sys ( amd_sata+2280 )
    BugCheck D1, {10010, 2, 0, fffff8800129c425}
    Arg1: 0000000000010010, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff8800129c425, address which referenced memory
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: AV_amd_sata+2280
      BIOS Version                  F7e
      BIOS Release Date             10/28/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  GA-890FXA-UD5
    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.
    **************************Fri Feb  8 16:27:29.398 2013 (UTC - 5:00)**************************
    ctac32k.sys                 Wed Jul  2 04:38:22 2008 (486B3E7E)
    LGPBTDD.sys                 Wed Jul  1 14:47:52 2009 (4A4BAF58)
    LGVirHid.sys                Mon Nov 23 20:36:48 2009 (4B0B38B0)
    LGBusEnum.sys               Mon Nov 23 20:36:48 2009 (4B0B38B0)
    psi_mf.sys                  Wed Sep  1 03:53:14 2010 (4C7E066A)
    SASKUTIL64.SYS              Tue Jul 12 17:00:01 2011 (4E1CB5D1)
    SASDIFSV64.SYS              Thu Jul 21 19:03:00 2011 (4E28B024)
    emupia2k.sys                Mon Aug 22 01:55:54 2011 (4E51EF6A)
    ctsfm2k.sys                 Mon Aug 22 01:56:00 2011 (4E51EF70)
    ctoss2k.sys                 Mon Aug 22 01:56:11 2011 (4E51EF7B)
    ha20x2k.sys                 Mon Aug 22 01:57:35 2011 (4E51EFCF)
    ctaud2k.sys                 Mon Aug 22 01:58:28 2011 (4E51F004)
    ctprxy2k.sys                Mon Aug 22 01:58:30 2011 (4E51F006)
    CTEXFIFX.SYS                Mon Aug 22 01:59:38 2011 (4E51F04A)
    CT20XUT.SYS                 Mon Aug 22 01:59:44 2011 (4E51F050)
    CTHWIUT.SYS                 Mon Aug 22 01:59:47 2011 (4E51F053)
    nusb3hub.sys                Mon Oct 24 20:57:37 2011 (4EA60981)
    nusb3xhc.sys                Mon Oct 24 20:57:38 2011 (4EA60982)
    AODDriver2.sys              Thu Apr  5 05:23:37 2012 (4F7D6499)
    usbfilter.sys               Tue Aug 28 21:27:12 2012 (503D6FF0)
    amd_sata.sys                Mon Sep 17 04:40:39 2012 (5056E207)
    amd_xata.sys                Mon Sep 17 04:40:43 2012 (5056E20B)
    Rt630x64.sys                Thu Oct 25 05:14:58 2012 (50890312)
    kerneld.x64                 Sun Oct 28 07:04:11 2012 (508D112B)
    SCDEmu.SYS                  Sun Dec  9 03:46:41 2012 (50C44FF1)
    atikmpag.sys                Wed Dec 19 14:32:55 2012 (50D21667)
    atikmdag.sys                Wed Dec 19 15:38:55 2012 (50D225DF)
    EpfwLWF.sys                 Fri Dec 21 07:00:01 2012 (50D44F41)
    epfwwfp.sys                 Fri Dec 21 07:00:03 2012 (50D44F43)
    epfw.sys                    Fri Dec 21 07:00:05 2012 (50D44F45)
    eamonm.sys                  Fri Dec 21 07:02:24 2012 (50D44FD0)
    ehdrv.sys                   Fri Dec 21 07:03:30 2012 (50D45012)
      My System SpecsSystem Spec

  5. #25

    Posts : 148
    Windows 8.1 Pro

    Hi there,

    Thanks for your response,

    Please see attached a new set of logs which informed that it completed okay.

    Regarding the out of date drivers I have raised this with Creative as I am concerned that their latest driver listed for Windows 8 on their website that they uploaded on the 28th Jan 2013 still dates back until 2011.

    I will also bring to the attention of Logitech's Tech support team the out of date drivers to see if they have any later drivers available.

    The motherboard BIOS is the latest available for my board, I have contacted Gigabyte on several occasions regarding this and they have said that they have no plans to produce any later BIOS than f7e as the board is now EOL, before I contacted Gigabyte about this the board was using F6 bios which dated back to late 2010 so f7e is a slight improvement over the f6 bios.

    I have removed Superanti spyware and will use the online tools listed in your links instead to check for any malware threats etc.
    Last edited by wizkid; 16 Feb 2013 at 12:17.
      My System SpecsSystem Spec

  6. #26

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

    I'm late for work right now, but the upload doesn't contain the systeminfo.txt report - I haven't had time to run the report collection app recently, so I don't know if it's the report or not. But, all that's needed from that report (at this point) is to see if you have ALL available Windows Updates.

    I have to wonder if your Creative Sound Card is truly compatible with Win8. This isn't the first issue that I've seen with their outdated drivers.

    Also, if the mobo is EOL, and they are not issuing any further BIOS updates, then it's likely that they won't support the use of Win8 with it either.

    Logitech drivers don't seem to cause as many problems as other drivers when they're outdated - and you can always use their devices with the standard, built-in Windows drivers.

    I'd suggest at least a new mobo and sound card at this point. I hope that you can get the system to be stable until you're able to upgrade.

    Good luck!
      My System SpecsSystem Spec

  7. #27

    Posts : 148
    Windows 8.1 Pro


    Just to update you regarding the drivers for the sound Card. Below is the response I've received from Creative regarding the driver dates:

    " I received a request to address your concerns about X-Fi X-Treme Gamer sound card driver. : SBXF_PCDRV_L11_2_18_0015A.exe
    That was posted Jan 25, 2013 , You concern has to do with the driver dates. Please note that the driver date and the release date are not the same. Also this is a universal driver not just a Windows 8 driver. This driver actually applies to XP 32/64, VISTA 32/64, Win 7, and Win 8 32/64 bit OS's due to this there are some common files that will work with all these systems. We provide a common driver pool as opposed to separate packages as this allows for a smaller download. "
      My System SpecsSystem Spec

  8. #28

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

    First, while we're presuming that this is most likely a Creative driver problem - it's also possible that it might not be (for example, the BIOS is older and could be causing problems). So we must consider all things before condemning a certain product. That being said, here's my thoughts on the possibilities of it being the Creative drivers:

    Yes, they can release a 2008 driver in a package that is dated from 2013.
    But Windows 7 SP1 came out in 2009 and changed things in how the OS operates
    And Windows 8 came out in late 2012 and changed things in how the OS operates

    There are standards for driver writing that Microsoft asks developers to follow.
    The more successful developers tend to follow these standards
    As such their drivers usually seem to be more compatible than others.

    So my question (rhetorical) is - did Creative successfully anticipate the changes in Win7 SP1 and Win8 when they wrote this driver back in 2008? And, have they thoroughly tested this particular scenario?

    With BSOD issues, there generally isn't a huge sample population to deal with. Millions may install their software and we may only see a couple of BSOD's.
    For example - the ASACPI.sys driver for Asus mobo's that dates from 2005 is a known cause of BSOD's. BUT, I have that driver on my system (and have had it through Win7, Win7 SP1, and the different Win8 iterations) without any problems.
    My point here is that this is a relatively uncommon situation when looking at all the Creative installations in the world - so they may not even realize that there is a problem.

    If all of this is true, then you're left with testing to verify if it is the Creative drivers or not. To do this you'll have to remove the Creative device and the software/drivers that go with it. Then you'll either have to use a non-Creative device, or go without sound while testing. If it is found to be a problem with the Creative drivers then you'll have the satisfaction of being able to send an "I told you so" email to Creative - but be aware that it costs them money to have a developer rewrite the drivers, and it may not be worth it for them to do this for just a few cases.
      My System SpecsSystem Spec

  9. #29

    Posts : 148
    Windows 8.1 Pro

    Thanks for your response I agree I'll need to look into further to see if the Creative card is the issue here. In the meantime however, I've just received this response from Logitch regarding the g19 drivers for Windows 8.

    "Latest version of the software was released on December 12 2012. Indeed it contains some components dating back to 2009, but that is because they are still fully functional.
    As the core components of the Windows are based on earlier version it's not necessary to re-invent the wheel for every single part of the software to ensure compatibility.

    We always keep developing our software and update as needed, but exact changes and release dates are not known to us. This software is fully suitable for Windows 8."
      My System SpecsSystem Spec

  10. #30

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

    Basically the same reason that Creative gave. The key thing here is that they say it's compatible with Win8 (just as Creative did).

    I've seen more problems with Creative drivers than I have with Logitech drivers. But please remember that we're dealing with a very small sample of the population (those who have installed the software). While the primary suspicion (IME) lays with Creative, it's also possible that it could also be a problem with the Logitech.

    Finally, there's so few of these errors that we have to wonder if they're associated with more than one set of drivers. That's why I point to many different fixes when doing an analysis - so that you can remove all possible causes rather than just aiming at one thing. There's too many problems that exist even after we remove the one thing that we suspect - so I continue to wonder what else may be causing it.
      My System SpecsSystem Spec

Page 3 of 4 FirstFirst 1234 LastLast
Related Threads
I was recently checking the event viewer for errors and I noticed since August 16 I am having a huge pile of errors 90% coming from Kernal-EventTracing, event ID 2. I have tried troubleshooting yesterday for hours but could not find a solution. Even with a clean boot (disabling all non-Microsoft...
Hello! I'm having a problem with my Windows 8.1, witch freezes randomly, sometimes at startup itself, sometimes after 30 minutes, sometimes after waking up from hibernation. When I look in the Event Viewer, the timestamp of Error Event says always after restart (Kernel-Power ID 41 Critical) the...
Solved BSOD Windows 8.1 - Kernel (I guess). in BSOD Crashes and Debugging
Hello there, yesterday a BSOD appeared, the only thing I remember about it was 'nonpaged area'. Started BlueScreenView, it said it was caused by driver ntoskrnl.exe. The thing is I would like some wise person here help me to read the dump file and if its possible tell me what to do to fix it . My...
Windows 8.1 Kernel Security Check Failure in BSOD Crashes and Debugging
Been having this problem all of a sudden and blue screen keep happening. Thanks for you guys help first, please help me to solve this >.<
Windows 8 BSOD Kernel Security in BSOD Crashes and Debugging
New install of Windows 8 Professional on my homemade computer. Has seven on it as well, on a different HDD, but it's been having BSOD issues too. I believe they're seperate issues. I hope I got the files uploaded right. As far as i can tell, like many others, my issues reside in the Wireless...
Solved Windows 8 Kernel Power error in General Support
I installed clean Windows 8. I checked the event viewer to see if everything is OK. But it has 4 critical error and they were all Kernel Power Error. I noticed these Kernel Power Errors are caused by when I restart my PC. Example is when I installed Photoshop, I restarted and I checked the Event...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook