Z87-G43, MSI Command Center will not start.

Board: MSI Z87-G43
Bios: Version 1.5
VGA: EVGA GTX 770 SC
PSU: Rosewill Capstone 650
Intel Core i5-4670k (stock)
MEM: Crucial Ballistic Sport 8gb 2x 4gb
SSD: Kingston HyperX 120gb
COOLER: Cooler Master Hyper 212 EVo
OS: Windows 8.1
Command Center works on the main Windows account that I created when I installed Windows 8.1. I did not like having a Windows user account that was online all the time so I created an offline Administrator account.
Command Center freezes as it is trying to load on the offline user account and I have no idea why. When I ran Command Center the first time on my main user account(online), a window popped up I think it was for a .NET installation?
I did not get that window on the offline account. I know the solution has got to be simple and stupid. Just lost at what it is.
I have uninstalled and reinstalled Command Center on the the offline account and it still will not work. Still freezes as it's trying to load.

I know this is a little late, but I had the same issue with the same board. I discovered that it must have the "m" driver installed first or something similar, first, before it will work correctly. It states this in the download center (look there and it will have the correct information) but it's easy to get those two pieces of software and information about it separated. I hope this helps someone.

Similar Messages

Z87 MPower Max Command Center Hang on Start

Yes, yet another thread on this issue. My situation is slightly different than the other threads.
System
MSI MPower Max Z87 motherboard
i7-4770k
32GB G Skill 2400 RAM
Intel 335 Series 180GB SSD
2X BFG 260 GTX graphics cards in SLI
Windows 7 Professional x64
BIOS V1.3
Background
I assembled my system this past Saturday. I installed the latest drivers from the MSI web site and ran the auto update application which updated a few drivers that appear to not be available for download directly from the site. I also installed all the 250+ latest updates for Windows 7.
After installing and updating the drivers, OS and MSI applications Command Center worked. I even used the OC Genie in Command Center just to give it a try. I turned the OC Genie off, restarted then decided to play around with the RAM disk. This is when things started to go wrong.
At first, the RAM disk worked great. I got incredible performance using a 16 GB RAM disk when I loaded games on it. I set a backup file for the RAM disk and for it to backup during shutdown and every 30 minutes. The next time I restarted I noticed that the software that I set to auto-load to the RAM disk was not there. Command Center failed to start so I could not change any of the settings. I rebooted a couple times to try to get into Command Center and could not get back in. The RAM disk was still being set at boot so half of my RAM was used by the RAM disk whether I wanted it or not. I uninstalled Command Center to get rid of the RAM disk. That worked as the RAM disk was gone when I rebooted. I reinstalled Command Center but it still fails to start.
I am guessing that there must be some registry entries that are causing Command Center to hang. It does not make any sense that a new installation of Command Center should hang when the previous version was working.
Are there any registry changes that I need to find to "fix" this problem?

