A Quick Way to find Windows BSOD Problems

----

Problem report: \\
jackvull June 10, 2009 at 08:09:07 Pacific \\
Specs: Windows XP, 2Gb

    I am getting an intermittent BSOD 0x3F error. 
    ...usually after having the laptop on for a while but running over 1Gb memory in applications. I have 2Gb installed.
    I ran a hard drive scan - fine.
    I tested memory with memtest on 1 pass - fine.
    The error doesn't list "out of PTES" so it can't be that but that's the only reference I can find on Google searches.
    What else could it be?
    I replaced the memory recently to upgrade to 2x1Gb sticks. I replaced 1 of the memory sticks as I thought it was faulty but no change.
    Any ideas?
    There's no way I can identify if it is a driver as I have no way of knowing what drivers have been installed 
    in the last few months as I have been installing and uninstalling various bits of software.

    Error code 0000003f, parameter1 00000000, parameter2 0000000b, parameter3 000000e1, parameter4 000003df.

Reply ↓ \\
Johnw June 10, 2009 at 21:53:34 Pacific

    If the computer works ok in safe mode, try disabling all services and startup programs using the msconfig tool. 
    See if you still have the issue, then start them up in sequence to troubleshoot the device or driver that is causing the issue.
    Start, Run, "MSCONFIG"
    Click on the "Services" Tab, put a check in "Hide all Microsoft Services", then click "disable all"
    Click on the "Startup" Tab, click "disable all"
    Reboot and test

Reply ↓ \\
jackvull June 11, 2009 at 00:30:54 Pacific

    The problem is that the computer starts fine. I might get the error after 5 hours, or it might be 2 days, or it might be 30mins.
    Starting each program in turn is going to take a long time let alone the fact that I need all the programs on a daily basis :)
    Why doesn't the driver get listed in the BSOD?
    Is there any software I could use to help track the problem?

Reply ↓ \\
Johnw June 11, 2009 at 01:04:19 Pacific

    You may get more info from minidumps. Make sure it is Enabled.
    Control Panel --> System --> Advanced --> Startup and Recovery --> Settings ---> Write debugging
    information --> Complete memory dump.
    On XP and 2003 systems, mini dumps are located at %SystemRoot%\Minidump, or c:\Windows\Minidump; 
    kernel and full dumps are located at %SystemRoot%\MEMORY.DMP or c:\Windows\MEMORY.DMP.
    How to solve Windows system crashes in minutes
    http://www.networkworld.com/news/2005/041105-windows-crash.html
    http://www.codeproject.com/KB/debug/windbg_part1.aspx
    http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
    Install Debugging Tools for Windows 64-bit Version
    http://www.microsoft.com/whdc/devtools/debugging/install64bit.mspx
    http://www.microsoft.com/whdc/devtools/debugging/default.mspx
    http://forums.majorgeeks.com/showthread.php?t=35246
    This primer will show you how to solve problems quickly. Using a tool that costs nothing, 
    you can solve approximately 50% of Windows server and workstation crashes in a few minutes.
    The tool is WinDbg, the free Windows debugger.
    You've probably never used the debugger, don't have it and don't want it. 
    After all, it's a developer's tool, not an administrator's, right? Yes, but what you need to 
    know is remarkably easy to learn, and even a rudimentary familiarity with the debugger could 
    enhance your skills and your resume.
    Still hesitant? Think about this: After rebooting a crashed machine, we've brought up the debugger, 
    opened a memory dump file, given the debugger a single command, and learned not only that the cause 
    was a driver, but also the driver's name — all in less than a minute. Granted, the debugger was 
    installed and configured, we knew what commands to use and what to look for.
    But so will you by the end of this article.

    Or,

    Grabtxt
    http://www.snapfiles.com/get/grabtxt.html
    http://halmisbah.blogspot.com/2008/07/grabtxt-10.html
    Capture text from Windows error dialogs.
    Grabtxt is a simple utility that enables you to capture the text portions from many Windows dialog boxes. 
    The captured text can be copied to the clipboard (Ctrl+C) or used to search for details via Google 
    or Live.com with the provided shortcut buttons. The program can be useful if you need to copy an error 
    message for a bug report or want to find out additional information via online search engines without 
    having to manually type the text. Grabtxt worked with most, but not all, Windows dialogs that we tested.
    Requirements: .NET Framework 2.0 W2000/XP/2003/Vista.

    Or,

    Event Log Explorer
    http://www.softpedia.com/get/System/System-Info/Event-Log-Explorer.shtml
    http://www.eventlogxp.com/
    http://www.eventlogxp.com/download/elex.zip
    Event Log Explorer is a free software for viewing, monitoring and analyzing events recorded in Security, 
    System, Application and another logs of Microsoft Windows NT/2000/XP/2003/Vista ( 32 & 64 bit ) 
    operating systems. It extends standard Event Viewer monitoring functionality and brings new features. 
    Free registration.