Windows 7: Regular BSOD , ntfs.sys common

Ok this is my third attempt at writing a thread about my BSODS before being rudely interrupted by said BSODS so i'll keep it short for now and exapand in between resets.

Regular BSOD, usually within one hour of reboot. No specific task causing it (anything really, browsing net, playing games, music, movies all cause it)

tried to use Seatools for the Hard drive (A-ram 64gig SSD for the operating system) but not sure if it worked on the ssd.
Extended test failed immediately, normal test seemed to never complete, aborted after 6 hours.

tried using chkdsk /r at command prompt from dvd boot up instead, both the SSD and my other drive containing games and programs showed no issues with chkdsk.

tried windows memtest for a couple of hours initially but will run it longer overnight tonite, nothing showed up there from the brief test.

I've reviewed temperatures and voltages while gaming and other tasks and dont see anything excessive or out of place there.

figured it was SSD corrupted anyway even though chkdsk showed nothing so tried a system image restore using macrium. no change to type and regularity of bsods.

Attached is the dump zip, hopefully its all there but so far 3 attempts to actually use the program linked by this forum has directly resulted in a BSOD halfway through the process.

Attachment 184534

nothing attached try this

We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

It is almost impossible to spot trends from a single DMP file so if you have m ore than one please upload them. If you only have one please wait until the computer crashes again then upload both.

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.



The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.


To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

yeah srry just took me a few mins to figure out the attachment

I will also had that I've had boot sector corrupt on the SSD previously , say about 6months after building the box, and that would have been about 12-18months ago. At that time i did a format and fresh install.

decided to run chkdsk again on the c: while out of the house.

ran chkdsk c: /r /f
it appeared to hang at about 10% and was still stuck there 6 hours later. Can't find a log for the chkdsk in the event viewer either.

any ideas what it means when chkdsk freezes?

Several Issues here.




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 before)


2-SPTD.SYS

This is another large cause used by daemon tools and alcohol120

Remove any CD visualization programs such as Daemon Tools and Alcohol 120%.
They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller when you're done:DuplexSecure - Downloads

You can use MagicDisc as an alternative.

Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview



3-Avast

Please remove and replace your Avast with Microsoft Security Essentials


http://files.avast.com/files/eng/aswclear5.exe

Microsoft Security Essentials - Free Antivirus for Windows


4-Old drivers

Code:

ASACPI.sys    3/27/2005 9:30:36 PM        fffff880`042c7000    fffff880`042cf000    0x00008000    0x42476c4c                        
RTCore64.sys    5/25/2005 1:39:12 AM        fffff880`08711000    fffff880`08717000    0x00006000    0x42941d90                        
speedfan.sys    9/24/2006 8:26:48 AM        fffff880`01693000    fffff880`0169a000    0x00007000    0x45168798                        
npusbio_x64.sys    4/11/2007 6:44:53 AM        fffff880`05e00000    fffff880`05e11000    0x00011000    0x461cca35                        
ctac32k.sys    7/2/2008 3:38:22 AM        fffff880`05e17000    fffff880`05ec5000    0x000ae000    0x486b3e7e                        
Rt64win7.sys    2/26/2009 4:04:13 AM        fffff880`10b83000    fffff880`10bb5000    0x00032000    0x49a65b0d                        
LHidFilt.Sys    6/17/2009 11:49:39 AM        fffff880`05f62000    fffff880`05f75000    0x00013000    0x4a391ea3                        
LMouFilt.Sys    6/17/2009 11:49:43 AM        fffff880`049b5000    fffff880`049c9000    0x00014000    0x4a391ea7

How To Find Drivers:

Quote:

- 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.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

ok cool.
i've removed dtools, and used the sptd uninstaller linked
i've installed the atk0110 download from asus (asacpi.sys now shows 2009 date)

on the avast one: i did find a reference to avast related bsods so did remove it about 3 days ago. I didnt use the above linked uninstaller though. I have just tried to use it but have no folder to direct it to for obvious reasons. I just hit uninstall anyway, is there anything else i should do here?

I will now go through and address that drive list u have posted.

edit: some initial q's on the drivers listed.

some of those are apps that i rarely use or can accept not using anymore, would it be better to simply uninstall them?
things such as RTcore (rivatuner and evga video card manager),and speedfan for instance.

1-good sptd ia a large source of them.

2-asacpi.sys another huge source.

3-Search for anything with AVG in it and you could try renaming anything you find with *.bak so it cant load.

4-Anything you dont use remove.

let us know how it goes.

ok still working through the drivers listed.
i;m now up to the creative drivers.
my sound card (creative x-fi xtreme gamer) had a Windows 7 update in 2010
Creative Worldwide Support
i believe this is what i currently have installed., in dxdiag i note that the drivers listed for my sound is not ctac32k.sys but is instead ctaud2k.sys. are these just overhang from previous drivers?
i thought i used driver sweeper in the past to fully remove any pre-existing drivers before installing new ones, is this advsieable still and should i go back and do this again? (if i analyze my sound drivers in driver sweeper i can see several .sys drivers other than ctaud2k.sys listed)

creative has given me no end of grief in the past

Related to ctac32k.sys Creative AC3 SW Decoder Device Driver (WDM) from Creative Technology.

If there is no "removal tool" from the mfr Driver sweeper will have to do.

ok i've just had another BSOD after completing your above list.
took approx 15mins in a game for it to occur.

critical structure corruption (109)

Attachment 184562


i really do suspect the SSD dieing.
a quick question, if this is the case, will a system image of its current state be a bad idea for the purposes of a new HDD installation, will any corrupted data be carried over if i did that?