Pam,
This may help you look in the right direction. Hope so.
Beginning dump of physical memory, what should I do?
Commonly known as the blue screen of death or BSOD. When this happens on your computer the only thing you can do is to turn the computer off, removing the power source or just by pulling the power cable from the wall socket. Wait for a least10 seconds before turning it back on or plugging it back in. Your computer should boot up back to the normal logon screen.
Blue Screen of Death n. [common] This term is closely related to the older Black Screen of Death but much more common (many non-hackers have picked it up). Due to the extreme fragility and bugginess of Microsoft Windows misbehaving applications can readily crash the OS (and the OS sometimes crashes itself spontaneously). The Blue Screen of Death, sometimes decorated with hex error codes, is what you get when this happens. (Commonly abbreviated BSOD.)
The message you are getting is because of driver errors. The screen you are seeing is like the old blue screens on win 98/95. What happens is after a crash the computer dumps the physical memory into a log file with the .dmp extension. This log file can be used to determine what the cause of the crash is. Windows NT/2000 installs default to dump the memory into the log file and then automaticaly reboot the system. This option can be taken off in the system settings in the control panel on the last tab. (i cant recall what its labeled.)
I would suggest that you look at the log file and try to determine what is causing the memory dump before you turn the option off first so that the problem can be resolved first. If you dont then your computer will just crash instead of giving you the memory dump error. Most cases it is because of a corrupt driver or program error. Either way its because of something other than your memory chips so dont worry your ram isnt bad.
Problem: When I use a GPIB board in my Windows 2000 system, my computer crashes with the following error message:
Stop 0x000000D1 (0x00000060, 0x00000012, 0x00000000, 0xBFE6058A)
DRIVER_IRQL_NOT_LESS_OR_EQUAL
Address BFE6058A base at BFE5C000 DateStamp 37939fe5 - gpibpci.sys (gpibatnt.sys for PCMCIA)Beginning dump of physical memory.
Solution:
Windows 2000 controls power in such a way that the system crashes under heavy communication traffic to the PCI-GPIB board. This is a timing-related issue with the driver, which shows up when the ACPI mode is enabled (by default) under Windows 2000. To fix the problem, replace the gpibpci.sys file on your machine with the one that is attached below and then reboot the machine. It should be at this location on your Windows 2000 system: C:winntsystem32driversgpibpci.sys
Since files with the .sys file extension are typically hidden by Windows 2000 by default, you may have to alter your View settings in Windows Explorer to see this file (see KnowledgeBase 2IQB2PLI, linked below).
Note: We received feedback that this same error message occurred due to a defective RAM chip in one customer's computer system.
PCMCIA Solution:
The Blue Screen is caused by an older Client Manager software for a Lucent WaveLAN wireless LAN card. This software starts a process called CMLUC. Updating to version 2.58 of the WaveLAN software should solve the problem.
Related Links: KnowledgeBase 2IQB2PLI: How Do I Show Hidden/System Files on Windows Operating Systems?
