Personal computing discussed

Moderators: Flying Fox, Ryu Connor

Topic Author
Posts: 47
Joined: Sat Aug 20, 2011 5:38 am

BSOD On Windows 7 Pro

Tue Jul 09, 2013 1:48 am


Currently i'm using Win 7 Pro machine, while I was just browsing the net I got a BSOD all of sudden.

I googled to see how to open the .dmp file that was created however i'm not successful even with Windows SDK

So my questions is, is there a way to open .dmp files with Windows SDK? Thanks

I'm using Intel x64 I7 CPU by the way. Thanks
Gerbil Elite
Posts: 565
Joined: Sun Dec 16, 2007 2:42 pm

Re: BSOD On Windows 7 Pro

Tue Jul 09, 2013 2:00 am

I used this in the past I would suggest to post your issue on Windows 7 forum as well.
Alienware: Core i7 960 3.2GHz | 12GB RAM | 1.5TB HD | EVGA GTX Titan X | Dell WFP 3008 30" 2560x1600 | Windows 10 Pro 64 Bit
just brew it!
Gold subscriber
Posts: 47840
Joined: Tue Aug 20, 2002 10:51 pm
Location: Somewhere, having a beer

Re: BSOD On Windows 7 Pro

Tue Jul 09, 2013 3:06 am

New build? Old build? Anything changed in the system config (hardware or software) lately?
If the world isn't making sense to you, you're either drinking too much or not drinking enough.
Grand Gerbil Poohbah
Posts: 3671
Joined: Tue Jan 01, 2002 7:00 pm
Location: Solna/Sweden

Re: BSOD On Windows 7 Pro

Tue Jul 09, 2013 11:18 pm

You can open dump-files from WinDbg that's available in the WinSDK IIRC. You also need the correct symbol set for your installation and point windbg to look at that, otherwise it will make very Little sense. Even then, if the BSOD is tied to a driver that you dont have the symbols for, it will still not Always make that much sense. One thing to note is that is that it's not always the driver/etc that the BSOD information points to that is the main culprit, it could just as well be something else that for some reason disburbs/intersects with said driver in different ways.
Grand Admiral Gerbil
Posts: 10246
Joined: Thu Jun 19, 2003 3:11 pm

Re: BSOD On Windows 7 Pro

Wed Jul 10, 2013 12:47 am

Are you overclocked at all? Did you look at temps?

Absent those, it's almost always bad hardware or drivers.

Who is online

Users browsing this forum: No registered users and 5 guests