• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

--New MEM!! Help Me!!--

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

Starfoxer

World's Biggest E-Thug
Joined
Feb 9, 2002
Location
USA
Hey all. I finally got my Mushkin pc3000 from newegg.
I installed it, and unlocked my CPU.

it ran fine at 7x166 but i bumped the multi to 9 and i never
got a post, or a boot, just a black screen.

i whiped off the conductive grease and cleaned my XP
off real good. works fine, but only on normal bios settings.

i tried to run it at what my crucial was at. cas 2, and 2-2-5-2-1
@ 155fsb. no go. it would boot the first time, but once i got
out of the bios i got this BSOD error message.

PAGE_FAULT_IN_NONPAGED_AREA

so i reboot like it says and it also says change hardware blah blah
the usual BSOD.

it hangs up on where it would check my drives and all and
where it would say "DEL to enter BIOS and F1 to continue"
it says "F1 to continue and DEL to skip memor"

it hangs up there and i can't press DEL or F1, totally frozen.
so i reset CMOS and all is well at stock everything.

i also have a new 430W antec true power PSU if that makes
any difference which seems to be doing fine. my CPU temps are
fine at 34-39.

Running on Windows XP home edition

ANY help at all would be greatly appreciated as i really wanted
to push this mushkin. just ask if you need more info, THANKS! :p
 
Have you tried putting your old mem back in and reclocking??.. It sounds to me that another problem has surfaced.. I dont usually hear of memory of that quality giving this kind of trouble.. I have no experience with muskin but i hear its as good as corsair.. the pc3000 should goto 200 fsb or better..
BTW changing the multiplier should have zero affect on ram. so going from 7 to 9 on mult couldn't cause tam failure
 
no i havent tried the the crucial again but i guess i will later.
i tried putting my swap file to 512/512 and now i get BSODS
with ACPCI.SYS and them some BSODS with codes like
0x000000007e........ etc

so i set it all back to stock settings and it's fine now.
any help would be greatly appreciated. thanks walaka
 
oh and is that a picture of you??? i think you look like max
payne :p
 
my crucial did the same exact thing at 155FSB but now works
fine at 151.

could it be that it just doesnt like 155fsb?
it was running perfect before on my crucial at 155.

is there any possibility it is my new PSU??? that would
seem odd.

thanks for the help DaWhip, that helped a lot!
 
Is it guist me or does Microsoft has every 0x0000000000 Error known to man at that link. Thought i would share that with every one hehe.
 
should i RMA my mushkin??? i wish i could get my money back
or get a stick of samsung but they want 15% stocking fee
or something. anyone have any experience with this?
 
I have heard that muskin is top notch.. I would try it in another rig before condeming it.. sometimes you run into compatibility issues where great ram just doesn't work in a givin system.. But hey , anything's possible.. I had a stick of corsair that gave out in 3 months.. .. The companies i deal with give me 30 days to send anything back with no restocking fee.. what company did you buy the ram from??

BTW in thinking about this further.. have you tried a diff vid card?? its kinda a long shot but i found one if my cards would not clock well and caused similar errors
 
just great! new install and format of windows = same
probs. im really PI$$ED. thought that would fix it. guess
i just need a new mobo.
 
Back