Microsoft-Windows-Kernel-EventTracing

wizkid · Feb 2, 2013

Hi

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.

usasma · Feb 2, 2013

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.

wizkid · Feb 10, 2013

Hi
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,

usasma · Feb 12, 2013

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: https://www.eightforums.com/bsod-cr...-pc-reboots-when-waking-sleep.html#post169956

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
http://www.carrona.org/drivers/driver.php?id=ctac32k.sys

LGPBTDD.sys Wed Jul 1 14:47:52 2009 (4A4BAF58)
Logitech GamePanel Software
http://www.carrona.org/drivers/driver.php?id=LGPBTDD.sys

LGVirHid.sys Mon Nov 23 20:36:48 2009 (4B0B38B0)
Logitech Gamepanel Virtual HID Device Driver
http://www.carrona.org/drivers/driver.php?id=LGVirHid.sys

LGBusEnum.sys Mon Nov 23 20:36:48 2009 (4B0B38B0)
Logitech Keyboard
http://www.carrona.org/drivers/driver.php?id=LGBusEnum.sys

psi_mf.sys Wed Sep 1 03:53:14 2010 (4C7E066A)
Secunia PSI (Personal Software Inspector) driver
http://www.carrona.org/drivers/driver.php?id=psi_mf.sys

SASKUTIL64.SYS Tue Jul 12 17:00:01 2011 (4E1CB5D1)
SUPERAntiSpyware
http://www.carrona.org/drivers/driver.php?id=SASKUTIL64.SYS

SASDIFSV64.SYS Thu Jul 21 19:03:00 2011 (4E28B024)
SUPERAntiSpyware
http://www.carrona.org/drivers/driver.php?id=SASDIFSV64.SYS

emupia2k.sys Mon Aug 22 01:55:54 2011 (4E51EF6A)
Creative E-mu Plug-in Architecture Driver
http://www.carrona.org/drivers/driver.php?id=emupia2k.sys

ctsfm2k.sys Mon Aug 22 01:56:00 2011 (4E51EF70)
Creative SoundFont Management Device Driver
http://www.carrona.org/drivers/driver.php?id=ctsfm2k.sys

ctoss2k.sys Mon Aug 22 01:56:11 2011 (4E51EF7B)
Creative OS Services Driver
http://www.carrona.org/drivers/driver.php?id=ctoss2k.sys

ha20x2k.sys Mon Aug 22 01:57:35 2011 (4E51EFCF)
Creative 20X HAL (WDM)
http://www.carrona.org/drivers/driver.php?id=ha20x2k.sys

ctaud2k.sys Mon Aug 22 01:58:28 2011 (4E51F004)
Creative Audio Driver (WDM)
http://www.carrona.org/drivers/driver.php?id=ctaud2k.sys

ctprxy2k.sys Mon Aug 22 01:58:30 2011 (4E51F006)
Creative Audio Driver (WDM)
http://www.carrona.org/drivers/driver.php?id=ctprxy2k.sys

CTEXFIFX.SYS Mon Aug 22 01:59:38 2011 (4E51F04A)
Creative sound card driver
http://www.carrona.org/drivers/driver.php?id=CTEXFIFX.SYS

CT20XUT.SYS Mon Aug 22 01:59:44 2011 (4E51F050)
Creative sound card driver
http://www.carrona.org/drivers/driver.php?id=CT20XUT.SYS

CTHWIUT.SYS Mon Aug 22 01:59:47 2011 (4E51F053)
Creative sound card driver
http://www.carrona.org/drivers/driver.php?id=CTHWIUT.SYS

Analysis:
The following is for informational purposes only.

Code:

[font=lucida console]**************************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: [B]9200[/B].16461.amd64fre.win8_gdr.121119-1606
System Uptime:[B]0 days 0:55:50.088[/B]
*** 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 :[B]amd_sata.sys ( amd_sata+2280 )[/B]
BugCheck [B]D1, {10010, 2, 0, fffff8800129c425}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x000000D1]DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)[/url]
Arguments: 
Arg1: 0000000000010010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800129c425, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]AV_amd_sata+2280[/B]
  BIOS Version                  F7e
  BIOS Release Date             10/28/2011
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  GA-890FXA-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

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:

