MSI K8T Neo Core Center not working

edem5 · 10-14-2004, 02:42 AM

Hi!,

Has anyone had the issue where the core center software says "hardware not recognized" and then doesn't load on startup? I have all the latest drivers installed and have re-installed them repeatedly.

The strange thing is that if I start core center after startup it loads up just fine.

Any advice? Thanks

Amd_Lover2004 · 10-18-2004, 12:04 AM

no ive never heard of that b4, try contacting MSI, or wait for more advice from these other nice, smart ppl

***Darthtanion*** · 10-18-2004, 11:37 PM

Did you install Windows fresh after changing to this motherboard? It sounds like an issue where the CoreCenter is trying to load before some of the necessary device drivers. I had it running at startup during my testing of this board and never had an issue.

tmessinger · 10-21-2004, 01:03 PM

This has happened to me also. I have two users on my new computer. The first person to log on has the core center working fine. When the second person logs on, they get the error messages and the core center does not load. I have not contacted MSI yet, but I plan to.

edem5 · 10-22-2004, 01:34 PM

Quote:

Originally Posted by Darthtanion

Did you install Windows fresh after changing to this motherboard? It sounds like an issue where the CoreCenter is trying to load before some of the necessary device drivers. I had it running at startup during my testing of this board and never had an issue.

Yes I did and CoreCenter ran just fine. The problem started after I got optimum online and I configured the Realtek gigabit controller to use BIOS startup. Previous to this I was using dial-up.

***Darthtanion*** · 10-22-2004, 07:19 PM

Try removing CoreCenter from the Control Panel and then making sure the folder under Program Files is deleted as well. Reinstall it again and see if this fixes the problem. It might be hacking up a furball because it thinks you're using two different Internet connections. Don't know why this might be an issue, but with the new hardware addition you did, this might be worth a shot.

edem5 · 10-23-2004, 12:00 PM

Quote:

Originally Posted by Darthtanion

Try removing CoreCenter from the Control Panel and then making sure the folder under Program Files is deleted as well. Reinstall it again and see if this fixes the problem. It might be hacking up a furball because it thinks you're using two different Internet connections. Don't know why this might be an issue, but with the new hardware addition you did, this might be worth a shot.

That didn't work but STRANGELY something else did. I created a network bridge between the 2 1394 connections, rebooted, had startup problems, deleted the network bridge, rebooted, and now Corecenter is starting up correctly!

Thanks for your feedback.

edem5 · 10-23-2004, 12:05 PM

Quote:

Originally Posted by edem5

That didn't work but STRANGELY something else did. I created a network bridge between the 2 1394 connections, rebooted, had startup problems, deleted the network bridge, rebooted, and now Corecenter is starting up correctly!

Thanks for your feedback.

Nope I was wrong. It worked once just to screw with my head and now it's saying "hardware monitor not loaded" again before saying that "core center does not support your motherboard". Yet when I start corecenter after startup everything is fine.

londonsam · 10-25-2004, 06:05 PM

Has anyone figured this one out?

I am having the same problem. If i log on as a user i get errors and core centre wont run leaving my cpu fan running double time.
If i log in as an administrator core centre starts up and my fan works ok.
Any ideas??

edem5 · 10-26-2004, 08:58 AM

Quote:

Originally Posted by edem5

Nope I was wrong. It worked once just to screw with my head and now it's saying "hardware monitor not loaded" again before saying that "core center does not support your motherboard". Yet when I start corecenter after startup everything is fine.

Okay! I dropped the overclocking from Colonel (7%) to Captain (5%) and it seems to be OK now. It used to work just fine at Colonel, I'll probably never know why I had to drop to captain.