Win 8 dmps

[Wrench97]

0x116?

 

[zigzag3143]

Mostly BCC141's (video engine timeout, so yes like a 116)

You might want to update the Asacpi.sys , win 8 really doesnt like the 2005 version.

Asacpi.sys

The pre 2009 version of this driver is a known BSOD cause.

Please visit this link: Asus tek computer inc. -support- drivers and download p7p55d le

http://support.asus.com/download.aspx?slanguage=en&m=p7p55d%20le&p=1&s=32&os=29&hashedid=e7zic83pvqsr80lm"]ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE

http://www.asus.com/motherboards/intel_socket_775/p5kvm/#download ASUSTeK Computer Inc. - Motherboards- ASUS P5K-VM

 

[Wrench97]

Thanks zig, it's installed by Win 8 update is the issue.

 

[jcgriff2]

Hard to believe 2005 ATK0110 is showing up in W8 RTM build 9200 -

[COLOR="#FF0000"]ASACPI.sys[/COLOR]   Sun Mar 27 22:30:36 [COLOR="#FF0000"]2005[/COLOR] (42476C4C)

 

[usasma]

Ive got it on my Win8 64 bit RP system - and still no crashes
Had it in Win7 also - without any crashes

 

[Wrench97]

What I don't understand is why it is installing the 05 version and not the 09?
When I first installed there was not a internet connection, every driver except the ATK0110 and the linksys usb wireless adapter where installed, the ATK01010 driver did not get installed until after the internet connection and then it was Win8 that installed it.

 

[usasma]

This goes back to the Win7 days and a discussion with Stephen Rose at the MVP Summit
It also tends to illustrate that a huge problem for us isn't a big deal for the general population

**************************************************************************
Back then, we'd (jcgriff2 and I) just figured out that there was an issue with the 2005 version of ASACPI.sys in Win7 installs and were wondering where it came from. I experimented a bit at work and found that it was installed from the Microsoft Update site during the installation of the OS. I haven't experimented without using an internet connection - but seem to recall that the few times I installed without an internet connection, that the system picked it up as soon as it was connected (sorta like a mandatory download from Windows/Microsoft Update).

While researching this, I discovered that I had it on my Win7 system and I didn't have any problems with it. Further research hasn't figured out anything more specific, but we've solved quite a few BSOD issues simply by updating this driver.

IMO what we see in the BSOD community is only a small segment of the total Asus population. So although the ASACPI.sys is a huge problem to us, it seems to me that it's just not that big of a deal to the large majority of Asus owners that have this driver installed. Why does this happen to some and not to others? I've been thinking on this for years and am not any closer to a solution!

*************************************************************************
In 2009/2010 I attended a session at MVP Summit given by a team that included Stephen Rose.
In that session they discussed the role of Windows/Microsoft Update in system installations (this was actually an IT Pro session)

Since we'd been pondering the issue about ASACPI.sys - I posed the question to him - "Why does Microsoft supply an outdated driver that's known to cause BSOD's?".
The response was that Microsoft provides the space for the drivers on it's Update site - but it does not require any testing of the submissions.

I was initially appalled at this, but have thought about it a lot since and I see that this is actually the only reasonable way that Microsoft can improve the installation experience for Windows.
If it required testing (like the WHQL certification), then it would increase the cost to manufacturer's and it would delay (or even prevent) the release of updated drivers.
The OEM's do a pretty good job of fixing problems even if they don't update drivers as often as we'd like. But, because they're running a business, they only invest in updating drivers when it makes economic sense to do so.

 

[Corrine]

Going out on a limb here but I suspect that one reason for a delay in submitting the latest drivers to Microsoft for inclusion in Windows Update by vendors may be to cover timing scenarios. That is, the original driver may work OOTB but the latest driver on the vendor site fixes an issue resulting from a combination of changes in the system environment -- could be a combination of security updates, A/V engine conflicts, printers -- whatever, but something that hits a large segment of the population.

 

[satrow]

Re the Asacpi.sys, I had the 2005 version installed on my current machine (W7, specs in the dropdown), presumably via Microsoft Update as I didn't use the MB CD (old); after having 3 BSOD's in ~8 months, I noticed it and updated to the 2009 version. Some months later I decided to disable it altogether via Device Manager as a test, it no longer showed up DriverView. After some 3 months or so of it being disabled, I then re-enabled it but at no time did I see any change in performance, any increase in error messages in the logs - nothing that indicated it was needed at all.

I just wonder if the only time it's actually needed is when other ASUS 'utilities' are used?

 

[jcgriff2]

...I experimented a bit at work and found that it was installed from the Microsoft Update site during the installation of the OS. I haven't experimented without using an internet connection - but seem to recall that the few times I installed without an internet connection, that the system picked it up as soon as it was connected (sorta like a mandatory download from Windows/Microsoft Update).

That is exactly what I see in the Event Viewer logs.

From systeminfo output file -

OS Name:                   Microsoft Windows 8 Pro
OS Version:                6.2.9200 N/A Build 9200
OS Manufacturer:           Microsoft Corporation
Original Install Date:     10/21/2012, [COLOR="#FF0000"]9:34:41 AM[/COLOR]

During Windows 8 installation, WERCON reports driver for device ATK0110 missing:

Event[314]:
  Log Name: Application
  Source: [B]Windows Error Reporting[/B]
  Date: 2012-10-21T[color=blue]09:34:42[/color].000
  Description: 
Fault bucket , type 0
Event Name: PnPDriverNotFound
Response: Not available
Cab Id: 0

Problem signature:
P1: x64
P2: ACPI\VEN_[COLOR="#FF0000"]ATK[/COLOR]&DEV_[COLOR="#FF0000"]0110[/COLOR]
P3: 

Attached files:
C:\Windows\Temp\DMIA582.tmp.log.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_x64_b4b52ea32f66bc4692c77fd610d04fe4d667da57_cab_03b5a591

Analysis symbol: 
Rechecking for solution: 0
Report Id: 36672a32-1b9d-11e2-be67-e0cb4ec3b40e
Report Status: 4
Hashed bucket:

22 minutes later after connected to the Internet, ATK0110 service installed and asacpi.sys is seen in \system32 -

Event[146]:
  Log Name: System
  Source: Service Control Manager
  Date: 2012-10-21T[color=blue]09:58:01[/color][color=purple][b].513[/color][/b]
  User Name: NT AUTHORITY\SYSTEM
  Description: 
A service was installed in the system.

Service Name:  [COLOR="#FF0000"]ATK0110[/COLOR] ACPI UTILITY
Service File Name:  \SystemRoot\system32\DRIVERS\[COLOR="#FF0000"]ASACPI.sys[/COLOR]
Service Type:  kernel mode driver
Service Start Type:  demand start
Service Account:

0.250 ms later, asacpi.sys driver installation completed -

Event[144]:
  Log Name: System
  Source: Microsoft-Windows-UserPnp
  Date: 2012-10-21T[color=blue]09:58:01[/color][color=purple][b].763[/color][/b]
  Description: 
Driver Management concluded the process to install driver 
   atk2000.inf_amd64_a91abe245a6c41c8\[B]atk2000.inf[/B] for 
   Device Instance ID ACPI\[COLOR="#FF0000"]ATK0110[/COLOR]\1010110 with the following status: 0x0.