ram problems

[psychonaut13]

i don't know why the fuck this keeps happening, but it's making me crazy.

i had a gig of ram in my machine, 1 512 stick and 2 256 sticks. it ran fine, but then i lost my 512 stick for some reason...it just.....went bad i guess. so i went through all this madness to get another 512 stick, made sure that i had the right kind of ram for my mother board and everything but the damn machine kept having weird errors having to do with the memory so i took it back and got another one, 2 times! same problem every time. computer locks up for no reason or goes straight to blue screen with a irq not equal or some shit. anyway, i got another 256 stick last week, every thing ran fine for like 5 days and then it started hanging up and crashing on me again. the only thing that had changed was the stick being put it. but i'm sure that i'm using the right ram....at least i think i am.

here is a link to my mobo if someone could look at that and tell me wtf is going on i'd greatly appreciate it. the stick that i'm having issues with is...pc2100U and i'm pretty sure it should work.

so wtf?

 

[DiLLa]

i dont know enuff about cpus to help you with that one man :/

 

[psychonaut13]

this is the event viewer error info all greek to me

0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 38 1000008
0020: 65 20 20 50 61 72 61 6d e Param
0028: 65 74 65 72 73 20 63 30 eters c0
0030: 30 30 30 30 30 35 2c 20 000005,
0038: 38 30 35 38 34 36 39 66 8058469f
0040: 2c 20 66 32 32 66 63 62 , f22fcb
0048: 64 63 2c 20 30 30 30 30 dc, 0000
0050: 30 30 30 30 0000

Error code 1000008e, parameter1 c0000005, parameter2 8058469f, parameter3 f22fcbdc, parameter4 00000000.

 

[rocklee]

Could you possibly post the Brand and model of the ram you bought? That would help also.

Or a link to the ram you bought?

 

[psychonaut13]

this is everything it says on the ram

korea 0249
PC2100U-25330-A0
M368L3223CTL-CB0
256MG DDR PC2100 CL2.5

 

[Puppet]

I know you guys are stuck on this being a memory incompatibility issue, but how's about you entertain that it might be something else? My first question would be, are the 4 parameters after the bugcheck 0x1000008e always the same every time it happens? Secondly, technet article 893239 says this can happen on XP and the fix is to install Service Pack 1. Also, a cursory look at the parameters after the bugcheck shows that it crapped out in kernel space but the routine that called it is in trap frame f22fcbdc, which I'd be willing to bet is held by a device driver. You should be able to use pstat.exe to find out what driver holds that space. Just some thoughts in case this isn't related to your memory sticks.

 

[Hypnos]

Damn puppet....was that for real or were just making up alot of complicated bullshit? Cause it sounded like you either REALLY know what the deal is or your REALLY good and making up some insane bullshit.

 

[Puppet]

No, I actually get paid for spouting off bullshit. Life is grand.

 

[Hypnos]

After examining the hex dump error log.cfg.txt. I would suggest that the problem lies in the root sectors of the biniary quad unit located within the flux capacitor. The most logical corse of action would be to recompile the dump code after splicing the config.bat with the hex animator, but don't, of course, forget to restart the computer first. And that should solve the problem.


Can I have your job now puppet?

 

[psychonaut13]

I know you guys are stuck on this being a memory incompatibility issue, but how's about you entertain that it might be something else? My first question would be, are the 4 parameters after the bugcheck 0x1000008e always the same every time it happens? Secondly, technet article 893239 says this can happen on XP and the fix is to install Service Pack 1. Also, a cursory look at the parameters after the bugcheck shows that it crapped out in kernel space but the routine that called it is in trap frame f22fcbdc, which I'd be willing to bet is held by a device driver. You should be able to use pstat.exe to find out what driver holds that space. Just some thoughts in case this isn't related to your memory sticks.

thanks for the idea and all man but wtf does that mean?

 

[psychonaut13]

i found a copy of pstat.exe, downloaded it and ran it, but it just runs like mad and then the window shut down.

 

[Defender]

WOW maybe you can help me out puppet. I had a gig dual channel ram in my dell but the system crashed way too much especially when I played CZ and HL2. It even crashed when I ran programs like Fireworks.

So I swapped all the chips (4 in total of exact brand, type, and speed) and no matter what combo I was in it crashed. It was running as dual-channel I think at 333mghz.

Eventually I went to 512 dual channel and all was fine but I did see a performance drop. Recently I decided to try and add a single chip so now I am at 768 and the system doesn't ever crash. I am of course not in dual-channel mode though.

What do you think I should do? Is there a test I can run when I have the 1 gig dual-channel installed?

 

[Ind3lible]

Damn puppet....was that for real or were just making up alot of complicated bullshit? Cause it sounded like you either REALLY know what the deal is or your REALLY good and making up some insane bullshit.

Didn't you know that Puppet is our clinically insane PuNx. He play CZ in a padded room wearing a straight-jacket.

 

[psychonaut13]

so what you're saying is that i need to install service pack 1? does that mean i need to UNinstall service pack 2??

 

[Puppet]

i found a copy of pstat.exe, downloaded it and ran it, but it just runs like mad and then the window shut down.

Geez. Do this. Pipe it to a file and then read the file. The drivers are at the bottom and it will tell exactly what space the driver occupies in your computer. Find the one that occupies the area around f22fcbdc. The first thing I would do is get the latest version of that driver. Hey, this may not lead to your problem but you have to look at more that the memory when you get one of these bugchecks. Drivers are by far the most common cause of bugchecks.