Memtest 86+ Errors (v1.60)

Hiya,
I'm having a few problems with Memtest 86+ (v1.60) which is really annoying, so im hoping someone will be able to offer me some advice
I have 2x512mb of Crucial Ballistix 3200 (DDR400) with Memtest 86+ i get constant errors at stock speeds, ive tried relaxing the timings and tested each stick individually, they are running at the rated voltage of 2.8v.
The memory has been tested on a Abit board at DD400 and ran fine with no errors.
The errors do not cause my PC to crash or freeze ive ran prime95 for 5hrs+, 4hrs+ of Half life2 with absolutely no issues.
What could be causing the problem (could it be the bios?) and if my computer runs fine should i worry about it?
Any suggestions would be appreciated
Thanks

Richard
The chipset on the ABIT board i used to test the RAM is VIA KT600 with a 3200+ Athlon XP (Socket A)
Syar
The RAM i'm using is low latency Crucial Ballistix 3200, which has rated timings of 2.2.2.6 (see link)
I get constant Mem86+ errors with all my settings at stock speeds, ive even slackened the timings but still get errors

Similar Messages

Memtest.exe error, won't recover

Hey all. I'm not sure what to do with my Toshiba Satellite. It's giving me a PXE-MOF No bootable device error. When I try to do the built in Toshiba recovery option, it acts like it's on it's way to recovering but then restarts by itself and goes right back to the PXE-MOF screen. Now I was initially thinking my hard drive was messed up but it IS detecting my hard drive in the BIOS screen or whatever.
(I was getting the blue screen of death before all of this started happening, then I wiped my hard drive and tried to recover it but it doesn't want to recover)
I got into the memory diagnostic option (or something like that) and it says that my error is memtest.exe and says I need to repair it by the Windows installation cds? I don't have that cd. Now I'm not sure if I should buy a new hard drive and install Windows 7 or if it's a hardware problem or if I should just get a new computer all together. It's a $500 laptop and didn't even last a year. It's very frustrating considering Toshiba is supposed to be one of the most reliable brands.
Any thoughts?

Because the recovery isn't working, it seems likely that it's either the hard drive or some other hardware failure. However, if it's under warranty you should contact customer support.
- Peter

MemTest 86+ Errors

I am running my memory as shown in the profile. I have overclocked slightly to 210MHz FSB. I am getting a memory error on Test#7 with MemTest86+. I have tried increasing the memory voltage but that gives additional errors. I also get the error with no overclocking and the memory voltage as shown and also with increases up to 2.8v. I am also using 1T timing. Would appreciate any suggestions for fixing the memory error. Thx

If your 3200s are like those 4000 I once had you can run 2-2-2-8 up to 205, after that it is 2.5-2-2-8 up to may be 220. Then comes 2.5-3-3 which they might do up to 24x. Dont give more than 2.8v - they get very hot. More didnt help me either.
One thing is for sure, there is no way these will run with 1T - ONLY 2T. Loads of memtest errors as you know and Prime95 is even worse. Try oc very moderately and I think you will run into blue screens even before you see desktop. Not a problem with 2T.
May be module is dying as said, possible. Try 2.5-2-2 - really no loss in performance and 2.5 definitely suited mine better. Think that is common experience with Ballistix.
A matter of compatibility this 1T/2T. I also have some Kingston HyperX 3500 - same, 2T only. Then these 2 slow 1gb Corsair PC4000PT modules run with 1T like it was nothing. I was sure it was bios and perhaps it is, tuned to slower latency ram. I have done some tests with same cpu, mhz, fsb and it is a bit funny that for example SuperPI give almost same result. Ballistix faster of course but 1T make up for 3-4-4.
If I remember correctly it help passing memtest and Prime95 to set TRRD and TRTW to 3 or higher, 4-4 or even 5-5. I remember those settings were important, got some tip about that on a DFI forum. Also perhaps increase TRC to 14. Mine passed 12 hours of Blend with this at 246fsb. 2.5-3-3-8. Booting at 246fsb with 1T would give stopcode for sure, 2T all the way.

Memtest-86 errors (Geil PC3500)

Hi guys,
Just put together my system and I ran Memtest-86 and got some errors.
Would you be so kind as to look at these screenshots and advise me what to do ?
Here's my info on the ram. It's Geil Golden Dragon PC3500 (2x512)
First off my memory settings from CPU-Z
CPU-Z Settings
and my Sisoft Sandra Memory Bandwith info.
and lastly my memtest 86 results after running last night as I slept.
This is the first system I put together and I am not real sure about memory timings voltage etc. I am still learning.
Do I need to return this memory ?
Thanks for your help,
Jimmy

Quote
Originally posted by Jimmymac1000
The GeIl website says the ratings for Golden Dragon PC3500 are :
# CAS 2.5 6-3-3 1T @ DDR433 PC3500
# 2.55V-2.95V
My settings are 2.5 6-3-3 1T and 2.85V. Isn't that right at spec ?
I see that some other people on the board are running at 2 6-3-3 1T with no errors.
I really don't want the down time of sending back the RAM, but I will if it's advisable.
Hope I'm not beating a dead horse. I'm just trying to following the steps in the forum for setting up a new computer and have never messed with ram/ram timings before. Still have to run prime 95.
Thanks for you paitience.
Jimmy
The timings are right, Jimmy. Templar2k must think you have the same RAM he does- which you don't. Although they are both GEIL, you have PC3500, and he has PC3200. The timings will be different.
I'f I'm not mistaken, 2.85V is the highest the MSI board will go, without hardware modification. The fact that you still get errors during memtest is definitely a cause for concern then. I'm guessing your sticks are probably good, that is, there is nothing wrong with them physically. But, they are just too power hungry and need all of the 2.95V that GEIL recommends.
One thing you can try is relax the memory timings even further. Go to 2.5-4-4-8, and in doing so, go ahead and reduce the voltage back down to about 2.7 or so. The RAM will almost certainly run stable at these speeds. You'll find that these timings are pretty common with most other [email protected]

MSI K7T266 Pro2-RU - Memtest-86 Errors

Hi, I have two 256MB 266DDR's by VM (there's "Nanya" on the chips) and when running Memtest-86 V3.0, I get about 10-15 errors in test 10. This doesn't happen when I test the sticks alone, only when they are together. When searching for this I found that some ppl with Abit and ECS VIA KT266a boards had this problem, and the solution was like this:
* 1T Command - OFF
* DDR DQS Input Delay - 20
* DDR DQS Ouptut Delay - 40
* Command drive strength - Hi
But the BIOS of my mobo has only the first option to set, I tried to set it OFF and it didn't helped, same with changing DDR voltage to 2.7 volts.
Other options (CAS, RAS etc) are set by SPD.
All the errors in memtest are like this:
- all adresses above 256 MB
- no exact address had error more than 1 time (it's random)
- all adresses end with 5c, 9c, dc, 7c...
- The pattern Memtest wrote is f7f7f7f7 or 7f7f7f7f
- The pattern Memtest read is f7f7f7ff or 7f7f7fff

i have k7t266 pro2 aswell and had memtest errors too.
I solved the errors by loading bios defaults,not performance and setting memory timing to
2,2,5,2-most aggresive
settings
memory interleaving 2 way for 1 stick,4 way for 2 sticks.
sdram 1t command-disabled
fast command enabled.
Also clear nv ram in the bios after changing memory timings and reboot and retest,it worked for me,good luck.

Memtest crashes

Hello my friends,
MY system
P4 2.6 HT
1 gb twinmos twister cl2 dual kit pc 3500
msi 875p neo2 lsr (B0OS 1.9)
aopen H600B-13 case with 300watt psu
Today I bought new memorys which twinmos twister pc3500 cl2 and
turn on my pc and I set the timings 2-4-4-8 but in mem test give some errors then I try microsoft mem test but give some errors too.PAT=SLOW and 216*13=2.8ghz (433mhz ram) 1:1 and I try different voltages 2.65-----2,90 but everything bad and programs give some errors.Example 100 errors in memtest 50 errors microsoft mem test. and I
Then I went home and say my friend who have got my same ram(same cpu) and asus p800 and his rams is normal at 2-3-3-8 pat enabled and 3.ghz.
Then He try different settings but board don't change the ram timings We change 3-4-4-8 but mainboard is change too(2-4-4-8)
My friend says this errors is not normal and try different rams and everything is same.
Then I try this performance setting/give some errors memtest) on windows pc works great I played 1hour Halo then 2 hour need for speed and some 3Dmark03 tests works great.
This Board works on his had
I don't trust this board.In my opinion MSI to do false bioses and don't correct this errors example dot settings come on my board 2 days then go to havaii maybe then return 1 hour then goes
I don't understand this board working.

Ruckus17, Is 100% Correct. as I cant find Twinmos Twister CAS Latency 2 RAM anywhere on the (Supported RAM Page) and any, I mean ANY 300 Watt PSU is Going to be Very Questionable when it comes to Powering ANY i875P with a P4 that is Over 2.0GHZ and thats even if you have the minimum amount of additional Componants.....And if you Happen to Have a Powerful Vidio Card such as a ATI-9600+ , or Nvidia-FX 5600+ Series, I would be supprised if the System could even Boot, let alone Remain stable , You are Going to be Much more Successful with Maintaining Stability, if you upgrade to a Quality Powersupply that has the minimum Rail Specs. (in Amps) of +12V=18-20 Amps, +3.3V=30+ Amps, +5.0= 35Amps........And I mean that 18-20Amps on the +12V Rail is the Minimum...As these Days if you have a Powerful Vidio Card, That you are Constantly Pushing the 3D Mode of the GPU with Gaming or Vidio Editing, You should have Closer to 25 AMP Capability on the +12 Volt Power Rail...............Sean REILLY875

K9N Platinum and Corsair CM2X1024-6400 **UPDATE - FIXED**

I'm trying to help a friend with their new K9N Platinum motherboard. We got everything installed successfully, but after getting into Windows, the machine will just freeze up randomly doing anything, software install, whatever, within a minute, or sometimes as long as 5 or more minutes.
Basic specs:
K9N Platinum motherboard
Flashed to BIOS version 1.4
AMD Athlon64 X2 3800+ (65W) socket AM2
BFG Geforce 7900GS
500W PCI-E power supply
Wester Digital 120GB 7200rpm SATA HD 8MB cache
Single 1GB stick of Corsair CM2X1024-6400 RAM (DDR2 800MHz) - Brand New - DIMM slot 1
Windows XP Professional with SP2 and all windows updates installed. (using IE6)
Installed all latest drivers from MSI's website for this board.
We tried 1st with DRAM timings on auto, then tried to set the timing manually according to Corsair's spec sheet for this module, including memory voltage at 1.9V.
We think it might be a bad memory module, because after getting into Windows, we run memtest, and errors are detected within the 1st minute. We have RMA'd the RAM module. I'm wondering though if we just didn't have the timing for the memory set correctly in the BIOS.
Is anyone here runnning this exact memory successfully, or is this board incompatible with this Corsair module? If you are running successfully, did you have to change the SPD timings manually, or are you running using the SPD Auto setting?
If you had to use manual setting, any help with the values to set in DRAM Timing would be greatly appreciated. As much detail as you can provide would be great. Thanks for your help.

