locked
Random Blue Screens RRS feed

  • Question

  • I am getting random blue screens on my Windows 7 machine. Its a Dell Optiplex 990, i5, 8gb ram. The blue screens only seem to happen when the machine is idle. Here are the results of the most recent dump file however I do not really know how to read them. It looks like wfd01000.sys is the issue but everything I've read online said that its probably something else. Any help would be greatly appreciated. 

    Loading Dump File [C:\Windows\Minidump\021114-21044-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path.           *
    * Use .symfix to have the debugger choose a symbol path.                   *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is: 
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0xfffff800`02c08000 PsLoadedModuleList = 0xfffff800`02e4b6d0
    Debug session time: Tue Feb 11 01:57:17.757 2014 (UTC - 8:00)
    System Uptime: 0 days 0:07:58.959
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...............
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {ffffffffffffffa4, 2, 1, fffff88000eed227}

    Unable to load image Wdf01000.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for Wdf01000.sys
    *** ERROR: Module load completed but symbols could not be loaded for Wdf01000.sys
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!KPRCB                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!KPRCB                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    Probably caused by : Wdf01000.sys ( Wdf01000+7b227 )

    Followup: MachineOwner
    ---------

    Tuesday, February 11, 2014 6:42 PM

Answers

  • Generally, you may update BIOS and other hardware drivers first.

    Do you have any third party security programs installed?

    If so, please temporarily disable all the third party security programs and test the issue.

    Meanwhile, you may reinstall or update the drivers for the network related device.

    Check these KB's

    Bug Check Code 0xD1
    http://msdn.microsoft.com/en-us/library/windows/hardware/ff560244%28v=vs.85%29.aspx

    Stop error when you resume a computer that is running Windows 7 or Windows Server 2008 R2 from sleep or from hibernation: "STOP: 0x000000D1"
    http://support.microsoft.com/kb/978982

    Stop error on a Windows Server 2008 R2-based or Windows 7-based computer when the operating system uses a virtual storport miniport driver to save a dump file or a hibernation file: "0x000000D1"
    http://support.microsoft.com/kb/2320550

    Another option is to contact Microsoft CSS for assistance.

    • Marked as answer by Cloud_TS Tuesday, March 4, 2014 3:40 PM
    Tuesday, February 25, 2014 9:13 AM

All replies

  • More Info...

    ADDITIONAL_DEBUG_TEXT:  
    Use '!findthebuild' command to search for the target build information.
    If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

    FAULTING_MODULE: fffff80002c08000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  51c51641

    WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
     ffffffffffffffa4 

    CURRENT_IRQL:  0

    FAULTING_IP: 
    Wdf01000+7b227
    fffff880`00eed227 f044014b0c      lock add dword ptr [rbx+0Ch],r9d

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0xD1

    LAST_CONTROL_TRANSFER:  from fffff80002c7d169 to fffff80002c7dbc0

    STACK_TEXT:  
    fffff800`00b9c258 fffff800`02c7d169 : 00000000`0000000a ffffffff`ffffffa4 00000000`00000002 00000000`00000001 : nt+0x75bc0
    fffff800`00b9c260 00000000`0000000a : ffffffff`ffffffa4 00000000`00000002 00000000`00000001 fffff880`00eed227 : nt+0x75169
    fffff800`00b9c268 ffffffff`ffffffa4 : 00000000`00000002 00000000`00000001 fffff880`00eed227 fffff800`02db1d0e : 0xa
    fffff800`00b9c270 00000000`00000002 : 00000000`00000001 fffff880`00eed227 fffff800`02db1d0e 00000000`00000000 : 0xffffffff`ffffffa4
    fffff800`00b9c278 00000000`00000001 : fffff880`00eed227 fffff800`02db1d0e 00000000`00000000 00000000`00000000 : 0x2
    fffff800`00b9c280 fffff880`00eed227 : fffff800`02db1d0e 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1
    fffff800`00b9c288 fffff800`02db1d0e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Wdf01000+0x7b227
    fffff800`00b9c290 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt+0x1a9d0e


    STACK_COMMAND:  kb

    FOLLOWUP_IP: 
    Wdf01000+7b227
    fffff880`00eed227 f044014b0c      lock add dword ptr [rbx+0Ch],r9d

    SYMBOL_STACK_INDEX:  6

    SYMBOL_NAME:  Wdf01000+7b227

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: Wdf01000

    IMAGE_NAME:  Wdf01000.sys

    BUCKET_ID:  WRONG_SYMBOLS

    Followup: MachineOwner
    ---------

    Tuesday, February 11, 2014 6:45 PM
  • We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  
    We prefer at least 2 DMP files to spot trends and confirm the cause.

    Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here
    If you have any questions about the procedure please ask

    Wanikiya and Dyami--Team Zigzag

    Tuesday, February 11, 2014 7:03 PM
  • Generally, you may update BIOS and other hardware drivers first.

    Do you have any third party security programs installed?

    If so, please temporarily disable all the third party security programs and test the issue.

    Meanwhile, you may reinstall or update the drivers for the network related device.

    Check these KB's

    Bug Check Code 0xD1
    http://msdn.microsoft.com/en-us/library/windows/hardware/ff560244%28v=vs.85%29.aspx

    Stop error when you resume a computer that is running Windows 7 or Windows Server 2008 R2 from sleep or from hibernation: "STOP: 0x000000D1"
    http://support.microsoft.com/kb/978982

    Stop error on a Windows Server 2008 R2-based or Windows 7-based computer when the operating system uses a virtual storport miniport driver to save a dump file or a hibernation file: "0x000000D1"
    http://support.microsoft.com/kb/2320550

    Another option is to contact Microsoft CSS for assistance.

    • Marked as answer by Cloud_TS Tuesday, March 4, 2014 3:40 PM
    Tuesday, February 25, 2014 9:13 AM