Hello I had a power outage a few weeks back and when I came back to the PC the bios was reset to default and once I got it setup I started getting Display Driver Stopped Responding and has recovered errors. I ended up doing a full system reinstall since it has been a while and I still get this error but I am also getting the BSOD. Any ideas? I have included a zip file with all logs. Thanks
Hello and welcome snipe mate I have never heard of a BIOS being chnaged to default by a power outage because it has it's own power supply - the CMOS battery so unless that was completely flat or broken by that outage then the BIOS settings would have stayed what they were.
In the msinfo32 file there isa problem device - the Ethernet connector is disabled but apart form it nothing sticks out as obvious. So do you know what the BIOS settings were before the outage if so why haven'y you reset them. The battery by the ay would be best renewed before you do that anyway.
I figured the cmos battery was probably the reason for the bios reset. This motherboard has 2 ether net controllers and the one I am plugged into is working so it must be the other one. I have been wondering if my psu was causing the display driver issues. Blue screen view says the problem ed driver is atikmdag.sys. I have the most current and drivers installed (beta).
Ok mate go back a driver because that error is probably the beta and usually the advice is to uninstall the Catalyst Control Centre and use the device driver alone.
Now to test your PSU use my little ditty and report back the rail volts
Using HW Info
PART A:
You can test the volts on the PSU with HW Info HWiNFO, HWiNFO32/64 - Download < download the right bit version and close the right hand window select Sensors and scroll down to the power section where you will see what the volts are doing see my pic. In my pic the section (Nuvoton) with VBATT as a dead give away you are in the section for the rail voltages. There are other section titles and one that pops up often is ITE (sometimes the usual one for Gigabyte boards)
Now the voltage on the different rails have to be within 5% =+/- of what is required or the machine will not work properly if at all.
Limits +/-
12v = 11.4 – 12.6v
5v = 4.74 – 5.25v
3.3v = 3.135 – 3.465v
The Power good signal voltage at pin 8 on the 24 pin plug (grey cable) should be the same as the 5v rail reading/s
See this for the rail voltage info
PSUs 101: A Detailed Look Into Power Supplies (Section 2.)
The original right hand window shows the machine running and is handy for that but for looking at the components in some detail close it and use the main left hand side panel
FOR OTHER COMPONENTS
PART B:
Open each small square with + in it on the section the components are in and then click on the individual component/s (it will highlight in blue) - in the right hand side will appear all sorts of details including brands speeds and other essential info that particular device. See pic for example.
Handy program to keep for very detailed info on components anyway
Ok I am out atm so I will try this out later when I get a chance. Thanks KS for the info. I will report back once I know more.
I just booted up and withing 20 sec of desktop showing I got display driver stopped responding and has recovered. Usually though if that happens it will not happen again until reboot. I have also tested the system while playing Metro 2033 (POWER HUNGRY GAME) and the GPU will have 99% load and not problems (for the 10mins I tested) Here is a screen of my voltages which tome look ok, some are a bit lower but not too bad. I have a Corsair CM750M so it def isnt a crappy PSU. I am going to try going back in the display driver to the previous version now.
Yep mate the PSU is real good the 5v is low if you could call that low - you only have to do the maths to find that 5% +/- of rated volts to see that.
I also run Corsairs in my builds too and never had a problem myself. But at least it has eliminated any issue there. What I don't get is why the BIOS reset to default back then.
Well there is 1 test for that I have not done. If the cmos battery is dead and I shut down the system and unplugit, the bios should reset again if the battery is dead. I still have not had a chance to roll back the driver yet but I should be able to do that today.
Yes well the BIOS will reset to default if you do that or at least the default that was there where you last updated it. It (the BIOS) is unless I have it terribly wrong not back dateable if you get what I mean the default is what it normally sets itself at - any "tweaks" ie any overclocking settings will the only stuff lost.
For example say the original version was 4.1 and over time it has been updated to 4.5 then 4.5 stays as the default you cannot again unless I am terribly wrong go back to an older version because it is firmware as opposed to software which what drivers are. As you probably know already messing in the BIOS can be hazardous so be careful - there are boards with a dual BIOS so that in the event of one being trashed the other can be used.
Another thing to be mindful of is make sure the power is unplugged the power switch held down for a few seconds and ground yourself on the case before touching that battery to renew it which is what I would do because they are cheap enough not to have to worry about the cost of doing that.
You can in a lot of instances not even touch the battery to default the BIOS and that is to breifly touch the small pins alongside the battery to clear the BIOS to default.
Rolling back the driver is a good idea and you have nothing to lose.
Anyway perhaps another member might know more than I ad disagree with what I have stated above but I am fairly sure of it being the state of affairs.
If you want a fairly comprehensive read on the BIOS see this https://en.wikipedia.org/wiki/BIOS
Well I have not done anything with CMOS battery yet. I have uninstalled previous driver with Display Driver Uninstaller and installed last current version (DRIVER ONLY no CCT) and within 5 mins I got Display Driver Stopped Responding msg after screen goes black for a second. I do not know what the hell is going on, I have followed all suggestions for this error and still it is happening.
Quote