BSOD caused by driver ntoskrnl.exe

  1.    10 Feb 2016 #1

    BSOD caused by driver ntoskrnl.exe

    Dear All,

    I recently upgraded to Windows 10 Pro from 7 Pro and facing problem of BSOD, attached are minidumpts captured from my system for different dates.

    Please can any one help me on this to resolve it. Really making problem for me and I am unable to figure out the root.

    Waiting for help.

      My ComputerSystem Spec

  2.    10 Feb 2016 #2

    Hello, any body out there to help
      My ComputerSystem Spec

  3. axe0's Avatar
    Posts : 13,921
    Windows 10 Pro
       10 Feb 2016 #3

    warning   Warning
    Programs that claim to update your drivers install either the wrong or corrupted drivers.
    If you have installed any driver with Driver Genius, please remove them as it may cause trouble.

    Please be sure to update your VMware to the most recent version or remove it for the time of troubleshooting.
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
        # Any other values for parameter 1 must be individually examined.
    Arg1: 0000000000041284, A PTE or the working set list is corrupt.
    Arg2: 00000000f7261000
    Arg3: 000000000001076a
    Arg4: fffff58010804000
    Debugging Details:
    BUGCHECK_STR:  0x1a_41284
    PROCESS_NAME:  vmware-vmx.exe
    ffffd001`aa1db2d0  fffff800`1cb76160Unable to load image \??\C:\WINDOWS\system32\drivers\vmx86.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for vmx86.sys
    *** ERROR: Module load completed but symbols could not be loaded for vmx86.sys
    0: kd> lmvm vmx86
    start             end                 module name
    fffff800`1cb60000 fffff800`1cb7a000   vmx86    T (no symbols)           
        Loaded symbol image file: vmx86.sys
        Image path: \??\C:\WINDOWS\system32\drivers\vmx86.sys
        Image name: vmx86.sys
        Timestamp:        Sat Feb 07 03:29:47 2015 (54D5789B)
        CheckSum:         0001EE47
        ImageSize:        0001A000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My ComputersSystem Spec

  4.    16 Feb 2016 #4

    Hello Support,
    I changed my memories, I have four slots, I was having two one kind and two one kind but both DDR3, any way I changed all to same type. It is been 5/6 days no BSOD appeared again. So this could be from memory?
      My ComputerSystem Spec

  5. axe0's Avatar
    Posts : 13,921
    Windows 10 Pro
       16 Feb 2016 #5

    Yes it could be memory, using 2 different kind causes problems.
      My ComputersSystem Spec


Related Threads
Solved Various BSOD Caused by ntoskrnl.exe in BSOD Crashes and Debugging
Hi, I'm facing various BSOD. After I open minidump files via Bluescreenview, it's caused by Ntoskrnl.exe. Here's the minidump files Microsoft OneDrive - Access files anywhere. Create docs with free Office Online. Here's the screenshot of...
BSOD caused by driver ntoskrnl.exe in BSOD Crashes and Debugging
Hi, Got today brand new laptop-Alienware 17 R3. Randomly getting BSOD, some time irql_not_less_or_equal, or MEMORY_MANAGEMENT error. Happens during playing game or browsing or something else. Got 5-6 times. Could you help me please? Appreciate in...
Solved BSOD caused by ntoskrnl.exe please help in BSOD Crashes and Debugging
Hey all, I've attached 4 minidumps. Can you please help troubleshoot this intermittent BSOD?
BSOD caused by ntoskrnl.exe in BSOD Crashes and Debugging
Hello! I have recurring blue screens on my laptop and can't seem to figure out what's causing them. Sometimes, the computer also freezes completely without any forewarning and the only way to shut it down is to remoce the battery. I should...
BSOD caused by ntoskrnl.exe in BSOD Crashes and Debugging
BSODs have been happening for a while but I'm not really sure what's the actual cause.
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 18:22.
Find Us