Horize/Clevo P150EM + 7970M + AMD Catalyst Mobility 13.5/6 beta BSOD IRQL_NOT_LESS_OR EQUAL

Howdy all,

I understand that there is another thread for the general discussion of the beta driver release, however I felt that it was appropriate to create a new thread as I'm having a rather specific issue.

Some days ago, I attempted to install the Catalyst Mobility 13.6 beta driver for my Horize/Clevo P150EM using a AMD 7970M. The driver installed fine and I could see no visible issues when playing a game - however, upon closing the notebook lid/screen and reopening it, I was met with a BSOD that stated IRQL_NOT_LESS_OR_EQUAL.

Now, I've been able to replicate the issue several times without fail on both the 13.5 and 13.6 drivers, but everything works dandy on the 13.4 WHQL drivers.

I'm wondering if anyone else here has had the same issue and/or if they've been able to replicate it.

Unfortunately I can't seem to driver sweep my system as I return an endless BSOD after windows loading but that an entirely different issue.

 

I think problem in Wi-Fi driver compatibility , you got Realtek 8188CE?

 

Nah, device manager lists RTL8723AE.

 

anyway try to update realtek wi-fi driver , latest on station-drivers.com

 

Yes could be WiFi. I get the same bsod and message when trying to connect to my phones network. I haven't bothered solving it though.

 

Still Realtek so it's very possible. If it only occurs on particular CCC versions then it's probably not a memory problem, but you can run MemTest86+ if you haven't already, just to rule it out.

 

Sorry for the thread necromancy, guys.

Last night I performed a clean installation of my operating system to see if the issue would desist, and I'm fairly sure it has. I'm able to close my notebook lid on default power settings and on the CCC 13.6 Beta 2 drivers without it BSOD'ing. One thing that I did differently this time around is that I didn't install the 'LENOVO THINKPAD 1080x1920 DISPLAY" optional update from Windows updates, which leads me to think that was causing a conflict between the AMD drivers.

I'm *also* hoping that the "Driver has crashed and recovered" messages will stop due to this. While I have a hunch, I can't prove that Lenovo driver was responsible for it.

 

Thanks for following up, hyp3erstrike! That Lenovo software update via Windows update could have very well been a conflict. Glad things are looking good now. :thumbsup: