Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Crash Analysis and Debugging › Beginner BSOD Crash Dump Analysis and Debugging Guide
New Posts  All Forums:Forum Nav:

Beginner BSOD Crash Dump Analysis and Debugging Guide

post #1 of 27
Thread Starter 

pjBSOD's Beginner Crash Dump Analysis and Debugging Guide for Windows



Please do not post your BSOD related issues here, or PM me with any questions, ask them here. If you're having blue screens and would like them analyzed, post a thread in the Crash Analysis and Debugging forum as this thread is strictly for learning how to analyze and debug dump files at the most basic level. You're also more than welcome to PM'ing me if you need a crash dump file analyzed / BSOD related assistance. Thanks smile.gif

** Last updated 8/20/2013

pjBSOD, what's the point of this thread, why did you even make this guide?

It's very simple, actually. I made this thread because blue screens are and have always been a huge problem, and a VERY large number of PC users (even PC Enthusiasts and builders) don't know how to analyze dump files to troubleshoot their issues, or the issues of a family computer, etc. Growing up and using computers, when I got BSOD, it was the end of the world to me. I'd see this blue screen with a bunch of numbers and technical mumbo jumbo, and none of it made sense to me, because to me, it was just "Oh crap, I'm screwed, I have no idea what to do.. I think I'll just reformat if it gets really bad", and this is unfortunately the case with a lot of people. Some people don't even know how to reformat a computer, or have access to a disk, so they pay a Geek Squad or some other local repair shop HUNDREDS of dollars to reformat a computer.

Another big reason I made this guide is because analyzing and debugging crash dump files should not be a secret, it should be available to read and learn on every computer forum.

pjBSOD, why should I learn how to debug dump files with WinDbg if there are programs like BSV (Blue Screen View) out there?

I go into my personal opinion / rant on BSV later in this post, you can read it there.

Disclaimer

This guide will not turn you into a Crash Dump Analysis Guru. For example, you won't be like that guys that work at Microsoft that can take a look at a stack of memory in a dump and go "Okay, here's what caused it", or like the various MVP's across forums that are expert analysts, etc. This is simply a beginner guide I have written and compiled to give you a head-start / idea. Knowledge like that with this takes years of schooling, years of reading over dump files to get used to it and learn it.

If you truly want to be one of those people, all it takes is practice and a will to learn and work for it like everything else. Hang out around BSOD sections on forums, read blogs, study bugchecks and their usual causes, see popular culprits, etc. It's all a matter of practice and a will to learn.

Alright, sounds good, where do I begin and what do I need to analyze dump files?

A) You're going to need the Windows Debugging Tools, or better known as "WinDbg". Download the appropriate tools for your version of Windows from here.

If you're running 32 bit Windows, download the 32 bit Debugging Tools. If you're running 64 bit Windows, download the 64 bit Debugging Tools. You'll still be able to debug x64 dumps if you've installed the x32 bit, same with x64 and debugging x32 dumps.

B) Once you've downloaded and installed the Windows Debugging Tools, you have to configure WinDbg before you start analyzing dumps. The most important part of configuring the debugging tools is the symbol path, so pay attention:

1. Open WinDbg, but do not open any dump files, just open WinDbg.

2. Go to File>Symbol File Path or alternatively hit Ctrl+S.

3. Set the Symbol File Path to:
4. Click "Ok" and exit WinDbg.

5. It should ask you if you'd like to save the workspace, click "Yes".

Basically, in short, we set this symbol path because it caches each symbol it has to download from the Microsoft symbol server. So, rather than taking forever to load a dump file, since it has already been cached in the past, it will load quickly so you can get to analyzing faster. Do note that the Microsoft symbol file does NOT contain 3rd party drivers, but we'll get to that later.

C) There are other OPTIONAL things you can setup for your WinDbg. If want to get right to analyzing, skip this.

1. One optional thing you can do is setup WinDbg to be the default application / program for crash dump related files. I really recommend doing this as instead of having to open up WinDbg, hitting Ctrl+O to open a dump, etc... you can easily just double click the dump file in question and WinDbg will take care of the rest. In layman's terms, it saves a ton of time. Thanks to H2S04 over at SevenForums for this option!

- Run CMD as admin (elevated command prompt)

-

C:\> cd debuggers

