Windows 10: BSOD fvefol.sys
No problem, mate.
Now please Rebuild MBR on Disk 1.
See how it goes. Let us know.
thanks so much. I will try later. also it is very late for you. I will post reply after.
rebuilt the mbr with partition wizard. boot to the same bsod.
Now we have two options left. To check the disk and to perform a clean reinstall of windows.
As you can neither boot to windows nor set the storage controller mode to IDE, we cannot perform the disk check right now. So what else we can do in this stage is to go for a clean install of windows.
Windows 10 - Clean Install - Windows 10 Forums
If a clean install also does not work, we have to concentrate on the disk.
I did chkdsk several time and result is good. I am try to avoid clean install as so many important file need to be safe. sadly I don't have a backup.
chkdsk is a basic tool .... the dedicated disk check utilities does a better job.
You may not loss the files. There are several ways to revive those. You may use Windows 10 Recovery Tools - Bootable PE Rescue Disk in this purpose. Download it. Burn it in either a DVD or a USB flash disk, boot from it, browse to your computer and back up the important data externally.
Hi, i got this computer about 3~ Weeks ago, and have gotten random BSOD's after that.
System Information Bellow
Intel Core i5-6600K 3.5Ghz @ 3.5
GeForce GTX960 2gb GDDR5, Physx CUDA
1TB Harddisk 7200RPM
8Gb DDR4 2133Mhz Dual Channel, 2x4gb...
I recently upgraded to Windows 10 from 7. I did choose the non-clean install, and i wish to keep it this way. i do NOT wish to clean install, as id rather just fix the problem.
Anyways, my problem is; During the boot process, the pc...
I recently upgraded my htpc from 8.1 pro to Win 10 pro. I have had multiple BSOD since then. 4 were for store exception not handled and the last 2 were for kmode exception not handled mv91xx.sys. Please advise.
Over the past couple of days I have been having reasonably frequent BSODs. Some have not created a dump file. I cant pinpoint anything in particular but it seems to be pointing to a driver issue but never identifies the driver from what I can...