memory issues

[jason1488]

Subject: memory issues
From: "jason1488" <[email protected]>
Sent: 8/1/2004 6:08:09 AM




ive got a kt6delta mobo w/ winxp pro and a nividia fx5200
256 mb graphics card.had 512 cl2.5 pc2700 and tried to put
512 cl3 pc3200 in and i keep getting device and gaphics
device driver errors.i put the pc2700 back in no errors.im
running 3dmark03 to test system.it crashes on the first
test w/ pc3200 cl3 and runs fine w/ pc2700cl2.5.ive got
the newest bios on my mobo and the newest drivers from
nividia.ive also tried several other navidia drivers.??????
im abotu out of ideas .my mobo supports the memory i
have.its kingston value ram and was suggested by msi web
site.i dont know why memory would cause graphic driver
errors??????????????????????????????????????

 

[Malke]

Subject: memory issues
From: "jason1488" <[email protected]>
Sent: 8/1/2004 6:08:09 AM




ive got a kt6delta mobo w/ winxp pro and a nividia fx5200
256 mb graphics card.had 512 cl2.5 pc2700 and tried to put
512 cl3 pc3200 in and i keep getting device and gaphics
device driver errors.i put the pc2700 back in no errors.im
running 3dmark03 to test system.it crashes on the first
test w/ pc3200 cl3 and runs fine w/ pc2700cl2.5.ive got
the newest bios on my mobo and the newest drivers from
nividia.ive also tried several other navidia drivers.??????
im abotu out of ideas .my mobo supports the memory i
have.its kingston value ram and was suggested by msi web
site.i dont know why memory would cause graphic driver
errors??????????????????????????????????????

Kingston Value RAM often causes problems. Try a different brand of RAM,
making sure it is correct for your motherboard. Do not overclock the
new RAM.

Malke

 

[Alex Nichol]

ive got a kt6delta mobo w/ winxp pro and a nividia fx5200
256 mb graphics card.had 512 cl2.5 pc2700 and tried to put
512 cl3 pc3200 in and i keep getting device and gaphics
device driver errors

XP is very fussy about exact matching of memory modules, and you appear
to have got two that do not match well enough. You *might* get away if
you go to BIOS setup and set the CAS Latency up to the higher figure (3)