Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I have a Acer netbook with Windows 7 64bit (it is an Acer Aspire TimelineX AS1830T-3927) where I experience a crash every few days. No crash dump is generated and no log in the event viewer are found, even though I have both options set in the "Advanced System Settings" -> "Startup and Recovery" ("Write an event to system log" is set and "Write debugging information" is set to "Kernel memory dump").

I wasn't sure where I should expect the memory dump to be created (no Windows\Minidumps folder, no Windows\Memory.dmp file). Also no related 'problem' is available in the famous "Problem Reports and Solutions" section of the control panel.

Can anyone suggest how to further pursue this issue?

share|improve this question
    
Please further define 'crash'. Does the system shut down unexpectedly? Does it just 'freeze'? If it's freezing, can you still operate the mouse cursor when it is frozen? –  Ƭᴇcʜιᴇ007 Mar 25 '11 at 18:53
    
In 'crash' I mean that the screen goes black and the machine boot up from scratch, without a hint on the cause. –  Uri Cohen Mar 25 '11 at 21:12

1 Answer 1

Set the crash dump to small memory dump. Create the Minidump folder manually. See if it creates a dump file next crash. Be sure pagefile is enabled. Also see this article. I doubt it applies to most users but is worth a look.

http://support.microsoft.com/kb/2495523

.

This article is for XP but the cause section applies to Vista and W7 also

http://support.microsoft.com/kb/130536

The Memory.dmp file already exists and the option Overwrite Any Existing File (found in Control Panel System) is not selected. It is a good idea to leave this box checked and to move or copy the current Memory.dmp file.

The paging file on the boot drive is not large enough. To use the "Write Debugging Information To" feature to obtain a complete memory dump file, the paging file on the boot drive must be at least as large as physical memory + 1 MB. When you create a kernel memory dump file, the file is usually around one-third the size of the physical memory on the system. Of course, this quantity will vary, depending on your circumstances.

The paging file is not on the %systemroot% partition. When the STOP error occurs, the system crash dump is written out to the pagefile on the root of the %systemroot% drive. There is not room for the Memory.dmp file in the path specified in Control Panel for writing the memory dump.

It is possible that the SCSI controller is bad or the system crash is caused by a bad SCSI controller board.

If you specify a non-existent path, a dump file will not be written. For example, if you specify the path as C:\Dumpfiles\Memory.dmp and no C:\Dumpfiles folder exists, a dump file will not be written.

.

As a last resort you can uncheck the "automatically restart" in the startup and recovery settings. This way you can at least see the bsod message and write it down. While you are in there Uncheck "overwrite any existing file"

. enter image description here

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.