Gigabyte Z68 Motherboard disaster

[TJones2]

Got another bluescreen:

http://i.imgur.com/oAd8y.jpg

but this was after dropping back to stock voltage AND running it at 3.7mhz. I did put the new HSF on, it works great. Dropped idle temps to the low 30s, highs to the upper 50s, and high 60s if overclocked to 3.7. Hoping that by boosting the ram voltage back to 1.56v that will solve it.

 

[you2]

Sounds like what i get with stock cooler. Bit concern that you have to up voltage. I test both my sysytem to 4.0 ghz with stock (default) voltage and cooler. Toched 70 with prime 95 after 30 min @ 4.0 so dropped speed down to 3.8. From what i read default voltage should be fine till 4.4 to 4.6 dependent on batch. Btw i use 2500k (needed 3000hd in one otherwise 2400 ok but 2100 only dual-core). Game sys prefer 2500k.

 

[TJones2]

Now I'm really ticked at my vendor. I've been going back and forth with their tech support person trying to get a handle on these bluescreens, and today, the tells me if I want things to work to "exact specs" I should return the ram, pay a 15% restocking fee, and try ram that's "compatible" with the motherboard. This is the first time he's suggested the ram might not be compatible, not that I believe that. In fact, he hasn't given me any answers at all. I'm not looking for "exact spec" I'm looking for it to work as it should without bluescreening on my three times a week.

 

[you2]

Did you enable xmp on mb? Is your ram 1.5v or 1.6 or ...

 

[TJones2]

Unless xmp is turned on by default, I'd guess no. Ram is 1.5v

 

[TJones2]

They released a new bios yesterday...was hoping it would take care of these issues. Didn't. Got a bsod and a spontaneous reboot shortly after. Anyway, if it were an incompatibility with the ram (as the tech suggested) you'd think it would have been addressed in the new bios.

 

[iTwins]

Why guess at BSoD when you can find out yourself.

Install Windbg (Windows Debugger) from the Windows Developer's Kit and wait for the next BSoD core dump. The MEMORY.DMP is located in C:\WINDOWS\MEMORY. You cannot solve everything but at least it could pinpoint and tell you what *could* be the culprit. Keep in mind if the system Just BSoD but doesn't auto reboot does not produce a dump. In that, you are on your own again.

Come to think of it, nowadays you don't often get BSoD on NETBT.SYS. LAN driver issue? Or virus/trojans? You gotta lay off on the pr0n and warez, dude!

 

[TJones2]

What's the learning curve for Windbg? I have the weekend to decide if I'm sending the entire lot back.

 

[you2]

Enable xmp and run memtest or prime95. Bad memory happens.

 

[iTwins]

What's the learning curve for Windbg? I have the weekend to decide if I'm sending the entire lot back.

If you can return the whole system, then by all means do it. Afterall, new system. Windbg is for last resort situations, just before the end of the world. But don't get your hopes too high, this is Microsoft. If it's really good, you don't usually get it from Microsoft.

For more info: http://m.networkworld.com/news/2005...sh+dump&ie=UTF-8&oe=UTF-8&hl=en&client=safari

 

[TJones2]

Enable xmp and run memtest or prime95. Bad memory happens.

See post #30.

Afterall, new system.

At this point, if I ship it all back, I'm giving up. Everything goes back to before the upgrade and I'm looking at Dell's and Apples.

Windbg is for last resort situations, just before the end of the world. But don't get your hopes too high, this is Microsoft. If it's really good, you don't usually get it from Microsoft.

For more info: http://m.networkworld.com/news/2005...sh+dump&ie=UTF-8&oe=UTF-8&hl=en&client=safari

Thanks.

Update. Shipping it back...no one can figure out what's up and they're being pretty cool about the entire thing. Think I will give it another shot, just not right away.