BleepingComputer.com: No minidump or event log after BSOD.

My pc has been giving BSOD STOP error messages continuously. However I do not find any minidump files in Windows/Minidump. I have set system to create a minidump and write a event log but there no effect. The event viewer does not show any errors or warnings after BSOD or crash, neither there is a dump file. I used BlueScreenView but even it does not show anything. I confused that without any minidump file how should I figure out the problem. Also after BSOD and pc restart chkdsk starts scanning. I searched my computer for files *.dmp but there was nothing related system crash. I need help with this problem.

Check the event log for any error messages pertaining to System and Applications.

I would suggest that you have a hard drive with problem or a file system with problems.

After XP boots...Start/Run...type chkdsk /r (space between k and /) and hit Enter. Type Y in response to onscreen query and hit Enter.

Reboot the system, the command will run...system boots into XP upon command completion.

If you receive any error messages explaining that chkdsk /r cannot complete or that the file system has problems...write such down and post.

Louis

It's possible that memory dumps are turned off...

1. Click Start, and then click Run.
2. Type sysdm.cpl, and then click OK.
3. On the Advanced tab, in the Startup and Recovery section, click Settings.
4. In the Write debugging information list, click Kernel memory dump, and then click OK.
5. Click OK to close the System Properties dialog box.
6. In the System Settings Change dialog box, click Yes if you want to restart your computer now. Click No if you want to restart your computer later.

Your settings should look like this (with XP instead of Windows 7, obviously):

hamluis, on Apr 30 2010, 06:29 PM, said:

Chkdsk runs on its own after my pc gets a BSOD. It shows some error but also tell that it has recovered them. I think this chkdsk utility runs because one of my drives is FAT32. But everything seems to be okay with chkdsk.

keyboardNinja, on May 1 2010, 12:51 AM, said:

Actually in the Write debugging information list, Small minidumps(64k) is selected, which is directed to %Systemroot%/Minidumps. But there is nothing in that folder. I don't understand what is the difference between Small minidumps and Kernel memory dump options. Will changing it to kernel memory dumps create dumps? If so where will I find them?

cryptodan, on Apr 30 2010, 04:16 PM, said:

The event logs don't show any errors or warnings during the time when BSOD was generated. If I find the minidump by some way I can send it to bleeping computer to solve the problem with my pc.

bomblast, on May 1 2010, 04:19 AM, said:

Well, it should create dumps either way, but try it and see (change to kernel, reboot, and wait for a BSOD).

Then check BlueScreenView again.

keyboardNinja, on May 2 2010, 01:10 AM, said:

Well, I will try and hope that it solves the problem.

Also, make sure BlueScreenView is looking in the right place. You might have to direct it to the folder where the dumps should be contained.

bombblast, are these topics for the same computer?

http://www.bleepingcomputer.com/forums/topic313711.html
http://www.bleepingcomputer.com/forums/topic312960.html

Double-posts about the same problem are not allowed.

keyboardNinja, on May 2 2010, 11:34 PM, said:

When I changed the 'Write debugging information' to Kernel memory dump, its dump file location is shown to %Systemroot%/MEMORY.DMP. However there is no folder named "MEMORY" in Windows directory. So where would the dump files go? Should I change dump files location to some other folder like %Systemroot%/Minidump.dmp for kernel debugging option? If not then how would I be able to access the log files?

keyboardNinja, on May 3 2010, 01:11 AM, said:

Actually both topics are for same computer, but while solving one I emerged with another problem. I did not know that these topics would be considered for same problem. So I had started a new topic. Without one being solved it was difficult for the other one to be solved. If necessary topic312960 can be deleted. I will continue that topic's problem in this topic once this this original problem of 'dump file location' is solved.

The reason I pointed out the duplicate topics is this: conflicting advice can be given in both topics. If helper A in the other topic says to do "this", and I say to do "that"....everybody is confused when said advice doesn't work. Nobody has a clue what the other is trying to do, and we get nowhere. And we certainly can't coordinate advice between two topics and multiple helpers. That's why double-posting about the same computer/problem is a bad idea.

Okay, to find your dumps...I don't know why it is set the way it is (%Systemroot%/MEMORY.DMP). That is not the actual location. %Systemroot% is just your Windows directory. MEMORY.DMP is a file (with a .dmp extension). However, you will not find a .dmp file in your Windows directory. Don't ask me why...

In BlueScreenView > Options > Advanced Options >



Set it to what I have and see what comes up...

keyboardNinja, on May 3 2010, 08:35 PM, said:

The BlueScreenView does not show anything even in the minidump folder that you told. It is always empty. The BlueScreenView always shows 0 crashes. After I set the debugging mode to kernel mode I saw a file in windows directory named "MEMORY" (MEMORY.DMP). But it does not open. It neither opens with BlueScreenView nor with notepad. It has a file size of 82 MB. Now I have once again changed Write Debugging information to Small minidumps(64k) to see whether my system creates dump files now or not. If I get a small minidump file I will upload it. If you have any idea to open the MEMORY.DMP, then I will surely welcome the suggestion.

This time when I got BSOD I saw these significant things:

PAGE_FAULT_IN_NONPAGED_AREA.

***STOP: 0x00000050 (0xF5247C46, 0x00000001, 0x8057FB84, 0x00000000)

Also after BSOD restart my pc audio went off. The Soundmax control panel also appears half in size. The device manager also shows problem with 'Plug And Play Software Device Enumerator'. In the Device status of properties of this enumerator it is written that:

This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)