(If it doesn't change directory automatically, you'll have to specify the entire path... for example, I type the following to get to my windbg:

cd \ (this will send you to root)

cd program files (x86)\windows kits\8.0\debuggers\x86

Once inside specified .EXE directory, type the following:

C:\program files (x86)\windows kits\8.0\debuggers\x86> windbg.exe -IA

- In response, WinDBG should pop up a dialog box that says this:

WinDbg:6.11.0001.402 AMD64
WinDbg successfully registered file assocations for .DMP, .HDMP, .MDMP, .KDMP and .WEW.
OK

pjBSOD, I've set all of this up, but for some reason crash dumps aren't being generated! What should I do?

Ensure and know the following things first:

  • In order for crash dumps to be written, your Page file must be on the OS drive.
  • Page file allocation size must be greater than the physical amount of installed RAM. Also ensure that the Page file is set to system managed.


If you're curious and how to get more info on your Page file, there's two methods of doing this:

1. Run CMD as admin (elevated command prompt) and paste / type the following:
Quote:
SystemPropertiesPerformance.exe /pagefile

2. Paste / type the following into the Windows search box:
Quote:
SystemPropertiesPerformance.exe /pagefile

Quick in-depth tutorial on how to ensure dumps are being generated:

1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.

2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.

3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log' > Ensure 'Automatically restart' is un-checked.

Ensure Small memory dump is selected and ensure the path is %SystemRoot%\Minidump.

4. Double check that the WERS is ENABLED:

Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

Regarding Blue Screen View:

*Note that I'll be abbreviating Blue Screen View with BSV.

BSV, where do I even begin. Well, first off, I should probably say that BSV in layman's terms is a simplified WinDbg. With that said, it misses a lot of information that WinDbg provides that will help you solve BSOD related issue. For example, one of the very basic things you cannot do out of the many compared to WinDbg, is you cannot view the currently loaded modules / drivers at the time of the crash from that specific dump. This is very important because the "probably caused by", PROBABLY BEING THE KEYWORD, is not always the key to solving BSODs. There are also many other examples, but the modules one is a big one / easy one to mention.

With this being said, BSV is a great program, so hats off to the creator(s), however, for fully accurate debugging and analysis, the best way to go is WinDbg, especially if you want to learn.

An important thing to note about assisting individuals that are having BSOD's / something to think about:

I can assume you're reading this guide for two main reasons. Either it's one out of the two or both, and that's to analyze dump files yourself and gain personal knowledge, and to learn to analyze dumps files to assist others who are having issues. With the latter in mind, it's very important to be patient, respectful, calm, and VERY informative (don't be lazy and skimp out of details). This goes for BOTH parties, the user having the issue, and the person analyzing and debugging said crash dumps.

From an analysts point of view, it's very important that the user you're assisting is being respectful and is following your instructions carefully. The thing that's important to realize is crash analysis and debugging is mutual as I have mentioned earlier. If the user you're assisting is being informative and respectful, it makes it very easy for the person analyzing your dumps to do the same and provide the best assistance as you're being cooperative and following all of the instructions given to you.

Bottom line is, both parties need to maintain a bond of patience, respect and most of all, trust. If either is not, it makes the analysis very difficult and the user having the issues will likely not receive the best help possible, or any help at all. An important thing to note, if the user for whatever reason is being very disrespectful, will not cooperate, etc, simply make the choice of whether or not you'd like to continue helping this user, do NOT make it personal.

D) With all of this being said, once you have WinDBG's Symbol File Path all set up, we can now begin analyzing dump files! See the next post smile.gif
Desktop
(18 items)
 
   
CPUMotherboardGraphicsRAM
i7-2600K Asus P8P67 Pro Asus Radeon HD 5850 Corsair Vengeance 8GB DDR3 
Hard DriveCoolingOSMonitor
Samsung Spinpoint F3 1TB Corsair H70 Windows 7 Professional x64 Acer AL2216Wbd 22" 
MonitorMonitorKeyboardPower
Acer V223Wbd 22" Acer V223Wbd 22" Das Ultimate Blank Corsair CMPSU-750TX v2 
CaseMouseAudioOther
LIAN LI Lancool PC-K56 Razer Lachesis X-Fi Titanium Fata1ity Professional Logitech z-5500 
CPUMotherboardGraphicsRAM
Intel Core i7-4770 Haswell 3.4GHz LGA 1150 84W ... GIGABYTE GA-Z87X-UD3H LGA 1150 Intel Z87 HDMI S... MSI Gaming N770 TF 2GD5/OC GeForce GTX 770 2GB ... G.SKILL Trident X Series 16GB (2 x 8GB) 240-Pin... 
Hard DriveCoolingPowerCase
SAMSUNG 840 Pro Series MZ-7PD128BW 2.5" 128GB ...  CORSAIR Hydro Series H100i Water Cooler  CORSAIR GS800 800W ATX12V v2.3 SLI Ready Cross...  Corsair Obsidian Series 800D CC800DW Black Alu... 
  hide details  
Reply
Desktop
(18 items)
 
   
CPUMotherboardGraphicsRAM
i7-2600K Asus P8P67 Pro Asus Radeon HD 5850 Corsair Vengeance 8GB DDR3 
Hard DriveCoolingOSMonitor
Samsung Spinpoint F3 1TB Corsair H70 Windows 7 Professional x64 Acer AL2216Wbd 22" 
MonitorMonitorKeyboardPower
Acer V223Wbd 22" Acer V223Wbd 22" Das Ultimate Blank Corsair CMPSU-750TX v2 
CaseMouseAudioOther
LIAN LI Lancool PC-K56 Razer Lachesis X-Fi Titanium Fata1ity Professional Logitech z-5500 
CPUMotherboardGraphicsRAM
Intel Core i7-4770 Haswell 3.4GHz LGA 1150 84W ... GIGABYTE GA-Z87X-UD3H LGA 1150 Intel Z87 HDMI S... MSI Gaming N770 TF 2GD5/OC GeForce GTX 770 2GB ... G.SKILL Trident X Series 16GB (2 x 8GB) 240-Pin... 
Hard DriveCoolingPowerCase
SAMSUNG 840 Pro Series MZ-7PD128BW 2.5" 128GB ...  CORSAIR Hydro Series H100i Water Cooler  CORSAIR GS800 800W ATX12V v2.3 SLI Ready Cross...  Corsair Obsidian Series 800D CC800DW Black Alu... 
  hide details  
Reply
post #2 of 27
Thread Starter 

Crash Dump analysis basics and extras



If you're reading this post, you've set up your WinDbg to properly open dump files and you can begin analyzing dump files! Great smile.gif

**Before we begin, there's something relatively important to mention. If you or the user you're assisting has their system overclocked in any way, whether it be their GPU or their CPU or even their RAM, return your clocks back to factory defaults, or tell them to do the same. An unstable overclock will cause issues and is actually the leading cause (aside from buggy drivers) of BSODs. You or the user are more than welcome to continue overclocking after their issue has been solved.


A) First off, analyzing dump files will depend on how you set it up and if you followed the optional step to save time in opening dump files. If you did not follow the optional step, simply open WinDbg, Ctrl+O and navigate to the location of your dump file that you want to be analyzed. If you DID follow the optional step, simply double click the dump file and WinDbg will do the rest for you.

B) Once you've opened your dump, you should see this (I'll be using a very easy dump file that I've analyzed a few months back with a very simple culprit as our first example):

358

Once you see that, click the small window containing the information and drag it onto the debugger program. Once you've done that, it should look like this:

358

C) Now that you have dragged the window out onto the debugger window, I'll explain what all of what you see so far means.

1. So, as you can see, it starts off by showing the Symbol Search Path, then it shows the executable search path, then the OS version, system uptime, etc. So right off the bat, what do you notice anything important before it says "Loading Kernal Symbols"? Well, if you couldn't guess, the important thing was system uptime. System Uptime is a very important thing to look at as in many cases it can tell YOU the person analyzing the dumps generally how long the user's rig goes before crashing.