Ok, still having major problem with running world of warcraft. This PC freezes/locks up in the game every single time within 5-10 minutes of play no matter what we've tried so far. This is not a shutdown or restart problem, just a freeze/lock-up symptom. I'm getting a bit frustrated at this point. No other problems in windows are encountered. We can work in windows with any other application, like adobe photoshop or any other software, with zero trouble. I'm beginning to think this is video card related somehow with this 7900 GS card.
For added info, the video card being used is this;
BFG Tech BFGR79256GSOCE GeForce 7900GS 256MB 256-bit GDDR3 PCI Express x16 Video Card
Chipset Manufacturer NVIDIA
GPU GeForce 7900GS
Core clock 525MHz(vs. 450MHz standard)
PixelPipelines 20
Memory Clock 1320MHz
Memory Size 256MB
Memory Interface 256-bit
Memory Type GDDR3
3D API
DirectX DirectX 9
OpenGL OpenGL 2.0
Ports - DVI 2
The mouse used is a logitech USB track ball mouse if that has any bearing on anything. No mouse troubles though, just thought I'd mention it.
Here's what we've tried so far;
Updated to BIOS version 1.4. This was done after the Windows XP install though, so not sure if something is hosed up here.
1) We set the RAM timings to 5-5-5-12-2T and 2.1Volts in BIOS manually, as per direct recommendation from Corsair.
1a) Ran memtest all night for about 9 hours straight and no errors at all detected. So I'm guessing this isn't a RAM problem really, but who knows .
2) Installed the Windows XP SP2 Hotfix for Dual Core Processors - hotfix KB896256
3) Installed the AMD Dual Core Optimizer from here -->http://www.amd.com/us-en/Processors/TechnicalResources/0,,30_182_871_13118,00.html
4) Updated the Nvidia system drivers with the nForce 550/570/570/590 SLI (C51+MCP55) driver package 9.19 WHQL from MSI's website here--> http://www.msi.com.tw/program/support/download/dld/spt_dld_detail.php?UID=730&kind=1
5) Currently running Nvidia video driver version --> ForceWare Release 90 Version: 93.71 Release Date: November 2, 2006 WHQL Certified.
6) Ran a complete Direct X diagnostics via dxdiag. All tests passed successfully.
7) Tried to install the AMD Athlon™ 64 X2 Dual Core Processor Driver for Windows XP and Windows Server 2003 Version (x86 and x64 exe) 1.3.2.16 from here -->http://www.amd.com/us-en/Processors/TechnicalResources/0,,30_182_871_13118,00.html
But it would NOT install because it says I have to first uninstall the current driver via add/remove programs, but it's not listed there, before installing this one. So, I have no idea where to look or how to do this, I'm afraid of messing up the processor driver. Can someone explain how to install this driver, and would not having this installed possibly be a potential cause of the game lock-ups?
I don't know what else to do. Could the version 9.19 Nvidia SATA or IDE drivers I installed be causing these game lock-up problems? If so, do I just go into device manager and just rollback drivers for all of the devices listed under the "IDE/ATA ATAPI Controllers" in device manager?
Again, this was a fresh windows XP Pro install on a newly formatted hard drive. Obviously something is fubar, but I'm running out of things to try. Maybe going into BIOS and "load optimized defaults" and start over?
Lastly, the tech specs on newegg.com for this video card say "A 350W PCI Express compliant system power supply (with 12V current rating of 22A or more)" is needed. Since the 500W power supply we're using has 2 separate 12V rails rated at 20A each, could this be the problem?? I'm open to suggestions. Thank you.