[font=lucida console]**************************Fri Feb  8 16:27:29.398 2013 (UTC - 5:00)**************************
[COLOR=RED][B]ctac32k.sys                 Wed Jul  2 04:38:22 2008 (486B3E7E)[/B][/COLOR]
[COLOR=RED][B]LGPBTDD.sys                 Wed Jul  1 14:47:52 2009 (4A4BAF58)[/B][/COLOR]
[COLOR=RED][B]LGVirHid.sys                Mon Nov 23 20:36:48 2009 (4B0B38B0)[/B][/COLOR]
[COLOR=RED][B]LGBusEnum.sys               Mon Nov 23 20:36:48 2009 (4B0B38B0)[/B][/COLOR]
[COLOR=RED][B]psi_mf.sys                  Wed Sep  1 03:53:14 2010 (4C7E066A)[/B][/COLOR]
[COLOR=RED][B]SASKUTIL64.SYS              Tue Jul 12 17:00:01 2011 (4E1CB5D1)[/B][/COLOR]
[COLOR=RED][B]SASDIFSV64.SYS              Thu Jul 21 19:03:00 2011 (4E28B024)[/B][/COLOR]
[COLOR=RED][B]emupia2k.sys                Mon Aug 22 01:55:54 2011 (4E51EF6A)[/B][/COLOR]
[COLOR=RED][B]ctsfm2k.sys                 Mon Aug 22 01:56:00 2011 (4E51EF70)[/B][/COLOR]
[COLOR=RED][B]ctoss2k.sys                 Mon Aug 22 01:56:11 2011 (4E51EF7B)[/B][/COLOR]
[COLOR=RED][B]ha20x2k.sys                 Mon Aug 22 01:57:35 2011 (4E51EFCF)[/B][/COLOR]
[COLOR=RED][B]ctaud2k.sys                 Mon Aug 22 01:58:28 2011 (4E51F004)[/B][/COLOR]
[COLOR=RED][B]ctprxy2k.sys                Mon Aug 22 01:58:30 2011 (4E51F006)[/B][/COLOR]
[COLOR=RED][B]CTEXFIFX.SYS                Mon Aug 22 01:59:38 2011 (4E51F04A)[/B][/COLOR]
[COLOR=RED][B]CT20XUT.SYS                 Mon Aug 22 01:59:44 2011 (4E51F050)[/B][/COLOR]
[COLOR=RED][B]CTHWIUT.SYS                 Mon Aug 22 01:59:47 2011 (4E51F053)[/B][/COLOR]
[COLOR=RED][B]nusb3hub.sys                Mon Oct 24 20:57:37 2011 (4EA60981)[/B][/COLOR]
[COLOR=RED][B]nusb3xhc.sys                Mon Oct 24 20:57:38 2011 (4EA60982)[/B][/COLOR]
[COLOR=RED][B]AODDriver2.sys              Thu Apr  5 05:23:37 2012 (4F7D6499)[/B][/COLOR]
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)
[/font]

wizkid · Feb 12, 2013

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.

usasma · Feb 12, 2013

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!

wizkid · Feb 20, 2013

Hi

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. "

usasma · Feb 20, 2013

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.

wizkid · Feb 22, 2013

Hi
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."

usasma · Feb 23, 2013

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.

wizkid · Feb 27, 2013

Hi,

Thanks for your response,

Attached below is the latest response I have received from Creative. They state that the drivers work okay but even when I was using the latest drivers from their website these did not work correctly with Windows 8, the Creative forums are also full of complaints regarding poor drivers etc. I have therefore decided to go back to using the Realtek onboard sound chip for the time being until I find sound card that is specifically designed for Windows 8.

'Pertaining to the file date in the drivers set, it is expected that some binaries are dated as far back as 2008. The reasoning behind this is that the drivers being used were working properly.

At this time there is no technical requirement to amend these drivers, if at a later date a reason arises it would be addressed accordingly. The driver date need not be changed as well, as the date provides continuity with in the driver development process.'

usasma · Feb 27, 2013

I think that, at this point in time, the best thing to do is to do without the Creative card. Remember that the mobo is likely reaching it's End Of Life (EOL) cycle also - so investing in new equipment for this board is probably not a good idea .

wizkid · Mar 21, 2013

Hi,
Thanks for your response,

I have today updated to a newer version of Logitech drivers for the G19 keyboard, and wondered if you could please take a look the attached logs to see if any of old drivers have now been updated? Also would you be able to check the logs to see if there are still any Creative drivers left on the system?

Many thanks,

usasma · Mar 23, 2013

Sorry for the delay - work has gotten real busy, so I'm putting in extra hours.

The reports are incomplete - please let the report program run for at least 15 minutes (or until it says it's done).

I was only able to find two Creative drivers - but don't have any dates for them.

Code:

ha20x2k     Creative 20X HAL Driver    c:\windows\system32\drivers\ha20x2k.sys     Kernel Driver    No    Manual    Stopped    OK    Normal    No    No

Code:

mbwrp64     1.0.0.200    81.13 KB (83,072 bytes)    12/02/2013 13:34    Creative  Technology Ltd.    c:\windows\system32\mbwrp64.dll

wizkid · Mar 23, 2013

Hi,

Thanks for your response and no worries about the delay.

I have attached a new set of logs which said completed okay. I have now done away with the Creative Sound Card and have been trying to remove any left over traces of the drivers from the system. Please can you advise which is the best way to delete the drivers that are still showing for the sound card? Also Logitech have released a new version of Setpoint and I wondered if you would please be able to check the latest attached logs to see if any of the older Logitech drivers have now been updated?

Many thanks for your continued help.

usasma · Mar 26, 2013

There's no dates on the drivers in these reports. But the Logitech installation has .exe's and .dll's that all date from 2013 - so it's safe to presume that the drivers are the most updated available.

As for removing drivers - I don't suggest you remove anything manually unless you're still having BSOD's. If the Creative drivers show up in the BSOD analysis - then I'll make suggestions on how to remove it/them safely.

Microsoft-Windows-Kernel-EventTracing

wizkid

Guest

My Computer

Mr. Cranky Pants

My Computer

wizkid

Guest

My Computer

Mr. Cranky Pants

My Computer

wizkid

Guest

My Computer

Mr. Cranky Pants

My Computer

wizkid

Guest

My Computer

Mr. Cranky Pants

My Computer

wizkid

Guest

My Computer

Mr. Cranky Pants

My Computer

wizkid

Guest

My Computer

Mr. Cranky Pants

My Computer

wizkid

Guest

My Computer

Mr. Cranky Pants

My Computer

wizkid

Guest

My Computer

Mr. Cranky Pants

My Computer