Hi everyone,

my computer keeps crashing at least three times a day (sometimes every half an hour). I already tried a lot such as updating drivers, updating apps, changing software, following threads and manuals in various forums. Unfortunately I am not as "computer-skilled" as I'd love to be so really need some help on this.

The system is stable for hours while operating some apps, but then randomly keeps crashing while browsing with chrome (or IE, firefox, etc.) or streaming music.

Some computer stats:

Lenovo ideapad U310
Core i3 - 1.8
4 GB RAM
Windows 8 (64-Bit)

If it's useful, i uploaded four dmp files from the minidump folder on my computer at:
http://www.filedropper.com/tinoiver-minidump

eventvwr.msc - lists a critical event related to "kernel power" and remarks that the driver \Driver\WUDFR for ROOT\LENOVOVHID\0000 wasn't found. I assume that this error is however due to the system being rebooted without being previously shut down (i.e. after the BSOD).

Sorry for bothering, but really need some help.

Thank you so much in advance!

TinoIver

To be able to troubleshoot what might be causing your system to crash, we need the dump files. In an ideal situation, more than one file would be needed to establish a pattern so if you do have more than one, please upload them.

Please refer to the link below for steps to retrieve, zip and upload them to the file sharing site like onedrive, google's "dropbox, etc.

When you are done, make the folder public and share the link here.

Blue Screen of Death Co-Authored by ZigZag3143& JMH3143
http://answers.microsoft.com/en-us/windows/wiki/windows_other-system/blue-screen-of-death-bsod/1939df35-283f-4830-a4dd-e95ee5d8669d

Never mind, i found it.

ERROR: Module load completed but symbols could not be loaded for vsdatant.sys

 vsdatant.sys : http://www.sysnative.com/drivers/driver.php?id=vsdatant.sys

Could you do a search on your system for  vsdatant.sys, and uninstall it and the program/application associated with it.

If you cannot find it, download "autoruns" and use it to locate and disable the driver, after making certain that all Microsoft entries have been hidden, to eliminate the possibility of a mistake.(instructions in the youtube video link below.)

Autoruns for Windows
v13.01

This utility, which has the most comprehensive knowledge of auto-starting locations of any startup monitor, shows you what programs are configured to run during system bootup or login, and shows you the entries in the order Windows processes them. These programs include ones in your startup folder, Run, RunOnce, and other Registry keys. You can configure Autoruns to show other locations, including Explorer shell extensions, toolbars, browser helper objects, Winlogon notifications, auto-start services, and much more. Autoruns goes way beyond the MSConfig utility bundled with Windows Me and XP.
Autoruns' Hide Signed Microsoft Entries option helps you to zoom in on third-party auto-starting images that have been added to your system and it has support for looking at the auto-starting images configured for other accounts configured on a system
https://technet.microsoft.com/en-us/sysinternals/bb963902.aspx

How to use Autoruns.
https://www.youtube.com/watch?v=HhtSDsQYi28

If the system continues to crash,

Please run driver verifier (DV) per the instructions in the link below.
Note: Make sure to read and remember the steps to reset DV in the event of a crash, and post a link to the newly generated crash dump here.

Driver Verifier-- tracking down a mis-behaving driver. Co-Authored by ZigZag3143& JMH3143
http://answers.microsoft.com/en-us/windows/wiki/windows_other-system/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983

Never mind, i found it.

ERROR: Module load completed but symbols could not be loaded for vsdatant.sys

 vsdatant.sys : http://www.sysnative.com/drivers/driver.php?id=vsdatant.sys

Could you do a search on your system for  vsdatant.sys, and uninstall it and the program/application associated with it.

If you cannot find it, download "autoruns" and use it to locate and disable the driver, after making certain that all Microsoft entries have been hidden, to eliminate the possibility of a mistake.(instructions in the youtube video link below.)

Autoruns for Windows
v13.01

This utility, which has the most comprehensive knowledge of auto-starting locations of any startup monitor, shows you what programs are configured to run during system bootup or login, and shows you the entries in the order Windows processes them. These programs include ones in your startup folder, Run, RunOnce, and other Registry keys. You can configure Autoruns to show other locations, including Explorer shell extensions, toolbars, browser helper objects, Winlogon notifications, auto-start services, and much more. Autoruns goes way beyond the MSConfig utility bundled with Windows Me and XP.
Autoruns' Hide Signed Microsoft Entries option helps you to zoom in on third-party auto-starting images that have been added to your system and it has support for looking at the auto-starting images configured for other accounts configured on a system
https://technet.microsoft.com/en-us/sysinternals/bb963902.aspx

