Problem here is definitely calling functions trying to cross over and an interrupt request can't be handled in that event. Everything I see is pointing towards the NT kernel itself as the culprit though, so not much there.
I see one big problem here, and a notorious one for BSOD's
Code:
fffff880`08df6000 fffff880`08dfe000 ASACPI ASACPI.sys Sun Mar 27 20:30:36 2005 (42476C4C)
You want versions 2009 or later for ASACPI.sys - versions earlier than this (2005) are known BSOD causes
You can choose to disable the Asus ATK0110 ACPI Utility in DeviceManager (under System Devices) with no apparent problems, or update the driver.
ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE Download is under Utilities as the ATK0110 driver
1) Download the driver and extract it to a folder.
2) Open the Device Manager.
3) Right click the device you wish to change the drivers for. You can select Properties > Driver > Driver Details to check you have the right device. In this case System Devices >> ATK0110 ACPI Utility
4) Choose Update Driver Software.
5) Select Browse My Computer For Driver Software.
6) Select "Let me pick from a list of device drivers on my computer".
7) Select "Have disk"
8) Select "Browse"
9) Navigate to the extracted folder and double click on the .inf file
10) Hit OK, then Next and the driver(s) will then begin to install.
11) After it has installed, GoTo C:\Windows\System32\Drivers. Locate the Asacpi.sys driver, right click it and check the dates under its properties. You're looking for a "Modified" date which should be at least 2009 or later.
If this issue continues afterwards, i'll get you to run Driver Verifier
Driver Verifier: Note make sure you backup your data first
If you have access to another computer you can contact us through your other working system in case any problems prevent you from getting into Windows. Make a System Restore point as well.
A startup repair disk may assist you in a system restore during boot if you can't get into Windows as well. In Windows 7 you can make a Startup Repair disk by going to Start - All Programs - Maintenance - "Create a System Repair Disc". With Windows Vista you'll have to use your installation CD/DVD or the "Repair your computer" option in the F8/Safe mode boot menu
Follow these steps:
- Go to Start and type in "verifier.exe" and press Enter
- Select "Create custom settings for code developers" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
- Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Note: If Norton Antivirus is installed, do not enable Driver Verifier's Deadlock Detection
Reboot the system and wait for it to crash to the BSOD. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then make sure to let it run for at least 48 hours.
Reboot into Windows after the crash once again and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, or by opening a command prompt and typing in: "verifier /reset" without the quotes. If for some reason you can't get into Windows after the crash and reboot, try booting up in Safe Mode, then try these options to disable Driver Verifier from there.
If you can't get into Windows because it crashes too soon, it is recommended to try it in Safe Mode or boot from Last Known Good Configuration.
If you can't get into Safe Mode, try using System Restore from your installation DVD or startup repair menu to set the system back to the previous restore point that you created.
Make sure your minidumps are enabled so Driver Verifier can output one to the location for you, and post it so I can review it.
