Windows 10: Windows 10 Issues - SOLVED 2016-03-16

In the past two months, I've updated to Windows 10 from Windows 7. Since then, my computer has crashed roughly every week. The best information I can provide relating to these crashes is that it always seems to happen around the time I put my computer to sleep, or taken it out of sleep. Most of the time, I find my computer already on after having crashed and rebooted automatically.

Another issue I would like to mention (but I may need to go to a Minecraft forum for it) is how, from one day to the other, Minecraft's performance has dropped with no obvious explanation. I've been running it over 60 FPS for a while, and after shutting down my computer one evening and turning it back on the next morning, it has been running below 20 FPS. After removing VSync, setting the FPS limit from 120 FPS to Unlimited, doubling up on RAM, decreasing the render distance and setting the program on high priority, it still runs on average between 25 and 30 FPS at best. It's somewhat surprising considering my computer's specs.

I doubt this is related to anything above, but I'll mention this as well just in case. When building my computer, I bought one of the cheaper Wi-Fi adapters for it. It seems to stop working every so often, causing me to have to reset my computer. It is a known issue with those adapters though, and I am planning on getting new one.

My computer is a desktop I've had built for me. Below, I have provided my computer's specs that I've filled out to the best of my ability upon joining the forum. The computer is roughly 2 years old. If any other information is needed, I'll do what I can to provide it.

Computer type: PC/Desktop
System Manufacturer/Model Number: Unknown
OS: Windows 10
CPU: Intel Core i7 4770 @ 3.4 GHz
Motherboard: Unknown
Memory: 16 Gb
Graphics Card(s): AMD Radeon HD 7900

==
See my final post for solution.

:)

 

How to fix errors found when running scannow in windows 10 Version 1511 (OS Build 100586.164)

2016-03-23 12:18:09, Info CSI
00000058@2016/3/23:16:18:09.415 Primitive installers committed for repair

2016-03-23 12:18:09, Info CSI
00000059@2016/3/23:16:18:09.431 Primitive installers committed for repair

2016-03-23 12:18:09, Info CSI
0000005a@2016/3/23:16:18:09.452 Primitive installers committed for repair

2016-03-23 12:18:09, Info CSI
0000005b@2016/3/23:16:18:09.468 Primitive installers committed for repair

2016-03-23 12:18:09, Info CSI
0000005c@2016/3/23:16:18:09.484 Primitive installers committed for repair

2016-03-23 12:18:09, Info CSI
0000005d@2016/3/23:16:18:09.515 Primitive installers committed for repair

2016-03-23 12:18:09, Info CSI
0000005e@2016/3/23:16:18:09.531 Primitive installers committed for repair

2016-03-23 12:18:09, Info CSI
0000005f@2016/3/23:16:18:09.552 Primitive installers committed for repair

2016-03-23 12:18:09, Info CSI
00000060@2016/3/23:16:18:09.568 Primitive installers committed for repair

2016-03-23 12:18:09, Info CSI
00000061@2016/3/23:16:18:09.599 Primitive installers committed for repair

2016-03-23 12:18:09, Info CSI
00000062@2016/3/23:16:18:09.615 Primitive installers committed for repair

2016-03-23 12:18:09, Info CSI
00000063@2016/3/23:16:18:09.631 Primitive installers committed for repair

2016-03-23 12:18:09, Info CSI
00000064@2016/3/23:16:18:09.653 Primitive installers committed for repair

2016-03-23 12:18:09, Info CSI
00000065@2016/3/23:16:18:09.668 Primitive installers committed for repair

2016-03-23 12:18:09, Info CSI
00000066@2016/3/23:16:18:09.699 Primitive installers committed for repair

2016-03-23 12:18:09, Info CSI
00000067@2016/3/23:16:18:09.715 Primitive installers committed for repair

2016-03-23 12:18:09, Info CSI
00000068@2016/3/23:16:18:09.731 Primitive installers committed for repair

2016-03-23 12:18:09, Info CSI
00000069@2016/3/23:16:18:09.753 Primitive installers committed for repair

2016-03-23 12:18:09, Info CSI
0000006a@2016/3/23:16:18:09.768 Primitive installers committed for repair

2016-03-23 12:18:09, Info CSI
0000006b@2016/3/23:16:18:09.800 Primitive installers committed for repair

2016-03-23 12:18:09, Info CSI
0000006c@2016/3/23:16:18:09.815 Primitive installers committed for repair

2016-03-23 12:18:09, Info CSI
0000006d@2016/3/23:16:18:09.831 Primitive installers committed for repair

2016-03-23 12:18:09, Info CSI
0000006e@2016/3/23:16:18:09.852 Primitive installers committed for repair

2016-03-23 12:18:09, Info CSI
0000006f@2016/3/23:16:18:09.884 Primitive installers committed for repair

2016-03-23 12:18:09, Info CSI
00000070 [SR] Verify complete

2016-03-23 12:18:10, Info CSI
00000071 [SR] Verifying 100 (0x0000000000000064) components

2016-03-23 12:18:10, Info CSI
00000072 [SR] Beginning Verify and Repair transaction

2016-03-23 12:18:11, Info CSI
00000073@2016/3/23:16:18:11.432 Primitive installers committed for repair

2016-03-23 12:18:11, Info CSI
00000074@2016/3/23:16:18:11.448 Primitive installers committed for repair

2016-03-23 12:18:11, Info CSI
00000075@2016/3/23:16:18:11.470 Primitive installers committed for repair

2016-03-23 12:18:11, Info CSI
00000076@2016/3/23:16:18:11.502 Primitive installers committed for repair

2016-03-23 12:18:11, Info CSI
00000077@2016/3/23:16:18:11.517 Primitive installers committed for repair

2016-03-23 12:18:11, Info CSI
00000078@2016/3/23:16:18:11.533 Primitive installers committed for repair

2016-03-23 12:18:11, Info CSI
00000079@2016/3/23:16:18:11.564 Primitive installers committed for repair

2016-03-23 12:18:11, Info CSI
0000007a@2016/3/23:16:18:11.570 Primitive installers committed for re

 

Error when upgrading to Windows 10: 0xC1900101 – 0x40017

There is also this one from this morning:

2016-06-16 07:33:26, Error MOUPG CSystemHelper::CheckConnectedStandby(642): Result = 0x80070057

2016-06-16 08:06:03, Error MOUPG CSetupManager::GetDUSetupResults(5095): Result = 0x80070490

2016-06-16 08:06:03, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(DWORD) returned: [0x80004005]

2016-06-16 08:06:03, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(DWORD) returned: [0x80004005]

2016-06-16 08:06:03, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(DWORD) returned: [0x80004005]

2016-06-16 08:06:03, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(DWORD) returned: [0x80004005]

2016-06-16 08:06:03, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(DWORD) returned: [0x80004005]

2016-06-16 08:06:03, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(DWORD) returned: [0x80004005]

2016-06-16 08:06:03, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(DWORD) returned: [0x80004005]

2016-06-16 08:06:03, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(DWORD) returned: [0x80004005]

2016-06-16 08:06:03, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(DWORD) returned: [0x80004005]

2016-06-16 08:06:03, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(DWORD) returned: [0x80004005]

2016-06-16 08:06:03, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(String) returned: [0x80004005]

2016-06-16 08:06:03, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(DWORD) returned: [0x80004005]

2016-06-16 08:06:03, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(DWORD) returned: [0x80004005]

2016-06-16 08:06:03, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(DWORD) returned: [0x80004005]

2016-06-16 08:06:03, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(DWORD) returned: [0x80004005]

2016-06-16 08:06:03, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(DWORD) returned: [0x80004005]

2016-06-16 08:06:03, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(String) returned: [0x80004005]

2016-06-16 08:06:03, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(DWORD) returned: [0x80004005]

2016-06-16 08:06:03, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(DWORD) returned: [0x80004005]

2016-06-16 08:06:03, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(DWORD) returned: [0x80004005]

2016-06-16 08:06:03, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(DWORD) returned: [0x80004005]

2016-06-16 08:06:03, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(DWORD) returned: [0x80004005]

2016-06-16 08:06:03, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(String) returned: [0x80004005]

2016-06-16 08:06:03, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(String) returned: [0x80004005]

2016-06-16 08:06:03, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(String) returned: [0x80004005]

2016-06-16 08:06:03, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(DWORD) returned: [0x80004005][gle=0x00000002]

2016-06-16 08:06:03, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(DWORD) returned: [0x80004005][gle=0x00000002]

2016-06-16 08:06:03, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(DWORD) returned: [0x80004005][gle=0x00000002]

2016-06-16 08:06:03, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(DWORD) returned: [0x80004005]

2016-06-16 08:06:03, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(DWORD) returned: [0x80004005]

2016-06-16 08:06:03, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(DWORD) returned: [0x80004005]

2016-06-16 08:06:03, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(DWORD) returned: [0x80004005]

2016-06-16 08:06:03, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(DWORD) returned: [0x80004005]

2016-06-16 08:06:03, Error MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(DWORD) returned: [0x80004005]

2016-06-16 08:06:06, Error MOUPG CDlpTask::Cancel(979): Result = 0xC1800104

2016-06-16 08:06:06, Error MOUPG CDlpTask::Cancel(979): Result = 0xC1800104

2016-06-16 08:06:06, Error MOUPG CDlpTask::Cancel(979): Result = 0xC1800104

2016-06-16 08:06:06, Error MOUPG CDlpTask::Cancel(979): Result = 0xC1800104

 

Hello FredJ,

It must be very frustrating for you because that is a good build spec and should provide good gaming performance. I see that you do not know anything about the motherboard, that actually could turn out to be quite critical and I would guess you have not updated any of the motherboard drivers if you do not know what make or model it is. The first thing I would suggest is that you find out from whoever built it what the board is (or look inside and see what you can read off the motherboard labels) and then update the drivers from the manufacturer's website. This may go a long way towards sorting out all your problems. The graphics card will also have regularly updated drivers and you might need to install the latest version for this.

Please review what you find and we can take it from there.

 

Can't he just restart the computer and during the cycle period constantly press F2 or delete? That should take hime to the BIOS where he will be able to determine the make and model of his motherboard.

 

@FredJ

Motherboard Make and model
From a command prompt ADMIN enter:
wmic baseboard get product,Manufacturer,version,serialnumber

2nd Choice would be to download a program called Speccy which will give you lots more information. Its Free.
Download Speccy | Find your computer specs, free!

 

I have updated my specs after doing a bit of research. My motherboard is a Gigabyte H87-D3H. Below is a link for drivers, but I'm not sure which of those are up to date on my computer. Which one(s) should I install, if any?

GIGABYTE - Motherboard - Socket 1150 - GA-H87-D3H (rev. 1.x)


As for the graphics card, the drivers are up to date, and for Minecraft I have updated Java about a week ago.

Let me know if I forgot something else.

 

IMPORTANT UPDATE

I think I may have identified the issue, but I would require extra expertise that I do not have. After explaining my issues to one of my coworkers, he told me it could be a RAM related issue, possibly failure. Just to be sure, I used the Windows Memory Diagnostic tool to see if anythign came up. Upon completion, I booted up Minecraft and it was running at well over 150 FPS, according to the F3 menu.

Something I hadn't mentioned before that I noticed about Minecraft, which I never thought would be an issue, is how it never seemed to use most of it's allocated memory, usually remaining below 25%. Since the restart, I've been able to use shaders and still perform above 35 FPS, and the memory was used up easily above 60%.

Last night, I had shut down my computer for fear of a blackout (there was a storm in the area) and lo and behold, Minecraft's performance was down in the dust again. One quick Memory Diagnostic later, back to normal above 150 FPS.

I'm guessing it has something to do with my RAM not properly being used to it's fullest, but I would rather hear it from people who know better than from my less educated self diagnostic.

Thanks to everyone who has helped me so far. I've been able to learn more about my computer in the past three days than in the last two to three years.

 

UPDATE 2016-03-03

I'm still getting occasional Blue Screen crashes, but I'm never there to see them happen. Since I last updated, I've updated my BIOS, which was a few versions late. Otherwise, everything is up to date. I'm still looking for help.

 

You can try this: Blue screen of death (STOP error) information in dump files. to view past BSODs.

 

Further to CountMike's advice, do the following to see the BSODs and the STOP value.

Rt click the windows icon bottom left and then click 'Control Panel'. Next click 'System' then click the 'Advanced' tab. Now click 'Settings' under 'Startup and Recovery'. Uncheck 'Automatically restart' under 'System failure'.

Now the BSOD will stay on the screen after a crash and you will be able to note the STOP number.

 

UPDATE 2016-03-16

There were two issues that contributed to my computer's poor performance.
1. My CPU needed cleaning
2. The Fast Start-up feature

Every time I shut down my computer and later turned it back on, I had the freezing issues, but never after restarting. The aforementioned Fast Start-up feature, which is only used upon shutting down, caused my computer to have between 10 and 14% of CPU usage for System Interrupts. When I restarted, the feature wasn't used and CPU usage was 0.1% at its highest. Turning off the feature solved the issue.

Thanks to everyone for your help!