Windows 7 Analyze BSOD with windbg

mramirm · Dec 18, 2010

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 · Dec 18, 2010

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 · Dec 18, 2010

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 · Dec 18, 2010

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 · Dec 18, 2010

i'm just sharing man, thats it

Captain Jack · Dec 18, 2010

Is that your site ?

TorrentG · Dec 18, 2010

Captain Jack said:
Is that your site ?

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

Link Removed

mramirm · Dec 18, 2010

Captain Jack said:
Is that your site ?

nope it's not

ickymay · Dec 18, 2010

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 :razz:

try kd> .hh for help :-bd

jcgriff2 · Dec 18, 2010

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 -

Link Removed

Regards. . .

jcgriff2

`

mramirm · Dec 19, 2010

jcgriff2 said:
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 -

Link Removed

Regards. . .

jcgriff2

`

thanks for the info i'll give it a try

Search

Navigation section

Windows 7 Analyze BSOD with windbg

mramirm

New Member

jcgriff2

TorrentG

Banned

mramirm

New Member

TorrentG

Banned

mramirm

New Member

Captain Jack

Former Moderator

TorrentG

Banned

mramirm

New Member

ickymay

New Member

jcgriff2

Extraordinary Member

mramirm

New Member

Similar threads