Fed up with Windows 10

I’ve been having problems with Windows 10 for almost a month now. And the problems keep getting worse.

It started with the Nov upgrade that was forced upon us, which I delayed for some time, and since then I haven’t had a stable system. Just to make sure it wasn’t a hardware problem, I’ve run every test I can think of to check stability. I’m not overclocked, the memory checks to be good (both the Windows built in memory test and Memtest 86+ run overnight). The SSD checks out and I have no SMART flags showing up on any of the hard drives either. Maybe a psu issue, but I don’t think so. Temps are normal.

Going back to an image made in October eliminates the issues so far, but the damn thing is going to “upgrade” itself eventually. I’m seriously thinking of going back to my last image of Windows 8.1.

I’ve found corrupted files using sfc.exe/scannow and I cannot repair them. Yes, I’ve tried numerous methods.

Re-installing from a newly downloaded ISO from Microsoft also gives the same message from the scannow command. Yes, a completely fresh install says that it is corrupted. Updating from the ISO gives me a system that freezes constantly. Even Task Manager freezes and I am forced to reboot.

I don’t want to have to monitor updates constantly, so the best choice seems to be going back to 8.1 or 7. Unlike most, I rather liked 8.1 and never had issues with it.

Any other suggestions?

sounds like the MS iso is a bad download hence your problems?!

you got 30 days to revert from 10? make up your mind or your old keys will be invalidated.

If there was something fundamentally wrong with Win 10 1115 update causing file corruption, then it should be affecting everyone.

The 1115 update has a new kernel, which does stress the system more under load, and also has new power saving features.

My guess would be that the new kernel is exposing a system stability problem that the old kernel didn’t show.

Since you don’t have an overclock then I’m assuming that voltages in the BIOS are set on AUTO. This should give a stable system, but this isn’t always the case.

You may have to tweak v-core, and DRAM voltages manually, and perhaps even the ‘system agent and VCCIO’ voltages to get the system stable with the new Win 10 1115 update.

If you are not comfortable in doing this, then perhaps going back to Win 8.1 would be best for you.

I used the Microsoft Media Creation Tool. I don’t believe the ISO was corrupted upon download. I’m trying it again, but I don’t think this will solve anything.

The October image is running flawlessly so far. No BSOD’s, no freezing. I’ve been trying to see if I’ve installed anything since then that might have a deleterious effect, but haven’t seen anything obvious other than the updates from Microsoft.

The 8.1 image will reinstall without issues. It is already activated, so that is not a barrier to using it. Also, I don’t think the old keys get blacklisted. My copy came from a Windows 8 upgrade, (I did a clean install with it, following a few instructions on the net), and then the key changed when it was upgraded to 8.1. I can install the original Windows 8 in another machine I believe, though MS might not agree with that interpretation.

And I see Dee has answered while I was typing. I can adjust voltages easily enough but my system has been stable in the past before the updates. Stable enough to do video encodes overnight or do Prime95 overnight also. There is something with the updates that is screwing with my system.

I’ve tried updating drivers where it was possible, but this had no effect.

Also, freezing issues are not uncommon with Windows 10. I’ve been doing some searching on the subject.

If you can find the one bad update and hide it?
With the Pro version one can hide an update, I didn’t know this.
Reply #10 and #11.

There may be something else over there on tenforums that can help, if you haven’t already visited it.

Thanks for that Steve. I had forgotten about that Show/Hide updates tool from Microsoft.

Not sure it will work on the big 1511 upgrade however, and it may be the primary culprit.

New ISO had no errors in scannow once installed. Maybe this will help, but I’m now downloading updates to see if I can reproduce the freezing/BSOD symptoms.

Ok, next report. No programs installed, [B]only updates[/B]. sfc.exe/scannow reports corrupted files that it cannot fix. ???

I’m not sure this is an entirely bad thing, since the Oct. image that works without problems also has this reported by scannow. It just doesn’t have all the same updates.

Will test this to see how stable it remains under normal use, but if it starts exhibiting the same symptoms as before, its the last straw, and I’ll be going back to 8.1.

You have my sympathy Kerry, it’s damn infuriating. I’ve noticed that some rigs (including laptops) of all ages don’t like windows 10. (like the post about Jim’s lappie) Some wont even load it, some BSOD all the time, some work OK at least for a while. It seems every time an update Tuesday is installed more hassle seems to appear.

I have two main rigs, this one that has 7 on it and works perfectly whatever I throw at it and another with 10 on it and that one is a pain in the butt! Both rigs use Sandybridge i5 (this one) or i7 K processors and have the best memory and mobo’s money could buy at the time. The i7 rig is the one with 10 on it, a clean install and it likes to screw it’s self whenever it feels like it. It was perfect with 7, so what gives?

Neither machine is overclocked. The 10 machine is set to only install critical updates. All other updates I do myself via the manufacturers websites (or Nvidia)
I wonder how many computers there are that have been bricked by 10. This is some serious fiasco.

Not that I am any kind of expert but that sounds like driver(s) misidentified by WU and the changes are causing your system to be unstable.

BTW, over on tenforums, there is a subforum dedicated to BSOD and there are lots of threads.
I haven’t read any of them so have no clue if they are helpful or not.

I would be curious if there is any way to contact MS concerning this?

Windows update doesn’t load any drivers. If it ever does, I would remove them and use the up to date drivers that are supplied by the manufacturers.
All this points to a conflict with the updates and the hardware. Dee has a new rig with up to date components, she has no problems with 10. A huge amount of people don’t have the latest, or near latest hardware and are having hassles. Strange though it may seem, I was talking to Jim this morning and he gave up with his older lappie and spent nearly £2000 on a new laptop with windows 10 and it went BSOD within an hour. He now owns a Macbook, it cost a bit more, he’s more than happy as it does exactly what he wants. email and web browsing and can connect to work without interruptions.

Microsoft are impossible to contact as far as I know, the only way is through Facebook it seems and I don’t subscribe to that. Has anyone else tried Facebook and what kind of answer did you get?

[QUOTE=Kerry56;2767747]Ok, next report. No programs installed, only updates. sfc.exe/scannow reports corrupted files that it cannot fix. ???

I’m not sure this is an entirely bad thing, since the Oct. image that works without problems also has this reported by scannow. It just doesn’t have all the same updates.

Will test this to see how stable it remains under normal use, but if it starts exhibiting the same symptoms as before, its the last straw, and I’ll be going back to 8.1.[/QUOTE]

I.ll try to assist you if you like to proceed finding the culprit and not give up…

First of all, I understand that you did not have any flaws once Windows was installed and so the trouble is caused by one of the updates from Windows update.
I will in this case advice yet again that if you choose to start over… Download the updates from Windows update using Portable updater http://www.portableupdate.com/ - That should make you able to install one update at a time and thereby find the culprit causing your trouble. I personally think this may be the shortest route to a solution.
Voxsmart is correct in that choosing the manufacturer’s drivers instead of MS provided ones may bring stability back, but for the record I have come across situations where the MS provided driver was the one making the system stable. In your case however, if this is the case, a MS provided driver may be the culprit.

If you rather not start over, there are a few pieces of information I would like you to provide.

  1. I presume you have updated BIOS and checked compatibility with the hardware manufacturers (motherboard, add-on cards and so on).
  2. Can you inform me of the 0x??? error code and error description on the BSOD
  3. Are there any errors found in ‘Device manager’(devmgmt.msc)?
  4. What errors do you have in ‘Event viewer’ (eventvwr.msc).?
    (right-click start and choose run from the context menu, then paste one of the filenames above)

If any errors in Event Viewer seem to multiply or otherwise be constant, I would very much like you to grab the following:

Just the description as shown

Snap the contents of the XML view.

With this information, I probably can figure out where it hurts and advice you further. :flower:

I ran Prime95 overnight. No problems, so I don’t believe there is any inherent instability in the hardware.

Bios of the motherboard has been updated to the latest version.

There are no add-in cards on the motherboard, not even a video card. Neither do I have any external devices, like an external hdd, though I do have one hub and the keyboard and mouse of course.

Since installing the ISO and the updates there have been no BSOD’s nor any signs of freezing, but I’m still testing and that will take days. There have been no critical errors, though lots of other types. If I get something that looks like it is the primary culprit, I’ll post it.

sfc.exe/scannow?.. still errors I guess…

your choice take the bubbling risk or revert as long as you still can

From the logs, it seems that Opencl.dll is one of the main culprits. Most of the people having issues with it are using Nvidia video cards and there is a conflict between Win 10 and this part of their drivers. Some, like me, are just using the Intel graphics, but still having issues. http://www.tenforums.com/performance-maintenance/29947-sfc-some-corrupt-files-can-not-fixed.html

Insider builds apparently have solved the problem, but those haven’t gone out to the general public yet.

I’ve followed instructions from the Windows 10 forum thread, and done a successful DISM cleanup using yet another ISO, this time from TechBench. Sfc.exe/scannow reports no errors. So maybe I’ve got it under control.

Now, they have multiple install files requiring people to download the right one for sfc to work? I read .iso works as well! MS is becoming more n moa a bunch of coding clowns.

What a waste of data bandwidth just to get another error corrected!
Don’t despair next winx update will plant new problems and so on.

Windows as a service?
MS is kiddin’ themselves big time when they believe people are paying for this service disaster - seriously!

okay, just my thought of the day!

Great that it sorted out :flower:
It is really such a drag when updating Windows leaves a mess behind. I can only verify that it does happen here as well

OpenCL.dll is not a NVidia developed component as it belongs to Khronos Group’s OpenCL components and is used by Intel and AMD as well.

00008390 01 00 4C 00 65 00 67 00 61 00 6C 00 43 00 6F 00 ..L.e.g.a.l.C.o.
000083A0 70 00 79 00 72 00 69 00 67 00 68 00 74 00 00 00 p.y.r.i.g.h.t...
000083B0 43 00 6F 00 70 00 79 00 72 00 69 00 67 00 68 00 C.o.p.y.r.i.g.h.
000083C0 74 00 20 00 A9 00 20 00 54 00 68 00 65 00 20 00 t. ... .T.h.e. .
000083D0 4B 00 68 00 72 00 6F 00 6E 00 6F 00 73 00 20 00 K.h.r.o.n.o.s. .
000083E0 47 00 72 00 6F 00 75 00 70 00 20 00 49 00 6E 00 G.r.o.u.p. .I.n.
000083F0 63 00 20 00 32 00 30 00 31 00 31 00 00 00 00 00 c. .
00008400 32 00 09 00 01 00 46 00 69 00 6C 00 65 00 56 00 2.....F.i.l.e.V.
00008410 65 00 72 00 73 00 69 00 6F 00 6E 00 00 00 00 00 e.r.s.i.o.n.....
00008420 31 00 2E 00 32 00 2E 00 31 00 31 00 2E 00 30 00 1...2...1.1...0.
00008430 00 00 00 00 3C 00 0E 00 01 00 43 00 6F 00 6D 00 ....<.....C.o.m.
00008440 70 00 61 00 6E 00 79 00 4E 00 61 00 6D 00 65 00 p.a.n.y.N.a.m.e.
00008450 00 00 00 00 4B 00 68 00 72 00 6F 00 6E 00 6F 00 ....K.h.r.o.n.o.
00008460 73 00 20 00 47 00 72 00 6F 00 75 00 70 00 00 00 s. .G.r.o.u.p...
00008470 2E 00 07 00 01 00 49 00 6E 00 74 00 65 00 72 00 ......I.n.t.e.r.
00008480 6E 00 61 00 6C 00 4E 00 61 00 6D 00 65 00 00 00 n.a.l.N.a.m.e...
00008490 4F 00 70 00 65 00 6E 00 43 00 4C 00 00 00 00 00 O.p.e.n.C.L.....
000084A0 3E 00 0B 00 01 00 4F 00 72 00 69 00 67 00 69 00 >.....O.r.i.g.i.
000084B0 6E 00 61 00 6C 00 46 00 69 00 6C 00 65 00 6E 00 n.a.l.F.i.l.e.n.
000084C0 61 00 6D 00 65 00 00 00 4F 00 70 00 65 00 6E 00 a.m.e...O.p.e.n.
000084D0 43 00 4C 00 2E 00 64 00 6C 00 6C 00 00 00 00 00 C.L...d.l.l.....

For more information about Intel’s implementation, go here:
For actual drivers:
…or for backround, go to Khronos Group’s homepage:

One final note from me. Microsoft is quickly earning a reputation for cluster****s with their update/upgrade schedule in Windows 10. [I]Each time[/I] something breaks for someone, and its becoming Russian Roulette with your operating system.

If they don’t get this under control quickly, Windows 10 is going to be a slowly sinking ship, with everyone looking for a way off. Only the Enterprise edition might succeed, and only because the IT admins have control over what is updated with it.

Hey Guys, can we not get Windows 10 Enterprise via MyCE as a group? I know very little about how Enterprise versions work. Just a thought. Does anyone else have any ideas on the subject.

[QUOTE=voxsmart;2767874]Hey Guys, can we not get Windows 10 Enterprise via MyCE as a group? I know very little about how Enterprise versions work. Just a thought. Does anyone else have any ideas on the subject.[/QUOTE]

To qualify for a MS Enterprise license [U]your company[/U] must have 500+ employees - rules changed just recently