No luck with the reinstall. Looks like it might be .NET related. I have a feeling that a recent .NET patch might have broken something.
Here are two errors in the application event log:
Log Name: Application
Source: .NET Runtime
Date: 9/16/2013 5:52:03 PM
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Pile
Description:
Application: CommandCenter.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Windows.Markup.XamlParseExceptio n
Stack:
at System.Windows.Markup.XamlReader.Rewrap Exception(System.Exception, System.Xaml.IXamlLineInfo, System.Uri)
at System.Windows.Markup.WpfXamlLoader.Loa d(System.Xaml.XamlReader, System.Xaml.IXamlObjectWriterFactory, Boolean, System.Object, System.Xaml.XamlObjectWriterSettings, System.Uri)
at System.Windows.Markup.WpfXamlLoader.Loa dBaml(System.Xaml.XamlReader, Boolean, System.Object, System.Xaml.Permissions.XamlAccessLevel, System.Uri)
at System.Windows.Markup.XamlReader.LoadBa ml(System.IO.Stream, System.Windows.Markup.ParserContext, System.Object, Boolean)
at System.Windows.Application.LoadBamlStre amWithSyncInfo(System.IO.Stream, System.Windows.Markup.ParserContext)
at System.Windows.Application.LoadComponen t(System.Uri, Boolean)
at System.Windows.Application.DoStartup()
at System.Windows.Application.<.ctor>b__1(System.Object)
at System.Windows.Threading.ExceptionWrapp er.InternalRealCall(System.Delegate, System.Object, Int32)
at MS.Internal.Threading.ExceptionFilterHe lper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOper ation.InvokeImpl()
at System.Windows.Threading.DispatcherOper ation.InvokeInSecurityContext(System.Object)
at System.Threading.ExecutionContext.runTr yCode(System.Object)
at System.Runtime.CompilerServices.Runtime Helpers.ExecuteCodeWithGuaranteedCleanu p(TryCode, CleanupCode, System.Object)
at System.Threading.ExecutionContext.RunIn ternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOper ation.Invoke()
at System.Windows.Threading.Dispatcher.Pro cessQueue()
at System.Windows.Threading.Dispatcher.Wnd ProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbac kOperation(System.Object)
at System.Windows.Threading.ExceptionWrapp er.InternalRealCall(System.Delegate, System.Object, Int32)
at MS.Internal.Threading.ExceptionFilterHe lper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.Inv okeImpl(System.Windows.Threading.DispatcherPrio rity, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMe ssage(System.Windows.Interop.MSG ByRef)
at System.Windows.Threading.Dispatcher.Pus hFrameImpl(System.Windows.Threading.DispatcherFram e)
at System.Windows.Threading.Dispatcher.Pus hFrame(System.Windows.Threading.DispatcherFram e)
at System.Windows.Application.RunDispatche r(System.Object)
at System.Windows.Application.RunInternal(System.Windows.Window)
at System.Windows.Application.Run(System.Windows.Window)
at CommandCenter.App.Main()
Log Name: Application
Source: Application Error
Date: 9/16/2013 5:52:04 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Pile
Description:
Faulting application name: CommandCenter.exe, version: 1.0.0.18, time stamp: 0x51e788d9
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18229, time stamp: 0x51fb1116
Exception code: 0xe0434352
Fault offset: 0x0000c41f
Faulting process id: 0x1730
Faulting application start time: 0x01ceb3401a956d4d
Faulting application path: C:\Program Files (x86)\MSI\CommandCenter\CommandCenter.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: 5dfc47d6-1f33-11e3-8a76-6817295a6e86

MSI Gaming App Will NOT Start

If this is the wrong forum I apologize, I didn't see any other place for topics about MSI software.
When my PC starts, the MSI Gaming App doesn't start automatically, I have to manually start it by double-clicking the icon on the desktop. However, it is a crap shoot if the program will even run; usually it doesn't and I have to completely restart my computer and cross my fingers. I've re-installed, updated, etc., but it keeps doing this. Any help would be fantastic.
Specs: Windows 7 Professional 64-bit, 14GB G.Skill RipjawsX DDR3, i5 2500K @ 4.5GHz, MSI GTX760 2GB OC Gaming Edition

Hi
Quote from: MysticDaedra on 10-April-15, 03:07:13
Specs: Windows 7 Professional 64-bit, 14GB G.Skill RipjawsX DDR3, i5 2500K @ 4.5GHz, MSI GTX760 2GB OC Gaming Edition
Are you mixing RAM?
Did the software ever worked before? Try to uninstall it (Programs&Features), remove any folders and registry files that Gaming App have made (you can also use CCleaner to clear registry errors). Then reboot and try to install+run Gaming App again. What was the version you have tried? From the CD included with the card or from MSI website? If possible, tell exact version.

MSI Gaming app will not start up or run

I just installed a new MSI GTX 960 Gaming 4G and also installed the MSI gaming app. When I click on the app to open it appears in my notification window, but as soon as I mouse over the icon it disappears. The app stops running. I have uninstalled and re-installed like 12 times and restarted the computer 15 times. I'm kind of a noob when it comes to using new stuff so any help would be nice. Thanks

It's an issue with Gaming APP that is currently not fixed. Open a ticket with MSI support to add more cases for MSI to check and find the problem: >>How to contact MSI.<<

MOVED: MSI Gaming App Will NOT Start

This topic has been moved to GAMING Graphics Cards.
https://forum-en.msi.com/index.php?topic=254732.0

Hi
Quote from: MysticDaedra on 10-April-15, 03:07:13
Specs: Windows 7 Professional 64-bit, 14GB G.Skill RipjawsX DDR3, i5 2500K @ 4.5GHz, MSI GTX760 2GB OC Gaming Edition
Are you mixing RAM?
Did the software ever worked before? Try to uninstall it (Programs&Features), remove any folders and registry files that Gaming App have made (you can also use CCleaner to clear registry errors). Then reboot and try to install+run Gaming App again. What was the version you have tried? From the CD included with the card or from MSI website? If possible, tell exact version.

HT4972 my ipad will not start it has an apple in the center and no matter what I do it will not dispeasr, erase or open

MY ipad will not start. I can only see an apple in the center.

Have you tried this?
Reboot the iPad by holding down on the sleep and home buttons at the same time for about 10-15 seconds until the Apple Logo appears - ignore the red slider - let go of the buttons.

Mac book pro (2008)will not start up,command-v gives (error) Import:Importer start failed for 89(kr:268435459)invalid destination port)

