New
#21
Still crashing, I just froze with pretty much nothing open. Just pokerstars. Nothing is being produced(minidump or memory.dmp)
Still crashing, I just froze with pretty much nothing open. Just pokerstars. Nothing is being produced(minidump or memory.dmp)
Hello,
The reason why the Minidumps are not creating is because according to Event Viewer is
To fix itCode:Event[80]: Log Name: System Source: Microsoft-Windows-Subsys-SMSS Date: 2010-07-12T17:20:52.760 Event ID: 12 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Josh-PC Description: The crash dump file could not be created due to a lack of free space on the destination drive. Increasing the amount of free space on the destination drive may help prevent this error.
How to generate a kernel or a complete memory dump file in Windows Server 2008
Few time Windows Update failed with this error Windows Update error 8024001FClick Start, right-click Computer, and then click Properties.
Click Advanced system settings on the System page, and then click the Advanced tab.
Click Settings under the Writing debugging information area, and then replace the path with an appropriate value in the Dump file field. In other words, you can change the path from %SystemRoot%\Memory.dmp to point to a local drive that has enough disk space, such as E:\Memory.dmp.
Hope this helps,
Captain
Awesome, I hope it works. I tried changing it to just C:\Memory.dmp cause I don't have an E:\ next time it crashes hopefully it will produce some type of report.
Last edited by So1dier; 14 Jul 2010 at 22:20.
I just found out when I thought I was installing different drivers for my video card I really wasn't changing anything. It was just staying with my most updated driver cause it thought it was better. Anyways I figured out how to switch out drivers and I'm now testing the 10.5 version. So hopefully this will fix it.
Try freeing up some space on your hard drive, such as removing unnecessary programs, cleaning out your downloads folder, etc.
Here's a cool little app to help you: WinDirStat - Windows Directory Statistics
Hello,
Follow these steps provided by John !
Hope this helps,For Kernel memory dumps to be produced. . .
- Page file must be on OS drive (see kb307973 below)
- Page file base allocation size must be > than installed physical RAM
- Windows Error Reporting (WER) system service should be set to MANUAL
- Set page file to system managed, OS drive
Set System Crash/ Recovery Settings to "Kernel Memory Dump" - this will produce. . .
--> a Full Kernel Memory Dump - c:\windows\memory.dmp
--> a Mini Kernel dump c:\windows\minidump
The Full Kernel is overwritten each BSOD; a new mini kernel dump is created w/ different name for each BSOD
To check your system's "Recoveros" (Recovery) and Page File settings via Windows Management Instrumentation (WMI), download the EXE file - save to Desktop. RIGHT-click on EXE icon, select "Run as Administrator".
http://jcgriff2.com/0x2/WMIC_Recoveros_Pagefile_04-2010_jcgriff2_html.exe
IE 8 screen will open with the results.
For additional information, please see kb307973 --> How to configure system failure and recovery options in Windows
If no dump files are produced, the reason may be due to catastrophic hardware failure. The system would come down so fast in which case Windows 7 will do all possible to save itself and therefore may not have the time to produce a kernel memory dump - mini or full. The Event Viewer logs or WERCON would be a good source to verify that a BSOD has in fact occurred.
Regards. . .
jcgriff2
Captain
I went through that list with a friend and the only thing I could find that might help was changing the 2nd thing on the list.
- Page file base allocation size must be > than installed physical RAM
I have 4GB of ram and the default was set to 4096MB. I changed it to 6141MB so hopefully it has enough room to store a memory.dmp or minidump.
I haven't gotten a blue screen but my computer just crashed and it said...
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Like I said before the geek squad tested the PSU and they said it was fine. If it is the PSU I'm not even sure where I could get another one to test it out unless I spend another $80-$150. I might end up just sending the computer in to geek squad and paying the $75 so I can figure it out. But first I'll wait until I know I got a blue screen and make sure that no memory.dmp's are being produced.