Retail Abit IN9 32X-MAX - Pictures, observations and testing...

[Slammin]

Just go into Device mangler and disable, then re-enable your sound. Works for me. Try with and without reboot. One or the other should work.

If that fails to solve it, uninstall the nVidia ethernet driver and just us the MS default one. Some have had this work.

By the way, even after you do get rid of that startup static, it could come back. Just repeat the above steps if it does.

[JargonGR]

Just go into Device mangler and disable, then re-enable your sound. Works for me. Try with and without reboot. One or the other should work.

If that fails to solve it, uninstall the nVidia ethernet driver and just us the MS default one. Some have had this work.

By the way, even after you do get rid of that startup static, it could come back. Just repeat the above steps if it does.

Thanks for the advice I tried it and it did not work. It was a much deeper issue as it seems and I solved it by reverting to the old bios. Everything works fine so far as it was working before.

Maybe V12 official release is not for me.

[brdavis]

Well,
Add another one to having RAID issues. I am also getting event errors! This will be my last Abit board.

[Lvcoyote]

I must be one lucky bastage..... I've been running a DUAL raid0 array, large overclock, SLI, and the whole shabang on this board....... Never even a hint of Raid problems......

[day187]

Well,
Add another one to having RAID issues. I am also getting event errors! This will be my last Abit board.

My motherboard is on it way back from rma due to the raid issues, windows got corrupt and I could not reinstall XP because my had drives would not show up in raid, they only showed up when I used them as single drives.

[JargonGR]

I must be one lucky bastage..... I've been running a DUAL raid0 array, large overclock, SLI, and the whole shabang on this board....... Never even a hint of Raid problems......

Same here and my sound issue is solved. It is rock stable @ 450FSB , 3.6GHZ E6600, SLI 8800GTX 665/1536/1029 and RAID0 - never had an issue.

[The Nemesis]

I think I'm finally gonna give up on this board. It's been pretty stable since 1.2B1 bios, but the FSB holes & massive vdroop have always irritated me. I tried a Q6600 in it last night and 400FSB was not possible. Nor was 378. I got 367 to boot but it was not stable. I tested the chip on the DFI P965-S first, and it ran all those FSB's fine. 367FSB was 12 hours prime stable. I need sli & quad core and this board doesn't seem right for it. I did try the latest offical bios which made the system unstable and would restart properly even @ stock.

[Slammin]

Your situation is exactly why I didn't get a Q6600 instead. I was afraid, not knowing much about what mobos did best with QUAD at the time, and not wanting to wound up with a 3.6 capable CPU that was limited by the mobo.

As it turns out, my chip will do 3.6 fine, but my PWM's hit shutdown temp! Obviously, I could just add water, but I'm not really hurting over it since I usually do run 3.6 with EIST enabled. Have not had any PWM related shutdowns running everyday stuff, and it's only when I do 4 instances of P95 w/small FFT's does the PWM immediately shoot up to 120+c and the machine goes dead.

As far as I can tell, the higher I can get FSB, the higher my ram bandwidth goes for any given timing. Not sure what the real-world affect of not being able to get a high fsb OC is with these quads, but I've read that quads do benefit from high ram bandwidth. I'm sure there is a point where more memory bandwidth does not really add performance for the CPU, but I'd sure like to know for sure where that point is.

[brdavis]

What kind of burst speeds are you guys getting on RAID? Best I have got is 128.6 MB/s

[day187]

My motherboard is back with a different problem : mad: for the last seven hours i been trying and get the mobo to save the settings to the bios with no luck. Here we go

1 Received my new mobo today from scan.co.uk after RMA because of my raid issues on my old board.

2. booted the motherboard got cmos checksum error and cmos battery error override enabled-defaults loaded Warning! cpu has been change to enter boot menu F1 to continue, del to enter setup. So i update the bios to the latest bios from the abit site, using the floppy and dos mode

4. Update went ok

