locked
Bluescreen (with dump file!) RRS feed

  • Question

  • I just factory restored the whole system from scratch, installed Microsoft updates, Spotify, Chrome, AVG, & VLC media player. Thought it was fine until, boom. Starts crashing again. I've looked at many sites and posts saying it's probably a driver, or some cpu, ram, hd issue, but I cannot find the problem. It is an HP slimline desktop

    Here is the info that Windows welcomes me with when I resume from sleep.

     Problem Event Name: BlueScreen
      OS Version: 6.1.7601.2.1.0.768.3
      Locale ID: 1033

    Additional information about the problem:
      BCCode: 7a
      BCP1: 0000000000000020
      BCP2: FFFFFFFFC000009D
      BCP3: FFFFFA800609B588
      BCP4: 0000000000000000
      OS Version: 6_1_7601
      Service Pack: 1_0
      Product: 768_1

    Files that help describe the problem:
      C:\Windows\Minidump\060315-43493-01.dmp
      C:\Users\Austin\AppData\Local\Temp\WER-81494-0.sysdata.xml

    Here is a link to the Dump

    http://1drv.ms/1EXoz1h

    Wednesday, June 3, 2015 10:08 PM

All replies

  • These crashes were related to memory corruption (probably caused by a driver). 

    Please run these two tests to verify your memory and find which driver is causing the problem.  Please run verifier first.  You do not need to run memtest yet unless verifier does not find the cause, or you want to.


    If you are over-clocking anything reset to default before running these tests.
    In other words STOP!!!  If you do not know what this means you probably are not


    1-Driver verifier (for complete directions see our wiki here)

    2-Memtest. (You can read more about running memtest here)



    Wanikiya and Dyami--Team Zigzag

    Wednesday, June 3, 2015 10:27 PM
  • Hmm... I had  been running Verifier before the crash. I'll let it crash a few more times and upload all the dmps.

    The memtest looks complicated, and I'd hate to waste a disc, burning it to a cd, but I'll try that if the verifier proves unhelpful.

    Wednesday, June 3, 2015 11:31 PM
  • Hi,

    How's everything going? If you get any progress, please feel share it with us.

    Regards


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Friday, June 5, 2015 7:44 AM
  • I have let Verifier run some more.

    I also noticed, after factory reset, I had 130 updates to install. Foolishly, I must have selected to download all of them. Now, whenever I shut down the pc, it tries, and fails to install them. It will "install" all the way, but after the reboot, when finalizing/optimizing them, it reverts back to before the changes, because there was an error.

    Here are the latest two dump files.

    http://1drv.ms/1KeShpw

    http://1drv.ms/1KeSiK9

    Friday, June 5, 2015 2:09 PM
  • Not driver verified but it does not matter

    There was a hardware error with the HD

    I would go to the HD maker>download and run their HD checking utility

    Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\zigza\Desktop\060515-38095-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Machine Name:
    Kernel base = 0xfffff800`02a55000 PsLoadedModuleList = 0xfffff800`02c9a650
    Debug session time: Fri Jun  5 09:41:10.719 2015 (UTC - 4:00)
    System Uptime: 0 days 5:45:15.311
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ....................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 7A, {20, ffffffffc000009d, fffffa80067ea078, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+51140 )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    KERNEL_DATA_INPAGE_ERROR (7a)
    The requested page of kernel data could not be read in.  Typically caused by
    a bad block in the paging file or disk controller error. Also see
    KERNEL_STACK_INPAGE_ERROR.
    If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
    it means the disk subsystem has experienced a failure.
    If the error status is 0xC000009A, then it means the request failed because
    a filesystem failed to make forward progress.
    Arguments:
    Arg1: 0000000000000020, lock type that was held (value 1,2,3, or PTE address)
    Arg2: ffffffffc000009d, error status (normally i/o status code)
    Arg3: fffffa80067ea078, current process (virtual address for lock type 3, or PTE)
    Arg4: 0000000000000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
    
    Debugging Details:
    ------------------
    
    
    ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED
    
    DISK_HARDWARE_ERROR: There was error with disk hardware
    
    BUGCHECK_STR:  0x7a_c000009d
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  1
    
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff80002ac99fc to fffff80002ad4d00
    
    STACK_TEXT:  
    fffff880`03355a88 fffff800`02ac99fc : 00000000`0000007a 00000000`00000020 ffffffff`c000009d fffffa80`067ea078 : nt!KeBugCheckEx
    fffff880`03355a90 fffff800`02abe957 : fffffa80`067ea010 00000000`c000009d 00000000`00000000 fffffa80`067ea0a8 : nt! ?? ::FNODOBFM::`string'+0x51140
    fffff880`03355b50 fffff800`02ac8377 : fffffa80`03725680 fffffa80`037256d0 fffffa80`06814010 fffffa80`06814078 : nt!IopCompletePageWrite+0x57
    fffff880`03355b80 fffff800`02ada19d : fffffa80`03725680 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1c7
    fffff880`03355c00 fffff800`02a9c27b : fffffa80`03725680 fffff880`02f68f40 00000000`00000000 fffff800`02a649e0 : nt!KiCommitThreadWait+0x3dd
    fffff880`03355c90 fffff800`02a64a3a : fffffa80`03725680 00000000`00000001 fffffa80`03684890 00000000`00000000 : nt!KeWaitForGate+0xfb
    fffff880`03355ce0 fffff800`02d7132e : fffffa80`03725680 30000004`41408140 00000000`00000080 00000000`00000001 : nt!MiModifiedPageWriter+0x5a
    fffff880`03355d40 fffff800`02ac6666 : fffff880`02f64180 fffffa80`03725680 fffff880`02f6efc0 84020000`00004000 : nt!PspSystemThreadStartup+0x5a
    fffff880`03355d80 00000000`00000000 : fffff880`03356000 fffff880`03350000 fffff880`03355a80 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+51140
    fffff800`02ac99fc cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+51140
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b
    
    IMAGE_VERSION:  6.1.7601.17592
    
    FAILURE_BUCKET_ID:  X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+51140
    
    BUCKET_ID:  X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+51140
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x7a_c000009d_nt!_??_::fnodobfm::_string_+51140
    
    FAILURE_ID_HASH:  {1680a4a2-ab7e-74d3-69ee-09929c93c442}
    
    Followup: MachineOwner
    ---------
    
    


    Wanikiya and Dyami--Team Zigzag

    Friday, June 5, 2015 2:17 PM
  • I system restored a second time, and selectively updated. I have not had any problems with the sleep function since then.

    Granted, I have about 100 updates I haven't installed, but it's worth it so far!

    Tuesday, June 9, 2015 5:41 PM