If you have a nice chunk of RAM (3GB+) and have enabled memory remapping; you may suddenly find that CrossFire doesn't enable and you just get a hard reset.
Steps to reproduce:
Important! You must have a 64bit OS, and enough memory to require remapping (3GB+).
In the BIOS enable memory remapping, boot into Windows as normal.
Enable CrossFire.
The screen will go blank, and just before reinitialising the display, the computer will hard reset.
As soon as Windows starts up and you login, CrossFire tries to enable and the same issue occurs.
Workaround
Temporary workaround is to disable memory remapping, once CrossFire is successfully enabled, you can reboot and enable remapping again. Unfortunately this isn't paticularly acceptable because it requires no less than two reboots to get CrossFire working with full access to your physical memory. Two more reboots to disable CrossFire too.
If anyone is beta testing for ATI, feel free to pass this info on. For the very few this affects, hopefully this will still let you play around with CrossFire as neccesary
Steps to reproduce:
Important! You must have a 64bit OS, and enough memory to require remapping (3GB+).
In the BIOS enable memory remapping, boot into Windows as normal.
Enable CrossFire.
The screen will go blank, and just before reinitialising the display, the computer will hard reset.
As soon as Windows starts up and you login, CrossFire tries to enable and the same issue occurs.
Workaround
Temporary workaround is to disable memory remapping, once CrossFire is successfully enabled, you can reboot and enable remapping again. Unfortunately this isn't paticularly acceptable because it requires no less than two reboots to get CrossFire working with full access to your physical memory. Two more reboots to disable CrossFire too.
If anyone is beta testing for ATI, feel free to pass this info on. For the very few this affects, hopefully this will still let you play around with CrossFire as neccesary
