New
#1
BSOD browsing web and hard drive
Hi there,
Many thanks in advance for taking a look at my situation. I think I'm starting to circle the drain and with my limited skill set, I think it's time to call in the cavalry.
Sudden BSODs have be plaguing me the last few days. Activities during the BSODs are pretty much browsing the web and dealing with files on the hard drive. I also do some work in Photoshop, geotag photos with the Microsoft tool, and play various video files.
The PC has started to lag, with the CPU jumping to 100% when it didn't "need" to do this previously.
I followed the directions for memory dumps and page file sizes, waited for another BSOD, ran the SF diagnostic tool, and attached a zipped file here. Incidentally, I peeked in some of the text files generated by the tool and noticed that EventSys.txt shows entries like:
Event[889]:
Log Name: System
Source: Disk
Date: 2013-06-24T06:58:27.041
Event ID: 11
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: MEGATRON
Description:
The driver detected a controller error on \Device\Harddisk6\DR6.
I mention this entry because the last two BSODs happened right when I right clicked the C drive to get into properties. I don't know if this references my C drive or not as I have a separate data disk in the box as well. A previous EventSys.txt showed similar entries, only referencing the page file in the description. Unfortunately I overwrote this file when I ran the diagnostic tool a second time. Perhaps my C drive is failing? Have not scanned the disk, awaiting a recommendation.
The first batch of BSODs made reference to "sasdifsv" and "saskutil", which I found out are files from Supersecret Anti Spyware. I removed this program and now the actual screen of the BSOD references timntr.sys, a file from Acronis, which doesn't show up in Add Remove Programs, so I can't uninstall it. Also, starting to feel like the problem is hopping around, perhaps because I'm not really addressing the root cause.
Please let me know if I need to do a better job of explaining my situation or if additional info is needed. I noticed that MEMORY.DMP is not gathered up by the diagnostic tool, probably a good thing as the file is now 8 GB in size. I attached a zipped copy here in case it is helpful. WinDbg suggests a problem with timntr.sys when it looks at this dump file.
Thanks in advance for the help!
David