Solved Random BSOD, becoming more frequent, most common code is 0x00000024

[lemwells]

System Specs:
(Note that software has been installed from .iso files under a licensing agreement)
Windows 7 Enterprise 64 bit
Semantec Endpoint Protection (Antivirus etc)
MS Office 2007

ASUS M4A785-M motherboard
AMD Phenom X4 2.1GHz processor
PNY 3x2Gb DDR2
ASUS EN210 video card


I built this system last February. The video card was the last item installed in May, along with a KVM switch. The first BSOD was in June. The KVM switch was determined to be the cause of the BSOD's and was removed. All was relatively peaceful until near the end of October. I hadn't made any changes to the system at the time. Since then they have become more frequent, and seem to happen twice in a day on days that they occur. While looking for information on interpreting the codes, I happened upon this site. I've been putting off posting for a few weeks now, hoping to find something myself, but it's getting annoying and I've got papers to write. It's no easier when I have to open the autorecover version this often. Thanks in advance for your help, I've read through some other posts and what you're doing here is amazing. Thanks.

 

[panais]

Hi.

Remove symantec\norton from your system for testing purposes.


Download and install Microsoft Security Essentials with windows firewall enable.


Also,for easy and free system security you can read this http://www.sevenforums.com/system-s...-system-security-combination.html#post1732627

Update these old software\drivers

Afc.sys        fffff880`04c00000    fffff880`04c09000     0x00009000    0x44b48d24    12-Jul-06 7:48:20 πμ                        
PxHlpa64.sys        fffff880`010c1000    fffff880`010cc380     0x0000b380    0x45c3ac06    02-Feb-07 11:24:22 μμ                         
tifsfilt.sys        fffff880`00c5c000    fffff880`00c73000     0x00017000    0x46d56889    29-Aug-07 2:37:29 μμ                        
timntr.sys        fffff880`018da000    fffff880`0198a000     0x000b0000    0x46d568bf    29-Aug-07 2:38:23 μμ                        
tdrpman.sys        fffff880`01afa000    fffff880`01b8e000     0x00094000    0x473856e1    12-Nov-07 3:36:33 μμ                        
snapman.sys        fffff880`01b96000    fffff880`01bd1000     0x0003b000    0x47453b95    22-Nov-07 10:19:33 πμ  6:56:27 μμ                        
AsUpIO.sys        fffff880`04a2f000    fffff880`04a35000     0x00006000    0x4a515fb2  06-Jul-09

How to find and update drivers? Read HERE.


Then run http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html


Finish and post back.

 

[lemwells]

I prefer to take things in steps rather than all at once and when I got my 2nd BSOD of the day just after reading this with tifsfilt.sys in memory, I started with your list of drivers. I wasn't able to update any of them, but I was able to work around that by disabling them and simply removing unneeded software.. My original suspects were 1) a piece of hardware, or 2) some update software. Turns out there were a drive, an updater, AND a backup program wreaking havoc. I would have been chasing that forever so thanks a million. I have to wonder how you found that driver list though. Awesome work. I do have a question about the spldr.sys file though. I can't find a way to get a newer version, just the one already on my installation DVD. Any advice on that while I wait to see if we crash again in a week or two?

Here's what I've done so far.

Afc.sys 12-Jul-06 7:48:20 pµ Microsoft (CD-DVD Writer)
PxHlpa64.sys 02-Feb-07 11:24:22 µµ Microsoft (CD-DVD Writer)
Action taken: added ".old" to each filename, restarting after each change
Uninstall the non-functioning DVD drive, and restart. Driver installation failed. Ran this:
Your CD or DVD drive can't read or write media. The drive now runs and the
2 drivers listed above have not been replaced (not with the same filename at least).

tifsfilt.sys 29-Aug-07 2:37:29 µµ Acronis (Seagate Disc Wizard)
timntr.sys 29-Aug-07 2:38:23 µµ Acronis (Seagate Disc Wizard)
tdrpman.sys 12-Nov-07 3:36:33 µµ Acronis (Seagate Disc Wizard)
snapman.sys 22-Nov-07 10:19:33 pµ Acronis (Seagate Disc Wizard)
Action taken: Uninstalled Seagate Disk Wizard, added ".old" to each filename, restarting after each change

