OT: ASUS P9X79 PRO Memory Timings (BSOD)

JohnnyRoy wrote on 2/28/2014, 5:01 AM

I’m in BSOD h-e-l-l and need help from those of you who may have built a VideoGuys DIY9 around the ASUS P9X79 Pro motherboard like I did.

My once stable PC is now blue screening several times an hour! Sometimes I will boot it and not touch anything and 10 minutes later it BSOD’s all by itself without being touched! Sometimes it will BSOD before getting to the desktop and other times it may run for an hour or two just fine and then BSOD when I click shutdown. In this state it's unusable.

What changed you may ask? I broke the cardinal rule of PC maintenance… “if it ain’t broke, don’t fix it!”.

During routine maintenance I thought it might be time to upgrade all of my drivers from ASUS and that required a new BIOS because I was still using a very old BIOS version from over a year ago and some of the newer BIOS’s said they had improvements in USB 3.0, etc. The problem is that ASUS changed BIOS structure from .ROM to .CAP for Windows 8 “full-functionality” and once upgraded, there is no going back to my old BIOS. How bad can it be, I thought? Maybe I might want to try Windows 8, I thought? So I flashed the BIOS to the latest level. What a BIG mistake!!!

I’m using the recommended memory for VideoGuys DIY9 which is G.SKILL Ripjaws Z Series 16GB (4 x 4GB) 240-Pin DDR3 SDRAM DDR3 1866 (PC3 14900) Desktop Memory Model F3-14900CL9Q-16GBZL. I remembered that when I first built this PC, it did not work correctly. I had to upgrade the BIOS from the factory and tweak the memory timings to get it stable. But it has been rock solid for over a year. This memory is XMP compatible so this time I select Profile 1 which seems to have the correct timings and boot the computer. Then I upgraded the Chipset drivers, SATA, LAN, Audio, etc. All seemed to be working well. So a week has gone by and I don’t really use my PC much anymore because I do all of my work on my Mac so I haven’t had the PC on for any extended amount of time since the upgrade. Now I turn it on and try and get a few hours of Vegas Pro editing done and it starts blue screening like crazy before I can even load Vegas Pro. What’s crazy you may ask? How’s this for a list of BSOD errors in the past two days:



REFERENCE_BY_POINTER - STOP 0x0000018



CACHE_MANAGER - STOP 0x0000034



(no name) - STOP 0x0000024



(no name) - STOP 0x000007E



BAD_POOL_HEADER - STOP 0x0000019



IRQL_NOT_LESS_OR_EQUAL - STOP 0x000000A



DRIVER_IRQL_NOT_LESS - STOP 0x00000D1 - DXGMMS1.SYS



QUOTA_UNDERFLOW - STOP 0x0000021



SYSTEM_SERVICE_EXCEPTION - STOP 0x000003B

I didn’t think that many things could be wrong at one time! Each time the BSOD error is a different. There were more but I got tired of writing the new ones down. Can anyone see a pattern? I ran memtest86 and it went through 3 passes clean with no errors so while I always suspect a bad RAM stick, the RAM seems to be OK. Should I run memtest86 longer? How long is long enough?

Here is my request:

The question for those of you who built the VideoGuys DIY9 and used an ASUS P9X79 PRO motherboard with G.SKILL Ripjaws Z Series 16GB DDR3 1866 (PC3 14900) memory (part# F3-14900CL9Q-16GBZL) recommended by VideoGuys.

Q1. If your BIOS version is 2002 or greater, what version are you using that is stable?

Q2. What memory timings are you using? (are you using XMP Profile 1 or 2 or default, or manual timings?)

This has been an absolute nightmare and I would appreciate any help you can provide.

Thanks in advance,

~jr

Comments

Grazie wrote on 2/28/2014, 7:05 AM

Overheating? PSU?

G

paul_w wrote on 2/28/2014, 7:16 AM

Without thinking too hard about this, i think you answered your own question of what is causing this. You updated your ASUS drivers and flashed BIOS to a later version to help USB3 Windows 8 support.
I guess rolling back both bios flashing and drivers would clear this.
Can you get hold of an older version of the bios to flash?
Then proceed with updating one step at a time.

edit:more
link here explaining you need to run Bios Converter depending on your motherboard.
http://support.asus.com/Search/KDetail.aspx?SLanguage=en&no=CCBF53F7-9084-B397-C729-7C5579704573&t=2

Dd you do that?

and then this comment:
"Note: After converting your BIOS to .CAP structure, you cannot convert it back to .ROM structure. "

find it hard to believe its irreversible.

Paul.

craftech wrote on 2/28/2014, 7:29 AM

In terms of Memtest, you have to run it for at least 2 hrs to get any real accuracy.

I don't have that motherboard, but you might try the following:

Change the memory configuration from Automatic to Manual, and then select the multiplier as 10 : 1333. Save and exit. See if that works.

Make sure you have them in the correct slots. I believe it says to use the blue slots first.

The memory may have a different SPD on X.M.P. profile. If so, try two modules that match.

You could also try going into the bios and select optimal mode instead of normal mode, turn off turbo mode, then put the memory on xmp= 1866. It may not run higher than 1333 when turbo mode is on.

In the end it may only be stable when the bios runs on normal mode and the ram is in auto and picked up by the motherboard as 1333mhz.

In terms of memory timing and other problems I would suggest you go to Newegg User Reviews and read the 13 user reviews there to see if anyone else had similar problems. Alternately try the GSkill forums.

John

OldSmoke wrote on 2/28/2014, 8:40 AM

JR
I have only good things to say about GSKILL service. You can drop them an email and ask for the timings for your memory and board; I got a reply within a day.
I personally would try and run the memory and the recommended 1600MHz for a i7 3930K. There isn't much gain of going higher and you risk getting problems that are hard to rectify. I have 2133MHz memory chips in my system but run it at 1600MHz with a tighter timing as recommended by GSkill.
Another possibility, I know that from my own experience, is a slightly dirty CPU socket or CPU contacts. I had exactly the same symptoms as you describe on my previous 3770K build. I later found that there where fingerprints on the CPU contacts and once I cleaned that, all issues went away.

Steve Mann wrote on 2/28/2014, 9:18 AM

What size PSU do you have? Random BSOD's can be caused by a PSU that's just a little too low on capacity because it can make a random memory write error.

xberk wrote on 2/28/2014, 12:28 PM

When ever I've had a Windows PC do this sort of thing in the past, I've always tried a fresh harddrive, with a fresh install of the same OS. Will the PC run stable with just the OS installed under the new BIOS? If it will, then hardware issues are likely not the problem. IF hardware/bios/memory timings are an issue, likely the OS will not even install properly.

BruceUSA wrote on 2/28/2014, 12:49 PM

I don't use Videoguy DIY recommandation. But I made my custom built PC is a Asus P9X79 Pro I use Bios 2004. As for memory I used the same as yours but mine are 64gb. I can used XPM profile or manual in the bios. But I chose to to manual and use default timing. No problem what so ever.

Lovelight wrote on 2/28/2014, 12:54 PM

Right on. If worse comes to worse. Build it up from the ground up isolating the bad variable. We need to know that the mobo is still good & hasn't suffered a micro fracture causing the BSOD.

I use the P8P67 board with the 3602 bios, XMP2 memory timings.

And good luck.

JohnnyRoy wrote on 2/28/2014, 1:25 PM

> Reply by: Grazie “Overheating? PSU?”

Definitely not overheating since this happens during a cold start and my CPU is liquid cooled. I supposed it could be a coincidence that the PSU went bad?

> Reply by: paul_w “find it hard to believe its irreversible.”

Apparently so… the BIOS updater only recognizes CAP files and not ROM files anymore after you run the converter.

> Reply by: craftech “I would suggest you go to Newegg User Reviews and read the 13 user reviews there to see if anyone else had similar problems.”

Wow, looks like BSOD’s are popular. I’ll have to read these and try some of them.

> Reply by: OldSmoke “I have only good things to say about GSKILL service. You can drop them an email and ask for the timings for your memory and board;”

I never though of that and it’s certainly worth a try. I have the timings from their web site but it would be good to know if I have too tweak a voltage setting or something in addition. I doubt it’s sockets or anything since it’s been running stable for more than a year and nothing else has been touched except flashing the BIOS.

> Reply by: Steve Mann “What size PSU do you have? Random BSOD's can be caused by a PSU that's just a little too low on capacity because it can make a random memory write error.”

I have the “CORSAIR Professional Series Gold AX850 (CMPSU-850AX) 850W ATX12V v2.31 / EPS12V v2.92 80 PLUS GOLD Certified” My entire specs are on my web site: Intel Hex Core Video Editing Workstation

I did add a second SSD so I suppose I could take this out which would bring me back to the same power consumption as before. Worth a try.

> Reply by: xberk “When ever I've had a Windows PC do this sort of thing in the past, I've always tried a fresh harddrive, with a fresh install of the same OS.”

Yea, that’s actually my next move. I’m going to install Windows 8.1 Pro on a new SSD and see if it’s stable.

> Reply by: BruceUSA “But I made my custom built PC is a Asus P9X79 Pro I use Bios 2004. As for memory I used the same as yours but mine are 64gb. I can used XPM profile or manual in the bios. But I chose to to manual and use default timing. No problem what so ever.”

I'm going to try BIOS 2004 then. I think I can still use that. I’ve tried default, XMP 1 and 2 and all of them BSOD on my current BIOS. Maybe your BIOS version will be more stable. I remember having to tweak the voltage but the XMP profiles seem to have the correct voltage and if you didn't have to then I shouldn't have to. That's why I was wondering what people with the same motherboard and memory have done.

> Reply by: Lovelight “Build it up from the ground up isolating the bad variable. We need to know that the mobo is still good & hasn't suffered a micro fracture causing the BSOD. ”

I guess anything is possible and something could have failed that had nothing to do with Flashing the BIOS. I restored the computer back to a January backup and that BSOD’s shortly after boot so I can’t even apply the new Chipset Drivers.

Thanks to all of you for your suggestions. I’m going to remove the extra SSD drive and try the 2004 BIOS tonight and see if it makes a difference. If not, I guess it could be a coincidence that a part failed at the same time I updated the BIOS and the BIOS has nothing to do with it. I'm also going to try a clean install of Windows 8.1 Pro. I’ll let you know how I make out.

Thanks again and keep those ideas flowing. ;-)

