Windows 10 BSOD with driver Famv4.sys
Hi,
Issues with BSOD and reboot on a Dell laptop running Windows. 10. When booted in Windows, I get a BSOD kmode exception not handled. I have booted into safe mode and have followed instruction on how to troubleshoot this error. I have turned off FAST BOOT from within Safe mode, I have run Malwarebytes on the system and did an online scan from Trendmicro to check for both of these, but the problem still persists. I am under the suspicion it is malware of virus only because when it boots, I continuously get an uninstall of the program Touchpad Options. Although it always reaches 100% of deletion, it still does this each time I power up. Suspecting a driver problem, I also did a BIOS update on the PC the one and only time it booted to Windows. That did not clear anything.
I cannot seem to do driver updates from Safe mode via Dell connect software.
Not sure where to go from here.
Dell E5430 8gb ram. Windows 10 patched.
Issues with BSOD and reboot on a Dell laptop running Windows. 10. When booted in Windows, I get a BSOD kmode exception not handled. I have booted into safe mode and have followed instruction on how to troubleshoot this error. I have turned off FAST BOOT from within Safe mode, I have run Malwarebytes on the system and did an online scan from Trendmicro to check for both of these, but the problem still persists. I am under the suspicion it is malware of virus only because when it boots, I continuously get an uninstall of the program Touchpad Options. Although it always reaches 100% of deletion, it still does this each time I power up. Suspecting a driver problem, I also did a BIOS update on the PC the one and only time it booted to Windows. That did not clear anything.
I cannot seem to do driver updates from Safe mode via Dell connect software.
Not sure where to go from here.
Dell E5430 8gb ram. Windows 10 patched.
Famv4.sys is typically related to backup software. Are you using a backup application in the OSD process? Also, make sure you are using the latest driver pack for the system: http://en.community.dell.c
Please post the .dmp file from Windows\minidump .
ASKER
Thanks for your comment. I booted the system into Safe mode and uploaded the most recent BSOD crash from the minidump location on the disk. Analysis is pretty intense. Under primary analysis, it shows Code_corrution in SVChost.exe. It also shows x64_memory_corruption_larg
I can post the pages here for you too look at, but... is this stating I have a bad memory stick? It is not very clear!
I can post the pages here for you too look at, but... is this stating I have a bad memory stick? It is not very clear!
Please post the .dmp file.
It can be a RAM corruption and might need to replace.
It can be a RAM corruption and might need to replace.
ASKER
Here is the mini dump file
051817-40218-01.dmp
051817-40218-01.dmp
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
FAMv4.sys is the cause of Problem, search it on your system, find associated software and try to update it.
let us know the result for further assistant.
let us know the result for further assistant.
ASKER
So, I ran MEMTEST 86 (it is still running) and no errors
** Pass Complete, no errors, Pres Esc to exit **
Not sure what is happening. I uploaded the most current file from the minidump. Perhaps it was wrong??
Thoughts?
** Pass Complete, no errors, Pres Esc to exit **
Not sure what is happening. I uploaded the most current file from the minidump. Perhaps it was wrong??
Thoughts?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The info I found suggests that Famv4.sys is a driver used by File Access Manager developed by VisionWorks Solutions:
http://www.solvusoft.com/en/files/bsod-blue-screen-error/sys/windows/visionworks-solutions-inc/file-access-manager/famv4-sys/
https://technet.microsoft.com/en-us/library/dd789637(v=exchg.80).aspx
Can you see if you have this program installed? The technet article above details how to disable File Access Manager in the registry.
http://www.solvusoft.com/en/files/bsod-blue-screen-error/sys/windows/visionworks-solutions-inc/file-access-manager/famv4-sys/
https://technet.microsoft.com/en-us/library/dd789637(v=exchg.80).aspx
Can you see if you have this program installed? The technet article above details how to disable File Access Manager in the registry.
did you install or connect any hardware lately ?
try removing it and test again
if this does not work -try a system restore to a date it worked - if you cna boot to safe mode
try removing it and test again
if this does not work -try a system restore to a date it worked - if you cna boot to safe mode
ASKER
HI,
Sorry to answer late. I did a search on the web for FAMv4 and yes, saw the article on where it is from and what is it doing. I have NOT added any new hardware or software to the system. The ONLY thing I can find is a Windows update (Critical) done a few days before the crash started. I looked for the "offending" software in my list but did not see anything installed with that name either. This is what led me to believe that the issues were that the file itself was corrupted.
That being said... I have removed the HD and done a full scan with Malwarebytes and am currently doing a scan with Avast. Malwarebytes detected NO anomalies. Avast is still running on the HD. I have also looked at the startup to see IF i can stop the process from starting when windows boots, but again, I cannot locate the local program at all or the driver!! (This is totally weird) Also, a scan of the disk on the laptop does not find the file either. (it may be hidden)
thanks for being patient with me. Some of these processes (including the boot of the hardware) take quite a long time to process. I may have to do an inplace upgrade of the O/S to fix the issue as suggested above, but was hoping not to.
Sorry to answer late. I did a search on the web for FAMv4 and yes, saw the article on where it is from and what is it doing. I have NOT added any new hardware or software to the system. The ONLY thing I can find is a Windows update (Critical) done a few days before the crash started. I looked for the "offending" software in my list but did not see anything installed with that name either. This is what led me to believe that the issues were that the file itself was corrupted.
That being said... I have removed the HD and done a full scan with Malwarebytes and am currently doing a scan with Avast. Malwarebytes detected NO anomalies. Avast is still running on the HD. I have also looked at the startup to see IF i can stop the process from starting when windows boots, but again, I cannot locate the local program at all or the driver!! (This is totally weird) Also, a scan of the disk on the laptop does not find the file either. (it may be hidden)
thanks for being patient with me. Some of these processes (including the boot of the hardware) take quite a long time to process. I may have to do an inplace upgrade of the O/S to fix the issue as suggested above, but was hoping not to.
can you boot into safe mode? (f8 key)
then use last known good - or do a system restore
then use last known good - or do a system restore
ASKER
Windows 10 does not allow a "safe mode boot" from an f8 key. (Windows XP) I can boot into safe mode IF i use the restore CD to boot and then get to my command prompt and type bcdedit /set {default} safeboot network. Tried a system restore but, of course, all 3 listed are invalid or corrupt. And unlike Windows XP I cannot find anything older. (Stupid Windows 10)
I have successfully booted into SAFE mode on this PC to Windows 10 and that works. Kind of a pain to do it (wish MS would bring back the safe boot option using f8.
I have successfully booted into SAFE mode on this PC to Windows 10 and that works. Kind of a pain to do it (wish MS would bring back the safe boot option using f8.
ASKER
So,
I looked at the article from Ramin and booted into safe mode. Then edited the registry to STOP the FAMv4.sys from loading. The system has booted fine, albeit with OTHER issues at this time. (Disk errors, McAfee not working, VERY SLOW BOOT etc.) the list goes on and on. Honestly, Microsoft needs to get their heads around some of this crap TBH if they expect to continue making O/S that just don't measure up to the tasks that they are meant for. I love my MACbook and would never give it up. I have had no issues with it at all from an O/S point of view.
Regardless, I will say that RAMIN gets the points on this. With huge thanks to all who contributed.
I looked at the article from Ramin and booted into safe mode. Then edited the registry to STOP the FAMv4.sys from loading. The system has booted fine, albeit with OTHER issues at this time. (Disk errors, McAfee not working, VERY SLOW BOOT etc.) the list goes on and on. Honestly, Microsoft needs to get their heads around some of this crap TBH if they expect to continue making O/S that just don't measure up to the tasks that they are meant for. I love my MACbook and would never give it up. I have had no issues with it at all from an O/S point of view.
Regardless, I will say that RAMIN gets the points on this. With huge thanks to all who contributed.
ASKER
With thanks to you both. You gave excellent insight to the issue at hand and were right there when I needed you most.
I'm glad I could help, and Thank you.
http://www.osronline.com/page.cfm?name=Analyze
It will tell you what driver or process is causing BSOD.
You can post result or dump file here