• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Lavalys Everest makes system unstable

A

athlon64X2

Member
I am trying to benchmark my system (built a new one) and am having some trouble. I have loaded Everest just now, and the moment I run Everest, my keyboard and mouse stop communicating with the system.

Both USB and PS2 have been tried out.

What could be the issue?

I flashed the bios yesterday with the latest from the Chaintech website, and reloaded the nForce Nvidia drivers (ver. 36).

Am at a loss here -- cannot think of anything. Until I run Everest, the system works fine. All the other programs/OS work absolutely ok.

Any hints?
 
Not sure, I've been running Everest for 2+ years including the beta samples. I have it on right now. What happens to your cpu usage when you fire up Everest?
 
How long does it freeze up for? When I run Lavalys....and benchmark...My keyboard and cursor freeze's for about 15 second's while benching, then unfreeze's. How long have you waited?
 
Thanks for the prompt responses.

I opened up the task manager and then ran everest. The CPU utilization went up to 50% and in about 3 seconds it came down to 10%. And everything froze.

Nothing on my monitor is getting refreshed. Not even the taskmanager. No activity with the HD. My screen is like a still photo.

I waited at least 3 mins. ANd then reset the system.

🙁
 
I installed the latest NVIDIA chipset drivers, ver 6.66 from Nvidia website. Restarted the machine -- my machine took longer to load Windows XP.

Then I re-ran Everest, only to get new kind of error -- now after running everest, and in about 3 seconds, my monitor went blank --- poof. The monitor light stayed green, which means it was getting a signal. Just that it was not able to display anything on the monitor. Never seen this one before.

Am not aware of how Everest works -- but I have 2 HDs in the machine, one has Windows and the other is just plugged in -- raw --- not formatted. Would this be an issue?

And should I go back to the chipset driver ver 3.6 that came with my MoBo? Or 6.66 should be ok?

Thanks.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top