I am not thinking about the seatools, despite of it being odd. Because, Seatools is not for the SSD, the SeaGate HDD is not any suspect (at least till now), and the suspect, the external HDD is a WD; we checked it with a different appropriate program.
It is good that you updated the SSD firmware.
And I think you should take a care to the My Passport disc. Either full format it to see if it can solve the issue; or retire it.
Let us know for any further BSOD.
I don't know if what you said solves my BSOD problem? as mentioned, even when I unplug my external WD hard drive, I still keep getting BSOD errors. That definitely proves that is not the culprit.
Running SEAgate tools for windows doesn't even get me to the part where the menu shows up. It hangs my computer just when it is about to scan for drives.
Please review my previous posts and attached documents/images for my results.
Reviewed. :)
I suggested to test the MyPassport knowing that it will not give a pass result, at least. And the end result supports that view:
Attachment 316497
You apply the SATA cables on different SATA ports on the motherboard, and try seatools for windows again?
BTW, SSDs are not subject to test with this tool.
And if you get any more BSOD after applying the latest SSD firmware, post it following the Blue Screen of Death (BSOD) Posting Instructions. Post the data in this thread, in any of your subsequent post.
Thanks. But i currently do not know how to switch SATA cables to a different SATA port. Is there any harm in doing so? Will I need to reconfigure windows or install any software? Sorry, I'm just a layman, I don't know much about tech support.
I suspected that would be the reason why seagate tools for DOS wasn't working, was because maybe it simply wasn't detecting the port that my hard drives are on.
On the other hand if the seagate tools for DOS is not for my main intel ssd drive that has windows in it, then what is the point of testing? If anything, I think the ssd drive may be the main reason bsods are occuring. I don't have windows or any important driver installed in my SATA 900 GB drive.
Power off the computer. Open the case. Open the sata cables from the motherboard. Apply those in other unused ports. No reconfiguration or no installation of software is needed.
If it could do any harm, I would never have suggested it to you.
That is why I was always reluctant to pay any attention on it. Running this test is not very required for you. Specially when the Seagate HDD is not a suspect at all.
Let us know about any further BSOD after applying the latest SSD firmware.
Thanks, I'll try opening the case and switching SATA ports. But since my intel SSD does not need to be scanned by seagate tools for DOS, can I leave at least that harddrive in the same port and only switch my 900 gb SATA drive?
Better you leave the plan to scan with seatools till any further 0xF4 BSOD appears.
You also feel that it is not very necessary for you.
alright thanks I will. But in the event I do need to scan, can I leave the intel SSD hardrive in its port as is and just change my SATA one?
I have the latest intel SSD toolbox, and its firmware that has to be the latest is what you are talking about, right? Currently it is v3.2.1, the "update" button is phased out since it is probably already at its latest.
If you scan using seatools, change the ports to get it recognised. Then test the HDD only, not the SSD.
Although I have had no BSODs since you helped me,( particularly i think updating the ssd toolbox may have something to do with it) Today i have received it again but of a different .sys problem.
This time I get a partmgr.sys , which is A filter driver that sits on top of the disk driver. All disk driver requests pass through the partition manager driver. This driver creates partition devices and notifies the volume managers of partition arrivals and removals. Exposes IOCTLs that return information about partitions to other components, and allow partition configuration.
I have attached my new sfc /scannow log and as usual it found errors it could not fix.
Also uploaded it the updated DM log
Please advise me what to do next but would it make a difference to go through and manually replacing the dll files that showed up in the log with the copy from my windows 7 installation disc or from a friend's BSOD free computer or try using sfc /scannow at BOOT UP?
Here are the links that explain this in better detail,
Extract Files from Windows 7 Installation DVD
Use the System File Checker tool to repair missing or corrupted system files
Or otherwise in a desperate attempt,
Use the SFCFix Script
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a file should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put tags around the log to break up the text.
Quote