Just wondering re this program

[ICIT2LOL]

Having a look at some Googles tonight I came across this site and was wondering if it is of any use as my progress in reading the dump files is really very slow and maybe this will help>
Blue screen of death (STOP error) information in dump files.

 

[ICIT2LOL]

Anyone??

 

[Hexagon12]

Well, I use BlueScreenView to simply manage and view the partitially details about the BSOD.
I rather prefer you to use WinDbg.
It says all the information about the BSOD. But it's sometimes annoying that it says Unknown_Image (ANALYSIS_INCONCLUSIVE). Then you can write about all the hardware tests like MemTest86+ or the hard disks checks like SeaTools for DOS for Seagate hard drives. You can also delete the information about antiviruses, unless the antivirus did the BSOD.

 

[ICIT2LOL]

Ok mate I was just wondering as I use the WinDBG but I just don't see the really obvious stuff that the others do, I was rather hoping this method would be a little plainer. Never mind I was just curious and thanks for your input.

 

[Hexagon12]

1. Open the .dmp file with WinDBG
2. Find , what was the causer of the BSOD,
3. Go to this page http://www.carrona.org/dvrref.php and find the driver. It shows what the driver was.

 

[ICIT2LOL]

1. Open the .dmp file with WinDBG
2. Find , what was the causer of the BSOD,
3. Go to this page Driver Reference Table (DRT) and find the driver. It shows what the driver was.

Thanks Hexagon I do that as matter of fact it - it is more what I am looking at that is my problem. I go to that analyse in blue and it gives me a heap of stuff to sort through and if it is not blatantly obvious it leaves me scratching around for the problem. Yet give it to one of you folks and the problem is picked just like that is seems to me. But I shall keep on trying all the same and ok I shall use that link too

 

[Callender]

Crash Dump Analysis

Hi, I'm not great at Crash Dump analysis either but I'm more used to looking at Explorer crash dumps rather than BSOD crash dumps.

There are some ideas posted on GEGeek (Geeks Toolbox link in signature) that might possibly help.

If you visit the site and navigate to Articles By GEGeek > 2013 > Debugging with WinDbg there's a reasonable amount of information available.

View attachment 339007

Also see an example of Explorer crash dump analysis:

Process ID: When explorer.exe, D:\oesn't play along

Sometimes this online tool pinpoints the problem straight away:

Instant Online Crash Analysis

 

[ICIT2LOL]

Sorry late reply Callender looks good might give it a burl as soon as I can