Time to admit defeat!
Hmm, after a little research it seems you're not the only A8V-VM SE user with this problem.
Many people have similar issues, with games slowing right down or crashing when using this motherboard. It seems to be an issue with the motherboard dramatically throttling (reducing) the CPU speed when the temperature reaches 45-50degrees+. There doesn't seem to be any way of disbling this "feature" in the BIOS either and so far there isn't a solution.
I'll post some links to discussions relating to this that I found on other forums if that's allowed.
Many people have similar issues, with games slowing right down or crashing when using this motherboard. It seems to be an issue with the motherboard dramatically throttling (reducing) the CPU speed when the temperature reaches 45-50degrees+. There doesn't seem to be any way of disbling this "feature" in the BIOS either and so far there isn't a solution.
I'll post some links to discussions relating to this that I found on other forums if that's allowed.
Could you try running with the case open and a desk fan blowing in to see if keeping it cool makes a difference? If it does you would then have a strong case for taking it back to the guy who replaced the MOBO as it is not fit for purpose (unless you specifically asked for that board in which case you may be in a dodgy situation). It might be that the problem could be solved by fitting an extra case fan.
I'd be tempted to download RMClock utility - a nifty app that shows lots of system information and includes the realtime monitoring of CPU throttling.
Info here: http://cpu.rightmark.org/products/rmclock.shtml#rmclock
Download here (first link in the 5th "box" down): http://cpu.rightmark.org/download.shtml
Launch it and click "CPU info" in the left hand pane. The "core clock" and "Throttle" values should be the same, showing the correct operating speed for your CPU.
(Alternatively, you can click on "monitoring" in the left hand pane. You should only see a red line in the graph at the top, a purple line in there indicates your CPU is throttling.)
Next, with the RMCLock utility open, launch a CPU benchmark - preferably one that runs in a window (so you can keep an eye on the RMClock figures while the benchmark is running).
Keep looping the benchmark to get your CPU nice & hot and see if RMClock shows any throttling.
If it does, and your temperatures are within the safe limits of the CPU then you have very good grounds to complain and obtain an alternative motherboard.
Edit:
I've just realised that RMClock can record the monitoring data in a log file. This way, instead of using a windowed benchmark to heat-up your CPU, you can use a game instead (therefore re-creating the original cause of your problem perfectly) and check the results in the log file afterwards (make sure RMClock is running before you start the game though of course
). To enable the logging, in "Settings" tick the "Enable logging of monitoring data" box in the "Logging options section" near the bottom. This will create a text document log in your RMClock program folder.
Info here: http://cpu.rightmark.org/products/rmclock.shtml#rmclock
Download here (first link in the 5th "box" down): http://cpu.rightmark.org/download.shtml
Launch it and click "CPU info" in the left hand pane. The "core clock" and "Throttle" values should be the same, showing the correct operating speed for your CPU.
(Alternatively, you can click on "monitoring" in the left hand pane. You should only see a red line in the graph at the top, a purple line in there indicates your CPU is throttling.)
Next, with the RMCLock utility open, launch a CPU benchmark - preferably one that runs in a window (so you can keep an eye on the RMClock figures while the benchmark is running).
Keep looping the benchmark to get your CPU nice & hot and see if RMClock shows any throttling.
If it does, and your temperatures are within the safe limits of the CPU then you have very good grounds to complain and obtain an alternative motherboard.
Edit:
I've just realised that RMClock can record the monitoring data in a log file. This way, instead of using a windowed benchmark to heat-up your CPU, you can use a game instead (therefore re-creating the original cause of your problem perfectly) and check the results in the log file afterwards (make sure RMClock is running before you start the game though of course
). To enable the logging, in "Settings" tick the "Enable logging of monitoring data" box in the "Logging options section" near the bottom. This will create a text document log in your RMClock program folder.
I already have probe II running and I have been keeping an eye on it - nothing spectacular - highest value 53c and the lowest 34c.
Your right about the NB heatsink having no fan. Its ironic because my last MB failed when the NB fan failed and it fried. That was an ASUS too
I have tried to recreate the crash in normal apps but cant - even with video running.
Your right about the NB heatsink having no fan. Its ironic because my last MB failed when the NB fan failed and it fried. That was an ASUS too
I have tried to recreate the crash in normal apps but cant - even with video running.