Hi Everyone,

 

Since my new computer was built (about a month ago), I've recieved quite a few "blue screen of death"s telling me that there is an error, and (the more worrying bit) that it was "beginning memory dump".

 

This error message seems to appear randomly (sometimes it appears at startup, sometimes it appears while I'm networking, other times it just appears while the computer is idle).

 

I was wondering what "memory dumping" was and why this error occurs?

 

Thanks in Advance

 

Oh yeah, by the way, I'm running WinXP Pro SP1 with all critical updates installed.

 

My system specs:

Intel P4 3.0C

GA-8KNXP

1GB DDR 400 (PC 3200) RAM

120GB HDD

What causes the so called 'BSOD' is a system event that threatens the integrity of the system. Windows stops everything, and tries to tell you as much about the situation as it can. The information isn't terribly useful unless you see the same information recurring over and over and can link it to a particular process or something. The dump usually consists of the values in the processor registers and the area of memory around the instruction pointer.

 

If the BSoD is happening in way that you can't link to system events, it may mean that you have a bad driver or a hardware issue. If a card isn't seated quite right, there is a flawed component, or the processor is overheating, this can cause system instability.

 

I'd make a check of all the component manufacturer's websites for fresh drivers, reseat memory and expansion cards, monitor CPU and GPU temps (sometimes there's an onboard probe, but a medical thermometer can work), and look at the power regulation capacitors around the processor for leakage (they will be bulged or titled). (In that order is probably best)

Dont worry about the statement regarding "dumping physical memory to disk". Its not hurting anything. All its doing is taking the entire contents of your memory and logging it to a file (think its called Memlog and is stored under your root directory - C:\)

 

Like Gavion0 said, this isnt terribly useful, unless you know what everything is.

I thought XP reboots instead of Blue Screen?

Well, WinXP certainly didn't reboot. The blue screen of death came up and I was stuck there. Also, there is definitely no single program that generates these faults. So, I'll probably follow GavinO's advice and have a check of the computer and update as necessary. I'll see how it goes. Thanks anyway.

 

(More Tips/Suggestions welcomed)

vbFace: There is an XP blue screen. More rare, but when stuff goes to pot, you get an NT-style BSoD (if anything, more intimidating than the 9x one). Only MS product that doesn't blue screen is the XBox; it presents fatal error info against a black screen :)

hi everyone again

 

this whole BSOD thing has just risen to new heights. Since this morning (thursday Australian time), Windows wouldn't even boot properly anymore. The Windows loader screen (with the little bar flashing accross at the bottom) would appear, and when its just about to go into the login menu, the BSoD appears, telling me that there was an error, and that I should restart (which i did, over and over again).

 

Does anyone have any idea what may be wrong? or should i just reflash my m/board bios and see?

 

If you can help at all, please do.... Its frustrating to have a supposedly fast computer tha is almost useless at the moment.

 

Thanks in advance

Is your system a DELL? If so there is a 31 mbs partition thats a FAT (EISA Configuration). Delete this and should fix your problem.

 

I had 3 DELL's do the samething, I removed this partition and everything been fine since.

 

 

hopes this helps.

Unfortunately, no. :( I built the computer by myself so everything is basically OEM.

 

just out of interest, how do I find this partition?

 

Thanks

You can use Disk Management in the Control pannel. This will show you what FIXDISK are present.

 

1. Another thing you can try to increase your Virtial Memory.

2. Pull one 512 (ram chip) out and run it for a few days and see if that fixes your problem.If not try the other chip.

I think I will have to pull out and individually test the RAM chips like you said. Nothing else seems to be wrong. However, (and hopefully), there isn't something wrong with the RAM (its annoying going to the shops and asking for refunds, etc.).

 

You'll hear from me in about a day or two.

 

Thanks!

I think I will have to pull out and individually test the RAM chips like you said. Nothing else seems to be wrong. However, (and hopefully), there isn't something wrong with the RAM (its annoying going to the shops and asking for refunds, etc.).

 

You'll hear from me in about a day or two.

 

Thanks!

 

Please let me know what you find out. Plus just PM if you need anything else.

I've just reseated the RAM. Dunno if it did any thing (the only indication would be whether the BSOD comes up again), so i think I'll just wait and see now.

 

Cheers

It is NOT a big prob the Memory Dump is like a bult in "ghost" system basicly it takes a "snapshot" of your computer and puts int in a folder in %Sysroot% named Memdump it is ok

;)

I had the same problem when trying to add another 512mb RAM onto my computer. The RAM I was added definately was the same stick as I had before. My computer would just randomly start a memory dump in the blue screen when I had both RAM sticks in. I tested it with 1 stick in at a time and it ran fine :confused:

 

 

/~Alex

Interesting problem isn't it? Though i did hear from somewhere that too much RAM may not actually be beneficial to your computer (though i personally don't think so)...

 

Does anyone know anything about that?

 

oh, BTW, i never thought my initial thread would result in more than 1000 views! :D

Alex: On non-NT versions of Windows, there is a problem with part of the Windows memory setup will cover up another fixed memory window. See, by default there is a cache that is set up as a proportion to the amount of memory in the system. For memory sizes 512Mb and below, this is fine. When you hit 1GB, however, the cache uses all addresses that another subsystem (not sure what it is; might be AGP?) can use, causing a problem. Check this out: http://computermemoryupgrade.mysuperpc.com/out_of_memory.shtml

 

Of course, if you're using an NT-based Windows (NT, 2K, XP), then this really doesn't apply ...