spldr.sys 11-May-09 6:56:27 µµ Microsoft (Windows Defender?)
Action taken: none

AsUpIO.sys 06-Jul-09 4:21:38 pµ ASUS Updater
Action taken: uninstalled ASUS Updater, disabled ASUS update in setup, added ".old" to the filename, restarting after the change

 

[panais]

Ignore spldr.sys is the loader for security processor,updated through windows update dont bother with it.

Do you have done these?


Remove symantec\norton from your system for testing purposes.


Download and install Microsoft Security Essentials with windows firewall enable.


RAM - Test with Memtest86+

 

[lemwells]

That's what I thought. Seems like the only version available is the same one I have so it should only need repair if it's been corrupted.

I'll run the memory test overnight tonight. I ran a memory test a couple of weeks ago though and all was good so I don't expect much different today.

I'll wait to see if it crashes again before changing security software, thank you. I really think the driver related issues will take care of it. They fit with all other indications quite well.

 

[panais]

That's what I thought. Seems like the only version available is the same one I have so it should only need repair if it's been corrupted.

You can always to "fix" the os using http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

I'll run the memory test overnight tonight. I ran a memory test a couple of weeks ago though and all was good so I don't expect much different today.

Is good idea though to check the memory because you had a memory corruption.

I'll wait to see if it crashes again before changing security software, thank you. I really think the driver related issues will take care of it. They fit with all other indications quite well.

Ok give it time few days,work\play as usual and post back with news.

 

[lemwells]

Memtest found no errors in 8 passes.

I had a full system scan scheduled to run daily and to be run within 8 hours if it could not run at 4am. Shortly after the scan started yesterday morning, the system crashed. After restart, I ran a full system scan manually which was clean. However, even after that scan was complete I noticed that it was still trying to run the scheduled scan. Obviously, there is some problem with SEP vs11 here then. MS Security Essentials was available from my employer, but I downloaded the newer version from the link you provided (thank you again). I disconnected from the network, unistalled all Semantec programs, and installed MSSE. I've used Semantec for years with no problems and no viruses so I'm a little dissappointed in this. The first scan with MSSE found nothing (quick scan). However, I then ran a full scan of my boot drive and it found 2 suspicious files which were deleted. Since the SEP full scan ran with no problems when run manually, would it be a bad idea to have both installed and simply run a manual scan now and then? On that note, is it a bad idea to have multiple softwares in the hopes that if one misses something the other will catch it?

Now I guess we wait a few more days and see if there's another blue screen. Thanks again for all of your help.

 

[panais]

Read and use this Good and Free system security combination.

With this combination you dont need anything else.

 

[lemwells]

Just got another BOSD just after updating definitions for MSSE. The system health report listed errors with Cisco Anyconnect VPN Client. I can do without the VPN temporarily, so I went ahead and uninstalled those services. I also ran the BSOD File Collection app and Perfmon report and am attaching the files here in case you'd like to see them.

 

[lemwells]

Video Card

So this was a fairly random BSOD. The only "patterns" were that I could expect it ever week or two, and when there was one in a day, there was usually another in the same day. Randoms (in my experience) are usually hardware/driver related. However, after updating all of my drivers, changing my antivirus, and testing my RAM for 16 hours to no avail, I acted on a hunch and removed my video card. That was several weeks ago. No more blue screens. Still, the new security detected things that Semantec didn't. I learned a little more, and I learned how to check for out of date drivers without just relying on Windows to take care of it. Thank you for all your help and advice.

 

[panais]

So this was a fairly random BSOD. The only "patterns" were that I could expect it ever week or two, and when there was one in a day, there was usually another in the same day. Randoms (in my experience) are usually hardware/driver related. However, after updating all of my drivers, changing my antivirus, and testing my RAM for 16 hours to no avail, I acted on a hunch and removed my video card. That was several weeks ago. No more blue screens. Still, the new security detected things that Symantec didn't. I learned a little more, and I learned how to check for out of date drivers without just relying on Windows to take care of it. Thank you for all your help and advice.

I thank you for your kind words and also for trusting my Good and Free system security combination

Also no more bsod and as you said you learn here how to update software\drivers and protect better your system.

This is an achievement!