Fellow computer nerds - Question about memory dumps?

[neoteric lefty]

I am running a Win2k system and recently (last month or so) everytime I run a hevy application (mostly games but sometime when I am using phtoshop with a big 300dpi photo), at some point the application crashes to desktop with an error or I get a BSoD with a memory dump code (either 0x000001e or 0x00000050). Now, I checked with MSFT and other message boards and none of the solutions (drivers, updates, servie packs) seem to fix the problems. I am hoping it isn't a fauly memory module. I can't reformat my system until I get a DVD burner (lots of important stuff). Anyone have any ideas of what may be wrong?

[Occulus]

1. Sounds like a RAM issue.

If you have less than 512M, you don't have enough. If you have that or more, it very well may be a bad RAM module. Unfortunately, the only utils I've heard of that FULLY test RAM cost bookoo bucks.

Try removing your RAM chips, one at a time, and see if you can norrow it down to a faulty chip. If you can't, you likely just need more RAM.

edit: run scandisk, defrag, etc. See if you have bad sectors on your drive. Barring THAT, doa total reformat/reinstall. Use a CLEAN WinX CD; DON'T use the CD that "came with your PC"; those have loads of crap that install with the OS. You really likely don't need that.

Get thyself a WinXP OEM CD. The kind that DOESN'T come in the pretty blue box; you're paying hundreds more for that box. Keep it handy and reformat every couple months or so. I;ve been doing thus for about six years, and the only reason I experience problems is because I push my system to its absolute limit daily.

[neoteric lefty]

2. I got a single 512MB pc3200 DDR

I have tried 3 different memory testing suites and all say a.o.k. Sounds like RAM too. Oh well, I am building a new system in about 2 months, I just hope it stay up until then.

[huellewig]

3. I don't really know.

I'm a Mac/Linux guy. Getting new RAM would be good. If you bought a new stick I would add that. If the problem persists install the new one in place of the old.

Do you have a way to get data off your computer? It is time for a backup. Using CD's might take some time but you don't lose anything. A USB/Firewire drive is great for this too. If you have a feeling you are going to lose your data do whatever it takes to keep it. Oh, and WinZip + Nero can split large files to span mulpitple CD's.

It might be time for a clean install.

[Robert Oak]

4. video card

1. does it happen on large data files that are not associated
with images or only graphics? If yes, then 2 is probably not
relevent.

2. If it is only graphics, I would be looking at your AGP bus
&/or your graphics card. If rendering, especially for games
is done on the card, your card might be bad...or your video buffers
are overflowing and can't handle it and are dumping...


3. I'd try

a. seeing if I could modify the video buffer size on the video
card.
b. swapping out video cards for another to see if that makes a difference.
c. hunting the forums for video memory dumps and problems
with your particular video card.

my 2 cents.

[neoteric lefty]

5. thanks, i'll look into that possibility nt

[Kellanved]

6. Have a look into the dumped memory image

The Windows Debugger does that nicely, you can find it here:
http://www.microsoft.com/whdc/devtools/debugging/default.mspx


With the symbol files it's a 177 MB download, should that be too much, ask again: there is a trick to download the symbols on-the-fly.


Anyway, use Windbg to load the dumped file - it will produce a "Probably-Caused-By". That guess is correct in 95% off all cases in my experience. Should the guess be inconclusive, enter "!analyze -v". The call stack displayed should include the culprit.

Should the identified file be part of the graphics driver, replace the video card.


Edit: USe the Win2k tool "verifier" (use run... in the start menu). Sometimes a driver might bring the system into a state that all but guarantees a crash in the near future. The verifier catches those with a special BSOD.




For people with a stable Windows: open the registry, go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters\ . Add a new DWORD: CrashOnCtrlScroll.

From now on Windows will crash with a BSOD every time "scroll" is pressed twice while holding down CTRL: nasty pranks are possible with that :evilgrin: .