BSOD caused by driver ntoskrnl.exe

wajeeh1981 · 10 Feb 2016

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.

Regards,
Wajeeh

wajeeh1981 · 10 Feb 2016

Hello, any body out there to help

axe0 · 10 Feb 2016

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.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: 00000000f7261000
Arg3: 000000000001076a
Arg4: fffff58010804000

Debugging Details:
------------------

BUGCHECK_STR:  0x1a_41284

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  vmware-vmx.exe

CURRENT_IRQL:  2


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
 vmx86+0x16160

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

wajeeh1981 · 16 Feb 2016

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?
Regards,

axe0 · 16 Feb 2016

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