Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
ionbasa

BSOD Posting Instructions - Please Read!

Recommended Posts

If my desktop just crashed all of a sudden whilst playing game. And unable to boot up even with USB bootable windows, how should I generate the dump of BSOD informations? :/ 

Link to post
Share on other sites
Posted · Original PosterOP
23 hours ago, WeeHong said:

If my desktop just crashed all of a sudden whilst playing game. And unable to boot up even with USB bootable windows, how should I generate the dump of BSOD informations? :/ 

You may have bigger issues than looking at the dump files. If your PC can't boot there's a hardware error going on. FIrst read through the suggestions here:

 

At the very least you need to boot off a USB flash drive or plug the hdd in another computer to recover the files. 


▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to post
Share on other sites

hello i want to make a BSOD report but my crash dump files can't be archived winrar shows an access denied dialogue when trying to compress them.

Link to post
Share on other sites
Posted · Original PosterOP
On 3/21/2019 at 11:43 AM, MrFixitBlankFace said:

How large is the Sysnative tool app?

166.46 KB according to Sysnative.

 

On 3/21/2019 at 11:43 AM, MrFixitBlankFace said:

What if my PC does not have enough space? 

That is probably causing your BSODs. /s All joking aside, if you are seriously out of space, then that is outside the scope of this thread... Upgrade to a bigger storage device (HDD/SSD) or remove unneeded files with the built in Disk Cleanup Utility.

 

If this question has another implied meaning that you do not want to use the Sysnative app due to concerns, then you can follow method B in my OP which outlines manually copying the dump files by yourself without the use of the app.

 

On 3/21/2019 at 11:43 AM, MrFixitBlankFace said:

What if the BSOD is a driver problem?

That is actually expected, most BSODs are caused by 3rd party drivers (not developed my Microsoft) ie: AMD, Intel, Qualcomm, Relatek, Nvidia, etc.

 

On 3/21/2019 at 11:43 AM, MrFixitBlankFace said:

Will Sysnatve tell me that?

The app will not tell you whats causing the BSOD. It collects the DUMP file created during a BSOD plus additional system info related to the BSOD and packages it into a .zip You then upload the zip file in your own forum post here, or elsewhere, and someone who knows how to use the Microsoft Debugging Tools for Windows (WinDbg) will load the DUMP file and look data as to pipoint the reason why the BSOD occurred. WinDbg is specialized software that can interpret the information collected during a BSOD.

 

If you are curious as to see what someone like myself would see when we look at these files and spinets of data from the Kernel, drivers, memory, etc, it would like like this:

18697d1431201493-windbg-basics-debugging

 

18697d1431201493-windbg-basics-debugging

 

Images taken from TenForums because I cant locate my post detailing how to use WinDBG here on LTT.


▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


×