For example, say a user's rig boots up and immediately crashes, system uptime is almost nothing, not even a few minutes... it's likely a 3rd party driver on start up (you can of course find out further via the bugcheck and the probably caused, but we'll go into that later). However, if a user goes DAYS without an issue, maybe even a week, it's likely a random hardware issue, possibly memory. It's also important to know that very large amounts of system uptime will cause memory leaks, etc.

2. Moving on past System Uptime, the next thing is it's loading the symbols. After it does that, you can say it says in my example:

"Unable to load image \SystemRoot\system32\DRIVERS\avckf.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for avckf.sys
*** ERROR: Module load completed but symbols could not be loaded for avckf.sys"

As I said earlier, the reasoning behind this driver having no symbols off of the symbol server is because it is a 3rd party driver not supported by Microsoft, therefore it is not in their symbol server. So right off of the bat, it's saying.. "Hey. this 3rd party driver, it's the culprit, and I have no idea who it cause, cause it ain't from my company."

3. Moving on past that, it'll tell you to use the kd> command !analyze -v to get detailed bugging information (you can click this or type this into the kd> command box).

What is !analyze v and what sort of information does it give you? The v in "analyze v" stands for "verbose", basically giving you more detailed debugging information, just like it says. You'll want to click this or type this after I am done explaining the rest.

After that you see a bugcheck code or better known as a STOP code (what you see on the blue screen, and then it goes black). Say the dump is unanalyzable, it's just giving a stop code as usual, but it's not giving a non-Microsoft related fault or anything. Well, one thing you can do (but I will explain what you SHOULD do) is take a look at the stop code.

For example, say the stop code is a D1 bugcheck, aka.. the famous IRQL NOT LESS OR EQUAL. We know (or may not know) that this crash can be stemmed from: A device driver has a bug and attempted to access invalid memory, the pagefile has been corrupted or there is a memory problem.

So, you can tell the user to do things based off of what you see for the stop code, etc.

4. After that, in my example, you see "Probably caused by : avckf.sys ( avckf+183d )"

Probably caused by is basically Windows saying "Hey, I'm pretty sure this is the driver that caused me to crash". In most cases, Windows is thankfully and fortunately right. However, in some cases, you may get an incorrect probable fault. Why does this happen? Well, because sometimes Windows does not know what caused it to crash, so it'll point to an incorrect probably cause, which in most cases is a Microsoft related driver or file.

For example, Windows will point to a very important core Windows file. The reasoning for these core / important files not being the crashes (very very unlikely, in all my months of debugging I have never seen an OS file be a culprit) is because these Microsoft files are protected by the SFC (System File Checker), and are very hard to become corrupt or the actual culprit... very hard.

I'll go further into how to make a false cause analyzeable later.

5. So, you see "Probably caused by : avckf.sys ( avckf+183d )". Well, what you're going to want to do is now type (or click) that !analyze -v command. Once you've done that, a bunch of technical mumbo jumbo should appear and scroll down, and then eventually end. Once it ends, simply scroll up to where you previously were.

Right off of the bat, it gives the stop code, and a short description (if it can and if it's a popular stop code).
Quote:
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.

In other words, there was a bug in a driver and it forced a crash. As you scroll down, you'll see memory that couldn't be reference, stack texts, etc. What we're interested in is the module that crashed (or the driver). As we saw earlier, the probable cause and module that crashed is: avckf.sys. Now, I already know right off the bat what avckf.sys is, but you're new to this, so you very likely have no idea what this driver is and what it does. Well, as we said earlier, since it is not a Microsoft driver and it's a 3rd party driver, we'll want to use the Carrona Reference Table.

The Corrona Reference Table is pretty much any 3rd party driver you can think of right there, what program(s) uses it, and where to update it if need be. So now that we're here, we'll want to hit Ctrl+F and search our probably caused fault / faulting driver (avckf.sys). Once we do that and hit enter, we'll see that avckf.sys is the BitDefender Active Virus Control Kernel Filtering driver. So right then and there, the culprit is BitDefender.

What you'd do at this point is fully uninstall / remove Bit Defender from the system, install Microsoft Security Essentials for testing purposes, and see if you can reproduce the same crash. If you cannot, you know that BitDefender was the cause, and you can try and reinstall it or choose another AV.

D) So there, that's it... those are the basics and some extra information on how to analyze a dump file. I do not stop there however, I check a few more things before I make a post and tell a person to do so and so, specifically speaking the loaded modules list / drivers list. In the next post, I'll explain further into that smile.gif
Desktop
(18 items)
 
   
CPUMotherboardGraphicsRAM
i7-2600K Asus P8P67 Pro Asus Radeon HD 5850 Corsair Vengeance 8GB DDR3 
Hard DriveCoolingOSMonitor
Samsung Spinpoint F3 1TB Corsair H70 Windows 7 Professional x64 Acer AL2216Wbd 22" 
MonitorMonitorKeyboardPower
Acer V223Wbd 22" Acer V223Wbd 22" Das Ultimate Blank Corsair CMPSU-750TX v2 
CaseMouseAudioOther
LIAN LI Lancool PC-K56 Razer Lachesis X-Fi Titanium Fata1ity Professional Logitech z-5500 
CPUMotherboardGraphicsRAM
Intel Core i7-4770 Haswell 3.4GHz LGA 1150 84W ... GIGABYTE GA-Z87X-UD3H LGA 1150 Intel Z87 HDMI S... MSI Gaming N770 TF 2GD5/OC GeForce GTX 770 2GB ... G.SKILL Trident X Series 16GB (2 x 8GB) 240-Pin... 
Hard DriveCoolingPowerCase
SAMSUNG 840 Pro Series MZ-7PD128BW 2.5" 128GB ...  CORSAIR Hydro Series H100i Water Cooler  CORSAIR GS800 800W ATX12V v2.3 SLI Ready Cross...  Corsair Obsidian Series 800D CC800DW Black Alu... 
  hide details  
Reply
Desktop
(18 items)
 
   
CPUMotherboardGraphicsRAM
i7-2600K Asus P8P67 Pro Asus Radeon HD 5850 Corsair Vengeance 8GB DDR3 
Hard DriveCoolingOSMonitor
Samsung Spinpoint F3 1TB Corsair H70 Windows 7 Professional x64 Acer AL2216Wbd 22" 
MonitorMonitorKeyboardPower
Acer V223Wbd 22" Acer V223Wbd 22" Das Ultimate Blank Corsair CMPSU-750TX v2 
CaseMouseAudioOther
LIAN LI Lancool PC-K56 Razer Lachesis X-Fi Titanium Fata1ity Professional Logitech z-5500 
CPUMotherboardGraphicsRAM
Intel Core i7-4770 Haswell 3.4GHz LGA 1150 84W ... GIGABYTE GA-Z87X-UD3H LGA 1150 Intel Z87 HDMI S... MSI Gaming N770 TF 2GD5/OC GeForce GTX 770 2GB ... G.SKILL Trident X Series 16GB (2 x 8GB) 240-Pin... 
Hard DriveCoolingPowerCase
SAMSUNG 840 Pro Series MZ-7PD128BW 2.5" 128GB ...  CORSAIR Hydro Series H100i Water Cooler  CORSAIR GS800 800W ATX12V v2.3 SLI Ready Cross...  Corsair Obsidian Series 800D CC800DW Black Alu... 
  hide details  
Reply
post #3 of 27
Thread Starter 

Using the Modules list to find a culprit driver, etc



If you're reading this post, you've learned the basics of analyzing a dump file. Now, in this post, I'll explain how you would use the loaded modules (or drivers) list to find possible 3rd party culprits, drivers that need to be updated, etc.

Before we begin, there's a general theory for updating and downloading drivers...
Quote:
Driver search theory:
- Look for drivers at the website of the company that made the device/program. They have the most updated drivers for their stuff.
- If they don't offer drivers, then search Google for drivers from the PC/Mobo (OEM) manufacturers - and pick the most updated one from there.
- As a last resort, get drivers from the support website for the manufacturer of your PC/Mobo.
- DON'T get drivers from Windows Update or the Update drivers function of Device Manager. They only search for drivers at the Windows Update website and most often will not be the most updated version available.

A) First off, there's two ways to showing the loaded modules in WinDbg. I prefer the second way, but I'll show both of course.