~jr

Stringer wrote on 2/28/2014, 2:36 PM

The one item in your reply that got my attention:

I would be surprised if your SSD is drawing more than 5w max - so if that is tipping you over, you seriously need to evaluate your over-all PSU situation ...

JohnnyRoy wrote on 2/28/2014, 4:14 PM

Yea, I didn't think the SSD had anything to do with it and I doubt I'm close to my PSU's 850W max but I'm just trying to get things as close to how they were when everything worked.

~jr

BruceUSA wrote on 2/28/2014, 4:31 PM

Correction.... I said bios 2004 is incorrect. I meant to say bios 2104

NormanPCN wrote on 2/28/2014, 4:43 PM

JohnnyRoy> the BIOS updater only recognizes CAP files and not ROM files anymore after you run the converter.

ASUS has ways to update besides the updater built into the BIOS. Maybe one of the others can still handle the previous BIOS image file format. Like creating a bootable USB thumbdrive.

paul_w wrote on 2/28/2014, 5:53 PM

more thoughts:
Hard clear of CMOS memory. Battery out for 10 minutes (or shorting link to force cmos clear) with mains power off etc.. then try loading defaults. Some talk on the forums with some success doing this.
Worst case, replacement of actual bios chip available on Ebay for around $17. No idea what version they come with (.ROM or .CAP) some checking needed.

