New
#11
If i could, i would have asked you to check all the dump files as i dont know anything about the crash dump analysis,and because i have struggled so much with this BSOD errors. I can only work the laptop with a fear about when the next BSOD is going to happen.
But i donno if i will trouble you asking you to do that much..
Thanku for all the support. I appreciate your help. I will let you know if i get more BSOD's. Thanks a lot. :)
hello yowanvista, i found out that there is also another utility causing BSOD's by bluescreenview
it is the one causing some BSOD's, and this one - 020811-16302-01.dmp
can you tell me what caused the BSOD in this one?
It would be very helpful :)
Hey Yowanvista...
I had a BSOD again. Please help me. Please check it out.
This one indicates no probable cause, please use driver verifier
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: 0000000000000000, The exception code that was not handled Arg2: 0000000000000000, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000000000000, Parameter 1 of the exception Debugging Details: ------------------ EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully. FAULTING_IP: +0 00000000`00000000 ?? ??? EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000000 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x1E PROCESS_NAME: System CURRENT_IRQL: 0 EXCEPTION_RECORD: fffff8800391ba38 -- (.exr 0xfffff8800391ba38) ExceptionAddress: fffff800034176dc (hal!KeQueryPerformanceCounter+0x0000000000000104) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff TRAP_FRAME: fffff8800391bae0 -- (.trap 0xfffff8800391bae0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=000000038fb8d22f rbx=0000000000000000 rcx=0000000000000001 rdx=00000e3e00000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff800034176dc rsp=fffff8800391bc70 rbp=0000000000000000 r8=fffffa800b7d35e0 r9=000000000025a7ee r10=0000000000000000 r11=fffff880009ec180 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up di pl nz na po nc hal!KeQueryPerformanceCounter+0x104: fffff800`034176dc 4c890f mov qword ptr [rdi],r9 ds:e380:00000000`00000000=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800034bac2e to fffff800034c2ed0 STACK_TEXT: fffff880`0391ab18 fffff800`034bac2e : 00000000`00000000 fffffa80`04501f90 fffff880`0391b290 fffff800`034efe28 : nt!KeBugCheck fffff880`0391ab20 fffff800`034e8bed : fffff800`036cff78 fffff800`0360e1d0 fffff800`03451000 fffff880`0391ba38 : nt!KiKernelCalloutExceptionHandler+0xe fffff880`0391ab50 fffff800`034f0250 : fffff800`03610b5c fffff880`0391abc8 fffff880`0391ba38 fffff800`03451000 : nt!RtlpExecuteHandlerForException+0xd fffff880`0391ab80 fffff800`034fd1b5 : fffff880`0391ba38 fffff880`0391b290 fffff880`00000000 01000000`00000000 : nt!RtlDispatchException+0x410 fffff880`0391b260 fffff800`034c2542 : fffff880`0391ba38 00000000`00000002 fffff880`0391bae0 fffff880`009ec180 : nt!KiDispatchException+0x135 fffff880`0391b900 fffff800`034c0e4a : fffffa80`043dfeb0 00000000`00000000 00000000`00000000 fffffa80`043dfed0 : nt!KiExceptionDispatch+0xc2 fffff880`0391bae0 fffff800`034176dc : 00000000`00000001 fffffa80`0d1b3450 ffffffff`fffffffd 00000000`00000014 : nt!KiGeneralProtectionFault+0x10a fffff880`0391bc70 fffff800`034d0ab7 : 00000000`0025a7ee 00000000`00000002 fffff880`009ec180 00000000`00000001 : hal!KeQueryPerformanceCounter+0x104 fffff880`0391bca0 fffff800`034cb6cc : fffff880`009ec180 fffff880`00000002 00000000`00000002 fffff880`00000000 : nt!PoIdle+0x5b7 fffff880`0391bd80 00000000`00000000 : fffff880`0391c000 fffff880`03916000 fffff880`0391bd40 00000000`00000000 : nt!KiIdleLoop+0x2c STACK_COMMAND: kb FOLLOWUP_IP: nt!KiKernelCalloutExceptionHandler+e fffff800`034bac2e 90 nop SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!KiKernelCalloutExceptionHandler+e FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600 FAILURE_BUCKET_ID: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e BUCKET_ID: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e Followup: MachineOwner ---------
what do you mean to use driver verifier??
what do you mean use driver verifier??
Enable it Driver Verifier - Enable and Disable
Then upload any new dump files created
I notice Kaspersky has been shown as the cause in more than one of your.dmp files so for the purpose of debugging please can you remove kaspersky and replace with MSE or Avira until you have found the cause ?
please continue to upload anymore .dmp files as they occur ?
Before i could get on to it, I got two more
Attached the files.