So I just noticed this today, but think this might have been going on for a few days. Usually when I'm not playing a game, the clocks are at the P12 state, then when I load up a game, it'll switch over to whatever I have it set at, usually I keep it a mild OC of 750/1800. Now whenever I load up a game, it'll stay at the powered down state and not switch out of it. Does this mean my card is possibly fried?
Yesterday when I was playing Need For Speed World, I was only running at 14 FPS (Usually 60+), but when I played AION, it was back up to it's normal 50 FPS. So I thought perhaps there was some issues with the game. Today I've logged into both, and they are both running on the powered down state.
-
-
What are you temps?
-
Temps are normal. 53C. With a custom fan profile, it's around 34C non gaming.
When I boot up Windows, the clocks are at the powered state. If I use nvidia Inspector and change the clocks, it'll switch for a few min, then switch back. -
The Revelator Notebook Prophet
A few beta drivers have caused 580M's to hang at the P0 (3d) state after the load drops, but I am not aware of the problem carrying over into any WHQL versions. Which drivers are you using?
-
I'm currently on the beta 301.24 driver. I've been running it since release and haven't had any issues with it. I decided to do a clean reinstall and that seems to have fixed the issue.
-
The Revelator Notebook Prophet
Good deal. I've also been using the 301.24 drivers without issue since they were released.
Sudden issue w/ 580M
Discussion in 'Alienware 17 and M17x' started by SkylineLvr, May 13, 2012.