Resolved XP SP3: BSOD Physical Memory Dump Error on Cold Boot

Windows XP (Home) SP3
Intel CPU 6400 @ 2.13 GHz,
2.00 GB RAM;
HD - SATA 500 GB ample free space

Problem:
BSOD 10/25/10
“Blue Screen Physical Memory Dump Error" "“ On cold boot.
Shut off (had to unplug), removed USB flash drive and the next (cold) boot there was no error.

Tried to copy files / folder to a new USB flash drive.
This took over THREE hours NOT to complete. I canceled it. Got message that USB devices were not working.
Tried the flash drive (after scanning it AVAST! 5.x Antivirus) on another PC and it could not be read.
Eventually used CDS (MS Backup) which seem to take longer to complete.

Relevant Issues / Issues Possibly Related
Had installed:
1. Windows Media Player update (11) on 10/12/10
2. K-lite CODEC 10/15(?)/10.
System *may* have slowed down after these.
Have noticed a new file in start-up: "NvCpl" "“ Not sure when it was added, but may have followed the above installs

Have had various errors: "program has encountered error and had to closeâ€
(Firefox (3.x) "“ relating to adobe flash?)
Just after running AVAST! (Full scan) my dial up program (ATT) "had to closeâ€.
A few minutes ago, opened a MS Word (2007) file and another word file had apparently "crashed" on Sunday 10/24/10

Troubleshooting:
1. Restored registry "“ tried 2 times "“ message stated could not restore. (Was trying for dates prior to 10/11/10) (Did not try safe mode)
2. Received a "Stop Error" After 1st UNsuccessful registry restore
3. Uninstalled CODEC
4. Successfully restored registry from 2 (?) days ago. (11/24/10)
5. Ran quick AV scan: No threats found
6. Ran Full AV scan: No threats found
7. Removed Windows media player update just now.

Since it is still running poorly, i.e. (errors, slowness) (although
I haven’t "tested" it since removing the Windows media player update.)
Dying RAM?
Or
Board issue (USB drivers were "unrecognized" last night and the slowness with trying to copy to USB flash drive.)
Driver Issues

QUESTIONS:
1. Is there a very basic memory test on XP? (?Testmem? or something?)
2. Is there a possibility of a corrupt USB flash drive corrupting (or being corrupted by) the same PC and corrupting another PC? Similar to the click-of-death for zip drives / discs?
3. The "stop error" advised updating drivers.
Not sure what to do first:
save more files (large) with another new USB flash drive?
Or
Update drivers?
Any advice would be greatly appreciated
Thanks!

 

If you ask questions mainly about this system, it would help us and be easier for you if you put your system details in your WindowsBBS User Profile
http://www.windowsbbs.com/adding_system_specifications.html

The symptoms might be unrelated, some or most would be the result of the main cause/s. Chasing a single error may run you round in circles, so you need to focus on errors that are re-occurring and can tell you something about the cause.

Run Error Checking (CHKDSK) on the drive (drives, if you have more than one partition or hard disk). Look up Error Checking in Help and Support. You should also be able to run it on the USB flash drive (but make sure you check the Windows drive (C:?)).

If you have only had one "BSOD Physical Memory Dump Error on Cold Boot" that can be a one-off glitch, especially if it seemed to occur when the flash drive was connected.

Try running Error Checking (and put checks in the boxes when you go to start it). It can take several hours, so set it up to run overnight.

I have memory diagnostics in my signature if you want to run them. Also set those to run overnight. If you have only had one or two BSOD, memory is probably not the cause.

You can update drivers, that should not have any adverse effects.

Matt
PS: "Nvcpl ", run a websearch on things you are not sure about. I know that one, it is the NVIDIA control panel. It is the manager of your graphics adapter.
PPS: You don't mention that you looked in Event Viewer, look it up in Help and Support. Go to Event Viewer after you have major errors and see if some seem to relate to the main "cause ".

 

Hi and thanks for replying.

Thanks "“ I have another PC "“ and will have 2 more, so I guess it will depend on which is the the most problematic.


Since I panicked I had not mentioned part of the BSOD error: "Bad_Pool_Cache" "¦ "Stop errorâ€. On Microsoft’s Web site this is apparently due to a driver issue.

I appreciate the directions / pointers / information and am still in the process of troubleshooting thanks to your help.

I will post back with anything interesting or when it is resolved.

Because I had not looked in the Event Viewer until now:
It seems that the majority of "issues" are due to improper shut down from a program that is not closing properly i.e. is still in memory... I have found this:
Advanced troubleshooting for shutdown problems in Windows XP
http://support.microsoft.com/kb/308029/en-us
Thanks again,
Tanya

 

Closing thread and Correction:
I am closing this thread as the BSOD issue has been solved.
It was due to the "self-protection module" in my Antiviral (Avast! - version: 5.0.545)

Correction:

The actual error on the blue screen was not "Bad_Pool_Cache" it was BAD_POOL_CALLER"

Tanya

 

Well done! Thanks for letting us know.