What is Reddit's opinion of
WhoCrashed?
From 3.5 billion Reddit comments
➔ WhoCrashed website
By popularity on Reddit, this Service is:
100 reviews of this app found across Reddit:
My mom knows how to send me a Minidump report generated when a BSOD occurs.
edit: for anyone interesed, I installed WhoCrashed on her computer. She runs the analysis and sends me the report.
True that. I use WhoCrashed to find out what did what, and it's actually been helpful for debugging.
For example, i learned that Malwarebytes was causing my BSOD on win 10 that was so annoying. Damn real time protection.
What is up with these responses. Jesus people dont come to tech support and post shit if you dont know anything about tech support.
IRQ errors many times mean that there is an issue with your hardware or a driver.
A good utility would be http://www.resplendence.com/whocrashed
This can lead you to the driver that may be causing the issue. Update that driver.
Another thing you can do is test your RAM using this utility.
Which motherboard do you have? Often these are caused by the motherboard as well, you should look into updating the firmware, many times there are updates that increase system stability, this is very often the case with gamer motherboards.
sure but I mean maybe there is a specific driver causing the freeze. What you can do is disable autoreboot on error so that you maybe get an error (https://www.tenforums.com/tutorials/69012-enable-disable-bsod-automatic-restart-windows-10-a.html) and install http://www.resplendence.com/whocrashed
Run WhoCrashed which may tell you which driver is at fault. Google the filename it gives to determine what hardware device its for (a .sys file usually) and upgrade that driver, or if its a driver relating to a software product like an anti-malware suite then either uninstall it or upgrade it.
Run WhoCrashed every time after rebooting from a BSOD: http://www.resplendence.com/whocrashed
I have a good trick if you're not used to logs -
Install and run "analyse" with this; http://www.resplendence.com/whocrashed
If you post back the results we should have a good idea, but the summaries are usually pretty accurate for basic stuff.
Did you reinstall windows with this new hardware, or swap out hardware and install drivers for it?
If you did not reinstall windows: what did you upgrade from?
ALSO
Are you able to catch the stop error windows provides you on the bluescreen?
This program Whocrashed will be able to scan your minidumps and give the error, and rough diagnoses if what the issue might be.
If you are able to get the error/information from that program paste it here ^_^
Lass mal Whocrashed analysieren welche HW das Problem verursacht (wenn es ein Dumpfile gibt). Dann mal bei den entsprechenden Treibern nachhaken, evtl. ein BIOS-Update in Betracht ziehen wenn es kürzlich ein Treiberupdate gab.
Before we assume anything download WhoCrashed
http://www.resplendence.com/whocrashed
And share the info of the BSOD that it reveals. I'm about to get off for the night but if you do this and no else helps you in the mean time I'll swoop back in later and do my best.
Gonna need more information and I'll help you. What do you mean by crash? Everything locks up? BSOD? Restart? Diablo closes?
PC Specs? D3 settings?
First thing I would do honestly is download this program. Run it after a crash and it will tell you what it thinks the problem is. It won't be exact 100% of the time but it will give you a hint as to what happened before the crash.
did you check what caused the blue screen? try http://www.resplendence.com/whocrashed and analyze your mini dump files that get created when you have a blue screen and try to find out what caused the bluescreen. i once hat a bluescreen because of my keyboard driver - so it's not always apparent what causes it.
edit: when analyzing your minidump files, search for .dll files that caused the crash. e.g. dll files that start with nv.....dll are mostly nvidia graphic card related.
I would suggest you take the CPU back out and check all the pins again, it's likely that the force from the CPU when you inserted it after has straightened the pin out and should be back to normal.
If the pin is still bent, than straighten it again and be careful when you insert the CPU. Use a flat surface like the edge of a bank card to make sure the pin is in line with all the others in both directions.
If MW3 caused the PC to crash, then you could use who crashed to read the dump file and try to find the source of the problem. If the game just crashes itself, try a re-install/repair and also check drives (mainly GPU) are up-to date
Edit: This website has a good guide and advice on straightening pins. http://www.wikihow.com/Fix-Bent-Pins-on-a-CPU
Just be sure to take your time and don't bend pins back and forth. Think how much time it would take to earn the money to replace the CPU/motherboard, so spending 10 minutes in comparison to ensure the pins are bent back carefully isn't allot.
I had to bend a few back on my brothers CPU when replacing his heat sink not too long ago, I used the stock paste as I was out of after market paste when building, come time to remove it, it had set like concrete, had to apply allot of force to get it off as my 99% alcohol didn't help much. When it fell off, the CPU dropped on the carpet.
I've used this site to help figure out which tree to bark up.
Then there's Whocrashed which is a pretty neat little program that searches your computer for crash dump log files and presents them to you in a more intuitive format.
Couple of things. Unused memory is wasted memory. You don't have to worry about things using too much memory unless you physically run out of it and that causes the crash.
Second thing. What is the specific STOP code you get when the BSOD happens? In fact, just download WhoCrashed and see if that gives you any clue as to the source of the BSOD. There are a million and one reasons for a BSOD and it is impossible to diagnose without the STOP code, parameters, and any specific files referenced.
Use this on your BSOD crash dumps to figure out what crashed: http://www.resplendence.com/whocrashed
Update graphics card as other people have said.
You should also know that a lot of people complain about Fallout crashing. You're not alone. It tends to be a bit buggy. Make sure Fallout itself is up to date.
Uninstall the drivers completely (driver sweep if you have to), then reboot. Perform a clean installation after this. If this does not resolve the issue, I'd like to know what is creating that error. There is a program called WhoCrashed that can give you all of the information that you'll need to paste to me. You can get it here.
It sounds like you have a driver problem, download and run WhoCrashed: http://www.resplendence.com/whocrashed
It should tell you whats causing the BSOD and give you a solution to fix it. If you cant boot into windows, try booting into safe mode and running it from there.
Ensure everything is connected properly, re-seat the GPU.
You may want to give whocrashed a try. Unlikely there will be a dump file for a hardware-related crash, but if it is the GPU or some other peripheral component, it may show something.
http://www.resplendence.com/whocrashed
The local PC shop wont do anything except look at it, charge you some money, try to sell you stuff you dont need, and optionally steal your hard drive contents.
If you can get another GPU to test with, try switching it out. Alternatively, try another PCIe slot if applicable. The GPU PCB or the PCIe slot may have been bent or damaged during transit, if the card is particularly large or heavy.
Not too familiar with that error, I'd suggest downloading who crashed to get some insight:
http://www.resplendence.com/whocrashed
And see if you can solve it if not the guys over on http://www.tomshardware.com/forum/forum-129.html will probably be able to help
Try and download WhoCrashed. It does the same thing as BlueScreenView but provides a paragraph description of your what caused your computer to crash. Just click analyze and scroll down to view each crash log's simplified description. For me my computer crashes from ntoskrnl.exe and nvlddmkm.sys. I'll keep looking into this issue as well.
Alright, first of all calm down. Are you able to at-least boot into Windows for sometime before this occurs?
If so download whocrashed http://www.resplendence.com/whocrashed
It will point you in the direction of what is causing it. Post the results in a edit above but do reply to this comment when you do so, so I can see it if someone doesn't help you before me.
>Also, Yesterday my computer blue screened before i went to bed, i restarted it and its fine now, But how can i check why it blue screened etc?
You can download WhoCrashed: http://www.resplendence.com/whocrashed
Windows Memory Diagnostics is not a very good method to test your memory (it's like Windows Defender for viruses). I'd recommend running MemTest to test out your RAM. I'd also suggest using WhoCrashed to read your BSOD dump files in more detail. You'll be able to really narrow it down as to why you're crashing all the time.
Download whocrashed and it will provide more info.
http://www.resplendence.com/whocrashed
More than likely there's a software driver that isn't playing nice with your install, but this may or may not tell you which one that is.
Yeah, I had the same problem. Especially when I would wake my PC from sleep. It turned out to be a driver issue for me (NVIDIA and Wacom).
I used WhoCrashed (it's free) to find out what the issue was. It analyzes your crash log to give you a general idea of what's causing it.
Good luck!
Try downloading and installing Whocrashed. It will read the Windows logs and point you in the direction of possible causes. Almost always they are memory or driver issues.
I'm far less an expert than many people on this sub, but I just barely had my own struggle with a mysterious BSOD, so I've read a hell of a lot about it lately. In my case, it turned out to be a faulty DDR3. What sucks is I ran mem-test for like 5 passes and it didn't detect any problems, but then I switched out the memory module and my computer stopped crashing.
Other things to try: make damn sure that you really have installed all the drivers for the motherboard. Also, if you have tweaked the BIOS settings a lot, try going to the "exit" tab and see if you can restore defaults.
Make sure all the power cables are properly seated.
If the mystery BSOD continues to happen, consider that it could be a faulty PSU. This was not the case for me, but after reading around the internet a lot I have seen a lot of people attribute mysterious crashes to faulty PSUs. There are tools for testing PSU voltage available on Amazon for $20-30.
If you can get windows running, run command prompt as an administrator and type sfc /scannow. This will detect whether you are missing any important windows files.
This app was useful for me: http://www.resplendence.com/whocrashed
Again, I'm sure others know more than me, but I just barely had a long (totally pain in the ass) experience with it. Good luck!
Try installing Whocrashed. It will give you a fairly simplified version of what Windows logs are showing and hopefully make it clear what the issue might be. These are almost always memory or driver issues.
Definitely sounds like some sort of hardware issue (several even maybe), but even so whenever bluescreens are involved I would suggest running who crashed to get a bit more info on exactly what's going on.
These types of stability issues are often driver related. Have you downloaded and installed all the latest drivers from the motherboard manufacturers site?
Have you checked Windows Event Viewer to see if there are any warnings or error notifications for the exact time the PC reboots or shut downs?
Download and install Whocrashed to view Windows logs that might show what has been happening at the time of reboots or shut downs. Often they will point to memory failure or driver issues.
Sounds like either your CPU is overheating or you have some instability with your OS. I recommend HWMonitor to see your CPU temps. If they're getting higher than ~60C, reapply the thermal paste or find a way to fix your CPU cooling. If it's something else, try installing WhoCrashed and have your friend take a look at it.
Download WhoCrashed and it should tell you what caused it (if you have minidumps enabled).
I had the same problem and it turned out my sound card drivers needed to be updated.
use this to see if there is any minidump files created by drivers during the crashes http://www.resplendence.com/whocrashed Download this to monitor your temps and voltage to make sure you're not over heating or having power problems http://openhardwaremonitor.org/ Also make sure your cpu cores aren't parked http://www.youtube.com/watch?v=xrvDVZg6C58
Edit: You might wanna check your ram too using memtest just to be safe
Well as far as I know AMD does not auto update their drivers. If you haven't already go to the and site and follow there complete driver uninstall guide then download the latest AMD omega driver.
Do not skip the driver uninstall part.
Also please run http://www.resplendence.com/whocrashed and link the output or copy past it here so we can see exactly what is causing the crash
Easiest way for problem 1 would be to disable the on-board graphics via the BIOS. I hate doing that sort of thing rather than find the cause of the problem, but I might just about be able to force myself for something like this.
No idea for problem 2, but for problem 3 you should try something like whocrashed, might give you more info about th issue.
I can take a look at these dump files. In the meantime, you can download and install WhoCrashed to see if it is a hardware or software problem. Basically it analyzes the dump files and makes the info more easily understandable.
Download and install Whocrashed from here
This will point in the direction of whatever it is that's causing the crashes, and it's possible fixing the cause of the crash will cure your issue. I'd also take a good look at reinstalling all of the drivers for the PC including the motherboard chipset driver, audio, LAN, Wireless, etc etc, just to make sure you have the latest drivers and they are in good shape.
I also wonder if the hard drive might not be failing. If it's a hard drive you can use Western Digitals Lifeguard Diagnostics to see if there are any serious issues. Found here
If you're using an SSD, check the manufacturers website for diagnostic software.
Download, install and run Memtest on one stick at a time or what you think you have left that is operable. There is a link in the following webpage to the manual for Memtest also, so you have a better idea how to work with it.
I'd run Memtest for 1000% coverage, because going over the RAM once may not show any errors whereas going over it numerous times is more like to show errors if there are any problems with the RAM.
I'd also be inclined to download and install WhoCrashed to get a better read on the blues screens if you haven't already.
No, not all graphics issues crash to desktop. Could this be applicable to you?
Anyway, I recommend using WhoCrashed to see what's actually crashing your computer first.
It's quite possibly an outdated/corrupt driver. I normally download a utility like WhoCrashed, which reads the minidump file and tells you which driver failed, if it's possible to tell. Otherwise, you might need to test the hardware parts individually to see if any is failing.
Download WhoCrashed and post the report here.
http://www.resplendence.com/whocrashed
>If this was an issue of being a bad card, is it normal to not have any problems at all until 2 months later?
No I wouldn't say that is normal but it could be bad RAM on the video card that only shows up once a certain point has been reached. The card itself could be fine, but will still need to be replaced under this situation.
If you're getting reboots or crashing to a BSOD try running this and see what your logs tell you about the possible causes. Whocrashed is at:
http://www.resplendence.com/whocrashed
I'd be checking the hard drive also. run the full scan and not the quick test to check for bad sectors. WD Data Lifeguard Diagnostics.
http://support.wd.com/product/download.asp?groupid=613&sid=3&lang=en
File corruption to the system files due to faulty RAM or a failing hard drive can be checked by opening command prompt as administrator and running "sfc /scannow". This will try to repair them if possible and provide you a log of the issues found.
Whocrashed might tell you what is causing the BSOD. Otherwise, since you're likely under warranty if you can't deduce it yourself I'd take it in to get replaced.
If you're getting a BSOD in Borderlands 2 (or anything really) I would suggest using a utility like <http://www.resplendence.com/whocrashed>. You can guess all day long about whether it's your graphics card driver or your motherboard or whatever, but the fact is it could be anything. My last BSOD problem turned out to be RAID controller drivers.
Excellent with your cables. OP, I had a similar issue with my recent build. I used a Gigabyte motherboard and G.Skill RAM (though with an AMD Phenom X2 965). My PC would randomly crash and reboot. And by random, I mean after either five minutes or five hours or twenty five hours. There was no way to tell, since I never got BSODs.
For me, the problem was due to memory timing in the BIOS. The motherboard was set on AUTO (to autodetect memory timings) and still managed to incorrectly detect them. I researched my RAM online and manually input the timings. Then I saved/booted. Haven't had a crash since.
I did learn something during this harrowing 48 hour quest to figure out what was wrong: I suggest checking Event Viewer (just type it in the Start Menu) and go to Administrative Tasks--if in fact you can get to it (may require several boot attempts). There, look for the Critical (!) errors and see if you can't figure out what causes them. Other than that, check this site for a program called WhoCrashed. It will read the page file if your memory is set to dump during a crash.
I highly suggest that you run this : http://www.resplendence.com/whocrashed
Also - these guys are correct, it is more than likely a driver issue. The items that you have narrowed it down to.. That is not a very narrow view of the issue at all. It could be any one of these, or any driver / service associated with any piece of hardware in your system. I would not suggest taking your heat sink off, I would not suggest pulling your processor if you are not comfortable with this. Have you updated ALL of your drivers? When I say ALL, I MEAN EVERY DRIVER - and while you're at it flash your BIOS with the latest firmware for your motherboard.
Also, have you tried loading up safemode and recreating the issue? Have you reviewed your event viewer and looked for other errors around the same time the BSOD hits?
Run whocrashed and see if it can identify a driver in the crashes. If it is multiple, re-install the drivers for each device. With the problem carrying over from install to install, you may also consider getting a new disc for your windows image. Where did you obtain the windows copy to begin with? Is it a retail disc, restore image, etc.? This could also be a windows driver.. In your BSOD, I noticed that your description did not identify a specific file in the error message, though the message its self is different each time. Is there a file identified on screen when it happens?
Another few questions.. Have you updated windows 7 to the newest service pack? Do you have an on-board video card, if so, have you disabled it within the device manager (as you are not using it)? What antivirus are you using?
I apologize if I asked any questions that you have already answered, I've tried to review the previous posts and make sure I'm not hitting any of the same points. If you still need help send a reply and I'll help as best I can! Otherwise good luck!
Does it create any logs in the Event Viewer before rebooting? An easy way to check is to run WhoCrashed. This can help to narrow it down a lot.
Does it crash in Prime95 blend test? Let it run for a number of hours. If so then it's probably an unstable overclock. If not, try running Furmark, if that crashes it then try 1 video card at a time.
Powercool PSU? I'd be highly suspect of that being the issue if it just seems to be random. They aren't exactly the highest regarded PSUs.
Use this on your BSOD crash dumps to figure out what crashed: http://www.resplendence.com/whocrashed
Update graphics card as other people have said.
You should also know that a lot of people complain about Fallout crashing. You're not alone. It tends to be a bit buggy. Make sure Fallout itself is up to date.
Download and run WhoCrashed and let us know what it says is crashing (if anything).
http://www.resplendence.com/whocrashed
Basically this just analyzes any crash dumps.
EDIT
You can also try this: http://connect.microsoft.com/systemsweeper
It creates a bootable disk with Microsoft Security Essentials that you can use to run a scan.
I've been using WhoCrashed from Resplendant because it has a free trial and installs in seconds. Since I don't really need it on my own PC's I don't have to worry about the trial running out generally.
Try this.
​
If you have another PC or way to get to the internet.
Download and run - http://www.resplendence.com/whocrashed
It will pull your log files and present them in a form that hopefully which process is causing you the issue.
​
The it is google fu to try to resolve.
​
​
Do you get bsod ? cos that would mean you have dmp files that can be analyzes if its freezes thats a big pain in the ass to figure out, set performance plan to high performance for now and hard drive timeout to 0, anyway if you get bsod you most likely have dmp files crash logs these are good clues on what is going on whocrashed is a great tool to analyze that
Get WhoCrashed
Let it run, use your PC normally, then when it crashes, you can reboot and open WhoCrashed and it might give you some more information.
> BSOD
yep i have got that but i didnt have time to take a peek at the error code. is WhoCrashed this software http://www.resplendence.com/whocrashed ?
also when a crash happens normally what kind of damage should you expect? and what are some main causes apart from overheating.
Kernel Error 41 just means windows restarted and it doesn't know why. It doesn't point at PSU at all beyond fact PC is restarting, you can download and run who crashed(http://www.resplendence.com/whocrashed) - it will give us a glimpse of the errors you getting and might help us solve them
I'm not at all affiliated with this site or tool, but the only thing I've ever found (as an IT professional) that pinpoints the cause of a BSOD is a utility called WhoCrashed. Well worth keeping in your arsenal.
Windows 10 fully updated? WhoCrashed might be able to help you pin point the crash culprit http://www.resplendence.com/whocrashed
If your antivirus is really causing this you can add the hirez folder into the antivirus 'exceptions' list and it will leave that folder alone
Install WhoCrashed
This app analyzes your crashdump and tells you what caused the crash.
I was fighting a 2-3x a days BSOD after a major windows 10 update. In my case one of the app that i used caused the crash. https://i.imgur.com/hxAc0b7.png
Sounds like you’ve done the right things. If in doubt you can use a crash dump analyser like Whocrashed to get more details on what’s gone wrong. http://www.resplendence.com/whocrashed
Also remember odd things can cause BSODs. I thought my new A17R5 was borked but It turns out my BSOD was caused by my 6 month old external Hdd that I was using to restore data.
It also means that not everyone has the issues/problems that some experience.
You're having issues/problems? Fine tell us what they are and those of us that can help will help... That's what the forum is for after all.
It's not for automatically assuming and claiming that everyone using Windows 10 must have the issues/problems you're having, and/or that it means Windows 10/Microsoft are crap.
Some tips on running computers without issues...
When you have a problem with Windows 10, a Clean install is (most often) NOT the best/required solution.
The last time I did a clean install was to upgrade from Windows XP to Windows 7 fifteen+ years ago. Since then all my upgrades (W7 > W8 > W8.1 > W10) have been updated through WU or with the Media Creation tool using the option to keep my personal files...
Constantly updating drivers to the latest driver version is a very bad idea, especially when some (crap) third party driver update is telling you your current drivers are out of date. These programmes are worse than third party registry cleaners for effing up Windows...
This is from personal experience, when I religiously used to run a driver update programme weekly, then spent the next week undoing all the 'damage' the driver updates had caused.
If you must play around with drivers then download and use Who Crashed to find out what happened, and how to fix the problem, especially BSOD crashes...
http://www.resplendence.com/whocrashed
Backup every thing OFTEN
A restore from the latest backup will fix most problems.
Google is your friend when you do have problems.
Most often, the cause of the issues/problems you're having is PEBKAC
https://en.wikipedia.org/wiki/User_error
The easiest fix to PEBKAK problems is undo what you did...
My 02c...
WhoCrashed will read the file automatically. You can see about it here: http://www.resplendence.com/whocrashed. As for windbg I would recommend to avoid this and use whocrashed.
As for memtest86 you can read on it here: https://www.memtest86.com/technical.htm
Good luck, check your hardware drivers to and make sure the BIOS is up to date. Other than that set Windows to save the MEMORY.DMP files. You can use whocrashed I believe is free for home users, it will analyze the memory dumps.
EDIT: Still free for home use, http://www.resplendence.com/whocrashed
Windows is ALWAYS recording errors...most don't matter. You would actually have to list them to get a diagnosis, but the bigger issue are the crashes.
Most crashes occur due to driver issues.
Might want to download and install
When you get it all working again, get WhoCrashed. http://www.resplendence.com/whocrashed
This will tell you which driver caused any blue screens you get, and usually points you in the right direction to fix the problem...
I've used it for years, and it hasn't failed me yet.
Ok grabbing at straws, but my ideas in order:
- See if http://www.resplendence.com/whocrashed can tell you what is crashing.
- It could be heat related we will want to look at your temps.
- Could be your ram we will want to test that
Have you been into Event Viewer to see if anything is throwing an alert?
right click my computer/manage/event viewer (in the left pane)
While there also go into Device Manager and see if you have any exclamation marks etc by any of your hardware which likely indicates a driver issue.
Whocrashed might also help shed some light on things.
In my own experiences smite would make my pc run hot and cause blue screens.
Try this program out, http://www.resplendence.com/whocrashed
WhoCrashedMe will pinpoint what caused your crash. Feel free to post the text or pm it to me when you run it. It should be able to read your crash logs already present. If not make your game crash again so you have a crashdump file for it to work with.
What kind of storage devices are you using in these machines? Windows 7 can get dicey on SSDs and NVME drives without the appropriate hotfixes. Works fine for a while, then blue screens for no apparent reason.
Disable auto-reboot on blue-screens so you can get a better idea of what's causing the crashes. If windows is producing dump files you can analyze them with a utility like whocrashed or Wincrash report
Might want to try this: http://www.resplendence.com/whocrashed
Have you had this issue with games other than WoW? If not then uninstall WOW and reintall, make sure to clear out all addons and slowly add them back. Might want to try disabling shadowplay if thats turned on.
You could also try an older driver from nvidia like 2 or 3 versions back. Make sure you have the latest Intel Management Engine Interface drivers, and IST Drivers.
Who Crashed might be able to point you in the right direction. Usually this type of behaviour is driver related.
If it turns out the drivers are corrupted, then you may have data errors and this could be the result of failing C: drive or RAM that's throwing errors and corrupting data...but start with the easy stuff first Who Crashed and look at replacing your old motherboard and graphics drivers. Not with Windows updates replacements but with drivers from the motherboard and graphics card makers website or the website support pages for your factory built PC or laptop.
Schau dir mal über die Computerverwaltung die System-Ereignisanzeige an, da sollte etwas zu finden sein zum Zeitpunkt des Absturzes.
Ein Tool wie WhoCrashed kann dir auch die wesentlichen Informationen gleich schön aufhübschen.
http://www.resplendence.com/whocrashed
> Latest version: WhoCrashed v 5.54
> WhoCrashed reveals the drivers responsible for crashing your computer
> Whenever a computer running Windows suddenly reboots without displaying any notice or blue or black screen of death, the first thing that is often thought about is a hardware failure. In reality, most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, most computers running Windows do not show a blue or black screen unless they are configured to do so. Instead these systems suddenly reboot without any notice.
After running this app I realized no Drivers were responsible and I had to perform additional Tests:
> Based on the well-known original memtest86 written by Chris Brady, memtest86+ is a port by some members of the x86-secret team, now working at www.canardpc.com. Our goal is to provide an up-to-date and completly reliable version of this software tool aimed at memory failures detection.
After running the MemTest86 I realized one of my RAM is faulty and I exchanged my RAM bricks under lifetime warranty with Corsair.
> critical Kernel-Power ID:41 Task: (63)
This is quit a generic message, as the cause can vary a lot from a computer to another. In the detailed view you should have the bugcheckcode and 4 parameters bugcheckcodeparameterX.
First off, even if your computer restart without showing the bugcode, you can check if you have something in the mini-dumps that should be generated each time a process crash.
Esier way is to run this :
http://www.resplendence.com/whocrashed
The thing is that the error message may not point directly at the root problem. So in the event log, just look for the past few days which event are marked with a red flag. Those are the critical events.
That may point out where you should focus on.
Run the dxdiag tool, let it finish loading the go through all the tabs and see if any errors are reported.
edit: Download and run who crashed, then see what it finds as the program that crashed.
take a look at this, try the easiest first ( bios update - cleaning the pc - video card update )
also, you can download whocrashed http://www.resplendence.com/whocrashed , it will give a little more info.
keep me updated!
Possible. If you have a minidump you can find out.
Whocrashed might be easier for this job ;) http://www.resplendence.com/whocrashed
With some luck it will point straight at the offending driver
You need to provide more information;
When it 'crashes' does it hang?, freeze?, blue screen?, restart? glitch? please define what you mean.
Is there a pattern to the crashes? - something you can do that will make it crash each time? - or are they random?
Do you have any error code?
Everyone has given these points but I would do them in this order: * Run whocrashed by Resplendence. It's incredibly useful. Most likely it will point you to the network adapter. If so, figure out how to sort out the driver for it, or better yet completely replace it. * Otherwise, run Memtest with one stick at a time. Most likely 1 of your sticks will be faulty.
Good luck!
Try a different driver version, while making sure that windows doen't automatically update your drivers again. If that doesn't work, pull the card and see if you get the same proplem (with the funky text) with integrated graphics. Are your crashes throwing codes? If they are, what is it? WhoCrashed isn't 100% perfect but if it can identify the error it may help point you in the right direction.
So typically all that stuff means you've got a driver that's causing crap somewhere in the mix.
Ok first open command prompt as an admin and run this command.
sfc /scannow /offbootdir=c:\ /offwindir=c:\windows
Note there's a good chance it might find errors but not be able to fix them. Don't worry about it.
Next download who crashed here http://www.resplendence.com/download/whocrashedSetup.exe
Directions for it here. http://www.resplendence.com/whocrashed, but what should happen is it will generate a crash report in that crash report there should be a file path that indicates what file has crashed or you can post a screenshot and I'll look at it.
That sounds like my problem. I say BSOD, but the screens were off at the time :)
If it was a BSOD in the background, then a dump file will have been created. You can view it with this program and it will tell you why it rebooted. I was getting TDR errors caused by nvidia drivers.
I would say run http://www.resplendence.com/whocrashed 1st and see what it brings back for your BSOD at the very least.
Being lazy I would prb just download all the drivers I would need (wifi,mouse,gpu, ect) from MSI (and who ever provides the drivers for your GPU),
download the win10 iso (https://www.microsoft.com/en-us/software-download/windows10/)
Post what whocrashed says could be the issue 1st
Run WhoCrashed to analyze the crash dump generated by Windows from the most recent blue screen, and it will tell you what failed. Usually it's a driver issue. If it's in a game, I would bet it's a graphics card driver incompatibility. If you recently updated the driver, try installing the previous version instead and see if it still crashes.
Whocrashed that will be able to analyze the bsod , take it from there, possibly the av , what is it ? > FAILURE_ID_HASH_STRING: km:av_nt!kxwaitforlockownership
Try reinstalling your video drivers. Also check the event log to find the error. Could help you troubleshoot the issue. Also, check out Whocrashed: http://www.resplendence.com/whocrashed
It will go though the crash dump files, and give suggestions on how to resolve the problem. Good luck!
The black screen can be many things. Before going all crazy replacing everything, check to see if it is a software issue. Download Display Driver Uninstaller follow directions to start in safe mode to delete old drivers and re-install clean drivers.
Can download Whocrashed on the chance a dump is being written, and it will tell you what is making it crash to narrow it down.
If the computer will not even boot with the one stick of RAM (but will with the other) it's the RAM.
To check your dump files, run this program: http://www.resplendence.com/whocrashed - that will point you in the right direction on blue screens.
Could be anything, you need to check your crash dump, have a look in Event Viewer or run Whocrashed, it should give you a basic idea of what caused the error.
There are no perfect antiviruses that stop everything, programs like Malware Bytes, Spybot, ADWCleaner and ComboFix (pre Win8) are very good at detecting viruses that slipped through.
You can use WhoCrashed to analyze any BSODs that have happened on your computer for the cause, but again, it may just be a one-off sort of thing.
Also, like retrocomputix was saying, it could be heat related, try taking the side panel off your computer (while its tuned off) and look to see if there is much dust in there.
If you want to save yourself some frustration, friend, I'd recommend reinstalling your OS. If not and you feel like in the problem solving mood, there are a few things we can do. Let's get started:
First, we'll want to deal with why your disk usage is so high all the time. There's a few things we can do to fix that:
Run Disk Cleanup to clean up unwanted files on your harddrive. Also go through your Programs list in Control Panel and uninstall any Programs you don't use any more.
Ccleaner is another godsend in cleaning up your computer very well. Download it and use it! It's free, too!
Hit Windows Key + R and type in 'msconfig' (without quotes) in the box and hit Ok. Go through the Services and Startup tabs and uncheck Programs that you don't use or look sketchy to you. (In the Services tab, to make things easier, just check the 'Hide all Microsoft services' box. Also, if you're unsure what qualifies as sketchy or if you're not sure, just Google it.) This will speed up your computer immensely.
Hit Windows Key + R again and type in '%TEMP%' (without the quotes) and delete everything in the windows that pops up.
Do the same thing above (Windows Key + R) but this time type in 'prefetch' (without quotes) instead. Delete everything.
After all's said and done, run Disk Defragmenter and let it do its' thing. I guarantee you'll see a difference. Also, if none of these things fixes your 100% disk use problem, open up Task Manager and see what's eating your disk usage.
Now, after that's fixed, we can find out why you're crashing. Download this tool. It's VERY useful in finding the reason why a computer keeps crashing:
Get back to me if you still have problems, man.
Try downloading and using this program to find out why she crashed:
If you can, take a screenshot when you have the program open and I can help you from there.
We'd like to help, but at the same time you have to help us as well by providing more information.
When does it occur? In the middle of a game? In the middle of a video? When the computer is just idling?
Your system specs?
Download WhoCrashed here and run the analysis and copy paste it here if thats okay. If not at least take a screenshot.
Next time it bluescreens, take note of the STOP code. It should look like 0x00000** (where the *s vary). This error code will be the most useful in identifying the problem.
As for now, download and run WhoCrashed. It will analyze your crashdumps and hopefully point to a culprit.
This is a page from Microsoft dealing with this Stop code.
Looks like a fairly typical blue screen situation. Try downloading and installing Whocrashed to view the log file on this. Usually this is memory issues or more likely driver related...Whocrashed may point out which.
That sounds about right. I'm happy to look at it myself, but there is an application called WhoCrashed -- free for home use -- that will tell you the likely culprit. It analyzes the dumpfile, so you don't have to. I'm very curious what it would tell you.
edited for link: http://www.resplendence.com/whocrashed
There is an application called "who crashed". Im not sure if it has support for Win10 yet, but it worked miracles in Win7 for me.
Just go about your day, catch the BSOD, restart, and open up the application. Hope that helps!
So you've downloaded ad installed all of the drivers from HPs website for the Elitebook? Just checking. :)
You can install Whocrashed and see what your Windows log files have to say by running this.
Nine times out of ten it's driver related, hence my first question.
If you haven't had a different BSOD since that one, there should still be a memory dump on your machine from that crash. An awesome (and free for personal use) program for this is WhoCrashed, which will analyze the dump file that was created at the time of the BSOD and tell you exactly what program, service, or driver caused the crash. From there you can focus your troubleshooting more accurately.
The dump file it's reading is called MEMORY.DMP and is found in C:\Windows.
Try downloading WhoCrashed and upload the results of your crash dump here. I'm about to sign off for the night but when you get those I'll try to get it figured out.