[callisto9]

here are my specs: dell inspiron 1420, just added an additional 1GB of RAM yesterday. vista home premium. have had the laptop about two months now. installed adobe creative suite 3 a few days ago. used limewire last night. been running media monkey, surfing the web, picasa, gmail, etc.

in the past 24 hours, i've had 2 BSODs. i just replaced my two 512MB sticks of RAM with two 1GB sticks of RAM, but i'd been having problems before that. however, they seem to be more serious now.

i can't read the error on the blue screen since it's only up for a second, but i did get this upon my machine rebooting:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6000.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 1000008e
BCP1: C0000005
BCP2: 81CD8EC0
BCP3: AEE89844
BCP4: 00000000
OS Version: 6_0_6000
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\Mini011908-02.dmp
C:\Users\erin\AppData\Local\Temp\WER-25630-0.sysdata.xml
C:\Users\erin\AppData\Local\Temp\WER842C.tmp.version.txt

Read our privacy statement:
http://go.microsoft.com/fwlink/?link...3&clcid=0x0409

any help? i'm about ready to chuck this thing out the window.

[Rich-M]

But have you been having the same problems and have you had BSOD's before changing the ram?
I would bet the ram is not compatible, where did it come from and did you check a configurator to be certain it is compatible.

[callisto9]

Originally Posted by Rich-M

But have you been having the same problems and have you had BSOD's before changing the ram?
I would bet the ram is not compatible, where did it come from and did you check a configurator to be certain it is compatible.

i did not have any BSODs before the RAM upgrade. i got the RAM from newegg and it's the exact same specs as what i had. DDR2 SODIMM @ 667mhz 200 pin.

i ran memTest and i immediately got errors on the new RAM. i have put back in the old RAM (came with my dell) and we'll see how it goes from here. i did not get any immediate errors.

could bad RAM cause those kinds of errors?

[Rich-M]

OK you did not buy the same ram you bought the same speed and unfortunately that has little to do with compatibility. You need to go to www.crucial,corsair or kingston .com and put in your pc brand name and they will match the ram desnity, ecc factor and cas latency you need. Get the models and you can buy anywhere including Newegg but buy the exact models recommended only.

[callisto9]

Originally Posted by Rich-M

OK you did not buy the same ram you bought the same speed and unfortunately that has little to do with compatibility. You need to go to www.crucial,corsair or kingston .com and put in your pc brand name and they will match the ram desnity, ecc factor and cas latency you need. Get the models and you can buy anywhere including Newegg but buy the exact models recommended only.

i bought 1GB 200-pin DDR2 SO-DIMM at 667mhz. PC2-5300

my dell takes: http://www.newegg.com/Product/Produc...82E16820148086
according to the crucial memory checker. i believe these are the same kinds of RAM, right?

[callisto9]

i've also had the following happen since i put the original RAM back in:

01.19.08 changed back to original RAM.

01.19.08 8:06pm
firefox is not responding. i was trying to get an RMA on newegg.com and firefox crashed. i now have a white bar going across my screen.

01.19.08 8:16pm
internet explorer has stopped working. this happened as soon as i opened it up.

01.19.08 8:33pm
firefox has stopped working. happened when i clicked on a link in an email.

[callisto9]

i've also got this stuff in event viewer.

Activation context generation failed for "C:\Windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.163_no ne_0c187ef99ee1d25a\MFC80U.DLL". Dependent Assembly Microsoft.VC80.MFCLOC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a 1e18e3b",type="win32",version="8.0.50608.0" could not be found. Please use sxstrace.exe for detailed diagnosis.

The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume OS.

Faulting application iexplore.exe, version 7.0.6000.16575, time stamp 0x470c3339, faulting module kernel32.dll, version 6.0.6000.20608, time stamp 0x465cf04b, exception code 0xc0000005, fault offset 0x00047378, process id 0x9f4, application start time 0x01c85b0a725a5feb.

The program firefox.exe version 1.8.20071.12718 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Problem Reports and Solutions control panel. Process ID: a6c Start Time: 01c85b061a522394 Termination Time: 92

[Rich-M]

Yes they are similar...but the issues sound more like bad hard drive now. I would run checkdisk as suggested next.

[callisto9]

ran bitdefender. one little virus in a cellphone game. game deleted. i've had that game on my system for a few years and never used it, so i'm guessing that's not the problem.

up next, check disk!

memTest did give me several errors about my corsair RAM i got from newegg. just for the record.

and btw, thank you so much for all your help. i really appreciate it!

[callisto9]

the results of chkdsk are (the stuff worth pointing out):

"Index entry jap.ytr in index $I30 of file 128103 is incorrect.
,,,
Errors found. CHKDSK cannot continue in read-only mode."

now what? it just closed real quick after that. i had to run it twice to get a screen shot of the text.

[callisto9]

Originally Posted by callisto9

the results of chkdsk are (the stuff worth pointing out):

"Index entry jap.ytr in index $I30 of file 128103 is incorrect.
,,,
Errors found. CHKDSK cannot continue in read-only mode."

now what? it just closed real quick after that. i had to run it twice to get a screen shot of the text.

ran chkdsk /f and it seemed to fix the jap.yrt thingie. the rest of the stuff i couldn't catch 'cause it went by so fast and then windows vista loaded.

i guess i'll wait and see now.

[Rich-M]

Are the problems still there though as I would return any ram if there is a single Memtest error.

[callisto9]

Originally Posted by Rich-M

Are the problems still there though as I would return any ram if there is a single Memtest error.

i am returning (exchanging the RAM). already filed an RMA. we'll see how it goes from here. hopefully the new RAM won't cause problems, too.