Go Back   AnandTech Forums > Software > Software for Windows

Forums
· Hardware and Technology
· CPUs and Overclocking
· Motherboards
· Video Cards and Graphics
· Memory and Storage
· Power Supplies
· Cases & Cooling
· SFF, Notebooks, Pre-Built/Barebones PCs
· Networking
· Peripherals
· General Hardware
· Highly Technical
· Computer Help
· Home Theater PCs
· Consumer Electronics
· Digital and Video Cameras
· Mobile Devices & Gadgets
· Audio/Video & Home Theater
· Software
· Software for Windows
· All Things Apple
· *nix Software
· Operating Systems
· Programming
· PC Gaming
· Console Gaming
· Distributed Computing
· Security
· Social
· Off Topic
· Politics and News
· Discussion Club
· Love and Relationships
· The Garage
· Health and Fitness
· Home and Garden
· Merchandise and Shopping
· For Sale/Trade
· Hot Deals with Free Stuff/Contests
· Black Friday 2014
· Forum Issues
· Technical Forum Issues
· Personal Forum Issues
· Suggestion Box
· Moderator Resources
· Moderator Discussions
   

Reply
 
Thread Tools
Old 11-02-2012, 01:08 PM   #1
vegoen
Junior Member
 
Join Date: May 2010
Posts: 17
Default Anyone experienced with WinDbg and BLUESCREENVIEW?

I'm trying to discern which one is more beneficial? Which is better for what use? Essentially, both show me which .sys has crashed. Bluescreenview is easier to use, but does WinDbg offer any advantages? It claims to go "deeper" but can anyone quantify that in anyway? I've read a lot about it, but I haven't found where it really shines and brings solutions to solving BSOD.
vegoen is offline   Reply With Quote
Old 11-02-2012, 03:23 PM   #2
Nothinman
Elite Member
 
Nothinman's Avatar
 
Join Date: Sep 2001
Posts: 30,672
Default

WinDbg is designed for people developing their own kernel mode drivers. Unless you're interested in trying to track down which function caused the BSOD, you shouldn't need to 'go deeper' than which driver crashed.
__________________
http://www.debian.org
Nothinman is offline   Reply With Quote
Old 11-02-2012, 03:57 PM   #3
vegoen
Junior Member
 
Join Date: May 2010
Posts: 17
Default

Quote:
Originally Posted by Nothinman View Post
WinDbg is designed for people developing their own kernel mode drivers. Unless you're interested in trying to track down which function caused the BSOD, you shouldn't need to 'go deeper' than which driver crashed.
Thank you for your reply.

This is precisely what I want to do, try to re-create the driver scenario that caused the crash, "Force BSOD".

For instance, I'm dealing with the ambiguous ""ntkrnlmp.exe" BSOD. This can be any hardware or software issue. In the WinDbg it shows the call stack as:

STACK_TEXT:
fffff880`0a06c888 fffff800`032f7b40 : 00000000`0000001a 00000000`00041790 fffffa80`0092cf10 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0a06c890 fffff800`0325d405 : ffffffff`00000000 00000000`0789ffff fffffa80`00000000 fffffa80`08291060 : nt! ?? ::FNODOBFM::`string'+0x355e4
fffff880`0a06ca50 fffff800`0355d6da : fffff8a0`017f3050 00000000`00000001 00000000`00000000 fffffa80`08291060 : nt!MmCleanProcessAddressSpace+0x679
fffff880`0a06caa0 fffff800`0353efb8 : 00000000`00000000 00000000`00000001 00000000`fffdb000 00000000`00000000 : nt!PspExitThread+0x56a
fffff880`0a06cba0 fffff800`0328b453 : fffffa80`07977060 00000000`00000000 fffffa80`08291060 00000000`05595110 : nt!NtTerminateProcess+0x138
fffff880`0a06cc20 00000000`771215da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0018dfc8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x771215da

This is the last memory transfers before the BSOD. I'm trying to figure out if I can discern exactly when, what and where caused the BSOD. Is it hardware, or is it software?

In the case of the ntkrnl crashes, I DO need to track down the functions
vegoen is offline   Reply With Quote
Old 11-03-2012, 10:12 AM   #4
Bubbaleone
Golden Member
 
Bubbaleone's Avatar
 
Join Date: Nov 2011
Posts: 1,670
Default

Posting just the call stack gives no insight to the problem you're having. Upload your latest small memory dump to a free file hosting site e.g., MediaFire, and post the download link. I'll analyze it for you with WinDbg.
Bubbaleone is offline   Reply With Quote
Old 11-05-2012, 12:38 PM   #5
reallyscrued
Platinum Member
 
reallyscrued's Avatar
 
Join Date: Jul 2004
Posts: 2,403
Default

This thread is about to get sexy.
__________________

AMD Phenom II BE965 - 4.0 Ghz || Gigabyte 7850 2GB - 1050/5500 || GA-MA790X-UD4P - 240 Mhz FSB
4 GB Dual-Channel DDR2 - 800 Mhz || WD Caviar Black 1TB || WD Caviar Green 2TB
Denon AVR-591 || Pioneer SP-FS51/C21/BS-41 || BIC F12 || Klipsch RW-12D || Sennheiser HD 202-II || Panasonic TC-P50U50
reallyscrued is offline   Reply With Quote
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -5. The time now is 02:57 PM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.