locked
Windows 7 Home Edition Computer Blue Screen Error Code 7f RRS feed

  • Question

  • I have a Windows 7 Home Edition machine, an Asus G73JH-BST.  I have been getting various blue screen errors such as 9c and 3b, to the point that I could not keep the machine up and running long enough to try to fix it further.  I restored the system to factory settings using the disks I created when I purchased the machine.  Things have been going good for a few days but today I got the 7f error on a blue screen.  I have included the minidump and the first portion of the system information in the bottom of this message, any help or direction would be greatly appreciated.

    ----------Minidump---------------

    Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\082913-26847-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 \SystemRoot\system32\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 (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.18205.amd64fre.win7sp1_gdr.130708-1532
    Machine Name:
    Kernel base = 0xfffff800`03261000 PsLoadedModuleList = 0xfffff800`034a46d0
    Debug session time: Thu Aug 29 17:39:32.627 2013 (UTC - 4:00)
    System Uptime: 0 days 0:35:02.610
    *********************************************************************
    * 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 \SystemRoot\system32\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 7F, {8, 80050031, 6f8, fffff800033113bb}

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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 : ntoskrnl.exe ( nt+75b80 )

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

    ---------- System Information ----------------

    System Information report written at: 08/29/13 19:44:12
    System Name: WIN00
    [System Summary]

    Item Value
    OS Name Microsoft Windows 7 Home Premium
    Version 6.1.7601 Service Pack 1 Build 7601
    Other OS Description  Not Available
    OS Manufacturer Microsoft Corporation
    System Name WIN00
    System Manufacturer ASUSTeK Computer Inc.
    System Model G73Jh
    System Type x64-based PC
    Processor Intel(R) Core(TM) i7 CPU       Q 720  @ 1.60GHz, 1600 Mhz, 4 Core(s), 8 Logical Processor(s)
    BIOS Version/Date American Megatrends Inc. G73Jh.213, 1/27/2011
    SMBIOS Version 2.6
    Windows Directory C:\Windows
    System Directory C:\Windows\system32
    Boot Device \Device\HarddiskVolume2
    Locale United States
    Hardware Abstraction Layer Version = "6.1.7601.17514"
    User Name win00\Randall
    Time Zone Eastern Daylight Time
    Installed Physical Memory (RAM) 12.0 GB
    Total Physical Memory 11.9 GB
    Available Physical Memory 9.35 GB
    Total Virtual Memory 23.9 GB
    Available Virtual Memory 20.8 GB
    Page File Space 11.9 GB
    Page File C:\pagefile.sys

    Friday, August 30, 2013 2:24 AM

All replies

  • Bug Check 0x7F: UNEXPECTED_KERNEL_MODE_TRAP

    0x00000008, or Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Typically, the two exceptions are handled serially. However, there are several exceptions that cannot be handled serially, and in this situation the processor signals a double fault. There are two common causes of a double fault:

        * A kernel stack overflow. This overflow occurs when a guard page is hit, and the kernel tries to push a trap frame. Because there is no stack left, a stack overflow results, causing the double fault.
        * A hardware problem.

    It may caused by ZoneAlarm, if you have it installed, update the network card drivers first.

    You can also try this Hotfix (or install the Windows 7 Sp1 which includes the hotfix) if updating the network driver doesn't fix it:

    Stop error message when you run an application that transfers data by using the UDP protocol in Windows Server 2008 R2 or in Windows 7: "STOP 0x0000007F"
    http://support.microsoft.com/kb/981180/en-us

    When this doesn't fix it, remove ZoneAlarm.

    The minidumps are not useful for UNEXPECTED_KERNEL_MODE_TRAP bug checks.

    Configure your Windows to create a kernel dump [1] and upload the zipped dump (C:\Windows\memory.dmp) to your SkyDrive [2] and post a link here when the PC still crashes after removing ZoneAlarm and updating the drivers.

    André

    [1] http://www.brighthub.com/computing/windows-platform/articles/81867.aspx
    [2] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65


    "A programmer is just a tool which converts caffeine into code"

    Friday, August 30, 2013 5:28 AM
  • Hi Randall Weytens,

    Please try the following methods to solve this issue:

    Method 1: Diagnose memory problems.

    Run Memory Diagnostics tool to check for any memory problem. Please refer to the article Diagnosing memory problems on your computer to learn more about this tool:

    http://windows.microsoft.com/en-US/windows7/Diagnosing-memory-problems-on-your-computer

    Method 2: Get the latest drivers.

    Check if you are using the latest hardware drivers, especially the chipset and video drivers. Older drivers are a common contributor to BSOD issues. For your information, please review the following articles to get more help:

    Update drivers: recommended links http://windows.microsoft.com/en-us/windows/update-drivers-recommended-links#update-drivers-recommended-links=windows-7

    Update a driver for hardware that isn't working properly http://windows.microsoft.com/en-us/windows/update-driver-hardware-isnt-working-properly#update-driver-hardware-isnt-working-properly=windows-7

    Method 3: Safe mode and clean boot

    1. Safe mode starts Windows with a limited set of files and drivers. Startup programs do not  run in safe mode, and only the basic drivers needed to start Windows are installed. Safe mode is useful for troubleshooting problems with programs and drivers that might not start correctly, or that might prevent Windows from starting correctly. As for how to start into safe mode, please review this KB article Start your computer in safe mode.
    2. Perform a clean boot.

    A clean boot helps to verify if any third party application services or startup item is causing this issue. For your information, please review this KB article to put the computer in clean boot:

    How to troubleshoot a problem by performing a clean boot in Windows 8, Windows 7, or Windows Vista

    Note: Make sure you put the computer back to Normal Startup once you are done with the troubleshooting.

    For your information, please refer to the articles to get more help:

         http://windows.microsoft.com/en-us/windows7/Resolving-stop-blue-screen-errors-in-Windows-7

         http://support.microsoft.com/kb/981180/en-us

    Regards,

    Lany Zhang

    Friday, August 30, 2013 5:49 AM
  • Hello Andre,

    I do not have ZoneAlarm installed.  I do have Win7 SP1, and I tried the hotfix but it says it is not compatible with my computer.  I will configure my machine to do a kernel dump and upload it when it crashes again.

    Thank you,

    --Randall Weytens

    Friday, August 30, 2013 2:17 PM
  • Andre,

    Here is the location of the zipped dump file.  I don't have skydrive, but I do have dropbox.

    https://www.dropbox.com/sh/5av142w7ln0kzr3/aqSsFPIQeW

    Thank you,

    --Randall

    Friday, August 30, 2013 6:21 PM
  • this time you got a new bugcheck code:

    IRQL_NOT_LESS_OR_EQUAL (a)

    http://msdn.microsoft.com/en-us/library/ff560129%28v=vs.85%29.aspx

    The IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x0000000A. This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

    WinDbg tells memory corruption:

    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: fffffd680009e6a0, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, bitfield :
    	bit 0 : value 0 = read operation, 1 = write operation
    	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff8000323e232, address which referenced memory
    
    Debugging Details:
    ------------------
    
    Page 332950 not present in the dump file. Type ".hh dbgerr004" for details
    
    READ_ADDRESS:  fffffd680009e6a0 Nonpaged pool
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!MiSetPagingOfDriver+14e
    fffff800`0323e232 45397d00        cmp     dword ptr [r13],r15d
    
    DEFAULT_BUCKET_ID:  CODE_CORRUPTION
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  System
    
    ANALYSIS_VERSION: 6.3.9431.0 (debuggers(dbg).130615-1214) amd64fre
    
    TRAP_FRAME:  fffff880035e7970 -- (.trap 0xfffff880035e7970)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000058000000000 rbx=0000000000000000 rcx=0000000fffffffff
    rdx=fffff80003461de0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8000323e232 rsp=fffff880035e7b00 rbp=0000000000000002
     r8=fffff88003288800  r9=0000000000000000 r10=fffff8000321e000
    r11=00000000000002ca r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po cy
    nt!MiSetPagingOfDriver+0x14e:
    fffff800`0323e232 45397d00        cmp     dword ptr [r13],r15d ds:00000000`00000000=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80003293129 to fffff80003293b80
    
    STACK_TEXT:  
    fffff880`035e7828 fffff800`03293129 : 00000000`0000000a fffffd68`0009e6a0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`035e7830 fffff800`03291da0 : 00000005`00000000 00000001`00000000 0000d507`00000001 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`035e7970 fffff800`0323e232 : 00000000`00000000 00000000`00000000 00000000`00000002 fffff880`032887f0 : nt!KiPageFault+0x260
    fffff880`035e7b00 fffff880`035e7cd0 : fffff880`035e7c78 fffff800`034615e0 00000005`00000005 00000000`00000000 : nt!MiSetPagingOfDriver+0x14e
    fffff880`035e7c10 fffff880`035e7c78 : fffff800`034615e0 00000005`00000005 00000000`00000000 00000000`000000ff : 0xfffff880`035e7cd0
    fffff880`035e7c18 fffff800`034615e0 : 00000005`00000005 00000000`00000000 00000000`000000ff 00000001`40222a09 : 0xfffff880`035e7c78
    fffff880`035e7c20 00000005`00000005 : 00000000`00000000 00000000`000000ff 00000001`40222a09 fffff880`035e7c40 : nt!MmWorkingSetManagerEvent
    fffff880`035e7c28 00000000`00000000 : 00000000`000000ff 00000001`40222a09 fffff880`035e7c40 fffff880`035e7c40 : 0x00000005`00000005
    
    
    STACK_COMMAND:  kb
    
    CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
        fffff8000322e304 - nt! ?? ::FNODOBFM::`string'+46c9d
    	[ 78:58 ]
        fffff8000322e30c - nt! ?? ::FNODOBFM::`string'+46ca5 (+0x08)
    	[ 07:27 ]
        fffff8000322e314 - nt! ?? ::FNODOBFM::`string'+46cad (+0x08)
    	[ 8e:ae ]
        fffff8000322e32c - nt! ?? ::FNODOBFM::`string'+46cc5 (+0x18)
    	[ 4c:48 ]
        fffff8000323e34c - nt!MiSetPagingOfDriver+268 (+0x10020)
    	[ 4d:6d ]
        fffff8000323e354 - nt!MiSetPagingOfDriver+270 (+0x08)
    	[ fe:de ]
        fffff8000323e35c - nt!MiSetPagingOfDriver+278 (+0x08)
    	[ 49:69 ]
        fffff8000323e374 - nt!MiSetPagingOfDriver+290 (+0x18)
    	[ ff:fb ]
        fffff8000324e304 - nt!PfLogEvent+24 (+0xff90)
    	[ f1:d1 ]
        fffff8000324e30c - nt!PfLogEvent+2c (+0x08)
    	[ 8b:ab ]
        fffff8000324e31c - nt!PfLogEvent+3c (+0x10)
    	[ 0f:2f ]
        fffff8000324e334 - nt!PfLogEvent+54 (+0x18)
    	[ 45:41 ]
        fffff8000326e304 - nt!EtwpTraceMessageVa+19c (+0x1ffd0)
    	[ 48:68 ]
        fffff8000326e30c - nt!EtwpTraceMessageVa+1a4 (+0x08)
    	[ 00:20 ]
        fffff8000326e314 - nt!EtwpTraceMessageVa+1ac (+0x08)
    	[ 00:20 ]
        fffff8000327e344 - nt!MiProcessWorkingSets+388 (+0x10030)
    	[ 11:31 ]
        fffff8000327e35c - nt!MiProcessWorkingSets+3a0 (+0x18)
    	[ 00:20 ]
        fffff8000327e36c - nt!MiProcessWorkingSets+3b0 (+0x10)
    	[ ff:fb ]
        fffff8000328e30c - nt!ZwPulseEvent+c (+0xffa0)
    	[ 48:68 ]
        fffff8000328e31c - nt!ZwPulseEvent+1c (+0x10)
    	[ 00:20 ]
        fffff8000329e344 - nt!KiRetireDpcList+1f4 (+0x10028)
    	[ 00:20 ]
        fffff8000329e34c - nt!KiRetireDpcList+1fc (+0x08)
    	[ 83:a3 ]
        fffff8000329e354 - nt!KiRetireDpcList+204 (+0x08)
    	[ c6:e6 ]
        fffff8000329e36c - nt!KiRetireDpcList+21c (+0x18)
    	[ 47:43 ]
        fffff800032ae30c - nt!MmMapLockedPagesSpecifyCache+141 (+0xffa0)
    	[ 85:a5 ]
        fffff800032ae314 - nt!MmMapLockedPagesSpecifyCache+149 (+0x08)
    	[ 4d:6d ]
        fffff800032ae334 - nt!MmMapLockedPagesSpecifyCache+169 (+0x20)
    	[ 05:01 ]
        fffff800032be34c - nt!RtlUnwindEx+596 (+0x10018)
    	[ 0f:2f ]
        fffff800032be35c - nt!RtlUnwindEx+5a6 (+0x10)
    	[ 48:68 ]
        fffff800032be364 - nt!RtlUnwindEx+5ae (+0x08)
    	[ 0f:0b ]
        fffff800032be374 - nt!RtlUnwindEx+5be (+0x10)
    	[ e9:ed ]
        fffff800032ce30c - nt!KiPreprocessFault+88 (+0xff98)
    	[ 81:a1 ]
        fffff800032ce31c - nt!KiPreprocessFault+98 (+0x10)
    	[ 00:20 ]
        fffff800032ce324 - nt!KiPreprocessFault+a0 (+0x08)
    	[ 4c:48 ]
        fffff800032ce33c - nt!KiPreprocessFault+b8 (+0x18)
    	[ 0f:0b ]
        fffff800032de344 - nt!FsRtlpCancelExclusiveIrp+3c (+0x10008)
    	[ 4c:6c ]
        fffff800032de354 - nt!FsRtlpCancelExclusiveIrp+4c (+0x10)
    	[ c7:e7 ]
        fffff800032de364 - nt!FsRtlpCancelExclusiveIrp+5c (+0x10)
    	[ 8b:8f ]
        fffff800032de37c - nt!FsRtlpCancelExclusiveIrp+74 (+0x18)
    	[ 48:4c ]
        fffff800032ee304 - nt! ?? ::FNODOBFM::`string'+10774 (+0xff88)
    	[ e0:c0 ]
        fffff800032ee30c - nt! ?? ::FNODOBFM::`string'+1077c (+0x08)
    	[ 00:20 ]
        fffff800032ee314 - nt! ?? ::FNODOBFM::`string'+10784 (+0x08)
    	[ 4d:6d ]
        fffff800032ee324 - nt! ?? ::FNODOBFM::`string'+10794 (+0x10)
    	[ 24:20 ]
        fffff800032ee32c - nt! ?? ::FNODOBFM::`string'+1079c (+0x08)
    	[ 66:62 ]
        fffff800032fe34c - nt! ?? ::FNODOBFM::`string'+2b905 (+0x10020)
    	[ 48:68 ]
        fffff800032fe35c - nt! ?? ::FNODOBFM::`string'+2b915 (+0x10)
    	[ 8c:ac ]
        fffff800032fe36c - nt! ?? ::FNODOBFM::`string'+2b925 (+0x10)
    	[ e9:ed ]
        fffff8000330e314 - nt! ?? ::FNODOBFM::`string'+40c44 (+0xffa8)
    	[ 99:b9 ]
        fffff8000330e31c - nt! ?? ::FNODOBFM::`string'+40c4c (+0x08)
    	[ 8c:ac ]
        fffff8000331e36c - nt!ST_STORE<SM_TRAITS>::StRegionFindRepurpose+ac (+0x10050)
    	[ 44:40 ]
    WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view  entire output.
        fffff800033ce30c - nt!PspBreakOnFailedProtectedProcessOpen+3385
    	[ 00:20 ]
        fffff800033ce314 - nt!PspBreakOnFailedProtectedProcessOpen+338d (+0x08)
    	[ 00:20 ]
        fffff800033ce31c - nt!PspBreakOnFailedProtectedProcessOpen+3395 (+0x08)
    	[ 00:20 ]
        fffff800033de34c - nt!_imp_NtOpenSymbolicLinkObject+3e14 (+0x10030)
    	[ 1a:3a ]
        fffff800033ee304 - nt!_imp_NtOpenSymbolicLinkObject+13dcc (+0xffb8)
    	[ f0:d0 ]
        fffff800033ee30c - nt!_imp_NtOpenSymbolicLinkObject+13dd4 (+0x08)
    	[ 01:21 ]
        fffff800033ee314 - nt!_imp_NtOpenSymbolicLinkObject+13ddc (+0x08)
    	[ 5a:7a ]
        fffff800033ee31c - nt!_imp_NtOpenSymbolicLinkObject+13de4 (+0x08)
    	[ 01:21 ]
        fffff800033ee334 - nt!_imp_NtOpenSymbolicLinkObject+13dfc (+0x18)
    	[ 0c:08 ]
        fffff800033fe34c - nt!_imp_NtOpenSymbolicLinkObject+23e14 (+0x10018)
    	[ 01:21 ]
        fffff800033fe36c - nt!_imp_NtOpenSymbolicLinkObject+23e34 (+0x20)
    	[ 14:10 ]
        fffff800033fe374 - nt!_imp_NtOpenSymbolicLinkObject+23e3c (+0x08)
    	[ 20:24 ]
    Page 332950 not present in the dump file. Type ".hh dbgerr004" for details
        fffff800037fb6b2-fffff800037fb6b3  2 bytes - nt!_NULL_IMPORT_DESCRIPTOR <PERF> (nt+0x5dd6b2)
    	[ 0d 0a:00 00 ]
        fffff800038006b7-fffff800038006b8  2 bytes - nt!_NULL_IMPORT_DESCRIPTOR <PERF> (nt+0x5e26b7) (+0x5005)
    	[ 0d 0a:00 00 ]
        fffff80003800788-fffff8000380078b  4 bytes - nt!_NULL_IMPORT_DESCRIPTOR <PERF> (nt+0x5e2788) (+0xd1)
    	[ 0d 0a 0d 0a:00 00 00 00 ]
        fffff8000380097e-fffff8000380097f  2 bytes - nt!_NULL_IMPORT_DESCRIPTOR <PERF> (nt+0x5e297e) (+0x1f6)
    	[ 0d 0a:00 00 ]
        fffff8000380099e-fffff8000380099f  2 bytes - nt!_NULL_IMPORT_DESCRIPTOR <PERF> (nt+0x5e299e) (+0x20)
    	[ 0d 0a:00 00 ]
    103 errors : !nt (fffff8000322e304-fffff8000380099f)
    
    MODULE_NAME: memory_corruption
    
    IMAGE_NAME:  memory_corruption
    
    FOLLOWUP_NAME:  memory_corruption
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MEMORY_CORRUPTOR:  LARGE
    
    FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE
    
    BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE
    

    !chkimg and 103 errors : !nt tells me that the ntkrnlmp.exe on your HDD is corupted.

    Open a command prompt with admin rights and run sfc /scannow.

    http://support.microsoft.com/kb/929833


    "A programmer is just a tool which converts caffeine into code"

    • Proposed as answer by ZigZag3143x Friday, August 30, 2013 6:56 PM
    Friday, August 30, 2013 6:44 PM
  • Andre,

    I ran sfc /scannow as an administrator and it came up with no integrity violations.

    --Randall

    Saturday, August 31, 2013 2:18 PM
  • Larry,

    I have run memtest86 several times on this machine, and it came up with no errors found.  I have also tried reseating the RAM and HDD.  I looked through the drivers and everything is up to date, and there are no hardware errors reported.  I just did the safe boot and we'll see how that goes.

    Thank you for your help.

    -Randall

    Saturday, August 31, 2013 2:22 PM
  • Also run chkdsk C: /f. Is the HDD fine?

    "A programmer is just a tool which converts caffeine into code"

    Saturday, August 31, 2013 6:59 PM
  • Yes, I have run chkdsk C: /f.  The HDD is good.  I tried to replace it a few weeks ago because I thought this was the issue and I came up with the same problems.  I haven't had a crash since the clean boot, so I'm suspecting there is a service or startup program that was causing this.  
    Sunday, September 1, 2013 1:59 PM
  • Run CPU-Z look into the SPD and memory tab and compare the Timings

    "A programmer is just a tool which converts caffeine into code"

    Sunday, September 1, 2013 8:22 PM
  • I ran CPU-Z and the timings between the three memory slots in which I have RAM installed produce the same numbers.  I'm not that savvy with this program so number-wise, I don't know what I'm really looking for.  It recognizes all of the the memory installed.  Here's the validation page:

    http://valid.canardpc.com/2897966

    Monday, September 2, 2013 11:42 AM
  • post pictures of the SPD and memory tab

    "A programmer is just a tool which converts caffeine into code"

    Monday, September 2, 2013 7:20 PM