Blue screen of death stopcode – CRITICAL SERVICE FAILED

On June 29^th, as usual I was playing a heavily modded Skyrim that freezes and crashes a lot. I decided to stop playing and started photoshop to edit some screenshots from the game, but when I opened it, it gave me an error that said:

“Photoshop has encountered a problem with the display driver, and has temporary disabled enhancements which use the graphics hardware.”

I clicked ok, and I was able to continue so I ignored the error and kept using photoshop. There was some screen tearing, but nothing else happened. After about half an hour I opened Microsoft Word 2016, and suddenly I got an error as well that said:

“Were sorry, but Word has run into an error that is preventing it from working correctly. Word will need to be closed as a result.”

Attachment 142060

I realized this is a serious problem, and restarted my computer. During boot up I got the blue screen of death, and windows tried to automatically do a startup repair but it failed multiple times. After trying out different startup options the only one that has worked so far is, disable driver signiture enforcement.

Every time I restart or start the pc, I have to repeat the process, and some things don’t even start like device manager and windows defender.

The device manager error:
Attachment 142059

the windows defender error:
Attachment 142061

Things I have tried are:

1. “sfc /scannow” found corrupted files, but it failed to repair some of them.
2. Windows restore fails too.
3. DISM.exe /Online /Cleanup-image /Scanhealth and Restorehealth didn’t do anything either.
4. I also realized my page file size was set to 400mb, when changed it to a higher number it temporary let me open device manager, but now it doesn't work anymore.

The only thing I haven’t tried is to do a complete reset from boot menu, but if this is a hardware problem, then is a reset even worth it?

The files and logs were not yet posted. See: BSOD - Posting Instructions - Windows 10 Forums

Link to the full cbs.log:
CBS.log - Google Drive

Link to the sfcdetails.txt:
sfcdetails.txt - Google Drive

Please follow the instruction on this web page: BSOD - Posting Instructions - Windows 10 Forums

Attachment 142089

Code:

BugCheck 5A, {1, ffff9d8f9722fa20, ffffd80d09582080, ffffffffc0000428}
Probably caused by : memory_corruption
Followup: memory_corruption

Code:

BugCheck 5A, {1, ffffbb03cae30c00, ffffd087cf2381c0, ffffffffc0000428}
Probably caused by : memory_corruption
Followup: memory_corruption

Code:

BugCheck 5A, {1, ffff9483db285920, ffffc9805bb1ec00, ffffffffc0000428}
Probably caused by : memory_corruption
Followup: memory_corruption

Code:

BugCheck 5A, {1, ffffb08631386df0, ffffdc0e16f1e180, ffffffffc0000428}
Probably caused by : memory_corruption
Followup: memory_corruption

Code:

BugCheck 5A, {1, ffffb38d8d417df0, ffffdc06253f4490, ffffffffc0000428}
Probably caused by : memory_corruption
Followup: memory_corruption

Code:

BugCheck 5A, {1, ffffc18942aa19d0, ffffe18151edd740, ffffffffc0000428}
Probably caused by : memory_corruption

Code:

AppxDeploymentFailureBlue

Code:

6/28/2017 5:22 PM    Application Error    Faulting application name: GTA5.exe, version: 1.0.1103.2, time stamp: 0x593a8107
Faulting module name: GTA5.exe, version: 1.0.1103.2, time stamp: 0x593a8107
Exception code: 0x80000003
Fault offset: 0x0000000001208d53
Faulting process id: 0x21bc
Faulting application start time: 0x01d2f03227d5af18
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Grand Theft Auto V\GTA5.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\Grand Theft Auto V\GTA5.exe
Report Id: 4e6f54d4-c36f-48bf-a9d9-0352dc3ac004
Faulting package full name: 
Faulting package-relative application ID:

Code:

6/17/2017 7:34 AM    Application Error    Faulting application name: FalloutNV.exe, version: 1.4.0.525, time stamp: 0x4e0d50ed
Faulting module name: FalloutNV.exe, version: 1.4.0.525, time stamp: 0x4e0d50ed
Exception code: 0xc0000005
Fault offset: 0x0077ac2d
Faulting process id: 0x27c8
Faulting application start time: 0x01d2e73890bd4092
Faulting application path: C:\Program Files (x86)\Fallout New Vegas\Fallout New Vegas\FalloutNV.exe
Faulting module path: C:\Program Files (x86)\Fallout New Vegas\Fallout New Vegas\FalloutNV.exe
Report Id: 502e4bbd-692d-454f-b8e2-358313610ada
Faulting package full name: 
Faulting package-relative application ID:

Code:

The system failed to flush data to the transaction log. Corruption may occur in VolumeId: J:, DeviceName: \Device\HarddiskVolume12.
(The I/O device reported an I/O error.)

Code:

The following file necessary for Windows startup was corrupt: c:\windows\system32\drivers\nvstor.sys

Code:

The following file necessary for Windows startup was corrupt: c:\windows\system32\drivers\nvstor.sys

nvstor64.sys
nVidia Storage Driver (nForce chipset driver)
NVIDIA

Code:

The driver \Driver\tunnel failed to load for the device SWD\IP_TUNNEL_VBUS\ISATAP_0.

Code:

The driver \Driver\tunnel failed to load for the device SWD\IP_TUNNEL_VBUS\ISATAP_0.

Code:

The driver \Driver\tunnel failed to load for the device SWD\IP_TUNNEL_VBUS\Teredo_Tunnel_Device.

Code:

Startup Repair failed.

Code:

The driver detected a controller error on \Device\Harddisk5\DR44.

Code:

The driver detected a controller error on \Device\Harddisk5\DR44.

Code:

Failed initializing BT device, failed RAM patch file open.

2017-06-29 13:42:51, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2017-06-29 13:42:51, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2017-06-30 10:16:39, Info CBS Failed loading COMPONENTS hive with ERROR_SHARING_VIOLATION, retry #1
2017-06-30 10:16:39, Info CBS Failed loading COMPONENTS hive with ERROR_SHARING_VIOLATION, retry #2
2017-06-30 10:16:40, Info CBS Failed loading COMPONENTS hive with ERROR_SHARING_VIOLATION, retry #3


Make sure all of your files are backed up. See the information below on making a backup image.

If you are unable to perform any of the routine steps an alternative option is to start with an in-place upgrade.
This will save your files and applications and reinstall the operating system.
To do this you must be able to boot to the desktop.
Create a bootable windows 10 iso: Download Windows 10
Repair Install Windows 10 with an In-place Upgrade Windows 10 Installation Upgrade Tutorials




Make sure that there is no over clocking while troubleshooting.
Sometimes there are problems in the bios that produce bsod.
The bios in your computer: BIOS Version/Date AMI 8.07, 8/24/2012
Please check the HP web site HP Software and Driver Downloads for HP Printers, Laptops, Desktops and More | HP® Customer Support
to see if this is the most up to date version.
To ensure that there are no improper bios settings please reset the bios.
Sometimes there can be failure to boot after resetting the bios.
So please make sure your files are backed up.
Please make a backup image with Macrium:
Macrium Software | Macrium Reflect Free: Macrium Software | Macrium Reflect Free
And please create a restore point.
How to Clear Your Computers CMOS to Reset BIOS Settings:
How to Clear Your Computers CMOS to Reset BIOS Settings
3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow
Once you have updated and reset the bios and made a macrium image and made a restore point perform these steps:
1) delete or rename the current cbs log (add old to the end of the file)
2) delete or rename the current dism log (add old to the name of the file)
3) winver (in the pop up about windows > view your windows version and build > type this information into the thread)
4) sfc /scannow (when this completes it should produce a brand new cbs log)
5) dism /online /cleanup-image /checkhealth
6) dism /online /cleanup-image /scanhealth
7) dism /online /cleanup-image /restorehealth (when this completes it should produce a brand new dism log)
8) chkdsk /scan
When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on copy > paste into the thread
9) Perform windows updates and post any failed KB# with error code into the thread
10) create a share link using onedrive to post the new cbs log: C:\Windows\Logs\CBS\CBS.log
11) create a share link using onedrive to post the new dism log: C:\Windows\Logs\Dism\Dism.log
12) Uninstall Fallout New Vegas and reinstall the application
13) Uninstall Grand Theft Auto and reinstall the application
14) use the Safely Remove Hardware icon in the notification area to stop a disk before you remove it from any USB port.The system failed to flush data to the transaction log. Corruption may occur.
This issue may occur if the disk is "surprise removed." For example, this behavior may occur if you remove the disk without using the Safely Remove Hardware icon in the notification area to stop the disk first.
15) Uninstall all Nvidia drivers/software
The best way to do this is to uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from the HP web site. HP Software and Driver Downloads for HP Printers, Laptops, Desktops and More | HP® Customer Support
Enter you computer's product or serial number, select the applicable operating system and find the Nvidia drivers
Display Driver Uninstaller Download version 17.0.6.7: Official Display Driver Uninstaller DDU Download
16) Uninstall the bluetooth driver using device manager and reinstall with the appropriate driver from the HP web site HP Software and Driver Downloads for HP Printers, Laptops, Desktops and More | HP® Customer Support
for your computers configuration and operating system
17) Run memtest86+ version 5.01 for at least 8 runs.
This may take hours so plan to run it overnight.
http://www.memtest.org/https://answe...f-ecc7b7ff6461
When Memtest86+ has completed 8 or more runs make an image of the results to post into the thread.
Memory problems. - Microsoft Community
18) Download and install HP UEFI diagnostics version 6.4
HP PC Hardware Diagnostics | HP® Official Site
Power on the computer clicking the F2 or F10 key repetitively. In the bios run the UEFI diagnostics in loop until failure mode. Start in the evening so that you can stop the loop in the AM.
If there is a failure it will stop and post an error code. If it does not stop press the escape key and exit the bios and boot to the desktop. Report the results in the thread.
19) Read this link on Windows driver verifier so that it can be used after the memory testing has completed.
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
20) The system settings need to be modified to not automatically restart so that you have ample time to view the bsod window.
Follow the settings in this link:
BSOD Finding and fixing them - Microsoft Community
Keyboard: win + r keys simultaneously > type or copy and paste: sysdm.cpl > click advanced tab > under startup and recover click settings > under system failure un-check automatically restart
See this link: BSOD Finding and fixing them - Microsoft Community
BSOD Finding and fixing them - Microsoft Community

Thank you for your suggestions. I fixed the issue by upgrading windows using the media creation tool.

Great. That has taken care of many problems and reduced the troubleshooting. Bsod can come from drivers, software applications, and hardware. HP is one of the few computer companies that provides on board diagnostic studies. If you are able to download and install the latest version if the HP UEFI diagnostics please run them overnight to rule in or rule out any hardware problems. Then you will have addressed two possible areas and have unchecked drivers. This would be helpful if you have another bsod. The UEFI diagnostics can be run as one extensive test which generally runs for about 4 hours but depends on the amount of RAM and the size of the drive. Run the loop until failure in the evening and in the morning if there is no failure press the escape key and exit the bios. If there is a failure there will be a code that only HP can decipher. This may give you a little peace of mind knowing that you have done an in place repair to the os and checked the hardware.