New
#10
Well done, But I don have the guts to play with something like this!
Well done, But I don have the guts to play with something like this!
Ok Colin as it says earlier about that cache it is slow but am getting the hang of using it and am only still seeing very obvious faults / whatever - now I just need to know is what some of the terms used are and how to post the stuff I find in those blue hued windows you blokes can.
Now one last thing when I hit the dump file the WBG grey window opens very low down on the left hand side of my screen and dump opens in the centre of it. So is there some way I can get it to open centrally?? I only ask to save having to drag and drop the grey screen so that I see the whole window.
Colin, would adding the file association of NFO files to MSINFO32 be a good idea to put in the tutorial or not?
Thanks for writing this tutorial, WinDBG works as expected.
Also just to let you know, recent bluescreenview from Nirsoft will also accept external Dumps:
Blue screen of death (STOP error) information in dump files.
This allows people to quickly analyze dumps if they cannot install Dotnet 4.5.2 (unlikely) or WinDBG.
Have a nice day ^^.
Ok Golden I have just reinstalled my OS (and added WinDBG as before) and the reason for the install was my hard drive became full and in the process of trying to clear it I wrecked the OS.
Now clearly I should not have let it get that full and I am wondering because I used this feature quite a bit on top of my other programs etc if any of the material to be looked at gets saved in any form .
If it does then I am going to have to know if anything does get banked up like say restore points and before the drive gets anywhere near full make sure data is erased, as I am not fond of reinstalling and the time it takes.
But I must say installing WinDBG this time seems to work better in that it opens mid screen for a change.
John, if you select open on the dump files it is in the temp file and is not supposed to save anything. I don't believe it does unless you save the dump to your hard drive. Just select open and it will not save it. Or, at least it is not supposed to.
Unfortunately, BlueScreenView and other BSOD applications very rarely pinpoint the true cause of BSOD's, often assigning the blame to the process that happened to be running at the time of the crash.
The only tool that allows you to dig down deeply into the system and isolate the true cause of BSOD's is WinDBG.
Thanks for the tutorial. Followed it exactly and everything seems to be in working order. :)