P4 3.2 DDR400 ram on a P4R800-VM

D

dtw

2 x 512mb Infineon pc3200 ddr400 ram,
P4 3.2 800FSB
Asus P4R800-VM
40gb Maxtor 7200rpm HD
Asus 52x24x52 CDRW
Windows XP Pro SP1

System keeps giving my Blue Screen Page fault errors. Any suggestions?
 
K

Ken Fox

dtw said:
2 x 512mb Infineon pc3200 ddr400 ram,
P4 3.2 800FSB
Asus P4R800-VM
40gb Maxtor 7200rpm HD
Asus 52x24x52 CDRW
Windows XP Pro SP1

System keeps giving my Blue Screen Page fault errors. Any suggestions?

I don't know your specific system (I have a P4P800 Deluxe), and I run W2K
(which is similar to XP Pro), but I don't think anyone can answer your
questions without more information.

For one thing, you need to configure your system so that it does not
automatically reboot after a blue screen of death (BSOD), so that you can
write down the "stop" message and any other details. This information can
help you to trouble shoot your problems, especially using the Microsoft
Knowledge Base, which you can search off of the Microsoft website
(www.microsoft.com)

If the problem is software related, you would probably get more useful
information, when YOU give more information, from a Windows XP newsgroup.

One thing you might try is making a floppy with Memtest86 on it. Do a
google for Memtest86, download the program, put it on a floppy (pretty
obvious how to do this), then boot your system from this floppy. It will
run indefinitely and will make multiple "passes," checking the RAM and the
memory cache on your processor. If it finds errors, it is very likely that
the problem lies in bad RAM or a bad processor, but I don't think you can
tell which just with Memtest. So you would need to sequentially remove 1
RAM stick, retest, then the other, and if it isn't the RAM them most
probably it is the cache on the processor.

If you do run Memtest, you will need to go into your BIOS and disable
"legacy USB support," which might be called "USB keyboard support" depending
on the bios. If you don't disable Legacy USB support, Memtest will "hang"
during the first pass due to a bug in the program, not problems with your
system. Finally, 1 pass will pick up gross errors, but if you run it for a
couple of hours and get no errors, you will know that the RAM and the CPU
are not the problem. I am assuming that you are not overclocking, which is
the first thing I'd turn off if you are overclocking, to eliminate that as a
possibility.

I'm not saying that OC'ing is bad, just that it is one more thing that could
complicate things and should be turned off when you are troubleshooting this
sort of hardware and or software problem.

good luck,

ken
 
D

dtw

what more do u need to know about my system. I told u everything that's in
it. And yes i tried memtest86 which reported 0 errors
 
T

The Black Wibble

dtw said:
what more do u need to know about my system. I told u everything that's in
it. And yes i tried memtest86 which reported 0 errors

When did these BSOD start occurring? Do you get them when booting into Safe Mode? What is the model of
graphics card and PSU you have?

Tony.

--
3GHz P4 (HT enabled)
Asus P4C800-E Deluxe
PDC20378 IDE/SATA controller
ADI AD1985 audio
MSI FX5900U-VTD256 (BIOS 4.35.20.22.0)
2x 512MB Kingston PC3500
2x 36.7 SATA WD Raptors
52/32/52 LiteOn CD-Writer
16x Pioneer DVD-120S
Enermax 550W PSU
Windows XP Pro & Linux Fedora
PC-70 Lian Li case w/ side window
Hitachi 174SXW B 17" LCD

To email me, replace org.nz with net.nz
 
K

Ken Fox

dtw said:
what more do u need to know about my system. I told u everything that's in
it. And yes i tried memtest86 which reported 0 errors

I spent 15 minutes trying to answer your question and given your response I
wonder why I did . . . . .

There are Blue Screens and there are Blue Screens. The "stop message" given
has context and allows one to troubleshoot a problem using various resource
tools including MS Knowledge Base. Without the stop error you are simply
saying, "my operating system crashed." It can crash from hardware and
software reasons and without the stop code and associated message, as well
as any particular precipitating factors ("it happens on boot up, it happens
after I plug in a USB device, blah blah blah") there is no context. So
simply saying what your hardware is and that you blue screened with XP is
not enough information to answer the question.

If you go into your "system tab," which in W2K is in control panel and I
assume the same place in XP, you can configure what happens when the system
crashes. Uncheck "automatically reboot," and you will be able to read in
code what caused the error. If you just let it automatically reboot you
will have no clues to guide you in searching for what the cause is.

It is NOT enough information to simply list the hardware and say you
"bluescreened," and if you think it is, then maybe you should answer the
question for yourself!

ken
;-)
 
D

dtw

Started as soon as i set the system up. The gfx i use is all onboard. Only
thing that is not onboard is the hard drive and the cdrw. not sure on the
power supply but it worked perfect on my old system MSI nforce2 board with
AMD athlon 1800xp. This BSOD started the first time i turned the system on.
I installed the 2 sticks of ddr into 2 seperate channels. On the asus boards
they color them blue. And the BSOD occurs during safe mode / normal bootup.
I also tryed updating bios to the 3 different versions available including
the beta bios.