will not start up.
tried Command-v
message reads
(error) Import:Importer start failed for 89 (kr:268435459)invalid destination port)

First, uninstall "SuperTV" (whatever that is) according to the developer's instructions. It isn't working and it's filling the log with noise.
If you have more than one user account, these instructions must be carried out as an administrator.
Launch the Console application.
Step 1
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left.
Enter "BOOT_TIME" (without the quotes) in the search box. Note the timestamps of those log messages, which refer to the times when the system was booted. Now clear the search box and scroll back in the log to the last boot time when you had the problem. Post the messages logged before the boot, while the system was unresponsive or was failing to shut down. Please include the BOOT_TIME message at the end of the log extract.
Post the log text, please, not a screenshot. If there are runs of repeated messages, post only one example of each. Don’t post many repetitions of the same message. When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.
PLEASE DO NOT INDISCRIMINATELY DUMP THOUSANDS OF LINES FROM THE LOG INTO A MESSAGE. If you do that, I will not respond.
Important: Some private information, such as your name, may appear in the log. Edit it out by search-and-replace in a text editor before posting.
Step 2
Still in Console, look under System Diagnostic Reports for crash or panic logs, and post the most recent one, if any. In the interest of privacy, I suggest you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if present (it may not be.) Please don’t post shutdownStall, spin, or hang logs — they're very long and not helpful.

HT1349 My ipad will not start up, it has the swirl in the center of the screen and has been there for 30hrs now.

My ipad will not start up, it has the swirl in the center of the screen and has been there for 30hrs now, what can I do?

First thing to try is a reboot of your iPad. Press and hold the Home and Sleep buttons simultaneously ignoring the red slider until the Apple logo appears. Let go of the buttons and let the iPad restart. See if that fixes your problem.

P67A-G43 (B3) and iPhone App 'MSI Command Center'

Hey guys,
This is my first post here, I did a little bit of searching but haven't come up with any info.
I downloaded the MSI Command Center app to my phone, and wanted to use it with my board P67A-G43 (B3). The app states that I should have Control Center 2.5.014+ installed on my computer, but then when I search on the MSI website for the latest version of Control Center for my board, it tells me 2.2.097 is the latest.
Is CC 2.5 compatible with my board, and is my board compatible with the app?

I couldn't find that version anywhere and as no one else has answered this and I have no idea, it is best to contact msi.
Sorry.
>>How to contact MSI.<<

MSI Command Center and OC Genie

I have an issue with the MSI command center. I know very little about overclocking and that's why i use the command center with OC Genie. Oc Genie raised my CPU to 4.10GHz and ram to 1600(was 1333). Everything went fine until about 30 minutes of game play where i kept on getting a blue screen. Did some searching and found out that it was because of the CPU Core Voltage. My CPU Core Voltage was 1.1 and changed it to 1.2 using MSI Command Center. It was fine the whole day/week. The issue is that the voltage never saves after each restart of the computer. I have to manually change the voltage each time i power on my computer. I tried to save/apply the voltage but it doesn't seem to save. Any idea how to fix this?
i7-4770K @ 3.50 (4.10GHz)
Z87-G43 Gaming MB
2x2GB 1333 (1600)
Geforce 650 ti boost 2gb
CX500 Power Supply

Dont use Command Center for OC. Use BIOS settings.
If you're not pro (or proper user) OC just a bit the multiplier in the BIOS. Software FAILS