1. The first method is via commands. In the kd> command box, type "lmntsm" without the quotes. What does this mean and what does this do?

lm = loaded driver listing.

n = displays the image name.

t = timestamp information.

lmnt - All together, this displays the loaded driver list in order of memory address.

Alternatively, you can type lmntsm.

lmnt = see above explanation.

sm = sorts the display by module name, so it's alphabetical and you don't have to sort through drivers to find the one you're looking for.

2. The second method (my preferred as it's faster and easier to me) is to click Debug > Modules. This will open up a window containing the loaded drivers.

Now that I have explained these methods, I'll further elaborate on why you'd want to even be looking this the loaded modules list in the first place. The loaded modules will show any driver (even 3rd party) that was loaded at the time of the crash. Now, what you'd do is take a look at this list to make sure the user doesn't have any outdated drivers, or a very popular culprit drivers. For example, a driver that is very guilty of causing BSODs in the Windows 7 environment is dtsoftbus01.sys (Daemon Tools driver). Now, the general beginner analyzer will not know this. Learning what drivers are popular culprit drivers takes a lot of analysis and a lot of reading various forums, taking a look at different completed analysis threads, etc.

Another example of a popular culprit driver is sptd.sys (driver for image virtualization programs such as Alcohol or Daemon Tools). There are tons, I am just giving a few examples.

Now, what I always do first when opening up this sort it by Symbol File. This alphabetically sorts the loaded drivers so I can run down the list to ensure there are no loaded popular culprit drivers. If there are, I'd tell the user to fully remove / uninstall the program that driver uses. If there are none, move on.

Once you've taken a look alphabetically at the loaded modules list, you'll next then want to sort it by Timestamp to see if there are any out of date drivers. What's considered 'out of date' depends on the OS. However, generally, it's easy enough to say that 'out of date' in regards to a drive is anything but the latest version for that specific OS.

Now, you may be asking.. "Okay, I get it.. culprit drivers and out of date drivers. So, if I see either, how will I know which program uses that driver, and where to update a driver that is out of date"? Good question, you'll want to look at this page here.

So, now that we've ironed out the basics of crash dump analysis and how to use the loaded modules list to find culprits, you may be asking how would you make an unanalyzable crash dump... analyzable. Well, I'll explain that in the next post smile.gif
Desktop
(18 items)
 
   
CPUMotherboardGraphicsRAM
i7-2600K Asus P8P67 Pro Asus Radeon HD 5850 Corsair Vengeance 8GB DDR3 
Hard DriveCoolingOSMonitor
Samsung Spinpoint F3 1TB Corsair H70 Windows 7 Professional x64 Acer AL2216Wbd 22" 
MonitorMonitorKeyboardPower
Acer V223Wbd 22" Acer V223Wbd 22" Das Ultimate Blank Corsair CMPSU-750TX v2 
CaseMouseAudioOther
LIAN LI Lancool PC-K56 Razer Lachesis X-Fi Titanium Fata1ity Professional Logitech z-5500 
CPUMotherboardGraphicsRAM
Intel Core i7-4770 Haswell 3.4GHz LGA 1150 84W ... GIGABYTE GA-Z87X-UD3H LGA 1150 Intel Z87 HDMI S... MSI Gaming N770 TF 2GD5/OC GeForce GTX 770 2GB ... G.SKILL Trident X Series 16GB (2 x 8GB) 240-Pin... 
Hard DriveCoolingPowerCase
SAMSUNG 840 Pro Series MZ-7PD128BW 2.5" 128GB ...  CORSAIR Hydro Series H100i Water Cooler  CORSAIR GS800 800W ATX12V v2.3 SLI Ready Cross...  Corsair Obsidian Series 800D CC800DW Black Alu... 
  hide details  
Reply
Desktop
(18 items)
 
   
CPUMotherboardGraphicsRAM
i7-2600K Asus P8P67 Pro Asus Radeon HD 5850 Corsair Vengeance 8GB DDR3 
Hard DriveCoolingOSMonitor
Samsung Spinpoint F3 1TB Corsair H70 Windows 7 Professional x64 Acer AL2216Wbd 22" 
MonitorMonitorKeyboardPower
Acer V223Wbd 22" Acer V223Wbd 22" Das Ultimate Blank Corsair CMPSU-750TX v2 
CaseMouseAudioOther
LIAN LI Lancool PC-K56 Razer Lachesis X-Fi Titanium Fata1ity Professional Logitech z-5500 
CPUMotherboardGraphicsRAM
Intel Core i7-4770 Haswell 3.4GHz LGA 1150 84W ... GIGABYTE GA-Z87X-UD3H LGA 1150 Intel Z87 HDMI S... MSI Gaming N770 TF 2GD5/OC GeForce GTX 770 2GB ... G.SKILL Trident X Series 16GB (2 x 8GB) 240-Pin... 
Hard DriveCoolingPowerCase
SAMSUNG 840 Pro Series MZ-7PD128BW 2.5" 128GB ...  CORSAIR Hydro Series H100i Water Cooler  CORSAIR GS800 800W ATX12V v2.3 SLI Ready Cross...  Corsair Obsidian Series 800D CC800DW Black Alu... 
  hide details  
Reply
post #4 of 27
Thread Starter 

Make an unanalyzable crash dump file analyzable



If you're reading this post, you know the basics of crash dump analysis and how to check a loaded drivers list for out of date drivers and possible culprits. In this post, I will explain how to make an unanalyzable dump file analyzable. Do note that in rare occasions in which hardware is the final culprit, a 3rd party driver will never be displayed as the culprit, and the bugcheck will be a hardware related bugcheck.

A) So, you're analyzing a dump of yours or a family member's and it's not showing anything. You cannot find any probable cause in multiple dumps, and there's nothing really hinting to your knowledge in the loaded modules list. For example, the dumps are constantly showing core Microsoft files and drivers in every dump, and never displaying a 3rd party driver. The next best thing to do is enable what's called Driver Verifier.

