several fvevol.sys and BSOD and crashes

amitbaz

Reputable
Jul 16, 2014
52
0
4,630
Hello everyone, in the past few weeks i've had a few crashes in windows 8.1 and crashes+BSOD in windows 10. in windows 8.1 i've had this sudden black screen for a second whether i was playing a game or not, the screen went black for a second and then got back to normal. in windows 10, which is my current os, i'm having in addition to this crashes, a BSOD at least once a day regardless if i was playing a game or just doing a regular stuff on my pc. All of them are labeld with the string "THREAD STUCK IN DEVICE DRIVER" while some of them caused by fvevol.sys and the others by dxgkrnl.sys.
Another thing, and this is a weird one, is that despite the fact i set the os to power off the screen after 10 minutes, the screen stayes turn on forever, evethough i don't touch my pc in any way.

So, what i did for now is to take out my gpu and put it in my brother's pc which is almost the same as mine (except his gpu,but it doesn't matter), and i ,as for the moment, work with the built-in gpu, which seems to be stable for now. Anyway, its been a few hours since i put my gpu in my brother's pc and so far so good! we played gta v and watchdogs on the highest graphic settings and everything is just fine.

My thought is that the gpu is fine, and since the problems happend before and after i updated the driver, i don't think its the problem either. My fears is that it is something related to my PSU, so i'm asking you, if there is any thing that you suggest me to do or check before i send the pc to a lab (cause i really, really don't want to do that, obviously)

my pc specs are:

intel i5-4590 3.3 Ghz
GIGABYTE H87-HD3 motherboard
SAPPHIRE r9-280x vapor-x 3gb ddr5 oc edition
16gb ram 1600 Mhz
1tb HDD WESTERN DIGITAL
RAIDER 650W psu
windows 10 X64 home edition

thanks for the patient and please help me as far as you can :)
 
fvevol.sys is for BitLocker Driver Encryption Driver. kind of depends on the exact bugcheck code and parameters to determine the most likely cause.

you might put your memory dump file on a server and post a link. Often a person can tell what is most likely wrong by looking at the memory dump in the windows debugger.

 

amitbaz

Reputable
Jul 16, 2014
52
0
4,630


how can i get the memory dump file?
 

amitbaz

Reputable
Jul 16, 2014
52
0
4,630


Here is the BDOS info:
https://www.dropbox.com/sh/pulpxjzcycapmgn/AABiRvRleuj9VmhHBrFMISIHa?dl=0


Here is the latest dump files:
https://www.dropbox.com/s/lrxs22ebjsutjt8/Minidump.rar?dl=0]https://www.dropbox.com/s/lrxs22ebjsutjt8/Minidump.rar?dl=0[/url]
 
all memory dumps looked the same, the stack for the ati driver was messed up.
I would, boot into BIOS, reset it to defaults, boot into windows safe mode, remove the video drivers and install an updated version.

I would also go to :http://www.gigabyte.com/products/product-page.aspx?pid=4516#bios
and grab the bios update. Then go here: http://www.gigabyte.com/products/product-page.aspx?pid=4516#dl
and grab all of the windows 10 updates.
including the current Intel Management Engine Interface driver update.
(your version was old)
reboot and see if you can still get a bugcheck.
(you might have to remove the ati driver in safe mode to get your current system to boot)

----------
most current bugcheck was caused because something corrupted the stack that was being used by the graphics adapter driver. It can be bugs in the graphics driver or what ever driver was next to it in memory. (you cannot tell with a minidump)
you have to change the memory dump type to a kernel memory dump and run cmd.exe as an admin, then run
verifier.exe /standard /all
and reboot. this will force windows to check drivers to make sure they don't write outside their memory areas. if it finds a error it will call a bugcheck at the time of the corruption and name the driver in the memory.dmp file

will look at the other memory dumps to see if I see something more useful.



your only old driver on your system was:
Intel Management Engine Interface driver
\SystemRoot\system32\DRIVERS\TeeDriverx64.sys Tue Jul 02 11:38:08 2013

C:\Windows\SysWOW64\drivers\HWiNFO64A.SYS Sun Nov 23 08:24:07 2014

looks like you have a slight CPU overclock.

machine info:
BIOS Version F8
BIOS Release Date 05/02/2014
Manufacturer Gigabyte Technology Co., Ltd.
Product Name H87-HD3

Processor Version Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz
Processor Voltage 8bh - 1.1V
External Clock 100MHz
Max Speed 7000MHz
Current Speed 3500MHz