Windows 7 Analyze BSOD with windbg

[mramirm]

Hi Guys,

my pc was always got a blue screen after a period of time and it drove me crazy, after searching with google to find a solution, i found a guide that tells you how to know exacly why you get a blue screen, in my case it was bluetooth driver.

Link Removed - Invalid URL


hope it will help you aswell.

 

[TorrentG]

Hey, welcome.

In 95% of cases, it doesn't clearly show what the issue is. You have to know what's what from lots of experience and previous knowledge, or why certain software does certain things.

You were lucky that yours didn't fall into that category. Enjoy, and good job.

(That page was only created today....are you sure you aren't making up any stories here? Hrrrrrmmm)

 

[mramirm]

no i'm not, i played along with the windbg but didn't understand how to deal with it, until i found that guide.

 

[TorrentG]

Cool, cool...

I just find it slightly unusual that the page was created AND updated today, the subject of the page is XP SP2 at that, and out of nowhere you show up linking to it...

Just seems like all too much coincidence to me that you found a page that was created/edited today with old subject matter and then link to it here within the same very day....

 

[mramirm]

i'm just sharing man, thats it

 

[Captain Jack]

Is that your site ?

 

[TorrentG]

Is that your site ?

The site is hosted in Singapore....dunno if it's the OP's site....just a fyi.

http://www.ip-adress.com/ip_tracer/182.50.134.128

 

[mramirm]

Is that your site ?

nope it's not

 

[ickymay]

analyze v isnt offering much info theres a lot more commands to use for debugging ......

I tend to use !analyze -v; kv; r; k; lmnt; lmntsm; .bugcheck mostly

try kd> .hh for help :-bd

 

[jcgriff2]

When debugging your own system, use the full kernel memory dump v. the mini kernel dump.

c:\windows\memory.dmp

It is overwritten each BSOD, so be sure to copy it out.

If Microsoft Windows OS driver or NT listed as the probable cause, run the Driver Verifier -

Driver Verifier - sysnative.com

Regards. . .

jcgriff2

`

 

[mramirm]

When debugging your own system, use the full kernel memory dump v. the mini kernel dump.

c:\windows\memory.dmp

It is overwritten each BSOD, so be sure to copy it out.

If Microsoft Windows OS driver or NT listed as the probable cause, run the Driver Verifier -

Driver Verifier - sysnative.com

Regards. . .

jcgriff2

`

thanks for the info i'll give it a try