New
#1
AcdSee BSOD KERNEL_SECURITY_CHECK_ERROR
Hi all,
First of all, i spend a lot of time trying to understand my problem, checked lot of drivers, tested "verifier" function under windows but without success, so need your help :)
verifier crash at startup without say me the problem
My Windows 10 x64 work pretty well BUT each time i launch ANY version of ACDSee i got a BSOD with KERNEL_SECURITY_CHECK_ERROR
It can appear at launch or some seconds after using it.
What ive done so far :
MemTest
Updated all drivers
Downgrade Intel ME from v11 to v8 ( as v11 shown a yellow exclamation, and find this good solution on forum)
Trying forced it to launch with nvidia drivers or intel drivers change nothing.
No virus, no adware
Version 8, version 9, version 9 pro do the same
Cleaning registry etc..
Unpluged some USB device
Disable WIFI and bluetooth drivers ( for a time i think it was it, but no )
MSI web site, doesn't give win 10 specific drivers ( MSI Global )
A lot are windows 10 native
I don't understand because i used this software for long time and i d'ont change anything in my laptop configuration.
Hope you will find something i miss , thanks by advance !
OSRonline sit give me this but not sure what to understand :
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR Homepage | OSR)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 10240 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10240.16590.amd64fre.th1_st1.151104-1714
Machine Name:
Kernel base = 0xfffff801`ca01e000 PsLoadedModuleList = 0xfffff801`ca343070
Debug session time: Sun Jan 10 15:21:19.113 2016 (UTC - 5:00)
System Uptime: 0 days 2:02:34.764
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffd00024829670, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffd000248295c8, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
OVERLAPPED_MODULE: Address regions for 'srvnet' and 'dump_storpor' overlap
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x139
PROCESS_NAME: ACDSeeIndexerP
CURRENT_IRQL: 2
BAD_PAGES_DETECTED: 5a3a
LAST_CONTROL_TRANSFER: from fffff801ca177ea9 to fffff801ca16d4d0
STACK_TEXT:
ffffd000`24829348 fffff801`ca177ea9 : 00000000`00000139 00000000`00000003 ffffd000`24829670 ffffd000`248295c8 : nt!KeBugCheckEx
ffffd000`24829350 fffff801`ca1781d0 : 00000000`00000000 ffffab1c`c993b6ce 00000000`00000000 fffff800`33343861 : nt!KiBugCheckDispatch+0x69
ffffd000`24829490 fffff801`ca1773f4 : ffffe000`42fbd090 00000000`00000000 00000000`00000000 ffffe000`47608b20 : nt!KiFastFailDispatch+0xd0
ffffd000`24829670 fffff801`ca1adbb6 : 00000000`00000000 fffff901`4079d2e0 fffff901`4079d205 fffff901`00000001 : nt!KiRaiseSecurityCheckFailure+0xf4
ffffd000`24829800 fffff960`6c6b6313 : fffff901`4079d2e0 fffff901`42617500 ffffe000`474d7080 ffffd000`24829a99 : nt! ?? ::FNODOBFM::`string'+0x31ab6
ffffd000`24829830 fffff960`6c6b617b : 00000000`00000000 fffff901`42617500 ffffd000`248299d8 fffff960`6c674c0c : win32kbase!DirectComposition::CChannel::OnProcessDestruction+0x4b
ffffd000`24829860 fffff960`6c6b606a : 00000000`00000000 00000000`00000000 00000000`00000000 ffffd000`248299d8 : win32kbase!DirectComposition::CProcessData::`scalar deleting destructor'+0x1f
ffffd000`24829890 fffff960`6c3bd5a4 : fffff901`4513d720 ffffe000`47608800 00000000`00000000 ffffe000`43e99180 : win32kbase!DCompositionProcessCallout+0x3a
ffffd000`248298c0 fffff801`ca4bcc82 : ffffd000`248299d8 ffffd000`24829a99 ffffe000`43e99180 00000000`00000000 : win32kfull!W32pProcessCallout+0xb4
ffffd000`248298f0 fffff801`ca4bd39f : 00000000`00000000 ffffe000`4469a920 ffffd000`24829a99 00000000`00000001 : nt!PsInvokeWin32Callout+0x42
ffffd000`24829930 fffff801`ca4a400a : 00000000`00000000 ffffd000`24829a01 00000000`00000000 ffffe000`474d7080 : nt!PspExitThread+0x66f
ffffd000`24829a30 fffff801`ca177b63 : 00000000`00000006 ffffffff`ffff0000 ffffe000`47608800 ffffd000`24829b80 : nt!NtTerminateProcess+0x11a
ffffd000`24829b00 00007ff9`8e19383a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000093`a0edfbe8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ff9`8e19383a
STACK_COMMAND: kb
SYMBOL_NAME: PAGE_NOT_ZERO
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: PAGE_NOT_ZERO
Followup: MachineOwner
---------
*** Memory manager detected 23098 instance(s) of page corruption, target is likely to have memory corruption.
Here is my configuration : Configuration
Last edited by PinkFloyd; 12 Jan 2016 at 15:51.