BOINC has been running fine for a little over 20 months on this current build. Then about a month ago, I started getting the blue screen of death. At first did not know what was causing it. The Stop Code is: THREAD STUCK IN DEVICE DRIVER.

So I disabled all start-up apps and PC ran fine for several weeks.

I then re-started BOINC and within 2-3 minutes, Blue Screen. I disabled BOINC and again it ran fine for a couple of weeks.

BOINC will run in CPU mode only (snoozing GPU). As soon as I start running GPU tasks it crashes within 1-2 minutes.

I installed the latest version of BOINC 7.6.33 and I updated the AMD drivers 17.10.1711.

Has anyone else come across this.

To this point what I have yet to do is go back to an much older driver, say 16.7.3.

Thanks,

Brett

---

To this point what I have yet to do is go back to an much older driver, say 16.7.3.

Given the age of the card, an older driver is probably what will be required, I would probably go for the first or second release for Win10 that supports that model, but given the limited amount of VRAM on that card i'd suggest not using it at all- it's performance about on par with your CPU, but uses a lot more power and can't do more than 1 WU at a time.
CPU- 4 WUs, 95W.
GPU- 1WU, 175W.
Similar run time for WUs. So it's just not worth running that card, even if you didn't have issues with it IMHO.

From one of your WUs that validated
WARNING: Used device has emulated local memory, WG restriction applied. User-defined WG size will be ignored if exceeds allowed value
WARNING: Used device has low amount of local memory,local memory FFT size will be reduced. User-defined local FFT size will be ignored if exceeds allowed value
WARNING: Used device has emulated local memory, WG restriction applied. User-defined WG size will be ignored if exceeds allowed value
WARNING: Used device has low amount of local memory,local memory FFT size will be reduced. User-defined local FFT size will be ignored if exceeds allowed value
WARNING: Used device has emulated local memory, WG restriction applied. User-defined WG size will be ignored if exceeds allowed value
WARNING: Used device has low amount of local memory,local memory FFT size will be reduced. User-defined local FFT size will be ignored if exceeds allowed value
WARNING: Used device has emulated local memory, WG restriction applied. User-defined WG size will be ignored if exceeds allowed value
WARNING: Used device has low amount of local memory,local memory FFT size will be reduced. User-defined local FFT size will be ignored if exceeds allowed value
WARNING: Used device has emulated local memory, WG restriction applied. User-defined WG size will be ignored if exceeds allowed value
WARNING: Used device has low amount of local memory,local memory FFT size will be reduced. User-defined local FFT size will be ignored if exceeds allowed value
WARNING: Used device has emulated local memory, WG restriction applied. User-defined WG size will be ignored if exceeds allowed value
WARNING: Used device has low amount of local memory,local memory FFT size will be reduced. User-defined local FFT size will be ignored if exceeds allowed value
WARNING: Used device has emulated local memory, WG restriction applied. User-defined WG size will be ignored if exceeds allowed value
WARNING: Used device has low amount of local memory,local memory FFT size will be reduced. User-defined local FFT size will be ignored if exceeds allowed value
WARNING: Used device has emulated local memory, WG restriction applied. User-defined WG size will be ignored if exceeds allowed value
WARNING: Used device has low amount of local memory,local memory FFT size will be reduced. User-defined local FFT size will be ignored if exceeds allowed value
WARNING: Used device has emulated local memory, WG restriction applied. User-defined WG size will be ignored if exceeds allowed value
WARNING: Used device has low amount of local memory,local memory FFT size will be reduced. User-defined local FFT size will be ignored if exceeds allowed value
WARNING: Used device has emulated local memory, WG restriction applied. User-defined WG size will be ignored if exceeds allowed value
WARNING: Used device has low amount of local memory,local memory FFT size will be reduced. User-defined local FFT size will be ignored if exceeds allowed value
WARNING: Used device has emulated local memory, WG restriction applied. User-defined WG size will be ignored if exceeds allowed value
WARNING: Used device has low amount of local memory,local memory FFT size will be reduced. User-defined local FFT size will be ignored if exceeds allowed value
WARNING: Used device has emulated local memory, WG restriction applied. User-defined WG size will be ignored if exceeds allowed value
WARNING: Used device has low amount of local memory,local memory FFT size will be reduced. User-defined local FFT size will be ignored if exceeds allowed value
WARNING: Used device has emulated local memory, WG restriction applied. User-defined WG size will be ignored if exceeds allowed value
WARNING: Used device has low amount of local memory,local memory FFT size will be reduced. User-defined local FFT size will be ignored if exceeds allowed value
WARNING: Used device has emulated local memory, WG restriction applied. User-defined WG size will be ignored if exceeds allowed value
WARNING: Used device has low amount of local memory,local memory FFT size will be reduced. User-defined local FFT size will be ignored if exceeds allowed value
WARNING: Used device has emulated local memory, WG restriction applied. User-defined WG size will be ignored if exceeds allowed value
WARNING: Used device has low amount of local memory,local memory FFT size will be reduced. User-defined local FFT size will be ignored if exceeds allowed value
WARNING: Used device has emulated local memory, WG restriction applied. User-defined WG size will be ignored if exceeds allowed value
WARNING: Used device has low amount of local memory,local memory FFT size will be reduced. User-defined local FFT size will be ignored if exceeds allowed value

Another shows lots of restarts.

---

Grant
Darwin NT

I'm not sure which driver you are actually using. The latest driver package for Windows 10 is 17.5.1 released on 2017-05-04, but since the end of 2015 only GCN GPUs have been supported "officially". The .inf shows several non GCN GPUs still in there.
The last official release for the Radeon HD 4000 series was the 13.1 legacy driver for Windows 8.

Whatever driver you are using has the same OpenCL and CAL driver as the 13.1 legacy driver. Which actually dates back to mid 2012.

Driver version:	CAL 1.4.1734
Version:	OpenCL 1.0 AMD-APP (937.2)

If the driver you are using has been updated and is using the older OpenCL components that could be a problem.
It used to be a common source of issues in the past. Where the main driver would get updated but the OpenCL and CAL components would not.
Which would result in errored tasks or driver crashes.
Since the HD4000 series only supports OpenCL 1.0 that may also be a factor.

My HD 4870 has been sitting on a shelf for while but I could try putting it in my i7-860 and installing Windows 10 for comparison.

---

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

Sorry guys. It is not the machine ID 6683283, i5-750 with the Visiontek 4870, it is the machine ID 7785479, the one with the 7870 and the R9-380. It has the specs of my signature i7-6700K etc......
It is driver package 17.4.3 dd. 2017-04-29

Brett

---

Sorry guys. It is not the machine ID 6683283, i5-750 with the Visiontek 4870, it is the machine ID 7785479, the one with the 7870 and the R9-380. It has the specs of my signature i7-6700K etc......
It is driver package 17.4.3 dd. 2017-04-29

Brett

I can give that configuration a try and see if I get the same weirdness.

---

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

Sorry guys. It is not the machine ID 6683283, i5-750 with the Visiontek 4870, it is the machine ID 7785479, the one with the 7870 and the R9-380. It has the specs of my signature i7-6700K etc......
It is driver package 17.4.3 dd. 2017-04-29

Brett

I can give that configuration a try and see if I get the same weirdness.

After using DDU to remove the old driver and installing 17.4.3 with my R9 390x I had a few BSODs before I ever had the chance to run BOINC.
I've gone back to 15.12 which I was using previously.

---

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