How to use Autoruns.
https://www.youtube.com/watch?v=HhtSDsQYi28

If the system continues to crash,

Please run driver verifier (DV) per the instructions in the link below.
Note: Make sure to read and remember the steps to reset DV in the event of a crash, and post a link to the newly generated crash dump here.

Driver Verifier-- tracking down a mis-behaving driver. Co-Authored by ZigZag3143& JMH3143
http://answers.microsoft.com/en-us/windows/wiki/windows_other-system/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983

• Proposed as answer by MeipoXuMicrosoft contingent staff 50 minutes ago

Never mind, i found it.

ERROR: Module load completed but symbols could not be loaded for vsdatant.sys

 vsdatant.sys : http://www.sysnative.com/drivers/driver.php?id=vsdatant.sys

Could you do a search on your system for  vsdatant.sys, and uninstall it and the program/application associated with it.

If you cannot find it, download "autoruns" and use it to locate and disable the driver, after making certain that all Microsoft entries have been hidden, to eliminate the possibility of a mistake.(instructions in the youtube video link below.)

Autoruns for Windows
v13.01

This utility, which has the most comprehensive knowledge of auto-starting locations of any startup monitor, shows you what programs are configured to run during system bootup or login, and shows you the entries in the order Windows processes them. These programs include ones in your startup folder, Run, RunOnce, and other Registry keys. You can configure Autoruns to show other locations, including Explorer shell extensions, toolbars, browser helper objects, Winlogon notifications, auto-start services, and much more. Autoruns goes way beyond the MSConfig utility bundled with Windows Me and XP.
Autoruns' Hide Signed Microsoft Entries option helps you to zoom in on third-party auto-starting images that have been added to your system and it has support for looking at the auto-starting images configured for other accounts configured on a system
https://technet.microsoft.com/en-us/sysinternals/bb963902.aspx

How to use Autoruns.
https://www.youtube.com/watch?v=HhtSDsQYi28

If the system continues to crash,

Please run driver verifier (DV) per the instructions in the link below.
Note: Make sure to read and remember the steps to reset DV in the event of a crash, and post a link to the newly generated crash dump here.

Driver Verifier-- tracking down a mis-behaving driver. Co-Authored by ZigZag3143& JMH3143
http://answers.microsoft.com/en-us/windows/wiki/windows_other-system/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983

• Proposed as answer by MeipoXuMicrosoft contingent staff Tuesday, May 19, 2015 6:32 AM

Never mind, i found it.

ERROR: Module load completed but symbols could not be loaded for vsdatant.sys

 vsdatant.sys : http://www.sysnative.com/drivers/driver.php?id=vsdatant.sys

Could you do a search on your system for  vsdatant.sys, and uninstall it and the program/application associated with it.

If you cannot find it, download "autoruns" and use it to locate and disable the driver, after making certain that all Microsoft entries have been hidden, to eliminate the possibility of a mistake.(instructions in the youtube video link below.)

Autoruns for Windows
v13.01

This utility, which has the most comprehensive knowledge of auto-starting locations of any startup monitor, shows you what programs are configured to run during system bootup or login, and shows you the entries in the order Windows processes them. These programs include ones in your startup folder, Run, RunOnce, and other Registry keys. You can configure Autoruns to show other locations, including Explorer shell extensions, toolbars, browser helper objects, Winlogon notifications, auto-start services, and much more. Autoruns goes way beyond the MSConfig utility bundled with Windows Me and XP.
Autoruns' Hide Signed Microsoft Entries option helps you to zoom in on third-party auto-starting images that have been added to your system and it has support for looking at the auto-starting images configured for other accounts configured on a system
https://technet.microsoft.com/en-us/sysinternals/bb963902.aspx

How to use Autoruns.
https://www.youtube.com/watch?v=HhtSDsQYi28

If the system continues to crash,

Please run driver verifier (DV) per the instructions in the link below.
Note: Make sure to read and remember the steps to reset DV in the event of a crash, and post a link to the newly generated crash dump here.

Driver Verifier-- tracking down a mis-behaving driver. Co-Authored by ZigZag3143& JMH3143
http://answers.microsoft.com/en-us/windows/wiki/windows_other-system/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983

