OS and Software > Microsoft Help > [WIN7] Memory dump

[WIN7] Memory dump

Thank you for your reply.

How do I get the "dump" to post it.

Please talk to me like a 4 year old if you can tell me how..ie, step by step. Not the greatest on computer

I think I may have found a fix?

From Microsoft a 'debug"
. I found it doing a search for my problem about the blue screen and dumping.

»msdn.microsoft.com/en-us/windows···009.aspx

Would this be what I need to do?

Thanks in advance.

reply to ez2cy
I think I may have found a fix?

From Microsoft a 'debug"
. I found it doing a search for my problem about the blue screen and dumping.

»msdn.microsoft.com/en-us/windows···009.aspx

Would this be what I need to do?

Thanks in advance.

reply to ez2cy
That would be a set of tools to view the memory dumps, but won't be of that much use to you if you don't know what you're looking at.

To upload the minidump files, go to the C:\Windows\minidump folder, zip up the files there (if there are a lot, the most recent three or so would be a good start) and then attach them to a reply post in this thread.

Someone will hopefully then be able to look them over and possibly give you some input on what may be causing the problem.
--
Brain: Pinky, are you pondering what I'm pondering?
Pinky: I think so, Brain, but "Snowball for Windows"?

reply to ez2cy
Either the date/time is set incorrectly on your machine or you didn't get the latest dump file(s). The 2 files you zipped up are from Sept. 2010 and both deal with a video driver issue.

reply to ez2cy
Look to see if you have the folder C:\Windows\minidump\

If so are there any files in there with today's or yesterdays date/time stamp?

If so, please zip up the most recent 2 files and then upload them.

Just the two files I uploaded that are from 2010. Only 2 there.

Why I was asking about the uploaded printscreen, if that is where it's going instead to the Kernel memory dump, and if I should change that. ????

There are two types of dump that you can configure:

1) "All of kernel memory" - ends up in C:\Windows\memory.dmp

2) "Small memory dump" - ends up in C:\Windows\minidump

You're configured for #1, aguen gave instructions for #2.

Take a look and see if you have a recently-written C:\Windows\memory.dmp. Though it might be too large to upload.

It might be worth switching your config to "small memory dump" so you can collect more than one, since we may need to look for commonalities.

Ok...I have...C:\Windows\LiveKernelReports

Within that is a file "WATCHDOG" but nothing with today's date.

the list of files that have today's date on them are; (in Windows)

assembly
inf
Installer
system32
bootstat.exe
setupact.log
WindowsUpdate.log

Should I be looking in one of those for something?

I will change the config to small memory dump as suggested.

No one?

No, that's not it.

It's either C:\Windows\memory.dmp (one file from kernel memory dump) or C:\Windows\minidump (folder containing multiple files)

WEll then something is really screwed up.

There is not Memory.dmp.....there is minidump...but the two files in it are the ones I posted and they are from 2010.

It's just done the blue screen dump thing to me 3 times in the past hour.

Also, computer is really slow booting up, to password sign in,...and then after I enter it. NOt sure if that helps or not.

When it does boot up, get a message from the bottom right screen that says, a windows service did not start....but it says something about other users not being able to use it or something. ????

Also, where someone told me to change the "kernel dump" to "small memory dump" in Systems, start up and recovery, it has "Small dump directory" as %SystemRoot%\Minidump ????? no idea what that means

%systemroot% is a symbol that means "where the OS is installed", and it is usually C:\Windows, though need not be. Using the symbol makes the setting independent of the name chosen by whoever installed the OS.

So, leave it as it is, and your minidump files will be in C:\Windows\Minidump

Ok...but that's the point....no files are going to Minidump period. I found how to stop the auto reboot so I can read the whole blue screen.

But...as I said, it's happened this evening a few times and no files after in minidump.

I'll wait for it to happen again I guess

reply to ez2cy
You should and can check your memory by typing 'memory' in the search box which will give you the option to run Windows Memory Diagnostic on the next re-boot. If you get an error you'll have to check each stick by trial and error with this tool. Bad memory is a very common cause of your problem and it sounds like you have a hardware problem from the random nature of your errors.
--
"The best laid schemes of mice and men often go awry . . . " --Robert Burns

reply to ez2cy