The Black Wibble said:
When did these BSOD start occurring? Do you get them when booting into
Safe Mode? What is the model of
 
E

end user

You gave an expert opinion & I have to agree with your latest
comments. However the guy at the other end may be frustrated as hell &
not thinking straight.

nice answer.
locust
 
K

Ken Fox

ok.

So what you need to do, assuming the system stays up long enough to do so,
is to go into "control panel," click on "system," go to the "advanced" tab,
and UNCHECK the box that says "automatically reboot"

This is what you need to do with W2K; it might be slightly different or
exactly the same set of screens with XP, but I've never used XP so I don't
know.

If the system won't stay up long enough to do this, then the only solution I
can think of is to remove components one by one and test if the sytem will
work minus each particular component. If it will, most probably you have a
bad piece of hardware and doing this will tell you which piece. Otherwise,
it COULD be the system board, which is chock full of components you cannot
remove!

When you get your next blue screen, get out a piece of paper and a pencil or
pen, and write down EXACTLY what is written on your screen. It might help
to see if you can get several blue screens and if the message is the same
each time; most probably it will be very similar or identical.

Only with this information can you begin to decipher what is going on. The
other pieces of useful information could be the "logs." In W2K, these are
viewed by clicking on "control panel," then "administrative tools," then
event viewer. You should look at, especially, the "system log" and the
"application log." If these have a bunch of red or yellow errors and
warnings, see if there is a pattern to them.

None of this stuff is easy. These sort of problems can be maddening. In
the end it could be a loose connection somewhere, a PCI card that isn't
seated right, a bad controller or other hardware component, software
corruption, bios corruption, problems with a hard disk, bad RAM, etc. etc.
etc.

These kinds of problems are why a lot of people end up buying Dells; they
can call up on the phone and if the thing can't be easily sorted out they'll
either come and fix it or you send it back to them. Undoubtedly, they don't
even bother trying to sort out these kinds of problems because it is not
cost effective to pay real wages to get someone to do it, so they toss a lot
of systems and components rather than find the error. But you don't have
this option. Trying to sort this stuff out yourself can be very very
trying. And there are no easy answers.

No one can tell you why your computer is bluescreening just based upon a
list of components; there are soooooooooooo many possible reasons, and it
might take you a few days to sort it all out. If you don't have the
patience or toleration for this sort of stuff, pack all the components up
and send them back to where you got them for a refund. Then buy a Dell.

I wish I could suggest an easier solution, however my own experiences in
this area have tempted me to take the whole system and heave it out of a
high window on more than one occasion! In the end, with lots of patience,
these sort of problems can (usually) be sorted out.

good luck,

ken
 
T

The Black Wibble

dtw said:
Started as soon as i set the system up. The gfx i use is all onboard. Only
thing that is not onboard is the hard drive and the cdrw. not sure on the
power supply but it worked perfect on my old system MSI nforce2 board with
AMD athlon 1800xp. This BSOD started the first time i turned the system on.
I installed the 2 sticks of ddr into 2 seperate channels. On the asus boards
they color them blue. And the BSOD occurs during safe mode / normal bootup.
I also tryed updating bios to the 3 different versions available including
the beta bios.

The drivers loaded for Safe Mode are pretty generic so I doubt there is a driver problem. Does BIOS reflect
the correct DDR reference voltage for those Infineon modules?

Tony.

--
3GHz P4 (HT enabled)
Asus P4C800-E Deluxe
PDC20378 IDE/SATA controller
ADI AD1985 audio
MSI FX5900U-VTD256 (BIOS 4.35.20.22.0)
2x 512MB Kingston PC3500
2x 36.7 SATA WD Raptors
52/32/52 LiteOn CD-Writer
16x Pioneer DVD-120S
Enermax 550W PSU
Windows XP Pro & Linux Fedora
PC-70 Lian Li case w/ side window
Hitachi 174SXW B 17" LCD

To email me, replace org.nz with net.nz
 
T

The Black Wibble

Use the Memtest86 utility from www.memtest86.com if you would like to test the DDR modules. It installs on to
a diskette. Disconnect any USB keyboard and mouse before performing the test, else it will cause a lock up
during one of the stages.

Tony.

--
3GHz P4 (HT enabled)
Asus P4C800-E Deluxe
PDC20378 IDE/SATA controller
ADI AD1985 audio
MSI FX5900U-VTD256 (BIOS 4.35.20.22.0)
2x 512MB Kingston PC3500
2x 36.7 SATA WD Raptors
52/32/52 LiteOn CD-Writer
16x Pioneer DVD-120S
Enermax 550W PSU
Windows XP Pro & Linux Fedora
PC-70 Lian Li case w/ side window
Hitachi 174SXW B 17" LCD

To email me, replace org.nz with net.nz
 
K

Ken Fox