• Proposed as answer by MeipoXuMicrosoft contingent staff Tuesday, May 19, 2015 6:32 AM
• Marked as answer by Yolanda ZhuMicrosoft contingent staff, Moderator 23 hours 51 minutes ago

Never mind, i found it.

ERROR: Module load completed but symbols could not be loaded for vsdatant.sys

 vsdatant.sys : http://www.sysnative.com/drivers/driver.php?id=vsdatant.sys

Could you do a search on your system for  vsdatant.sys, and uninstall it and the program/application associated with it.

If you cannot find it, download "autoruns" and use it to locate and disable the driver, after making certain that all Microsoft entries have been hidden, to eliminate the possibility of a mistake.(instructions in the youtube video link below.)

Autoruns for Windows
v13.01

This utility, which has the most comprehensive knowledge of auto-starting locations of any startup monitor, shows you what programs are configured to run during system bootup or login, and shows you the entries in the order Windows processes them. These programs include ones in your startup folder, Run, RunOnce, and other Registry keys. You can configure Autoruns to show other locations, including Explorer shell extensions, toolbars, browser helper objects, Winlogon notifications, auto-start services, and much more. Autoruns goes way beyond the MSConfig utility bundled with Windows Me and XP.
Autoruns' Hide Signed Microsoft Entries option helps you to zoom in on third-party auto-starting images that have been added to your system and it has support for looking at the auto-starting images configured for other accounts configured on a system
https://technet.microsoft.com/en-us/sysinternals/bb963902.aspx

How to use Autoruns.
https://www.youtube.com/watch?v=HhtSDsQYi28

If the system continues to crash,

Please run driver verifier (DV) per the instructions in the link below.
Note: Make sure to read and remember the steps to reset DV in the event of a crash, and post a link to the newly generated crash dump here.

Driver Verifier-- tracking down a mis-behaving driver. Co-Authored by ZigZag3143& JMH3143
http://answers.microsoft.com/en-us/windows/wiki/windows_other-system/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983

• Proposed as answer by MeipoXuMicrosoft contingent staff Tuesday, May 19, 2015 6:32 AM
• Marked as answer by Yolanda ZhuMicrosoft contingent staff, Moderator Thursday, May 21, 2015 7:34 AM

Hi XP Rocks,

Thank you so much! Really appreciate your help. Just installed the app associated with it, it's actually the ZoneAlarm firewall. Will just use the Microsoft Firewall and see whether it keeps on crashing.

Thanks again.

Hi XP Rocks,

Thank you so much! Really appreciate your help. Just installed the app associated with it, it's actually the ZoneAlarm firewall. Will just use the Microsoft Firewall and see whether it keeps on crashing.

Thanks again.

• Proposed as answer by MeipoXuMicrosoft contingent staff 50 minutes ago

Hi XP Rocks,

Thank you so much! Really appreciate your help. Just installed the app associated with it, it's actually the ZoneAlarm firewall. Will just use the Microsoft Firewall and see whether it keeps on crashing.

Thanks again.

• Proposed as answer by MeipoXuMicrosoft contingent staff Tuesday, May 19, 2015 6:32 AM

Hi XP Rocks,

Thank you so much! Really appreciate your help. Just installed the app associated with it, it's actually the ZoneAlarm firewall. Will just use the Microsoft Firewall and see whether it keeps on crashing.

Thanks again.

• Proposed as answer by MeipoXuMicrosoft contingent staff Tuesday, May 19, 2015 6:32 AM
• Marked as answer by Yolanda ZhuMicrosoft contingent staff, Moderator 23 hours 51 minutes ago

Hi XP Rocks,

Thank you so much! Really appreciate your help. Just installed the app associated with it, it's actually the ZoneAlarm firewall. Will just use the Microsoft Firewall and see whether it keeps on crashing.

Thanks again.

• Proposed as answer by MeipoXuMicrosoft contingent staff Tuesday, May 19, 2015 6:32 AM
• Marked as answer by Yolanda ZhuMicrosoft contingent staff, Moderator Thursday, May 21, 2015 7:34 AM

You are welcome. Let us know if this helped resolve the issue.

Thanks.

Hey XP Rocks,

It works! Didn't not experience any BSOD since then. Thank you so much! It works! Never thought of the firewall for it previously never made any problems. Had those BSOD for almost 4 months now. Gosh, spent so much time trying to fix it by myself - updating, auto-start, plug-ins...

Thanks!