BSOD after installing 12.11 beta

Hello,

As discussed in a few threads in this forum, I've seen that several people (including myself) keep getting a BSOD after installing 12.11 beta.

I'm trying to understand why it seems to work for some people and for others it doesn't? I tried most methods outlined in the forums, from installing over previous drivers to doing clean installations using driver sweeper / driver fusion. If it isn't the way in which these drivers are installed then it has to be something else. Perhaps the BIOS version? Could that affect the drivers at all?

Could people please post their system specs along with BIOS versions / what drivers they upgraded from? Please also mention if you're still getting BSODs or if you've resolved your issues somehow.

------

I tried different methods of installing the 12.11 beta. I was on 12.9 on my first try, I simply did an express uninstall from AMD, then installed the new drivers. It worked on first reboot and DX11 games seemed to work fine, but after subsequent reboots I got the usual BSOD on an "atikmpag.sys" file.

After that I tried the different ways to clean install the drivers (plus Intel ones) as suggested in various threads but I've had no luck.

System Specs

Clevo P150EM (not Sager)
i7 3610QM
7970M
16 GB DDR3 1600 MHz RAM
Win 7 x 64

CLEVO BIOS & EC version 1.00.04 (I'll have to double-check and update my post)

 

I had the bluescreen issue and I couldn't fix it without removing the 12.11 beta 3s.

I eventually gave up and reinstalled windows, installed the intel drivers first, then installed beta 3s. It has been fine for 10 reboots now...

System Specs

Sager NP9150
i7 3610QM
7970M
8 GB DDR3 1600 MHz RAM
Win 7 x 64

CLEVO BIOS 1.00.10 & EC version 1.00.07

 

Pretty much same problem as you. It will work fine after driver install at first reboot and BSOD after every restart. I tried pretty much all the methods I read on the forum other than fresh install windows (I really don't want to go through that). But seriously, it's a graphic driver update for crying out loud. We shouldn't have to reinstall whole windows for that.

Sager 9170
i7 3610QM
7970M
16 GB DDR3 1600 MHz RAM
Intel 520 SSD main HD
750GB 7200RPM secondary HD
Win 7 x 64

I did not update anything since I got my laptop so everything is stock.

I wish I had research more before buying this AMD card or I would easily just drop $300 extra for 680m so I don't have to deal with this problem. Last AMD product for me for sure.

 

Wish I had waited as well. Coming from 8600GT/310M.

I had heard of the ATI driver horror stories. But I was so desperate to get a new laptop. In addition the 7970 stacked up so well versus the 680m. I like many others didn't see the point in paying a premium for such little gain.
It's not a bad piece of hardware. But upgrading drivers shouldn't be such a headache, I've lost count of the uninstall/resinstall/restarts. It's all too much.

 

Ya sadly enough that seems to be the story with AMD all too often: Good hardware crippled by bad software. It is sad, I want to like their stuff, but then crap like this happens.

What makes me even more annoyed isn't just that there has been this big problem, but that they hinted at fixing it but haven't. On various forums there was stuff like "Enduro owners will be happy after 10/22" from AMD resp. Well, no, we won't. We'd be happy if there was an officially supported driver we could download and install without issue. However there's a beta driver, that is buggy, and still doesn't fix the DX9 issues. That is coming Real Soon Now(tm) still.

That annoys me as much as the problem itself. This false projection of "We are going to release a fix soon!" and then not. Look if it isn't ready, just tell us that. Give us a status update that says "Hey we still don't have a fix. We have a fix for some of the problems, but it is still a buggy beta. We'll let you know when it is completely fixed." That is much better, and more professional, than trying to tease about a fix you know isn't coming.

 

Not so complicated, but

-Control panel-> Uninstall AMD Catalyst Install Manager->Express Remove Everything
-Run Driver Sweeper
-Restart.
-Install Intel HD4000 Drivers (for laptops)
-Restart
-Install New 12.11.beta3
-Restart
-Maybe 1 BSOD on boot
-Power off
-Power on.
-Done

 

lol it's a beta, there are going to be issues. there are some reports of crashing, but it's not like it's the majority of people out there. if you want reliable drivers, don't download a beta... period.

anyway, back on topic, I got a few BSODs yesterday while trying to apply an overclock in afterburner, but they stopped after I quit messing with it and reinstalled afterburner. everything has been stable since, and performance is awesome. specs in my sig.

 

Already tried this and BSOD after 3 and 4 restarts.


My specs:

Clevo 150EM

I7 - 3610
7970M
8GB Kingston X 1600
128GB Samsung III
250 HD



When I bought this laptop I decided to invest for amd in case they fix the problem and because I wanted new generation hw. However the 680m was to expensive for me and that was the other reason to go with 7970m. But that doesn't mater any more as amd didn't keep their promise to give us working driver by the end of october.

Installing drivers usually shouldn't be a difficult task neither make you reinstall the whole operation system. Drivers should install with few clicks and one restart however this didn't happened with the new 12.11beta neither with 12.9 beta. Basically these drivers for me didn't work of how it suppose to work.

I won't complain about that as it was my decision to go with 7970m. If they fix it in the future or not that doesn't matter as amd couldn't keep their deadline, that mean I would not go back to a company that can't keep with deadlines.

For now I'll stay with the stock drivers until there is a stable driver, installs without problems and the update system detects it as a new driver. Or just save some money and upgrade next year with something else and throw 7970m in the bin.

About the amd driver division if hey can't test properly driver just don't say yee here is your driver fix. One of the most basic procedure in system building design cycle is to test project (product) for all possible errors, before releasing it.

 

i find out that whenever BSOD happens after reboot, the card fails to switich to idle mode.

 

Any idea why is this happening to handful of people but not all? faulty card?

 

i believe everybody will get a chance to have BSOD just matter of time.

 

yeah, I did great now for 3 days with 12.11 over the top, with stock intel's, but after some frequent unrelated restarts now I'm back to bsod's and reinstalling.... its beta thats for sure...

 

Dude, EXACTLY the same here. 3 days of no BSODs, and now all of a sudden BSODs every other restart. No idea how that happens.

 

I know this suggestion is weird and doesn't make much sense, but humor me and yourself, just try it.

Try going into device manager and then disabling ACPI Battery. It's annoying to have it off, but whatever, may work for you or not. I think it's moronic that the ACPI drivers for Windows 7 are older than Windows Vista and have been updated seems since XP.

You decided to try overclocking I bet and Afterburner is messing it up, with the ULPS disabled. Why that should matter, not sure since ULPS is power management for CFX. But that's my suspicion. Try disabling ACPI battery, let me know if that works. If it does, then, well we can scratch our heads and wonder, what is going on?

 

Nope, I did not try overclocking. The only things I have done include: gaming, web browsing and working on school work. I did install one program last night called the AMD System Monitor, but all that does is record GPU/CPU values. BTW how do you disable ULPS and ACPI?

 

To OC with Afterburner you'll need to disable ULPS:
- Go to start, type in the search regedit
- Search for EnableULPS_NA
- Change the 1 to 0.
- Restart

To disable ACPI Battery
- Go to device manager.
- Batteries, right click ACPI Control Compliant Method and disable it.

This won't disable ACPI while on A/C or Battery. It just stops monitoring for battery. You still have Intel Speedstep and AMD Enduro working.
- Also I found for Afterburner, be sure you are in high performance before using it or it may cause you to get BSOD if you try using it while in power saving mode.

Dunno, all of this is confusing me too.

Let me know if this stops your BSODs. After overclocking a bit, I started getting BSOD too, but since doing above, haven't had em. Knock on wood, but no idea if this is a fix or just coincidence.

 

OK........ This sounds stupid, but on my computer it is fact. I boot with charger -> bsod. I boot on battery - no bsod. EVERY time. Something is up with power management......
My guess - Every BSOD I get states that timeout was reached before the display could be reset. So when I boot from charger the 7970m roars and the timeout is reached before the power management scheme can implement the igpu display and the system shuts down to prevent bad things..... because the 7970 has to pass through the hd 4000...

 

EDIT: Nvm I still get BSOD on next boot.

I wanted to share the fix for the BSODs I was getting. I ran CMD in administrator mode and changed the HPET timing.

TWEAK: Enable HPET (in BIOS and OS) for better performance and FPS - Neowin Forums

1. I installed latest intel, and then latest amd drivers.
2. reset
3. BSOD
4. restart in safe mode
5. do the CMD switch above.
6. reset

 

Is somebody having the same power management problem as me, or am I alone on that one ? Are any of you getting the "display reset timeout" BSOD or do you get other warnings ?

 

I installed the newest intel hd drivers. On power adapter I can hear the 7970m start up at the login- screen, and then the intel hd takes over ......... sometimes. Running restart several times, this is not consistent. sometimes the 7970m powers down like it should, sometimes it doesn't. When it doesn't the desktop hangs almost immediately, and I get the typical bsod with the display driver reset problem....

 

At least I can control the problem now. Turning off catalyst control center in msconfig startup I don't get blue screened anymore, though I would like to know what is happening there.....
It seems that with catalyst control center starting, it has some default power setting connected to one or more services or applications, and those in turn cause the 7970m to turn on maximum performance ??

 

BSOD of death upon reboot and switching between performance modes. Installed from 12.8's.

I don't get why people re-install windows when AMD drivers don't work properly . Its overkill, gonna be forever re-installing.

Anyway back on 12.8 until next round of crud is released