Beginning dump of physical memory software

Log In. Thank you for the message, dhawthorn! The computer is "crashing" sporadically. Thanks again! HTH Pete RE: Beginning dump of physical memory What is the stop code? After the STOP 0x??

What fills in the question marks? You might have to search several time and reduce the length of the string but you should get your answer. This error message usually is caused by a device driver problem or hardware incompatability. Be suspicious of anything new added to the machine. Most people will tell you to make sure you have the latest drivers, and this is usually true. But occasionally I have updated drivers in NT and had problems. Going back to an older driver settled things down.

Also you can check your event log and the dr watson log drwtsn Now I was working with photoshop last night and the blue screen came up, and again today while I was installing updates hoping these would fix the problem. Does anybody know what has happened to my laptop? My warranty of course is expired and I have taken good care of it since I purchased it 17 months ago.

Any help would be greatly appreciated. All forum topics Previous Topic Next Topic. Replies 2. Post Reply. Top Contributor. Dell Support Resources. Latest Solutions. Can't find what you're looking for? There are TONS! The one that seems to be causing the major issue however states:.

I'm seeing winlogon errors, eventsystem errors, and DCOM errors through the roof. However, the bugcheck isn't registering with the event logging subsystem due to the aforementions eventsystem errors, apparently , so the next time the box bluescreens PLEASE write down the information onscreen including the numbers.

I'd say it'd be easier just to write the bluescreen info down. However, I doubt this is related to your bugcheck issue, it's just another problem I see on the system. Ok, bluescreened again. The info I listed in the original post is the only technical info in the entire screen.

It seems to me at first it is a RAM issue. Have you tried running memtest? Or maybe the memory was not seated in right? I would not rule out a corrupted XP install but that seems less probable than just bad ram.

That is why i always go with either Corsair or OCZ no matter how expensive they are. OK, so I'm going to need a complete dump of the OS when it bluescreens. To do this, go into the Properties of "My Computer", then click the "Advanced" tab, click the "Settings" tab under the "Startup and Recovery" heading, and then select "Complete memory dump" under the "Write debugging information" heading.

Once the system bluescreens after making this change, it will create a memory. This file should be the same size as the amount of physical memory in the machine - if you compress this and send it to me or post it here, I can then run it through a debugger and get some "root cause" information.

You need to be a member in order to leave a comment. Sign up for a new account in our community. It's easy!