OMG sorry wrong post at wrong thread im very sorry!!!
OMG sorry wrong post at wrong thread im very sorry!!!
Cooler Master HAF 922
Samsung 830 128GB SSD
500GB W'D Caviar Black HDD
G Skill Ripjaws X (2x8gb) 1866
ASUS Maximus IV Gene-Z/GEN3
Intel i5-2500k @ 4.5mhz 1.270vcore
CORSAIR Enthusiast Series TX650 V2 650W
ThermalTake Frio running at 1300-1400rpm
EVGA SuperClocked GeForce GTX 560 Ti (Fermi) 1GB 256-bit
I would gladly send the misplaced post home but i do not have an address. LOL.
GLiffjOhn already posted it at "home" (http://rog.asus.com/forum/showthread...!!!!!!!!/page2) - maybe just forgot to delet it from here...
3 series MIVE, MIVG BIOS FLASH GUIDE
RAID GUIDE * Memtest86+ GUIDE * CAP GUIDE * USB BIOS Flahsback GUIDE * Win8 Rampage Install
ONLY IF 2003 BIOS or NEWER
To Flash back to 1xxx.ROM, Rename 1xxx.rom to ERALL.ROM and Use USB Flashback
Wow I had no idea that I've caused so many problems with this thread. I'm back now, because I've stripped it down as if Zeus were a used computer. In the process I removed the AMD graphics card and replaced it with an ASUS, I removed one set of RAM per G.SKILLs request, correctly enabled XMP profiling in the BIOS and have been using 3dsMax and the Unreal Dev. Kit for almost a week, but not without errors. I've been absentmindedly blaming these errors on the fact that UDK is a beta, after all, and that I don't understand 3dsMax well enough to criticize it. RCTweakIt claims my VTTCPU Voltage is not perfect, but according to a thread on here it's less than Intel's 1.40 max limit and higher than 1.20.
The errors: UDK crashes, a lot. I usually pin it on my lack of experience, for example some times I'll try taking an average height map without any falloff, and it crashes, or I minimize the brush size to 0 and then try to increase the size by percentage. But recently I've been noticing corruption, in the landscape specifically. At first I would attempt to colorize a few vertices with stone material and the entire sector would overflow with random colors. Today, the problem worsened, and instead of defaulting to the random colorization, it randomly chooses any material that I've already loaded into the landscape. Smoetimes it covers the landscape in shadow, blocking all light. I decided to play along and avoid using terrain that the material wouldn't agree with, and when I finally thought I had it all figured out, my computer shut off as if someone had unpluggged the power cord. No warning, and when it booted up it didn't try for safe mode. my CPU was at 49 degrees Celcius, the MB at 45 degrees, PCH in the high 40s. ( I run a separate tablet PC just to monitor Zeus). I've also had problems with file transfers and corruption of programs, I had to install 3ds Max a few times before it worked. Right now my VttCPU voltage is at 1.356 and is red. Should I fix it?
Welcome back, Lugh Azreak!I was really hoping that the incident didn't discouraged you to come back and seek for, or even offer help...
After you built your system, did you run any testing on it? I'm particularly curious if you used Memtest86+ for checking the memories stability...
When your system suddenly shut of, did you checked the Even Viewer? Is there a note around that time?
I did no testing. I've never built a system before. I'll run the memtest86+ now, and I'll check the event viewer at the time of my last post.
Okay I finally got around to running memtest86+ since my problems haven't fixed themselves. So far I have 5 failures, I'll try to list them before more show up:
Tst Pass Failing Address Good Bad Err-Bits Count Chan
___ ____ _____________________ ________ _________ _____________ __________ ______
3 0 0032ffec570-13055.9MB 01010101 21010101 20000000 1
4 0 0002d93d6f0-729.2MB d554da23 f554da23 20000000 2
4 0 0012dd9cfd0-4829.6MB 93347c9c b 3
4 0 001f095f2e0-7945.3MB 4ccfd2a3 6 4
4 0 0025d01eee0-9680.1MB 3164bc0c 1 5
4 0 00304e3ec60-12366.2MB 3b5f3d79 1 6
5 0 0003324fbb0-818.3MB 22000000 0 7
5 0 0003724fb90-882.3MB 22000000 0 8
6 0 00051dffd60-1309.9MB 40000000 6 9
6 0 0004949eee0-1172.6MB ff7fffff d 10
6 0 000b2e1dfe0-2862.1MB 10000000 3 11
6 0 0009e13d80-2529.2MB 00000008 2 12
6 0 0018ea1d0f0-6378.1MB 7fffffff 5 13
6 0 0028d63c060-10454.2MB dfffffff f 14
6 0 003002cd960-12290.8MB fffffffe d 15
This is where I caught up with the errors. The test is in the random numbers sequence and it looks like Zeus is doing well on this portion. I've noticed the pattern by now but will still write down the significant numbers, the error bits number sequence is always the same, the bad is the same as the good except for the first number/letter. I've recorded the bad unit only.
As a reminder, this is a Rampage IV Extreme motherboard running G.Skill Model F3-19200CL11Q at 2400 Mz with the Extreme Memory Profile enabled.
Have you enabled the XMP profile? https://docs.google.com/document/pub...0OU5VPe6CUoFso