end user said:
You gave an expert opinion & I have to agree with your latest
comments. However the guy at the other end may be frustrated as hell &
not thinking straight.

nice answer.
locust

People have problems with systems for different reasons. In my own case it
is because I tend to continually upgrade and buff up my system until
something gives up the ghost! It is almost predictable with the amount of
fussing I do with what is inside my box, that given a year or two I'll trash
SOMETHING.

My latest solution, for lack of a better one, is to have redundancy. I've
got a laptop that usually works ok, and on which the potential for doing
serious harm is more limited. Now, I've also got a SFF dual boot
W2K/Mandrake Linux box that provides further reduncancy for that next awful
day when I ruin my system!

I just wish I could justify even a tiny fraction of the time I waste on this
sh*t!!

ken
 
D

dtw

there is no pci cards installed on this board. it is using onboard ethernet,
onboard radeon 9100 IGP graphics and onboard soundmax audio. I have ran the
memtest86 by gettin the cd image and burning it and let the test go through
3 complete cycles with 0 errors reporting. The blue screen says in event
viewer :

The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007e
(0xc0000005, 0x00000000, 0xf47e2c94, 0xf47e2994). A dump was saved in:
C:\WINDOWS\Minidump\Mini010102-03.dmp.

But its not only BSOD that i have problems with, when the machine do stay
running i get application crashes etc.....

Also there is no option in BIOS to check the mhz rating of the ram, only
the total memory which it does read correctly
 
K

Ken Fox

Hi,

I'm not familiar with the particular error screen you are getting. This is
a start, however, in sorting this problem out. Most probably it is not the
RAM or the CPU cache given your Memtest86 results. The fact that Memtest86
will run for 3 passes suggests that the problem may be software related to
me but I really don't know that.

The first thing you need to do is to figure out if the problem is hardware
or software related. One possibility, probably not real likely, is that you
neglected to load the chipset and other drivers that came with your mobo.
Assuming you loaded these drivers, I suggest you go over to the Microsoft
website and try different search terms like "bugcheck" in the Windows XP
Knowledge Base. You could also try the MS Windows XP forums, at this URL:

http://www.microsoft.com/windowsxp/home/using/newsgroups/default.asp This
is the XP Home forums, but there are also XP Pro forums and they both might
be worth checking since the OS is basically the same.

I think that someone who is knowledgeable about blue screen messages could
probably look at what you have transcribed below and tell you pretty quickly
whether it is hardware or software related. It sounds like you don't have
any cards in your board, so that really limits the hardware that could be
causing the problems, if it is hardware.

Was there any indication of what problems are going on in the event viewer?
If there are scads of red and yellow error and caution listings, from a wide
variety of services, I'd suggest the most likely problems are bios
corruption or some sort of hardware problem with the mobo, which you could
get a replacement for from the vendor and then just reinstall everything
into the box and see what happens.

IF THERE ARE LOTS OF ERRORS IN THE EVENT VIEWER, and since you, in an
earlier post, I think, said that you had flashed the bios, you could try
removing the CMOS battery and shorting out the CMOS jumpers. This is easy
to do, and check your mobo manual for detailed instructions. Basically, you
need to remove all power from the system (pull out the plug in the back),
open the case, ground yourself to the case, remove the battery, (the battery
is one of those disk batteries and you can't miss it), then short the jumper
(needle nose pliers or computer tool kit has something that will work to
remove the jumper, reposition it, then put it back) for 10-15 few seconds,
then replace the jumper where it was originally, then put the battery back
in. You will then need to hit delete when the system boots and hit "system
defaults" in the bios. Then, you may have to work on the boot order and
other stuff in the bios to get it configured right. Only do this if you
think the Bios may be the culprit. Lots of errors in the even viewer would
suggest that as a possiblity, at least.

Problems like this make you tear your hair out, they make you want to
SCREAM! I've been there, and I hate this sort of sh*t. I just don't know
how to solve this type of problem without a process of elimination, which is
hugely time consuming and only rewarding when you finally solve it.

Good luck,

ken
 
K

Ken Fox

dtw said:
Actually it was a ram problem. Was a Syncing error between the 2 chips

like I said, there are endless possible causes. Sorting them out is usually
possible, but it takes a toll on your stomach lining.

Glad you got it sorted out.

ken
 
D

dtw

thnx for the help though :)
Ken Fox said:
like I said, there are endless possible causes. Sorting them out is usually
possible, but it takes a toll on your stomach lining.

Glad you got it sorted out.

ken


related hell message,
 
T

Technotrone

We built 20 systems for a customer featuring this motherboard and 2
pieces of DDR-400 ram. Every single one was crashing either during or
after win2k installation. This motherboard suffers from serious
instability, go with P4P800-VM based on intel chipset. No problems with
this model in any configuration.
 
D

David Shorthouse

Sounds to me like VRAM issues. Most DDR400 sticks need at least 2.6v (some
work best at 2.7+v). As far as I know, there is no way to adjust the VRAM in
the P4R800-VM BIOS from the default 2.5v.

Dave
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top