Started a few weeks ago and could not get to the bottom of them so I have re-installed the OS and the errors have continued.
System: Original install of Windows 7 Home Premium, full retail, X86, home build system about 2 years and just re-installed OS 10/17/11.
Have updated all drivers since re-install. Replaced display card and had been running without the sound card until today. New ethernet card.
1-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
ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.SYS file is date stamped from 2009 or 2010 (NOT 2005).
Thanks for the help ZigZag. I updated that file and I went for 7 hrs without a BSOD error! That's the longest I have gone without one. The next time I have a "Bug Check String": Memory_Management and the "Caused by Driver": ntkrnlpa.exe. So, I am back to square one again.
Thanks for your help, because it did help some!
Attached is new zip file per requesrt................
Jack
Thanks
Newest crash still points to memory issues, either RAM itself or a driver. Does it BSOD in safe mode?
These two tests will further narrow our focus but are lengthy.
These were caused by a memory exception. Please run these two tests to verify your memory and find which driver is causing the problem.
1-Memtest.
*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool
*Boot from the CD, and leave it running for at least 5 or 6 passes.
Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.
Test the sticks individually, and if you find a good one, test it in all slots.
RAM - Test with Memtest86+
2-Driver verifier
I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).
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 disk or the "Repair your computer" option at the top of the Safe Mode menu .Driver Verifier - Enable and Disable
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) 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.
Reboot the system and wait for it to crash to the Blue Screen. 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 let it run for at least 36 hours of continuous operation (an estimate on my part).
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
I'll give all of this a try. As far in SafeMode, before I re-installed this copy of the OS, it crashed. I have not tried it since re-installing, but I will.
Appreciate all of your help and I am learning more each day!!!!!!!
I tried all of these steps and it seems the more I tried, the more times the machine re-booted. Many times it wasn't even a BSOD, so I am laying the problem to hardware and the MBO in particular. The memory and cpu all worked fine in another identical machine I have.
Thanks again for all of the help and advice, I really appreciated it.
Quote