BSOD help

julianbraso said:

why my system clock out of sync ken?

I suspect it is more than your system clock. If you want to sync your clock go to the time and say update now.

If there is a modded OS it will tell you



See picture

Julian, please upload your latest .dmp file..

https://www.sevenforums.com/crashes-d...tructions.html

Hi,
Your dumps bugcheck:
- 0x1E = KMODE_EXCEPTION_NOT_HANDLED probably cause by driver or RAM
- 0x3B = SYSTEM_SERVICE_EXCEPTION

Msmpeng.exe was involved in the both dumps, It relates to your Windows Defender or MSE.
So I would recommend you to reinstall that applications.

Then these drivers need to be update:

Code:

ASACPI.sys   Wed May 13 18:25:17 2009 --> Asus ATK0110 ACPI Utility
AsIO.sys     Mon Apr 06 00:21:08 2009 --> Asus PCProbe Utility

Nvdia chipset drivers: 
nvmf6264.sys Thu Apr 30 12:45:59 2009
nvstor.sys   Tue May 19 23:45:37 2009
nvstor64.sys Wed Apr 29 18:57:30 2009

Make sure to do the update, and if the problem persist then test your RAM with memtest86 for at least 7 passes.
RAM - Test with Memtest86+

Code:

BugCheck 1E, {ffffffffc0000005, fffff800028f1065, 0, ffffffffffffffff}
Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+265 )

Log

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff800028ffc22, fffff88004239a70, 0}

Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800028ffc22, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88004239a70, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP: 
nt!KxWaitForLockOwnerShip+12
fffff800`028ffc22 48890a          mov     qword ptr [rdx],rcx

CONTEXT:  fffff88004239a70 -- (.cxr 0xfffff88004239a70)
rax=000000000000003e rbx=fffff80002a37e80 rcx=fffff80002a385e0
rdx=0040000000000000 rsi=0000000000000001 rdi=fffff80002a385e0
rip=fffff800028ffc22 rsp=fffff8800423a450 rbp=fffff8800423a4c0
 r8=4000000000000000  r9=0000000000000000 r10=00000000000002fe
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=fffffa80029bfb30 r15=0000000000812df0
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
nt!KxWaitForLockOwnerShip+0x12:
fffff800`028ffc22 48890a          mov     qword ptr [rdx],rcx ds:002b:00400000`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  MsMpEng.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff800028ffc22

STACK_TEXT:  
fffff880`0423a450 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxWaitForLockOwnerShip+0x12


FOLLOWUP_IP: 
nt!KxWaitForLockOwnerShip+12
fffff800`028ffc22 48890a          mov     qword ptr [rdx],rcx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KxWaitForLockOwnerShip+12

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

STACK_COMMAND:  .cxr 0xfffff88004239a70 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!KxWaitForLockOwnerShip+12

BUCKET_ID:  X64_0x3B_nt!KxWaitForLockOwnerShip+12

Followup: MachineOwner
---------

MSE should be OK; you can leave it for now. It is probably a victim of the crash rather than a cause. I think you have other problems. Please update the drivers that Wish listed above.