Hi,
I started having BSOD's about a week ago. They came "out of the blue" I could say. I appreciate any help I get :)
info:
-Win 7 x64 ultimate
-Retail version
-Age of the hardware and windows is about a year
-no re-installs
(Q6600@stock clocks, 4Gb ram, sapphire hd 4870)
EDIT: I ran memtest86+ 3 hours and it reported no mistakes
Multiple things wrong
1-spdt.sys from 2005 almost always causes bsod's
ASACPI.sys Sun Mar 27 22:30:36 2005
The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
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 8th 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).
2-Old drivers
How To Find Drivers:Code:ASACPI.sys fffff880`042c1000 0x00008000 3/27/2005 22:30:36 0x42476c4c fffff880`042b9000 SSPORT.sys fffff880`063b4000 0x00008000 8/11/2005 19:07:32 0x42fbda34 fffff880`063ac000 AsIO.sys fffff880`03fb6000 0x00007000 12/17/2007 05:11:49 0x47663d55 fffff880`03faf000 TFsExDisk.sys fffff880`081ad000 0x00009000 9/11/2008 02:15:03 0x48c8b767 fffff880`081a4000 cpuz132_x64.sys fffff880`04679000 0x00008000 3/26/2009 19:17:23 0x49cc0d03 fffff880`04671000 spldr.sys fffff880`015e8000 0x00008000 5/11/2009 12:56:27 0x4a0858bb fffff880`015e0000 amdxata.sys fffff880`00c35000 0x0000b000 5/19/2009 13:56:59 0x4a12f2eb fffff880`00c2a000- - The most common drivers are listed on this page: Driver Reference- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - Driver manufacturer links are on this page: Drivers and Downloads
3-An OS file blamed but not the cause. Please run a system file check
SFC /SCANNOW Command - System File Checker
If the above dont stop the BSOD's run driver verifier
Beyond that, please run Verifier with these settings:
[quote]
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
So, I'd suggest that you first backup your stuff 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).
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"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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).
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.
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.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
Using Driver Verifier to identify issues with Windows drivers for advanced usersCode:Delete these registry keys (works in XP, Vista, Win7): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
Ken J
Hi,
Thank you for your response! It helped me a lot!
I updated ASACPI.sys, SSPORT.sys and cpuz drivers.
I couldn't find AsIO.sys from my computer and I did a google search about it and it seems to be related to asus. Some say it has something to do with that old ASACPI.sys and I think after updating ASACPI.sys this AsIO.sys is now gone.
I also couldn't find TFsExDisk.sys from my computer and when googled it, i found results that indicates that it is a virus. What should i do with it? I have MSE and xonealarm free installed and I have done virus checks every week. Nothing has came up.
spldr.sys and amdxata.sys seems to windows' own files so what should I do with those?
System file check reposted some errors. I atteched the .txt file to this post. It would be nice if someone could take a look at it :) Again thank you for your help!
Quote