BSOD Dump Files Not Present?

[Charitzo]

Hey there,

So I've been experiences a whole bunch of BSOD's lately, notably, 0x19, 0xC5. Obviously I can look up these codes, but I'm finding it hard to pin-point the culprit.

I downloaded Blue Screen Viewer, and realised I had no dump files. The only files I found with the *.DMP extension were under C:\Windows\LiveKernalReports\WATCHDOG

Are these files the correct dump files? I figured how to change the dump director on blue screen viewer, but I've found no mention of this directory in my research on the issue. Are these the correct files?

In sysdm.cpl (Advanced\Startup and Recovery Settings\), I had my "Write Debugging Information" set to Kernal memory dump. The directory for this is %SystemRoot%\MEMORY.DMP, however, this folder does not exist.

If those *.DMP's I mentioned erlier aren't the correct reports, how can I get Windows to correctly create these dumps? (Am on Win7 Profession 64 bit).

Thanks,
Char

 

[supasieu]

Have you check C:\Windows\Minidump

 

[Charitzo]

Have you check C:\Windows\Minidump

That folder doesn't exist. When I set the "Write Debugging Information" to Small memory dump, it sets the location to there. However, upon BSOD no dumps are written.

 

[johnbl]

%systemroot% is a variable in a environment block it is generally set to the value of "c:\windows" so in your case
you file should be at
c:\windows\memory.dmp

what happens to the memory dump depends on your system settings. if you have windows error reporting the information is copied up to microsoft so they can download fixes to your machine, and track problems.

other settings will determine what happens if you get another memory dump. it might be set to just over write the last memory dump.

note: the error codes you indicated indicate memory corruption in kernel memory. most often caused by one device driver writing over the data of another device driver. the second driver fails and bugchecks the system. It can also be caused by viruses attempting to gain access to your system, and certain types of memory problems.

 

[Charitzo]

%systemroot% is a variable in a environment block it is generally set to the value of "c:\windows" so in your case
you file should be at
c:\windows\memory.dmp

what happens to the memory dump depends on your system settings. if you have windows error reporting the information is copied up to microsoft so they can download fixes to your machine, and track problems.

other settings will determine what happens if you get another memory dump. it might be set to just over write the last memory dump.

note: the error codes you indicated indicate memory corruption in kernel memory. most often caused by one device driver writing over the data of another device driver. the second driver fails and bugchecks the system. It can also be caused by viruses attempting to gain access to your system, and certain types of memory problems.

I thought it would be at C:/Windows/System/Memory.dmp, but that folder doesn't exist. The only *.DMP files I could find were at the mentioned address.