Card Going South?

FredEx

New member
Don't know if you all know what "Going South" means, here it means it is going bad. All of a sudden the last two days I've had crashes. First, all temps are good, better in fact since I turned the heat down and the ambient in the house is lower. I may have more than on issue.

I had not used Firefox for a while, not at all on this system and since they'd come out with 20.01 I decided to give it a go. I get errors on it, but that may be related to Tab Mix Plus auto upgrading. Problems with it started the same day, but other problems started then too. Is it different issues or are they related? Have not figured that out.

I'm having to run my 6850 which is just a year old, sis bought it for me for my birthday last year when my 5770 died. That was this time of year, since my BD is May 4th and the card died just before it last year. ANYWAY...I was getting a message the Windows Desktop Manager stopped working and it was closed down. I think I fixed that dumping Aero (or whatever you call the transparent desktop). I have not gotten the error since changing it. I still have gotten BLUE SCREENS in the last couple days. Also the Catalyst Control Center has died a few times. I updated to a Beta to see if that helps, it didn't. It has only crashed once in a day. I'm back on Chrome and it died on me a bit ago. Fluke or related?

When the blue screen hits I get a screen full of graphics artifacts and then to BLUE SCREEN. That leads me to believe there is a graphics card issue. I backed off the card overclocking which I have done nearly since I got it last year and it was in my old system. Temp was fine, it ran at 50 to 52, it is 49 right now.

Right now I'm scratching my head trying to track it down.

UPDATE: Odd shit going on. MSE would not complete a full scan without crashing. It may not be a Graphics Card (on topic mention) problem. I am doing many things. I uninstalled MSE and reinstalled, strange thing now is it is not going through files as fast. Before time wise it would be at about 500,000 scanned and crashing. After reinstall it is 16:30 in and at 92,000 files scanned.

The memory a few days ago I stepped up to spec, I backed it down. It is 2133 and I backed down to 18XX (forget exactly). No crash so far. Now MSE is flying through the files, 3 minutes later it has gotten to 340,000 files.

What I am doing as it runs is monitoring temps via CPUID. CPU is running at 100% and it is OCed to 4.204 and core temps now are bouncing 48 to 57 on one. The scan has gone 15 longer than before when it would crash. Maybe I'm okay now. Don't know why the Catalyst Control Panel died before unless it can't handle any instabilities and crashed before anything else would or the BSOD hit. That threw me off thinking a graphics card issue or graphics drivers due to it crashing. If the memory ends up being the problem I may need to look into some air hitting the memory...could put a filtered fan in the top of the case blowing down on it.

I'm at over 1,200,000 files scanned. Forgot I did not need to scan backed up files from my old systems drives. It is a good thing though, running the CPU at 100% for 38 minutes now and top temp on one core 58.
 
Last edited:
just btw firefox is an unstable piece of shit now
step everything back down to stock clocks and see if the same stuff happens, but as i said, don't use firefox as a reference point, it crashes no matter what you do.
 
It could just be AMD drivers mate. What you describe seems to be pretty common for driver issues on Radeons.

I'd try some other drivers :)
 
just btw firefox is an unstable piece of shit now
step everything back down to stock clocks and see if the same stuff happens, but as i said, don't use firefox as a reference point, it crashes no matter what you do.

I have heard A LOT, and buy saying a lot i mean like really a lot of ppl saying eh firefox keeps crashing and crashing. To be honest i am using firefox for 5-6 years now and i haven't had more then 10 crashes in the while time. No matter how many tabs i open or whatever i do. I even wrote some crazy java applications (Mandelbrot, Sierpinski triangle[SIZE=+1][/SIZE] etc.) to stress the cpu via the browser and it still didnt crash.
 
I have heard A LOT, and buy saying a lot i mean like really a lot of ppl saying eh firefox keeps crashing and crashing. To be honest i am using firefox for 5-6 years now and i haven't had more then 10 crashes in the while time. No matter how many tabs i open or whatever i do. I even wrote some crazy java applications (Mandelbrot, Sierpinski triangle[SIZE=+1][/SIZE] etc.) to stress the cpu via the browser and it still didnt crash.

i used it for 3 years as well, then about a year ago it just started running terrible when i had two tabs on different screens, it would run at sub 1 fps. awful. i used to love it though, until v12 or something like that, it basically went downhill when they changed the layout. since then i am using chrome and i love it, especially the part with the cloud which stores my bookmarks etc.
 
I used Firefox for many years tbh. I jumped aboard as soon as it came out years ago and used it faithfully until last spring when it started to get bloated and slow.

At first I didn't like Chrome's basic, almost naked layout. Didn't take long to get used to it though. It's just so fast tbh.
 
just btw firefox is an unstable piece of shit now
step everything back down to stock clocks and see if the same stuff happens, but as i said, don't use firefox as a reference point, it crashes no matter what you do.

It could just be AMD drivers mate. What you describe seems to be pretty common for driver issues on Radeons.

I'd try some other drivers :)

I have heard A LOT, and buy saying a lot i mean like really a lot of ppl saying eh firefox keeps crashing and crashing. To be honest i am using firefox for 5-6 years now and i haven't had more then 10 crashes in the while time. No matter how many tabs i open or whatever i do. I even wrote some crazy java applications (Mandelbrot, Sierpinski triangle[SIZE=+1][/SIZE] etc.) to stress the cpu via the browser and it still didnt crash.

i used it for 3 years as well, then about a year ago it just started running terrible when i had two tabs on different screens, it would run at sub 1 fps. awful. i used to love it though, until v12 or something like that, it basically went downhill when they changed the layout. since then i am using chrome and i love it, especially the part with the cloud which stores my bookmarks etc.

I used Firefox for many years tbh. I jumped aboard as soon as it came out years ago and used it faithfully until last spring when it started to get bloated and slow.

At first I didn't like Chrome's basic, almost naked layout. Didn't take long to get used to it though. It's just so fast tbh.

I used Firefox faithfully for years. Later last year i started having issues on YouTube...slow, would not run vids at all and crashed on them. I get pissed at YouTube since they do have problems at times, but these were all Firefox. In Chrome everything ran perfectly...except when YouTube was slow itself.

I heard they'd updated Firefox, so tried it again. It was working fine until all these problems started. Any of the browsers were crashing when I hit a video or a large pic. The Catalyst Control Panel was dying. The scrambled screen and then the BSOD mislead me to thinking video.

There is a BIG reason I leaned that way, since I have had this system graphics problems have been a problem. The video card that was in it was dead. I run my old card in it now. I had it in PCIE slot one and that started acting up. It would run, but when shut down and then rebooting it could no see the video card. It got worse and worse. I pushed on the card as it booted and it worked. The slot feels loose, a card is too easy to push in it. I moved the card to the second PCIE slot (fits a lot tighter) and that problem disappeared. SO, that is why I thought graphics card problem right away when this started.

Friday and Saturday were busy days for updates...I started using Firefox again, Java updated, I jumped the memory up, Windows applied some updates, Malwarebytes did a full update (some reported it killing Win on the update before that fix) and I'm sure I forgot something. There were many directions to look.
 
Back
Top