BSOD On Just About Every Action

Page 2 of 4 FirstFirst 1234 LastLast

  1. Posts : 20
    Windows 10
    Thread Starter
       #11

    Memtest had 10 runs with no errors. @axe0 yes those were the BSOD on boot when driver verifier was on. Sorry about the lack of dump files about it but in order to access the pc I had to reset it. For whatever reason, dump files aren't included in the 'Keep Documents' option and I had yet to make a restore point.

    How would I go about checking the memory descriptors of the addresses with which this driver attempted to free the memory?
    Last edited by Mashalien; 24 Jul 2016 at 07:24. Reason: just something I forgot
      My Computer


  2. Posts : 14,901
    Windows 10 Pro
       #12

    How would I go about checking the memory descriptors of the addresses with which this driver attempted to free the memory?
    That is more a thing that we do.
    You would require knowledge about Windows as you need to know what is and what is not a violation, you also need to know how to debug a kernel memory dump.
    With knowledge about Windows I do not mean the visible part, but the part 'behind the scenes', thus the part that happens in the background that the user is not aware of.

    An example of a mini memory dump.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
    This means a trap occurred in kernel mode, and it's a trap of a kind
    that the kernel isn't allowed to have/catch (bound trap) or that
    is always instant death (double fault).  The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. Here is a *portion* of those codes:
    If kv shows a taskGate
            use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
            use .trap on that value
    Else
            .trap on the appropriate frame will show where the trap was taken
            (on x86, this will be the ebp that goes with the procedure KiTrap)
    Endif
    kb will then show the corrected stack.
    Arguments:
    Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
    Arg2: ffffd000ebb96a30
    Arg3: 000000007267d5e9
    Arg4: fffff8016286ffb3
    
    Debugging Details:
    ------------------
    
    
    DUMP_CLASS: 1
    
    DUMP_QUALIFIER: 400
    
    BUILD_VERSION_STRING:  10240.17022.amd64fre.th1_st1.160623-1726
    
    SYSTEM_PRODUCT_NAME:  To Be Filled By O.E.M.
    
    SYSTEM_SKU:  To Be Filled By O.E.M.
    
    SYSTEM_VERSION:  To Be Filled By O.E.M.
    
    BIOS_VENDOR:  American Megatrends Inc.
    
    BIOS_VERSION:  P2.60
    
    BIOS_DATE:  07/11/2013
    
    BASEBOARD_MANUFACTURER:  ASRock
    
    BASEBOARD_PRODUCT:  FM2A75 Pro4-M
    
    BASEBOARD_VERSION:                        
    
    DUMP_TYPE:  2
    
    DUMP_FILE_ATTRIBUTES: 0x8
      Kernel Generated Triage Dump
    
    BUGCHECK_P1: 8
    
    BUGCHECK_P2: ffffd000ebb96a30
    
    BUGCHECK_P3: 7267d5e9
    
    BUGCHECK_P4: fffff8016286ffb3
    
    BUGCHECK_STR:  0x7f_8
    
    BAD_STACK_POINTER:  000000007267d5e9
    
    CPU_COUNT: 4
    
    CPU_MHZ: ed1
    
    CPU_VENDOR:  AuthenticAMD
    
    CPU_FAMILY: 15
    
    CPU_MODEL: 10
    
    CPU_STEPPING: 1
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ANALYSIS_SESSION_HOST:  DESKTOP-FO9QHGA
    
    ANALYSIS_SESSION_TIME:  07-24-2016 14:34:50.0967
    
    ANALYSIS_VERSION: 10.0.10586.567 amd64fre
    
    MISALIGNED_IP: 
    nt!PpmIdleExecuteTransition+e43
    fffff801`6286ffb3 0200            add     al,byte ptr [rax]
    
    UNALIGNED_STACK_POINTER:  000000007267d5e9
    
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff8016286ffb3
    
    STACK_TEXT:  
    00000000`7267d5e9 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PpmIdleExecuteTransition+0xe43
    
    
    STACK_COMMAND:  kb
    
    THREAD_SHA1_HASH_MOD_FUNC:  65379b530d41d556923d028b21bfeaf00278ad84
    
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  350c605a2a491af7c8be756570a5f8f1e6fb91d1
    
    THREAD_SHA1_HASH_MOD:  76cd06466d098060a9eb26e5fd2a25cb1f3fe0a3
    
    FOLLOWUP_IP: 
    nt!PpmIdleExecuteTransition+e43
    fffff801`6286ffb3 0200            add     al,byte ptr [rax]
    
    FAULT_INSTR_CODE:  48000002
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  nt!PpmIdleExecuteTransition+e43
    
    FOLLOWUP_NAME:  MachineOwner
    
    IMAGE_NAME:  hardware
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    IMAGE_VERSION:  10.0.10240.17022
    
    MODULE_NAME: hardware
    
    FAILURE_BUCKET_ID:  IP_MISALIGNED
    
    BUCKET_ID:  IP_MISALIGNED
    
    PRIMARY_PROBLEM_CLASS:  IP_MISALIGNED
    
    TARGET_TIME:  2016-07-23T15:24:42.000Z
    
    OSBUILD:  10240
    
    OSSERVICEPACK:  0
    
    SERVICEPACK_NUMBER: 0
    
    OS_REVISION: 0
    
    SUITE_MASK:  272
    
    PRODUCT_TYPE:  1
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 10
    
    OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS
    
    OS_LOCALE:  
    
    USER_LCID:  0
    
    OSBUILD_TIMESTAMP:  2016-06-24 05:57:23
    
    BUILDDATESTAMP_STR:  160623-1726
    
    BUILDLAB_STR:  th1_st1
    
    BUILDOSVER_STR:  10.0.10240.17022.amd64fre.th1_st1.160623-1726
    
    ANALYSIS_SESSION_ELAPSED_TIME: 3ed
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:ip_misaligned
    
    FAILURE_ID_HASH:  {201b0e5d-db2a-63d2-77be-8ce8ff234750}
    
    Followup:     MachineOwner
      My Computers


  3. Posts : 14,901
    Windows 10 Pro
       #13

    @Mashalien, please provide results to suggested tests, we are waiting for you to reply.
      My Computers


  4. Posts : 20
    Windows 10
    Thread Starter
       #14

    @axe0 The MemTest had 10 successful passes with no errors. The only other test mentioned was the Driver Verifier. Which spectacular backfired and required me to reset the computer to a previous state. I put down 'save documents' but evidently dmp files are not listed in the documents saved. I could try it again, but this time use a different method to turn the Verifier off, if you wish.
      My Computer


  5. Posts : 14,901
    Windows 10 Pro
       #15

    There are some ways to turn off driver verifier




    Diagnostic Test

     DRIVER VERIFIER


    warning   Warning
    Please make a backup of your important files and get your rescue media or create one.
    Please create a restore point.

    Please follow this tutorial to run driver verifier.

    Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

    Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

    If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

    Note   Note
    Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
      My Computers


  6. Posts : 20
    Windows 10
    Thread Starter
       #16

    Sorry for late response, there was a medical emergency.
    Will redo the Driver Verifier and post results shortly.

    UPDATE
    After I rebooted the PC to put Verifier into effect, it went through a 'scan and repair C drive' thing and then put me into the log in screen. The last time I used the Verifier I got BSOD within seconds. This time, it's been a few minutes and nothing has happened. It occurred to me that the scan and repair might have turned the Verifier off but the tutorial does not list a way to check to see if it is.
    Last edited by Mashalien; 26 Jul 2016 at 09:47. Reason: update
      My Computer


  7. Posts : 20
    Windows 10
    Thread Starter
       #17

    Alright so it finally crashed. Attached are the dmp files and BlueView screenshots.
    Attachment 92219
    Attachment 92220
    Last edited by Mashalien; 26 Jul 2016 at 12:48. Reason: posted before attached
      My Computer


  8. Posts : 14,901
    Windows 10 Pro
       #18

    You could check if driver verifier is enabled by entering (copy/paste) below command in an admin command prompt
    Code:
    verifier /query
    I'll leave the analysis to @Ztruker as he is the one that started troubleshooting.
      My Computers


  9. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #19

    Please post the results of verifier /query and verifier /querysettings from a Elevated Command Prompt, as verifier is not setup correctly:

    Code:
    2: kd> !verifier
    
    Verify Flags Level 0x00000000
    
      STANDARD FLAGS:
        [X] (0x00000000) Automatic Checks
        [ ] (0x00000001) Special pool
        [ ] (0x00000002) Force IRQL checking
        [ ] (0x00000008) Pool tracking
        [ ] (0x00000010) I/O verification
        [ ] (0x00000020) Deadlock detection
        [ ] (0x00000080) DMA checking
        [ ] (0x00000100) Security checks
        [ ] (0x00000800) Miscellaneous checks
        [ ] (0x00020000) DDI compliance checking
    
      ADDITIONAL FLAGS:
        [ ] (0x00000004) Randomized low resources simulation
        [ ] (0x00000200) Force pending I/O requests
        [ ] (0x00000400) IRP logging
        [ ] (0x00002000) Invariant MDL checking for stack
        [ ] (0x00004000) Invariant MDL checking for driver
        [ ] (0x00008000) Power framework delay fuzzing
        [ ] (0x00040000) Systematic low resources simulation
        [ ] (0x00080000) DDI compliance checking (additional)
        [ ] (0x00200000) NDIS/WIFI verification
        [ ] (0x00800000) Kernel synchronization delay fuzzing
        [ ] (0x01000000) VM switch verification
    
        [X] Indicates flag is enabled
    
    
    Summary of All Verifier Statistics
    
      RaiseIrqls           0x0
      AcquireSpinLocks     0x0
      Synch Executions     0x0
      Trims                0x0
    
      Pool Allocations Attempted             0x0
      Pool Allocations Succeeded             0x0
      Pool Allocations Succeeded SpecialPool 0x0
      Pool Allocations With NO TAG           0x0
      Pool Allocations Failed                0x0
    
      Current paged pool allocations         0x0 for 00000000 bytes
      Peak paged pool allocations            0x0 for 00000000 bytes
      Current nonpaged pool allocations      0x0 for 00000000 bytes
      Peak nonpaged pool allocations         0x0 for 00000000 bytes
    The dumps are similar to others you've uploaded, ntkrnlmp and AuthenticAMD. Neither was triggered by Driver Verifier.

    Setup Driver Verifer again. Make sure you check the boxes specified in the tutorial then see what we get.

    Attachment 92264
      My Computers


  10. Posts : 20
    Windows 10
    Thread Starter
       #20

    I'll have to do the test and post the results in a few hours
      My Computer


 

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

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




Windows 10 Forums