The MSI Neo2 Platinum Owners Help Thread
- Thread starter derthballs
- Start date
- have now 
Associate
- Joined
- 16 Aug 2004
- Posts
- 732
- Location
- Bury
what have you got the venice upto Topitoff?
CaNNoN_1981 said:
System:
3000 Venice + freezer 64: 2 x 256mb Mushkin v2 TCCD : Neo 2 : ATI 9600XT
ATM I'm at 270 x 9 2.43Hz HTx3 @ 1.5v set and 1.41v readback
RAM @ 2.5-3-3-7 1T @ 2.65v on 1:1 divider
It's b.. hot today cpu idle temp 36C on load 48C (yesterday 31 and 43).
Have not yet found point at which RAM fails memtest.
System cycling benchmarks and OK.
Impressed that the 9600XT @stock gets over 15k in 3D2k1 and 4100 in 3d2k3.
When I've max'd it out, I will probably treat it to more RAM and a better gfx
T
This is now faster than I can get from my 3500 winnie
Now at 275 x 9 2.5GHz: Stopping here now, will push it further when it is a bit cooler
Last edited:
Associate
- Joined
- 26 Jan 2005
- Posts
- 116
- Location
- Glezga
I took the advice on this post for the PSU and I can say that so far I am well happy with it. MAllen I think it was, thumbs up though to everyone whos 2 bob made a difference.
Its a Tagan 480W, however it has PCI Express GFX power adapters whilst I am still AGP! Good news for me in the future then, as long as they don't change it again!
Finally an MS-7025 that doesn't appear to have any issues, 3rd time lucky I guess!
I'm gonna burn it in for a few weeks then take the plunge in OCing it so I will return for info if I get stuck! Plus I will let ppl know how how far I can push the 'enhanced' Winchester core, ie week 9 2005.
Its a Tagan 480W, however it has PCI Express GFX power adapters whilst I am still AGP! Good news for me in the future then, as long as they don't change it again!
Finally an MS-7025 that doesn't appear to have any issues, 3rd time lucky I guess!
I'm gonna burn it in for a few weeks then take the plunge in OCing it so I will return for info if I get stuck! Plus I will let ppl know how how far I can push the 'enhanced' Winchester core, ie week 9 2005.
Associate
- Joined
- 26 Jan 2005
- Posts
- 116
- Location
- Glezga
AARRRGH!
MSI K8N Neo2 Platinum and Creative Audigy2.
Trying to install the latest EAX4 driver to experience DoomIII with uber surround (apparently) but the installation tells me there is no product installed in my system!
Please help as this is a MSI board issue as the card installed fine on another PC.
MSI K8N Neo2 Platinum and Creative Audigy2.
Trying to install the latest EAX4 driver to experience DoomIII with uber surround (apparently) but the installation tells me there is no product installed in my system!
Please help as this is a MSI board issue as the card installed fine on another PC.
U need to give us more details..... i.e. what other cards do you have in that system?
Suggestions to try.....
1\ Is onboard audio definately disabled?
2\ Try it in a different PCI slot.
3\ Try removing other PCI cards that may be installed.
4\ Swear loudly at how badly Creative do their drivers....
5\ Does it get detected at boot time. i.e. turn on the full diagnostics screen and then let me know if there is an IRQ allocated to the sound or multimedia device. (The last bit of black and white screen before the XP logo. You may need to hit the Pause button to see it. Or stick a dud floppy in so it fails to boot to OS)
6\ Have IRQs been allocated to it in Windoze? Bring up Device Manager and Change the view to "Recources by Type". Open the list of "IRQs". List them on this page to let us know if anything is clashing. Try shuffliing the card to another PCI slot to stop it sharing with anything else.
7\ What USB devices do you have plugged in? Unplug them or try in a different set of sockets. Could be clashing IRQs.
Suggestions to try.....
1\ Is onboard audio definately disabled?
2\ Try it in a different PCI slot.
3\ Try removing other PCI cards that may be installed.
4\ Swear loudly at how badly Creative do their drivers....
5\ Does it get detected at boot time. i.e. turn on the full diagnostics screen and then let me know if there is an IRQ allocated to the sound or multimedia device. (The last bit of black and white screen before the XP logo. You may need to hit the Pause button to see it. Or stick a dud floppy in so it fails to boot to OS)
6\ Have IRQs been allocated to it in Windoze? Bring up Device Manager and Change the view to "Recources by Type". Open the list of "IRQs". List them on this page to let us know if anything is clashing. Try shuffliing the card to another PCI slot to stop it sharing with anything else.
7\ What USB devices do you have plugged in? Unplug them or try in a different set of sockets. Could be clashing IRQs.
Associate
- Joined
- 26 Jan 2005
- Posts
- 116
- Location
- Glezga
Apologies!
I wasn't clear enough in my previous post. BTW, I'm using the 1.8 BIOS.
I can get the web updates that take the driver from the installed 1.80.11 up to 1.80.40, then up to 1.80.50 but even though its detected fine, the 1.80.55 driver fails to see the card during installation.
One thing to note is the driver says Audigy2 ZS in the dialog box even though its a vanilla SB0240 Audigy2 I'm using, so I wondered if the auto update feature was misdetecting the card. So, I uninstalled and reinstalled the Creative suite and got the 2 updates, as previously mentioned, then downloaded the other one manually, but the EXACT same thing occurs.
I've contacted Creative, so I expect an answer sometime tomorrow. I was just curious if anyone else had a similar issue with a resolution to it. As for changing the slot, its not exactly viable due to the airflow restrictions it would impose on my GeForce 6800 with Zalman VF-700 and, as far as I'm aware and this forum, you can't install it in the very bottom orange slot as its configured differently??
I wasn't clear enough in my previous post. BTW, I'm using the 1.8 BIOS.
I can get the web updates that take the driver from the installed 1.80.11 up to 1.80.40, then up to 1.80.50 but even though its detected fine, the 1.80.55 driver fails to see the card during installation.
One thing to note is the driver says Audigy2 ZS in the dialog box even though its a vanilla SB0240 Audigy2 I'm using, so I wondered if the auto update feature was misdetecting the card. So, I uninstalled and reinstalled the Creative suite and got the 2 updates, as previously mentioned, then downloaded the other one manually, but the EXACT same thing occurs.
I've contacted Creative, so I expect an answer sometime tomorrow. I was just curious if anyone else had a similar issue with a resolution to it. As for changing the slot, its not exactly viable due to the airflow restrictions it would impose on my GeForce 6800 with Zalman VF-700 and, as far as I'm aware and this forum, you can't install it in the very bottom orange slot as its configured differently??
So does your board just not detect the sound card at all?
I have seen other threads where it won't detect any PCI cards at all, and that normally ends in RMA.
In fact, MSI made a beta BIOS for this, but please don't use it..
Well you could if you decide it's a last ditch attempt (meaning your gonna RMA it) or you have a BIOS savior.
Note here..
7025v152.zip 1. Fix the Audigy problems ?
Also see this thread.
Someone tried that BIOS, and had grief.
Got it back after some fun tho
Seen another person use it with no probs at all...go figure
I have seen other threads where it won't detect any PCI cards at all, and that normally ends in RMA.
In fact, MSI made a beta BIOS for this, but please don't use it..
Well you could if you decide it's a last ditch attempt (meaning your gonna RMA it) or you have a BIOS savior.
Note here..
7025v152.zip 1. Fix the Audigy problems ?
Also see this thread.
Someone tried that BIOS, and had grief.
Got it back after some fun tho
Seen another person use it with no probs at all...go figure
Last edited:
JoeySchmidt said:
Not a chance... LOL. Creative's "support" is hopeless. Unless something dramatic changed over the last few years. It is the classic case of a dominant company not caring about their customers as there is no decent alternative. (I remember problems with SB Live and VIA boards.... arggggh!!)With your collection of drivers - did it work at any stage? i.e. on the original drivers? Could it be a Creative update that killed it?
Re the Slots: My suggestions are based around testing and trying to get the item to work. Narrowing down where the real problem lies. Creative PCI cards have often been trouble due to their excessive demands on the PCI bus. (One of the reasons I don't have an add-in sound card).
Using the orange slot should be fine. The "different config" of that orange slot is so it can use the special MSI Wireless card. It should still work fine with other PCI cards.
When trying other PCI slots, avoid the first one next to your GeForce as this nearly always shares with the video card (which makes problems worse). I just meant move the card down to another slot. There are 5 to choose from. #1 is out due to it being blocked by the GeForce, but what about the rest?
Problems will often occur when IRQs clash. So it is still worth checking there as well
Associate
- Joined
- 26 Jan 2005
- Posts
- 116
- Location
- Glezga
Yea the card works fine but only up to the 1.80.50 drivers will install, the latest, 1.80.55, fails to detect the card during installation. The 1.80.55s are the ones that allow proper EAX4 support in Doom3, which is what I'm looking for as this motherboard runs the game well sweet.
Creative's support, in my experience, in recent months has been great. I got a reply today for instance. Saying that, I was only asked to confirm my OS revision!
As for the VIA chipset incidents back in the day, I avoided that like the proverbial plague as I knew VIA wasn't reliable then, oh how the times have changed!
Creative's support, in my experience, in recent months has been great. I got a reply today for instance. Saying that, I was only asked to confirm my OS revision!
As for the VIA chipset incidents back in the day, I avoided that like the proverbial plague as I knew VIA wasn't reliable then, oh how the times have changed!
It sounds to me like a minor upgrade to the Creative drivers is where the real trouble lies. If it was working perfect up to that point, it would imply to me that the motherboard is working fine. At a guess, the code within 1.80.55 wasn't fully tested with your exact version of the Audigy, so it has been missed out of the supported models list. A few gentle prods at Creative will eventually spew out a solution.
(You could try hacking it by hand. Track down the inf file which identifies your sound card to the OS. I expect the version in the 1.80.50 lists your card, but the .55's have missed it out. You could even try manually adding it back in. A trick often done with video card drivers. If you want to try this - ask me for a better explanation)
I am also very glad to hear that Creative have sorted out their support. I have had too many painful experiences of them in the 90's which made me walk away from their products completely. I'll be interested to see how they treat your problem, and it may even tempt me back.
Re VIA / SB-Live problems in the past. Should be fair that the problem was on both sides there. Which meant they both blamed the other and never really fixed the problem. The VIA chipset just couldn't handle that amount of excessive chatter over the PCI bus. Amazing how much better my old rig worked when I replaced the SB-Live with a Hercules Game Theatre.
(You could try hacking it by hand. Track down the inf file which identifies your sound card to the OS. I expect the version in the 1.80.50 lists your card, but the .55's have missed it out. You could even try manually adding it back in. A trick often done with video card drivers. If you want to try this - ask me for a better explanation
)I am also very glad to hear that Creative have sorted out their support. I have had too many painful experiences of them in the 90's which made me walk away from their products completely. I'll be interested to see how they treat your problem, and it may even tempt me back.
Re VIA / SB-Live problems in the past. Should be fair that the problem was on both sides there. Which meant they both blamed the other and never really fixed the problem. The VIA chipset just couldn't handle that amount of excessive chatter over the PCI bus. Amazing how much better my old rig worked when I replaced the SB-Live with a Hercules Game Theatre.
Associate
- Joined
- 26 Jan 2005
- Posts
- 116
- Location
- Glezga
Its working, its working
Right, first off I must admit an error on my part regarding the driver version numbers.
The first one (from the Audigy disk) is 1.80.00
The first web update is 1.84.11
The second web update is 1.84.40
Theres also a downloadable update that used to be in the auto update with the version number 1.84.50. This is what I used to only be able to update to.
The latest driver is 1.84.55 and incorporates the new EAX4 instructions for Doom 3, which is what I wanted it for.
Now, to cut a long story long, Creative got back to me after they finally realised what OS I was running even though I filled that box in during the web question thing! It turns out that this driver on my card requires a manual install. This is done via the decompressing of the 1.84.55 driver file, which can be downloaded separately or found in your 'Creative\Updates' folder if, like me, you have a failed installation. I will paste this verbatim:
"Open up the installation file with winzip, extract all the components
out into one folder. try to find for a ctzapp.exe. Make sure it is the
file in all caps and that has an icon of a blue and red or orange
triangle. Double click on this file.
When the Creative Driver Update Utility comes up, choose Driver
Installation and WDM and hit OK. It will now reinstall only the drivers
for the sound card. Again, when it is done, it will ask to restart the
computer, which you will want to do."
So, there you go MAllen, you were spot on regarding the implementation of my version of the Audigy 2. For the record, I used WinRAR if anyone is interested. Also, the file in my extracted directory was CTZAPXX.EXE instead of the one mentioned above.
[EDIT] Another thing, at least its not an issue with the MSI board.
Right, first off I must admit an error on my part regarding the driver version numbers.
The first one (from the Audigy disk) is 1.80.00
The first web update is 1.84.11
The second web update is 1.84.40
Theres also a downloadable update that used to be in the auto update with the version number 1.84.50. This is what I used to only be able to update to.
The latest driver is 1.84.55 and incorporates the new EAX4 instructions for Doom 3, which is what I wanted it for.
Now, to cut a long story long, Creative got back to me after they finally realised what OS I was running even though I filled that box in during the web question thing! It turns out that this driver on my card requires a manual install. This is done via the decompressing of the 1.84.55 driver file, which can be downloaded separately or found in your 'Creative\Updates' folder if, like me, you have a failed installation. I will paste this verbatim:
"Open up the installation file with winzip, extract all the components
out into one folder. try to find for a ctzapp.exe. Make sure it is the
file in all caps and that has an icon of a blue and red or orange
triangle. Double click on this file.
When the Creative Driver Update Utility comes up, choose Driver
Installation and WDM and hit OK. It will now reinstall only the drivers
for the sound card. Again, when it is done, it will ask to restart the
computer, which you will want to do."
So, there you go MAllen, you were spot on regarding the implementation of my version of the Audigy 2. For the record, I used WinRAR if anyone is interested. Also, the file in my extracted directory was CTZAPXX.EXE instead of the one mentioned above.
[EDIT] Another thing, at least its not an issue with the MSI board.
Last edited:
This is one reason I would never trust an auto-updater. They have a tendacy to auto-feckup. (This includes MSI's auto-updater I believe.)
Good to hear that not only were Creative quick to reply, but they actually answered your question.
Though it is bad to hear that they are still ******* up their driver installs. Do they still install all kinds of other "useful" progams to take over your system? When I had my SB-Live, the default install included CD Players, desktop taskbars, Effects Managers, tasktray utils. All kinds of pointless crep. When I re-built the PC at a later date, I found that I could get away with a minimal "driver only install" and all the games behaved fine. This way I could continue to use my own CD Players, etc....
I would also be interested to hear what you think of the Audigy. Is it worth that upgrade from the onboard stuff?
Good to hear that not only were Creative quick to reply, but they actually answered your question.
Though it is bad to hear that they are still ******* up their driver installs. Do they still install all kinds of other "useful" progams to take over your system? When I had my SB-Live, the default install included CD Players, desktop taskbars, Effects Managers, tasktray utils. All kinds of pointless crep. When I re-built the PC at a later date, I found that I could get away with a minimal "driver only install" and all the games behaved fine. This way I could continue to use my own CD Players, etc....
I would also be interested to hear what you think of the Audigy. Is it worth that upgrade from the onboard stuff?
Associate
- Joined
- 26 Jan 2005
- Posts
- 116
- Location
- Glezga
I'm the same I only ever perform 'Driver Only' installs!
[EDIT] Got the GTA:VC issue resolved.
I actually reinstalled the game on a new hardware platform with a save games folder from a previous hardware installation, so what I did was I deleted the 'gta_vc.set' file from said folder and da-dah, it now works! So, again no issue with said mobo.
[EDIT] Got the GTA:VC issue resolved.
I actually reinstalled the game on a new hardware platform with a save games folder from a previous hardware installation, so what I did was I deleted the 'gta_vc.set' file from said folder and da-dah, it now works! So, again no issue with said mobo.
Last edited:
Looks like my on-board Realtek ethernet has died today on my board. I had problems booting my desktop today so I swapped out the ATI 9800 Pro for my spare GeForce FX5200, same problem (hangs at boot config of Realtek card). I then tried each memory module seperately incase it was faulty RAM but the problem was still there. Once I swapped over to the other on-board ethernet (NVidia) the problem went away and now boots into WinXP. I then repeated the memory swapping process and no problems.
Sometimes during the boot config the desktop screen would get corrupted and go white/grey with random squares as if it was faulty memory but having swapped controller slot the problem went away. Has anyone else had this problem before on this board or others?
Sometimes during the boot config the desktop screen would get corrupted and go white/grey with random squares as if it was faulty memory but having swapped controller slot the problem went away. Has anyone else had this problem before on this board or others?