• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Did some upgrades, now BSOD!!

misle

misle

Diamond Member
I'm running WinXP and this system has been extremely stable for the last 6-8 months. I've never had a problem before.

Old setup:
2000+ AthlonXP
Epox EP-8DRA
512 MB Crucial PC-3200
eVGA GeForce4 Ti4200
TDK CD-Burner
Pioneer DVD-ROM

Today I upgraded to:
2800+ Athlon XP
Added 512 MB Corsair PC-3200
Ditched the Pioneer and added a NEC 2500A DVD+-R

Ever since the upgrade, my computer crashes. Especially when actually used, Like running audio editing programs, which is what this computer is mainly used for.

I already pulled the new RAM out, but I'm still getting BSOD.

Any ideas?

-oh, I also went ahead and updated to the latest BIOS after the first BSOD.
 
I'll check that on next reboot 😛

Info from last BSOD:
The problem seems to be caused by the following file: win32k.sys
PAGE_FAULT_IN_NONPAGED_AREA

STOP: 0x00000050 (0xBC00FCF4, 0X00000000, 0XBF848851, 0X00000001)

win32k.sys - address...

then it reboot.
 
"Real Clock 2083 MHz"
FSB = 166 MHz
166 x 12.5

I forgot to get voltage, but I remember seeing 1.65V or 1.68V
 
Voltage is at 1.65V

Anyone have any ideas? Will reinstalling WinXP help?
Is this a known problem with my motherboard?
Is it bad to mix Crucial and Corsair memory (yet this seem not to matter b/c it crashed with just the crucial)?
Did the Pioneer DVD-ROM drive curse my computer?
 
Pull the old RAM. Random BSODs are often caused by bad RAM. Also, try different memory slots on the motherboard.

\Dan
 
Originally posted by: EeyoreX
Pull the old RAM. Random BSODs are often caused by bad RAM. Also, try different memory slots on the motherboard.

\Dan
Click to expand...

Well, I pulled the Crucial memory out and left the Corsair and it seems to be working again. I'm going to run a stress test over night to make sure. Could the Crucial memory have been damaged when I added the Corsair?

I was wrong earlier, the Crucial is 333 MHz memory, while the Corsair is 400 MHz memory. Yet, I only ran it at FSB=166 -> 333 MHz.

I have emailed Crucial asking how I should go about getting my RAM replaced.

Thanks for the help guys.
 
Originally posted by: misle
memtest?

Where can I find a memory test?
Click to expand...

MemTest86 is your best bet. I don't know if I can do seperate tests, so you might have to just boot up with the Crucial in.

http://www.memtest86.com/

I had those BSODs before, but I cannot remember why I was getting it, but I know it wasn't RAM. It might have been driver problems.
 
Originally posted by: misle
memtest?

Where can I find a memory test?
Click to expand...

It looks like you've already found your answer but here is the link you requested anyway.
edit: someone beat me to it while I was typing. Each time I have heard of that particular BSOD, it's been the ram. A page fault is the inability to read data in a paged block. An unpaged area is physical memory (not paged to pagefile) so that error message means that the system couldn't read back what was written to memory.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top