Windows 10: BSOD after upgrade to Win10/trouble "Resetting" Win10/

It's installed in C:\\Program Files\\Adobe\\Adobe Photoshop CC 2015.

 

I ran a program called CCleaner, (The Pro version...which is supposed to delete all sorts of things including old files and unused extensions) and also just deleted the entire Adobe main folder. Will that fully rid my PC of the program?

 

One last change. Edit the hosts file and remove the entries for adobe.

As mentioned earlier, the dump (only one in the zip file) shows a DRIVER_POWER_STATE_FAILURE (9f). There are several BIOS updates for your system board ASUSTek P8H77-V. Please update to the latest which is:
Code: P8H77-V BIOS 1905 Improve system stability. File Size 4.18 MBytes update 2015/03/20[/quote] See if that resolves the problem. If not, run the following in sequence from a Elevated Command Prompt:
Code: Dism /Online /Cleanup-Image /StartComponentCleanup Dism /Online /Cleanup-Image /RestoreHealth SFC /scannow[/quote]

 

See if that resolves the problem. If not, run the following in sequence from a Elevated Command Prompt:
Code: Dism /Online /Cleanup-Image /StartComponentCleanup Dism /Online /Cleanup-Image /RestoreHealth SFC /scannow[/quote] [/quote] Ok, thank you Rich. These are all complicated steps for me, please pardon my lack of knowledge and thank you for helping! I have so far managed to remove the string of adobe entries from the hosts.txt file. I have also found the BIOS 1905 file from the ASUS website, it downloaded into a file type I am unfamiliar with (cap) so I am researching how to update that. I will respond again once I can properly install it. Then I will simply leave my PC on idle for a few hours, as the BSOD always happens if I do that. Fingers crossed!

EDIT: I updated the BIOS to the version you suggested and almost immediately my system froze. I should add that it rarely goes to the BSOD, usually it just states that windows has stopped responding and then everything stops working/responding.

I then ran that command prompt you said and the first operation completed successfully.

The second operation stalled at 99.2% with error code 0x800f081f The source files could not be found. It made a log file and also gave me a link for more information on specifying a "source location"

 

KYHI posted direction on how to fix it here: SFC SCANNOW and DISM RESTOREHEALTH - Repair Corrupt Files

See if you can follow Kyhi's instructions. They work most of the time.

 

Thank you VERY much for all of your time Ztruker! I have borrowed a repair disc from a friend and will try KYHI's directions later this evening. Then I will do a few tests to see if we have fixed it!

 

Sounds good. Let me know how you make out.

 

Ok I have made the boot repair USB and am starting with the operations, should I just start at 1 and make my way all the way down?

EDIT: I am sorry, I made the wrong file. I made a backup recovery tool, I am now downloading the ISO so that I can mount it.

 

I attempted to use the first several steps of the windows image health program by Kyhi.Step 1 and Step 2 provided me with .txt files which I included.Step 2 and Step 3 provided me with the same error code.Step 4 recommended that no component cleanup was needed.Step 7 ran a scan to completion and provided me with a .txt file which I included.I have not yet run any steps 8-15I ran Step 16 to help me download the proper .iso file.

 

You need to provide a Windows 10 source that Kyhi's program can use to repair missing files.The tutorial says to use Step #16. Once you have the ISO downloaded, just right click on it and select Mount. Then run Steps 1, 2 and 3.

 

Sorry I wasn't more specific, I actually did that. I mounted the windows.iso file and then chose that source. I can retrace those steps once more to ensure that I selected the proper source.

Again thank you for taking your time to help me. I have already learned so much.

 

There is a chance the corruption is too large for DISM to fix, a quick look shows tons of payloads corrupted. There is a chance an in-place upgrade helps faster/better.

 

Ok, thank you! I have found a tutorial for "in-place upgrade" and will attempt later tonight when I get home.

 

Ok, After several days of attempting this in-place upgrade I am getting no where. I followed a tutorial on these forums for this type of upgrade, making sure to log in as admin, turn off AV software, and to disable secure boot from my BIOS. When mounting the ISO file, I am getting a setup error asking me to reboot and try again.

My next question I have, is would it be possible to just to a completely clean install, just wipe the HD and everything and start over?

 

It is possible, but if you don't mind I would like to rule out a few things as possible interference before moving forward.







Diagnostics Test

HDD TEST
*Arrow Run HDTune to

• check the health,
• scan for errors, no quick scan but full scan
• run a benchmark.

It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following

• the health,
• the error scan,
• the benchmark incl. following
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

*Arrow Run SeaTools DOS to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run the long test.
*Arrow Run chkdsk
Disk Check - Windows 7 Help Forums
Use option TWO with parameter /r
Upload the chkdsk log *Arrow Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums







Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.