Hello everyone. Hope I'm posting this in the correct forum. Sorry for the very long post, just trying to give as much detai as possible .
I have a HP Envy Notebook J100-CTO which I bought in early 2016. This laptop has ever since been working just fine up until a year ago from which it started to show signs of slowdown. No matter how many times I've installed a new Windows, installed drivers and updates, dusted the laptop and even upgraded the RAM (from 8 to 12) it stayed the same in terms of performance. A week ago I've decided to check the manufacturer's site for any updates and I noticed that my BIOS (F.35 Rev A) is way outdated so I foolishly decided to update it to the latest (F.52 Rev A) in hopes of faster performance. Right after the BIOS update, I got BSOD no matter what I did. If I touched the computer when the disk was at 100%, I got BSOD. When I used Android Emulators, games etc I got BSOD and even sometimes when I came back to my computer after leaving it idle for long.
Here are the things that I have tried ever since:
1: Ran sfc and other disk repair commands. They found corrupted files and repaired them but it did not help.
2: Ran Mem check and it said I have a corrupted memory but I have to note that it did NOT say that when I ran the test a while BEFORE BIOS update.
3: Roll-back of BIOS which failed because it says "Cannot open the signature file" which I believe means they block me from downgrading it.
4: Ran Driver Verifier for ALL drivers which gave me BSOD upon system login for a few intel and *Realtek drivers (more details below) but after updating the drivers, I no longer got BSOD after I ran the test on them again.
*The intel drivers that gave me BSOD after running the Driver Verifier were Dptf_cpu.sys, Esfi_lf.sys
**The Realtek/PCIE drivers that gave me BSOD afterrunning the Driver Verifier were rt640x64 and Rtsper.sys
In order to get a better understanding of the BSOD, I checked the minidump files with BlueScreenView app and they are ALL caused by the driver ntoskrnl.exe
Below is the attached .zip file that has the past 3 minidump files and a msinfo32 in case if anyone wants to look at it.
https://drive.google.com/file/d/1Qbtti-pXYKTA32bqMxwBZiRjPPHpRs2A/view?usp=sharing
Thank you for your assistance.
I have a HP Envy Notebook J100-CTO which I bought in early 2016. This laptop has ever since been working just fine up until a year ago from which it started to show signs of slowdown. No matter how many times I've installed a new Windows, installed drivers and updates, dusted the laptop and even upgraded the RAM (from 8 to 12) it stayed the same in terms of performance. A week ago I've decided to check the manufacturer's site for any updates and I noticed that my BIOS (F.35 Rev A) is way outdated so I foolishly decided to update it to the latest (F.52 Rev A) in hopes of faster performance. Right after the BIOS update, I got BSOD no matter what I did. If I touched the computer when the disk was at 100%, I got BSOD. When I used Android Emulators, games etc I got BSOD and even sometimes when I came back to my computer after leaving it idle for long.
Here are the things that I have tried ever since:
1: Ran sfc and other disk repair commands. They found corrupted files and repaired them but it did not help.
2: Ran Mem check and it said I have a corrupted memory but I have to note that it did NOT say that when I ran the test a while BEFORE BIOS update.
3: Roll-back of BIOS which failed because it says "Cannot open the signature file" which I believe means they block me from downgrading it.
4: Ran Driver Verifier for ALL drivers which gave me BSOD upon system login for a few intel and *Realtek drivers (more details below) but after updating the drivers, I no longer got BSOD after I ran the test on them again.
*The intel drivers that gave me BSOD after running the Driver Verifier were Dptf_cpu.sys, Esfi_lf.sys
**The Realtek/PCIE drivers that gave me BSOD afterrunning the Driver Verifier were rt640x64 and Rtsper.sys
In order to get a better understanding of the BSOD, I checked the minidump files with BlueScreenView app and they are ALL caused by the driver ntoskrnl.exe
Below is the attached .zip file that has the past 3 minidump files and a msinfo32 in case if anyone wants to look at it.
https://drive.google.com/file/d/1Qbtti-pXYKTA32bqMxwBZiRjPPHpRs2A/view?usp=sharing
Thank you for your assistance.