Small problem after I flashed my bios

[ZeroPenguins]

^Hmm actually I been having this issue with CCC it's like a win or lose situation. Before 12.1 my CCC wouldn't open up for months and I tried everything to fix it but nothing worked. Then after installing 12.1 CCC wouldn't start. So I went back into troubleshooting found out the issue was with .Net Framework, turns out CCC needed .Net Framework v4 but I had that installed, the issue was that .Net Framework had older versions and apparently CCC tried to run older version of .Net Framework and CCC refused to run. Now if I tried updating to 12.3, CCC won't start for me so I'm sticking with 12.1 for now. I honestly don't want to go through headaches of troubleshooting again.

Here's the fix:

[† L4ugh]

I gave up on ATI and Catalyst a while ago, so I'm not sure if this will be of any help. Some programs seem to require the full version of .net instead of the client version that comes default. Had this problem a while back, think it was with comicrack but can't remember for sure. It would only run when I had the full version of .net installed. Problem was the full version seemed to brake other software like aegisub. Don't really know why this was, or if it's been fixed yet. I just gave up on comicrack.

[nightraven]

This is what I would do.

Wipe and reinstall install all drivers and updates and confirm the problem still exists. The next step would be to reflash the new bios reboot and confirm that the problem still existed if so I would flash the bios down to the version before the newest. I would also check and make sure the the bios that got flashed was the correct revision for your board exp.. v2.0 2.1 some board change though there release cycle so they my not be exactly the same as an older version. I have had the automaded flash tools kill a board by installing the wrong bios.

[shadowtheman]

Ok I think this topic is getting pulled in the wrong direction. You said that one of the programs you found worked. Since thats what you really wanted all along, you now have a new question. Keep it as it is possibly at your own risk. (Sense you said it registered your temp at 19c it's probably your readouts that are bad and not your mother boards ability to track the safety data.) In this case this isn't that bad, consider your self lucky. If you leave it and nothing else happens than you should just leave sleeping dogs lie. If you do choose to reflash your bios how ever there is a chance the problem wont go a way due to the high possibility that the problem a now physical one with your mother board. Meaning re-flashing might cause more issues.

It is true that running a boot disk or flash stick to flash your bios does show better results but before you do make sure you know every thing you can. Not only that but make sure you know all risks before preceding forward.

Also note when you clean your registry your are removing unnecessary registry data that gets in the way of your pc running other programs at any given time. Doing a registry clean is something every one should do once a month to help your pc or mac run at peak health. (Note running other defrag programs to much can promote bad registry health. ) So clean regularly.

[† ballard]

I clean my registry on a regular basis. I have a really good cooler on my processor so 19c seems about right. However, any programs that tries to read the motherboard temps causes my computer to grey or white screen. I also noticed last night that after the bios update I get random artifacts in games. The shadows from time to time will freak out for less than a second. I'm currently on a fresh install of windows 7 64bit. I doubt it's my graphic card though since this didn't happen before the bios flash. I think this motherboard is screwed... I have another one under my bed. I just haven't felt like swapping everything out.

[shadowtheman]

Sigh, unfortunately it happens, to live and learn. I believe your right, about it not being your graphics card. Its more likely your boards a goner. That sucks. Just in case after you switch out the old board double check your hardware just in case. You never know what might have been effected.

Note, just in case after you switch to the new board you might lose owner ship of your files on your hard drive, or drives due to a prime hard ware change. If this happens post a thread and ill help you fix it.

[† ballard]

I'll be sure to run a thorough test on all my hardware. It really sucks that his happened. I'm definitely going to be way more cautious while updating my bios next time... if I ever do again. This motherboard is still under warranty, so I could probably send it in for a replacement. I've only had it for about 2 months. I bought it as a replacement for my asus board... they were taking so long to repair it I decided to buy and use this one temporarily. I'm just glad that I still have that one to switch back over to. I hope they repaired it properly.