June 2019
@puzzlezaddict @holger1405
I moved Procdump out of System32 and into its own folder and the dump was created without issue.
Here it is, it's a bit beefy, 21 MB. Let me know next steps whenever you can.
https://mega.nz/#!iaIVTYDS!NObNvSaZ5lQHfbrN4sZDTirGg8DSO35Gjf4PZAc3uZw
June 2019
Dentface-ah wrote:
I moved Procdump out of System32 and into its own folder and the dump was created without issue.
OK, that is strange.... but great that you found a workaround.
This is the error:
FAILURE_PROBLEM_CLASS: BREAKPOINT
FAILURE_SYMBOL_NAME: TS3.exe!Unknown
FAILURE_BUCKET_ID: BREAKPOINT_80000003_TS3.exe!Unknown
A breakpoint error means, in simple terms, that a point was reached at that a normal execution of the program was not longer possible.
This error is normal caused by a Registry mismatch and/or drivers missing/corrupt/not compatible with the hardware running the program.
You wrote on the first side that "Disable Game Mode" doesn't show up as an option in the game mode settings area. There's no switch to tick it on or off. I ticked "Disable fullscreen optimizations" as suggested in the link you gave."
Could you provide a screenshot of the entire "Gaming" page in WIndows settings?
You don't use a Windows "N" version?
Run "chkdsk /r" on your C: and D: drive.
Furthermore:
June 2019 - last edited June 2019
Hello, @holger1405:
Here's what I see in the Windows Game Mode settings. As you can see, there's no option to turn it on or off.
Windows "N" version is exclusively sold in Europe, I believe. My computer model is GL702VSK Signature Edition by ASUSTek Computer Inc. Other specs were listed in my first post in this thread.
I have attached the logs of chkdsk for both the C drive and the D drive. Both appear normal.
For the DISM Restorehealth, there was this error:
PS C:\WINDOWS\system32> DISM.exe /Online /Cleanup-image /Restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.17134.1
Image Version: 10.0.17134.829
[===========================84.1%================ ]
Error: 0x800f081f
The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
I looked in dism.log and there's just tons of stuff going back to May 2018. If there's anything you need to see from inside there, let me know.
Here is the sfc / scannow log. No issues here.
PS C:\WINDOWS\system32> sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
Let me know if there's anything else you need.
June 2019
Do you have a installation medium for Windows Build 17134? (Version 1803)
June 2019
@holger1405
I'm not entirely sure what an "installation medium" is. Could you explain further please?
June 2019
@dentfaceah Holger1405 means do you have a DVD or USB that you could use to install Windows 10, specifically build 1803, which is the one you currently have. You could create one; it's not that hard. But let us know if you already have one.
June 2019
@holger1405 @puzzlezaddict My PC doesn't have a disk insert, but I could use a USB, only problem is I don't believe I have any USBs on hand that hold very much data. What would be the purpose of doing a Windows 10 reinstall?
June 2019
It wasn't so much about a Windows 10 reinstall but to repair the component store.
The error the DISM command gave you renders the SFC scan practical useless because SFC uses the component store to repair defective Windows files.
The USB stick would need at least 8GB.
June 2019 - last edited June 2019
I unfortunately do not have a USB stick with 8GB. The best I have is 4GB. Is there another way to do this?
June 2019
You would need a iso file of the Windows install DVD.
But the newest build is 18362, there are no official MS sources for 17134 anymore and the build looses support in november anyway.
So it might be a good idea to update to the newest build anyway.
I however can't promise that a update will help with the error. But we most probably would have a working component store and purged other possible error sources as well.