Now, you may be asking "What the heck is Driver Verifier?", well, Driver Verifier is possibly the best thing to be graced upon crash dump analysts and debuggers. Driver Verifier runs in the background after you've enabled it and "stresses" all 3rd party drivers you've chosen. If it finds a driver in violation, it'll force a BSOD and write a very detailed crash dump file (or better known as a verifier enabled dump) about the driver that forced this crash.

Here's a guide on what Driver Verifier does and how to use it.


DO NOTE, as with any crash, Driver Verifier has a chance of corrupting your OS installation. I recommend making a backup if you can or if you wish, but you don't have to. I very rarely have seen Driver Verifier corrupt an OS, but it does happen, just like with every other BSOD and crash.


Once you have enabled Driver Verifier, or told the user to enable it for further analysis, use the computer as you would regularly. Browse the internet, play games, do whatever you want I generally recommend keeping Driver Verifier enabled for at LEAST ~48 hours. If it has not forced a crash by then, it's very very unlikely your issue is driver related, but actually hardware related.

If and once Driver Verifier forces a crash, the PC will restart as usual. Once you're in Windows, it will have written a verifier enabled dump which will be the LATEST dump file. Once you have it, open it up like we've been doing and take a look. Right off the bat, if it's software / driver related, it should it has issues loading the symbols / timestamp for the driver as it'll be a 3rd party driver not stored on the Microsoft symbol server. As we've been doing, run the command !analyze v, and it'll tell you all about this driver and more information as we've discussed before.

B) Sometimes after enabling Driver Verifier, it'll still show core Microsoft files and drivers, and if there are different bugchecks every time, or random bugchecks, it's very likely hardware related. At this point, I would then recommend whatever I feel necessary, whether it may Memtest, or a video memory stress test, or a chkdsk, etc. It all depends on what the bugchecks are showing, and what the probable causes are showing as well in some cases.

1. For example, I'd recommend running Memtest in a situation in which a dump or multiple dumps are showing probably caused faults as memory management issues or memory corruption faults. These two are very likely due to bad memory, or an unstable overclock. As we've discussed earlier, always bring your clocks back to stock when diagnosing BSOD issues, or always tell user's to bring their clocks back to stock.

2. If you're getting bugchecks that relate to sometimes OS file corruption, etc, tell the user to run a chkdsk or a hard drive diagnostic if they have one available (Seagate has great HDD diagnostic tools).

This concludes our thread. With this thread, you should learn the basics and more when it comes to crash dump analysis and debugging. There is another whole world to crash dump analysis and debugging, but like having an expertise in everything, this requires much schooling and reading, and most of the information is not free. In the next and final post, I will link to great references and links you can and should turn to for reading and analysis.
Desktop
(18 items)
 
   
CPUMotherboardGraphicsRAM
i7-2600K Asus P8P67 Pro Asus Radeon HD 5850 Corsair Vengeance 8GB DDR3 
Hard DriveCoolingOSMonitor
Samsung Spinpoint F3 1TB Corsair H70 Windows 7 Professional x64 Acer AL2216Wbd 22" 
MonitorMonitorKeyboardPower
Acer V223Wbd 22" Acer V223Wbd 22" Das Ultimate Blank Corsair CMPSU-750TX v2 
CaseMouseAudioOther
LIAN LI Lancool PC-K56 Razer Lachesis X-Fi Titanium Fata1ity Professional Logitech z-5500 
CPUMotherboardGraphicsRAM
Intel Core i7-4770 Haswell 3.4GHz LGA 1150 84W ... GIGABYTE GA-Z87X-UD3H LGA 1150 Intel Z87 HDMI S... MSI Gaming N770 TF 2GD5/OC GeForce GTX 770 2GB ... G.SKILL Trident X Series 16GB (2 x 8GB) 240-Pin... 
Hard DriveCoolingPowerCase
SAMSUNG 840 Pro Series MZ-7PD128BW 2.5" 128GB ...  CORSAIR Hydro Series H100i Water Cooler  CORSAIR GS800 800W ATX12V v2.3 SLI Ready Cross...  Corsair Obsidian Series 800D CC800DW Black Alu... 
  hide details  
Reply
Desktop
(18 items)
 
   
CPUMotherboardGraphicsRAM
i7-2600K Asus P8P67 Pro Asus Radeon HD 5850 Corsair Vengeance 8GB DDR3 
Hard DriveCoolingOSMonitor
Samsung Spinpoint F3 1TB Corsair H70 Windows 7 Professional x64 Acer AL2216Wbd 22" 
MonitorMonitorKeyboardPower
Acer V223Wbd 22" Acer V223Wbd 22" Das Ultimate Blank Corsair CMPSU-750TX v2 
CaseMouseAudioOther
LIAN LI Lancool PC-K56 Razer Lachesis X-Fi Titanium Fata1ity Professional Logitech z-5500 
CPUMotherboardGraphicsRAM
Intel Core i7-4770 Haswell 3.4GHz LGA 1150 84W ... GIGABYTE GA-Z87X-UD3H LGA 1150 Intel Z87 HDMI S... MSI Gaming N770 TF 2GD5/OC GeForce GTX 770 2GB ... G.SKILL Trident X Series 16GB (2 x 8GB) 240-Pin... 
Hard DriveCoolingPowerCase
SAMSUNG 840 Pro Series MZ-7PD128BW 2.5" 128GB ...  CORSAIR Hydro Series H100i Water Cooler  CORSAIR GS800 800W ATX12V v2.3 SLI Ready Cross...  Corsair Obsidian Series 800D CC800DW Black Alu... 
  hide details  
Reply
post #5 of 27
Thread Starter 

Additional links to check out and various references



General reference links:

