BSOD, Freeze, and Restart

[So1dier]

Still crashing, I just froze with pretty much nothing open. Just pokerstars. Nothing is being produced(minidump or memory.dmp)

 

[Capt.Jack Sparrow]

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

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: 
[COLOR=Red][U][B]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[/B][/U][/COLOR].

To fix it

How to generate a kernel or a complete memory dump file in Windows Server 2008

Click 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.

Few time Windows Update failed with this error Windows Update error 8024001F

Hope this helps,
Captain

 

[So1dier]

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.

 

[So1dier]

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.

 

[CarlTR6]

I hope it works. Thanks for the update.

 

[Jonathan_King]

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

 

[Capt.Jack Sparrow]

Hello,

Follow these steps provided by John !

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

Hope this helps,
Captain

 

[So1dier]

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.

 

[Jonathan_King]

Is your PSU the one in your specs?

I would try another PSU in the machine if I were you.

 

[So1dier]

Is your PSU the one in your specs?

I would try another PSU in the machine if I were you.

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.

 

[So1dier]

Ya, I just got a blue screen and no memory.dmp was created...



I don't know why but my automatically restart was checked in system settings but that also doesn't happen. It just freezes on the blue screen and I have to manually press restart.

 

[Capt.Jack Sparrow]

Hello,

Check this article on forcing a System to crash and generate a Blue screen using Keyboard http://www.sevenforums.com/crash-lockup-debug-how/78561-enabling-dump-files-2.html#post855782 the last post my me

Hope this helps,
Captain

 

[So1dier]

Hello,

Check this article on forcing a System to crash and generate a Blue screen using Keyboard http://www.sevenforums.com/crash-lockup-debug-how/78561-enabling-dump-files-2.html#post855782 the last post my me

Hope this helps,
Captain

Ok, so I did what you told me to and it actually made a minidump and memory.dmp!!!!
What do I have to do now?

Memory.dmp and Minidump from the keyboard crash.

 

[So1dier]

My computer has crashed 4 times in the last 20 minutes, I just woke up and turned it on to try and get on world of warcraft.

Edit: If for some reason it made a successful minidump/memory.dmp how would I know that it has successfully made one(Because I already have an existing one with the keyboard crash)? It will just overwrite the file right? Should I delete the other minidump and memory.dmp?



Edit Edit: Also, I'm not sure if this has any relevance, but when my computer crashes ventrilo sometimes looses the password information to my vent channels.

 

[So1dier]

Bump.

Edit: My computer froze again. One thing I noticed is when it does get a blue screen it freezes on the blue screen which is probably why it doesn't finish making a report.


It says

dumping physical memory to disk: 80 or 60

and stays at that number so I have to manually press restart.

 

[Capt.Jack Sparrow]

Hello,

We really apologize for the delayed response. !!

So lets start with basic. First we will try to narrow down the issue. Lets see if some Hardware is causing the problem.

So i would recommend to run Hardware Diagnostic: Follow this link for instructions Hardware Diagnostic !! « Captain Debugger

There are few error messages in Event Viewer I'm listing that are specific ones.

There was a "Microsoft-Windows-CAPI2" error due to a certificate fail to download. Go to this link http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab Download and apply it.

Event Name: AEAPPINV2 a possible fix could be to update your BIOS Firmware GA-790XTA-UD4 (rev. 1.0) - GIGABYTE - Support&Download - Motherboard - BIOS

Event Name: RADAR_PRE_LEAK_WOW64:
It's basically referring to some kind of Process leak or a Kernel leak. But something hard to troubleshoot without seeing the PC. I'll list few troubleshooting steps which you try to fix the issue.

Open Task Manager then add the "Memory (Private Working Set)" column to Task Manager's Processes tab, and sort it in descending order see which process it taking up lot of Memory and see if it's stable or constantly spiking up

(or)

Download Processor Explorer

Open it then go to View | Select Columns | Check on Private Bytes

Then press OK. Then sort the list by Private Bytes and see which process it taking up lot of Memory and see if it's stable or constantly spiking up. Not down which process is leaking. If it's a process leak we can figure out this way. But if its a handle leak or Kernel leak then we have to dig more.

It's also possible the Kernel Memory Page Pool might also Paged out which can cause Bluescreen. We can use Poolmon.exe for that purpose. Try this article How to use Memory Pool Monitor (Poolmon.exe) to troubleshoot kernel mode memory leaks

Also you could Enable Driver Verifier http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html let it run few atleast 36 hours.

Then open Driver Verifier again the Select "Display information about the currently verified drivers" then click next. There is will Display the Drivers that has verified. Few you have more that one Drivers listed Click next then it will display the "Global counters" click next again there in a Drop down it will again show you the list of Drivers that has been verified.
Look for "Paged Pool - Bytes allocated" and if you see a Driver with high number then that the culprit.

Hope this helps,
Captain

 

[So1dier]

Np, thanks for the response. Just a couple days ago I changed my ram speed from 1600 to 1333MHz and I haven't crashed yet so hopefully that fixed it. I'm going to try running a couple games that are more likely to crash it and see what happens.

 

[Capt.Jack Sparrow]

Np, thanks for the response. Just a couple days ago I changed my ram speed from 1600 to 1333MHz and I haven't crashed yet so hopefully that fixed it. I'm going to try running a couple games that are more likely to crash it and see what happens.

Your Welcome ! Lets hope that solved the mystery In case of any issues post us back.

 

[CarlTR6]

Good news. Do let us know if that is the fix.

 

[So1dier]

Alright, well it's been a week and no crashes so I guess that was the problem. Before I bought my computer everyone said that my motherboard was 1600MHz RAM compatible. I don't know what this means but the majority of motherboards say something like 1333, 1600(OC), 1800(OC), etc. I'm guess the (OC) means there is a driver or setting in the bios that makes that RAM speed compatible as long as you know what to change. I only changed the ram speed from x6 to x8 in the bios making it 1600MHz.

Anyways I'm not to worried about the speed of the RAM, as I'm guessing it won't improve performance that much anyways, and I'm happy that my computer isn't crashing anymore. Thanks for the help guys . Time to play some games!!!