After removing system fonts and reinstalling fonts, FireFox will not start

After removing system fonts and reinstalling fonts, FireFox will not start! When I start FireFox the "Mozilla Crash Reporter" opens as if FF just crashed??? I don't see any records in event viewer. I am using FF v3.6.3 on a Windows 7 box. I tried uninstalling 3.6.3 and installing 3.0.18 and had the same problem!
== This happened ==
Every time Firefox opened
== After a uninstalled all fonts including system fonts and then reinstalling system fonts. ==
== User Agent ==
Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; GTB6.4; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; AskTB5.5)

The files with submitted crash report ids are inside the ''submitted '' directory, from the directory you found the LastCrash.txt timestamp file.
The file names will begin with '''bp-'''
There might be more information from the crash report, but it might just tell us you are crashing the first time Firefox tries to use a font.
One thing I suppose you could do is select only those fonts you've got in Tools -> Options -> Content -> Fonts and Colors -> Advanced and then uncheck the '''Allow pages to use their own fonts''' option.
See http://support.mozilla.com/en-US/kb/Options+window+-+Content+panel#Fonts_Dialog
To be honest, I can't find anything on this Netscape Font Navigator and it sounds highly dubious.

Also got an issue with MSI command center, maybe windows is to blame?

MSI Command Center crashes every time after it's been running a little while, googling it I've noticed there have been a lot of topics about it crashing. I think someone here on this forum suggested reinstalling windows might help :/ Not too keen on that but better now than when I've installed a ton of stuff on the PC.
Actually both MSI command center and Intel extreme tuning utility crash for me. MSI command center crashes after a while it's been running and Intel extreme tuning utility crashes every time I click on the settings menu.
I wonder if something is still wrong with my OS, first time I installed windows 8.1 games crashed if they ran in fullscreen but ran fine in windowed mode. Later after reinstalling widows games started working fine, in fact I haven't had any crashes since (other than from these 2 programs).
Just yesterday I decided to make a bootable USB drive for windows 8.1 and I noticed that my PCcouldn't actually create an ISO from the windows CD cause the DVD drive couldn't read it properly no matter how many times I tried. My other PC managed to read the Windows DVD just fine, so managed to make a bootable USB drive after all. Donno how it managed to install windows at all, it did struggle a bit.
I wonder if doing a repair install or a completely fresh install of Windows now when my PC can actually read the windows installation media properly would fix these last issues.
Is there a difference between a clean install of windows and an install where it keeps all settings and programs? Think reinstalling windows a 3rd time would help (3rd time is the charm right?) Think reinstalling windows again would help?
Application: CommandCenter.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ArgumentOutOfRangeException
Stack:
at System.ThrowHelper.ThrowArgumentOutOfRa ngeException()
at CommandCenter.Toolkit.CPUFrequency.<Timer_AnimationShowHW>b__0()
at System.Windows.Threading.ExceptionWrapp er.InternalRealCall(System.Delegate, System.Object, Int32)
at MS.Internal.Threading.ExceptionFilterHe lper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOper ation.InvokeImpl()
at System.Windows.Threading.DispatcherOper ation.InvokeInSecurityContext(System.Object)
at System.Threading.ExecutionContext.RunIn ternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOper ation.Invoke()
at System.Windows.Threading.Dispatcher.Pro cessQueue()
at System.Windows.Threading.Dispatcher.Wnd ProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbac kOperation(System.Object)
at System.Windows.Threading.ExceptionWrapp er.InternalRealCall(System.Delegate, System.Object, Int32)
at MS.Internal.Threading.ExceptionFilterHe lper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.Leg acyInvokeImpl(System.Windows.Threading.DispatcherPrio rity, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMe ssage(System.Windows.Interop.MSG ByRef)
at System.Windows.Threading.Dispatcher.Pus hFrameImpl(System.Windows.Threading.DispatcherFram e)
at System.Windows.Threading.Dispatcher.Pus hFrame(System.Windows.Threading.DispatcherFram e)
at System.Windows.Threading.Dispatcher.Run()
at System.Windows.Application.RunDispatche r(System.Object)
at System.Windows.Application.RunInternal(System.Windows.Window)
at System.Windows.Application.Run(System.Windows.Window)
at CommandCenter.App.Main()
Faulting application name: CommandCenter.exe, version: 1.0.0.82, time stamp: 0x542c7911
Faulting module name: KERNELBASE.dll, version: 6.3.9600.17055, time stamp: 0x532943a3
Exception code: 0xe0434352
Fault offset: 0x00011d4d
Faulting process ID: 0x1764
Faulting application start time: 0x01cfe0e065a99cf3
Faulting application path: C:\Program Files (x86)\MSI\Command Center\CommandCenter.exe
Faulting module path: C:\Windows\SYSTEM32\KERNELBASE.dll
Report ID: 6fe5aaa5-4cd6-11e4-8264-448a5b9f9b8d
Faulting package full name:
Faulting package-relative application ID:

This issue isn't super important but I don't like programs crashing. None of the games I've played so far crash. (after I reinstalled windows once) Windows never crashes, and the PC has never crashed either so far.
Both MSI command center (version 1.0.0.82) and intel extreme tuning utility (version 5.1.0.23) crash. Both are kinda same type of programs it seems. MSI CC crashes sometimes immediately sometimes 15 minutes after I start it. The intel program crashes every time I click on the settings menu. MSI CC gives those errors when it crashes, the Intel program has no errors recorded in the event viewer when it crashes.
Board: MSI Z97 Gaming 5
Bios: Version 1.0 (Well that's what CPU-Z says it is)
VGA: MSI GTX 970 Gaming 4g
PSU: Asus 850W CP-850
Intel Core i5-4670K Haswell 3.4GHz (3.8GHz Turbo Boost)
MEM: Kingston HyperX Fury 1866Mhz DDR3
SSD: Crucial MX100 256Gb
HDD: Seagate Barracuda 2Tb
COOLER: Noctua nh-d15
OC: Everything stock (for now)
OS: Windows 8.1 64bit
I tried reinstalling windows by keeping all applications and settings, that didn't help at all. I could still do a fresh windows 8.1 install and remove everything, still I'd rather avoid doing that if I can. Maybe I'll just ignore the errors. Perhaps it's something related to the motherboard since both are these sort of OCing software.

Mac crash; recovery will not start

Yesterday my Mac suddenly crashed into a screen with blue (and white) lines. It wouldn't respond to anything, so I powered it down and tried to boot again. However, it will not boot. It will show the Apple logo, request my password and after a while (with the Apple logo and the spinning wheel) it just shows a blank screen (grey), while the CPU fans are spinning like crazy.Sometimes will it not even get this far and stop doing anything before requesting the password. The guest mode has the same problem.
I basically tried everything to fix it; the recovery option will also show the blank grey screen but nothing else (even after 30 minutes); the internet recovery downloads fine and then pulls the same stunt, so even the recovery will not work. I've tried save mode, which cannot start up (Filevault is activated) and seems to end mid-way through. Sometimes the safe mode crashes immediately after the boot starts with a kernel panic (/sbin/launchd failed, errno 2); after resetting the NVRAM it won't panic.
I've checked the hardware (T startup option, full check), which al seems to be OK. SMART status from the harddrive looks OK (checked with DiskWarrior). Starting in single user mode sometimes gets me through the password request screen and allows me to check the hard drive (fsck -fy). This seems to change permissions, however, after a reboot or exit command, the problem persists and starting up in single user mode and performing the fsck -fy command again seems to fix some issues. When I enter the exit command in safe mode, it'll start up fine, but when the graphic user interface starts, it'll give me the grey screen again (so a blank screen, while the CPU fans are at full power).
Does anyone have any idea what I can do to fix this? Since even the recovery will not start (and neither will the internet recovery), I've got no clue what to do to fix this issue...

Your comment about the "blue and white lines" has me wondering. You say you have a fairly recent MacBook Pro, correct? If that is the case, you probably have a model which has both discrete and integrated GPUs. It is possible that your discrete GPU has failed, and whenever the OS is trying to switch to it is when your system just "hangs" (because the GPU has failed). It all works properly as long as it is on the integrated GPU, but when something causes it to switch it hits the bad GPU and locks.
I would suggest that you make an appointment at your nearest Apple Store to have the specialists at the Genius Bar take a look at it for you. If you are still under the 1 year warranty (or extended Apple Care if you purchased it) then any needed hardware repairs would be free, unless it is due to accidental damage such as a spill in the keyboard, etc.
If you don't have access to an Authorized Apple Service Center, and you do have access to another Mac, you could try making an external boot drive on the other Mac, then install the app "gfxCardStatus" on that MacOS instance (when booted from the external drive). While still booted from the external drive, use the gfxCardStatus app to force the Mac to only use the integrated GPU then shutdown and boot your "dead" Mac from that drive. If it boots and runs, now, try to change the external drive to force to use only the discrete GPU then see how your system boots. If your system, will fully boot using one or the other, then it seems that your problem is probably related to one of your GPUs. It could be a hardware failure, or it could be a corrupted driver. If your system won't boot from either GPU, then my guess about it being a GPU issue is probably wrong.

Vcore Warning in MSI Command Center.

I tried using the OC genie on my MSI z87-g55 to try and run Dragon Age: Inquisition a little better, but didn't like the results and the strain (I think) it put on my comp. The reason I say strain is because in MSI command center I got a warning message that said "Vcore 1.776V" got a bit scared so I turn OC genie off... But yet I am still getting the warning in MSI CC.
here's a screen shot of it:
Here's my comp Info too:
OS Name   Microsoft Windows 8.1
Version   6.3.9600 Build 9600
Other OS Description    Not Available
OS Manufacturer   Microsoft Corporation
System Name   VINNIESRIG
System Manufacturer   MSI
System Model   MS-7821
System Type   x64-based PC
System SKU   To be filled by O.E.M.
Processor   Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz, 3201 Mhz, 4 Core(s), 4 Logical Processor(s)
BIOS Version/Date   American Megatrends Inc. V10.7, 7/19/2014
SMBIOS Version   2.8
Embedded Controller Version   255.255
BIOS Mode   Legacy
BaseBoard Manufacturer   MSI
BaseBoard Model   Not Available
BaseBoard Name   Base Board
Platform Role   Desktop
Secure Boot State   Unsupported
PCR7 Configuration   Binding Not Possible
Windows Directory   C:\Windows
System Directory   C:\Windows\system32
Boot Device   \Device\HarddiskVolume1
Locale   United States
Hardware Abstraction Layer   Version = "6.3.9600.17196"
User Name   VinniesRig\VINNIESRIG\Vincent
Time Zone   Eastern Standard Time
Installed Physical Memory (RAM)   32.0 GB
Total Physical Memory   31.9 GB
Available Physical Memory   29.3 GB
Total Virtual Memory   36.7 GB
Available Virtual Memory   33.7 GB
Page File Space   4.75 GB
Page File   C:\pagefile.sys
Hyper-V - VM Monitor Mode Extensions   Yes
Hyper-V - Second Level Address Translation Extensions   Yes
Hyper-V - Virtualization Enabled in Firmware   Yes
Hyper-V - Data Execution Protection   Yes
I am also use a NVIDIA GeForce GTX 650 Ti graphics card.

under bios, does your Vcore still shows 1.7v? how about the vcore shown in Command center?
If problem persist, try to install the latest command center ?

Using msi command center vs bios to get 4.5

i7 4770k / 8 gig 1866 ram / msi z87 gd45 / 650 W psu / gtx 760 ...
going through bios setting for 4500 MHz I need to boost the cpu voltage to 1.25 + ( exact number I forget ) but... This is needed to even boot and run ...
However ,
if I boot to 4400 MHz I have the voltage to 1.050 and the machine boots and runs like a champ. (tech yes city video I saw and used those settings )
THEN if I go through the msi command center I can bump the cpu to 45 and keep the cpu voltage at 1.050 and it remains running strong and plays the games I play
without any issues.
just an observation but am happy I noticed this . now I can say I can run at 4.5

Quote from: not2intel on 26-April-14, 06:37:32
well , may have spoken too soon . tonight it didn't like the cpu boost without the voltage increase...
definately 4.4 on 1.050 works with everything thrown at it.
the 4.5 on 1.05 looks like it needs the voltage jump. ( for the .1 it's not worth it in my eyes to push more voltage to get that lil gain )
Yup! Wise decision!

Z87-G43, MSI Command Center will not start.

Similar Messages

Maybe you are looking for