Driver Reference Table. This lists practically every driver there is in a handy reference table. Refer to this when analyzing and debugging crash dump files if you need to. Created and maintained by John Carrona, Microsoft Expert-Consumer MVP since 2006!

Driver Download Sites. Contains links to where a driver is hosted and where to download it / update it. If a driver isn't available for download via the reference table, or you want to look here regardless.

Bugcheck or STOP Code Index. Great link for reading up on STOP codes and what causes those STOP codes.

Antivirus Uninstallers. Great blog post that provides Antivirus Uninstaller links (always recommended to use rather than using the traditional Programs & Features uninstall method). Written by Corrine, Microsoft MVP since 2006 in Consumer Security!

Troubleshooting Windows STOP Messages. Great link on how to troubleshoot various different STOP codes.

Fatal BSOD Solutions. Contains links to various different STOP codes, what causes them, how to troubleshoot, etc.

Seven Forums "Crash and lockup debug 'How to'. Contains various references and tutorials on how to analyze crash dumps with certain STOP codes.

Windows Hang and Crash Dump Analysis 1/9. Contains a NINE part video series on how to analyze and debug crash dumps.

Troubleshooting Microsoft Event Viewer Logs. Great website in which you can enter the Event ID and get details on that specific event entry you may have questions about.

Debugging In Progress - A TechNet blog about debugging and analyzing BSODs. Wonderful source of information, a bit advanced.

My BSOD blog. I update it almost daily with solved posts, debugging information, etc.

Forums to check out if you're looking to brush up on your analysis and debugging skills:

Sysnative BSOD, Crashes, Kernel Debugging.

TechSupportForum BSOD, App Crashes And Hangs.

Very informative books on analysis and debugging & more:

Windows Internals, Part 1: Covering Windows Server 2008 R2 and Windows 7

Windows Internals, Part 2: Covering Windows Server® 2008 R2 and Windows 7

Advanced Windows Debugging

Thanks for reading my thread.
Desktop
(18 items)
 
   
CPUMotherboardGraphicsRAM
i7-2600K Asus P8P67 Pro Asus Radeon HD 5850 Corsair Vengeance 8GB DDR3 
Hard DriveCoolingOSMonitor
Samsung Spinpoint F3 1TB Corsair H70 Windows 7 Professional x64 Acer AL2216Wbd 22" 
MonitorMonitorKeyboardPower
Acer V223Wbd 22" Acer V223Wbd 22" Das Ultimate Blank Corsair CMPSU-750TX v2 
CaseMouseAudioOther
LIAN LI Lancool PC-K56 Razer Lachesis X-Fi Titanium Fata1ity Professional Logitech z-5500 
CPUMotherboardGraphicsRAM
Intel Core i7-4770 Haswell 3.4GHz LGA 1150 84W ... GIGABYTE GA-Z87X-UD3H LGA 1150 Intel Z87 HDMI S... MSI Gaming N770 TF 2GD5/OC GeForce GTX 770 2GB ... G.SKILL Trident X Series 16GB (2 x 8GB) 240-Pin... 
Hard DriveCoolingPowerCase
SAMSUNG 840 Pro Series MZ-7PD128BW 2.5" 128GB ...  CORSAIR Hydro Series H100i Water Cooler  CORSAIR GS800 800W ATX12V v2.3 SLI Ready Cross...  Corsair Obsidian Series 800D CC800DW Black Alu... 
  hide details  
Reply
Desktop
(18 items)
 
   
CPUMotherboardGraphicsRAM
i7-2600K Asus P8P67 Pro Asus Radeon HD 5850 Corsair Vengeance 8GB DDR3 
Hard DriveCoolingOSMonitor
Samsung Spinpoint F3 1TB Corsair H70 Windows 7 Professional x64 Acer AL2216Wbd 22" 
MonitorMonitorKeyboardPower
Acer V223Wbd 22" Acer V223Wbd 22" Das Ultimate Blank Corsair CMPSU-750TX v2 
CaseMouseAudioOther
LIAN LI Lancool PC-K56 Razer Lachesis X-Fi Titanium Fata1ity Professional Logitech z-5500 
CPUMotherboardGraphicsRAM
Intel Core i7-4770 Haswell 3.4GHz LGA 1150 84W ... GIGABYTE GA-Z87X-UD3H LGA 1150 Intel Z87 HDMI S... MSI Gaming N770 TF 2GD5/OC GeForce GTX 770 2GB ... G.SKILL Trident X Series 16GB (2 x 8GB) 240-Pin... 
Hard DriveCoolingPowerCase
SAMSUNG 840 Pro Series MZ-7PD128BW 2.5" 128GB ...  CORSAIR Hydro Series H100i Water Cooler  CORSAIR GS800 800W ATX12V v2.3 SLI Ready Cross...  Corsair Obsidian Series 800D CC800DW Black Alu... 
  hide details  
Reply
post #6 of 27
Time for sticky! biggrin.gif
 
Terrorbyte V2
(17 items)
 
Le Papa's
(10 items)
 
CPUMotherboardGraphicsRAM
i7-4790 Asrock Z97 Extreme6 MSI GTX 660 Ti PE OC 32GB Kingston HyperX Beast 2400MHz 
Hard DriveHard DriveHard DriveHard Drive
Samsung 850 Pro Samsung 840 EVO  Micron M600 Micron M600 
Hard DriveHard DriveCoolingOS
WD Blue WD10EZEX Toshiba DT01ACA300 Cooler Master T4 Windows 8.1 Pro 64-Bit 
PowerCase
bequiet! Dark Power Pro 10 850W Thermaltake Urban T81 
CPUCPUMotherboardGraphics
Intel Xeon L5520 Intel Xeon L5520 Dell  ASPEED 
RAMHard DriveHard DriveHard Drive
Nanya 72GB 1066MHz ECC Registered Kingston V300 SanDisk Extreme II WD Red 
Hard DriveHard DriveHard DriveHard Drive
Samung Spinpoint F4 Hitachi Deskstar 7K3000 Samsung Spinpoint F3  Seagate 7200.12 
OSPowerCaseOther
Windows Server 2012 Datacenter Dell C1100 PSU and Corsair 650TX  Dell C1100 Chassis and Norco RPC 4224 LSI 9261-8i 
Other
Intel RES2CV240 
CPUMotherboardRAMHard Drive
A8 5600K BIOSTAR Hi-Fi A85W G.Skill Ripjaws X  Crucial M4 
Optical DriveOSMonitorMonitor
Asus DVD Burner Microsoft Windows 7 Professional  ASUS VE276Q HPw1907 
PowerCase
Antec Neo Eco 520 HAF 912 
  hide details  
