This makes sense as either the virus scanner driver or the hard disk driver is accessing memory in such way that the other one can't write to it, as a virus scanner scans files but this one seems to do it too early. There are ony two dumps mentioning the iastor.sys driver, which is related to your hard disk. If you can get into safe mode you can try to remove the virus scanner, if not you could attempt to rename C:\Windows\System32\drivers\mfehidk.sys so that the operating system should not load it anymore. It's April 2011 and that driver dates back to July 2009, that's horribly out of date for a virus scanner. Image path: \SystemRoot\system32\drivers\mfehidk.sys If we list the module, we get: fffff880`03ab2000 fffff880`03afba00 mfehidk T (no symbols) Probably caused by : mfehidk.sys ( mfehidk 188e9 ) The driver/function that caused the problem. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) The driver that is crashing your computer multiple times is mfehidk.sys, from McAfee, your virus scanner. The best way would be to connect the hard drive to another computer. So, you can try to remotely obtain the crash dump file, it is located at one of these two paths: Not checking the crash dump is trying to fix a problem without knowing what the problem is. If you can get there, please upload the dump file so we can analyze for you which driver did this. Please read this article to troubleshoot your BSOD, try to see if Safe Mode works and check the Event Log. This is likely a malfunctioning driver activated as it occurs after login, or do you experience randomness?
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |