Windows is crashing with the above error when I run BOINC and also when I use Capture 1. I get the Blue screen and the error "thread stuck in device drive"

I have tried updated the graphics driver AMD Radeon R9-380, even tried rolling back to one from 2016, all have no effect.

The timing of the crashing seems to coincide with Windows 10 Update failing. For about 2-3 months now Windows 10 update is stuck It is trying to install "Feature update to Windows 10, version 1703", but get the following error.
"We can't install some updates because other updates are in progress........"

I have googled the error and tried a few suggested fixes, but "no joy"

Other than the two issues, the PC seems to run fine.

Any thoughts, suggestions.

Brett

---

Windows is crashing with the above error when I run BOINC and also when I use Capture 1. I get the Blue screen and the error "thread stuck in device drive"

I have tried updated the graphics driver AMD Radeon R9-380, even tried rolling back to one from 2016, all have no effect.

The timing of the crashing seems to coincide with Windows 10 Update failing. For about 2-3 months now Windows 10 update is stuck It is trying to install "Feature update to Windows 10, version 1703", but get the following error.
"We can't install some updates because other updates are in progress........"

I have googled the error and tried a few suggested fixes, but "no joy"

Other than the two issues, the PC seems to run fine.

Any thoughts, suggestions.

Brett

I've had a related issue on a Windows 10 machine I use at work.
Since Windows update refused to stop updating the Intel GPU driver, which causes the monitors on my docking station to stop working, I added a group policy specifying the Intel GPU was not allowed to be updated.
Because it doesn't make any sense. Windows 10 downloads the Intel GPU driver that causes the problem and then gets stuck not being able to install it. So no other updates are ever installed or downloaded.
It would be really nice if that "don't download driver updates" setting actually worked.
Getting the latest driver from Intel has not yet solved my docking station monitors not working issue. Any driver I have tried after 2016-11 is no good.
I find it to be a really odd issue. As I don't see what the iGPU driver has to do with monitors attached to a USB 3.0 docking station & I disable to monitor on the notebook itself.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Brett,

Can you tell us how any tasks are you running on your GPU at the same time? And what does your mb*sog.txt command line look like?

eg. -sbs 192 -spike_fft_thresh 2048 -tune 1 64 1 4 ?

Are you running TThortle? (free temperature limiting software). If this is a laptop are you keeping it on a "cooling table" (external fan system) when you are not using it yourself?

What kind of memory usage does Gpu-Z report? Does it jump around a lot during processing of the same task? (That MIGHT mean you have -sbs set too large).

Have you tried a clean driver install directly from AMD? There are reports that AMD/NVidia drivers from Microsoft are missing stuff that make it possible (or reliable?) to run Seti on Windows 10. What I am less clear about is a report that after version xxxxx AMD has dropped the support necessary for their GPU to run Seti.

HTH,
Tom

---

A proud member of the OFA (Old Farts Association).

Couple of quick answers to some of your questions. The machine is the one listed in my signature, built Sep, 2015. Ran flawlessly until about 3-4 months ago. One task per GPU, R9-380 & 7870. One difference is it had the Corsair H80iGT. It failed and I currently have a heat sink and fan (Arctic Freezer 7 Pro). temps are fine.
I am not running TThortle.

I only install drivers directly from AMD, never from Windows.

Will follow up with the balance of your questions later.

Thanks,

Brett

---

Couple of quick answers to some of your questions. The machine is the one listed in my signature, built Sep, 2015. .....Will follow up with the balance of your questions later.

Thanks,

Brett

Ok. I only saw the laptop listed as a "current" system. I recommend TThortle highly because it does a better job of paying attention to the temperatures than looking at them in your bios settings. And it will reduce your cpu and/or gpu speed to meet the temperature targets that you have set.

HTH,
Tom

---

A proud member of the OFA (Old Farts Association).

Yes, you don't see it because it hasn't been running for a few months as it was crashing within minutes of starting BOINC.

I am focusing on getting my Windows update problem solved first. Once that is fixed I can eliminate it as the problem, but right now I do not know for sure. I have an IT expert (guy we use at work) working on it remotely, so hoping to know in a day or so (he can be a bit slow).

Will let you know where we are at once Windows update is fixed.

Thanks

Brett

---

Well, I determined it seems to be the HD7870.

I was running two GPU's in the machine than was crashing (R9-380 & HD7870). So I pulled the 7870 and replaced the 4870 in my second box with the 7870 . So now the main box, with only the R9-380 is running fine.

However as soon as I start GPU crunching in the second box with the 7870, everything freezes and the screen just shows red or grey with vertical black stripes. No BSOD. The PC runs fine, CPU crunching works no problem, but as soon as I start GPU crunching, within 15 seconds crash........

Brett

---

Hi!
I don’t know if this will be helpful, but I have an A10-7850K system, having R7 graphics, and I was having trouble with Seti GPU tasks resulting in corrupt screens. I also had the Blue screen error "thread stuck in device drive" for Einstein and Milkyway GPU tasks. I am still testing, so have not as yet posted results to questions I asked here and on Milkyway, but the problem seems to be the Crimson drivers. I back installed to 15.7.1, the last pre-Crimson driver, just over three weeks ago and have not seen either problem again as yet. I hope this helps.

Thanks. I didn't go that far back, but will give it ago.

Brett

---

Thanks. I didn't go that far back, but will give it ago.

Brett

You're going to have to use that version or older because the crimson drivers install only OpenCl 2.0 which your 4870 is unable to use. My guess as to why it stopped working when running with the R-380 goes back to your Windows Update problem in that Update messed up the driver just enough to take out the 7870 but not the R-380. If the 7870 fails on the 15.7.1 driver, then that will be a sign that the card itself has failed.

---

... and still I fear, and still I dare not laugh at the Mad Man!

Queen - The Prophet's Song

Installed the 15.7.1, and 7870 still crashing, so I probably a hardware issue.

Brett

---

Installed the 15.7.1, and 7870 still crashing, so I probably a hardware issue.

Brett

I guess you will just have to replace it with a RX Vega 64...

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Sorry to hear that the card has failed. One last thing you could try before pricing a new Vega replacement, is to take off the fan shroud and heat sink and re-apply some new thermal paste on the outside chance that the old paste has dried out and the chip is overheating rapidly and shutting down.

---

... and still I fear, and still I dare not laugh at the Mad Man!

Queen - The Prophet's Song

I am having a different problem along this same vane as crashes, mine has and been doing random restarts ( windows 10 pro) and minidump analysis said,
First crash:
Bugcheck-str: 0xIa-41792
Default-bucket-id: code-corruption
Process-name: setiathome-8.0
Current-IRQL: 2

Second crash:
Bugcheck-str: 0xIa-61941
default-bucket-id: win8-drive-fault
Process-name: setiathome-8.0
Current-IRQL: 0

I have been dealing with new system after the last one died a horrible death and still getting blue screen restarts and my desktop icons reverting default positions.
Any help would be appreciated.

---

Any help would be appreciated.

Your computers are hidden, so that makes it rather difficult.
The most likely issue is a driver fault, or a hardware problem. Power supply or memory could also be responsible.

Do all the WIn10 updates. Once those are done, and there aren't any more, go to your motherboard manufacturer's web site & download & install their drivers. Do the same with NVidia or AMD to download their drivers for your video card (or Intel if you have integrated CPU graphics).
If you have any USB devices (wireless adaptor, printer/scanner etc) go to the manufacturer's web site & download their current drivers.

---

Grant
Darwin NT