Reply
 
Terrorbyte V2
(17 items)
 
Le Papa's
(10 items)
 
CPUMotherboardGraphicsRAM
i7-4790 Asrock Z97 Extreme6 MSI GTX 660 Ti PE OC 32GB Kingston HyperX Beast 2400MHz 
Hard DriveHard DriveHard DriveHard Drive
Samsung 850 Pro Samsung 840 EVO  Micron M600 Micron M600 
Hard DriveHard DriveCoolingOS
WD Blue WD10EZEX Toshiba DT01ACA300 Cooler Master T4 Windows 8.1 Pro 64-Bit 
PowerCase
bequiet! Dark Power Pro 10 850W Thermaltake Urban T81 
CPUCPUMotherboardGraphics
Intel Xeon L5520 Intel Xeon L5520 Dell  ASPEED 
RAMHard DriveHard DriveHard Drive
Nanya 72GB 1066MHz ECC Registered Kingston V300 SanDisk Extreme II WD Red 
Hard DriveHard DriveHard DriveHard Drive
Samung Spinpoint F4 Hitachi Deskstar 7K3000 Samsung Spinpoint F3  Seagate 7200.12 
OSPowerCaseOther
Windows Server 2012 Datacenter Dell C1100 PSU and Corsair 650TX  Dell C1100 Chassis and Norco RPC 4224 LSI 9261-8i 
Other
Intel RES2CV240 
CPUMotherboardRAMHard Drive
A8 5600K BIOSTAR Hi-Fi A85W G.Skill Ripjaws X  Crucial M4 
Optical DriveOSMonitorMonitor
Asus DVD Burner Microsoft Windows 7 Professional  ASUS VE276Q HPw1907 
PowerCase
Antec Neo Eco 520 HAF 912 
  hide details  
Reply
post #7 of 27
Thread Starter 
tongue.gif

Thanks to those who have given me rep for posting this.
Desktop
(18 items)
 
   
CPUMotherboardGraphicsRAM
i7-2600K Asus P8P67 Pro Asus Radeon HD 5850 Corsair Vengeance 8GB DDR3 
Hard DriveCoolingOSMonitor
Samsung Spinpoint F3 1TB Corsair H70 Windows 7 Professional x64 Acer AL2216Wbd 22" 
MonitorMonitorKeyboardPower
Acer V223Wbd 22" Acer V223Wbd 22" Das Ultimate Blank Corsair CMPSU-750TX v2 
CaseMouseAudioOther
LIAN LI Lancool PC-K56 Razer Lachesis X-Fi Titanium Fata1ity Professional Logitech z-5500 
CPUMotherboardGraphicsRAM
Intel Core i7-4770 Haswell 3.4GHz LGA 1150 84W ... GIGABYTE GA-Z87X-UD3H LGA 1150 Intel Z87 HDMI S... MSI Gaming N770 TF 2GD5/OC GeForce GTX 770 2GB ... G.SKILL Trident X Series 16GB (2 x 8GB) 240-Pin... 
Hard DriveCoolingPowerCase
SAMSUNG 840 Pro Series MZ-7PD128BW 2.5" 128GB ...  CORSAIR Hydro Series H100i Water Cooler  CORSAIR GS800 800W ATX12V v2.3 SLI Ready Cross...  Corsair Obsidian Series 800D CC800DW Black Alu... 
  hide details  
Reply
Desktop
(18 items)
 
   
CPUMotherboardGraphicsRAM
i7-2600K Asus P8P67 Pro Asus Radeon HD 5850 Corsair Vengeance 8GB DDR3 
Hard DriveCoolingOSMonitor
Samsung Spinpoint F3 1TB Corsair H70 Windows 7 Professional x64 Acer AL2216Wbd 22" 
MonitorMonitorKeyboardPower
Acer V223Wbd 22" Acer V223Wbd 22" Das Ultimate Blank Corsair CMPSU-750TX v2 
CaseMouseAudioOther
LIAN LI Lancool PC-K56 Razer Lachesis X-Fi Titanium Fata1ity Professional Logitech z-5500 
CPUMotherboardGraphicsRAM
Intel Core i7-4770 Haswell 3.4GHz LGA 1150 84W ... GIGABYTE GA-Z87X-UD3H LGA 1150 Intel Z87 HDMI S... MSI Gaming N770 TF 2GD5/OC GeForce GTX 770 2GB ... G.SKILL Trident X Series 16GB (2 x 8GB) 240-Pin... 
Hard DriveCoolingPowerCase
SAMSUNG 840 Pro Series MZ-7PD128BW 2.5" 128GB ...  CORSAIR Hydro Series H100i Water Cooler  CORSAIR GS800 800W ATX12V v2.3 SLI Ready Cross...  Corsair Obsidian Series 800D CC800DW Black Alu... 
  hide details  
Reply
post #8 of 27
Thread Starter 
Bump smile.gif
Desktop
(18 items)
 
   
CPUMotherboardGraphicsRAM
i7-2600K Asus P8P67 Pro Asus Radeon HD 5850 Corsair Vengeance 8GB DDR3 
Hard DriveCoolingOSMonitor
Samsung Spinpoint F3 1TB Corsair H70 Windows 7 Professional x64 Acer AL2216Wbd 22" 
MonitorMonitorKeyboardPower
Acer V223Wbd 22" Acer V223Wbd 22" Das Ultimate Blank Corsair CMPSU-750TX v2 
CaseMouseAudioOther
LIAN LI Lancool PC-K56 Razer Lachesis X-Fi Titanium Fata1ity Professional Logitech z-5500 
CPUMotherboardGraphicsRAM
Intel Core i7-4770 Haswell 3.4GHz LGA 1150 84W ... GIGABYTE GA-Z87X-UD3H LGA 1150 Intel Z87 HDMI S... MSI Gaming N770 TF 2GD5/OC GeForce GTX 770 2GB ... G.SKILL Trident X Series 16GB (2 x 8GB) 240-Pin... 
Hard DriveCoolingPowerCase
SAMSUNG 840 Pro Series MZ-7PD128BW 2.5" 128GB ...  CORSAIR Hydro Series H100i Water Cooler  CORSAIR GS800 800W ATX12V v2.3 SLI Ready Cross...  Corsair Obsidian Series 800D CC800DW Black Alu... 
  hide details  