Paul.

JohnnyRoy wrote on 3/1/2014, 4:34 PM

> "Hard clear of CMOS memory. Battery out for 10 minutes (or shorting link to force cmos clear) with mains power off etc.. then try loading defaults. Some talk on the forums with some success doing this."

You know I remember reading about you might have to do this after going from a ROM BIOS to a CAP BIOS but then I forgot all about it. I reset the CMOS this morning, loaded the BIOS defaults, set the Memory XMP to Profile 2 and it's been running all day with no BSOD yet. This is encouraging. I'll keep you posted.

~jr

JohnnyRoy wrote on 3/2/2014, 7:03 AM

Well... that wasn't it. I turned the computer on this morning and barely got to the desktop when it BSOD'd with:

SYSTEM_SERVICE_EXCEPTION - STOP 0x000003B

I'm going to try flashing back to BruceUSA's 2104 BIOS and see if that helps next.

~jr

craftech wrote on 3/2/2014, 7:29 AM

Have you tried any of the suggestions I made above John?

Also many users face SYSTEM_SERVICE_EXCEPTION errors due to update number KB2778344 that Microsoft has developed as a Windows 8 update. You would have to manually uninstall it in safe mode. Microsoft rectified the problem by issuing update number 2818604.

Sometimes it occurs from problematic AMD drivers.
To fix SYSTEM_SERVICE_EXCEPTION BSOD error that arises due to AMD drivers, boot Windows 8 in safe mode and uninstall the problematic drivers.

John

JohnnyRoy wrote on 3/2/2014, 9:30 AM

> "Have you tried any of the suggestions I made above John?"

Yea, I played with the memory timings but nothing made it more stable. I've now set them to the defaults which are slower than the manufactures recommendation so hopefully will be more stable.

> "Also many users face SYSTEM_SERVICE_EXCEPTION errors due to update number KB2778344 that Microsoft has developed as a Windows 8 update. You would have to manually uninstall it in safe mode. Microsoft rectified the problem by issuing update number 2818604."

That was a February update. I restored the computer back to January 2nd, well before any of this started, and it was still unstable. So much so that I couldn't even install the new Chipset drivers without a BSOD.

Update on the 2104 BIOS:

I could not go back to the 2104 BIOS. Even though is was a CAP file, the updater rejected it as being too old. :(

~jr

BruceUSA wrote on 3/2/2014, 10:08 AM

I thought, you have to change to .rom not cap. After you download the cap file and you need to change it to .rom. Copy it into your fat32 usb stick and plug it into the usb hub. Restart the computer> enter the bios, try using the asus utility in the bios to do the update. Try that see it works.

Rob Franks wrote on 3/2/2014, 2:20 PM

Seems to be a common problem with one of the windows8 update files.
Try this:

[url=http://www.tomshardware.com/faq/id-1653284/fix-system-service-exception-bsod-error-windows.html]

JohnnyRoy wrote on 3/2/2014, 7:38 PM

> Posted by: BruceUSA "I thought, you have to change to .rom not cap."

No, it's the other way around. Here is a direct quote from the ASUS P9X79 Pro support page.

P9X79 PRO BIOS 2002

So the old BIOS is ROM format and the new BIOS is CAP format and once you convert to CAP format you can only load CAP files.

> Posted by: Rob Franks "Seems to be a common problem with one of the windows8 update files."

I appreciate the link but I'm not using Windows 8 so this shouldn't pertain to me.

It's been running OK under the default memory settings but then it just rebooted out of nowhere. I'm continuing to use it to see if I get another BSOD. If I do, I'm going to up the memory voltage a bit.

~jr

BruceUSA wrote on 3/2/2014, 8:48 PM

Sorry for the wrong information. You are correct, you are running Windows 8, so you need .CAP file I am on Windows 7 and I am on .rom file.