Possible mobo problem? New build. **updated**

[grohl]

No one likes potential hardware problems, especially when it's a new build.

I'll try to keep it simple.

ASRock Z68 Extreme 3 Gen 3
2500k stock (for now)
XFX 2 Gb 6950
Patriot 1600 8Gb
Crucial M4 128 Gb SSD

Selected ACHI in BIOS prior to fresh Windows7 64 install. Applied all current mobo drivers, video drivers, AVG, windows updates and multiple restarts. All went well. Then I added in old hard drive, 2 optical drives, flash card reader. On restart, the SSD took a big dump. After Windows flash screen, BSOD (so fast I didn't see error code). On restart, BIOS claims there is no legitimate Boot drive. Crap. BIOS is showing that the SSD is still there though, but could not get it to boot. Even took out everything BUT the SSD drive and same thing.

Well, I started over and reinstalled Windows. System is stable, played BF3 for a couple of hours. Except, in device manager, there is an error that the driver for "SM bus" is not installed. Can't find much out on this issue. Last thing is, was trying to update SSD firmware, but unable to burn .iso image. Sound like a mobo issue, right? Or problems with SATA interface? There are no "chipset drivers" that I am missing. I haven't updated the BIOS, yet. Just not sure how to proceed.

I did post a similar message to ASRock forums on TweakTown, but, well, you guys are the best.:awe:

edit: see updated info below

 

[ElFenix]

SM bus is monitoring. shouldn't affect your ability to burn CDs.

how was it unable to burn the iso? did it coaster or did the program refuse?

 

[grohl]

It hung halfway though the burn. Tried it again and it hung at 11% burn. Program also hangs when scanning for available devices.

I think I will try another burn program as well. I was using freeware...is alcohol 120% the program of choice?

Won't worry about SM bus then, thanks. Anything else I can do to ensure the SSD/mobo is ok? I figured playing BF3 and all that is a pretty good read/write/performance test.

 

[Topweasel]

SMbus is supposed to be installed with Intel chipset drivers. Even if you installed them once before do it again and maybe make sure you are using the latest from Intel's site. I have seen this happen before a second or third install has taken care of it. That doesn't work uninstall the ones in there before reinstalling.

Also check the firmware on your M4, there was an early firmware that wasn't stable, and another firmware that caused your computer to reboot every hour after 5k hours of uptime. Latest one should take care of all of that.

As for Burner. Try ISO burn. Seems to work great for most. But at least its another software to try.

 

[grohl]

Chipset drivers updated. SSD firmware updated.

SM bus error is gone. And now able to burn .iso image. Any more BSODs and I will be back. Thanks.

 

[grohl]

ok so more blue screens.

When I originally upgraded the chipset drivers and the SM bus problem went away I thought all was well. Nope. I then ran prime 95 for 10 minutes and after shutdown had a BSOD. Whoops. On to memtest86. I had all kinds of errors. Turns out I had both sticks (matching Patriot 1.5V 1600 4Gb) in the B1 and B2 slots.

I then tested each module individually and the memory passed.

Finally got around to reading the manual ( I know, RTFM) and the recommended setup for two sticks is use of the A1 and B1 slots (or A2 and B2 - see below).

So....then I placed the RAM in the proper slots ( A1 and B1 this time)...and the memory is not recognized in the B1 slot. It only shows the A1 slot as having a stick in. I then removed the A1 stick and left the B1 stick in...and it recognizes the B1 stick.

Am I correct to return this board to Newegg for being defective? Despite errors, it does not seem like it is the memory as above.

| | | |
| | | |
| | | |
| | | |
A1 A2 B1 B2

 

[ElFenix]

i'd ship it back at this point.

 

[birthdaymonkey]

It's not necessarily a defective motherboard. It could just be a RAM incompatibility. Have you got another set to try?

 

[grohl]

It's not necessarily a defective motherboard. It could just be a RAM incompatibility. Have you got another set to try?

No I don't have another set, just DDR2 from my last system.

You got me thinking. I never did look up on the ASRock website the RAM suggested on this thread, I just assumed it was compatible.

Then I found the list: There is no mention of the Patriot 1600 4gb modules. Then again, isn't this just a list of RAM that's CONFIRMED to work?

The fact that the DIMMs pass individually in several of the slots tells me the RAM is ok. Am I wrong?

 

[mfenn]

You are correct, the ASRock memory HCL is just memory that they've tested and confirmed to work. It in no way implies that memory that isn't on the list is incompatible.

The manual lists A2 and B2 as a valid 2 DIMM configuration, have you tried that?

 

[grohl]

You are correct, the ASRock memory HCL is just memory that they've tested and confirmed to work. It in no way implies that memory that isn't on the list is incompatible.

The manual lists A2 and B2 as a valid 2 DIMM configuration, have you tried that?

Alright, this is like a damn soap opera.

So, I had packed it all up, saw mfenn's post, thought, what the hell. Unpacked and did a bare bones setup, mobo/memory, used on board video, and then the old power supply. Bam, RAM recognized. Both at a1/b1 and a2/b2. Added on 6950, same thing.

Next I remounted the new board, used the old power supply, saw both sticks now recognized (?) and ran memtest three straight times. No errors were reported BUT the process hung every time requiring (step 7, this varied) hard restart.

Can I have my sanity back please? Motherboard back to Newegg. Memory previously checked ok individually - it's ok, right?

 

[Topweasel]

Are you using the XMP profile, default, or manually setting the memory up?

 

[grohl]

Default settings.

Currently able to game with new card and old setup (Q9300, 4Gb DDR2, 6950). Able to game decently. Will see when new board returned, if it's the RAM or not.

 

[ElFenix]

Can I have my sanity back please? Motherboard back to Newegg. Memory previously checked ok individually - it's ok, right?

not necessarily. it can go bad after a while. it's just rare.

 

[mfenn]

Alright, this is like a damn soap opera.

So, I had packed it all up, saw mfenn's post, thought, what the hell. Unpacked and did a bare bones setup, mobo/memory, used on board video, and then the old power supply. Bam, RAM recognized. Both at a1/b1 and a2/b2. Added on 6950, same thing.

Next I remounted the new board, used the old power supply, saw both sticks now recognized (?) and ran memtest three straight times. No errors were reported BUT the process hung every time requiring (step 7, this varied) hard restart.

Can I have my sanity back please? Motherboard back to Newegg. Memory previously checked ok individually - it's ok, right?

It could be that something on the board was shorting out in the case or was simply marginal and that normal handling was very slightly changing the properties of some solder joint. I think that an RMA is that best way to go about things.

 

[grohl]

So here is an update.

The motherboard (ASRock Extreme 3 Gen 3) was RMA'd through Newegg. Lightning fast - that company is the best.

While waiting for it to arrive, I decided to email Patriot and see if I should send back the memory. They though so, so memory was sent back. (Patriot 4Gb DDR3 x 2 1600).

Got the mobo lightning fast last weekend, then went to Fry's and bought same memory - they pricematched Newegg. I figured, when I get the memory back from patriot, I'll add it in and have 16Gb just for fun.

Summary - original memory (A) sent back to Patriot. New memory (B) from Fry's. Memory replacement from Patriot (C).

Now, the new problem. (B) memory placed in positions a2/b2. Mobo autodetects at 1333. Manually set to 1600. No prob. Other settings 9-9-9-24 set and Memtest runs it for 6-7 passes no errors. I go on to use this setup for a week, gaming, etc. All is good.

Then (C) memory arrives. I install in remaining slots a1/b1. Restart - doesn't post. Weird thing, fans start, shut down, restarts in 3-4 sec for 2 secs, shut down. Cycle repeats 2-3 times before coming up to BIOS. All memory recognized but at 1333 timings. Fine, then I run memtest on the whole batch together. 33 errors.

Now I am thinking, WTH? NEW memory from patriot is bad (C)? So, I take out (B) and leave (C) in existing slots. Same POSTing problems as above. Will not accept 1600 set manually. But - run memtest on (C) only and it passes 6 times.

So, currently running with (B) back in a2/b2.

Should I give up the thoughts of doing 16gb on this board? Should I send back (C) again? Could it be the motherboard, again?

 

[mfenn]

Well, the memory controller is built into the CPU these days, so it could also be that yours can't handle 16GB. Try increasing the DIMM and related voltages.

 

[birthdaymonkey]

Passing memtest doesn't always mean the memory is OK. My hunch is that this motherboard doesn't really like the Patriot memory that you have, which is causing the seemingly random problems (although this is just a hunch). If I were in your position, I would have tried a different brand of memory.

OTOH, if it's working perfectly with the 8GB, there's really no need to have 16GB except for a few specialized applications. You could just sell the extra RAM and be happy.

 

[grohl]

Yeah, I am happy to be up and running. I just want to be able to add friggin' 16 Gb to a board that's supposed to support it. And not really understanding the problem entirely.

I did reliably get the machine to POST with turning off the rapid boot sequnce, but only 80% of the time, and still only recognized it as 1333mhz despite manually adjusting the settings.

I will return or sell the remaining memory and be happy with 8Gb. I guess.

 

[ElFenix]

i'd figured with on die memory controllers using 4 sticks would be more reliable than it had previously been. guess not.

exactly which patriot set is it?

 

[mfenn]

i'd figured with on die memory controllers using 4 sticks would be more reliable than it had previously been. guess not.

exactly which patriot set is it?

More reliable on average, sure. Doesn't mean that you can't get a bad chip though.

 

[ElFenix]

More reliable on average, sure. Doesn't mean that you can't get a bad chip though.

i suppose that's true. could just be set (C) here.


seemed like for a while there if you wanted to run 4 sticks you had to run them with loose timings compared to running any pairs of those same 4 sticks.

 

[mfenn]

i suppose that's true. could just be set (C) here.


seemed like for a while there if you wanted to run 4 sticks you had to run them with loose timings compared to running any pairs of those same 4 sticks.

Very true. It should work, but it could be that the BIOS is being a little too aggressive with the timings for 4 DIMMs.