Reply
Desktop
(18 items)
 
   
CPUMotherboardGraphicsRAM
i7-2600K Asus P8P67 Pro Asus Radeon HD 5850 Corsair Vengeance 8GB DDR3 
Hard DriveCoolingOSMonitor
Samsung Spinpoint F3 1TB Corsair H70 Windows 7 Professional x64 Acer AL2216Wbd 22" 
MonitorMonitorKeyboardPower
Acer V223Wbd 22" Acer V223Wbd 22" Das Ultimate Blank Corsair CMPSU-750TX v2 
CaseMouseAudioOther
LIAN LI Lancool PC-K56 Razer Lachesis X-Fi Titanium Fata1ity Professional Logitech z-5500 
CPUMotherboardGraphicsRAM
Intel Core i7-4770 Haswell 3.4GHz LGA 1150 84W ... GIGABYTE GA-Z87X-UD3H LGA 1150 Intel Z87 HDMI S... MSI Gaming N770 TF 2GD5/OC GeForce GTX 770 2GB ... G.SKILL Trident X Series 16GB (2 x 8GB) 240-Pin... 
Hard DriveCoolingPowerCase
SAMSUNG 840 Pro Series MZ-7PD128BW 2.5" 128GB ...  CORSAIR Hydro Series H100i Water Cooler  CORSAIR GS800 800W ATX12V v2.3 SLI Ready Cross...  Corsair Obsidian Series 800D CC800DW Black Alu... 
  hide details  
Reply
post #9 of 27
Stickied. smile.gif


Good work on this. thumb.gif
MacBook Pro 13"
(6 items)
 
 
Desktop
(13 items)
 
CPUGraphicsRAMHard Drive
Intel i5 3210 @ 2.5 GHz Intel HD4000 4 GB DDR3 @ 1600 MHz 500 GB @ 5400 RPM 
OSMonitor
OSX Mountain Lion 13.3" @ 1280 x 800 
CPUGraphicsRAMHard Drive
Intel i5 480m@2.67GHz AMD Radeon Mobility 5650 4GB DDR3 500GB 
OSMonitor
Windows 7 64bit HP 15.6" 1366x768 
CPUMotherboardGraphicsRAM
E7500 Intel...:( MSI GTS250 1GB 2GB 
Hard DriveOSMonitorPower
250GB Windows XP 17" LG CRT 1280x768@85hz 400W 
  hide details  
Reply
MacBook Pro 13"
(6 items)
 
 
Desktop
(13 items)
 
CPUGraphicsRAMHard Drive
Intel i5 3210 @ 2.5 GHz Intel HD4000 4 GB DDR3 @ 1600 MHz 500 GB @ 5400 RPM 
OSMonitor
OSX Mountain Lion 13.3" @ 1280 x 800 
CPUGraphicsRAMHard Drive
Intel i5 480m@2.67GHz AMD Radeon Mobility 5650 4GB DDR3 500GB 
OSMonitor
Windows 7 64bit HP 15.6" 1366x768 
CPUMotherboardGraphicsRAM
E7500 Intel...:( MSI GTS250 1GB 2GB 
Hard DriveOSMonitorPower
250GB Windows XP 17" LG CRT 1280x768@85hz 400W 
  hide details  
Reply
post #10 of 27
Thread Starter 
Quote:
Originally Posted by {Unregistered} View Post

Stickied. smile.gif
Good work on this. thumb.gif

Thank you so much! Since this is stickied, I will further add to it relatively soon.

smile.gif
Desktop
(18 items)
 
   
CPUMotherboardGraphicsRAM
i7-2600K Asus P8P67 Pro Asus Radeon HD 5850 Corsair Vengeance 8GB DDR3 
Hard DriveCoolingOSMonitor
Samsung Spinpoint F3 1TB Corsair H70 Windows 7 Professional x64 Acer AL2216Wbd 22" 
MonitorMonitorKeyboardPower
Acer V223Wbd 22" Acer V223Wbd 22" Das Ultimate Blank Corsair CMPSU-750TX v2 
CaseMouseAudioOther
LIAN LI Lancool PC-K56 Razer Lachesis X-Fi Titanium Fata1ity Professional Logitech z-5500 
CPUMotherboardGraphicsRAM
Intel Core i7-4770 Haswell 3.4GHz LGA 1150 84W ... GIGABYTE GA-Z87X-UD3H LGA 1150 Intel Z87 HDMI S... MSI Gaming N770 TF 2GD5/OC GeForce GTX 770 2GB ... G.SKILL Trident X Series 16GB (2 x 8GB) 240-Pin... 
Hard DriveCoolingPowerCase
SAMSUNG 840 Pro Series MZ-7PD128BW 2.5" 128GB ...  CORSAIR Hydro Series H100i Water Cooler  CORSAIR GS800 800W ATX12V v2.3 SLI Ready Cross...  Corsair Obsidian Series 800D CC800DW Black Alu... 
  hide details  
Reply
Desktop
(18 items)
 
   
CPUMotherboardGraphicsRAM
i7-2600K Asus P8P67 Pro Asus Radeon HD 5850 Corsair Vengeance 8GB DDR3 
Hard DriveCoolingOSMonitor
Samsung Spinpoint F3 1TB Corsair H70 Windows 7 Professional x64 Acer AL2216Wbd 22" 
MonitorMonitorKeyboardPower
Acer V223Wbd 22" Acer V223Wbd 22" Das Ultimate Blank Corsair CMPSU-750TX v2 
CaseMouseAudioOther
LIAN LI Lancool PC-K56 Razer Lachesis X-Fi Titanium Fata1ity Professional Logitech z-5500 
CPUMotherboardGraphicsRAM
Intel Core i7-4770 Haswell 3.4GHz LGA 1150 84W ... GIGABYTE GA-Z87X-UD3H LGA 1150 Intel Z87 HDMI S... MSI Gaming N770 TF 2GD5/OC GeForce GTX 770 2GB ... G.SKILL Trident X Series 16GB (2 x 8GB) 240-Pin... 
Hard DriveCoolingPowerCase
SAMSUNG 840 Pro Series MZ-7PD128BW 2.5" 128GB ...  CORSAIR Hydro Series H100i Water Cooler  CORSAIR GS800 800W ATX12V v2.3 SLI Ready Cross...  Corsair Obsidian Series 800D CC800DW Black Alu... 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Crash Analysis and Debugging
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Crash Analysis and Debugging › Beginner BSOD Crash Dump Analysis and Debugging Guide