Physical memory Dump

[napster0317]

I have a computer that is giving the error that it has to do a physical memory dump. I have checked the fans to make sure that the pc is getting enough cold air, and it does seem to be. I have also set it to shut itself down when it reaches a certain temp.

any ideas?>
bad ram, bad power, Bad Dell????

 

[Menelmarar]

Could be driver/software related. Have you installed anything new recently? Recently upgraded any drivers?

Can you give us any text from the BSOD? Often they mention problematic dll files such as nv*.dll or ati*.dll.

 

[Slartibartfast]

I've seen a few of these, but they all had different causes. One thing to do is make note of the file that generated the dump. if it's non-system critical, go rename the file and see what happens. I've actually seen RAM overclocks cause these too. I know windows logs these too and that can help, I just don't remember quite where. Play around with your start-up/recovery settings. Also, be sure not to have it write a complete log file unless you want a 1gb .txt file

 

[karma29]

everytime I've ever ran into this problem. its been bad Hard Drive, check drivers and everything else first but 9 times out of 10 its the hard drive.

 

[Phoenix86]

any ideas?

Not really, I left my crystal ball at home. Care to give us some details or should I just post random BSOD links in Technet until we find the right one?

May I suggest listing the following:
System information. Kinda hard to know what hardware you w/o telling us. All we know is it's a dell.
OS version and service packs loaded.
Gee, I don't know, how about the actual error message?

The BSOD should have a stop error like this: IRQL_NOT_LESS_OR_EQUAL.
Also include the 0x00000000 information.
Also see the event viewer and post the detailed information in there.
Lastly, you can contact Ranma_Sao, he's a MS employee who will read the dump file. Search for a thread titled something like "help me: help you" posted in this subforum.

I was this close *holds index finger and thumb real close* to filtering the thread because you didn't include ANY usefull information.

 

[djnes]

everytime I've ever ran into this problem. its been bad Hard Drive, check drivers and everything else first but 9 times out of 10 its the hard drive.

I would say 9 times out of 10 a BSOD is caused by something other than a bad hard drive.

 

[Stormlifter]

Yeah bad HD is not the culprit, i'd try your BIOS and check out your RAM timings or your voltage settings, it might need more, might need less..
I didn't check, did you say you were OCing?

 

[feigned]

Not really, I left my crystal ball at home. Care to give us some details or should I just post random BSOD links in Technet until we find the right one?

May I suggest listing the following:
System information. Kinda hard to know what hardware you w/o telling us. All we know is it's a dell.
OS version and service packs loaded.
Gee, I don't know, how about the actual error message?

The BSOD should have a stop error like this: IRQL_NOT_LESS_OR_EQUAL.
Also include the 0x00000000 information.
Also see the event viewer and post the detailed information in there.
Lastly, you can contact Ranma_Sao, he's a MS employee who will read the dump file. Search for a thread titled something like "help me: help you" posted in this subforum.

I was this close *holds index finger and thumb real close* to filtering the thread because you didn't include ANY usefull information.

This too: http://aumha.org/win5/kbestop.php

Last time we were doing physical dumps it turned out to be buggy software that gave our Savin multifunction access to write .pdf's to a windows share. Funny thing is that it was on our Exchange box at the time, and still is. Yay.

 

[Phoenix86]

This too: http://aumha.org/win5/kbestop.php

I just use his source, Technet and MSDN. I can answer well over 1/2 of all windows threads with just using http://www.technet.com

That is a nice list though.

 

[Mister Natural]

I eat more vegatables when I have a problem taking a dump....