BSODs but no longer seem to create dump files


  1. Posts : 6
    Win7 Ultimate x64
       #1

    BSODs but no longer seem to create dump files


    First, let me say that the info on this site is a tremendous resource. You guys are great to run this.
    I started getting kernal_data_inpage_error BSODs about a month ago. I found your site and found minidumps were being created in c:\windows\minidump\ just like the site indicated. For the last couple of weeks, I still periodically get the BSODs but no .dmp files are getting created. The BSODs report that the physical memory dump has been completed successfully. I followed your procedure to try to enable the dumps (see attached jpeg) but still no longer see any dump files being produced.
    I walked through How to Force a Blue Screen in Windows: 13 Steps - wikiHow so that I can create BSODs at will but still do not see any dmp files actually being created. The three things I did around the time that I stopped getting minidumps were
    1) In a non-admin session, I used WinExplorer to navigate to windows\minidump. When I was prompted that I was would not be allowed access, I answered "yes" to grant me (from a non-admin logon) access to the folder.
    2) I saw there were some very old .dmp files (2+ years ago) in the folder. I deleted those .dmp files
    Would either of these stop minidumps from being taken?
    I know there is probably something I have messed up but I cannot see it. Can you help me get back to where minidumps are being created again.
    3) I walked through your process to systemadvancedsetup process a couple of times to change the dump type to a full dump and back to a minidump.
    FYI - before, I believe that before, a BSOD would roll "percentage xx complete" during the process... now, it just seems to immediately say "dump complete" or something like that.
    Any assistance would be greatly appreciated.
    Thanks,
    John
    FYI keyboard-generated BSODs immediately indicate "Collecting data for crash dump", "Initiating disk for crash dump" and "physical memory dump complete"... all show at once.
    Last edited by johncros; 18 Jul 2013 at 04:06. Reason: add info about BSOD display
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    johncros, your HDDs are not functioning properly.
    Event[34298]:
    Log Name: System
    Source: Ntfs
    Date: 2013-06-19T10:30:44.940
    Event ID: 55
    Task: N/A
    Level: Error
    Opcode: N/A
    Keyword: Classic
    User: N/A
    User Name: N/A
    Computer: HPDesktop
    Description:
    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume DadsHPDeskC.
    Now, the said volume is .....

    No code has to be inserted here.

    Do some Disc checks on that HDD, and on the others too.

    1. Reseat the sata and power.
    2. Run chkdsk /f/r, following the option two of the tutorial Disk Check
    3. Seatool for dos: SeaTools | Seagate download
      • Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.
      • You can use Win32 DiscImager to create a bootable USB and run Seatools for DOS. Follow this post to know how to make a bootable Seatools USB.


    At the same time, it appears that no disc controllers are not installed?

    1. Right click on "my computer" icon and click "manage" on the context menu.
    2. It will open the "computer management" window.
    3. Select "Device Manager" in the left pane, It will list all the existing devices up.
    4. Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
    5. Select one Intel device item under it, right click, Properties.
    6. In the Properties dialog, click on the Driver" tab, and then the driver details button.
    7. Take a screenshot using snipping tool and upload the screenshot here.

      It is to see the working drivers.

    It is also appearing that the hiosd.sys, WD Boost Storage Filter Driver is failing.
    Code:
    fffff880`03daf520  fffff880`0109e800Unable to load image \SystemRoot\system32\DRIVERS\hiosd.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for hiosd.sys
    *** ERROR: Module load completed but symbols could not be loaded for hiosd.sys
     hiosd+0x21800
    I would suggest you to uninstall the program and the associated filter driver (c:\windows\system32\drivers\hiosd.sys), bith is to be deleted.

    Let us know the results.
    ______________________________________________________________________
    BSOD ANALYSIS:

    Code:
    ..................................................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 7A, {fffff6fb40000008, ffffffffc00000c0, 4737a884, fffff68000001000}
    
    Probably caused by : volsnap.sys ( volsnap!VspCleanupVolumeSnapshot+16c )
    
    Followup: MachineOwner
    ---------
    
    1: 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: fffff6fb40000008, lock type that was held (value 1,2,3, or PTE address)
    Arg2: ffffffffc00000c0, error status (normally i/o status code)
    Arg3: 000000004737a884, current process (virtual address for lock type 3, or PTE)
    Arg4: fffff68000001000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
    
    Debugging Details:
    ------------------
    
    
    ERROR_CODE: (NTSTATUS) 0xc00000c0 - This device does not exist.
    
    BUGCHECK_STR:  0x7a_c00000c0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff80003535742 to fffff800034c2c00
    
    STACK_TEXT:  
    fffff880`03daf258 fffff800`03535742 : 00000000`0000007a fffff6fb`40000008 ffffffff`c00000c0 00000000`4737a884 : nt!KeBugCheckEx
    fffff880`03daf260 fffff800`034e991f : fffffa80`11ac7c80 fffff880`03daf3d0 fffffa80`06a3a3d8 fffffa80`11ac7c80 : nt! ?? ::FNODOBFM::`string'+0x36c1a
    fffff880`03daf340 fffff800`034d028a : 00000000`00000000 00000000`00000008 ffffffff`ffffffff fffffa80`06900e30 : nt!MiIssueHardFault+0x28b
    fffff880`03daf410 fffff800`034a4bca : 00000000`00000000 fffff680`00001000 fffffa80`07c5c000 fffffa80`06a4b040 : nt!MmAccessFault+0x146a
    fffff880`03daf570 fffff800`034f443a : 00000000`002a0002 fffff6fb`7da00000 fffff680`00001000 fffffa80`06a4b001 : nt!MiMakeSystemAddressValid+0xea
    fffff880`03daf5d0 fffff800`034f57d9 : fffff880`00000000 00000000`002bffff fffffa80`00000000 fffffa80`0aed43f0 : nt!MiDeleteVirtualAddresses+0xa39
    fffff880`03daf790 fffff800`037dd1c1 : fffffa80`07548540 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
    fffff880`03daf8b0 fffff800`037dd5c3 : fffff880`00000000 00000000`002a0000 fffffa80`00000001 fffff880`00000000 : nt!MiUnmapViewOfSection+0x1b1
    fffff880`03daf970 fffff800`034c1e93 : 00000000`00000200 fffffa80`00000000 fffffa80`06a3a040 00000000`00000000 : nt!NtUnmapViewOfSection+0x5f
    fffff880`03daf9c0 fffff800`034be450 : fffff880`022285cc 00000000`002c0000 00000000`00000000 00000000`206c644d : nt!KiSystemServiceCopyEnd+0x13
    fffff880`03dafb58 fffff880`022285cc : 00000000`002c0000 00000000`00000000 00000000`206c644d 00000000`00000000 : nt!KiServiceLinkage
    fffff880`03dafb60 fffff880`02229bf2 : fffffa80`07b49ae8 fffffa80`080443d8 fffffa80`07b49a30 00000000`00000000 : volsnap!VspCleanupVolumeSnapshot+0x16c
    fffff880`03dafbc0 fffff880`02229eca : 00000000`00000000 fffff800`03668200 fffffa80`080443d8 00000000`00000000 : volsnap!VspDeleteOldestSnapshot+0xf2
    fffff880`03dafc10 fffff800`034cc251 : fffff880`02229e30 fffff800`036682d8 fffffa80`06a4b040 fffffa80`0fc77010 : volsnap!VspDestroyAllSnapshotsWorker+0x9a
    fffff880`03dafc70 fffff800`03760ede : 00000000`00000000 fffffa80`06a4b040 00000000`00000080 fffffa80`06a3a040 : nt!ExpWorkerThread+0x111
    fffff880`03dafd00 fffff800`034b3906 : fffff880`03b64180 fffffa80`06a4b040 fffff880`03b6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`03dafd40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    volsnap!VspCleanupVolumeSnapshot+16c
    fffff880`022285cc 4533ed          xor     r13d,r13d
    
    SYMBOL_STACK_INDEX:  b
    
    SYMBOL_NAME:  volsnap!VspCleanupVolumeSnapshot+16c
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: volsnap
    
    IMAGE_NAME:  volsnap.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce792c8
    
    FAILURE_BUCKET_ID:  X64_0x7a_c00000c0_volsnap!VspCleanupVolumeSnapshot+16c
    
    BUCKET_ID:  X64_0x7a_c00000c0_volsnap!VspCleanupVolumeSnapshot+16c
    
    Followup: MachineOwner
    ---------
    
    1: kd> lmvm volsnap
    start             end                 module name
    fffff880`02200000 fffff880`0224c000   volsnap    (pdb symbols)          c:\symbols\volsnap.pdb\6C762AD2B37146AA848E4A16BD846B852\volsnap.pdb
        Loaded symbol image file: volsnap.sys
        Mapped memory image file: c:\symbols\volsnap.sys\4CE792C84c000\volsnap.sys
        Image path: \SystemRoot\system32\drivers\volsnap.sys
        Image name: volsnap.sys
        Timestamp:        Sat Nov 20 14:50:08 2010 (4CE792C8)
        CheckSum:         000527ED
        ImageSize:        0004C000
        File version:     6.1.7601.17514
        Product version:  6.1.7601.17514
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        3.7 Driver
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     volsnap.sys
        OriginalFilename: volsnap.sys
        ProductVersion:   6.1.7601.17514
        FileVersion:      6.1.7601.17514 (win7sp1_rtm.101119-1850)
        FileDescription:  Volume Shadow Copy Driver
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
      My Computer


  3. Posts : 6
    Win7 Ultimate x64
    Thread Starter
       #3

    mini dumps work again after reloading disk drivers


    THANK YOU.
    The cable and connectors were secure. I had already run chkdsk when win7 alerted on the NTFS problem in June and the chkdsk of all the partitions were still clean today. Deinstalling and then restalling the disk drivers seem to be what did the trick. At least now, the keyboard-induced BSODs create minidump files as they should. I will have to way and see if I get any more of the kernel_data_inpage-error s return.
    Thanks... At least I will be able to get a dump if they do.
    John
      My Computer


  4. Posts : 6
    Win7 Ultimate x64
    Thread Starter
       #4

    It has been a couple of weeks and I have not seen any more BSOD errors.
    Thanks you.
      My Computer


  5. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #5

    You are welcome mare :)
    For any further issue, let us know :)
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 05:01.
Find Us