i keep getting bsod'd i had a whole thing about it wrote up and then got it again before posting, it was fine with i built the comeputer but after i was forced to reinstall windows it started to happen alot, all dskchk and sfc scans came out fine, this is my last hope.
The first dumps shows a problem with amdkmpfd.sys.
Driver Description: AMD PCI Root Bus Lower FilterCode:ffffbf0a`6ea7d348 fffff801`64f6c70dUnable to load image \SystemRoot\System32\drivers\amdkmpfd.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for amdkmpfd.sys *** ERROR: Module load completed but symbols could not be loaded for amdkmpfd.sys amdkmpfd+0xc70d
Driver Update Site: http://support.amd.com/us/gpudownload/Pages/index.aspx
See if you can find an updated driver for your Radeon RX 580 Series
The latest dump shows a problem with eamonm.sys.
Driver Description: ESET Amon driverCode:ffff9182`c3efb0b0 fffff800`252a9a00Unable to load image \SystemRoot\system32\DRIVERS\eamonm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for eamonm.sys *** ERROR: Module load completed but symbols could not be loaded for eamonm.sys eamonm+0xa9a00
Driver Update Site: Support: http://kb.eset.com/
Downloads: http://www.eset.com/int/download/home/
Uninstall Eset and use Windows Defender for now, see if that makes a difference.
i have the latest AMD driver, 18.9.2 i believe. and ive uninstalled eset but i've had this issue before having eset. my computer is more stable atm so i should explain. i updated bios while having boot drive bitlocked, during the next boot i was confronted with needing the 'recovery key' and not the password i set for the drive. i thought i had my recovery key stored on a usb but it belonged to another drive so i just reinstalled windows over it. thing is dskchk and sfc /scannow comes back fine.
i've got the latest radeon driver installed, this issue has been going on with many drivers. 18.9.2 is what i have, also Eset is now uninstalled but ive had this issue pre ESet also.
In your first post you said you were forced to reinstall windows and then the problems started. What forced you to reinstall windows?
I had a bitlock encrypted boot drive and with out thinking updated my bios, bitlocker desider it wanted my recovery key and not the password I set for it at that point, I could have swore I saved the recovery key to a usb which I confidently plugged in to my computer and tried the only key I had on it and it failed, so I reinstalled the same windows image I used the first time but now thinking about it I didn’t delete the old boot drive back to unallocated nor did I click format I just allowed it to install. Would this cause such and issue? I’m prepared to fully wipe the drive if needed
I don't see why that would cause a problem like this but I don't think you can rule it out. SInce you are willing, I think the best bet is to do a Clean Install, deleting all partitions and installing to a raw, unallocated drive, letting the Windows 10 installer partition the drive as it needs.
Once the install is done, do several Windows Updates untill you get to 17134.330 (winver). Then restore your data and start setting up programs and such.
Reinstalled completely set it up exactly as I had it before the crash including software also, I’ve removed an ssd that shown as having “95% health” down graded my bios to what was originally on it, clocked my ram down to ddr4 standard. So far so good but I’ll have to give it more than a few hours will report back
Quote