3. restarted the pc and i got the same error again (cmos checksum error bla bla bla

4. Went into the bios set everything up to run stock F10 saved

5. On restarting i got the same error cmos checksum error and cmos battery error override enabled-defaults loaded Warning! cpu has been change to enter boot menu F1 to contiune, del to enter setup

6. Time for a new battery and yes after restarting yes i got the same error

7. Cleared the bios for 1 hour still the same error

8. More investigating then I noticed that the codes on the motherboard were not moving they just stay on 00 and CC, I looked in the manual and I can not find the codes

9. Pressing F1 and trying to boot to CDROM did not work (should have known that by now that nothing gets saved to the bios)

10. luckily the cdrom was the 3rd device in the boot order so I continued to set up windows with no problems oh just when windows restarted same error so I pressed F1 to continue windows loaded I installed all the drivers restarted same error, but now it loads into windows,

11. All my hardware works fine PSU.Memory,CPU

Any suggestions or should I just walk away from this motherboard.

Thanks for listening


Sorry for any spelling mistakes been along day and its 1:30am Nite all

[brdavis]

If you are getting a CC code your CCMOS jumper is set wrong. Move the jumer on the motherboard.

[day187]

If you are getting a CC code your CCMOS jumper is set wrong. Move the jumer on the motherboard.

Thanks i realized that soon as i posted but even with jumpers in he right place i get the CC error then staright to 00 error and the codes do not move even when i power on or restart, i manage to save some settings to the cmos but they show up wrong in windows, and when i restart the pc it does nothing just a black screen and after i restart my pc my settings get reset

any other ideas thanks

wrong speeds in windows pic here

[brdavis]

Hate to ask simple questions....
You did check and make sure the switch (CCMOS) in the back is set correctly? Also, If you are talking speed as in the CPU it looks about right.

[brdavis]

To all that have posted here with Raid errors. Searching the net tells me there is a pattern here with the 680 chipset...

The story continues...

[day187]

Yes all the cmos switches are correct and the cpu is showing the wrong speeds in cpu-z and in windows, I set the fsb 400x9= 3.6Ghz and the memory on 1000Mhz in the bios

In the bios it shows the correct speeds but windows and cpu-z say different and my settings get reset every time I restart and I’m still getting error codes (error code CC then 00) but it still boots into windows with default settings.

Might be a long nite

Thanks brdavis

Yes i turned EIST Function and c1e to disable in the bios.

[The Nemesis]

@day187

Your motherboard apparently has the official 1.2 bios. When I flashed to that bios this weekend, my E6600 & Q6600 did the exact same thing. No matter what I tried, the pc wouldn't restart, I had to turn it off, and when it rebooted, 350 FSB X whatever multiplier. It all cleared up after I flashed back to 1.2B1 or 1.2B3. I'm staying with 1.2B1, its been the most stable for me. Uguru still doesn't work for me but my system is rock solid @3.7GHZ. Hopefully a bios will come out soon that will remove my FSB holes & allow me to overclock my Quad. Anyway flash your bios to something else & that problem will go away.

[maxwedge]

To all that have posted here with Raid errors. Searching the net tells me there is a pattern here with the 680 chipset...

The story continues...

Yep, but it's not just raid but an issue of disk errors with memory set not much more over 800 mhz. I got errors raid or not but they stopped when I slackened the memory down to 800 mhz or so. I just tighten up the timings a little to make some performance up.

[day187]

Well now the motherboard will not recognize my A drive, I used Flashmenu to flash back to 1.2B3,

1. Codes on the motherboard change during boot up but time I get to windows logo with the scroll bar the code is back CC followed by 00 then into windows.

2. I still get the cmos error 9/10

3. Nothing will get save to bios and when it does after a restart it just resets its self back to default, date, time every settings

thanks all

[The Nemesis]

1.2B3 didn't work for me as I mentioned before. Please try the 1.2B1 and see if you have any better luck. Power off & clear cmos after flash.

[day187]

ok cheers

[day187]

1.2B3 didn't work for me as I mentioned before. Please try the 1.2B1 and see if you have any better luck. Power off & clear cmos after flash.

still no luck but i'm not getting the cmos errors no more, just the error codes CC and then 00 and nothing will save to the bios


Thanks The Nemesis

[leighrogers]

:-)

[maxwedge]

Day187, did you replace the battery? I see you said something about it but did you do it?

[day187]

Day187, did you replace the battery? I see you said something about it but did you do it?

Yes I replaced the battery with 2 brand new batteries, bottom line is that the motherboard is F**KED and it has gone back to scan on a second RMA 3rd time lucky. "Scan said they are going to get one of their super engineers on it like they did last time"

Thanks all for your input Keep it XS

So about my language don’t like swear but this as took the PI** sending a motherboard that’s worst than the one I just RMA ed thanks scan

Gone pub British style "hello Stella "

[brdavis]

FYI

Found that disabling command queuing in the RAID properties cleared up my RAID errors!!!