MSI K8N Neo2 Platinum has some SERIOUS vdimm issues

I did this post to other forum as well and I can be sure I'm not the only one with this problem and this has effect only if you are overclocking your system. I really hope some of the guys from MSI reads this post and if does not we need to notice them about this problem.
The link to other forum can be founded here
Problem #1
When you select (from BIOS) Cell Menu -> DRAM Configuration -> RAS to CAS (Trcd) and change the value to "2" it seems like it forces voltage to 2,7V, no matter what you select your Memory Voltage from BIOS (use multimeter if you don't believe).
Problem #2 (long story but keep reading, it's worth of it)
I was just tweaking my system up and I tried desperately achieve higher clock speed to my CPU, tried kinda everything out I could, more Vcore, more Vagp/Vchip, more vdimm, looser memory timings, dividers, all this without result.
After a while, I got my CPU running rock stable at 2520MHz with 1,55V (3500+ NewCastle, 252x10), Memory voltage(VDIMM) 2,65V and I was using 5:4 divider so my ram was running with 3-3-3-5 timings at 210MHz(Max Memclock: 166 used), VAGP/Vchip 1,50V. This far, all prime stable, superpi stable, 3d stable, etc, no problems at all.
So, I decided to go 2530MHz and higher. I fired my HTT (FSB) to 253MHz and it booted up. Went fine, and after Windows started I first ran SuperPi8M, 3DMark05 and PCMark04, it all went thru fine. Then Prime95, gave me error after 16mins. I just thought that maybe it didn't get enough juice, so I gave some more. I gave like 1,6V to cpu and I thought it should be stable now, but just a 8 minutes after I started Prime, I faced this same error again. Back to BIOS and I lowered my HT Frequency to 3x and I tried again, and now it took 11 minutes and Prime failed. Only problem I could imagine now was my memory, so I used loose 3-4-4-8 timings and guess what, Prime gave me error after 2minutes. I was totally pissed off and I thought CPU can't go any further.
This was rock stable:
CPU: 2520MHz (252x10 / 1,55V)
RAM: 210MHz (3-3-3-5 / 2,65V)
VAGP: 1,5V
And this was not stable:
CPU: 2530MHz (253x10 / 1,6V)
RAM: 210,83 (3-3-3-5 / 2,65V)
VAGP: 1,5V
And now comes the funny part. After like 20th visit to BIOS I increased my VDIMM to 2,7V and this wasn't stable neither, it was like 10 minutes and Prime failed. Okey, so AGAIN, back to BIOS and I ACCIDENTALY decreased my VDIMM to 2,6V and... it was stable, I ran prime like 6 hours and 59 mins and it was all ok. After that I was like ":censored: I did?" I just decreased my VDIMM and now I'm able to do higher overclock. My system is now running 2550MHz (255x10) with 1,6V
So my stable system now looks like this:
CPU: 2550MHz (255x10 / 1,6V)
RAM: 212,5MHz (3-3-3-5 / 2,6V)
VAGP: 1,5V
Can none of you guys give me some info what the h--- is this?!

Quote
Originally posted by Zebbo
Quote
Originally posted by RollerCam540
Okay, let's try this again: I'm not a hostile guy and I didn't intend to offend your intelligence with my first post. I know you're thinking, why did I post the first post then, if I didn't intend to offend you? Well I'll tell you why:L
I'm truly sorry, I sometimes get nasty with these things. The "New member" under my name don't mean that I'm new to whole overclocking scene so that's why I don't need thus' Basic Overclocking Tips . And if I did hurt your feelings somehow, I'm sorry, I truly are. This was not what I planned this to be, I was just looking people with same experiences like I do.
Quote
Originally posted by RollerCam540
You are blaming the motherboard for something that I feel you cannot blame the motherboard for. Why do I say this?...
Well, I understand you feel way like that, but I've tried everything else and only thing I can come up to is motherboard. Like the CPU example you gave me, I can ignore it easily right here; The only thing this memory integrated controller does is data transfering, and as far as I know the motherboard handles the power circulation for memory, not the CPU.
Quote
Originally posted by RollerCam540
Yes, the fact that VDIMM goes up without your consent is wierd, that would qualify as an issue. I'm assuming since your a smart guy, you have the latest BIOS and/or you've researched/tested all BIOS' to determine which works fastest/best with your configuration.
I assume you referred with this to an Trcd issue. And I have nothing to say to that, you can test it out if you want and be sure to get multimeter so you can be 150% sure about it. I've also tried 1.36, 1,37, 1.4 official, 1.41, 1.51 and 1.5X bioses and they all give me same problem. Trcd 2 forces your voltage to 2,7V, no matter what choose from BIOS.
Quote
Originally posted by RollerCam540
For every guy you claim has trouble with their OCZ memory, there's a whole list of guys who're successfully using that memory in the A64 nvidia forum. Does this still mean it's a motherboard problem?
No, I don't have OCZ brand memory. I have Infineon by myself, so this far this has nothing to do with OCZ.
Example; I know alot of people who are using Kingston with this board and it's running all fine, I also know people who are running same set of Kingston as these peoples whos PC works great but still they are facing random memory problems. Same thing goes for OCZ too.
Quote
Originally posted by RollerCam540
Look, I would be upset if I couldn't go higher than 210mhz FSB but I wouldn't be blaming the motherboard if I didn't know it was the motherboard?
I always do my research well and I'm not blaming anything 'til I'm sure of what is causing my problem. But in this case, I'm that 150% sure it is motherboard. (And by the way, my mobo does 340 FSB Prime & 3D Stable so that's not an issue)
Quote
Originally posted by RollerCam540
I would hate to see you buy another motherboard only to find out the limiting factor was your CPU.
Don't be, cause I actually could do that to proof I'm right here and the issue is mobo
Quote
Originally posted by RollerCam540
Have you tried running your computer 1:1? Do you get any memtest/goldmem errors with it 1:1?
This was kind of stupid question (sorry :D), you can't run 1:1 divider with memory stick which has example PC2700 SPD information (you can do that with A64 Tweaker but no use if you're planning to do memtest). According to Asus report this is caused by A64's integrated memory controller.
So let say this one more time, the voltage of your memory has nothing to do with A64's integrated memory controller, your motherboard handles this. That's why I know this is motherboard related issue, not CPU, memory, PSU, or anyone else I didn't mentioned.
I guess you got some of the answer you wanted to hear, but if you got any xtra questions, feel free to ask. Maybe the best way is to contact me via Messenger.
I got to tell you that the A64s have a lot more to do with the memory than the boards do. The cpu really has to be matched to the memory and not all 3500+ cpus will run a certain type memory the same. I have tried several diffrent boards and several diffrent types of memory and it seems to me the cpu has more to do with not only the memory timings they can handle but the speed as well. Also cpu temps can make a diffrence here as well. Remeber the controllers are in the cpu. I would also say that the older 3500+ did not have as good of controllers.

Lack of power?

Hello everyone,
I've been reading this great forum to find some answers but I'm still confused (so forgive starting a new thread about this)
I have had random crashes mostly when browsing internet but sometimes also when doing something else. Everything works fine and then suddenly computer boots itself without bsod or anything. Usually when this happens internet connection stops working until shutting down computer and doing the powercord off -trick.
I've been thinking maybe this is psu related, but what really confuses me is that I NEVER have any problems playing hours games like Far Cry. Should't that be much more loading (not sure if thats the right word) for psu than for example browsing internet??
I've tested memory with Memtest, no errors.
I have also changed my keyboard from ps/2 to usb w an adapter.
I am not oc:ing.
Really would appreciate any advice before buying a new psu or something.

Quote
Originally posted by Paul Foster
Glad to hear your system runs Prime95 just fine. To me that's an excellent sign that your hardware is in decent shape and you have plenty of power.
Thanks mate , do you think it would be good to run Prime95 longer?
Quote
You didn't give the full system error log messages but if you google search and compare yours to others you should be able to find out more information about what's causing them.
I've been trying to and it looks like it could be a bad driver thing as you said. Maybe I should try reinstalling Windows and all drivers.

6714 Ver 1 BIOS issue : will not boot OS

Hi ya,
I'm wondering if there's a way to force the flash program to replace the BIOS even though it detects it as a different / incorrect version ?
Just having an interesting problem with an old(ish) MSI 6714 motherboard.
The system was installed and working fine on a users desk, however we replaced the 6714 machine with a newer one and were going to re-format 6714 system, re-install the OS and use it to replace another users system.
During the OS installation (Windows 2K SP3 corp media), after the first re-boot the system will blue screen with an error similar to IRQ_NOT_EQUAL_TO or something to that effect.
No matter how we installed the system it kept dying at the same point.
I tried ghosting a copy of the OS onto the HDD, however it gets to the initial 'Windows 2K press F8' part, the loading line flicks across, and then it hangs.
The machine always POSTS and always allows entry to the BIOS.
A strange thing is though, if you change the 'USB Mouse Support' option from Disabled to Enabled then the system POSTS as normal but dies before it even brings up the 'Windows 2K press F8' section.
Looking at the BIOS though I think this system has been installed with an 845GEM Bios, when it may have needed the 845GVM Bios instead .. as the board has no AGP slot.
I've found some other people in the Forum's who have encountered a similar issue, but none of the links in the replies have worked.
The current BIOS on the sustem is the 2003/05/07 845GEM v1.2 BIOS (4Mb)
There isn't an updated version of this BIOS, and this was the BIOS version that was on the system before I started messing around with it (I tried over-writting it again but it does the same thing when booting the OS).
To be honest I think I encountered the same problem when I first got the system, but I somehow got it working by ghosting a copy of the OS onto the system. That may have just been pure luck though .. as nothing I've tried has gotten this system to work.
Specs are :
AOpen H340D case
MSI 6714 Ver:1 (BIOS 845GEM v1.2 2003/05/07)
256Mb DDR266 (tested with MEMtest without error)
WD 300B/400B drives (we've tried a few)
Also tried it with a PCI graphics card to no effect.
All capaciters are flat and look in good condition.
All cables have been checked and changed.
Thanks ???

Thanks Greyone, but I think I found the problem.
In answer to your Q though, the chip in front of where the AGP slot should be has a sticker on it saying 845GV ICH4.
System was made up by one of our venders. But I'm not sure if they could have been the culprit for the incorrect BIOS though as they would have had to have forced the BIOS onto the system since it returns a BIOS-Lock error if you try the GEM Bios on a GVM system and vice versa.
I downloaded the MSI-6714 845GVM v4.2 bios and flashed it with the /f switch, and it seems to be running ok.
Windows 2K had to find all the hardware again (and required the driver files for the GFX card), but it does now seem to be running and stable (that is if you can call something stable thats only been running for 45 minutes thus-far )
Hope this post can help out anyone else who comes across this issue though.
Thanks

Ram/Resetting problems

A couple of days ago I bought 2x 512mb DDR 400 sticks of ram. The PC worked fine until I tried playing Battlefield Vietnam. At random times the PC would shutdown and restart by itself with no error messages. It has also happened while not playing games.
I ran memtest with both sticks in and got 5 error messages on test 10. So i decided to test them individually. 1 stick I ran for 14 hours and got no errors, and then I ran the other for 10 hours and got no errors. I then put both back in, ran memtest and got no errors after 9 hours.
Memtest showed these settings - CAS: 2.5-4-4-8/Single channel (64 bits)/Dimms 1 & 2/Non ECC
Im not sure what the CAS settings mean or what would happen if I changed them. Are these right? I looked on PNY's website and couldnt find any help with changing CAS settings or what the effects would be. From a few posts i've read i've noticed that people have changed their settings but i didnt want to do that without getting sum advice first.
Core Centre shows this: Vcore = 1.47v / 3.3v = 3.31v / +5.5v = 5.03v / +12v = 11.88v (but can peak at 11.97v or 12v)
could upgrading to the latest BIOS be worth a try 2?
any help would be greatly appreciated!

first suggestion i would have is use dimm slots 1 & 3 not 1 & 2 .. seams most 512mb sticks work best in those... if memtest runs error free with the mem timings on auto i would suggest you leave them on auto... only start changing them for stability reasons or if overclocking and then its usually to loosen then to say 2.5-4-5-8 for stability
hope that helps some as im no expert ... the memory guru's will surely be along soon

Windows 7 Random freeze

I recently purchased a new Mac Mini(599 model 2/4/12). Only hardware change i've done is upgraded to 8gb of RAM. I installed Windows 7 Professional(32bit) via USB drive with bootcamp(60gb set aside for it). Installation went just fine, and installed Windows. The only programs installed on the windows side is VS 2010 and MS Office 2010 for school work. The problem i'm encountering is that Windows will just randomly completely freeze and lock up. It does not reboot unless i manually reboot it. This problem will come just 20 minutes after being on windows to sometimes not until i'm on it for 1-2 hours. It is not program specific of what i'm doing to freeze up, but i've noticed two times it has done it when i'm either moving a large file(~2gb) from a flash drive to the HDD, and when i was downloading adobe design standard(~2.3gb download). Any help is greatly appreciated.

DRAMV is 2.0
I ran memtest no errors, two hours prime94 nothing.
Know after computer restarts I received the following message:
Windows has recovery after blue screen:
Problem signature:
Problem Event Name: bluescreen
OS Version: 6.1.7600.2.0.0.256.1
Local ID: 1033
Additional information about the problem:
BCCode: d1
BCP1: 0000000000000008
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF8800162558D
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Files that help describe the problem:
C: \ Windows \ Minidump \ 012410-35812-01.dmp
C: \ Windows \ Temp \ WER-36859-0.sysdata.xml
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C: \ Windows \ system32 \ en-US \ erofflps.txt
How do I attach this files on this post, because i don't know how to open the file with extension DMP and the xml is not tell me anything. if someone could help me i appreciate! THX
it seems i have a software problem!!!

BSOD Vista x64 After Waking from Sleep

Hi. I recently re-installed my OS after purchasing a new MB (ASUS P8277-M LGA 1155). I in stalled a fresh (/mbr format) copy of WIN Vista x64. After my computer awakens from sleep mode a BSOD occurs. I've tried troubleshooting the issue with winDBg; however,
I cannot resolve the issue. The output from my dump file is below. Please let me know the next steps I should take to resolve this issue.
Thanks,
Chris
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini021214-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6002.18881.amd64fre.vistasp2_gdr.130707-1535
Machine Name:
Kernel base = 0xfffff800`01c15000 PsLoadedModuleList = 0xfffff800`01dd9e30
Debug session time: Wed Feb 12 19:04:50.893 2014 (UTC - 6:00)
System Uptime: 0 days 10:27:05.946
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck F4, {3, fffffa800c74a710, fffffa800c74a948, fffff80001ea5870}
Probably caused by : csrss.exe
Followup: MachineOwner
0: kd> !analyze -v
* Bugcheck Analysis *
CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa800c74a710, Terminating object
Arg3: fffffa800c74a948, Process image file name
Arg4: fffff80001ea5870, Explanatory message (ascii)
Debugging Details:
PROCESS_OBJECT: fffffa800c74a710
IMAGE_NAME: csrss.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: csrss
FAULTING_MODULE: 0000000000000000
PROCESS_NAME: csrss.exe
EXCEPTION_CODE: (NTSTATUS) 0x114adbb0 - <Unable to get error code text>
BUGCHECK_STR: 0xF4_114ADBB0
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
STACK_TEXT:
fffffa60`023421a8 fffff800`01f6cb63 : 00000000`000000f4 00000000`00000003 fffffa80`0c74a710 fffffa80`0c74a948 : nt!KeBugCheckEx
fffffa60`023421b0 fffff800`01f1c380 : fffffa80`114adbb0 fffffa80`114adbb0 fffffa60`02342c20 fffffa60`02342a40 : nt!PspCatchCriticalBreak+0x93
fffffa60`023421f0 fffff800`01ec2a98 : fffffa80`114adbb0 00000000`00000008 fffffa60`02342c20 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x103a6
fffffa60`02342240 fffff800`01c6bbf3 : fffffa80`0c74a710 fffffa80`114adbb0 fffffa60`02342320 fffffa60`02342c20 : nt!NtTerminateProcess+0xd8
fffffa60`023422a0 fffff800`01c6c100 : fffff800`01cce59d fffffa60`02342b78 fffffa60`02342ca0 fffffa60`02342c20 : nt!KiSystemServiceCopyEnd+0x13
fffffa60`02342438 fffff800`01cce59d : fffffa60`02342b78 fffffa60`02342ca0 fffffa60`02342c20 00000000`014915a0 : nt!KiServiceLinkage
fffffa60`02342440 fffff800`01c6bfa9 : fffffa60`02342b78 00000000`00005d2c fffffa60`02342c20 00000000`01491ba8 : nt! ?? ::FNODOBFM::`string'+0x2942c
fffffa60`02342a40 fffff800`01c6ada5 : 00000000`00000000 fffffa60`02342ca0 00000000`00000001 00000000`00005d2c : nt!KiExceptionDispatch+0xa9
fffffa60`02342c20 00000000`7767320e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x1e5
00000000`014914c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7767320e
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0xF4_114ADBB0_IMAGE_csrss.exe
BUCKET_ID: X64_0xF4_114ADBB0_IMAGE_csrss.exe
Followup: MachineOwner

cperry11
9 of 11 were related to memory corruption. Please run these 2 tests
These crashes were related to memory corruption (probably caused by a driver).
Please run these tests to verify your memory and find which driver is causing the problem.
If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you dont
know what it is you probably are not overclocking.
1-Memtest. (You can read more about running memtest here)
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Get it here
Boot from the CD, and leave it running for at least 5 or 6 passes.
Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.
Test the sticks individually, and if you find a good one, test it in all slots.
If a known good stick fails in one motherboard slot but not another it is probably the slot.
2-Driver verifier (for complete directions see our wiki here)
Using Driver Verifier is an iffy proposition.
Most times it will crash and it will tell you what the driver is, but sometimes it will crash and won't tell you the driver.
Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).
Here is the procedure:
Go to Start and type in "verifier" (without the quotes) and press Enter
Select "Create custom settings (for code developers)" and click "Next"
Select "Select individual settings from a full list" and click "Next"
Select everything EXCEPT FOR "Low Resource Simulation"
For Win 8 dont check Concurrency stress test, and DDI compliance checking click "Next"
Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Co-Authored by JMH3143
Wanikiya and Dyami--Team Zigzag

Mac Pro memory problems, or...?

I've been experiencing intermittent "goofy behavior":
1. fine horizontal black line across a window, today I had one half across the menu bar.
2. hangs -- i.e., will not respond to any keypress, mouse click, etc.
3. in the course of working through the usual list of troubleshooting steps I discovered that my Mac Pro does not recognize any of the startup keys http://option, cmd-opt-PR, shift, cmd-S, ...
- I have substituted an older Mac keyboard for the aluminum keyboard - still no startup keys
4. I've done the usual preferences, disk maintenance, etc.;
5. I can't run Hardware Test due to non-functioning startup keys [need D key for h/w test]
6. When the CPU wouldn't wake from sleep I got the below post-restart report.
7. I've run memtest two full nights, no errors detected.
8. I've removed the 2GB of OWC extra memory, running with Apple stock 1GB to see...
Any suggestions that may accelerate isolation would be much appreciated. Restart report follows:
Fri May 16 15:04:18 2008
panic(cpu 1 caller 0x00192EE1): "pmapflushtlbs() timeout: " "cpu 0 failing to respond to interrupts, pmap=0x534500 cpustosignal=1"@/SourceCache/xnu/xnu-1228.4.31/osfmk/i386/pmap.c:4570
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x5b44f8a8 : 0x12b0f7 (0x4581f4 0x5b44f8dc 0x133230 0x0)
0x5b44f8f8 : 0x192ee1 (0x45e364 0x0 0x534500 0x1)
0x5b44f968 : 0x194033 (0x534500 0x3baed000 0x0 0x19d709)
0x5b44fa08 : 0x173f7b (0x4cb8c 0x0 0x5b44fa58 0x1653b6)
0x5b44faa8 : 0x169d64 (0xa06cdac 0x0 0x0 0x1000)
0x5b44fbc8 : 0x16a361 (0x3baee000 0x0 0x1 0x0)
0x5b44fc08 : 0x16b2b6 (0x1921e10 0x3baed000 0x0 0x3baee000)
0x5b44fce8 : 0x127703 (0x1921e10 0x3baed000 0x0 0x8)
0x5b44fd78 : 0x14c0ae (0x5c2eee8 0x74d499c 0x74d49bc 0x74d49a8)
0x5b44fdb8 : 0x12d17b (0x74d40ac 0x74d4980 0x0 0x0)
0x5b44fdf8 : 0x12625d (0x74d4000 0x0 0x18 0x5b44fee4)
0x5b44ff08 : 0x1972ea (0x5b44ff44 0x0 0x0 0x0)
0x5b44ffc8 : 0x19f2b3 (0x61d45a0 0x0 0x1a20b5 0x6f95f20)
No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbfffe898
BSD process name corresponding to current thread: pmTool
Mac OS version:
9C7010
Kernel version:
Darwin Kernel Version 9.2.2: Tue Mar 4 21:17:34 PST 2008; root:xnu-1228.4.31~1/RELEASE_I386
System model name: MacPro1,1 (Mac-F4208DC8)

OK, updated the ATI drivers. I did NOT get auto-updated by Software Update. For ref, now have
ROM Revision: 113-A52027-202
EFI Driver Version: 01.00.202
Sadly, still seeing video artifacts -- I now have some evidence these are RAM-related.
Memory config when the video artifacts started was:
A-1 Apple 512MB
A-2 Apple 512MB
B-1 OWC 1GB
B-2 OWC 2GB
I ran for a while with OWC removed -- still saw artifacts, though possibly less frequent.
After fixing the startup key problem I was able to run the Hardware Test extended test this AM. Which reported no errors.
I then swapped OWC and Apple -- ran for several hours with no artifacts, then "screen rash" reoccurred followed very shortly by a hang [no mouse nor keyboard input], hard restart.
I've run the digLloyd run-stress-test to heat up RAM, then Rember/memtest -- no errors.
Does anyone know definitely whether RAM Riser A or B is used first?
Other suggestions?
Cheers, Steve

ITunes crashes entering the store

I have removed iTunes with Appzapper and installed fresh from Apple download. OSX version is 10.5.8, iTunes is 10.6.3 (25). The music library works just fine, but it crashes every time trying to enter the store. I have exhausted my abilities to troubleshoot this issue, and would greatly appreciate assistance. I have a crash report I captured this morning. I reviewed logs in console app and only found crash reports. All crash reports show kern_invalid_address as error code. I ran iTunes again, selected store, waited for it to crash, and viewed latest entries in system.log. Segmentation fault shows as expected from the invalid address error code. Normally this would point to memory but iTunes is the only item with any issues and even then the only issue I have is with store access. Internet access, internal network access all work perfectly well. Any guidance would be greatly appreciated.

Ran memtest, no errors detected. I'm thinking I have a code issue.

Memtest 86+ Errors (v1.60)

Similar Messages

Maybe you are looking for