Constant BSOD crashes while using several programs video conv/player..


  1. Posts : 1
    Windows 7 Home Premium 64bit
       #1

    Constant BSOD crashes while using several programs video conv/player..


    I've recently been getting ntoskrnl.exe errors, I've ran memeory diagnostics and ran several malware/virus scanners and currently am not picking up anything. I've attached all my dumb files from your diagnostics tool. Let me know if you need anything else!
      My Computer


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

    ntoskrnl.exe is a system kernel on which the computer is crashing. It is failing to find the appropriate cause of the crash and so blaming the kernel itself.

    We need to see some more info, so upload your MSINFO32.nfo file.

    1. Click on the start button
    2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
    3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
    4. Give the time for processing, it will save a .nfo file on your desktop.
    5. Zip it, and upload it following the instruction.

    Your crash dumps are not showing any finite probable cause.

    Test your RAM modules for possible errors.
    How to Test and Diagnose RAM Issues with Memtest86+
    Run memtest for at least 8 passes, preferably overnight.

    If memtest comes clean, enable Driver Verifier to monitor the drivers.
    Driver Verifier - Enable and Disable
    Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

       Information
    Why Driver Verifier:
    It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

    How Can we know that DV is enabled:
    It will make the system bit of slow, laggy.

       Warning
    Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

    If there is no points, make a System Restore Point manually before enabling DV.

       Tip




    Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.
    -------------------------------------------------------------------------
    BSOD ANALYSIS:
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 109, {a3a039d896468985, b3b7465ee8c4c747, fffff80000b96bb0, 6}
    
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Probably caused by : ntoskrnl.exe ( nt_fffff80000b95000+1bb0 )
    
    Followup: MachineOwner
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    CRITICAL_STRUCTURE_CORRUPTION (109)
    This bugcheck is generated when the kernel detects that critical kernel code or
    data have been corrupted. There are generally three causes for a corruption:
    1) A driver has inadvertently or deliberately modified critical kernel code
     or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
    2) A developer attempted to set a normal kernel breakpoint using a kernel
     debugger that was not attached when the system was booted. Normal breakpoints,
     "bp", can only be set if the debugger is attached at boot time. Hardware
     breakpoints, "ba", can be set at any time.
    3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
    Arguments:
    Arg1: a3a039d896468985, Reserved
    Arg2: b3b7465ee8c4c747, Reserved
    Arg3: fffff80000b96bb0, Failure type dependent information
    Arg4: 0000000000000006, Type of corrupted region, can be
        0 : A generic data region
        1 : Modification of a function or .pdata
        2 : A processor IDT
        3 : A processor GDT
        4 : Type 1 process list corruption
        5 : Type 2 process list corruption
        6 : Debug routine modification
        7 : Critical MSR modification
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    nt_fffff80000b95000+1bb0
    fffff800`00b96bb0 48895c2408      mov     qword ptr [rsp+8],rbx
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x109
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`031bd5d8 00000000`00000000 : 00000000`00000109 a3a039d8`96468985 b3b7465e`e8c4c747 fffff800`00b96bb0 : nt!KeBugCheckEx
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt_fffff80000b95000+1bb0
    fffff800`00b96bb0 48895c2408      mov     qword ptr [rsp+8],rbx
    
    SYMBOL_NAME:  nt_fffff80000b95000+1bb0
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt_fffff80000b95000
    
    IMAGE_NAME:  ntoskrnl.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5149a99c
    
    FAILURE_BUCKET_ID:  X64_0x109_6_nt_fffff80000b95000+1bb0
    
    BUCKET_ID:  X64_0x109_6_nt_fffff80000b95000+1bb0
    
    Followup: MachineOwner
    ---------
    
    3: kd> lmvm nt_fffff80000b95000
    start             end                 module name
    fffff800`00b95000 fffff800`00bab000   nt_fffff80000b95000 T (no symbols)           
        Loaded symbol image file: ntoskrnl.exe
        Image path: \SystemRoot\system32\ntoskrnl.exe
        Image name: ntoskrnl.exe
        Timestamp:        Wed Mar 20 17:50:44 2013 (5149A99C)
        CheckSum:         0000B8CF
        ImageSize:        00016000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  3. Posts : 2,014
    Windows 7 Professional 64bit
       #3



    Hi,
    There is a lot of info missing in your logs:

    Here are the instructions for posting:

    Posting Instructions

       Tip
    Ensure you click the "GRAB ALL" button and then wait for each window to appear in turn and then click OK



    Cheers

    Dave

    OOps! Sorry Arc
      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 01:47.
Find Us