New Hardware, Clean install

Actually, the cold boot run of Memtest is significant. Sometimes that is when the RAM errors show up. I would venture to say that you do have a RAM problem. It may not be one that shows up unless the RAM is really stressed.

Yesterday when I shut down the PC I got a BSOD again, NTFS_FILE_SYSTEM. It might be related to what you said.
I haven't had any other problems yet, not even when running prime blend from cold boot, so far. How much more can one stress the RAM besides prime95 and games and applications. Memtest is great, but if nothing happens during real-world usage, I'm just reluctant to once again send the modules RMA or even take out the whole motherboard for RMA

edit: the BSOD might also be related to defraggler 2.00.221 beta. If I remember correctly, it was the first defrag I did after recent format and it was with that piece of software. So I'll keep my eyes on that.

edit2: just had a memory_management BSOD again. So there's still something wrong with the memory, like you said. Also firefox keeps crashing so often and W7 aero sometimes gets turned off and then on again. Which I think is worth mentioning, sounds familiar? Don't really know where to go from here, so I've also asked OCZ.
I'll try all available QPI/vtt voltages in between 1.200v and 1.360v and see what that does in memtest from coldboot. It's pretty much the last memory setting I can try fiddling around with. Besides trying 1.64 RAM voltage instead of 1.66v (1.65v unselectable). After that I guess it's either memory modules RMA (again) or motherboard RMA.

Hello again Carl. Still in the process of sorting this one out, though it's still looking like I have faulty memory. Still getting errors in memtest upon coldboot, today when I got into windows after memtesting and getting coldboot errors, my firefox would crash and later on windows with memory_management. So that one is pretty obvious.

Now I've just had a bad_pool_header BSOD. To be precise, my windows aero effect disabled out of nothing, I decided to restart the system, upon logging off etc. it would BSOD.
Usual cause device driver, but can it also be caused by bad RAM? We've already looked into device drivers so much. In case you need it, I have attached the dump.
Should I turn on SMART in my bios for my RAID0 drives (I have been told it would have a negative effect in case of RAID(0)) and do a check up of some sort just to make sure? Though I don't think SMART will be able to read out data in RAID0.

Update: Current memory kit has been shipped RMA to OCZ, they're in the process of testing them I suppose. I still think the only problem here is/was the memory, but you never know. Will update this once RMA has been finished. Thanks again.

I apologize for the delay in getting back with you. I overlooked this thread. Please let us know what they say about the RAM.

Error code 19, BAD_POOL_HEADER - Usual causes: Device driver.

Error code 1A, MEMORY_MANAGEMENT. Usual causes: Device driver, memory, kernel.

You can see from the above that device driver is common to both error codes. We need to take this right down the line and eliminate any possible BSOD cause.. First uninstall Avast. Avast generally runs well with Win 7; but is known to cause BSOD's and some Win 7 systems. You can try it again after you get your system stable. You have MSE installed; so you are protected.

Next you should update or eliminate these obsolete drivers.

hamachi.sys Thu Feb 19 05:36:41 2009 - LogMeIn Hamachi Virtual Network interface driverhttps://secure.logmein.com/US/support/hamachi2/. Update this driver. If there is not a later driver. uninstall LogMeIn.

SSPORT.sys Thu Aug 11 19:07:32 2005 - Samsung printer driver Samsung. This is an XP driver. I do not believe there is an update. If you cannot update it, navigate to C:\Windows\System32\Drivers, locate this file and rename it from .sys to .bak. Reboot and this driver will not load. This will break the Samsung utility program; but your printer should still work.

Unistall Avast and take care of the above drivers. Let's see how your system runs. Please update us and let us know. Feel free to PM me if I miss your update.

MOM.exe is -

Catalyst Control Center: Monitoring program belongs to Catalyst Control Centre or Catalyst Control Center- or MOM.exe or Sony Ericsson Device Data or TurboTax 2008 WinPerProgramHelp by ATI Technologies Inc (www.ati.com) or Advanced Micro Devices Inc.

