I've been living on the Windows 32bit RC 7100 build since mid summer with no issues. I dual booted to another hard drive (same model as 32bit OS) with Windows 7 Ultimate 64 bit. I finally got all my software installed this weekend and since yesterday it's crashed 7 times. Can someone help me decipher the minidump. I'm attaching the last one.
Thanks
Carl
Hello and welcome to SF.
The problem is this driver...again...
Uninstall any ASUS software that you have installed (AI Suite, ASUS Probe, etc.). Also, navigate to C:\Windows\System32\drivers and locate ASACPI.SYS. Rename it to ASACPI.BAK and reboot the computer, then see if BSOD's persist.Code:fffff880`04ff7000 fffff880`04fff000 ASACPI ASACPI.sys Sun Mar 27 22:30:36 2005 (42476C4C)
Thanks DT Roberts.
Since this is the same software that I've been running with in 32bit mode is just lucky I've not had problems or is this 64bit incompatibility?
I'll post with status.
30 minutes later - I looked at what I installed, both from from my notes and what was installed on each boot, both 32bit and 64bit. The ASUS CD would not install on either boot. It gave the message that the "Motherboard Support CD does not support this operating system (WNT_6.1P_64_MCE.)". The only thing I installed was on the 32bit boot and that was the ASUSUpate utility, which I downloaded from their web site. This was to update the bios.
I did not install anything on the 64 bit OS, which is where I'm having the issue. I never had an issue on the 32bit OS.
However, based on your comments I uninstalled the ASUSUpdate on the 32 bit install, AND I renamed the ASACPI.sys to ASACPI.bak on the 64bit boot per your recommendation.
If you have any other recommendations then let me know. I will monitor to see what results I have.
And thanks for you quick response.
Last edited by CarlCP; 24 Feb 2010 at 22:31.
It is interesting that you say that; it actually sheds some light on the entire problem. ASACPI.SYS can be either installed as a system driver from your chipset drivers or via Windows Update, which is where I believe it came from on the 64-bit OS. Windows Update was dealing out a faulty ASACPI.SYS, the 2005 version that you have. The fact that the 32-bit OS is fine means to me that it may just be a problem with 64-bit Windows using ASACPI.SYS, something that I've always suspected. Perhaps the download for 32-bit Windows is the correct one.
If you don't mind, on your 32-bit installation, please navigate to C:\Windows\System32\drivers and locate ASACPI.SYS. Right-click>Properties; what date does it say for Created?
I do hope that you stay BSOD-free after renaming ASACPI.SYS. Let us know how it goes.
Ahhhh. Excellant observation DT. The driver on my 32 bit OS is dated 10/18/2006 1:44:48 PM where the 64 bit version is 3/29/2005 1:30 AM. Maybe your on to something. Thumbs up to you.
And so far no BSOD. I'll post again.
Although the 2006 version is VERY outdated, I have yet to see it cause any problems; or at least nothing like the 2005 version used by 64-bit Windows.
Thanks for checking. Keep us posted.
I just wanted to post back that I have NOT had a single BSOD since renaming that ASACPI.SYS. Again Thanks very much for the help.
Thanks for the update. I'm glad I could help!
Quote