![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
-
Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.
Got a BSOD in XP
- Thread starter Gibson
- Start date
TheMostWantedPolishTwin
Supreme [H]ardness
- Joined
- Sep 16, 2000
- Messages
- 6,206
run memtest86...
BUHEEEEEEEERRRRRRRRRRRRD
29 errors!
Test 5 [Block move, 64 moves, cached]
This test stresses memory by using block move (movsl) instructions
and is based on Robert Redelmeier's burnBX test. Memory is initialized
with shifting patterns that are inverted every 8 bytes. Then 4MB blocksof memory are moved around using the movsl instruction. After the moves are completed the data patterns are checked. Because the data is checked only after the memory moves are completed it is not possible to know where the error occurred. The addresses reported are only for where the bad pattern was found. Since the moves are constrained to a 8MB segment of memory the failing address will always be lest than 8MB away from the reported address. Errors from this test are not used to calculate BadRAM patterns.
29 errors!
Test 5 [Block move, 64 moves, cached]
This test stresses memory by using block move (movsl) instructions
and is based on Robert Redelmeier's burnBX test. Memory is initialized
with shifting patterns that are inverted every 8 bytes. Then 4MB blocksof memory are moved around using the movsl instruction. After the moves are completed the data patterns are checked. Because the data is checked only after the memory moves are completed it is not possible to know where the error occurred. The addresses reported are only for where the bad pattern was found. Since the moves are constrained to a 8MB segment of memory the failing address will always be lest than 8MB away from the reported address. Errors from this test are not used to calculate BadRAM patterns.
MTB2Live Live4Comps
[H]ard|Gawd
- Joined
- Dec 27, 2002
- Messages
- 1,968
what brand of memory? timings? speed? it's possibly loosening the timings a bit could help things up if it only happens in stressed situations
If you have errors in memtest your RAM is likely bad. If you have more than one stick test them separatly. A combination or order of sticks can cause errors, so testing them one by one may come up clean. This means you have a RAM mismatch, one stick just wont play nice with another. If only one tests bad (or multiple test bad by themselves) move them to another machine. This will test the mobo/CPU as they can introduce errors too...
I tested each stick seperately. The brand is just PNY stuff on account I used to work for best buy. I tested the one and got like 30 errors, I tested the other and got like 100+
Yet I reinstalled battlefield completely and it has yet to do it again...
Yet I reinstalled battlefield completely and it has yet to do it again...
Memtest isn't lying. 
You have memory errors in your system. At this point you really-really need to test each stick, one-by-bye, in another machine, find one.
This will show you the RAM or something else is to blame. Usually memory errors are caused by RAM, then CPU, then mobo, in that order.
You have memory errors in your system. At this point you really-really need to test each stick, one-by-bye, in another machine, find one.
This will show you the RAM or something else is to blame. Usually memory errors are caused by RAM, then CPU, then mobo, in that order.
I've seen an error similar to this one where in Test 5 I recieved memory errors on a stick of ram that was supposed to be 2/2/2/5/1T. Generally the error would occur anytime a game was being played like MOHAA or BH1942 or Empire Earth. Anyway, the solution was to adjust the timings to a less agressive CAS 2.5. If you are already running 2.5 CAS, I would recommend seeing if your motherboard supports adjust Vdimm voltage to ram. Try putting VDIMM to 2.6 if its only set to 2.5Volts. It won't really hurt the ram at all, but might give it enough juice to run at the timings you want. You might even be able to adjust it up further on the Voltage, but I wouldn't recommend any higher voltage without knowing first what kind of ram you are using and what the manufacturer's specification says about that ram's voltage. If you still have problems after adjusting down timings, try reseting your bios to Fail SAFe settings and using the lowest timings possible for the ram. See if it can work under that setting and if you don't recieve errors just adjust your settings slowly to more agressive timings until you find its optimal operation mode.
One more thing, if you just bought the ram and its supposed to be running at some agressive timings, you might consider returning it if you can for RMA replacement as you might have a stick that isn't up to the advertised specifications.
[Edit] Oh yea one more thing, are these 2 sticks you have the same memory type/size/manufacturer? [/edit]
Good luck
---John
One more thing, if you just bought the ram and its supposed to be running at some agressive timings, you might consider returning it if you can for RMA replacement as you might have a stick that isn't up to the advertised specifications.
[Edit] Oh yea one more thing, are these 2 sticks you have the same memory type/size/manufacturer? [/edit]
Good luck
---John
CVNet1,
Welcome to the thread, you may want to read it. Everything you said is a repeat of things already covered, even your quesitons...
Except the voltage change, which really, really isn't standard memory diag. That's just like changing the timings, which you even said to RMA it if it's not working at rated speeds. It may get it working, but only prooves the RAM is bad and needs to be replaced.
Welcome to the thread, you may want to read it. Everything you said is a repeat of things already covered, even your quesitons...
Except the voltage change, which really, really isn't standard memory diag. That's just like changing the timings, which you even said to RMA it if it's not working at rated speeds. It may get it working, but only prooves the RAM is bad and needs to be replaced.
Carnival Forces
Supreme [H]ardness
- Joined
- Feb 9, 2003
- Messages
- 4,297
RMA RAM
Actually Phoenix86, it doesn't necessarily prove what you said. There are a few factors that aren't up on here. First off you don't know if his PSU is supplying the correct voltage value to come out a to a Vdimm of 2.5~2.6. There is a possibility that he's undervolted already. A second factor you don't know is how good the 3 phase power system on his motherboard is functioning, it might also lead to undervoltage on the Vdimm. BTW, upping the voltage for the ram within the specifications does not indicate you have bad ram, I'll use for example the Kingston HyperX BH-5 PC3200 ram I got for a friends P4 3.0C and Abit IC7-G Max3 system. Running Dual Channel and sychronous with the 800Mhz FSB of that system, I encountered severe system instability at 2.6V Vdimm. The solution there was to up the Vdimm to 2.7 and all the problems ceased. Of course the Kingston HyperX is rated for up to 2.9 so I was well within the specifications, but the fact that I had to up the Vdimm does not indicate that those sticks of Ram were bad.
Now regarding my questions, I didn't see the part where he listed the PNY ram so do forgive the repeated question (of course PNY makes multiple types of PC2100 DDR ram, which would all have different model #'s, but no matter), your sarcasm though was completely unnecessary.
Now regarding my questions, I didn't see the part where he listed the PNY ram so do forgive the repeated question (of course PNY makes multiple types of PC2100 DDR ram, which would all have different model #'s, but no matter), your sarcasm though was completely unnecessary.
I actually didn't piece this particular system together, It was originally bought from BBY. Although one weird thing is the only game that does this is BF1942. And only after I install the update. And only after I've been playing for a minute or two.
Weirdness abounds eh?
Weirdness abounds eh?
If you were fortunate enough to get the PSP on the computer, you'd have new RAM for the computer by now.
If your BBY isn't too far from your home, I would take the RAM there and have them test it. They should have the tools to do it.
Since I do work on the pieces of crap we sell, what mfr/model of computer did you get?
If your BBY isn't too far from your home, I would take the RAM there and have them test it. They should have the tools to do it.
Since I do work on the pieces of crap we sell, what mfr/model of computer did you get?
I DO have a PSP on it. Hell the thing only cost me like $20 so of course I got it lol. It's just that they're solution is step 1: reformat HD, step 2: see if it still does it. Which I'm not a fan of backing up my whole HDD right now...
And it's an HP CTO from about a year and a half ago.
And it's an HP CTO from about a year and a half ago.
Got to agree with you on upping the voltage, but since it's a HP computer, I doubt it will have that option in the BIOS. An its probably already running pretty conservative memory timings.
Flame Disclaimer: I am basing these assumptions on a HP computer circa 2002
CVNet1,
Thats why I said "You have memory errors in your system. At this point you really-really need to test each stick, one-by-bye, in another machine, find one." That will change the platform and test the RAM alone. If the RAM errors out on two different machines it's bad. That is why I said jacking around with voltages really isn't SOP. The timings were already discussed, like the brand of RAM. I a being sarcastic, yes, sorry about that. It just looked like you read the first post and started to reply without reading what everyone else said.
Thats why I said "You have memory errors in your system. At this point you really-really need to test each stick, one-by-bye, in another machine, find one." That will change the platform and test the RAM alone. If the RAM errors out on two different machines it's bad. That is why I said jacking around with voltages really isn't SOP. The timings were already discussed, like the brand of RAM. I a being sarcastic, yes, sorry about that. It just looked like you read the first post and started to reply without reading what everyone else said.
Well I took her down to BBY today and we swapped out the memory for brand new crucial RAM. and it STILL gave the error! They wanna send my computer out to service, but I know what happens at service so I'm gonna ghost my HDD, and see if I can't think of any other solutions first.
Carnival Forces
Supreme [H]ardness
- Joined
- Feb 9, 2003
- Messages
- 4,297
lol, gotta make sure that your comp doesn't drop the soap in the service shower room, eh?
?? Maybe your service center isn't like ours. We haven't lost a unit since September's 'Direct to vendor' fiasco. We obviously don't do that anymore. If a customer is worried about their data we generally will ghost their hard drive ourselves.
Well I left BBY back in march 2003 so I dunno how things've been since then but man when they went out to service they came back in SOB(straight outta box) fashion. All custom hardware removed and harddrive wiped clean and reimaged.
Yeah, pretty much...
Yeah, pretty much...