CCC can be a real PIA on some Win 7 systems. You can install just the video drivers and uninstall CCC.

I agree that Hamachi and Avast should be OK. When troubleshooting, we have point out any potential BSOD cause. I think your problem was faulty RAM. And then CCC caused and app crash. You have done very well in troubleshooting and following suggestions.

Thanks Carl, I think and hope you are right about it just being a RAM problem. Hate to get more trouble going on after returning two RAM kits already.

I have now also deleted CCC, ran driversweeper, installed the whole package again except for CCC and the WoW trial of course. I take it audio HDMI stuff and the other Windows 7 support features are OK.
Hamachi is now also permanently deleted, hamachi.sys is gone and so is ssport.sys (double checked). Avast is also deleted for the time being.

This morning I ran memtest from coldboot, the first 2 tries getting into memtest failed: the memtest screen would stay blank (blue), no info. Third time worked though, and I did a 2.5 hour 3 pass run without errors. Not sure if that was actually a cold boot anymore by that time though. And I had that blank screen before on the other kit as well... So I don't know... Is this something significant? We might happen to run into something motherboard related here, considering this is my 3rd memory kit. Now, I do assume the RMA department checked the previous 2 kits and also found them corrupt. But you never know...
Also, some days ago when I wasn't at home and wanted to check back on the system with teamviewer, my PC just froze a couple of times. No errors or BSOD, just a freeze. I think prime95 was on, but I don't remember seeing any errors in the workers (didn't check to be honest...). Will try to replicate this.


Will use the system normally and keep doing coldboot checks as well. I'm sorry for this wall of text. I'll keep you posted.


p.s. when logging in and out of windows, the screen fades, you know? When it does, the picture on my screen vibrates, it gets off-center to the left I suppose. Don't think I had that before. Having samsungs monitor identification software installed or not doesn't make a difference (currently uninstalled again, whats the use please?).

Try running Prime95 to test both your CPU and your RAM. Follow the instructions in this tutorial: https://www.sevenforums.com/tutorials...t-prime95.html. Run 3 separate tests, one on each of the settings (Blend, Small FFTs, Large FFTs).

Try this free CPU stress test: |MG| CPU Stability Test 6.0 Download

Will do!

So far no BSOD, but I haven't tested for so long either (don't mean prime). I did get a couple of freezes, starting some days ago (that is on the new ram) Happened again just a minute ago. I noticed that during this freeze, my USB mouse and USB keyboard lights turned off as well. A clue perhaps? My PSU is brand new, Corsair HX850. But the previous two ram kits were also new, we all know how well those ran. The freezes I've had so far occurred during prime, gaming and idle windows.

I locked my CPU vCore at 1.23125v, if I remember correctly, the "normal" value. I did this because my motherboard suffers from coil whine when it varies voltages for power saving goals. The sound used to come from my old PSU. Now that I RMA'd that one, it comes from the CPU socket. Quite annoying, but locking the voltage fixed it. It is a known fault in the X58A UD3R motherboard and there's a fix for it. But that would mean another RMA and I'm getting sick and tired of that.
Maybe it (voltage locking in combination with other stuff) is the cause of the freezes, C1E and EIST are both on I suppose, didn't change those. Could try to replicate the freezes with vCore on auto of course. Or maybe it's still about trying to get the optimal QPI/VTT voltage (currently 1.34v). Pffff, back to the drawing board I guess...

Your thoughts please :)

Update
Blend test: Test completed, 22 tests in 54 minutes - 1 error, 0 warnings (worker #7) other workers were still running OK. I'm happy to see at least an error instead of a freeze. Though interesting that I didn't get errors before out of all the prime's I already ran.
And from the results log file:

FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.

Now running small FFT's, 8 threads...

Since Prime has found an error and your motherboard has a known fault, I recommend RMAing it. I would do so if it were my computer.