Bitcoin Forum

Alternate cryptocurrencies => Mining (Altcoins) => Topic started by: pornluver on April 27, 2017, 02:51:47 PM



Title: One of my card requires unusually high voltage
Post by: pornluver on April 27, 2017, 02:51:47 PM
https://i.stack.imgur.com/m7dHO.png

This is the default settings.

Most other cards I can undervolt to 910 volt

This card requires 930 mv

Not only that,

I wonder what is P1, P2, P3, P4, p5, p6 and P7?

It seems that the only things that matter is P7 right?

If I change value of P2 - P6 my rig crash

After that the radeon settings is "restored"

However, I wonder what's exactly going wrong?

What should I do? Check event viewer in windows? what?

This is the setting that's stable. However, as you see from screen shot, things are strange for P2 - P6.
https://i.stack.imgur.com/TOLi7.png

If I use this settings instead

It'll crash

https://i.stack.imgur.com/s2sN5.jpg





Title: Re: One of my card requires unusually high voltage
Post by: cptfisher on April 27, 2017, 03:02:31 PM
p1 - 7 are the power state... according to the work load cards change frequency and the voltage... you dont have to modify the voltage but better give a voltage offset. NOT EVERY CARD OF THE SAME KIND REQUIRES SAME VOLTAGE


Title: Re: One of my card requires unusually high voltage
Post by: pornluver on April 27, 2017, 03:12:15 PM
p1 - 7 are the power state... according to the work load cards change frequency and the voltage... you dont have to modify the voltage but better give a voltage offset. NOT EVERY CARD OF THE SAME KIND REQUIRES SAME VOLTAGE

What is power state? When does the program decide that it should enter one state and not the other? By GPU load?

What is a voltage offset? Why it's better to give a voltage offset than to modify the voltage directly?

I am aware that different cards require different voltages.

I check windows viewer I see
Code:
Display driver amdkmdap stopped responding and has successfully recovered.

followed by

Code:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000116 (0xffffb18cea2224a0, 0xfffff804149ced90, 0x0000000000000000, 0x000000000000000d). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: cde01c63-3a2f-4b5b-8df0-01f17762de4d.